Forum Replies Created
-
Posts
-
Ok, please try creating a BAT file containing the following 3 lines:
call C:WINDDK7600.16385.0binsetenv.bat C:WINDDK7600.16385.0 chk win7
cd /d c:UsersAdminDesktopDriverslegacyDrvlegacyDrv
buildLaunch the BAT file from Explorer. If that build succeeds, try launching the BAT file from “Visual Studio Command Prompt”. Maybe, there are some environment variable conflicts. If the BAT file fails, try to understand the difference with invoking “build” on its own (maybe, “cd” does not work?)
Please examine the entire output log (from the output window in VS) to understand why x64 build fails. You can also post the log here.
Regarding Virtual PC, you can use it, but the debugging will be extremely slow, as VirtualKD does not support Virtual PC. You can use either VMWare or VirtualBox instead.You did not enter the IP address of the virtual machine. To launch the driver, you should start the VisualDDK monitor on the virtual machine and specify its IP address in the launcher.
If you do not have the “root” prefix, you need some bus to provide a PDO node with the corresponding hardware ID (e.g. USB). Is the PDO node present in your case?
You don’t need to setup VirtualBox COM port. Instead, just run VMMON.EXE and let it run WinDbg for you. If this still does not work, try VirtualBox 3.0.x (or recompile VBoxDD.dll using latest VirtualBox headers). I’ll check the binary compatibility with 3.1 slightly later.
Ok, the “langfiles” is now removed.
Regarding most of the registry traces, it’s related to Windows architecture. Every time you connect a new device (e.g. a USB FLASH stick or a virtual CD-ROM), Windows creates an entry in the registry. This behavior is normal to Windows and should not create any problems to the user.
On the other hand, if you are continuously installing/uninstalling lots of programs (especially system ones) on the same PC, rather use some commercial “precise uninstaller”, or a VM with snapshots.The purpose of the uninstaller is to remove any components potentially using system resources (e.g. the driver) and the files occupying disk space. Forcing Vista/Win7 to purge device entries would be against its design. The registry keys describing the file extensions will be overwritten as soon as you install another image mounting tool (just reverting them to old values won’t be an option, as the user could remove the previously active tool before uninstalling WinCDEmu).
after the boot which isn’t officially requested but is needed
After the uninstaller has completed, no components are left in memory and no interference with other product installation can happen. Asking the user to restart just to have the last files removed “here and now” (provided that they do not interfere with anything) would be unreasonable.
Unfortunately, this is technically impossible. WinCDEmu includes a kernel driver for virtual CD bus. Without having the driver installed, no machine will be able to mount the images. Installing the driver every time for the image and uninstalling afterwards would cause ~30sec. delays for every image, that is not feasible.
—
UPD: Now possible. http://wincdemu.sysprogs.org/portableYou can see the function that calls CreateMainDriverInstance() and redefine it. The linker will ensure that the unused parts of BazisLib won’t get linked in.
STLPort containers are not thread-safe. Moreover, spin locks won’t do, as, by default, they use paged memory (as far as I remember). You need to use either fast mutexes, or define and use an STL allocator using non-paged memory.
