INACCESSIBLE_BOOT_ERROR (0x0000007B) W2K

[nitrousninja]

I just installed SP1 for W2K and after reboot that is what I got. Nothing new has been installed at all and my system is non-SCSI and running FAT32 for W2K and W98SE. All I got off the internet was SP1, I didn't go anywhere else or open mail so I doubt it is a virus. I have my HDD on IDE1 alone with my DVD and burner on the 2nd IDE. Has anyone else had this problem? Everything was running fine until I installed SP1. What do I have to change to get it to work? I looked for my HDD(WD 20.7GB) at NTcompatible.com and it wasn't listed at all. I bought it about eight months ago and haven't had any problems with it in W2K for the two weeks W2K has been installed. Hopefully I can get the Chkdsk/f to work in safe mode but if not what else can I do? Thanks in advance! Matt

 

[Iron Woode]

I have received this error once in a while. Not sure what causes it, but it usually goes away by forcing the OS to re-detect the hdd. For me, i just unplug the eide connector, turn on the pc. Then shut it down and reconnect the eide connector and it detects the drive and boots up normally.

 

[nitrousninja]

Thanks,I'll give that a try.

 

[yos]

I had this problem 10 times on my Harddrive... I have no idea what the problem is. If you find out, please PM me!!!

Thanks...

 

[nitrousninja]

I tried remonving the cables and booting up the powering down and that didn't work. I also tried changing HDD detect from auto to manual and that also did not work. I can't evn get into safe mode. After I hit F8 and pick any of the options I get the eror. This is all after downloading and installing SP1. Nothing else has been added or changed since I did the origional install of W2K. Any other ideas? Is ther a setting in BIOS that W2K might not like?

 

[cheapbastich]

had the exact same thing happen! did a complete reinstall (could not get it
to work), and have not
applied the service pack- anyone know what causes this? Ive been blaming my
maxtor hard drive and ata100 card, cause they dont boot in w98 either......

 

[yos]

You have a maxtor??? I do too and I heard it was a problem...
Check out my posts about this problem...

One
Two

and check out the posts linked in there...

- the yos

 

[DickBurns]

I had this problem too when I installed win2k. I had my hdd on the promise controller of my a7v. When I put it on the regular ide channel it worked fine and then I installed the drivers for the promise controller and it has worked perfect ever since. hope this helps

 

[yos]

I still don't have my promise controller on! I took it off and still have the problem...
Any ideas?

I also updated my BIOS (CMOS not promise), and ran fdisk /mbr A FEW TIMES.

I am so puzzled.... so puzzled...

 

[LordEdmond]

one point have you tried MS knowlege base search on the error??

I also had this in the dim past with NT4 turned out to be drivers for the ssci card not installed correctly.

the system seems to be unable to load the disk access drivers


but maybe not that is the question

 

[yos]

This is what I got from MS...
Knowledge Base

I don't know... my partitions are set up as 6,10,13.9....
I am well under the 7.88 but I will have to see.... maybe Maxtor has this on some of their hardrives...

Grrrrrrrr....

-the Yos

 

[Mal007colm]

I had a Maxtor 15.2 gig that had this same problem the only soluion I could get was to re-install the Os and it worked fine after that. No problems since then.

 

[yos]

Mal007colm,

Did you install the service pack after you re-installed?

 

[yos]

I changed the jumper on my hard drive to the normal "Master" position instead of what is was set for (the Cylinder Limitation Option), like microsoft said and with help from the installation book from Maxtor for my Diamond Max plus (30gb). After that, my hard drive wouldn't boot. It hung after the post.

Then I read in the maxtor book that if this happens, the hard drive must be set to the Cylinder Limitation Option. So it's a Catch 22. To get SP1, I need the Cylinder Limitation option jumper off; to boot, I need it on.

Anyone have a work around for this????

 

[yos]

bump

 

[cheapbastich]

bump

 

[forouza1]

O.k. I had the exact same problem. Got the Maxtor Diamond Max 60GB HD (See Rig). I had it occur a little differently. I had installed the Service Pack 1 and rebooted just fine. However when I went to add the Via Ultra DMA Bus Mastering Driver I got the error. I fixed this by using the F8 option on bootup and chose the option to reset to a configuration that worked previously (Must be kinda like system restore). Have tried that? Anyways I haven't tried to reinstall the driver again but I may try and see if it happens again.

 

[Blayze]

forouza1

I had the same problem on my K7V Athlon 800 system I tryed what you said and it still did not work

I guess I will have to reinstall

oh well no more VIA Busmaster drivers for me

I have also tryed all of the above in the thread with no luck.



Is it just me or are these VIA boards a little picky about drivers?

 

[cheapbastich]

anyone try the sp2 that is floating around?

 

[yos]

Just an update...

I reformatted last night and changed the Cylinder Limitation Jumper... and SP1 worked!! FINALLY After 10 tries!!

-Thanks...

-the Yos

 

[cheapbastich]

ok, after not buying a new motherboard this weekend, I'll try everything mentioned in
this thread next week, after finals, fingers crossed.........

 

[Abzstrak]

There is a bug in via busmastering drivers... just get into safe mode (if you can) and get rid of them, other wise manually replace the files with MS's. Then it'll work.

wihtout the newest busmastering from via, the only limitation is the lack of ata100 support (runs like 66)

L8R