CdSpeed surface scan results varying by device

cadjak · Nov 8, 2002

I burn a disk and then run CdSpeed surface scan. In my Lite-On 48x12x48 the disk can show up to 30% "damaged" (yellow) sectors. If I test the disk in my Asus 50x CD-Rom drive it comes out perfect. Is it me? The media? the drives? the test? This result is repeatable with different media and different burning software.

-cadjak

cadjak · Nov 8, 2002

Thanks Pokopiko. That's reassuring, since the CD ROM results were always good. The CDRW drive always showed errors. Are there better error detection programs than Cd Speed?

cadjak · Nov 8, 2002

How do I identify the system driver that they load?
-cadjak

LTR12101B · Nov 8, 2002

I have a vague recollection that the drive may need to support C2 error reporting, in order to get "damaged" reports.

Though on my writer, it just CRASHES it - though the DVD-ROM (which DOES do C2) works pretty well.

cadjak · Nov 9, 2002

CdSpeed recognizes when a drive does not support error reporting. For example, my system has a 2nd burner, an Imation 8x20 external scsi. If I try to use the surface scan function of CdSpeed with it, I get a messsage saying that the drive does not support error reporting.

BTW thanks for the partial name of that driver. I should be able to figure out the rest from that info.

-cadjak

Duracell · Nov 9, 2002

cdrpdacc.sys

Duracell

cadjak · Nov 9, 2002

Mille grazie!

-cadjak

Gilbert · Nov 10, 2002

pokopiko said:
CDR Inspector and CDR Diagnostic are both pretty good, although you should know that they use a very picky system driver which may conflict with some burning apps. So its better to have their driver deactivated when not using them.

How do you go about deactivating a driver? I thought they were automatically loaded when the os is loaded...

--
Gilbert

Gilbert · Nov 11, 2002

pokopiko said:
Either by hand, or by using an application that can do that. I can mention the diagnostic utility which is embedded in Feurio.

When you mention by hand, would you mean going into "services" and deactivating the driver there? I never did such thing before as I am more familiar with OS/2 which still has a config.sys to play around with...

--
Gilbert

Esprit · May 16, 2003

I had problems running CDR Inspector in XP. Found that the problem was a conflict between the program and Intel Application Accelerator that I had installed.
Removed Accelerator and the program works fine even with Alcohol, Nero and CLonecd also installed.

Got the tip from the Arrowkey home page.

scarecrow · May 16, 2003

CDR Inspector driver is really nasty. You'd better deactivate it when you don't use the program.