Jump to content
dbminter

Virtual CloneDrive 5.5.1.0 released

Recommended Posts

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.

Share this post


Link to post
Share on other sites

Me too and it causes problems. Using "ElbyCDIO" under "File I/O" results in IMGBurn "failure to lock for exclusive access

Reason: The sytem cannot find the file specified." Reverting to 5500 doesn't fix the issue. and i'm not changing file IO.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

I had problems where it would report incomplete or incorrect info in the explore info. Already informed elby. Awaiting response.

Sent from my Pixel 3 XL using Tapatalk

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

The second you click on burn, just before it actually starts burning data. Imgburn 'locks' the drive so it can't be accidentally ejected during the burning. (Which afaik is possible with Microsoft's SPTI io)

Sent from my Pixel 3 XL using Tapatalk

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Care to elaborate where/what/how? I can then relay that to elby.

Sent from my Pixel 3 XL using Tapatalk

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

 

Share this post


Link to post
Share on other sites

way ahead of you. Fixes this too :) No more error message.

btw ElbyCDIO > SPTI

Share this post


Link to post
Share on other sites

Well considering the last release (before the buggy 5510) was in 2016. I can live with 1 tiny bug every 4 years :D

 

But for me personally, these are the main 2 reasons for using ElbyCDIO over SPTI

 

1. SPTI CANNOT lock drives for exclusive use (meaning if you accidentaly hit the eject button, which on occasion happens in my triple drive setup) the disc burning process would be interrupted and the disc ejected. With the elby driver, that can't happen. The drive gets locked for use until burning is completed and the drive released. You can manually hit eject all you want, it aint happening.

2. SPTI requires admin rights and above on NT/2000/XP/Vista..

21 hours ago, dbminter said:

Info: HL-DT-ST BD-RE BU40N A102-01 (K:) (RAID)


That's another reason, this won't happen with elby driver. You can't (RAID) an optical drive :p

 

btw you the same dbminter over at the redfox forums?

Edited by Ch3vr0n

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

well the elby driver "locks" the drive entirely. No amount of pressing the eject button will kick the disc out, (havent actually tried the content menu, but i doubt it will do it).

As to the raid thing, perhaps something in the bios, DELL bios's are hardly ever optimized as they should (eg, instead of using AHCI, they're often set in IDE mode for hard drives)

As to your handle, well i guess you own the postcount here, over on the redfox forums i do. Don't know about our shared VSO forums, and i hardly ever visit the MR ones :) .

 

btw any chance of implementing HTTPS ;) kinda mandatory under the GDPR @LIGHTNING UK!

Edited by Ch3vr0n

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites

The physical eject button/tray lock is a command you send to the drive, it has nothing to do with the locking abilities of the I/O interfaces.

Both interfaces are, unless buggy, perfectly capable of gaining exclusive access to the drive and preventing other apps from trying to use them at the same time.

Apart from when I'm testing a different interface for something specific, I'm always on SPTI.

ElbyCDIO is great for XP and avoiding the need for admin rights, but XP also went EOL a long time ago.

 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

×

Important Information

By using this site, you agree to our Terms of Use.