support

Forum Replies Created

Viewing 15 posts - 6,961 through 6,975 (of 7,058 total)
  • Author
    Posts
  • in reply to: x64 building and debugging w/ virtual PC #1253

    support
    Keymaster

    Ok. There is a bug in Project Wizard that does not flag x64 configurations as x64. On my machine it results in building x86 binaries even if x64 was selected. To fix this after the project file was generated, please go to “Project Properties -> NMake -> Build Command Line” and insert “AMD64” before “Win7”. This should fix the problem.

    in reply to: WinCDEmu not in context menu anymore #1227

    support
    Keymaster

    Could you please send the contents of your “WindowsMinidump” folder, so I can investigate the “power failure” bug?
    If ISO files do not open automatically, you can use the manual override:
    1. Click on an ISO file.
    2. Right-click and select “Open With->Select Default”
    3. Press “Browse”
    4. Select “Program Files (x86)WinCDEmuvmnt.exe” (or just Program Files… on 32-bit machine).
    5. Press OK and try again.

    in reply to: x64 building and debugging w/ virtual PC #1251

    support
    Keymaster

    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
    build

    Launch 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?)

    in reply to: x64 building and debugging w/ virtual PC #1249

    support
    Keymaster

    Please provide the full build log produced by Visual Studio (Output window)

    in reply to: x64 building and debugging w/ virtual PC #1246

    support
    Keymaster

    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.

    in reply to: VS2010 #1223

    support
    Keymaster

    Supported in VisualDDK 1.4

    in reply to: invalid launch parametr specifed… #1216

    support
    Keymaster

    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.


    support
    Keymaster

    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?

    in reply to: virtualkd, virtualbox 3.1 #1221

    support
    Keymaster

    No source changes required, you just need to recompile the DLL with the latest VirtualBox SDK.

    in reply to: virtualkd, virtualbox 3.1 #1219

    support
    Keymaster
    in reply to: Erro code 39 in Vista x64 #994

    support
    Keymaster

    Run command prompt as administrator and type “bcdedit /set testsigning off”

    in reply to: Settings for com port on virtualbox 3.1??? #1217

    support
    Keymaster

    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.

    in reply to: Bug: Wincdemu 3 incompatibility with ImgBurn #1206

    support
    Keymaster

    Try 3.1

    in reply to: The uninstaller/unloader leaves leftovers #1193

    support
    Keymaster

    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.

    in reply to: is WinCDEmu possible to be portable #1148

    support
    Keymaster

    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/portable

Viewing 15 posts - 6,961 through 6,975 (of 7,058 total)