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 names, redo the suse installation in the new instance. I can't tell for sure but it looks like someone (VB? Windows?) has inserted a blank in your file name. If the names are EXACTLY identical, I would try copying your old instance files to the new instance files. 3) install the older instance of VB and try again. 4) is it possible to attach the copy of your running suse to a new instance as another disk? In any event, I would try to save the "current" suse instance files. Good luck, George... ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
