andyw

hehe, thanks, but the partition is marked as "active"... i can boot from this partition on the normal controller, but not at the udma66-controller.... in the meantime i learned why: when resizing the partition in 1gb-steps from 20gb downto 15gb, i was surprised that i could boot when the boot-partition size was smaller than 16gb!!! as this just something within the bios of the controller, i wrote an email to highpoint-tech to fix this in the next bios-update.... thanx to all, hope i could help others...

I have two drives from IBM, one with 15GB and one with 20GB. On both are W2k clean-installs (using the standard onboard ide-controller), but only the 15GB drive can boot on the UDMA66-controller (Abit BE6 Rev.2, HPT366-onboard-controller)... When connecting the 20GB drive to the HPT366 as master drive the htp366 setup tells me there is no bootable device connected, but on the normal ide-controller it works (like now, btw)! Any solution? Second problem: Both drives (15GB=master, 20GB=slave) work on udma4 w/o problems, but when using a drive from Maxtor instead the slave from IBM w2k hangs itself up upon rebooting. Yes, I have all the latest stuff installed (BIOS'es, drivers, ...) Doesnt the HPT366 like Maxtor drives or just not different manufacturers? AndyW

I installed w2k on udma33-controller on my 15gb ibm drive and it works with w2k on udma66... but now this: PROBLEM: I have the latest BIOS version and w2k drivers installed, but when using my IBM harddisk and my Maxtor disk together on the hpt366-controller (both udma mode 4) w2k hangs itself up upon starting... SOLUTION (?): When using another harddrive from IBM instead of the one from Maxtor it worked!!! Is the controller not capable of handling drives from different manufacturers or is there anything against Maxtor?