Pau Garcia i Quiles <[email protected]> writes: > Sounds like $HOME is not returning the location of the .VirtualBox > directory. That's why VBoxManage does not list anything: it looks > for .VirtualBox, finds none (or an empty one), then lists nothing. >
Thank you... now were talking. I haven't learned why that is the case yet though. ls $HOME/.VirtualBox/* /cygdrive/c/Users/harry/.VirtualBox/VBoxSVC.log /cygdrive/c/Users/harry/.VirtualBox/VBoxSVC.log.1 [...] /cygdrive/c/Users/harry/.VirtualBox/VirtualBox.xml /cygdrive/c/Users/harry/.VirtualBox/VirtualBox.xml-prev Or from an actual windows cmd shell: dir %home%\.VirtualBox\ Shows the same stuff. Is that settable somewhere in vbox?... I see nothing in `preferences' or `settings' that seems likely. Is there some ENV setting other than $HOME that will help? How would Vbox loose sight of ~/.VirtualBox? More importantly, how can I tell VBox where to look? I do have the `Default Machine Folder' set to E:\vb\vm But that isn't likely to be problem is it? ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
