TDK 48x Slow

Hi all,

I've been having problems burning with my TDK VeloCD 48x lately in that it
burns a full 700 MB of data in *5 minutes.* It should only take 2:30
minutes or so, but I can't imagine what the problem could be. I have the
latest firmware and am using TY Fuji Media (48x). I have finished burns in
2 min before, but can't think of why its not working now.

Anyone have any ideas? P4 1.7, 1 GB RAM

The Big D wrote:
Hi all,

I've been having problems burning with my TDK VeloCD 48x lately in that it
burns a full 700 MB of data in *5 minutes.* It should only take 2:30
minutes or so, but I can't imagine what the problem could be. I have the
latest firmware and am using TY Fuji Media (48x). I have finished burns in
2 min before, but can't think of why its not working now.

Anyone have any ideas? P4 1.7, 1 GB RAM

One possibility is that the current blanks are not recognized as capable
of 48x. They are rebadged, so may not even be T-Y, but if they are, they
may have a new identification in the ATIP which is not recognized by the
firmware of the drive. If there's new firmware, it may recognize the
blank and not use the default speed.

Mike
--

http://www.mrichter.com/

"Mike Richter" wrote in message
...
One possibility is that the current blanks are not recognized as capable
of 48x. They are rebadged, so may not even be T-Y, but if they are, they
may have a new identification in the ATIP which is not recognized by the
firmware of the drive. If there's new firmware, it may recognize the
blank and not use the default speed.

It turns out my drive is set to PIO mode under Device Manager. Even after
setting it to "DMA if available" I'm still not able to do get ot to change
to DMA Only. I've restarted, even disconnected the drive and had it
recognized again, and I still can't figure out whats wrong.

Big D

"The Big D" wrote in message
ink.net...

"Mike Richter" wrote in message
...
One possibility is that the current blanks are not recognized as capable
of 48x. They are rebadged, so may not even be T-Y, but if they are, they
may have a new identification in the ATIP which is not recognized by the
firmware of the drive. If there's new firmware, it may recognize the
blank and not use the default speed.

It turns out my drive is set to PIO mode under Device Manager. Even after
setting it to "DMA if available" I'm still not able to do get ot to change
to DMA Only. I've restarted, even disconnected the drive and had it
recognized again, and I still can't figure out whats wrong.

Big D



You may need to go into your computer BIOS settings prior to booting into
your operating system and set the drives to DMA or UDMA.

-JasonW

The Big D wrote:
"Mike Richter" wrote in message
...

One possibility is that the current blanks are not recognized as capable
of 48x. They are rebadged, so may not even be T-Y, but if they are, they
may have a new identification in the ATIP which is not recognized by the
firmware of the drive. If there's new firmware, it may recognize the
blank and not use the default speed.


It turns out my drive is set to PIO mode under Device Manager. Even after
setting it to "DMA if available" I'm still not able to do get ot to change
to DMA Only. I've restarted, even disconnected the drive and had it
recognized again, and I still can't figure out whats wrong.

Big D



Big D,

If you are using WinXP you'll have to remove and redetect your Primary
or Secondary IDE controller. No need to reboot. WinXP keeps track of
problem/failed reads and automatically drops your drive down to PIO
after a certain number. It can be indicative of some other problem.
For example, I had a power connector that was badly formed and would
cause the CD-ROM to which it was attached to misread.

Hope that helps,

Enkidu