inaccessable_boot_device 0x7B

[Michael]

Windows 2000 SP4, 1500 AMD, 256MB RAM; BIOS settings -
IDE0 is first boot device, then CD-ROM.

Initially, this problem was a missing "vgaoem.fon" file
that caused boot failure. I removed the HD from the
system, attached it to a different system as a slave, and
replaced the fon file. I replaced the drive back into the
original system and booted to my current problem:

inaccessable_boot_device 0x0000007b

The Microsoft Knowledge Base has this issue listed under
Windows XP(http://support.microsoft.com/default.aspx?
scid=kb;en-us;303786), but I don't think it applies in
this case.

I should also mention that when I attempt to do a repair
using the Windows disk, the setup routine reports that it
cannot find a boot device.

Please help and thanks to all who try. :~)

Michael

 

[Pegasus \(MVP\)]

Windows 2000 SP4, 1500 AMD, 256MB RAM; BIOS settings -
IDE0 is first boot device, then CD-ROM.

Initially, this problem was a missing "vgaoem.fon" file
that caused boot failure. I removed the HD from the
system, attached it to a different system as a slave, and
replaced the fon file. I replaced the drive back into the
original system and booted to my current problem:

inaccessable_boot_device 0x0000007b

The Microsoft Knowledge Base has this issue listed under
Windows XP(http://support.microsoft.com/default.aspx?
scid=kb;en-us;303786), but I don't think it applies in
this case.

I should also mention that when I attempt to do a repair
using the Windows disk, the setup routine reports that it
cannot find a boot device.

Please help and thanks to all who try. :~)

Michael

As a starting point you should determine if your file system
is intact and if it looks complete. Boot the machine with
your Win2000 CD, select "Repair" when prompted, then
select "Command Console". Are your files and folders still
there? What is the contents of c:\boot.ini?

 

[Guest]

I've already tried the repair process using the CD in both
console and auto modes, but the setup routine cannot find
a Windows installation. This makes me thinks that the
setup routone cannot log onto the drive either.

The files system appears to be intact when I looked at it
through an unrelated system. I also scanned it for virus'
with a virus' database dated today.

I haven't read the boot.ini - very tired and I will try
again tomorrow.

Thanks for the help. :~)

 

[Pegasus \(MVP\)]

I've already tried the repair process using the CD in both
console and auto modes, but the setup routine cannot find
a Windows installation. This makes me thinks that the
setup routone cannot log onto the drive either.

The files system appears to be intact when I looked at it
through an unrelated system. I also scanned it for virus'
with a virus' database dated today.

I haven't read the boot.ini - very tired and I will try
again tomorrow.

Thanks for the help. :~)

It looks as if the registry or some file got changed while
your disk spent some time in the other machine. I would
now rename "system" to "system.bad", and "system.sav"
to "system", both while in the Command Console.

 

[Guest]

Did you set any jumper on your HD when you moved it to
another computer?

 

[Robert]

I've suffered this problem on workstation. Began after
updating Windows 2K Pro a motnh ago. Anti-virus (Symantec
Corporate)was up-to-date and checking daily, with no hint
of infection. First symptoms started with problem holding
dual-monitor display settings. Then workstation began
locking up on occassion and, when restarting, would give
the STOP error message. Workstation finally began shutting
down and rebooting when tasks such as running CHKDSK or
virus scan were manually begun. Now workstation will not
boot, even though getting power. Was leaning towards
blaming Windows upgrades but now not sure. One other
workstation in our building has shown message once but no
other symptoms.