@DeathscytheHELL
Well, let me explain.
This thread is now 4 agonizing pages. And like everyone else, you have tried many different configs and driver installs.
What I should have said is that I needed a snapshot at this exact moment in time with your transfer problem, with that moments HW config. It is unfair to ask me "what did I do wrong"? You had also talked about buying a SATA drive - so I didnt know what was happening with that. You also said Fri was your deadline, but its now Saturday.
Now, thanks to this thread, and coupled with my obsession about understanding the reasons why computers do certain things, I have fresh installed XP SP2 12 times. When you do the math of around 35min each, you get 7 hours of joy just for that. The problem here is that by the nature of what we are doing, we cant just image the O/S - we have to go thru the whole enchilada each time. After a while one begins to lose the ability to recall what was actually done to be successful. Now that you have prompted me it comes back that I was having trouble getting the JM named IDE controller listed, so I used NLITE 1.3 final (just out) to SLIPSTREAM the JM driver pak into my XP SP2 CD. I also slipstreamed the X32 floppy, but that was no help after the fact. Thats why I had no burners showing - something VERY frequent in other forums about the DS3.
[As a side note, nlite is the answer for PC with no floppy].
link
So, at that early ttime in my DS3 journey, because I wanted to force the JM IDE controller in dev man, I did not use F6. As a result, after XP install I had no IDE showing, I had the JM generic 36X under SCSI controller and another JM under it as a yellow question mark (it didnt know if I wanted RAID because of no F6 "S" select option), so when I used my USB stick to do the JM setup.exe, I finally got my JM IDE controller showing in IDE controllers, and the questionmark raid was gone, because it now knew I didnt have RAID configured in BIOS. In other words, with the latest JM R17.11.02, this is now irrelevant. JM did add an inf file to the 17.11 that the 17.08 didnt have.
I might mention here you have to set "none" twice under intel - but thats a minor point. The second "none" speeds booting - nothing left on Intel to look for.at boot.
Getting back to your specifics. I still think you have a hardware prob.
I think it has to do with RAM, RAM settings, MIT bios settings and voltages
Repeating 2 things first---
One MUST use an XP SP2 embedded CD.
One must NOT overclock anything during O/S install and config., keep FSB at 266 and 2.0X (1:1), which will show as 533 in blue.
Having said that, I want you to buy and try some +R DVD - just for the heck of it.
I need you to download and run CPU-Z
1.39 and give me screenshots of memory and SPD tabs
http://www.cpuid.com/cpuz.php
I need you to download Intel TAT and give me temps
http://www.techpowerup.com/downloads/392/mirrors.php
And, most importantly, I want you to download orthos (dual core) and run it for an hour
http://sp2004.fre3.com/sp2004exe_20060405.cab
http://sp2004.fre3.com/beta/beta2.htm
http://forums.anandtech.com/messageview.cfm?catid=28&threadid=1901991
Im really thinking upping some of the various voltages will fix your prob
WITH ONE BIG CAVEAT -
If you have the JM loaded as AHCI (which you do), then you must have the JM 36x controller showing in IDE controllers, or you will indeed have optical burning problems, since it will confuse XP and try to work the IDE DVD as a SATA device. So your drive wont burn or will disappear after a while, or change drive letters, Those that use JM SATA side in IDE mode in BIOS will have no probs on green molex, since both sides can now use IDE.
And something else - non related to your prob. If you want AHCI on Intel, you must set it as AHCI in bios when you first turn intel on in bios and load hack drivers at first boot. You cant go from IDE to AHCI, but you can go from AHCI to IDE.
Yet another point on something I have advised about on other forums that absolutely no one has paid any attention to - The DS3 is a board that doesnt like to reboot on the fly (after no complete shutdown) with RAM reset in BIOS at 2.1 - 2.4V or higher. Thats why the nvidia 680i board has EPP. So just when initially setting up your computer (and
IF you have issues), one should purchase a single stick of RAM 512MB that has an SPD spec to run at 1.8V., or perhaps 1.9. and use it, instead of your super trick 2X1GB high FSB LL high voltage RAM.
Just think, if vailr hadnt posted a screenshot of his correctly configured dev manager, i would have done none of this.
:Q
Edit:
Almost forgot -
What is your PSU? If you have already stated it, I apologize, but I am not going back to look - lol