VBox 4.0.x was indeed broken, but 4.1.x is a lot better. It also
is able to use extended CPU virtualisation functions, present
from Nehalem upwards, thus its running on windows testbot.
On Thu, Jun 7, 2012, at 09:46 AM, Александр wrote:
07.06.2012, 01:53, cae...@myopera.com
Kind regards,
Sylvain Petreolle
De : Aleksey Bragin alek...@reactos.org
À : ReactOS Development List ros-dev@reactos.org
Envoyé le : Mercredi 6 juin 2012 14h45
Objet : [ros-dev] Debug log problems
Hello,
it's time for my periodical rant about debug log
You don't have a floppy drive attached to your VM, do you ?
Except the HACK thing this is the normal output when a device isn't there.
Kind regards,
Sylvain Petreolle
De : Aleksey Bragin alek...@reactos.org
À : ReactOS Development List ros-dev@reactos.org
This is my debug log, and as far as i know my test machine or virtual one (vbox 3) does NOT have floppy drive. But it has a floppy controller. 06.06.2012, 19:02, "Sylvain Petreolle" spetreo...@yahoo.fr:You don't have a floppy drive attached to your VM, do you ?Except the HACK thing this is the
http://www.reactos.org/bugzilla/show_bug.cgi?id=6789 i've upploaded vbox log, so you can analise it. 06.06.2012, 19:02, "Sylvain Petreolle" spetreo...@yahoo.fr:You don't have a floppy drive attached to your VM, do you ?Except the HACK thing this is the normal output when a device isn't there.Kind
Works fine on VBox 4.1.16?
We kinda dont support Vbox 3 as its... old and having problems
with com output?
On Wed, Jun 6, 2012, at 03:57 PM, Sylvain Petreolle wrote:
Kind regards,
Sylvain Petreolle
De : Aleksey Bragin
07.06.2012, 01:53, "cae...@myopera.com" cae...@myopera.com:Works fine on VBox 4.1.16?We kinda dont support Vbox 3 as its... old and having problems with com output? W00T?! I used to be told by a lot of devs that Vbox 4 is buggy suxx, and VirtualBox 3.2.14 is a better one. So where is the
