Custom Query (16363 matches)
Results (1087 - 1089 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7037 | obsolete | Copy/Paste files from a mapped network drive fails! | ||
| Description |
This happens with and without Networking Support. I created a shared folder named "s" in Virtual Box, mapped the drive in the Guest: net use s: \vboxsvr\s S drive comes up in My Computer. I can browse, execute and copy files, but if I do CTRL + C on any file or folder in the mapped drive then try to paste it anywhere on the C:\ drive of the Guest I get this message box: S:\ is not accessible. The request is not supported. I get odd errors with shared folders now and then, sometimes the mapping is inaccessible/disappears from my computer. I think fixing this is a good start. I think there's a confusion in the clipboard manager as to what's intended for guest and what's for host. Thanks |
|||
| #7039 | obsolete | usb device gets stuck in 'captured' state, not connected to either host or guest | ||
| Description |
This is with VirtualBox 3.2.4 under Windows 7 64-bit, with an Ubuntu 10.04 guest. I'm doing some Android development, so am frequently plugging in various phones and wanting to connect them to the VM. Frequently when I plug a device in, it connects to the host and shows up as "Busy" in the USB devices list. If I select it, it transitions to "Captured", but isn't actually visible to the guest; it's also been detached from the host at that point. When things get in that state, that device is basically "stuck" until I completely shut down the VM/VBox and restart -- even if I unplug the device, it remains displayed in the USB devices list as "Captured". Any attempts to select it again give a dialog box ("busy with a previous request") showing an E_INVALIDARG error from the IHostUSBDevice interface. There doesn't seem to be any particular pattern for when this happens, but it happens frequently enough -- around 50% of the time when plugging a device in. It's also not specific to any particular device, though I've only tried various phones and other similar devices. I've attached VBox.log, though there doesn't seem to be much interesting -- the messages at the end, e.g.: 01:04:29.330 VUSB: attached '00000000037151f0[proxy 0955:7820]' to port 2 01:09:04.888 VUSB: attached '00000000037151f0[proxy 0955:7100]' to port 2 01:28:45.744 VUSB: attached '00000000037151f0[proxy 0955:7100]' to port 2 Are successful attachment of a different device (same device, in normal and in firmware flash mode). The failing device is 22B8:41DB and isn't mentioned in the log. |
|||
| #7050 | obsolete | the installer repair option doesn't function properly | ||
| Description |
Host OS: Windows XP SP3 32 bit, Windows Installer 4.5 for XP (patched) Tested: VB 3.2.4, 3.2.6 beta1 and beta2 The problem: trying to repair the VB installation. The repair process reaches the end, asking at the end to reboot the host, while it automatically launches VirtualBox.exe (I don't think it should do that). Clicking yes to reboot, the VB installer displays error 1461 while the host starts the reboot process. I can reproduce this every time. |
|||

