Forum Replies Created
-
Posts
-
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.
The GUI will still be simple and will not cancel the simplicity of single-click mounting. You’ll be able to choose whether to prompt for a drive letter on each mounting, or use the default one.
As for signed drivers, next version will be signed by sysprogs.org certificate available for installing, that will allow running drivers on Vista/Win7 x64 in ‘driver test mode’ (Bcdedit.exe -set TESTSIGNING ON). Normal signing costs 500$ per year and, thus, is not a point for free software.When WinCDEmu is first installed, it sets up the driver for the virtual disk bus. As no virtual drives are present at that moment, the driver is not installed. This will maybe[/i/ be fixed in further versions by flushing an empty virtual drive during installation and updating the drivers.
Drive letter selection is a little bit tricky, however, I have an idea to implement something similar in the next version. However, note that the driver letter cannot be reserved while virtual CD is not active (if you insert a USB FLASH disk, it can still ocupy the letter), however, it will be possible to assign a given letter to a newly mounted image, instead of default one.As the crash is inside Cdr4_2K.SYS, most likely, it is a bug in this driver. For example, it can expect a full SCSI device behind the virtual drive and fail, when it cannot find such device.
Sorry, but it is almost impossible to pinpoint the problem without having debug information for Cdr4_2K.sys. You can try sending a minidump to the authors of this driver; maybe they’ll release a patch.Maybe, your browser took the unknown .sys file as a text file and corrupt it. Try the following link: http://wincdemu.sysprogs.org/win2kfix/BazisVirtualCD.zip
Yes, bcdedit testsigning on will help after I release a new version with SysProgs.org signature.
Could you please try the following driver on Win2K: http://wincdemu.sysprogs.org/win2kfix/BazisVirtualCD.sys
If it works for you, I’ll include the Win2K build in the next release.I did not test it on Windows 2000, however, I suppose, that the problem is due to some of API functions not supported by Windows 2000. Could you please perform a simple test?:
1. Try forcibly loading VirtDiskBus driver (net start VirtDiskBus from command line).
2. If the driver loads successfully, skip the next step.
3. Download Dependency Walker from http://www.dependencywalker.com/%5D and open VirtDiskBus.sys with it. Observe, which functions are not provided by Windows 2000 kernel and post them here.
4. Repeat steps 1-3 for BazisVirtualCD driver.
As soon as you provide enough information to pinpoint the problem, I’ll be able to release an update (if it is not related to some key functionality not supported by Win2K).
P.S. Regarding the digital signatures and x64, I’ll soon release an update based on Authenticode technology, that will allow running WinCDEmu on such machines after importing SysProgs.org certificate and enabling “driver test mode” via bcdedit. See the http://wincdemu.sysprogs.org page in one-two weeks.Could you please test whether VisualDDK wizard handles DDK2600 correctly, if you create an empty ntstrsafe.lib file in LIB directory?
Before creating a project, VisualDDK wizard searches for several header and library files in the DDK directory to detect correct include & lib paths for the project. You can see the search sequence in detail in the ProjectSettingsForm.cs file.
Basically, the following files are searched: ntddk.h, ntdef.h, wdm.h, excpt.h, guiddef.h, ntoskrnl.lib, hal.lib, int64.lib, ntstrsafe.lib, exsup.lib, amd64ntoskrnl.lib, amd64hal.lib, amd64ntstrsafe.lib. Could you please specify the paths for the files mentioned above on your system, so I can see, why VisualDDK does not find them.
It is very strange, that the wizard fails after successfully locating ntddk.h. Maybe, filemon shows failed attempt of locating other files (ntdef.h/etc)?
Additionally, you can recompile the DDKProjectWizard.sln solution and run the DDKProjectWizard2005 project (select devenv.exe as running executable). After setting breakpoint on TryCreateLocationInfoObject() method, you can see why exactly header search fails. Note that CreateLocationInfoObjects() calls this method four times for four different OSes (WLH/WXP/WNET/W2K), so, it is normally for some of them to fail, as not every DDK contains all four of them.
