I would post the screenshots in the thread, but they are fairly large (5 pics totaling about 500kb), so I’ll just link to them.
My problem is that for some reason, Nero, CloneCD, Alcohol, etc. don’t give my Liteon 32123S any respect.
When I first installed Windows XP, it was working fine. I could burn at 32X with no problem. However, after installing many applications on it, I have noticed several things.
1: It burns at 12X consistently
2: It uses up 100% of one of my CPUs (I own a dual processor machine so it uses 50% of my total CPU power)
3: In Windows Task manager Nero (or CCD) uses up about 5-6% of the CPU, but there are no other apps open that would use up the rest of the CPU cycles; even adding up all the CPU percentages would result in less than 20% usage.
However, the quality of the burns does not seem to denegrate, as I was able to copy GTA3, MOH:AA, etc. with no problem. I’m just getting ticked off at it.
Pre-burn - Taken just before burning a CD in Nero. Notice the CPU usage is very low and Nero is set to burn at 32X
During burning - Taken while Nero burns. You will see that Nero is only using 1% of the CPU (the max it ever gets to is 7 to 8%), system idle is using 94%, yet at the bottom of the screen it states that CPU usage is at 50% (Again, this is like a 100% usage on a uniprocessor machine)
During Burning - Same as the previous pic, only you can see the graph (the spike 1/4 into the graph is when Nero began burning)
Leadout - During the leadout. Notice that while Nero is writing the leadout, CPU usage is down to 4% and the graphs have fallen.
Burning complete - Notice how the CPU graphs have remained low and that a 32X burn of a 612MB CD took 5 minutes 34 seconds.
Dual AMD MP 2000+
Windows XP Pro SP1
Latest versions of Nero, CloneCD, and Alcohol 120%
Latest firmware for the LTR32123S
I tried burning CDs and images without ASPI layers installed, and with the brand new ASPI, but got the same result. Currently I have the brand new ASPIs (for Windows XP of course)
Anyone able to help me with this?
1: Something is wrong with my installation of Windows XP. This is my main guess, because I have a second installation of XP Pro dual-booting (this one runs in uniprocessor mode), and it burns completely fine. However, I know the problem doesn’t rest in the dual processors, because I had burned them at 32X for over 4 months in duallie mode.