Forum Replies Created
-
Posts
-
That’s strange. Normally, this error happens in one of 3 cases:
1. You’re trying to load a 32-bit driver on a 64-bit machine, or vice versa.
2. Your driver misses a signature (this shouldn’t matter if you have connected to the VM using WinDBG/VisualDDK). Anyway, you can make a free testsigning certificate (more info http://msdn.microsoft.com/en-us/library/windows/hardware/ff546236%28v=vs.85%29.aspx), but you’ll al need to enable testsigning mode (bcdedit /set testsigning on).
3. You have copied the driver file from an EFS-encrypted location (the ‘encrypted’ checkbox in file properties). Then, the SYS file in the DRIVERS directory will also be encrypted and the kernel won’t load it. This is very easy to check by right-clicking at the driver file, selecting properties and ensuring that encryption is off.Well, “yes and no”. Unfortunately, I don’t have much free time lately to implement some massive “nice to have” features. However, if you encounter a serious bug or have a suggestion that is relatively easy to add, I will probably find some time and make it 😉
Nevertheless, I have a long low-priority “wishlist” for features to add and will hopefully find time to do so, but I cannot promise doing it anytime soon.Please set HKCUSOFTWAREBazisSoftVisualDDKDDKDebuggerParametersDisableUpdateCheck to 1 (DWORD). However,this will disable the notifications when a new version is released.
It seems that some program keeps open handles to the drive. You can see which exact program it is by downloading Process Explorer from Microsoft and searching for handles to the drive letter.
Hi. FIrst of all, please use the latest version (3.6). If the problem persists, you’re welcome to post here.
