System Licence Violation

  • Thread starter Thread starter Black Shuck
  • Start date Start date
B

Black Shuck

Hi I am getting these, after FBA.

I have read the google archives, and checked the obvious:

1/ I am not using any PID at the moment, and the build log shows it's a
eval build
2/ I am using a parition over 5GB in size, and the size is set to 5000
3/ cluster size is default 4096 bytes.

Is there anything else that can cause this error? I am building on XP x64
edition, not sure if that matters (and booting the image using x64
ntloader). Also I updated my registered XPe to SP2 using the SP2 database
update from a eval disc set (assumed they are the same...).

I am hazzarding a bet that the last thing was my mistake, and am currently
downloading the proper SP2 update from the OEM site, but in the meantime
(the size is REALLY slow), is there anything else than people can think of
that causes 09A Security Violation STOP errors?

Thanks.
 
Try changing the boot partition back to 1024 instead of 5000.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.



Hi I am getting these, after FBA.

I have read the google archives, and checked the obvious:

1/ I am not using any PID at the moment, and the build log shows it's a
eval build
2/ I am using a parition over 5GB in size, and the size is set to 5000
3/ cluster size is default 4096 bytes.

Is there anything else that can cause this error? I am building on XP x64
edition, not sure if that matters (and booting the image using x64
ntloader). Also I updated my registered XPe to SP2 using the SP2 database
update from a eval disc set (assumed they are the same...).

I am hazzarding a bet that the last thing was my mistake, and am currently
downloading the proper SP2 update from the OEM site, but in the meantime
(the size is REALLY slow), is there anything else than people can think of
that causes 09A Security Violation STOP errors?

Thanks.
 
Try changing the boot partition back to 1024 instead of 5000.
Click to expand...

I only set it to 5000, as that's what the help says. Are you suggesting
the XPe help file is bad?

Rebuilding now, with the downloaded SP2, and it set back to 1024Mb, will
report back...
 
I only set it to 5000, as that's what the help says. Are you suggesting
the XPe help file is bad?

Rebuilding now, with the downloaded SP2, and it set back to 1024Mb, will
report back...
Click to expand...


Still got the same problem... Any other ideas? I removed the eval sp2
package and repositiory, and downloaded the oem version, updated the DB,
so that's not the issue, and as mentioned, no PID is entered, so am
running eval.

Will try a PID tomorrrow, see if it helps, unless someone has some better
ideas what can cause a STOP 9A, other than what I have checked so far...
 
I ran into a situation where setting to 5000 would work. Keeping the default
seem to work fine.

-Sean


Try changing the boot partition back to 1024 instead of 5000.
Click to expand...

I only set it to 5000, as that's what the help says. Are you suggesting
the XPe help file is bad?

Rebuilding now, with the downloaded SP2, and it set back to 1024Mb, will
report back...
 
Still got the same problem... Any other ideas? I removed the eval sp2
package and repositiory, and downloaded the oem version, updated the DB,
so that's not the issue, and as mentioned, no PID is entered, so am
running eval.

Will try a PID tomorrrow, see if it helps, unless someone has some
better ideas what can cause a STOP 9A, other than what I have checked so
far...
Click to expand...

In the end, it was EWF causing the problems, removed EWF, and is if by
magic, no licence vioations. The mystery continues. Will add EWF back in
later, once I have more time to sort these problems out. I did not FBA
process completed VERY quickly compared to when EWF was not there..
 
EWF caused this error! Something isn't right.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.



Still got the same problem... Any other ideas? I removed the eval sp2
package and repositiory, and downloaded the oem version, updated the DB,
so that's not the issue, and as mentioned, no PID is entered, so am
running eval.

Will try a PID tomorrrow, see if it helps, unless someone has some better
ideas what can cause a STOP 9A, other than what I have checked so far...
Click to expand...

In the end, it was EWF causing the problems, removed EWF, and is if by
magic, no licence vioations. The mystery continues. Will add EWF back in
later, once I have more time to sort these problems out. I did not FBA
process completed VERY quickly compared to when EWF was not there..
 
EWF caused this error! Something isn't right.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.
Click to expand...

I have a suspicion, as EWF needs a modified boot loader, and I am using XP
x64, with it's 64bit non EWF bootloader, it may be having a clash...
Ideally I need a x64 EWF compatible bootloader, but I doubt one of these
exists within the dark halls of redmond...
 
Okay. Now I understand.

-Sean



EWF caused this error! Something isn't right.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.
Click to expand...

I have a suspicion, as EWF needs a modified boot loader, and I am using XP
x64, with it's 64bit non EWF bootloader, it may be having a clash...
Ideally I need a x64 EWF compatible bootloader, but I doubt one of these
exists within the dark halls of redmond...
 
Back
Top