Difference between revisions of "Virtual Drives"

From RocketLauncher Wiki
Jump to navigation Jump to search
(Created page with "=Information= RocketLauncher supports all the popular '''CLI-supported''' virtual drive applications out there for windows. It is your choice to use what you want, but be care...")
 
 
(18 intermediate revisions by the same user not shown)
Line 4: Line 4:
  
 
=Supported Virtual Drive Applications=
 
=Supported Virtual Drive Applications=
 +
==Alcohol==
 +
:'''Supported Extensions:'''
 +
::b5t,b6t,bin,bwt,ccd,cdi,cue,iso,isz,mds,mdx,nrg,pdi
 +
:'''Installation Notes:'''
 +
:#Needs to be a registered copy otherwise you will get a nag screen on each use
 +
:#When installing, leave checkbox enabled "Add Alcohol Virtual Drive at first run"
 +
:#Start Alcohol and goto View -> Options -> General. Uncheck all the options there.
 +
:#In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to AxCmd.exe
 +
:#In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Drive Letter to match your virtual drive letter.
 +
==Daemon Tools 4==
 +
:'''Supported Extensions:'''
 +
::ape,b5t,b6t,bin,bwt,ccd,cdi,cue,flac,iso,isz,mds,mdx,nrg
 +
:'''Installation Notes:'''
 +
:#If running Windows 10, do NOT use a scsi drive as there are no drivers for scsi in Windows 10. Only use a DT drive. [http://www.rlauncher.com/forum/showthread.php?1602-Virtual-Drives-not-loading-images-anymore&p=14775&viewfull=1#post14775]
 +
 +
==Daemon Tools 4 Ultra==
 +
:'''Supported Extensions:'''
 +
::ape,b5t,b6t,bin,bwt,ccd,cdi,cue,flac,iso,isz,mds,mdx,nrg
 +
:'''Installation Notes:'''
 +
:#This version switches to Daemon Tools 5 mode if used. The CLI commands are the same and there is no support for -get_letter like in DT5.
 +
 +
==Daemon Tools 5==
 +
:'''Supported Extensions:'''
 +
::ape,b5t,b6t,bin,bwt,ccd,cdi,cue,flac,iso,isz,mds,mdx,nrg
 +
:'''Installation Notes:'''
 +
:#Have only tested the Lite version
 +
:#When installing, click the "Proceed with free licenese" blue link to install, not the Personal License or Commercial License options.
 +
:#Be sure to cancel all external components that try to install alongside DT.
 +
:#It's a good idea to disable checking for updates and sending anonymous statistics in DT's options.
 +
:#In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to DTLite.exe
 +
:#In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Drive Letter to match your virtual drive letter.
 +
:#I've found DT5 can be a little slow unmounting images, causing RL to get hung up for a few extra seconds waiting for the DTLite.exe to close.
 +
 +
==Daemon Tools 6 Pro==
 +
:'''Supported Extensions:'''
 +
::ape,b5t,b6t,bwt,ccd,cdi,cue,flac,iscsi,iso,isz,mds,mdx,nrg,tc,vdh,vdi,vmdk,wav,zip
 +
:'''Installation Notes:'''
 +
:#Must point your Virtual Drive Path to DTAgent.exe as this is the executable that supports CLI used by RocketLauncher.
 +
:#This is only for the Pro version
 +
:#Supports Windows 10
 +
:#In RLUI General Settings -> Third Party -> Virtual Drive -> Drive Letter, set this to 0, not a drive letter. 0 represents the first virtual drive in Daemon Tools.
 +
 +
==Daemon Tools Lite 10==
 +
:'''Supported Extensions:'''
 +
::ape,b5t,b6t,bwt,ccd,cdi,cue,flac,iscsi,iso,isz,mds,mdx,nrg,tc,vdh,vdi,vmdk,wav,zip
 +
:'''Installation Notes:'''
 +
:#Must point your Virtual Drive Path to DTAgent.exe as this is the executable that supports CLI used by RocketLauncher.
 +
:#This is only for the Lite version
 +
:#If your Lite version expires, you will get a 30-second delay when mounting your images. RocketLauncher will not be aware of this and only report this 30 seconds in your log. Nothing you can do about this other than purchase DT.
 +
:#Windows 10 Users:
 +
