"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.