Hello FreeBSDers,
I have an Epson V700 Photo scanner connected via USB. I use the original
Epson software running in a VirtualBox instance of Windows XP. It's all
worked fine for years until a couple of weeks ago.
The Epson software correctly detects the scanner and can initiate a scan
, Apr 02, 2019 at 04:04:49PM +1100, Graham Menhennitt wrote:
Hello all,
I recently upgraded my desktop box from 11-Stable to 12-Stable via source.
I've rebuilt and installed the 5.2.26 virtualbox-ose and virtualbox-ose-kmod
ports from scratch and made sure that no traces of older versions exist.
I
Hello all,
I recently upgraded my desktop box from 11-Stable to 12-Stable via
source. I've rebuilt and installed the 5.2.26 virtualbox-ose and
virtualbox-ose ports from scratch and made sure that no traces of older
versions exist.
I start the VirtualBox GUI successfully and see the table of
On 21/11/18 10:11 am, Jung-uk Kim wrote:
On 18. 11. 20., Graham Menhennitt wrote:
G'day all,
Does anybody have any clues on how to fix/workaround Bug 230053 -
emulators/virtualbox-ose 5.2.16 failed to build?
I've build VBox many times in the past but have just got this error.
In file
On 21/11/2018 10:11 am, Jung-uk Kim wrote:
On 18. 11. 20., Graham Menhennitt wrote:
G'day all,
Does anybody have any clues on how to fix/workaround Bug 230053 -
emulators/virtualbox-ose 5.2.16 failed to build?
I've build VBox many times in the past but have just got this error.
In file
G'day all,
Does anybody have any clues on how to fix/workaround Bug 230053 -
emulators/virtualbox-ose 5.2.16 failed to build?
I've build VBox many times in the past but have just got this error.
In file included from
On 26/01/2017 06:41, Hans Petter Selasky wrote:
On 01/25/17 10:00, Graham Menhennitt wrote:
On 25/01/2017 00:43, Hans Petter Selasky wrote:
On 01/24/17 12:03, Graham Menhennitt wrote:
On 24/01/2017 04:19, Alfred Perlstein wrote:
Graham, can you follow what Hans is asking and report back
On 25/01/2017 00:43, Hans Petter Selasky wrote:
On 01/24/17 12:03, Graham Menhennitt wrote:
On 24/01/2017 04:19, Alfred Perlstein wrote:
Graham, can you follow what Hans is asking and report back please?
On Jan 23, 2017, at 8:14 AM, Hans Petter Selasky <h...@selasky.org>
On 24/01/2017 04:19, Alfred Perlstein wrote:
Graham, can you follow what Hans is asking and report back please?
On Jan 23, 2017, at 8:14 AM, Hans Petter Selasky wrote:
There hasn't been any big changes in the FreeBSD userspace interfaces used by virtualbox for
a while.
G'day all,
About 6 months ago, the FreeBSD port of VirtualBox was upgraded from
version 5.0.26 to 5.1.4. The new version didn't work with USB devices
whereas the old one did. I raised PR
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212845 at the time.
Since then, the port has followed
I've been successfully running VirtualBox for some time. Last week I
updated my /usr/src/ and /usr/ports, built installed world and kernel,
and did portupgrade -a. Now VirtualBox won't start - it doesn't even
show the window with the list of VMs. I've tried as root and as myself.
I've also tried
11 matches
Mail list logo