Invalid license

  • Thread starter Thread starter ExpatEgghead
  • Start date Start date
E

ExpatEgghead

We have a p;roblem with our first build on XP Embedded. In short, in
spite of having 50 paid up licenses for prototypes, at the first one
all I get is a BSOD after FBA with the SYSTEM_LICENSE_INVALID.

I have embedded studio with Service Pack 2 but not the Feature pack. I
have checked the PID, several times, with other people. I've checked
the drives (one C: with XP Pro, D: for XPe). I've done the bit with
the partition size.

Short of wiping the dev PC and reinstalling I'm out of things to try.
Anybody any ideas? I have read all the posts in the past on this
subject and all I can think of is that I have a duff set of PIDs.

Adrian Edmonds
 
The number that you enter into Target Designer can be found on the yellow
card that comes with the license stickers. Do not enter the number that is
on the XPe tools box or the number on the stickers?

If you are entering the 5x5 alphanumberic number on the yellow card, talk to
your distributor to see if there is an error?

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
 
The number that you enter into Target Designer can be found on the yellow
card that comes with the license stickers. Do not enter the number that is
on the XPe tools box or the number on the stickers?

If you are entering the 5x5 alphanumberic number on the yellow card, talkto
your distributor to see if there is an error?

Regards,

Sean Limingwww.sjjmicro.com/www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
Thanks Sean. I'll post a follow up on this.
 
Well all;

As an update we are still trying to solve this problem. We got
escalated past our local distributors to Microsoft Ireland.
Unfortunately, they we're busy at an exhibition. It got bounced to
Redmond, didn't stop and ended up with Microsoft China. After some
documents,screen shots and emails later, they are convinced we're
doing things right and the PID is bad. The distributer is supposed to
supply one , good , known working PID but it isn't here yet.

Our customer is not happy and we're not exactly over the moon either.
Embedded Linux looks more and more attractive.

adrian
 
Do you have the Enhanced Write Filter included in your image? If yes try to
disable it and check if the error still occurs. I have had this behaviour
several times now and that fixed it.

Wolfgang
 
Not yet Wolfgang. I will try though once I get through the other
solutions from Microsoft.

adrian
 
I've seen on this group(Sean Liming maybe) that defining boot partition in TD
bigger than 1024MB can cause this. If your boot partition is bigger then
declare it as 1024 in TD. Only need to enter correct size when smaller than
1024MB.
Steve
 
Back
Top