System_License_Violation revisited

My distributer got me a new PID to try. We suspect that the original one
was from a batch near the beginning of the year that was known to be bad.
When I tried the new one, I still get the BSOD with
"System_License_Violation". The only difference is that the line before
"Invalid product key" in the FBA log now says "FBAPidGen Failed!" Does this
mean he gave me a PID for the Embedded tools instead of one for a run-time?
I say this from looking at the MS posts to the newsgroup after searching for
"FBAPidGen Failed!"

I guess its about time for a MS person to weigh-in on this issue...please!

3:23:13 AM - [FBASetProgressText] Setting PNP Flag...
3:23:25 AM - [FBASetProgressText] Initializing...
3:23:25 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAInitialize
3:23:25 AM - [FBASetProgressText] Setting SystemPrefix...
3:23:25 AM - [FBAPidGen] PIDGenW returned: [0]
3:23:25 AM - [FBASetProductKey] FBAPidGen Failed!
3:23:25 AM - [FBASetProductKey] Invalid product key
3:23:25 AM - [FBASetProgressText] Resetting Setup Flag...
3:23:26 AM - [FBARemoveRestart] Updated BootExecute!
3:23:26 AM - [FBASetProgressText] Replacing System Hives...
3:23:26 AM - [FBASetProgressText] Resetting Setup Flag...
3:23:27 AM - [FBAFlushFilesToDisk] FlushFileBuffers(C:\) succeeded!

To All:

Apparantly there was a type in the last PID from the distributor. After we
straightened that out my image is now working!

Sorry for the apparantly frustrated post.

Kent