dbminter

I decided not to switch back from Elby just to give it a go and see what it's like. If there's an issue, I'll switch back. And, when the next Windows 10 is released, I'll be restoring down my 1909 installation image, updating it, and saving a new Windows 10 image. That will restore the I/O back to SPTI anyway, if I don't do it in the meantime.

I have relatively few posts on the Redfox and VSO forums as compared to here and the Reflect forums.

I knew SPTI allowed for "soft" locks. Meaning you couldn't eject the locked access drive with a Windows/File Explorer Eject context menu command, but I wasn't aware it didn't not fully lock the physical eject method. Yes, ever since I got a Dell XPS 8930 a year and a half ago, I've wondered how an optical drive can be set up in a RAID configuration. It still says RAID on the Elby I/O interface option, though. And, yes, I am the same dbminter on the AnyDVD forum. I think I use the same nick on the ConvertXToDVD forum, too. And Macrium Reflect forum.

Except when they introduce bugs into new versions.

I just tested my installation of 5.5.2.0 and, on my machine, it DOES fix the locking drive for exclusive access failing issue 5.5.1.0 introduced. So, you should test it on your end and make sure it now works after updating to 5.5.2.0.

There's a new update, 5.5.2.0, but it's change log is a little odd: Fix: Bug introduced in 5.5.1.0, ElbyCDIO did not work with Windows Server OS, Windows XP, Windows Vista It doesn't mention this specific issue we've encountered on Windows 10. So, it may still be present in this new version.

