Forum Replies Created
-
AuthorPosts
-
supportKeymaster
I assume, the problem is with the VIRTUALKD_HOOKED_VBOX_DEVICE_NAME set to “pci” (see VBoxDD.cpp).
In your case you might have to change it to some other device loaded by VirtualBox.supportKeymasterThe sources are actual. The -1 in eax is even more strange.
I would suggest building a debug version of VBoxDD.DLL, copying it to VirtualBox dir, attaching to the VirtualBox process from Visual Studio and setting breakpoints on VirtualKDPortOutHandler() and VirtualKDPortInHandler(). These functions get called when the debug I/O port is read/written.
If VirtualKDPortInHandler() is not called, please try replacing 0x5658 (and 0x5659) with some other port number (note that 2 consequent ports are used). You will need to modify ConstructOverride() in VBoxDD.DLL and several .h/.asm files in kdvm directory.supportKeymasterThe problem is not about the format, it is about special SCSI commands that Windows uses to access non-data track. Anyway, I’ll consider supporting it in the future.
supportKeymasterok, thanks for the reference walkthrough.
supportKeymasterbcdedit /dbgsettings serial debugport:1
then, use VirtualKD entry
More details here: http://msdn.microsoft.com/en-us/windows/hardware/gg487520supportKeymasterGo to VM properties, add select Ports, set COM1 to point to a local pipe (\.pipecom_1), start WinDbg with parameters: “-k com:pipe,port=.\pipedebug”.
supportKeymasterOK, will add it to the roadmap.
supportKeymasterThis is very strange. I have just tested VirtualBox 4.0.8 with Win7 x64 guest and found no problems.
I assume something went wrong with installing the guest-side transport DLL. Can you try doing dynamic patching (described in http://virtualkd.sysprogs.org/ under “Manual Installation”)?supportKeymasterOK, 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.supportKeymasterYour CUE file represents a VideoCD disc (MODE2 statement). This is quite an old an rare format, so the current version of WinCDEmu does not support it.
Adding support for VideoCD and Audio CDs is in the long-term development plan, but is not a priority goal, as such images are very rare nowdays. I would recommend converting the movie into a newer format (e.g. an XVID/MPEG4 file).May 21, 2011 at 10:55 in reply to: Failed to install driver if remove "root/" before HardwardId #1215supportKeymasterWhat is your fully hardware ID and which bus are you using as the underlying bus?
supportKeymasterI will fix this in the future versions.
For now, you can create a symbolic link in your home directory using mklink command (will work on NTFS drives only).supportKeymasterCould you please copy-paste the CUE file contents here? CUE is a simple text file, you can open it with Notepad.
supportKeymasterThe latest version (2.5.2) already supports it.
supportKeymasterIs there a publicly available WinPE ISO out there? I don’t mind adding the support, but I need some test environment for that.
-
AuthorPosts