~~~~Free pr0n!~~~~

mHubs

Senior member
Oct 28, 2000
447
0
76
I lied!
Now to my problem
I just installed a KT7-RAID & Duron from a BM6 & Celery..
I remove all the stuff from device manager, install new mobo & proc, boot up, no go
Win98 works gr8..
In 2k I get the "inaccessable boot device" or whatever that error is,
So I went to the KT7 FAQ (unofficial) and it says to remove the IDE drivers...
Did that, win2k STILL gives that error...
What else do i gotta do?
I'm NOT goin to reinstall win2k, I've got a lot of stuff and am not goin to reinstall it all..
 

Marqui

Member
Aug 15, 2000
190
0
0
You are going to have to be a little more specific about how you came to that error. Was your system working and all of a sudden it happens, or did you build a new system and use the same drive, or were you dual booting previously and now made some changes. The error is not good. So I need some more info.

Also what does not make since is that your got an inaccessible boot device from Windows 2k. You must mean you got the message when you booted your system. That is a system message.


 

mHubs

Senior member
Oct 28, 2000
447
0
76
I had a BM6 and a celery, and upgraded mobo & proc (to KT7-RAID & Duron 800)
But the whole "I've got a lot of stuff..." should have shown that its an upgrade...
 

mHubs

Senior member
Oct 28, 2000
447
0
76
Well you see...
It IS a win2k error, cuz its already to starting up win2k and gives me a blue screen with some shi.t about a STOP error...blah blah blah.. inaccessible boot device or something like that
 

Marqui

Member
Aug 15, 2000
190
0
0
I don't see much else you can do... Im assumming you did not make any recovery disks....

You see, you basically really should not pull a hard drive from one system and stick it into another. For one, you went from a Intel based system to and AMD based system. All your settings are changed, including device addresses. Whenever you plan on doing something like this, you should always be ready to format and reinstall. I've seen it work sometimes, but 90 percent of the time it does not work properly. You system is looking for old settings and is barfing when not finding them.

Only thing else besides reformatting, is if you have your win2k cd handy, boot from the cd and have instead of installing, it should find your current partition, and then try the "REPAIR" utility. It will give you the choice of Installing or repairing on a particular partition.

If its a matter of just not wanting to spend 3 hours reconfiging and installing your system, then I would go thru with it. If its a matter of you not having all the programs on cd that u use then you may want to hook it back up to the old system and do some backing up toanother drive or cdr.
 

mHubs

Senior member
Oct 28, 2000
447
0
76
Dude, I was just about to go try the REPAIR thing and happened to check this out..
I knew that I might have probs goin between the 2 systems, but I removed the stuff from Device Manager so I thought that should have solved the prob..
O well, I guess I was wrong
 

mHubs

Senior member
Oct 28, 2000
447
0
76
Tried repair... didnt fix shi.t
GRRR WTF?! Win98 works fine(boots) with no changes.. Win2k is just fux0red
And I was convinced Win2k was the ultimate OS...
 

mHubs

Senior member
Oct 28, 2000
447
0
76
*bump*
I want this goddammed problem fixed, cuz reinstalling win2k is NOT an option until it has been proven that NOTHIN else will work
 

Dark

Senior member
Oct 24, 1999
639
0
0
Put your hdd on the ide device instead of the RAID. Win2k is trying to boot from the IDE. I had this problem with the A7v and the promise ATA 100.

 

rbV5

Lifer
Dec 10, 2000
12,632
0
0
Format and clean install, Win2k is not magic...you'll spend 10x more time trying to "fix" it, and you will likely have random/unexplained problems that will keep cropping up. In the time from your first post you could already be done! Win2k is a good stable OS by the way.

Good Luck:)

 

Moonbender

Golden Member
Oct 19, 2000
1,046
0
0
Win 2000 is very picky when it comes to radical changes to the hardware, and it won't get any more radical than your upgrade. From what I've read on these forums (try searching), it's related to Windows creating a HAL, Hardware Abstraction Layer, which is once created during install. There ought to be a way to rebuilt the HAL, but I'm not sure how anymore.
Reinstalling is definitively the best idea - if you don't want to, well it's not my system that isn't working.