Member Avatar for calvin12

I just got this drive and hooked it up and it burns ok but slowly. When I check the nero drive info. it tells me thats its a CLV drive instead of a CAV drive. Because of this it runs at ~20x all over. Now sure this is OK in terms of speed, but its not what I want it to do. Any ideas how to get it to go CAV as it should? I already updated the firmware on the drive. The CPU usage seems high to me which would indicate a DMA problem. Any ideas if this is the problem and how to fix it?


AMD 1100
512 ram
Ge4 4400ti video
Winxp Pro

Drive Information
-----------------
Drive : LITE-ON LTR-52327S
Type : CD-RW Recorder
Firmware Version : QS0C
Buffer Size : 2 MB
Date : ?
Serial Number : ?
Drive Letter : G:\
Location : 1:0
Mechanism : Tray
Read Speed : 52, 48, 40, 32, 24, 16, 12, 8, 4 X
Write Speed : 8, 4 X

Read CD Text : Yes
Return C2 Pointers : Yes
Read CD-R : Yes
Read CD-RW : Yes
Read DVD-ROM : No
Read DVD-RAM : No
Read DVD-R : No
Read DVD-RW : No
Read DVD+R : No
Read DVD+RW : No
Read Digital Audio : Yes
Read CD+G : Yes
Read VideoCD : Yes

Write CD-R : Yes
Write CD-RW : Yes
Write DVD-R : No
Write DVD-RW : No
Write DVD+R : No
Write DVD+RW : No
Write DVD-RAM : No
Buffer Underrun Protection : No
Mount Rainier : Yes
Modes : Packet, TAO, DAO, SAO, RAW SAO, RAW SAO 16, RAW SAO 96, RAW DAO 16, RAW DAO 96

Adapter 2
---------
Description : Secondary IDE Channel

Driver
Description : System32\DRIVERS\atapi.sys
Company : Microsoft Corporation
Version : 5.1.2600.1106 (xpsp1.020828-1920)
Description : IDE/ATAPI Port Driver

Attached Devices
Description : Master: LITE-ON LTR-52327S
Type : CD-Rom Drive
DMA : On
Autorun : On
Description : Slave: IDE DVD-ROM 16X
Type : CD-Rom Drive
DMA : On
Autorun : On

Software Information
--------------------
Operating System : Windows XP Professional (5.01.2600 Service Pack 1)
ASPI : Win32 Nero Aspi Library Ahead Software AG

ASPI Information
----------------
System ASPI

wnaspi32.dll : 4.57 (1008) 48128 bytes December 22, 1997
aspi32.sys : 4.57 (1008) 23936 bytes December 22, 1997
winaspi.dll : 4.57 (1008) 5600 bytes December 22, 1997
wowpost.exe : 4.57 (1008) 4672 bytes December 22, 1997

Nero ASPI

WNASPI32.DLL : 160016 bytes January 29, 2003

  • 2 Contributors
  • 2 Replies
  • 116 Views
  • 8 Hours Discussion Span
  • Latest Post Latest Post by TallCool1

Dani AI

Generated

Good follow-up from and thanks to for the acknowledgement. The behaviour described is a classic transfer-mode/negotiation issue rather than a laser/firmware fault: when the OS and controller don’t negotiate a high‑speed DMA mode the burn will look slow and CPU use rises. The reported fix worked because it let the motherboard present the optical device in a way Windows could negotiate the correct transfer mode.

Quick, safe checklist to prevent and diagnose this kind of slowdown:

  • Verify the current transfer mode in Device Manager: open IDE ATA/ATAPI controllers, pick the channel, and check Advanced Settings for the device’s Current Transfer Mode (should show an Ultra/UDMA mode, not PIO). If it’s PIO, try uninstalling the IDE channel and rebooting so Windows redetects it.
  • Use the correct hardware: an 80‑conductor IDE cable is required for UDMA66/100/133 speeds and good, firmly seated connectors prevent CRC errors that force PIO fallbacks. Avoid putting two high‑speed devices on one cable when possible.
  • Update chipset/motherboard drivers and BIOS (follow the vendor instructions). Replacing a flaky cable or moving the drive to a different controller can reveal if the drive or the host is at fault.
  • If a burning utility shows the drive running in CLV/CAV modes, remember some drives use zoned or pseudo‑CAV and software reports aren’t always a precise indicator of throughput. Use a CD/DVD benchmark or the burn log/graph to check actual sustained speed and CPU usage.
  • If third‑party ASPI layers are present, try disabling them or using native SPTI to rule out driver conflicts.

If problems persist after these checks, test the drive on another machine or controller and inspect Windows Event Viewer for IDE/ATAPI errors before assuming drive hardware failure.

Recommended Answers

All 2 Replies

Member Avatar for calvin12

got it fixed. it was in DMA multipage 2 mode and I ended up going back to the BIOS under the HDD detect area and had it detect the CD and DVD as HD's and that allowed WINXP pro to change the DMA mode higher. Before I didn't have the bios detecting the opticals, I just let windows get them itself.

Member Avatar for TallCool1

Thanks for letting us know what fixed your problem!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.