System License Violation - Part II

  • Thread starter Thread starter Kevin W
  • Start date Start date
K

Kevin W

The distributor sent me a XPE PID that their MS Guru used to make a
successful built. I copy and paste it from the email and same
System_License_Violation! The following is my FBALOG.txt

Tuesday, August 16, 2005

17:24:35 PM - [FBASetProgressText] Setting PNP Flag...
17:24:45 PM - [FBASetProgressText] Initializing...
17:24:45 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAInitialize
17:24:45 PM - [FBASetProgressText] Setting SystemPrefix...
17:24:45 PM - [FBASetProductKey] Invalid product key
17:24:45 PM - [FBASetProgressText] Resetting Setup Flag...
17:24:45 PM - [FBASetProgressText] Replacing System Hives...
17:24:45 PM - [FBASetProgressText] Resetting Setup Flag...
17:24:46 PM - [FBAFlushFilesToDisk] FlushFileBuffers(C:\) succeeded!

1. My image boots fine without the PID for the past two months
2. The boot partition is set to 5000 (max value) running on a 20 GB
partition (40 GB HD). It is the only partition and 4/6/20/40 GB gives
the same exact error.
3. I tried 3 PIDs so far, two from stickers and one from email. They
are 100% spelled correctly with 25 symbols + 4 dashes.
4. The drive letter is set to C (active) and I always do a clean
format.
5. System date/time is correct according to some posts.

What else can possibly cause this license error? How can I tell if I
am running SP2? I have TD version 2.00 and "Windows XP Embedded Tools
Update SP2" in my add/remove program. Is the PID really specific to
SP1 or SP2?

Any help would be greatly appreciated!
 
Of course, the PID from the distributor may be incorrect again. But I
am starting to get the feeling this is 70% possibility fault on my end.
 
Strangly, a clean install of XPE Development Tool SP2 fixed the
problem. No idea why tho.
 
Back
Top