Forum Replies Created
-
Posts
-
What is the image file name for Amiga? The CUE references “Impossible Mission 2025 – The Special Edition (1994)(MicroProse)(M4)(Track 1 of 9)[!].iso”. If the actual image has a different extension (e.g. IMG) or name, WinCDEmu won’t find it.
Hi,
try opening the CUE files in Notepad and deleting the first line (CATALOG xxxxx). This should make them mountable with WinCDEmu.
If this helps, I’ll update the next version, so that it will ignore the CATALOG line.Hi,
could you quiclky attach the CUE file and tell me the name of the BIN file? I think, I know where the problem could be.
Regarding the installation path, not planning now, but to be on the safe side, you can define an environment variable (e.g. BATCHMNT) pointing to batchmnt.exe and use it in your scripts (%BATCHMNT% xxx.iso).
P.S. Do not forget to use “/wait” in batchmnt, so that it waits until the drive is actually mounted and recognized by Windows.Try asking on nLite forums about how to prevent the installation from crashing when multiple textmode drivers are slipstreamed.
In fact, I am slowly writing a quickstart for complete beginners. Currently you can check out the old VisualDDK guide: http://visualddk.sysprogs.org/quickstart/
Hi, could you please replace the WinCDEmuContextMenu.dll with a debug version, wait until Total Commander crashes, and create a crash dump by opening task manager (press Ctrl+Shift+Esc), going to Processes, finding “totalcmd.exe” there, right-clicking and selecting “Create dump”?
You can attach the crash dump to a post on this forum or send it to support sysprogs org.Please go to “debug->exceptions” window in Visual Studio and enable breaking when System.IO.FileLoadException/System.IO.FileNotFoundException are thrown. Then you will be able to see which file is missing. Note that you will probably need to get the mscorlib sources from Microsoft (if you are using Visual Studio 2008 SP1 or later Visual Studio will do it automatically).
Well, no matter if you call it hacking or not, as soon as the disc producing companies find out about a new tool bypassing their protection, they would definitely try to sue the tool author. So, unless I have good lawyers on my side, I won’t risk it. And I don’t want to make WinCDEmu ‘yet another’ commercial emulator just to be able to afford those lawyers, as the primary goal of the project is to provide a free open-source tool for lawsuit-free scenarios.
Besides, if you don’t want to use the copy protection emulators, you can ask google about how to start your game without using them. However, please do not post any illegal instructions on this forum.
Hi. In fact, you don’t need any new driver for that. Just use nLite to integrate Intel AHCI drivers into a WinXP installation disc. The actual driver will be chosen by the system automatically.
VirtualBox is waiting for you to connect a debugger. Start VM monitor (vmmon/vmmon64) and select “run debugger”. Or use VisualDDK to debug directly from Visual Studio.
WinCDEmu installs custom drivers, so the user must be there to say “yes, I really want to install the driver without the WHQL signature from Microsoft”. There can be 2 solutions:
1. If you’re installing WinCDEmu on your company’s computers using unattended mode, allow installing non-signed drivers (it’s different from binary signing) in the group policy.
2. Pay Microsoft and get a WHQL signature for WinCDEmu binaries. However, this would cost…
As for the unattended uninstall, I’ve added it to the feature list for the next version, but I cannot promise any release date soon.OK. The point about the “protection decoders” is that unless you are a company with a legal department ready to defend you in court, you don’t mess with them.
So, keeping WinCDEmu free and open-source tool means no “protection hacking” tricks.BTW, the forgotten context menu on uninstall was fixed in version 3.5. Now the menu entry will disappear in a short time after uninstallation (when Explorer unloads unused modules) or after a restart.
Currently, BluRay discs are not supported, but it’s planned in the next release.
Update: try WinCDEmu 3.6 beta 1. It has an experimental support for Blu-Ray disc imaegs.OK. The portable WinCDEmu always uses its own driver and does not know anything about the “normal WinCDEmu driver”. I don’t see any reason to use portable WinCDEmu GUI while having the normal WinCDEmu installed.
As for the driver, the ‘uninstall’ button just removed the portable driver, making the PortableWinCDEmu GUI useless. Normally, it should reinstall the driver next time it is started. If this does not happen, remove the BazisPortableCDBus service manually and re-run the portable GUI. The normal WinCDEmu GUI should not interfere with the portable driver as well.
