Blue Screen On FBE after PID was entered



Don Streng
07-09-2005, 09:26 PM
Received a valid PID and entered it into a build that works fine
in evaluation mode. On FBE it choked rebooted and came up
with a blue screen with bold letters about a LICENSE_VIOLATION etc...

This PID worked on a earlier config that I used to test the PID
with. I didn't find and documentation saying that you can only
enter the PID in once to one configuration before you're SOL
but that appears to be the case. Has anyone else ran into this
frustration feature or am I doing something stupid?

KM
07-09-2005, 09:26 PM
Don,

There is no technical limitations on number of times you can use one PID in different projects but legal restrictions.

You may want to check that:
- the PID is in 5x-5x-5x-5x-5x format
- it is a valid PID from a COA sticker
- your target device specs match the settings you put in TD (target boot partition size)
- you build configuration with the right PID entered (Build process shouldn't throw the error about image evaluation period)

KM

> Received a valid PID and entered it into a build that works fine
> in evaluation mode. On FBE it choked rebooted and came up
> with a blue screen with bold letters about a LICENSE_VIOLATION etc...
>
> This PID worked on a earlier config that I used to test the PID
> with. I didn't find and documentation saying that you can only
> enter the PID in once to one configuration before you're SOL
> but that appears to be the case. Has anyone else ran into this
> frustration feature or am I doing something stupid?

Don Streng
07-09-2005, 09:26 PM
KM,

The PID is a valid PID from BSQUARE with a valid COA sticker.
It was entered in the proper 5x-5x-5x-5x-5x format.
For partition boot size I used a 1G compact Flash so I originaly
left the default of 1024 but after reading your message changed
it to 977M based on what XP Pro returns as the size 1024K bytes or 977M.
This had no affect on the getting rid of the problem during
the First Boot Experience i.e. Details follow

Blue Screen with
SYSTEM_LICENSE_VIOLATION

A bunch of meaningless Microsoft info. about stuff that's obvious

STOP 0x0000009A (0x00000004, 0xC0000034, 0x00000000, 0x00000000)

Thanks for taking a stab at it.

Don


"KM" wrote:

> Don,
>
> There is no technical limitations on number of times you can use one PID in different projects but legal restrictions.
>
> You may want to check that:
> - the PID is in 5x-5x-5x-5x-5x format
> - it is a valid PID from a COA sticker
> - your target device specs match the settings you put in TD (target boot partition size)
> - you build configuration with the right PID entered (Build process shouldn't throw the error about image evaluation period)
>
> KM
>
> > Received a valid PID and entered it into a build that works fine
> > in evaluation mode. On FBE it choked rebooted and came up
> > with a blue screen with bold letters about a LICENSE_VIOLATION etc...
> >
> > This PID worked on a earlier config that I used to test the PID
> > with. I didn't find and documentation saying that you can only
> > enter the PID in once to one configuration before you're SOL
> > but that appears to be the case. Has anyone else ran into this
> > frustration feature or am I doing something stupid?
>
>
>

KM
07-09-2005, 09:26 PM
Don,

I have no clue why you see the BSOD.
I would still think it is a bad PID. Any chance for you to create a simple
image (use Minlogon sample Macro) for the target hardware and test the PID
there?

Do you deploey the iamge and run FBA there on CF card directly?

KM

> KM,
>
> The PID is a valid PID from BSQUARE with a valid COA sticker.
> It was entered in the proper 5x-5x-5x-5x-5x format.
> For partition boot size I used a 1G compact Flash so I originaly
> left the default of 1024 but after reading your message changed
> it to 977M based on what XP Pro returns as the size 1024K bytes or 977M.
> This had no affect on the getting rid of the problem during
> the First Boot Experience i.e. Details follow
>
> Blue Screen with
> SYSTEM_LICENSE_VIOLATION
>
> A bunch of meaningless Microsoft info. about stuff that's obvious
>
> STOP 0x0000009A (0x00000004, 0xC0000034, 0x00000000, 0x00000000)
>
> Thanks for taking a stab at it.
>
> Don
>
>
> "KM" wrote:
>
>> Don,
>>
>> There is no technical limitations on number of times you can use one PID
>> in different projects but legal restrictions.
>>
>> You may want to check that:
>> - the PID is in 5x-5x-5x-5x-5x format
>> - it is a valid PID from a COA sticker
>> - your target device specs match the settings you put in TD (target
>> boot partition size)
>> - you build configuration with the right PID entered (Build process
>> shouldn't throw the error about image evaluation period)
>>
>> KM
>>
>> > Received a valid PID and entered it into a build that works fine
>> > in evaluation mode. On FBE it choked rebooted and came up
>> > with a blue screen with bold letters about a LICENSE_VIOLATION etc...
>> >
>> > This PID worked on a earlier config that I used to test the PID
>> > with. I didn't find and documentation saying that you can only
>> > enter the PID in once to one configuration before you're SOL
>> > but that appears to be the case. Has anyone else ran into this
>> > frustration feature or am I doing something stupid?
>>
>>
>>

Don Streng
07-09-2005, 09:26 PM
KM,

Thanks for you suggestions. I had already called BSquare to ask for another
PID. They sent it. It worked. All is right with the world again.

Don

"KM" wrote:

> Don,
>
> I have no clue why you see the BSOD.
> I would still think it is a bad PID. Any chance for you to create a simple
> image (use Minlogon sample Macro) for the target hardware and test the PID
> there?
>
> Do you deploey the iamge and run FBA there on CF card directly?
>
> KM
>
> > KM,
> >
> > The PID is a valid PID from BSQUARE with a valid COA sticker.
> > It was entered in the proper 5x-5x-5x-5x-5x format.
> > For partition boot size I used a 1G compact Flash so I originaly
> > left the default of 1024 but after reading your message changed
> > it to 977M based on what XP Pro returns as the size 1024K bytes or 977M.
> > This had no affect on the getting rid of the problem during
> > the First Boot Experience i.e. Details follow
> >
> > Blue Screen with
> > SYSTEM_LICENSE_VIOLATION
> >
> > A bunch of meaningless Microsoft info. about stuff that's obvious
> >
> > STOP 0x0000009A (0x00000004, 0xC0000034, 0x00000000, 0x00000000)
> >
> > Thanks for taking a stab at it.
> >
> > Don
> >
> >
> > "KM" wrote:
> >
> >> Don,
> >>
> >> There is no technical limitations on number of times you can use one PID
> >> in different projects but legal restrictions.
> >>
> >> You may want to check that:
> >> - the PID is in 5x-5x-5x-5x-5x format
> >> - it is a valid PID from a COA sticker
> >> - your target device specs match the settings you put in TD (target
> >> boot partition size)
> >> - you build configuration with the right PID entered (Build process
> >> shouldn't throw the error about image evaluation period)
> >>
> >> KM
> >>
> >> > Received a valid PID and entered it into a build that works fine
> >> > in evaluation mode. On FBE it choked rebooted and came up
> >> > with a blue screen with bold letters about a LICENSE_VIOLATION etc...
> >> >
> >> > This PID worked on a earlier config that I used to test the PID
> >> > with. I didn't find and documentation saying that you can only
> >> > enter the PID in once to one configuration before you're SOL
> >> > but that appears to be the case. Has anyone else ran into this
> >> > frustration feature or am I doing something stupid?
> >>
> >>
> >>
>
>
>


Blue Screen On FBE after PID was entered