Windows 2000 & System Commander ?

[Tuzinor]

Just installed Windows 2000 Professional.Works fine when I boot directly to it's hard drive- when booting normally with System Commander and selecting 2000 I get a symbol,the letter h & a flashing line that's it.Have the following setup:
Asus A7V Motherboard with both a built in Promise ATA 100-(has it's own bios)and a built in ATA 66 Controller,AMD 900MHZ Thunderbird Processor & 512mb PC133 ram & three ATA 100 hard drives.Normally boot from the ATA 100 controller where my first two hard drives are.(Both on Primary controller).
First hard drive:First partition: Windows 98SE-(where System Commander is installed),second partition-Linux.
Second hard drive:Windows partitions.
Third hard drive-on ATA 66 (on Primary Comtroller)-first partition:Windows 2000,second-Windows files,third-BeOS.
To install Windows 2000 I unhooked the first two drives- Fdisked the first partition of the third hard drive-made it active-via F6 added the Promise drivers for Mass storage controllers,formatted the drive NTFS with the 2000 disc and installed 2000 Professional.Works fine when changing the boot sequence to the ATA 66 hard drive.Hooked other dives back up- Windows 2000 sees the other drives fine.
Changed back to normal boot-ie-the ATA 100 controller- booted into Windows 98SE-re enabled System Commander-rebooted-System Commander shows the 2000 partition as a valid boot partition-tried booting 2000-just get a symbol,the letter h and a flashing cursor.I went thru a lot of posts and tech support to get Linux to work before I tackled installing 2000-so I guess I shouldn't be surprised at running into another roadblock.
Before anyone tells me to use Lilo to boot- I want to make this clear- I don't want to in ANYWAY screw up my Windows 98SE -this is my main OP System.That is why I bought Partition Commander with System Commander so the only changes made to the 98 boot record would be made by System Commander and can be activated ot deactivated at anytime.If anyone wants to know why I have installed these different Operating systems it's because I want to learn them in the hopes that someday I might become certified-time for a career change!
Windows 98SE & BeOS have booted fine with System Commander from day one- Linux was a challenge- not a surprise there-now I need to get the problem with 2000 figured out-any ideas out there? I did go thru this with Microsoft Support before I started installing 2000- followed his instructions to unhook the first two drives and install 2000 to the ATA 66 drive and then rehook up the first two drives.I did get all the latest drivers for my hardware for 2000.
Any help will be greatly appreciated- thank's- Dave

[Tuzinor]

NOW I'M PISSED! This was my second try at installing Windows 2000 & then trying to boot with System Commander.The first time I got a symbol,the letter u and a flashing cursor.Being my first time with Windows 2000- I figured it was me because I had a couple of Windows file protection messages when installing a couple of programs.I couldn't even boot into it when I changed the Boot sequence to that hard drive.So I used Partition Commander to delete the partition and then recreated it again as an NTFS partition-(same as before)- did as it said and used the Windows 2000 disc to do the NTFS formatting.Installed all my programs again except for the two that caused problems-everything worked fine except for the TV player for my ATI All in Wonder 128 Pro 4x AGP card.I was happy!
Since then I have disabled and re enabled System Commander a couple of times- the problem is deinitely with System Commander-it has somehow screwed up the 2000 setup- now I can't even boot directly to it.
The one difference I did with this install that I used FDISK first to make the partition "active"- at the time the third hard drive was the only one hooked up- I tried to make that same partition acvtive before with the other drives hooked up when trying to install Linux-I always would get a message saying I couldn't do that- was using a Windows 98SE boot disk.AS I said in previous post this what I understood to do from Microsoft Tech Support. Below is a link from V-COM support for System Commander- I have been trying to avoid letting anything else but System Commander write anything to the MBR of my first drive.
One other thing I noticed is that in Partition Commander it is only showing 968mb formatted as NTFS and the rest of the 9GB partition as free even though I formatted the whole partitioned as NTFS with the Windows 200 disk.Check out that link- let me know what you think- obviously I have to start over again- time to watch the Lakers-thank's for your time- Dave http://www.systemcommander.com/support/sup_os20.html