I believe the issue may be related to a change they made to DTLite for Windows 10 where it automatically deletes the device when you eject an image. This is something new in the Windows 10 version, previously DTLite operated like DTPro in that you could do this with the basic program.ģ. Advanced mounting is a DT Lite option which allows you to specify mounting points and device names. I still have DTPRo installed in another machine, and can run diagnostics from there.Ģ. Plus, I have yet to set up the other CDROM system emulators, and I can easily see this happening again with a different emulator.ġ. Reverting to an older version of Daemon Tools is not a possibility, as Windows 10 blocks the installation as incompatible (and overriding this bricks your installation, as I found out).Ĭan we please get DTPro to be recognized by Hyperlaunch? It seems like it might be a pain in the rear to support DTLite, would require passing the bus ID and drive ID of the newly mounted image to the fusion.ini file. Unfortunately, whenever you do a mount operation in Daemon Tools Lite (as Rocketlauncher must do), the device name changes, so Fusion never sees the correct CDROM drive. Fusion unfortunately saves the device name (and bus identification) in the configuration file as the CDROM drive.
Rocketlauncher works with this, HOWEVER, DTLite insists on spinning a random device name each time you mount an image. I then uninstalled it, and purchase Daemon Tools Lite (5.), with the Advanced Mounting feature. This is strange, seeing as how Hyperlaunch 3.X would happily mount images by pointing it to the same DTAgent.exe file. However, Rocketlauncher complains that it isn't compatible and won't mount the images. I had Daemon Tools Pro (7.) installed, to mount SegaCD images. Hyperlaunch 3 was having fits (hanging up the 2nd time I would launch an emulator), so I decided to move to RocketLauncher. Building up a new machine for the arcade cabinet.
0 kommentar(er)
