XPE image lock up at Welcome screen at Target Unit

[Guest]

Hi

When I boot my Target unit with my XPE image, it locks up at the Welcome screen everytime. Anybody knows what's going on? Thanks.

 

[KM]

Vantry,

By "lock up" do you mean the image hangs?
Check you FBALog.txt and setupapi.log files for any errors.
Also, you can check you Event log offline (by default, your event log file
*.evt will be under %SystemRoot%\system32\config directory) for any service
or app errors.

--
KM,
BSquare Corporation

Hi,

When I boot my Target unit with my XPE image, it locks up at the Welcome

screen everytime. Anybody knows what's going on? Thanks.

 

[KM]

Vantry,

Does you target hardware match your dev machine hardware?
If not, you can't just copy the image (pre or post FBA). You will need to
run TAP on your target and make a new image with that platform support.

--
KM,
BSquare Corporation

Hi KM, Yes it hangs. The Image works fine on my development unit. I

built it, and boot it up on my second partition, and it worked great. When
I copy the image and install it into another machine, it just hangs at the
Welcome screen. I also tried to take the image before FBA and put on the
same machine, and all it did were rebooting after initializing FBA. Please
help. Thanks.

 

[Guest]

Hi KM, Thanks for fast respond. Yes, they are all the same. We're trying to deploy the XPE image to the same kind of hardware. Thanks.

 

[KM]

Vantry,

Something obviously is not the same between your two tests.

Although, it does not seem you have a problem with partitions, do you have
the same partition setup on your target as on your dev machine?
There was XPe Tips page where you could find Slobodan's comments on what you
should do to have C: as you boot drive in TD in both cases. Now the XPe Tips
page is gone, you may only search in this NG archive for more info (search
for "MountedDevices"). Here is the link, though:
http://groups.google.com/groups?q=MountedDevices+group:microsoft.public.wind
owsxp.embedded.*&hl=en&lr=&ie=UTF-8&group=microsoft.public.windowsxp.embedde
d.*&selm=eTvzBimnDHA.3288%40tk2msftngp13.phx.gbl&rnum=1

And again, you will probably need to get more info from the runtime image
(FBALog, setupapi, event log) to see what's going on there.
Another great thing for you would be to set up Kernel Debugger to see
remotely why you image hangs (I think, that would be the best way to figure
this out). E.g, I used this approach when my XP Pro machine hanged on
Welcome screen (appeared to be a conflict with a third party app).

--
KM,
BSquare Corporation

Hi KM, Thanks for fast respond. Yes, they are all the same. We're

trying to deploy the XPE image to the same kind of hardware. Thanks.