On Wed, Mar 14, 2007 at 02:33:40PM -0700, Brad Templeton wrote:
>
> Well, now that I have XP up under 1.3.8 on kubuntu edgy, all is
> not quite perfect. I created two shares:
>
> VBoxManage sharedfolder add XPHome -name tmp -hostpath /tmp
> VBoxManage sharedfolder add XPHome -name home -hostpath /home/brad
>
> And then at the dos prompt the net use commands to map them to t: and h:
>
> I can access t:. However, any attempt to access h: (except for properties
> which works) gives a blue screen of death with a lot of text on it,
So I was playing around trying to fix this, and I tried to do vboxmanage
sharedfolder
remove on the folder causing the BSOD.
That gave an error:
[!] FAILED calling aVirtualBox->OpenSession(aSession, uuid) at line 5597!
[!] Primary RC = 0x8000FFFF
[!] Full error info present: true , basic error info present: true
[!] Result Code = 0x8000FFFF
[!] Text = The object functonality is limited
[!] Component = Machine, Interface: IMachine,
{fd443ec1-0009-4f5b-9282-d72760a66916}
[!] Callee = IVirtualBox, {e1d95593-f579-4f47-b489-0b67181014e1}
And yikes, now the VM is marked as "inaccesible" in vbox and it can't find the
image file with the uuid.
Though the vdi is still there and the Machines/XPHome directory with some giant
files in it one with a different id number, and the other in Snapshots.
I presume my VM is still there just damaged, but this is not heartening.
_______________________________________________
vbox-users mailing list
vbox-users@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-users
