On Sat, 19 Aug 2006 07:22:07 +1000, "Rod Speed"
<rod.speed.aaa@gmail.com> wrote:

>Echy <echy2007@yahoo.com.au> wrote:
>
>> I have encountered an "Inaccessible Boot Device" stop error
>> 0x0000007B on my desktop computer. The computer (in normal
>> & safe mode) will not progress past the blue stop screen.
>
>> It is an Acer PIII computer with Windows 2000 and was
>> running fine with no warning signs of this impending problem.

Examine the motherboard for popped capacitors. A very
instable system can exhibit seemingly unrelated problems.

Also check the drive cables.

>
>> I have current data back ups thankfully.I run up-to-date anti virus
>> software and Ad-Aware, Spybot, CCleaner, SpywareBlaster.

Is the drive NTFS or FAT32?
You might try pulling up a directory to see if the drive
contents are shown. Might also run the HDD manufacturer's
diagnostics on it.

How'd you run those other windows softwares if the system
isn't booting to windows?


>
>> I have not installed anything new in the way of hardware or software.
>> I have checked that all cables are tightly connected & have used a
>> boot floppy disk to run chkdsk & scandisk. When I run scandisk it
>> says all is OK but it cannot be checking anything I don't think as it
>> finishes in two seconds. Same for Chkdsk.

You might start up a repair install and see whether it shows
an existing installation... and maybe even let it try to
repair it.


>
>> I also managed to borrow a working hard disk with an operating
>> system etc on it, disconnected my drive and connected this one.
>> I get exactly the same error message ??


Since you have a second drive, you might try temporarily
installing Win2k to it, booting it then. Or, boot from the
windows CD or a bootable floppy and see what the system can
see sitting at DOS prompt or whatever interface you're left
at after booting a CD.


>
>That suggests something has died with the hard drive controller.

Nope, with the second drive it could suggest what we already
knew, you can't migrate an existing WinNT/2k/xp installation
to another dissimilar system (different OS drive controller
in this case).

It could be a bad cable or drive controller, but those are
less typical than what I wrote above.


>
>> Wondering if there a definitive help source or
>> if anyone can offer any thoughts on the problem.
>
>
>http://www.microsoft.com/technet/pro...s/pgsappb.mspx
>