::#Supports Windows 10 - Windows 10 users may want to use this as the driver required to run a virtual scsi drive will install fine.
 +
::#If you have a problem with the SPDT driver, like it cannot load or install successfully, try this:
 +
:::*There is an SPDT registry key in HKLM\system\currentcontrolset\services\sptd that is preventing the new updated win 10 sptd driver from installing. Since it exists in the registry and pointing to the old sptd.sys driver that doesn't work with win 10, there is a permissions issue on that registry key and subkey/values.
 +
:::*Right click the sptd registry key and in permissions, take ownership. It is very important you also check the box to replace all child object permissions.
 +
:::*After this, go ahead and rename the sptd key to something like sptd_old, and delete or rename sptd.sys in the system32\drivers folder.
 +
:::*Now run the sptd installer that is in the DTLite install folder called SPTDinst-x64.exe. It should succeed without error. Reboot and you should be good to go!
 +
:::*NOTE: You can find out if the sptd driver is actually loaded or not by getting some out put from this cmd.exe command:
 +
driver query /V |find "sptd"
 +
 +
==Daemon Tools Lite 10.4==
 +
:'''Supported Extensions:'''
 +
::ape,b5t,b6t,bwt,ccd,cdi,cue,flac,iscsi,iso,isz,mds,mdx,nrg,tc,vdh,vdi,vmdk,wav,zip
 +
:'''Installation Notes:'''
 +
:#See [http://www.rlauncher.com/wiki/index.php?title=Virtual_Drives#Daemon_Tools_Lite_10 Daemon Tools Lite 10] above as all those notes apply to this version as well.
 +
:#This version slightly changes the CLI sent to mount and unmount and changes to support this version were made on Virtual Drive.ahk v1.0.6.
 +
 +
==MagicISO (MagicDisc)==
 +
:'''Supported Extensions:'''
 +
::000,bin,bwi,bwt,c2d,ccd,cdi,cif,dao,ima,img,iso,md1,mdf,mds,nrg,p01,pdi,tao,uif,vaporcd,vc4,vcd,vdi,xa
 +
:'''Installation Notes:'''
 +
:#Could not get this to work in Windows 8.1. It might only support up to Windows 8.
 +
:#In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to miso.exe.
 +
 
==PowerISO==
 
==PowerISO==
 
:'''Supported Extensions:'''
 
:'''Supported Extensions:'''
Line 11: Line 84:
 
:#In PowerISO, goto Options -> Configuration. Then click the Virtual Drive tab. Set number of virtual drives to 1.
 
:#In PowerISO, goto Options -> Configuration. Then click the Virtual Drive tab. Set number of virtual drives to 1.
 
:#For your 1 virtual drive in the same window above, click Drive 0 in the letter assignment box and give it your preferred drive letter. It is safe to close PowerISO now.
 
:#For your 1 virtual drive in the same window above, click Drive 0 in the letter assignment box and give it your preferred drive letter. It is safe to close PowerISO now.
:#In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to piso.exe, not PowerISO.exe. (piso.exe is the CLI application)
+
:#In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to piso.exe, not PowerISO.exe. (piso.exe is the CLI application)
 
:#In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Drive Letter to match what you set your virtual drive letter to above.
 
:#In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Drive Letter to match what you set your virtual drive letter to above.
 
==Virtual CD==
 
==Virtual CD==
 
:'''Supported Extensions:'''
 
:'''Supported Extensions:'''
 
::b5i,bin,bwi,c2d,img,iso,mdf,nrg,vc4,xmf
 
::b5i,bin,bwi,c2d,img,iso,mdf,nrg,vc4,xmf
==Alcohol==
+
:'''Installation Notes:'''
:'''Supported Extensions:'''
+
:#During installation, you may want to select the customize option and uncheck many of the additional Programs it tries to install. They are not bad, but unnecessary for simple mounting and unmounting.
::b5t,b6t,bwt,ccd,cdi,cue,iso,isz,mds,mdx,nrg,pdi
+
:#In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to vc10cmd.exe.
==Daemon Tools 4==
 
:'''Supported Extensions:'''
 
::ape,b5t,b6t,bwt,ccd,cdi,cue,flac,iso,isz,mds,mdx,nrg
 
==Daemon Tools 5==
 
:'''Supported Extensions:'''
 
