|
| New Vbox/2 version available |
 |
Sun, 10 Feb 2008 11:53:04 GMT |
Yo all !
A new version of Vbox/2 is available from Paul Smedleys site.
Here is the news:
Build 7 10. feb 2008
----------------------------------------
- Included new Host InterFace (TAP) driver for OS/2 host.
This gives Vbox/2 full networking support. It currently only works with
VboxBFE.
- Fixed NAT networking. NAT networking is now working in all frontends.
- Included a conversion utility, which can convert VPC/2 images to Vbox/2
- Included new SDL driver, which supports VMAN (faster than Dive)
- Fixed Shared folders. Works in QT and SDL now.
Get Vbox/2 here:
http://www.smedley.info/os2ports/index.php?page=virtualbox
--
Allan.
It is better to close your mouth, and look like a fool,
|
| Post Reply
|
| Re: New Vbox/2 version available |
 |
Sun, 10 Feb 2008 17:07:15 GMT |
On Sun, 10 Feb 2008 11:53:04 UTC, "Allan"
<allan2@warpspeed.dyndns.dk>
wrote:
>
> Yo all !
>
> A new version of Vbox/2 is available from Paul Smedleys site.
All I ever get is:
VMMR0.r0 is importing RTR0MemObjLockUser which we couldn't find
VirtualBox Simple SDL GUI built Feb 10 2008 10:03:36
VM creation failed (GVMM)!
VBox status code: -37 (VERR_NOT_SUPPORTED)
Unknown error creating VM!
VBox status code: -37 (VERR_NOT_SUPPORTED)
Error: VM creation failed with VERR_NOT_SUPPORTED.
Whichever EXE I try and whatever ISO image.
--
Regards
Dave Saville
|
| Post Reply
|
| Re: New Vbox/2 version available |
 |
Sun, 10 Feb 2008 17:33:59 GMT |
On Sun, 10 Feb 2008 17:07:15 UTC, "Dave Saville"
<dave@nospam.deezee.org> wrote:
> On Sun, 10 Feb 2008 11:53:04 UTC, "Allan"
<allan2@warpspeed.dyndns.dk>
> wrote:
>
> >
> > Yo all !
> >
> > A new version of Vbox/2 is available from Paul Smedleys site.
>
> All I ever get is:
>
> VMMR0.r0 is importing RTR0MemObjLockUser which we couldn't find
> VirtualBox Simple SDL GUI built Feb 10 2008 10:03:36
> VM creation failed (GVMM)!
> VBox status code: -37 (VERR_NOT_SUPPORTED)
> Unknown error creating VM!
> VBox status code: -37 (VERR_NOT_SUPPORTED)
> Error: VM creation failed with VERR_NOT_SUPPORTED.
>
> Whichever EXE I try and whatever ISO image.
Then you'd better install the device driver, as the readme tells you to.
--
Allan.
It is better to close your mouth, and look like a fool,
|
| Post Reply
|
| Re: New Vbox/2 version available |
 |
Sun, 10 Feb 2008 18:32:30 +010 |
On 10.02.08 18.07, Dave Saville wrote:
> On Sun, 10 Feb 2008 11:53:04 UTC, "Allan"
> <allan2@warpspeed.dyndns.dk> wrote:
>
>> A new version of Vbox/2 is available from Paul Smedleys site.
>
> All I ever get is:
>
> VMMR0.r0 is importing RTR0MemObjLockUser which we couldn't find
> VirtualBox Simple SDL GUI built Feb 10 2008 10:03:36 VM creation
> failed (GVMM)!
IIRC, the GUI is not working yet. You have to use the command line
application.
--
|
| Post Reply
|
| Re: New Vbox/2 version available |
 |
Mon, 11 Feb 2008 08:52:33 GMT |
On Sun, 10 Feb 2008 17:33:59 UTC, "Allan"
<allan2@warpspeed.dyndns.dk>
wrote:
> On Sun, 10 Feb 2008 17:07:15 UTC, "Dave Saville"
<dave@nospam.deezee.org> wrote:
>
> > On Sun, 10 Feb 2008 11:53:04 UTC, "Allan"
<allan2@warpspeed.dyndns.dk>
> > wrote:
> >
> > >
> > > Yo all !
> > >
> > > A new version of Vbox/2 is available from Paul Smedleys site.
> >
> > All I ever get is:
> >
> > VMMR0.r0 is importing RTR0MemObjLockUser which we couldn't find
> > VirtualBox Simple SDL GUI built Feb 10 2008 10:03:36
> > VM creation failed (GVMM)!
> > VBox status code: -37 (VERR_NOT_SUPPORTED)
> > Unknown error creating VM!
> > VBox status code: -37 (VERR_NOT_SUPPORTED)
> > Error: VM creation failed with VERR_NOT_SUPPORTED.
> >
> > Whichever EXE I try and whatever ISO image.
>
> Then you'd better install the device driver, as the readme tells you to.
In the FAQ it says:
"Q: When I start VboxBFE.EXE I get the following error:
VirtualBox kernel driver not installed!
VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED)
Error: VM creation failed with VERR_VM_DRIVER_NOT_INSTALLED.
A: This error tells you, that you have not installed VboxDrv.sys
in config.sys (or it was not loaded). Install the driver, or
use "SET VBOX_SUPLIB_FAKE=fake" before you start
VboxBFE.EXE"
This implies it will work - I think an earlier release said it would -
but slowly :-) I had the SET - and my error is not that one anyway.
--
Regards
Dave Saville
|
| Post Reply
|
|
|
|
|
|
|
|
|
|