Win2K SP4

Gary Chanson wrote:
> "Jamie Furlong" wrote in message
>
>> I have a Maxtor drive on a reasonably recent (2 years old) motherboard, and
>> for the third time running, I'm now getting the error message: (the figures
>> are from a picture I took, so one or two might be wrong)
>>
>> ***STOP: 0x0000007B (0x053E29F0,0xC0000034,0xC0000032,0x00000000)
>> INACCESSIBLE_BOOT_DEVICE
>>
>> The strange thing is, I can't even re-install Windows 2000 over itself as
>> it says there's no valid install, but I can see it right there!
>>
>> I've run various checkers across the drive, like Maxblast, Spinrite etc,
>> and they and the SMART reporter report no faults. Could it be a fault with
>> the motherboard? That's the only thing I can think of - it fails with this
>> exact error so regularly. Is a newer OS more tolerant? Or how can I make
>> this disk more tolerant?
>
> Check to make sure that the drive is correctly set as the boot device.
>
> You might be able to run the repair console and execute FIXMBR and
> FIXBOOT. If the OS is intact, this might work. If not, the OS may be
> damaged beyond repair.


Yeah, there's the thing - I couldn't find enough floppies when I last
installed, so guess who doesn't have a repair console?!
 >> Stay informed about: Win2K SP4 

For next time;
http://support.microsoft.com/?kbid=216417

"Jamie Furlong" wrote in message

> Gary Chanson wrote:
>> "Jamie Furlong" wrote in message
>>
>>> I have a Maxtor drive on a reasonably recent (2 years old) motherboard,
>>> and for the third time running, I'm now getting the error message: (the
>>> figures are from a picture I took, so one or two might be wrong)
>>>
>>> ***STOP: 0x0000007B (0x053E29F0,0xC0000034,0xC0000032,0x00000000)
>>> INACCESSIBLE_BOOT_DEVICE
>>>
>>> The strange thing is, I can't even re-install Windows 2000 over itself
>>> as it says there's no valid install, but I can see it right there!
>>>
>>> I've run various checkers across the drive, like Maxblast, Spinrite etc,
>>> and they and the SMART reporter report no faults. Could it be a fault
>>> with the motherboard? That's the only thing I can think of - it fails
>>> with this exact error so regularly. Is a newer OS more tolerant? Or how
>>> can I make this disk more tolerant?
>>
>> Check to make sure that the drive is correctly set as the boot
>> device.
>>
>> You might be able to run the repair console and execute FIXMBR and
>> FIXBOOT. If the OS is intact, this might work. If not, the OS may be
>> damaged beyond repair.
>
>
> Yeah, there's the thing - I couldn't find enough floppies when I last
> installed, so guess who doesn't have a repair console?!
 >> Stay informed about: Win2K SP4 

Those commands don't require an ERD, just the install CD-Rom.

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Jamie Furlong" wrote:
> Yeah, there's the thing - I couldn't find enough floppies when I last
> installed, so guess who doesn't have a repair console?!
 >> Stay informed about: Win2K SP4 

"Jamie Furlong" wrote in message

> I have a Maxtor drive on a reasonably recent (2 years old) motherboard,
> and for the third time running, I'm now getting the error message: (the
> figures are from a picture I took, so one or two might be wrong)
>
> ***STOP: 0x0000007B (0x053E29F0,0xC0000034,0xC0000032,0x00000000)
> INACCESSIBLE_BOOT_DEVICE
>
> The strange thing is, I can't even re-install Windows 2000 over itself
> as it says there's no valid install, but I can see it right there!
>
> I've run various checkers across the drive, like Maxblast, Spinrite etc,
> and they and the SMART reporter report no faults. Could it be a fault
> with the motherboard? That's the only thing I can think of - it fails
> with this exact error so regularly. Is a newer OS more tolerant? Or how
> can I make this disk more tolerant?

Is the Maxtor replacing a main drive or is it being used as a secondary
drive? Are the jumpers set correctly?

later......

PS since the original post I would think you have come across a solution
if so please post
 >> Stay informed about: Win2K SP4