<
[email protected]> a écrit dans le message de
Kali,
I have an old DOS 6.2 (I think) boot floppy, which somehow
destroys the hard drive master boot record resulting in
same behavior as you describe. The only sure fire solution
is to start from scratch and reformat the offending boot
hard drive. You have to do fdisk with option to restore
the Master Boot Record . I think, not sure, it is
FDISK /MBR or FDISK space MBR.
Do FDISK ? to get help and to display the options.
Aurelien
would you please refrain from giving your solution to
anybody! It is the standard MS solution (run chkdsk),
which WILL not work on DEAD system! You need working
system to run DOS chkdsk. I wish someone in Redmond would
take this nonsense out of the Windows and publicly admit
that when things go south this bleeding edge technology
has to fall back on DOS to recover in too many cases!
Cheers Vaclav
The susgest
__________
Hi,
As I said before the stop 0x7b appears because of a a boot device
initialisation faillure.
That could be due to:
- corrupted scsi adapter or disk controler
- disk corruption
- system corruption
I am sure that to format the system and fix the master boot record will work
but this is not always the smartest solution, expecially on servers.
So before formating the system I propose to you the following tests:
- If you have installed a new device or a new adapter, try to remove it.
=> test if the computer boots correctly
- In the recovery console, you can also launch a chkdsk /r to check and
repair the disk integrity.
=> test if the computer boots correctly
- In recovery console launch a system reparation
=> test if the computer boots correctly
The better solution will be to analyse the memory.dmp generated to directly
point on the problem, but that could not be done on newsgroup.
Hope that it will help
Aurelien