Forum Replies Created
-
Posts
-
@bazis wrote:
OK, try it in the following sequence:
1. Start your VM. Do not start Windows
2. Start virtual machine monitor. Wait until the VM appears in the list and press “Start debugger”
3. Wait until WinDbg loads and says “connecting to pipe…”
4. Now start the VirtualKD version of Windows.
5. If nothing happens, look at the “packets, resets, OS, debugger and poll rate” fields in VMMON and post the values here.Thanks for your reply.
Tried that again:
1. startet VM, did not start Windows, VM stays at boot screen
2. started VMM
3. started Windbg from VMM
4. WinDbg shows:Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.Opened \.pipekd_Win7_Professional_32Bit
Waiting to reconnect…5. started windows 7 by selecting boot entry with [Virtual KD]
nothing happens, WinDbg stays as is, VMM does not show any other values, windows stays with “Windows wird gestartet”.
Pollrate 0
Packets 0
Resets 0
OS –
Debug –The pipe has a green dot and the Win7 setup is a fresh install with vminstall executed. VBOXDD is renamed/copied.
Host is XP SP3, guest is W7 32/64 with SP1. Tried VirtualBox v4.04 and v4.08, no difference.
The same setup works finr with an XP VM, also using VisualDKK, which is an awesome product btw. So the host and WinDbg part should be ok.
Thanks for any help or hints you can provide.
Regards,
Ronald@bazis wrote:
The latest version (2.5.2) already supports it.
Seems still not tow work under Windows 7. Installed 2.5.2 on the guest using vminstall, replaced and renamed vboxdd.dll, started vmmon.exe.
Starting the guest, either w7 32bit or 64 bit, selecting the Virtual KD start entry. Under 32 bit windows now just stays with “Starting Windows” or in german “Windows wird gestartet”. In vmmon I can see the pipe and can start the debugger manually, it just stays with “Opened \.pipekd_Win7_Professional_32Bit” Waiting to reconnect…
Nothing more happens. Doing the same with a w7 64 bit guest and selecting the virtual kd start option just starts windows normaly and nothing more happens.
Under XP SP3 everything works fine. I have tripple checked that everything is setup correctly. Tried 3 different guest w7 home, w7 prof 32 and 64 bit.
Any suggestions ?
Regards,
Ronaldmovie.cue details:
FILE “movie.bin” BINARY
TRACK 01 MODE2/2352
INDEX 01 00:00:00
TRACK 02 MODE2/2352
INDEX 00 00:04:37
INDEX 01 00:06:37cue/bin not support? i mount the cue file, but cannot read file in the image.
I’m using Windows 7 Ultimate 64bit.
OK thanks for the help. It’ll be a couple of days as I have overtime on at work 🙂
I should add that I’m very grateful for the development of the tool. I appreciate it takes a lot of hard work and its a great project concept.OK, I found it here : viewtopic.php?f=3&t=452
Hi
OK, I was not even aware that batchmnt.exe could do this – we are testing v 3.4 currently. So how should it be applied? Something like …
“batchmnt.exe pathmyiso.iso /drive”
“mygame_on_iso.exe” or whatever
“batchmnt.exe drive /unmount”Sorry, the computer with CDEmu installed is in the room where my daughter is now sleeping 🙂
Rgds/Kjeld
The ability to create persistent mounts is already great, and I will now use v 3.5 for running all my daugters games that require a plethora of CD-ROMs.
However, a command line mode would be great also, someting like:
pathmyiso.iso /drive
I suppose the Win7 UAC can me trained to not respond to this event?
Rgds/Kjeld
Tries to install the new hardware, then hangs. The “new hardware icon” stays in the taskbar and no corresponding drive letter shows up.
Exactly the same thing is happening for me with winCDEmu-3.3.1, under windows XP SP3 (x86) after trying to mount an iso
Pleeeeeease share VBoxDD.dll for VirtualBox 4.0.4!
BTW. VitualBox 4.0.4 includes a file VBoxDbg.dll that looks very similar to VisualDDK VBoxDD.dll.
Why don’t you update the website? Except the Headline, it already states one needs the testsigning mode. Thanks
Hi,
Just installed version 3.3 on a 32 bit Windows 7 system, with all the options left at the default. I wanted to mount an image over the network using a mounted network share (S: in my case), but after pressing OK on the “Mount a CD/DVD image” popup, I’m getting the message “The system cannot find the path specified”. Apparently the solution which works for the TS does not work for me.
I’ve checked various possible causes for this problem:
– Could it be the ISO? No, I can mount a copy of the ISO from a local drive without problems. Installing a program from the ISO while writing this. This also means that WinCDemu is doing the rest of its job quite properly. I’m happy.
– Could it be a “first run” problem? I hadn’t mounted anything before trying to mount this ISO, but after mounting a local copy, I still cannot mount ISOs from this S: drive
– Could it be the path length? Probably not: it’s only 64 characters, or 66 when counting backslashes as 2 characters, or 67 when including a trailing zero. This is well within the limits allowed by Windows.The workaround of creating a local copy works for me, but a real solution would be preferred of course.
Best,
Bart
