Date: Fri, 17 Jul 2015 03:36:58 -0400 From: Quartz <quartz@sneakertech.com> Cc: freebsd-questions@freebsd.org Subject: [OT] anyone know of a GOOD Windows help forum? Message-ID: <55A8B09A.7000200@sneakertech.com> In-Reply-To: <CAAVO5%2BLoW0G=on9A_MvMv29wDzHVCW7Vm66TetnNJnpkffxXGg@mail.gmail.com> References: <55A7D51D.1020605@hiwaay.net> <55A7F1DA.7040106@gmail.com> <55A8054B.7060700@hiwaay.net> <alpine.BSF.2.20.1507161338450.88007@wonkity.com> <56442.128.135.70.2.1437080215.squirrel@cosmo.uchicago.edu> <CAAVO5%2BLoW0G=on9A_MvMv29wDzHVCW7Vm66TetnNJnpkffxXGg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> I confirm VirtualBox works perfectly on FreeBSD 10.1. As a matter of fact > Hi, I confirm also this claim: FreeBSD 10.1 in Virtualbox is very > stable and works very well as workstation: vtnet net driver works at While we're on the topic of VirtualBox: I've just spent the last week banging my head against the wall trying to figure out a Windows 7 issue in VB. Today I double checked my sanity by installing fresh on raw hardware only to discover that my problem appears to be a Win7 design flaw or something and not related to VB at all. Anyone know of a GOOD mailing list or forum for figuring out real system issues with Windows? In other words, somewhere that can tell me something besides the generic "disable antivirus / safeboot / re-install" "solutions" that are always thrown around? (My problem is reproducible with a virgin install, so either it's a bug or I'm crazy).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55A8B09A.7000200>