I created a CD sized DVD Video image with Build and then used Write to write that image to a Ritek 8x DVD+RW. Here's the log: I 11:13:12 Microsoft Windows 10 Core x64 Edition (10.0, Version 1909, Build 18363) I 11:13:12 Total Physical Memory: 16,579,480 KiB - Available: 8,686,440 KiB I 11:13:12 Initialising SPTI... I 11:13:12 Searching for SCSI / ATAPI devices... I 11:13:12 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (N:) (SCSI) I 11:13:12 -> Drive 2 - Info: HL-DT-ST BD-RE BU40N A102-01 (K:) (RAID) I 11:13:12 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (L:) (SCSI) I 11:13:13 -> Drive 4 - Info: HL-DT-ST BD-RE WH16NS60 1.02 (R:) (USB 3.0) I 11:13:13 -> Drive 5 - Info: ELBY CLONEDRIVE 1.4 (Q:) (SCSI) I 11:13:13 Found 3 BD-ROM/HD DVD-ROMs and 2 BD-RE XLs! W 11:13:25 I/O Interface has been changed! I 11:13:25 Shutting down SPTI... I 11:13:25 Initialising ElbyCDIO... I 11:13:26 ELBYCDIO.DLL - Elaborate Bytes CDRTools - ElbyCDIO DLL - Version 6.1.9.2 I 11:13:26 ELBYCDIO.SYS - CDRTools - ElbyCD Windows x64 I/O driver - Version 6.1.3.0 I 11:13:26 Searching for SCSI / ATAPI devices... I 11:13:26 -> Drive 1 - Info: HL-DT-ST BD-RE BU40N A102-01 (K:) (RAID) I 11:13:26 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (L:) (SCSI) I 11:13:26 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (N:) (SCSI) I 11:13:26 -> Drive 4 - Info: ELBY CLONEDRIVE 1.4 (Q:) (SCSI) I 11:13:26 -> Drive 5 - Info: HL-DT-ST BD-RE WH16NS60 1.02 (R:) (USB) I 11:13:26 Found 3 BD-ROM/HD DVD-ROMs and 2 BD-RE XLs! I 11:13:42 Operation Started! I 11:13:42 Building Image Tree... I 11:13:44 Corrected file system selection for DVD Video disc. I 11:13:44 Corrected UDF revision selection for DVD Video disc. I 11:13:44 Calculating Totals... I 11:13:44 Preparing Image... I 11:13:44 Contents: 7 Files, 2 Folders I 11:13:44 Content Type: DVD Video I 11:13:44 Data Type: MODE1/2048 I 11:13:44 File System(s): ISO9660, UDF (1.02) I 11:13:44 Volume Label: [Not Configured] I 11:13:44 IFO/BUP 32K Padding: Enabled I 11:13:44 Region Code: 1, 2, 3, 4, 5, 6, 8 I 11:13:44 TV System: NTSC I 11:13:44 Size: 40,785,920 bytes I 11:13:44 Sectors: 19,915 I 11:13:44 Image Size: 41,418,752 bytes I 11:13:44 Image Sectors: 20,224 I 11:13:44 Operation Successfully Completed! - Duration: 00:00:01 I 11:13:45 Operation Started! I 11:13:45 Building Image Tree... I 11:13:47 Calculating Totals... I 11:13:47 Preparing Image... I 11:13:47 Contents: 7 Files, 2 Folders I 11:13:47 Content Type: DVD Video I 11:13:47 Data Type: MODE1/2048 I 11:13:47 File System(s): ISO9660, UDF (1.02) I 11:13:47 IFO/BUP 32K Padding: Enabled I 11:13:47 Region Code: 1, 2, 3, 4, 5, 6, 8 I 11:13:47 TV System: NTSC I 11:13:47 Size: 40,785,920 bytes I 11:13:47 Sectors: 19,915 I 11:13:47 Image Size: 41,418,752 bytes I 11:13:47 Image Sectors: 20,224 I 11:13:48 Operation Successfully Completed! - Duration: 00:00:02 I 11:13:48 Operation Started! I 11:13:48 Image Contents: 7 Files, 2 Folders I 11:13:48 Image Sectors: 20,224 (MODE1/2048) I 11:13:48 Image Size: 41,418,752 bytes I 11:13:48 Image Single Layer Profile: DVD-R/RW (Media Capacity: 2,297,888) I 11:13:48 Image Volume Set Identifier: 505B59B600004EE0 I 11:13:48 Image Implementation Identifier: ImgBurn I 11:13:48 Image File System(s): ISO9660, UDF (1.02) I 11:13:48 Destination Free Space: 874,760,036,352 Bytes (854,257,848.00 KiB) (834,236.18 MiB) (814.68 GiB) I 11:13:48 Destination File System: NTFS I 11:13:48 File Splitting: 4 GiB I 11:13:49 Writing Image... I 11:13:49 Operation Successfully Completed! - Duration: 00:00:01 I 11:13:49 Average Write Rate: 40,448 KiB/s (29.9x) - Maximum Write Rate: 40,448 KiB/s (29.9x) I 11:14:33 Operation Started! I 11:14:34 Source File Sectors: 20,224 (MODE1/2048) I 11:14:34 Source File Size: 41,418,752 bytes I 11:14:34 Source File Volume Set Identifier: 505B59B600004EE0 I 11:14:34 Source File Implementation Identifier: ImgBurn I 11:14:34 Source File File System(s): ISO9660, UDF (1.02) I 11:14:34 Destination Device: [0:2:0] HL-DT-ST BD-RE BU40N A102 (K:) (RAID) I 11:14:34 Destination Media Type: DVD+RW (Disc ID: RICOHJPN-W21-01) I 11:14:34 Destination Media Supported Write Speeds: 3.3x, 6x, 8x I 11:14:34 Destination Media Sectors: 2,295,104 I 11:14:34 Write Mode: DVD I 11:14:34 Write Type: DAO I 11:14:34 Write Speed: MAX I 11:14:34 Link Size: Auto I 11:14:34 Lock Volume: Yes I 11:14:34 Test Mode: No I 11:14:34 OPC: No I 11:14:34 BURN-Proof: Enabled E 11:14:47 Failed to lock drive for exclusive access. E 11:14:47 Reason: The system cannot find the file specified. E 11:14:50 Operation Aborted! - Duration: 00:00:13 I 11:14:50 Average Write Rate: N/A - Maximum Write Rate: N/A W 11:14:58 I/O Interface has been changed! I 11:14:58 Shutting down ElbyCDIO... I 11:14:58 Initialising SPTI... I 11:14:58 Searching for SCSI / ATAPI devices... I 11:14:58 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (N:) (SCSI) I 11:14:58 -> Drive 2 - Info: HL-DT-ST BD-RE BU40N A102-01 (K:) (RAID) I 11:14:58 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (L:) (SCSI) I 11:14:59 -> Drive 4 - Info: HL-DT-ST BD-RE WH16NS60 1.02 (R:) (USB 3.0) I 11:14:59 -> Drive 5 - Info: ELBY CLONEDRIVE 1.4 (Q:) (SCSI) I 11:14:59 Found 3 BD-ROM/HD DVD-ROMs and 2 BD-RE XLs! I'm not entirely sure what the extra log entries are for, but it's all there somewhere. Both the image creation and the attempted write. I removed some identifying log lines, though.

