Forum Replies Created
-
Posts
-
No, I am not saying that. I can’t even remember what I was thinking when I said that. WinCDEmu is definitely easier. It needs some polish though.
It’s been a while since I used WinCDEemu, but I don’t think the problem is the device ID. (I haven’t checked, so I don’t know). In any event, the “eject” operation (I think) should simply unmount the current image from the current volume. The problem I think installers have is once they have initialized a volume (scanned for it to see if it’s there) and you go and remove it, the installer is not going to go to the trouble of re-scanning. It simply assumes (as would be normal) that you are using the same volume to install. There is no reason on earth that you would be switching volumes in the middle of an installation (at least in the normal way of doing things). Also, since many of the ISOs people run are older (since they backup easily), this kind of operation is expected from the installer. I would not mind donating a few bucks to see this implemented. I really like the simplicity this application provides, but in this one area, it is lacking.
I’m really wishing I had read through an entire C++ book right now. I’ll wait till you have the time. I’ll keep my eye on the forum. Happy travels, :).
When do you plan to have a new version out? I know you don’t have all the time in the world, but I’m just trying to plan things out since I administrate networks and this tool would actually be EXTREMELY useful. But, because of this drawback I am forced to use other tools that require installation because they tackle the problem in a somewhat cleaner fashion at the moment.
I am thinking of trying to develop something using the Alcohol 52% driver, but time is not something I really have right now. Alcohol handles this beautifully, but it’s not portable. I’m very surprised at the lack of support for portable mounting. Microsoft actually has an app that does this, but it doe snot support .mds format or those other exotic formats we all know and love.
