RAM EWF and boot failure

  • Thread starter Thread starter Richard
  • Start date Start date
R

Richard

System Info
XPe SP1, 256 Megs Ram, Single Partition, RAM EWF Enabled, 105 meg image
total.

Yesterday, I went out to change a couple of application settings on one of
our XPe feild devices. It was running fine before I messed with it. It was
a simple change which has absolutely nothing to do with the OS. I
committed, then restarted. The system would not come up and was not
available on the network or remote desktop. So I hooked a keyboard and
monitor up and it was stuck at the XP boot logo screen. I pressed <enter>
for grins and it rebooted and came up and did the same thing again. This
continued several times so I changed out the CF which had a fresh image and
everything was fine.

Now, what in the world could have caused this and how do I go about finding
out what happened. I have the CF but I'm sure since it was RAM EWF nothing
will be written on it. It sure seems as some system files got scrambed when
I did a commit and rebooted.

Any Clues?

Richard
 
Richard,

same thing here: running XPe with RAM EWF, commit to CF, reboot -> no
boot, image scrambled.

It turned out that it was my CF that died. Try to check your CF, (in my case
we were unfortunatlely running FBA on the CF which is a bad idea).

Regards,
Mathias.
 
It appears to be fine, I can read all the files on it. Pretty new and
hasn't had FBA ran on it. Anything else to check? Maybe run some file
compares on it?
 
Richard,

I could not quite understand what errors/message you saw on (or instead of) the XPe Boot logo screen.
But you have options to debug it a little bit:
- hook up a KD to see what's going on behind the scene
- add /SOS switch to boot.ini to see what driver you get stuck on

Never assume that changes you do in image are unrelated to issues you may have with it. Whenever you change binaries and/or registry
entries it may possible affect other components. It all comes to testing.
 
Back
Top