Removable CF and XPe License error 0x80090006

[Guest]

Hi,

is it possible to run XPe on removeable CF-Card ?
I have tested the SanDisk Ultra II and Lexar. Booth marked as removable.
XPe boot fine but ... after logon i receive following error message:
"A problem is preventing from accurately checking the license for this
computer. Error Code 0x80090006"
The solution form Microsoft
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnxpesp1/html/winxpfaq.asp
is not a solution for my problem.
The boot partition size is the same as defined in the targed designer !

Have anybody working XPe on removable CD-Card ?
Can XPe run ONLY on a fixed CD-Cards ?

???

Thanks

 

[The Rob]

Hi XPeee,

There are no problems using XPe on removable CF´s (as long as you´re not
using EWF).

How is your target system set up? Do you have additional drives connected?
Do you use the "System Cloning Tool"? SP1 or SP2?
What´s the size of your CF and what are the settings in TD?

/Rob

 

[Guest]

Hi The Rob,

Our system use CF-Card with EWF in RAM mode. The CF-Card is physically 256MB,
1 partition 244MB formated with Fat32, 2KB cluster. TD is set to 244MB. The
Image was created with SP1 and the "System Clonig Tool" is used.

I have tested this image with another CF-Card - physically 512MB, 1
partition 486MB formated with Fat32, 4KB cluster. This CF-Card is marked as
"non-removable" and all work fine.

Is it a problem with EWF on removable CF ?

 

[The Rob]

XPeee,

First of all, I´m not an expert at XPe (although I hope to be one day ;-) ,
but since the "gurus" seem to be on vacation I´ll try to help anyway.

Hi The Rob,

Our system use CF-Card with EWF in RAM mode. The CF-Card is physically
256MB,
1 partition 244MB formated with Fat32, 2KB cluster. TD is set to 244MB.
The
Image was created with SP1 and the "System Clonig Tool" is used.

It seems to me that the cluster sizes are different here, or did you change
the cluster size settings in TD as well ( 2kB resp. 4kB )?

I have tested this image with another CF-Card - physically 512MB, 1
partition 486MB formated with Fat32, 4KB cluster. This CF-Card is marked
as
"non-removable" and all work fine.

Is it a problem with EWF on removable CF ?

There are some considerations in this scenario. You should use EWF RAM Reg
Mode for removable disks or use an additional unpartioned drive when setting
up your system. You can read some here:
http://msdn.microsoft.com/library/d...ry/en-us/xpehelp/html/xegrfewframoverlays.asp

I read somewhere about some problems with EWF RAM and SP1. Did you install
all the necessary QFE´s?
Does this happen before or after you call fbreseal.exe (I mean is this your
"golden image" or a clone)?

I assume that you entered the correct PID since it works on the other CF.

BR,
Rob

 

[Guest]

Hi The Rob,

thank you for your reply.

I use always the same image and test it with several CF-Cards. The settings
in the Target Designer are: Boot Partition Size 244MB, Cluster Size = 512B,
EWF in RAM mode, SP1 and many QFE`s but not all.

I use this image on CF-Cards with 244MB + Fat32 + 2KB cluster and on 486MB
Fat32, 4KB cluster. Booth marked as non-removable and all work perfectly.

Is the cluster size important for license check ?

Which QFE`s are important for this problem ?
I have installed many QFE's, but not all. Is it possible to extract info
list abot installed QEF`s from XPe database/target designer ?

This problem occur in the clone. I use only clons from master image.
Solve SP2 this problem ?

BR,
XPeee

 

[The Rob]

Hi XPeee,

Hi The Rob,

thank you for your reply.

I use always the same image and test it with several CF-Cards. The
settings
in the Target Designer are: Boot Partition Size 244MB, Cluster Size =
512B,
EWF in RAM mode, SP1 and many QFE`s but not all.

I use this image on CF-Cards with 244MB + Fat32 + 2KB cluster and on 486MB
Fat32, 4KB cluster. Booth marked as non-removable and all work perfectly.

Is the cluster size important for license check ?

No, the cluster size is only for TD to estimate the footprint of the image
(sorry for asking in the first place, I just learned ;-) )

Which QFE`s are important for this problem ?
I have installed many QFE's, but not all. Is it possible to extract info
list abot installed QEF`s from XPe database/target designer ?

You can list the QFE´s in Database Manager and also see what they contain.
Check under 'Package', highlight them and click 'Properties'.
I´m not sure anymore if this problem was fixed with SP1 or later in SP2. I
never built any EWF images with SP1...

This problem occur in the clone. I use only clons from master image.

Hmmm... If boot partition size is correct and the master works fine then I
wonder:

How did you make your master image? On an identical CF (as this 244MB card)
or on a different drive/CF? What does your master drive look like?
Does the reseal phase occur during FBA or did you call fbreseal after some
tweaking on the master? Fbreseal can make some problems, but I never had
this one, just problems with that a few (3 of 15) clones didn´t have the
user profiles....(?)
How do you deploy the clones (are you for example using Norton Ghost)?

Solve SP2 this problem ?

Don´t know. I as using EWF RAM and cloning with SP2, however I didn´t reseal
and clone it yet (still tweaking it a little), so I guess I´ll have to wait
and see

BR,
Rob

 

[Coderer]

My experience shows that RAM mode is a real pain, and unless you plan
to be using the commit functionality (it sounds like you're not), you
probably want Reg-RAM mode. You can do this the easy way by installing
SP2, or you can do it the hard way by changing your registry in SP1.
Search around a bit for the Reg-RAM SP1 component. Alternately, you
can make the change yourself.


A brief summary:

The pertinent entries are under

HKLM\SYSTEM\CurrentControlSet\Services\EWF\Parameters\Protected\Volume0

and you want to have a VolumeID, ArcName, Enabled, and Type. The first
two are REG_SZ and the last two are REG_DWORD. These basically store
the same settings you would make under the EWF component in TD. You
also need to disable FBA DLL/COM registration for the EWF component,
again in TD. After the registry entries are made, boot through the
FBA, shut down, and mount the embedded system's registry on a WinXP
desktop system. Change the "Enabled" reg entry from 0 to 1 and you're
in business.


The above is just the whirlwind tour. You'd be well advised to find a
more thorough writeup, though if you're still early in your development
process, you're probably better off getting SP2 and being done with it.
We can't because we've already documented a bunch of stuff using SP1,
but if you're not thusly encumbered... well, enough said.