I can verify it's a bug in the Elby driver. I got the same result. Switching back to SPTI still worked.

This should be what you're looking for:

Where/when do you see this error message you described in ImgBurn? I'll see if I can replicate the issue on my end.

I use the apparent default, SPTI. It always worked for me, so I never had a need or desire to try anything else.

There's a new update to Virtual CloneDrive, 5.5.1.0, just released. It might affect several users of ImgBurn. I know it does me since I use it. It's been a few years since the last update.

This sounds familiar. Was this posted once before?

If ConvertXToHD is anything like VSO's ConvertXToDVD, which I've used for years, there is an option to create ISO files with the software. I choose not to create ISO's except with ImgBurn because I add contents to my DVD's before burning them.

Probably not really a "security" issue. The other sites have probably stripped out the actual ImgBurn installer and put in their own download agent. They'll serve you ImgBurn, but also probably all kinds of unwanted crap. Well, I guess one could categorize that a "security" issue.

Never heard of PIODATA. They make BD burners? Full height internal models?

I sent LG a logical, detailed, and thorough explanation as to why they needed to update the firmware for the WH16NS60 to address the DVD-R's no longer writing properly. What did LG do? They sent me a boilerplate text response saying most issues are not firmware related. I've only been goddamn beta testing ImgBurn for 15 years. It's not like I can't follow Mill's methods of observation to determine a firmware problem.

Why do I need to call THEM? Shouldn't they know I need counseling and call me to let me know of impending doom?

On my Dell's, including 2 8930 XPS systems, I HAD to uninstall McAfee in order to install ZoneAlarm Free Firewall. I even had to download the FULL uninstall utility from McAfee's web site in order to remove its insidious tentacles from the system. Windows Defender has, indeed, come a long way since its inception. PC World tests place it as a more than capable AV solution now.

AAAAAAAAAAAAAAAAAND the play back test, of course, failed. So, it wasn't a dying drive, but CMC fucked with the DVD-R's now so they're just as useless as the DVD+R's from Verbatim DataLife Plus. I'll try those TY's I found. They may be cheaper, but they may be actual TY quality.

Installed the replacement NS60 a week ago this past Saturday. Since then, I've burned a few DVD+R DL and 2 BD-R and BD-RE fine. I had my first opportunity to burn a DVD-R in it just now. No noticeable read or write speed dips that weren't explainable in either Write or Verify. The play test will be the proof in the pudding. And, of course, before, I'd get 1 good burn and then a bad burn alternately. So, I still don't know yet if it's a change in the DVD-R's that CMC made that the NS60 doesn't like or maybe I got a bad batch of discs.

I can't say for sure but something must be wrong with the source because it took only 1 second, apparently, to create the Test ISO. I'd have thought a BD Video disc would be significantly larger than just a 1 second write.

I thought there was an option to queue image files. As long as you changed the name of the image file each time, it would queue up the entire list and then burn each one one after the other. In Build mode, under Options tab next to Information, make sure Add to write queue when done is checked. As long as you change the target image file name each time, each time you build a new image, it should queue them all in order or creation.

Oh, if that's what you wanted, then I think the only solution is to queue image files and burn the queue. The EZ Mode Picker option I mentioned, I think, only burns one task at a time. I don't think you can queue up anything in that. I've only used that option once I can think of, and that was a troubleshooting test.

As for #1, I don't really know if it's necessary or not. Couldn't hurt, though I don't think it's necessary. I don't understand what you're asking with #2. Are you asking is there a way to burn data to a disc without having to write to an image file first? If that's what you're asking, yes, there is. Under Mode, use the EZ Mode Picker. Then use Write files/folders to disc. It uses a similar interface to creating an image file from files, but instead of creating an ISO, it burns directly to disc.