System_License_Violation

[Kent Petersen]

Here it is again. My image works just fine if I build w/o entering the
run-time PID. I make no other changes in TD except to enter the 25 digit
run-time PID:

XXXXX-XXXXX-XXXXX-XXXXX

from the sticker sold to me by the distrubuter (I have to put on a different
pair of glasses to read it . The Target device settings are set to "C"
for the folders and the boot partition size is 2000 MB. I'm using
Slobodan's registry hack to force the boot drive to be "c" on the Multi-OS
HDD I'm using in the target. Again with no other change than leaving the
PID key blank the evaluation image works just fine.

Am I to the point where I need to contact the distributer?

 

[Kent Petersen]

Just had a look at the offending FBALOG. There's only 8-10 lines in it ,
one of which is simply "Invalid product key".

 

[Slobodan Brcin]

Type in the dashes also.

25+4=29 characters

Slobodan

 

[Kent Petersen]

I had 29 characters (included the dashes).

Kent

Type in the dashes also.

25+4=29 characters

Slobodan

 

[Slobodan Brcin]

I have just remembered, you need to set in TD partition size. But in your
case this is size of partition where XPE is loaded not C: from XP.

Does this helps?

Slobodan

 

[Kent Petersen]

I'm not quite sure I understand. When my target is booted up in XPPro, I
copy the image to the E drive. This partition is 2 GB in size. When I
re-boot and come up in XPe, it is now the C drive (because of your registry
settings you gave me). In XPe, the C drive is 2 GB and this is the number I
enter in TD for boot partition size (2000 MB).

Again, if I simply remove the PID and leave it empty, re-build (changing
nothing else), the image runs fine albiet in "Evaluation Mode".

Am I understanding this correctly?

Kent

 

[Slobodan Brcin]

You are using it correct then.

I have newer tried to use so large partitions for XPE with PID entered.
I'm using 64, and 196 MB sizes with PID and it works.

I don't know if this has any value but you should try 2048 MB (2GB).

Slobodan

 

[Kent Petersen]

After setting size to 2048 I still get the same error. Here's the entire
FBA log that I get:

0:20:02 AM - [FBASetProgressText] Setting PNP Flag...
0:20:12 AM - [FBASetProgressText] Initializing...
0:20:12 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAInitialize
0:20:12 AM - [FBASetProgressText] Setting SystemPrefix...
0:20:12 AM - [FBASetProductKey] Invalid product key
0:20:13 AM - [FBASetProgressText] Resetting Setup Flag...
0:20:13 AM - [FBARemoveRestart] Updated BootExecute!
0:20:13 AM - [FBASetProgressText] Replacing System Hives...
0:20:13 AM - [FBASetProgressText] Resetting Setup Flag...
0:20:14 AM - [FBAFlushFilesToDisk] FlushFileBuffers(C:\) succeeded!

I guess the entries after "Invalid product key" are just FBA putting its
ducks in a row before re-booting to a BSOD.

Kent Petersen

 

[Slobodan Brcin]

Just had a look at the offending FBALOG. There's only 8-10 lines in it ,

one of which is simply "Invalid product key".

I saw your last post.
Invalid product key is probably just that.

Look at the links:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=PID&btnG=Googl
e+Search&meta=group%3Dmicrosoft.public.windowsxp.embedded.*

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=Invalid+produc
t+key&btnG=Google+Search&meta=group%3Dmicrosoft.public.windowsxp.embedded.*



This was problem long time ago, all new stickers are ok, and you can use
numbers from them. But somehow you could be given old sticker.

Regards,
Slobodan


PS:
Stupid me, I lead discussion in probably wrong direction.