Custom Query (16363 matches)
Results (1462 - 1464 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2591 | fixed | Shared Folders do not work with MS-Office 2003 (Access/Excel/Word) -> Fixed | ||
| Description |
When I try to open an Access 2003 MDB file on a shared folder, I get the error message "too many active users". When I try to open an Access 2003 ADP file, the error message is "This file is not in the correct format for a Microsoft Office Access project." When I try to save an Excel 2003 XLS file, the error message is "Microsoft Office Excel cannot open or save any more documents because there is not enough available memory or disk space." When I try to save a Word 2003 DOC file, the error message is "Word cannot complete the operation because too many files are open." When I use normal Windows networking ("net use n: \10.0.2.2\sharename"), the errors do not occur. I used normal Windows networking since a long time with Virtualbox without any problems. But I cannot use normal Windows networking in this VM, because I have to use a Cisco VPN client which forbids local LAN access (The "Centralized Protection Policy" forbids split-tunneling). (I already checked that I have the newest guest additions (VBoxMRXNP.dll and VBoxSF.sys are version 2.0.4.0). I tried to stop the Webclient service and I tried the new VBoxSF.sys version from http://www.virtualbox.org/ticket/2461). |
|||
| #2594 | fixed | vboxmanage: make it easier to work with VDI files from different locations than ~/.VirtualBox/VDI | ||
| Description |
I have a local direcotry for VirtualBox images as I don't want to store them via NFS. Now when I want to clone an image I get this: ms@mango:~/lokal/VirtualBox-Images> vboxmanage clonevdi Debian-Etch-Template.vdi Debian-Etch-grsec.vdi
VirtualBox Command Line Management Interface Version 1.6.6_OSE
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.
[!] FAILED calling virtualBox->OpenVirtualDiskImage(Bstr(argv[0]), vdi.asOutParam()) at line 3307!
[!] Primary RC = NS_ERROR_FAILURE (0x80004005) - Operation failed
[!] Full error info present: true , basic error info present: true
[!] Result Code = NS_ERROR_FAILURE (0x80004005) - Operation failed
[!] Text = Could not access hard disk image '/home/ms/.VirtualBox/VDI/Debian-Etch-Template.vdi' (VERR_FILE_NOT_FOUND)
[!] Component = HardDisk, Interface: IHardDisk, {fd443ec1-000f-4f5b-9282-d72760a66916}
[!] Callee = IVirtualBox, {2d3b9ea7-25f5-4f07-a8e1-7dd7e0dcf667}
I can do: ms@mango:~/lokal/VirtualBox-Images> ln -s /home_lokal/ms/VirtualBox-Images/Debian-Etch-Template.vdi /home/ms/.VirtualBox/Debian-Etch-Template.vdi And then: ms@mango:~/lokal/VirtualBox-Images> vboxmanage clonevdi ./Debian-Etch-Template.vdi Debian-Etch-grsec.vdi ms@mango:~/lokal/VirtualBox-Images> vboxmanage clonevdi ./Debian-Etch-Template.vdi Debian-Etch-rsbac.vdi But now vboxmanage creates the images in ~/.VirtualBox/VDI. Thus I have to move them around again: ms@mango:~/lokal/VirtualBox-Images> mv ~/.VirtualBox/VDI/Debian-Etch-{grsec,rsbac}.vdi .
Thus all I ask is that vboxmanage respects the path I give instead of insisting on ~/.VirtualBox/VDI. I know I could symlink VDI completely, but I want to have the option to keep some images via NFS. I tested with VirtualBox 1.6.6 as thats the latest OSE edition I can get via backports.org for Debian Etch. I can try with a newer one in case its needed. The issue is minor, but rather annoying. |
|||
| #2596 | fixed | virtualbox-ose-2.0.4: host system (gentoo linux) becomes unresponsive on certain vbox operations | ||
| Description |
on certain operations of vbox, such as (formatting, or copying some big files) the host system becomes unresponsive -- due to high load of io operations? -- and has to be rebooted (hard). |
|||

