Sizzlechest

Same drives. I'm beginning to wonder if Windows 10 might be another factor. I'm trying to remember if we upgraded the old PC from Windows 7 or not. The WH16NS58 is what Primera uses in their duplicators. The WH16NS40 used to be a different drive, but at some point they used the WH16NS58 drive and hobbled the firmware. EDIT: Okay, I found the problem. The registry entry for Blocked needs SOMETHING in there. It can't be blank. DOH!

I have a bunch of LG HL-DT-ST BD-RE WH16NS40 drives cross-flashed to WH16NS58. Nero Discspeed can do quality scans on DVD and DVD-DL discs with these drives. We moved from desktop computers to HP Elitebooks and now Discspeed no longer seems to offer the quality tab. (Yes, I took out the "Blocked" string in the registry.) There's no way to play with the SATA settings in the BIOS. Other than try another kind of computer, does anyone have any suggestions for a workaround?

PrimeraUser: I have a lot of experience with Primera duplicators. Your best bet is to use the PTPublisher or PTBurn. If you're looking to automate burning, PTBurn is the way to go. All you need to do is create a program to generate text files with all the information needed to create jobs. I'd suggest using something else to create ISO files and then pass those to PTBurn. If you want to do everything from the command line, get mkisofs under Cygwin or built for Windows to generate ISO files instead. I'm not sure if it supports HFS+, but it supports UDF, Joliet, and RockRidge.

I've had issues like this and it's due to a non-standard security setting. Did you harden your Windows security? Maybe it's a group policy? You have to track it down and change it to get it to work. The only other workaround might be to install Virtual Clone Drive since that will ALSO install the ElbyCDIO drivers and you could use that for IMGBurn instead.

Because I am scripting a dvd robot handler and I want to check the iso so I can load the correct disc (DVD-R vs DVD+R DL) into the burner.

That's good to know. So I assume the ISO file format has no additional headers or padding? It's a "raw" file format?

Is there an algorithm I can use to determine if the contents of an ISO file will fit on a DVD+R? Checking the overall file size would be easy, but I do worry about edge cases where it's borderline. Are there any existing utilities that do this from the command line?

Good to know. I just verified that I did use the new cable. It's a rare occurrence, so it's not easy to test a fix. The only two other options would be to try a different cable and/or upgrade the computer.

Sorry, let me explain. There are two LG drives inside a Primera 4202 Blu-ray disc duplicator. The third drive in the log is the one that's inside the computer that operates the duplicator. It's an old computer that doesn't have USB 3.0 ports. That's why the log shows USB 2.0 even though the "enclosure" can support USB 3.0. It's a single USB cable for both drives. I have not attempted simultaneous burns yet. When I get a new computer with USB 3.0 capability, I will attempt it. Considering how rare this error is and that it might be related to a communications issue rather than an inability of the drive to read/write the disc, I suggested troubleshooting by changing out the USB cable. I might have re-used the USB 2.0 cable from the old duplicator rather than use a new USB 3.0 cable.

I know. I googled first before posting. I'm beginning to wonder if the solution is to change the USB cable! FYI, when the error occurs, the retries fly by almost instantaneously. It's not like it's reading a bad disc where it has to re-seek. It usually happened early on in the burn, but this one was near the end.

The drives are in a Primera Disc duplicator and it's new. The failures don't occur often. Maybe 1 every 50-100. I'm trying a different brand soon.

BTW, you can't get the CMC Pro DVD+Rs anymore. Only DVD-R is produced now.

These are CMC Pro, which are all you can get since TYs are no longer made in the old Japanese factory. Other people have tested these and found they were good.

