T
Tony
Hi all,
I have a simple test system here that is producing some interesting results.
This system has an XPe OS running on a CF card. I created a batch file that
is run on startup that does "shutdown -r -t 0". The system just cycles
reboots and I've been watching what its failure behaviour is.
When the system has its EWF turned on, it seems to reboot continuously
without any problems. However, when I turn the EWF off, the system will
eventually come up and indicate that "cmd.exe is corrupt". Manually trying
to launch cmd.exe confirms Windows thinks it is corrupt. However, if I just
cycle the power on the system, then everything runs again for a while until
the same error comes up.
Given that turning the EWF on remedies the problem makes me think that
somehow the system is restarting before data is safely written to the disk
(whatever that data may be). I still find it curious though, since I
thought using the shutdown command would commence a "graceful" shutdown, and
I wasn't expecting to see any problems.
Why would just cycling the power fix the corrupt file? Are there
buffer/cache settings I should be looking at in Windows? Any BIOS settings
that may be causing problems?
Anyone have any thoughts or insights?
Regards,
Tony
I have a simple test system here that is producing some interesting results.
This system has an XPe OS running on a CF card. I created a batch file that
is run on startup that does "shutdown -r -t 0". The system just cycles
reboots and I've been watching what its failure behaviour is.
When the system has its EWF turned on, it seems to reboot continuously
without any problems. However, when I turn the EWF off, the system will
eventually come up and indicate that "cmd.exe is corrupt". Manually trying
to launch cmd.exe confirms Windows thinks it is corrupt. However, if I just
cycle the power on the system, then everything runs again for a while until
the same error comes up.
Given that turning the EWF on remedies the problem makes me think that
somehow the system is restarting before data is safely written to the disk
(whatever that data may be). I still find it curious though, since I
thought using the shutdown command would commence a "graceful" shutdown, and
I wasn't expecting to see any problems.
Why would just cycling the power fix the corrupt file? Are there
buffer/cache settings I should be looking at in Windows? Any BIOS settings
that may be causing problems?
Anyone have any thoughts or insights?
Regards,
Tony