What is going on with fbreseal?

[Guest]

I'm encountering some odd behavior post fbreseal (no ewf on the unit). I've
got my image set to not reseal after FBA, so that I can make some additional
changes to the system. I have set cmiRemoveAutoLogon through cmiNoHelpFiles
all to false, with GenerateComputerName to 1. I run fbreseal with the
options -autologon -keepdomain -keepnet -keepuser –keepmounted. It completes
and pops up a messagebox telling me that it has completed and will restart
(whatever that message is). I let it reboot, and while the machine has yet
to complete the POST I turn off the machine. I make an image of the drive
using Ghost. Up until this point the process is well described and
everything makes sense. Beyond here there are no descriptions of the exact
behavior that should be expected, and what things may be indicators that
something is wrong. Past this point, I have experienced very odd things that
I cannot find any cause for. When I boot for the first time after fbreseal,
I get the standard progress bar at the bottom of the screen. Fine. I then
get a blue screen with a cursor. Okay. But that's all I get. It sits
there, doing nothing. After awhile I reboot, and everything appears to be
fine. Is this normal? What EXACTLY should occur during the first
boot after fbreseal?
Other odd things that have been happening after fbreseal, such as
explorer.exe being deleted and the touchscreen alignment going wonky (y-axis
reversed). All this weird behavior is driving me nuts! A detailed
description of xpe's post-fbreseal behavior would be greatly appreciated!

 

[KM]

William,

Some problems of fbreseal on SP2 have been reported in thig NG. You may want to search NG archive to find them.

...
something is wrong. Past this point, I have experienced very odd things that
I cannot find any cause for. When I boot for the first time after fbreseal,
I get the standard progress bar at the bottom of the screen. Fine. I then
get a blue screen with a cursor.

Does it say anythign there? It should state that FBA is preparing the system (.....).
If it doesn't, please add SOS and BOOTLOG switches to your boot.ini to see where (if) it hangs.

Also, connecting to the device with KD (kernel debugger) may help you to see where it hangs.

Okay. But that's all I get. It sits
there, doing nothing. After awhile I reboot, and everything appears to be
fine. Is this normal? What EXACTLY should occur during the first
boot after fbreseal?
Other odd things that have been happening after fbreseal, such as
explorer.exe being deleted

Wow.. This must be the strangest behaviour of fbreseal I ver heard. Must be a bug.
Please feel free to repot the bug to MS: http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx

and the touchscreen alignment going wonky (y-axis
reversed). All this weird behavior is driving me nuts! A detailed
description of xpe's post-fbreseal behavior would be greatly appreciated!

Well.. Supposedly, after he XP Logo booting screen you should see the FBA "blue" screen saying that it is preparing system for first
boot. That's it. Then the system continues to boot as normal.
Or, at least, that is how things worked on SP1.

If it doesn't work for you the same way, you want to report the bug to MS using the link provided above.

 

[SmprFidels]

William,
It is nice to know that i am not the only one who decided it was easier
to install stuff before the re-seal than to componitize everything.

I perform some of the same steps that you described and do not see the
lockups or need to power off my machine on the first reboot after
re-seal.
My run-time image is set to not reseal so that i can install custom
software and some hardware drivers before sealing it to make ghost
images of it. for me that is easier than trying to componitize
everything.

I had some cases where impatient technicians would power off the
machines durring the first reboot after re-seal and it caused me no end
of problems with drivers and eratic behavior. Maybe that has something
to do with your touch screen and explorer problems. It helped when i
removed the NOGUIBOOT switch from the startup sequence so that they
could see that it was doing something

Good luck
Sincerely,
Matt