On Fri, Apr 22, 2011 at 6:01 AM, Bernhard Froehlich <de...@freebsd.org>wrote:
> It's about two months since the last call for testers and a lot of > bugfixing has happened since then. Not all of the reported problems were > FreeBSD related which is a good indication that we're not too far behind > the stability of the other hosts. So let's get it one once again. > Probably not a FreeBSD specific issue, but my legacy XP VM had an issue. When viewing the Settings screen, a warning came up saying invalid VM name. Checking that field revealed a blank name. Reentering the correct one allowed me to proceed with settings changes, but after closing and reopening the main Vbox GUI, then Settings tab again the VM name was again blank. I then created a new XP VM with an identical name which took. At first this seemed odd, but I see Virtualbox changed it's configuration directory location to perhaps a more Windows friendly. I ended up deleting the old configuration and it seems to be working correctly with the new one. Thanks for the work, -- Adam Vande More _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
