• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Slow 52X LiteOn burner

Wolfchild

Senior member
Few weeks ago I bought two LiteOn 52x24x52 burners for two computers.
The one in my machine takes 5 minutes to burn a CD, set it to burn at 52X
but Alcohol says it's more like 24X and lower even at the outer edges.
The other burner burns just as it should, a whole CD in less than 2.5 minutes.

The slow one is just as slow as my older LiteOn 32X in another box. What to do?
It's working perfectly fine, just slow. Don't know if I want to bother with
returning it though, I'll be using the faster one in the other machine more anyway.
Just wondering if there is something I'm missing.
 
You gotta get 52x media, and make sure DMA is enabled and the drive is set to its max speed.
 
I should clarify a couple things. The slow one is on a Win 2K Pro machine,
the fast one on an XP Pro machine.

But same media, same software, same settings the one burns about
twice the speed. I'm using Fuji 48X media.

Where would I enable DMA in Win2K Pro? I'm not seeing a checkbox for it.
Thought that was automatic but maybe that's the problem. And where do
I set the max speed for the drive?? Kind of new to using these so bear with me.
 
That did it...thanks a bunch..was set to PIO mode for some reason. Guess it shows how ignorant I am
but with this and a new firmware flash it's burning CDs in under 2 1/2 minutes now
like the other one 🙂
 
I knew that was the problem,,, because when DMA (direct memory access) is disabled it will put the cpu on heavy load and the cpu will pretty much bottleneck it. Good thing its working now...
 
Yeah I had also wondered why the drive sucked so bad at ripping audio too...that's why.
LOL the cpu usage was sky-high and didn't rip very fast. Fixed now.
 
Back
Top