Anonymous

Forum Replies Created

Viewing 15 posts - 391 through 405 (of 665 total)
  • Author
    Posts
  • in reply to: VirtualBox running Win7 won’t start #1531
    Anonymous
    Participant

    Thanks a lot, i’m confused in a manual. 😥

    in reply to: VirtualBox running Win7 won’t start #1525
    Anonymous
    Participant

    I have attached to vbox process and looked for loaded modules

    ….

    VBoxC.dll C:Program FilesOracleVirtualBoxVBoxC.dll N/A N/A Symbols not loaded. 61 4.1.0.73009 19.07.2011 14:08 0000000003DD0000-0000000003FF6000* [11292] VirtualBox.exe: Native
    VBoxDD.dll C:Program FilesOracleVirtualBoxVBoxDD.dll N/A N/A Symbols not loaded. 89 19.07.2011 14:08 000000000B7D0000-000000000BA39000* [11292] VirtualBox.exe: Native
    VBoxDD2.dll C:Program FilesOracleVirtualBoxVBoxDD2.dll N/A N/A Symbols not loaded. 91 19.07.2011 14:08 000000000BA90000-000000000BABD000* [11292] VirtualBox.exe: Native
    VBoxDDU.dll C:Program FilesOracleVirtualBoxVBoxDDU.dll N/A N/A Symbols not loaded. 90 19.07.2011 14:08 000000000BA40000-000000000BA90000* [11292] VirtualBox.exe: Native
    ….

    As you can see, no VBoxDD.dll loaded, but I placed DLL to C:Program FilesOracleVirtualBoxVBoxDD0.dll from C:UsersrootDownloadsvirtualkd 2.5.4VirtualKD-2.5.4VirtualBoxx64VBoxDD.dll
    Md5 1A30E26B4FE413B196B4897169B46147 VBoxDD0.dll

    in reply to: VirtualBox running Win7 won’t start #1526
    Anonymous
    Participant

    @bazis wrote:

    Please uninstall VirtualBox, remove all contents of OracleVirtualBox folder in Program Files, reinstall it and use the VBoxDD.dll from VirtualKD 2.5.4. It supports VirtualBox 4.1

    Thanks for reply, but this case does not helps 🙁

    VirtualBox: 4.1.0
    Guest OS: Windows 7 Ulyimate 32 bit, build 7601, service pack 1 (Debug)
    Host OS: Windows 7 64 bit Home Ex, build 7601, service pack 1
    Virtual KD: 2.5.4
    WDK & debug tools: 7600.16385.1

    in reply to: VirtualBox running Win7 won’t start #1528
    Anonymous
    Participant

    @scorpion wrote:

    Does any one has virtualKD x64 for VirtualBox 4.1? I have recompiled manually with VBOX 4.1 headers, but I still have error message

    VirtualKD

    VirtualKD cannot patch VirtualBox on-the-fly.

    Please, shut down all your VMs, rename VBoxDD.dll
    to VBoxDD0.dll and copy VBoxDD.dll from VirtualKD
    package to VirtualBox directory.

    ОК

    Also after installing vminstall in guest OS Win7 32bit, VM has crashes at boot time

    in reply to: VirtualBox running Win7 won’t start #1527
    Anonymous
    Participant

    Does any one has virtualKD x64 for VirtualBox 4.1? I have recompiled manually with VBOX 4.1 headers, but I still have error message

    VirtualKD

    VirtualKD cannot patch VirtualBox on-the-fly.

    Please, shut down all your VMs, rename VBoxDD.dll
    to VBoxDD0.dll and copy VBoxDD.dll from VirtualKD
    package to VirtualBox directory.

    ОК

    in reply to: WINCDEMU #1901
    Anonymous
    Participant

    I install winCDemu 3.6 in order to check, and now both ISO works. I can’t explain, they are the same ISO.

    in reply to: INT3 breakpoint can not be under By VS2010 #1903
    Anonymous
    Participant

    I can confirm that I get the same behavior everytime I debug my driver. It happens especially when I chose debug -> local

    in reply to: Call for feature requests #1666
    Anonymous
    Participant

    Even if you could just mount zip and 7z archives. Think of the compression ratio difference between iso and 7z…The hard drive space you could save; as well as it being in a more open format. Rar isn’t as important to me, and is totally optional. I can see the licensing issues already, but zip and 7z are open source, free formats. :mrgreen: Those could at least help me get rid of WinMount! 😉

    in reply to: Call for feature requests #1664
    Anonymous
    Participant

    How about mounting zip, rar, and 7z archives? All you would have to do is use the 7za.exe or 7za.dll for zip and 7z, and for rar I guess you could use unrar.exe (unpack to a temporary directory, or use the open command line call). If you could accomplish this, you would have replaced about 6 programs of mine with just one. I still keep WinMount around so I can mount 7z and zip archives. If you do that, I’ll even donate. Cause that would be freaking awesome. I am a C++ coder as well, so if you need help in that respect, I could help there too.

    in reply to: VM<->VM kernel debugging #1919
    Anonymous
    Participant

    yes, please, it could make my life faster…!

    in reply to: Call for feature requests #1663
    Anonymous
    Participant

    Hi bazis,
    You have made a very good work with wincdemu.

    I have a feature request for portable version. A simple command-line with no gui. It can be like this:

    Mount.exe
    -Install driver if not exist
    -Mount the Image

    UnMount.exe
    -Unmount the image (not the drive)

    Uninstall.exe
    -Remove the drive letter
    -Remove driver
    -Cmd/Driverquery for update the driver list

    You don’t need to create the file association, anyone can do “open with” if need. I don’t know the c++, i have made some scritp with autoit.

    Best regards
    x_M

    in reply to: Call for feature requests #1661
    Anonymous
    Participant

    A way to check for the current installed version.

    I can’t seem to find it anywhere, version could be shown in WinCDEmu Setting or something like that.

    in reply to: Mounting & Unmounting #1889
    Anonymous
    Participant

    Hi All,

    have the same issue here. The actual image is unmounted when selecting eject however, it still holds the drive letter in this case V: with no image mounted to it.
    Does anyone else have the same problem, its quite annoying since im not able to mount any other image or assign the letter to this particular drive letter.
    Any of you have a work around other then a reboot?

    Thanks in advance!

    Cheers,

    Baz

    in reply to: Total Commander 32 bits and WinCdEmu #1777
    Anonymous
    Participant

    Hi, i habe the same error with TC and WinCDEmu 3.6! w7X64

    Protokollname: Application
    Quelle: Application Error
    Datum: 07.07.2011 08:31:41
    Ereignis-ID: 1000
    Aufgabenkategorie:(100)
    Ebene: Fehler
    Schlüsselwörter:Klassisch
    Benutzer: Nicht zutreffend
    Computer: froc
    Beschreibung:
    Name der fehlerhaften Anwendung: TOTALCMD.EXE, Version: 7.5.6.1, Zeitstempel: 0x2a425e19
    Name des fehlerhaften Moduls: WinCDEmuContextMenu.dll_unloaded, Version: 0.0.0.0, Zeitstempel: 0x4dfe05f0
    Ausnahmecode: 0xc0000005
    Fehleroffset: 0x6c9ceb55
    ID des fehlerhaften Prozesses: 0x1350
    Startzeit der fehlerhaften Anwendung: 0x01cc3c6f6bdc86ca
    Pfad der fehlerhaften Anwendung: C:totalcmdTOTALCMD.EXE
    Pfad des fehlerhaften Moduls: WinCDEmuContextMenu.dll

    gruss mausi

    in reply to: Cannot start debugging #1872
    Anonymous
    Participant

    No, i didn’t. And maybe i have a big misunderstanding.
    Because i am develloping a PCI device driver, i can not use a VM. My guest is another PC (Windows XP). But i thought, that it is possible to connect to the other PC through a name pipe over ethernet too.
    I have started the DDKLaunchMonitor on the guest PC, and i try to connect to this.
    Must i start something on my host PC (Win7 64 Bit)?

Viewing 15 posts - 391 through 405 (of 665 total)