::ape,b5t,b6t,bwt,ccd,cdi,cue,flac,iso,isz,mds,mdx,nrg
 
==MagicISO (MagicDisc)==
 
:'''Supported Extensions:'''
 
::000,bin,bwi,bwt,c2d,ccd,cdi,cif,dao,ima,img,iso,md1,mdf,mds,nrg,p01,pdi,tao,uif,vaporcd,vc4,vcd,vdi,xa
 
 
==Virtual CloneDrive==
 
==Virtual CloneDrive==
 
:'''Supported Extensions:'''
 
:'''Supported Extensions:'''
 
::bin,ccd,cdi,dvd,img,iso,udf
 
::bin,ccd,cdi,dvd,img,iso,udf
 +
:'''Installation Notes:'''
 +
:#In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to VCDMount.exe
 +
:#Manually run VCDPrefs.exe first so the registry keys are created for you. RocketLauncher will do this for you if you forget, but don't rely on it.
  
 
=Unsupported Virtual Drive Applications=
 
=Unsupported Virtual Drive Applications=
==Daemon Tools 10==
 
:'''Reason:'''
 
::There does not appear to be support for mounting and unmounting an image via CLI
 
 
==UltraISO==
 
==UltraISO==
 
:'''Reason:'''
 
:'''Reason:'''
 
::There does not appear to be support for mounting and unmounting an image via CLI. The only thing that exists is to build an iso through CLI, not simple mounting and unmounting
 
::There does not appear to be support for mounting and unmounting an image via CLI. The only thing that exists is to build an iso through CLI, not simple mounting and unmounting

Latest revision as of 23:07, 21 August 2016

Information

RocketLauncher supports all the popular CLI-supported virtual drive applications out there for windows. It is your choice to use what you want, but be careful to pick one that can mount the image extension types you use. Some do not support cue and that is usually a requirement in this hobby as many sets use them.

Supported Virtual Drive Applications

Alcohol

Supported Extensions:
b5t,b6t,bin,bwt,ccd,cdi,cue,iso,isz,mds,mdx,nrg,pdi
Installation Notes:
  1. Needs to be a registered copy otherwise you will get a nag screen on each use
  2. When installing, leave checkbox enabled "Add Alcohol Virtual Drive at first run"
  3. Start Alcohol and goto View -> Options -> General. Uncheck all the options there.
  4. In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to AxCmd.exe
  5. In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Drive Letter to match your virtual drive letter.

Daemon Tools 4

Supported Extensions:
ape,b5t,b6t,bin,bwt,ccd,cdi,cue,flac,iso,isz,mds,mdx,nrg
Installation Notes:
  1. If running Windows 10, do NOT use a scsi drive as there are no drivers for scsi in Windows 10. Only use a DT drive. [1]

Daemon Tools 4 Ultra

Supported Extensions:
ape,b5t,b6t,bin,bwt,ccd,cdi,cue,flac,iso,isz,mds,mdx,nrg
Installation Notes:
  1. This version switches to Daemon Tools 5 mode if used. The CLI commands are the same and there is no support for -get_letter like in DT5.

Daemon Tools 5

Supported Extensions:
ape,b5t,b6t,bin,bwt,ccd,cdi,cue,flac,iso,isz,mds,mdx,nrg
Installation Notes:
  1. Have only tested the Lite version
  2. When installing, click the "Proceed with free licenese" blue link to install, not the Personal License or Commercial License options.
  3. Be sure to cancel all external components that try to install alongside DT.
  4. It's a good idea to disable checking for updates and sending anonymous statistics in DT's options.
  5. In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to DTLite.exe
  6. In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Drive Letter to match your virtual drive letter.
  7. I've found DT5 can be a little slow unmounting images, causing RL to get hung up for a few extra seconds waiting for the DTLite.exe to close.

Daemon Tools 6 Pro

Supported Extensions:
ape,b5t,b6t,bwt,ccd,cdi,cue,flac,iscsi,iso,isz,mds,mdx,nrg,tc,vdh,vdi,vmdk,wav,zip
Installation Notes:
  1. Must point your Virtual Drive Path to DTAgent.exe as this is the executable that supports CLI used by RocketLauncher.
  2. This is only for the Pro version
  3. Supports Windows 10
  4. In RLUI General Settings -> Third Party -> Virtual Drive -> Drive Letter, set this to 0, not a drive letter. 0 represents the first virtual drive in Daemon Tools.

