#%&*ing Partition (Drive)! PLZ HELP!

[Beefy_Suavo]

It looks like getting Windows setup to find the driver for the SATA controller is what needs to be done before it can recognize any vaild partitions or talk with the drive correctly.

2. I tried the F6 SCSI/RAID drivers thing and it refuses to recognize that I am pressing F6. It has no problem recognizing F2 for automated repair blah (sadly I never made a floppy for automated repair).

When you press F6, the setup program will continue to load, but eventually take you to a screen that says:
"Setup could not determine the type of one or more mass storage devices installed in your system, or you have chosen to manually specify a driver."
It should then let you load a driver for the SATA controller off a floppy disk.

3. Is there any way to edit the boot.ini in the recovery console? Everytime I type, "C:\Windows\>edit boot.ini", it says it cannot recognize that command.

The recovery console does not come with a text editor. You have to make a boot.ini file on another computer, save it to a floppy disk, and use the recovery console to copy it to the hard drive.
A sample boot.ini file:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\Windows="Microsoft Windows XP Professional" /fastdetect

multi() is the drive controller. The first valid number is 0.
disk() is always 0
rdisk() is the physical hard disk attached to drive controller in multi(). The first valid number is 0.
partition() is the partition number on the physical disk specified by rdisk(). The first valid number is 1.

You can try to have the recovery console repair the boot.ini file by using the bootcfg /rebuild command. If that doesn't work you can view the existing hard drive information by using the map command in the recovery console. You use the information from the map command to create and edit a new boot.ini file using another computer and copy it over.
I would try increasing the number in multi() one by one and see what happens.

More information on the boot.ini file can be found here.