Forum Replies Created
-
Posts
-
Please examine the build log to ensure that you build the 64-bit version of the driver.
You might also need to enable testsigning mode on the VM.Fixed. Please download latest VisualDDK, use the driver project wizard and select “get additional templates”. It will download BazisLib and use the fixed RAMDISK temlpate.
Hi, all.
Starting from VisualDDK 1.5.2/BazisLib 2.5.2 the BazisLib project templates have been integrated into VisualDDK project Wizard and will work for Visual Studio 2005, 2008 and 2010.Fixed. Please use the following link:
http://sourceforge.net/projects/wincdemu/files/wincdemu/3.4/PortableWinCDEmu-3.4.exe/downloadHi, please don’t create multiple topics regarding the same problem. Check the default BazisLib::DDK::File flags.
This is something really strange. WinCDEmu does not do anything with WinZip. What do you mean by “Screen showed a dialogue box from WinCdEmu”? Could you please explain step-by-step what are you doing, what are you expecting, and what actually happens instead?
Did you use BazisLib installer? It should add the paths to Visual Studio settings automatically (after you restart Visual Studio, of course). If this does not help, simply go to Project Settings, Select Compiler -> Additional Include Paths and enter the BazisLib path and WTL path (BazisLib installer downloads and installs WTL).
Please ensure you are using the latest version of BazisLib. The problem was related to the default file opening flags.
Normally no, but you can easily build a version that can:
Simply download the sources, open batchmnt.cpp file, and replace this line:VirtualCDClient clt(&status);with this:
VirtualCDClient clt(&status, true);Then, build the batchmnt.exe project. The change will make batchmnt use the portable driver instead of the main driver.
Note that any version of Visual Studio (including the free Express version) will do, as you don’t have to change any kernel-mode stuff.Actively – no. But if you have a bug, that is consistently reproducing itself, please write a detailed description and I will fix it.
It seems like some antiviruses simply mark all UPX-compressed executables as suspicious.
I have done an experiment: compressed notepad.exe using UPX. According to VirusTotal, 7 of 42 antivirus programs treat this program as suspicious (http://www.virustotal.com/file-scan/report.html?id=8ecdc24105027e26069060173936d7202fd60bdab3eb62ca71af18730892566c-1288962310). Moreover, the unpacked Portable WinCDEmu triggers no antiviruses.What do you mean by “does not unmount”? What exactly happens?
My bet is that your player “forgets” to close some of the files on the image, so, closing the player before unmounting the image should help.It seems to me that modern antiviruses get closer and closer to the approach “every program that does not have a certificate bought from me is a virus”.
Are you using Portable WinCDEmu, or the normal WinCDEmu? Can you also tell when exactly does F-Secure pop up the alert and what is the exact error message text, so I could look it up in google?
