Re: [VBox-users] Machine suddenly inaccessible [SOLVED]

2014-03-08 Thread John Perry
On 3/6/2014 2:51 PM, vbox-users-community-requ...@lists.sourceforge.net wrote: > On Wed, Mar 05, 2014 at 01:57:17AM -0500, John Perry wrote: >> >Greg Novak wrote: > BTW, you've got my last name spelled wrong. Oops! Sorry, Greg. The last time I replied to list, Tbird didn't copy the message and

Re: [VBox-users] Machine suddenly inaccessible (Gregory Nowak)

2014-03-05 Thread Gregory Nowak
On Wed, Mar 05, 2014 at 01:57:17AM -0500, John Perry wrote: > Greg Novak wrote: BTW, you've got my last name spelled wrong. > There were two: opensuse 13.1.vbox-prev and opensuse 13.1.vbox-tmp. Both > gave exactly the same result. > > --

Re: [VBox-users] Machine suddenly inaccessible (Gregory Nowak)

2014-03-04 Thread John Perry
Greg Novak wrote: >>Runtime error opening 'C:\Users\John\VirtualBox VMs\opensuse >>13.1\opensuse 13.1.vbox' >>for reading: -102(File not found.). >Hmmm, strange. My suggestion would be to see if you have a >C:\Users\John\VirtualBox VMs\opensuse13.1\opensuse 13.1.vbox.prev >file. If you do, make a

[VBox-users] Machine suddenly inaccessible

2014-03-04 Thread George R Goffe
John, I am NOT an expert with this by any means and don't do much with Windows. Windows seems to like blanks in file names... A LOT. It seems to me that you have a couple of options here: 1) reinstall suse...:( 2) copy/rename the current instance of suse, recreate the instance, compare file

Re: [VBox-users] Machine suddenly inaccessible

2014-03-02 Thread Gregory Nowak
On Sun, Mar 02, 2014 at 08:38:54PM -0500, John Perry wrote: > Runtime error opening 'C:\Users\John\VirtualBox VMs\opensuse > 13.1\opensuse 13.1.vbox' > for reading: -102(File not found.). Hmmm, strange. My suggestion would be to see if you have a C:\Users\John\VirtualBox VMs\opensuse13.1\opensuse

[VBox-users] Machine suddenly inaccessible

2014-03-02 Thread John Perry
Hello, I was running VB 4.3.6 under Windows 7 early this week with no problems. Monday or Tuesday I got a Windows update that required a reboot; after it came back up I did some other work under Windows and then tried to restart my openSuse 13.1 VM, which I've used happily now for several mon