Forum Replies Created
-
Posts
-
Ok, the “langfiles” is now removed.
Regarding most of the registry traces, it’s related to Windows architecture. Every time you connect a new device (e.g. a USB FLASH stick or a virtual CD-ROM), Windows creates an entry in the registry. This behavior is normal to Windows and should not create any problems to the user.
On the other hand, if you are continuously installing/uninstalling lots of programs (especially system ones) on the same PC, rather use some commercial “precise uninstaller”, or a VM with snapshots.The purpose of the uninstaller is to remove any components potentially using system resources (e.g. the driver) and the files occupying disk space. Forcing Vista/Win7 to purge device entries would be against its design. The registry keys describing the file extensions will be overwritten as soon as you install another image mounting tool (just reverting them to old values won’t be an option, as the user could remove the previously active tool before uninstalling WinCDEmu).
after the boot which isn’t officially requested but is needed
After the uninstaller has completed, no components are left in memory and no interference with other product installation can happen. Asking the user to restart just to have the last files removed “here and now” (provided that they do not interfere with anything) would be unreasonable.
Unfortunately, this is technically impossible. WinCDEmu includes a kernel driver for virtual CD bus. Without having the driver installed, no machine will be able to mount the images. Installing the driver every time for the image and uninstalling afterwards would cause ~30sec. delays for every image, that is not feasible.
—
UPD: Now possible. http://wincdemu.sysprogs.org/portableYou can see the function that calls CreateMainDriverInstance() and redefine it. The linker will ensure that the unused parts of BazisLib won’t get linked in.
STLPort containers are not thread-safe. Moreover, spin locks won’t do, as, by default, they use paged memory (as far as I remember). You need to use either fast mutexes, or define and use an STL allocator using non-paged memory.Seems that IMGBURN sends a non-standard request to WinCDEmu and it responds with “incorrect request” reply. I’ll have a look later.
It’s hard to tell, what the problem is, not having the Saturn Emulator and its sources (and the time to analyze it). I guess, it sends some unusual SCSI codes that WinCDEmu fails to handle. Or this can be related to some copy protection mechanisms. Basically, WinCDEmu is a tool for mounting CD/DVD images with PC data, so, strictly speaking, using it with a specific Sega emulator is out of its main functionality. If you have free time (and some basic Windows Kernel knowledge), I can suggest what to look at in the debugger to determine, what does the Saturn Emulator want.
Audio CD images are not supported by WinCDEmu. My personal opinion is that storing audio CDs in ISO format is inefficient, as you cannot index separate songs, waste twice more space (compared to lossless APE format, if you are picky about quality) or 10x more if you accept MP3s with a reasonable bitrate, and have to mess with drive letters every time. Moreover, technically, emulating audio CDs is a non-trivial task (would take even more time than adding support for data NRG/MDS/CCD). So, if anyone submits a patch supporting audio CDs, I won’t mind including it, but I won’t develop such feature myself, as there is an easier and more smooth solution.
I recommend checking out various Audio CD ripping tools instead.I just created 2 network adapters: 1 NAT adapter to have Internet on VM, and 1 host-only adapter to access VM from host. A bit messy, but fast and easy.
Most likely, you are trying to mount an encrypted MDS image. Unfortunately, WinCDEmu cannot mount encrypted images, as the encryption algorithm is unknown. The only thing I can suggest is to avoid creating encrypted Alcohol images, as they cannot be mounted by any other tools.
Please look, what symbols are reported missing by linker, find a LIB file containing them and add them to VS project manually. That should help.
Admin account is required to perform such low-level system actions, as adding new virtual devices. Maybe, this restriction will be relaxed in further versions.
