which code is PID?

  • Thread starter Thread starter Jordi Giró \(ALVIC\)
  • Start date Start date
J

Jordi Giró \(ALVIC\)

I bought some runtime licenses for the Release version of XPe

and there are 3 codes

xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
yyyyy-yyy-yyy-yyy
zzz-zzzzz

wich I need to put into PID code?
 
Jordi,

I haven't bought stickers in awhilke, but the x's are the right format. I'd
use that key.

HTH,
Brad
 
Jordi said:
I bought some runtime licenses for the Release version of XPe

and there are 3 codes

xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
yyyyy-yyy-yyy-yyy
zzz-zzzzz

wich I need to put into PID code?
Click to expand...

Neither, I think, unless I misunderstood the question.

The PID is obtained separately from your dealer (where you got the
license for the development environment), one PID per project.

5x5 (the X-es) is the right format, but then the code would be different
for each license. Save yourself the typing ;)
 
Lucvdv said:
Neither, I think, unless I misunderstood the question.

The PID is obtained separately from your dealer (where you got the
license for the development environment), one PID per project.

5x5 (the X-es) is the right format, but then the code would be
different for each license. Save yourself the typing ;)
Click to expand...

If you have a deployment of 100, you'll receive 100 different PIDs (on
stickers). You can choose any one of those to act as your project PID to
enter into your SLX in TD.
 
If you have a deployment of 100, you'll receive 100 different PIDs (on
stickers). You can choose any one of those to act as your project PID to
enter into your SLX in TD.
Click to expand...

I didn't know those were all valid (assumed not, because not all PID's on
the toolkit CD's could be used to install the toolkit either).

I was thinking of how I got it, and of previous messages in this group, for
example
http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded/msg/82d447222c90c929
http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded/msg/91c9746974257557


Anyway, Jordi can just try: with the wrong PID he'll get a STOP 9A ;)
 
I found it!!!

is the 12345-67890-12345-67890-12345

without the "-"

1234567890123456789012345

:)
 
I found it!!!

is the 12345-67890-12345-67890-12345

without the "-"

1234567890123456789012345
Click to expand...


It works *with* the dashes here. I copied/pasted the key from the mail in
which I received it straight into TD to avoid typing errors, and it works.

Make sure your device didn't revert to a time-limited demo, as it would be
without a PID. I think you can check it in fbalog.txt: somewhere near the
top, there's

HH:MM:SS AM - [FBASetProductKey] Retail Product Key

I assume that line would say "demo" or "evaluation" if there's no PID.
 
Jordi,

Are you sure you used the PID numbers without the dashes?
I have always been using it here with the dashes. (the format is exactly what I mentioned: 5x-5x-5x-5x-5x)
 
Yes.

Works without the dashes.

KM said:
Jordi,

Are you sure you used the PID numbers without the dashes?
I have always been using it here with the dashes. (the format is exactly
Click to expand...
what I mentioned: 5x-5x-5x-5x-5x)
 
I'd double check that. My guess is that your image will timeout. I've
always used with the dashes also.
 
I vote for dashed flavor also.

Although I do not remember what was happening when there was wrong PID. Did XPe BSOD or reported eval version.

Regards,
Slobodan
 
Slobodan,

IIRC, if you use a wrong PID (e.g., without dashes) the image turns to Eval.
This means that you will get the "Evaluation ..." string at the right bottom corner of the Desktop at run time.

At least that is how it used to be :-)
 
Slobodan said:
I vote for dashed flavor also.

Although I do not remember what was happening when there was wrong PID. Did XPe BSOD or reported eval version.
Click to expand...

There have been some posts about STOP 9A with the wrong PID, and I think
everyone will know that no PID at all results in an eval build.

I wonder what happens if the PID _format_ is wrong.

I wanted to try it out earlier this week, but didn't get around to it.
 
Back
Top