Daemon Tools Lite 10

Supported Extensions:
ape,b5t,b6t,bwt,ccd,cdi,cue,flac,iscsi,iso,isz,mds,mdx,nrg,tc,vdh,vdi,vmdk,wav,zip
Installation Notes:
  1. Must point your Virtual Drive Path to DTAgent.exe as this is the executable that supports CLI used by RocketLauncher.
  2. This is only for the Lite version
  3. If your Lite version expires, you will get a 30-second delay when mounting your images. RocketLauncher will not be aware of this and only report this 30 seconds in your log. Nothing you can do about this other than purchase DT.
  4. Windows 10 Users:
  1. Supports Windows 10 - Windows 10 users may want to use this as the driver required to run a virtual scsi drive will install fine.
  2. If you have a problem with the SPDT driver, like it cannot load or install successfully, try this:
  • There is an SPDT registry key in HKLM\system\currentcontrolset\services\sptd that is preventing the new updated win 10 sptd driver from installing. Since it exists in the registry and pointing to the old sptd.sys driver that doesn't work with win 10, there is a permissions issue on that registry key and subkey/values.
  • Right click the sptd registry key and in permissions, take ownership. It is very important you also check the box to replace all child object permissions.
  • After this, go ahead and rename the sptd key to something like sptd_old, and delete or rename sptd.sys in the system32\drivers folder.
  • Now run the sptd installer that is in the DTLite install folder called SPTDinst-x64.exe. It should succeed without error. Reboot and you should be good to go!
  • NOTE: You can find out if the sptd driver is actually loaded or not by getting some out put from this cmd.exe command:
driver query /V |find "sptd"

Daemon Tools Lite 10.4

Supported Extensions:
ape,b5t,b6t,bwt,ccd,cdi,cue,flac,iscsi,iso,isz,mds,mdx,nrg,tc,vdh,vdi,vmdk,wav,zip
Installation Notes:
  1. See Daemon Tools Lite 10 above as all those notes apply to this version as well.
  2. This version slightly changes the CLI sent to mount and unmount and changes to support this version were made on Virtual Drive.ahk v1.0.6.

MagicISO (MagicDisc)

Supported Extensions:
000,bin,bwi,bwt,c2d,ccd,cdi,cif,dao,ima,img,iso,md1,mdf,mds,nrg,p01,pdi,tao,uif,vaporcd,vc4,vcd,vdi,xa
Installation Notes:
  1. Could not get this to work in Windows 8.1. It might only support up to Windows 8.
  2. In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to miso.exe.

PowerISO

Supported Extensions:
ashdisc,b5i,bin,bwi,c2d,cdi,cif,cue,daa,fcd,gi,img,iso,lcd,mdf,mds,ncd,nrg,p01,pdi,pxi,vcd
Installation Notes:
  1. Computer needs to be restarted after installing PowerISO
  2. In PowerISO, goto Options -> Configuration. Then click the Virtual Drive tab. Set number of virtual drives to 1.
  3. For your 1 virtual drive in the same window above, click Drive 0 in the letter assignment box and give it your preferred drive letter. It is safe to close PowerISO now.
  4. In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to piso.exe, not PowerISO.exe. (piso.exe is the CLI application)
  5. In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Drive Letter to match what you set your virtual drive letter to above.

Virtual CD

Supported Extensions:
b5i,bin,bwi,c2d,img,iso,mdf,nrg,vc4,xmf
Installation Notes:
  1. During installation, you may want to select the customize option and uncheck many of the additional Programs it tries to install. They are not bad, but unnecessary for simple mounting and unmounting.
  2. In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to vc10cmd.exe.

Virtual CloneDrive

Supported Extensions:
bin,ccd,cdi,dvd,img,iso,udf
Installation Notes:
  1. In RocketLauncherUI, set General Settings -> Third Party -> Virtual Drive Path to point to VCDMount.exe
  2. Manually run VCDPrefs.exe first so the registry keys are created for you. RocketLauncher will do this for you if you forget, but don't rely on it.

Unsupported Virtual Drive Applications

UltraISO

Reason:
There does not appear to be support for mounting and unmounting an image via CLI. The only thing that exists is to build an iso through CLI, not simple mounting and unmounting