Verifying DVD+R disc with Nero and NEC ND2510A

Ichinisan

Lifer
Oct 9, 2002
28,298
1,235
136
NEC ND2510A DL-capable
Standard DVD+R (not DL) disc, multiple brands

I burned a couple of files to a DVD+R disc and selected the option in Nero (6.6.0.1) to "Verify written data". One of the files is more than 4GB, and I'm trying to free up some space on my file server. Nero reported that "Data verification failed".

When I tried to copy the file to my desktop so that I could perform an "FC" (file comparison) from the command prompt, I got a cyclic redundancy check (CRC) error from Windows after a few minutes and the file will not copy from the disc.

I suspected that the burn was just a failed attempt, but I put the disc into my laptop and the file copied easily from the disc to my desktop. I was suspicious, so I transferred the file (via 1394 firewire) back to the file server and performed the file comparison. They were both byte-for-byte identical! This means that my drive burned a perfectly good disc, but is incapable of reading it back!

My last computer had an older NEC 4x DVD+R drive, purchased when recorders were all about $400.00 and dual-format was still on the horizon. It had the same exact problem! I never got a replacement for that drive because the site that sold it to me wouldn't communicate, so I had a $400 paperwieght. I've heard that these super-cheap NEC drives are crap by comparison with Plextor, Lite-on, and Sony; but how can they even be consumer-grade if they can't read back their own discs!?!

4:35:25 PM #32 Phase 37 File dlgbrnst.cpp, Line 1855
Burn process completed successfully at 2.4x (3,324 KB/s)

4:35:25 PM #33 Phase 78 File dlgbrnst.cpp, Line 1855
Data verification started

4:36:03 PM #34 SCSI -1093 File Cdrdrv.cpp, Line 1445
SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x0378C000
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x03 (KEY_MEDIUM_ERROR)
Sense Code: 0x02
Sense Qual: 0x00
CDB Data: 0x28 0x00 0x00 0x00 0x52 0x09 0x00 0x00 0x10 0x00 0x00 0x00
Sense Data: 0xF0 0x00 0x03 0x00 0x00 0x52 0x10 0x0A
0x00 0x00 0x00 0x00 0x02 0x00

4:36:03 PM #35 Text 0 File DriveFileSystemBlockReader.cpp, Line 231
Error during reading the sector: 21001

4:36:03 PM #36 VERIFYERR 6 File UDFCompilationImpl.cpp, Line 1686
Read error on CD file
Wrongfully Accused (Full Screen)\WRONG_DB.ISO

4:36:04 PM #37 VERIFYERR 13 File UDFCompilationImpl.cpp, Line 1385
Status summary
Total files=3, identical=2, different=0, inaccessible=1, skipped=0.

4:36:04 PM #38 Phase 81 File dlgbrnst.cpp, Line 1855
Data verification failed


Existing drivers:
File 'Drivers\atapi.sys': Ver=5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), size=95360 bytes, created 8/3/2004 5:59:44 PM (Adapter driver for rec)
File 'Drivers\d347prt.sys': Ver=3.47.0.0 built by: WinDDK, size=5248 bytes, created 8/22/2004 3:31:48 PM (Adapter driver for src)

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)
 

bigboxes

Lifer
Apr 6, 2002
42,391
12,428
146
I have the 2500 and have heard and experienced the same thing. It seems as if NEC makes an excellent burner, but their reading abilities are lacking. Luckily I have another DVD-ROM drive to do just that. Kinda sucks though.
 

Ichinisan

Lifer
Oct 9, 2002
28,298
1,235
136
Originally posted by: Trader05
have you tried the latest firmware upgrade?
I updated it about a month ago.

Originally posted by: MercenaryForHire
My older ND1100A doesn't have any issues verifying burns, but I've never tried a file >4GB.

- M4H
That's the same model I had, which failed after only a few burns. I don't really know if the "successful" burns were any good either...
 

Neptune3000

Senior member
Sep 15, 2004
278
0
0
oh crap, i have a 3500A on the way to be here on monday!!!!:eek:

Lite on sucks anyways, i have 2 of their drives and they suck....I shhould of gotten the plextor..save myself some headaches. newegg sucks :/ I cant even refund it because they already screwed up my other refunds and have neglected to refund my cash for over 3 weeks now. monday will make the start of the 4th week. I'm thinking about suring :X