7 Jun
2012
7 Jun
'12
5:52 p.m.
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, "caemyr(a)myopera.com" <caemyr(a)myopera.com>om>:
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 truth?
On Wed, Jun 6, 2012, at 03:57 PM, Sylvain Petreolle wrote:
Kind regards,
Sylvain Petreolle
____________________________________________________________
De : Aleksey Bragin <[1]aleksey(a)reactos.org>
À : ReactOS Development List <[2]ros-dev(a)reactos.org>
Envoyé le : Mercredi 6 juin 2012 14h45
Objet : [ros-dev] Debug log problems
--
With best regards
Caemyr
_______________________________________________
Ros-dev mailing list
[3]Ros-dev(a)reactos.org
[4]http://www.reactos.org/mailman/listinfo/ros-dev
--
С наилучшими пожеланиями, Александр.
_______________________________________________
Ros-dev mailing list
[5]Ros-dev(a)reactos.org
[6]http://www.reactos.org/mailman/listinfo/ros-dev
--
With best regards
Caemyr
References
1. mailto:aleksey@reactos.org
2. mailto:ros-dev@reactos.org
3. mailto:Ros-dev@reactos.org
4. http://www.reactos.org/mailman/listinfo/ros-dev
5. mailto:Ros-dev@reactos.org
6. http://www.reactos.org/mailman/listinfo/ros-dev