I've been periodically getting this kind of error on my new LG burner: I 11:47:56 ImgBurn Version 2.5.8.0 started! I 11:47:56 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1) I 11:47:56 Total Physical Memory: 6,193,436 KiB - Available: 3,280,584 KiB I 11:47:56 Initialising SPTI... I 11:47:56 Searching for SCSI / ATAPI devices... I 11:47:56 -> Drive 1 - Info: HL-DT-ST DVDRAM GH70N UGA0-01 (E:) (ATAPI) I 11:47:57 -> Drive 2 - Info: HL-DT-ST BD-RE WH16NS58 TST4 (F:) (USB 2.0) I 11:47:59 -> Drive 3 - Info: HL-DT-ST BD-RE WH16NS58 TST4 (D:) (USB 2.0) I 11:47:59 Found 1 DVD±RW/RAM and 2 BD-RE XLs! I 11:48:09 Operation Started! I 11:48:09 Source File: U:\Disc Images\MPOE\MPOE 6.0.5.0B1\MPOE 6.0.5.0B1 - Disc 1 of 5 - RHEL 6.8 64-bit DVD.iso I 11:48:09 Source File Sectors: 1,924,219 (MODE1/2048) I 11:48:09 Source File Size: 3,940,800,512 bytes I 11:48:09 Source File Volume Identifier: RHEL 6.1 I 11:48:09 Source File Application Identifier: GENISOIMAGE ISO 9660/HFS FILESYSTEM CREATOR © 1993 E.YOUNGDALE © 1997-2006 J.PEARSON/J.SCHILLING © 2006-2007 CDRKIT TEAM I 11:48:09 Source File File System(s): ISO9660 (Bootable), Joliet I 11:48:09 Destination Device: [0:0:0] HL-DT-ST BD-RE WH16NS58 TST4 (F:) (USB) I 11:48:09 Destination Media Type: DVD+R (Disc ID: YUDEN000-T02-00) I 11:48:09 Destination Media Supported Write Speeds: 4x, 8x I 11:48:09 Destination Media Sectors: 2,295,104 I 11:48:09 Write Mode: DVD I 11:48:09 Write Type: DAO I 11:48:09 Write Speed: MAX I 11:48:09 DVD+R Reserve Track: No I 11:48:09 Link Size: Auto I 11:48:09 Lock Volume: Yes I 11:48:09 Test Mode: No I 11:48:09 OPC: No I 11:48:09 BURN-Proof: Enabled I 11:48:09 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x) I 11:48:09 Book Type Setting: N/A (Reason: Invalid Command Operation Code) I 11:48:10 Filling Buffer... (80 MiB) I 11:48:13 Writing LeadIn... I 11:48:22 Writing Session 1 of 1... (1 Track, LBA: 0 - 1924218) I 11:48:22 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1924218) W 11:54:34 Failed to Write Sectors 1894432 - 1894463 - Reason: Data Phase Error W 11:54:34 Retrying (1 of 20)... W 11:54:53 Retry Failed - Reason: Invalid Address For Write W 11:54:53 Retrying (2 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (3 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (4 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (5 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (6 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (7 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (8 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (9 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (10 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (11 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (12 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (13 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (14 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (15 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (16 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (17 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (18 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (19 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write W 11:54:54 Retrying (20 of 20)... W 11:54:54 Retry Failed - Reason: Invalid Address For Write E 11:55:08 Failed to Write Sectors 1894432 - 1894463 - Reason: Data Phase Error E 11:55:08 Next Writable Address: 1893472 I 11:55:08 Synchronising Cache... W 11:55:11 User opted to skip the 'Close Track/Session/Disc' functions. E 11:55:11 Failed to Write Image! I 11:55:14 Exporting Graph Data... I 11:55:14 Graph Data File: C:\Users\Pvcsadmin\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_WH16NS58_TST4_THURSDAY-MAY-03-2018_11-48_AM_YUDEN000-T02-00_MAX.ibg I 11:55:14 Export Successfully Completed! E 11:55:14 Operation Failed! - Duration: 00:07:01 I 11:55:14 Average Write Rate: 9,355 KiB/s (6.9x) - Maximum Write Rate: 10,972 KiB/s (8.1x) I 11:55:14 Close Request Acknowledged I 11:55:14 Closing Down... I 11:55:14 Shutting down SPTI... I 11:55:14 ImgBurn closed!

Right, but I was wondering if there is a better way. This still brings up the GUI rather than a completely silent opperation. Could the output be dumped to standard output rather than a file. I'm not sure how it handles errors like when there's no disc in the drive. Stuff like that.