|"I have a xp pro sp3 disc that I downloaded from a msdn site."|
It's probably technically illegal, as far as Microsoft is concerned, to download a copy of any of their software that you normally have to pay for, unless Microsoft itself provides it (e.g. apparently you can get Windows 3.1 from them, free).
It's NEVER legal, as far as Microsoft is concerned, to use a Product Key that you do not own - either you must have paid for it, or you must own a computer that has the official sticker.
The latter is more important to Microsoft than the former.
If you have an official Microsoft sticker with the Product Key on it for the same version of Windows, Home or Pro (it doesn't matter whether it's got SPx updates or not) , which is supposed to be stuck to the outside of the computer case, that is the proof that you have a license to use that Windows version (you own the Product Key), and you can use an XP CD you have that came with the sticker, or a copy of one of the same version, Home or Pro.
Your Microsoft License allows to make one copy of your own Windows CD, for backup purposes in case the original CD is damaged.
It's perfectly legal, as far as Microsoft is concerned, for you to make a "slipstreamed" CD that has newer SP updates integrated into it by using your own XP CD's contents as the source of the files that you are integrating it into.
A CD-R is likely to work with virtually all CD or DVD drives - or a DVD-R if the drive can read them - other types of burned disks may not read properly in a drive they were not made in.
You must follow a proper procedure in the burning program you use, and there is a *.img file on Windows CDs and DVDs that is normally NOT visible in the operating system (or an equivalent file) even when the Views ettings in Window's Folder Options are custom set to show all files, that must be on the CD in order for the "slipstreamed" CD to be bootable.
Not all burning programs, including the simple one built into XP, can make a "slipstreamed" CD bootable.
E.g. Nero's Burning Rom module can, but that's usually not included in free versions of Nero, and some free burning software versions can. Most Paid versions of burning software can.
There are instructions all over the web for how to make a "slipstreamed" CD with SP3 updates integrated into the contents, using various versions of burning programs. There are similar instructions for how to integrate SATA drivers or other drivers into the CD's contents.
NOTE that if you use Nero's Burning Rom module, at least some versions have a bug - you must re-select something before you actually burn, otherwise the resulting CD will not be bootable. I have info about that for 6.x and 7.x versions of it.
"...the only thing I see in the bios settings that is Sata related is, Sata mode. I only have 2 options for it: IDE or Raid."
If you set that to IDE, you don't need to have SATA drive controller drivers installed in the operating system to use a SATA hard drive or optical drive - it's / they're recognized as (an) IDE compatible drive(s).
"....the DMA is disabled....
XP doesn't have the drivers built in for most things that first came out after XP was first released, circa 2001, and it doesn't have some of the drivers built in for things made before that.
The main chipset drivers for the mboard MUST be loaded in the operating system, otherwise it's likely the drives will not be able to run as fast as they are capable of because XP doesn't have the proper info about the main chipset's capabilities (main chipset "drivers" are mostly, or all, *.inf files that inform the operating system what the main chipset is capable of).
Whenever you load Windows from a regular Windows CD (or DVD) from scratch, after Setup is finished you must load the drivers for the mboard, particularly the main chipset drivers, in order for Windows to have the proper drivers for and information about your mboard hardware, including it's AGP or PCI-E, ACPI, USB 2.0 if it has it, and hard drive controller support. If you have a generic system and have the CD that came with the mboard, all the necessary drivers are on it. If you load drivers from the web, brand name system builders and mboard makers often DO NOT have the main chipset drivers listed in the downloads for your model - in that case you must go to the maker of the main chipset's web site, get the drivers, and load them.
Also, if you have an Intel main chipset and it's one of the earlier 8xx series that requires that you install the IAA (Intel Application Accelerator), you MUST install the IAA, otherwise the drives cannot run at the full speed they're cable of on the particular mboard. The IAA is listed in the downloads for the 8xx main chipset series on the Intel web site if it is required.
If you have a problem with the drive's data cable, Windows may detect too many data errors from the drive and automatically make a line in the Registry (without any error message appearing) that prevents that particular drive from using any UDMA mode (in will be set to PIO mode, and changing it to UDMA if available, saving settings, then going back in to look will find it's still in PIO mode) . Your SATA optical drive is probably supposed to show it's in UDMA4 mode (66 mbytes/sec max burst data transfer speed) , if your main chipset supports ATA66 or UDMA 66 or higher burst speed drives.
By the way, there is no advantage to using a SATA optical drive in comprison to an IDE optical drive regarding it's max burst data transfer speed, if the drive has the same or similar specs otherwise - the max UDMA4 / ATA66 / UDMA 66 rating is determined by the max speed the disk can be spun at without being likely to fly apart, and by the max density of the data that can be stored on current disks. That's not going to change until the disks are made of something that be safely spun faster, or they come up with disks that can store a lot more data on them in one circle of a data track on the disk than they presently do.
It doesn't matter, when a SATA optical drive is on a system, whether the SATA controllers are set in the bios to an IDE compatible mode or a SATA mode - the max burst speed is the same.
Depending on what main chipset brand you have, or in any case if it's not an Intel one, that's either shown in Device Manager - IDE ATA/ATAPI controllers - xxxx IDE channel - Properties - Advanced settings tab
or if you DO have an Intel main chipset and it's one of the earlier 8xx series that requires that you install the IAA (Intel Application Accelerator), the mode the drives are in are shown in the IAA in your all Programs list.
If you DO have an Intel main chipset and it's one of the earlier 8xx series that requires that you install the IAA (Intel Application Accelerator), you MUST install the IAA, othewise the drives cannot run at their full speed they're cable of on the particular mboard.
Check your SATA data cables. The connector on each end should "latch" into the socket on the drive and on the mboard, or on the drive controller card - it should not move when you merely brush your hand against it near the socket - if it does, mere vibration can cause a poor connection of it - use another SATA data cable that does "latch", or tape the connector in place.
(There is a slight projection or bump on one side of the outside of the connector that "latches" it into the socket - it's easily broken off or damaged)
The same thing applies for the SATA power connection.
If you can't get the SATA optical drive to use a UDMA mode after correcting the problem that caused the data errors, then you need to remove one or more specific lines from the Registry - we can tell you how to do that.
It is common to un-intentionally damage IDE data cables, especially while removing them - the 80 wire ones are more likely to be damaged. What usually happens is the cable is ripped at either edge and the wires there are either damaged or severed, often right at a connector or under it's cable clamp there, where it's hard to see - if a wire is severed but it's ends are touching, the connection is intermittent, rather than being reliable.
Another common thing is for the data cable to be separated from the connector contacts a bit after you have removed a cable - there should be no gap between the data cable and the connector - if there is press the cable against the connector to eliminate the gap.
80 wire data cables are also easily damaged at either edge if the cable is sharply creased at a fold in the cable.
Try another data cable if in doubt.
80 wire data cables must have the proper end connector connected to the mboard IDE header - usually that's blue, but in any case it's the one farther from the middle connector on a 3 connector data cable.
"....the computer boots sooo slow, and hangs sooo much....."
In addition to the above causes, if it's not a "fresh" installation, there are all sorts of things that can cause Windows to be slower than it once was with the same hardware components and amount of ram.