Run Time PID problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Having developed an application for Windows Embedded I am now trying to build
a fully functional Runtime Image.

I have the full (not evaluation) version of Windows XP Embedded (+SP2) and
have purchased a Runtime Key.

When I enter the runtime PID into the Settings of the Build Configuration
and run the resulting build on my target platform the First Boot Agent
reboots and causes a blue screen error SYSTEM_LICENSE_VIOLATION with the
codes ...

*** STOP : 0x0000009A (0x00000004, 0xC00000034, 0x00000000, 0x00000000)

Does anyone know what I have done wrong ?

The runtime PID I have is a standard 25 digit code in 5 blocks of 5, but the
entry box in Embedded Studio is just a blank input window. Do I enter the
dashes ? Upper or lower case ?

If I build an image without a PID it creates a working image but time limited.

Any help would be much appreciated.
Thanks
Mark
 
Usually this is one of a couple of different things that could be wrong....

1) The partition size in the "Setting/Target Device Settings/Boot Partition
Size" of your image doesn't match your actual image partition.

2) You have the toolkit with SP2, but SP2 didn't get installed. Make sure
you got SP2 installed. Either look in the Database Manager for the
repostitory or look to see if the marco component "Windows Application
Compatibility" exists in "Software\Test & Development". This is just a
random one that I know SP2 added. Not getting SP2 installed when you think
it has been has happened a lot.

3) You are not using the correct Runtime Key..this should have come on a
card that was with the XP Embedded COA license. The sticker is orange in
color on the card and says Runtime Product Key

-Scott Figg
Arrow Electronics
 
And to add a little bit more to this. Yes, you should type in dashes.

Just type in the PID as shown on the sticker: xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
 
Mark said:
Having developed an application for Windows Embedded I am now trying to build
a fully functional Runtime Image.

I have the full (not evaluation) version of Windows XP Embedded (+SP2) and
have purchased a Runtime Key.

When I enter the runtime PID into the Settings of the Build Configuration
and run the resulting build on my target platform the First Boot Agent
reboots and causes a blue screen error SYSTEM_LICENSE_VIOLATION with the
codes ...

*** STOP : 0x0000009A (0x00000004, 0xC00000034, 0x00000000, 0x00000000)

Does anyone know what I have done wrong ?

The runtime PID I have is a standard 25 digit code in 5 blocks of 5, but the
entry box in Embedded Studio is just a blank input window. Do I enter the
dashes ? Upper or lower case ?

If I build an image without a PID it creates a working image but time limited.

Any help would be much appreciated.
Thanks
Mark
Click to expand...

check PID with you distributor .
maybe it wrong.

Johnny Wu
(e-mail address removed)
 
Use the dashes and check the partition size and cluster size in Target
Device Settings

--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Back
Top