Forum Replies Created
-
Posts
-
Could you please send me the faulty CUE file by mail, or post it here? The parser for CUE files is now quite simple and may miss something.
Windows Vista indicates testsigning mode by /TESTSIGNING boot option. Win7 – just by TESTSIGNING (without slash). The original installer did not consider it.
WinCDEmu does not explicitly report its drives as CD or DVD. Maybe, your programs expect the virtual drives to handle some specific request codes? Which exact programs are confusing CD and DVD with WinCDEmu?
No, it is not possible. Full-featured local kernel debugging is impossible by definition: imagine what would happen, if a breakpoint inside a video or keyboard driver (or any other kernel component that makes any critical driver or service wait) is hit: kernel is halted until a debugger resumes it, and a debugger is halted until kernel processes your mouse or keyboard input…
Some limited local kernel debugging (no stepping, breakpoints, etc; basically, no code execution) is supported by WinDbg, but it is not very useful to debug drivers and not supported by VisualDDK.WinCDEmu has a universal 32-bit installer that automatically detects whether a 32-bit or a 64-bit system is running and installs the appropriate driver. Just use the default link (http://sourceforge.net/projects/wincdemu/files/wincdemu/WinCDEmu-2.3.exe).
Does the Device Manager display the device node for the new CDROM device? Maybe, the drive letter appears, but the window is not automatically opened due to disabled autorun?
You mean ‘is it compatible with PAE’? Not sure, did not test it. If you encounter any problems with PAE, just post description here…
Sorry, mistyped the link. Here is the correct one: http://wincdemu.sysprogs.org/win7fix/WinCDEmu-2.3-Win7.exe
Could you please try this version:
http://wincdemu.sysprogs.org/win7fix/WinCDEmu-2.3-Win7.exeCan you please open regedit.exe, go to HKEY_LOCAL_MACHINESystemCurrentControlSetControl, see the value of the “SystemStartOptions” parameter and post it here? Also, does the BCDEDIT report any error when you enable TESTSIGNING manually?
Yes, it supports Vista. You need to copy KDVM.DLL instead of KD1394.DLL and setup Vista to boot with 1394 debugging (bcdedit). Be sure to replace KD1394.DLL in DLLCACHE as well.
CPU usage while being paused happens only on multi-processor virtual machines and was not yet investigated properly. Maybe, it will be fixed in next versions.I have released version 2.3 with SysProgs.org signature. It should run normally with /TESTSINGING turned on (installer will do it automatically). Regarding the signature from Microsoft, I do not see any point in spending $500 per year (according to VeriSign price list) for a feature that can be achieved after a single bcdedit call.
Surely, same reason. WinCDEmu is not based on a complex virtual SCSI controller and returns STATUS_NOT_SUPPORTED for all SCSI-related requests. I suppose, it is quite a rare case from the filter developers’ point of view, and both filters completely do not expect such situation. WinCDEmu itself does not modify other driver’s code or data. That way, a situation when an unexpected set of valid parameters crashes such a filter, is a bug of this filter. You can try posting crash dumps to pxhelp20.sys driver developers, maybe this will help them pointing out the problem.
