[danielkza]

I personally don’t think this would be a good idea. There are plenty of feature rich, well tested, burning programs out there. Adding create/burn support would probably double (wild guess) WinCDEmu’s code base, and go against the very goal of it (be a dead simple ISO mounter).

My suggestion: use ImgBurn in addition to WinCDEmu.

[danielkza]

I think you could probably work around this.

1) Replace the file association with one running a custom script that would save the mounted ISO to the registry, and call the original executable afterwards.
2) Run another script on logon that loads the previously saved ISO list.

In fact, it would be better if it was included in WinCDEmu itself: I’ll what I can do about it (isn’t free software great?) soon.

[danielkza]

I was not able to reproduce the issue in Windows 7 x64 RTM: I copied the exact same file to my hard drive successfully. I can test it in Vista SP2 x86 later if it would help.

BTW, WinCDEmu rocks, I can finally ditch Daemon Tools xD.

[Author]

Posts