• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Asus A7V133 with Windows 2000, Problems???

I DO~!!
wont install win2k... it says "inaccessable boot device" or somehting in a blue screen
that same thing happened when i tried to install win2k on abit-kt7raid
could raid not work on win2k? or something.. i dunno
 
Hi, I didn't have any problems installing Windows 2000 and it runs VERY fast and VERY stable. I installed it on my ATA66 HDD on the Promise controller, too. No RAID setup yet, though. The ONLY problem that I have with it is that my system locks up when I transfer files over my network. I've been told that I should take my NIC out of slot 4 and put it in slot 2. I've narrowed it down, and it doesn't seem to be a software/OS problem, but yet a hardware conflict or BIOS problem. I've contacted several people with this problem and it isn't just me who's having it. 🙁
 
"inaccessable boot device" Windows is probably looking for the PROMISE controller to access your hard drive. Were your 3rd party Win2K drivers off the installation cd loaded before Win2K was installed? You can also run off
the secondary controller to install Win2K and swap after you are done with the install.

I had a similar problem. When I hooked up to the PROMISE controller after
installing Windows and PROMISE drivers, it identified my hard Maxtor hard drive as a Maxtor SCSI device and the performance was terrible even with
MS hotfix. I then shut down, hooked it back up to the secondary controller, rebooted and VIOLA it was identified as a Maxtor 5202H2 and it let me run in dma mode. (Much Faster)

I have had this A7V133 running Win2K 12 hrs a day for about 3 weeks without
any problems after the install. This is the most stable motherboard I have
owned to date.

By the way I did not install the 4in1 drivers. I only installed the 4.05
AGP driver and the AMD Microsoft patch.
 
Most NIC problems are common IRQ sharing issues... turn off everything you dont need like onboard audio... serial ports etc... This isnt a A7V133 issue. When you have alot of things onboard like Promise you have to share IRQs.
 
I know but i have pretty much the same thing with my present MSI K7T Pro2.
My 3com NIC shares the same IRQ with my IDE controller and i've didn't experience any crash.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top