XP on Windows 7 (& 8.1 & 10) with
you loved your XP and didn’t
understand why you have to give it up, this
is not for you. ... It won’t even run any
games, probably, except solitaire. (But then I got flight
simulator running and, in a final towering triumph, my beloved
But no, I
wanted it so I could update
a 1993 Casio
(synthesizer) librarian I wrote and
thoughtlessly neglected over the years. ... The following is a
summary of the virtual
box situation: if, for instance, you
don’t know what VirtualBox
is, you won’t find out here; google
— goto google.com and
most people use a search field built-in to their browser if it hasn’t,
like Firefox, been hijacked to some broken dreck like Yahoo search. ...
Well I suppose I should admit VirtualBox is free;
and that it
works noticeably better than it used to.....
1. Get a more-or-less
legal copy of the Windows XP operating system
is the last
that might run 16-bit
executables — there are
64-bit XPs, and strictly speaking there’re plenty of 32-bit Vistas,
but I guess I meant working
Windows. And Win 7 was also available in 32-bit versions which probably
run 16-bit executables. But XP’s the outstanding 32-bit remnant.
The point being, that when the great and incompetent Microsoft went to
64-bits, they broke
— apparently the CPU
do it, but not Microsoft. Or maybe they just didn’t feel like
... There are various dodgy amusements — I googled for “vbox
and found a few — but I
of course spent good money at Amazon ($30)
Ebay ($8) for my
XPs and both
appear to be ligit (!?) or at least not wildly felonious, although
looks scammy and I still
my doubts and I’ll never really know....
not up on stealing Windows operating systems — I never even
except with Windows 98
which’d work with anything,
but after that I just bought a new machine when the Microsoft planned
too fierce — so I wasn’t all au
courant about the enormous long gobbledygook
“key” code which is really what one pays a legitimate vendor
although the installation disc is probably necessary too. I “ISO”ed
VirtualBox can deal with the ISO file directly and it makes life
pay attention to the XP installation (i.e. inside virtualbox) if it
change the key code —
i.e. to the one the kindly vendor has sold you — on the (erroneous)
I, as a qualified
a chance and did just that, calling
insufferable Microsoft robot on
and repeating endless numbers back and
forth; which failed. The robot was very contrite. ... So then I
went back and changed
code to the vendor-supplied thing like I was supposed to,
went through the whole rigmarole again, all this of course inside
VirtualBox, i.e. after running the virtual XP install ISO — and it
work. This was from the Amazon vendor who sold me a CD which, totally
the one advertised, was “strictly for Dell reinstallation”
according to printing all over it. ... And oh yes; to start
the XP activation program, so I could change
my key code, I used the incantation (from somewhere on the web of
in a DOS box (i.e. inside the virtual XP in VirtualBox, inside a DOS
and who knows,
it might work
for you. The eye of a newt will probably help. ... I mean occasionally
program starts by
itself, randomly of course, because Microsoft’s so playful and
2. Getting your silly virtual XP on your silly LAN
directories is easier)
could copy dangerous files and stuff:
the internet you dangerous fool, XP
is like sharkbait
up there! ... No no just on the wonderful ethernet
I have strung around
the wandering ways so all my machines can yammer at each other. I
connect to the internet
wireless adapters, and never the twain
shall meet I sincerely hope, although you can apparently do that with
your VirtualBox if you have extreme
self-destructive urges. ... But really, the shared
route is better....
I confess the process was and is
puzzling and flaky, but quick ’n’ easy, and I could frequently
see my virtual machine when I went “net view” (in a DOS box)
on another or the same
the VBox XP: remember to “share”
if you want other machines to be able to see the XP virtual drive. XP
fight you like a puma.
XP, “Devices” on top-of-screen VBOX menu, “network”,
“network settings”, “adapter 1” tab:
to: Bridged Adapter
Name: Intel(R) 82579V Gigabit Network Connection?
select whatever looks like the ethernet
... The wireli seemed to be named
so I could tell, and one crate didn’t have
a wireless offering....
I don’t think I changed the
“advanced” settings — which is odd for me. ... Well actually
seem to provide a way to change the imaginary network card, and I
delude myself I did that and something got better; but probably just
moonphase. ... But I concluded by using the shared drive thing instead
which does most of what I’d want....
XP, “Devices” on top-of-screen VBOX menu, “network”:
I believe I had to
click “connect network adapter”, and after I did, the little
“disconnected network” icon from the virtual XP task bar disappeared.
“connect network adapter” cryptically signals its “on-ness”
by a little
fallen-in box appearing around some weird graphic, looks like a mouse?
net addresses vs names
I thought there was consistency, but I think the bottom
line is the
vbox network works sometimes, amusingly ... i.e. like my 2014
macbook — although
when I installed vbox there it was a treat to see XP with my beloved owenshow
running in the mac. But don’t
try copying your vbox XP startup icon thingey to the mac task bar; vbox
when you try to start that.
And the macintosh vbox network seemed much more
gershtunk than the windows host renditions. But the Win7
network with the macs works just fine; I assume Apple changed
vbox didn’t. ... And for that matter my Windows 7 ethernet works
better with the macs even when they can’t
see each other!
And actually the vbox XP network works
frequently, maybe more than real
XPs, particularly when mapping a real
computer share to an XP drive inside vbox, but the other way round
doesn’t seem to go good. Or at least not often. ... It seems as if
map real drives, including local drives, into the vbox XP with
So in a
feat of rubegoldbergesque daring which is so typical of my beautiful
technical world, I can copy things to host drives, and then copy from
them, in pool ball ricochet bouncing-around style. ... And maybe the
vboxXP drive can get mapped by that host....
then in the fullness of time, after one of my Vbox XP networks stopped
working almost entirely, I went and ritually changed bunches of setting
to no effect, but then after changing the “mac address” to
randomly by clicking the little Vbox button, it started working good!
directories are better
course you could just share
files with vbox’s shared directory feature instead
LANing around. I
scurrilously alleged here
before that vbox sharing was cranky, but it’s
more like tongue-tied; once one understands what they’re trying to
it’s really quite useful. You can designate any real hard drive path
to appear as a virtual drive
in the vbox XP system, writable or read-only. ... Tip
Before adding/changing shared
folders, you must shut down your
virtual XP with “power off” or something, instead of
“save”, where you just put it in suspended animation. ... Actually,
my vbox XPs, the emulated power-off really was just as fast: it takes
but a moment, while the save takes quite a while, the trade-off being
the emulated power-on boot taking longer, but it feels like a wash.
... And of course with the save route, vbox’ll let
you set-up numerous
shared folders (and other features), and
spit at you when you try to start the thing. ... And then after a while
doing this, vbox claimed the thing was “aborted”, but that
apparently just a snit; worked OK the next time....
might prefix the “Name”
you give these things with
numbers as shown .
If you want vbox to automount them, vbox’ll decide
which letters they get, which starts at some arbitrary drive letter and
up. If you’d prefer them to have some order, then numbers or something
at the front of the names’ll sort them like that. It’s
probably pretty easy to mount them inside
the virtual XP — in a startup batch file or something; I never tried,
explained somewhere — but the automount requires less thinking....
EDIT SHARED FOLDERS:
When I “imported” my precious XP system into a new PC virtualbox
4/20, it wouldn’t let me edit some of the shared folders (right-click,
edit). Of course they couldn’t actually have a useful error message,
but it was apparently because the folders referred to non-existent
directories — if only these programmers could speak!
And then I realized that instead of screwing-around with
obviously pathologically-flaky ethernet, I could just map
the local C: drive to the vbox thing — with the read-only
option of course — which mostly takes care of my frivolous
necessities. ... Using my pitiful OwenShow,
you understand, which is actually good
at traversing directories, i.e. as opposed to the we’re-all-friends
Windows file explorer....
shared directories: Use the double-click Luke
the other hand, vbox sharing barely worked on the Mac, at least with
Apple’s operating-system-of-the-week. Some smart person thought vbox
should pop-up a finder window when you click the “edit shared
directories” icon in vbox, and it wouldn’t
let me type in it.
so bad, except that when I clicked
“choose” in the finder window to select my chosen directory,
some invisible speechless cruelly-muted window
some kind of attention — I accidentally managed to click the sliver
of a button on it once, but I don’t think I ever figured-out what
was — because it is mysteriously obscured by a large speechless blank
window in front of it,
content. ... And I was so looking
forward to seeing my gwbasic
programs on the Mac....
that apparently was all because I was clicking
the stupid cryptic vbox
least, when I went back and plugged in my pitiful ancient “hot car”
mouse with only one headlight — instead
of using the laptop track pad —
the field I
wanted to change on the vbox “shared” form — why, I could
No sweat! Go right ahead
4. Endless Miscellany: GWBASIC & so much more...
And so gwbasic’s day came again, and it runs my
once more .
I vaguely remembered this towering masterpiece, but I
figured the “C” was for “color” or something ...
I copied it to
and added a delay
multiplier so it wouldn’t be so ridiculously speedy on my hot vbox
’n’ Mac systems! And the “C” flavor was doubtless
a previous new computer in forgotten ages long gone before....
XP ’n’ me
Back to the decent world of Windows &
ancient keyboard faker Stackey
(a primitive rendition of, for instance, MacroExpress,
which I have installed everywhere in my modern computery,
more like my
own recent kjorg,
except that Stackey was born in the foetid swamps of MSDOS
and consequently is
a TSR kind of thing).
Pitifully I forgot
how to run TSRs in Windows XP, so
when I couldn’t get vbox to install the beloved even-more ancient
Windows 98 which I delusionally believed would somehow accommodate
Stackey better, I fretted and fumed, but then decided I didn’t want that
old high memory
thing anyway. However I did
want to jog my
memory with Stackeyh.com
which ran fine in XP, so I could decode my ancient chicken-track-filled
batch files and
ridiculously incorporate their stackey-style syntax into my pitiful kjorg,
so I could once again run
16-bit Turbo C in all its antiquated and
But it was all my delusional dreamworld, forgetfulness,
XP can install the Stackey TSR,
and indeed I’d probably done
myself in those ancient days:
put the magic gobbledygook “lh
c:\elsecoms\stackey.com” into the \windows\system\autoexec.nt
my antediluvian 16-bit
Borland Turbo C ran in all my ancient
shabby automated glory, executing compiles against antique .PRJ files
bound! ... So then I had a remorseful anxiety fit, and dashed about
backing-up the marvelous virtual things I had created, so
they will never perish in hundreds
of weeks. ... With vbox’s
And I should note that I destroyed
my last XP desktop computers here in paradise
within the last few years — saving the hard drives, of course;
in which I
inspected their autoexec.nt files, and apparently Stackey was not
installed; must have been in an even earlier XP. ... Anyway, I just
have the room
for two redundant desktop systems anymore, even though as recently as a
few more years ago I had actually used them for work. ... Such reckless
wasteful folly! ... But in recognition of my new virtual world, I took
my last functioning XP machine — an adorable tiny hand-me-down
bricks-itself-very-occasionally ACER laptop — and turned off its
it will gaily frolic with the internet no more forever (after Spybot
let me down); an enforced inhibition I of course imposed without the
hesitation on the growing herd of virtual XPs....
that’s all she wrote! ... My story is so heart-breakingly short so
far — but
to destroy things. ... For instance I got the fabulous Linux
VirtualBox, working as well as Linux ever does, with this helpful
which sadly is more than 15 minutes old and hence didn’t
actually correspond to the Linux Mint before me.
And I suppose I should note that the VirtualBox additions may have
already been installed and working, since I got it from a VBoxish source.
Of course they won’t say, and the stuff seemed to work as little
as much before and is it did afterwards; as much as Linux ever does.
But with VirtualBox, you
than the universal solvent of
rebooting — so long as you saved a copy of the original giant download,
you can get your original hard
untouched by your
hands! ... Of course it’s still Linux....
Then, in the tragic end game, it turned-out it was
Virtual Box was going to emulate the joystick/MIDI interface whose hardware ports my
1993 CZ101 synth librarian
back in those never-to-return days. I can still taste
my intense frustration when Windows got all softwarey,
and I was forbidden
to touch those so-hugely-useful hardware thingeys. ... But I will still
treasure my Vbox XPs. I got hold of some ancient directories where I
had entombed all the executables for 16-bit software that would never
run after XP — and now I can get it all back, and revisit those
simpler days. ... And in the final irony, my 1993 CZ101 “jglib”
the last gasp! Which
was in fact, the 1995
— which was the one that worked with the XP joystick/MIDI card. The
1993 code worked with a PCMCIA
laptop plug-in MIDI card. ... Which leads us right to ...
& Win 3.1?!?!?!
I’ll never get it working perfectly, but it does
come-up and present me with a beautiful MSDOS 6.22 command line, and
in there’ll start-up the beloved Microsoft GUI.
This kindly fellow’s
got it, a 13Gb vbox VHD drive or whatever it is.
diskettes need apply ...
But I couldn’t
figure-out how to get any data into it (or out), so I can’t revive
herds of MSDOS/WIN3.1 programs & batch files of yore. I suspect
with concocting just the right disk image (nope).
... But for now, it’s still truly charming....
The Internet Disinformation Standard
the forum standard for problems like this is that those
who speak not only do not know,
of course, they’re
so very compassionate caring & smart.
So kindly caring feeling compassionate internet twits will proclaim all
the things you need to get a vbox MSDOS network
connection working without
I might get the necessary primitive software into
the vbox DOS. I actually got a forum thingey
where the guy and the helpful kindly compassionate etc. went on
and on, finally declaring victory, and claimed he
try to attach a step-by-step note — and
which seems to be completely worthless. Not only does he observe omerta about how to
share the files
to share files into your vbox MSDOS, but his links to the files
were broken, and then when I googled-up some substitutes, his
“explanation” was useless. ... I always say, if there’s
compassionate selfless and caring than the average internetty
know-it-all, it’s an internetty network
know-it-all. ... Anyway, the Virtual Box MSDOS diskette
probably don’t work nohow and
probably never did, no stinking image or not, after installing a bunch
images, not one of
which showed the slightest sign of functionality inside the MSDOS
— “dir a:[|b:]” just
And somehow I see I have failed
to unambiguously proclaim that these internet twits not only are
whatever it is they claim they got to work:
get it to work after endless forum fumfering about it, and are
obviously too embarrassed — and such lying weasels — to post
any admission, and so they cruise on
to the next astonishingly admirable geeky fictional achievement. Of
course I suppose they’re all of 12 years old. ... The mature ones....
anyway, when Vbox says
or more drives are inaccessible...”
something when Vbox starts,
you want to “check”, I clicked OK, and it gave not the
clue, but showed the “Virtual Media Manager” form —
get there explicitly
like “File / Virtual etc” or ^D. ...
Then, one (or
the tabs should have the international “danger triangle”
something symbol. In my case it was the “Floppy disks” tab,
tab there was a bunch of danger triangle floppy disk images left-over
from my pitiful attempts with MSDOS.
right-clicked each one, told it to “remove”, all fixed....
that a 99% certainty
vbox MSDOS diskette images don’t work. I found another vbox MSDOS
vhd site, the one named “Microsoft
MS-DOS 6.22 with CD-Rom Support [Virtual PC VHD].7z”) and randomly
discovered — after consistent diskette image total failure —
it’s all so simple:
In the vbox
for your MSDOS/WIN
virtualization, you can right-click on an image of the
provided CD (or you can probably add if it isn’t there?),
and change it to one’s desired ISO. ... That’s all she wrote!
point! (But there’s some more below.)
Both of my MSDOS virtual systems had a CD drive
already tacked-on, and obviously that was what was supposed
to be used. The kindly caring internetty helpful folk just thought
it’d be wrong
they are so compassionate
Note incidentally that both of my vbox MSDOS systems
had the same
and vbox gets upset if you try to use a VHD with an existing
UUID. I fixed that with the magic mumbo jumbo “vboxmanage
internalcommands sethduuid Offending.vhd”. ... All
this means that the two systems I found were derived from each other,
the beautiful Windows
3.1 virtualization from the other guy, who didn’t provide
... Anyway, all
that nonsense about diskette images — that was just compassionate
smart people trying tell me, use
ISO luke! ... I never did
learn to speak Stupid Internet. ... So I have plenty of programs
that’ll make CD ISOs; imgburn
is nice, and its ISOs mounted-up EZ, unlike anything else vboxish so
7 I could
- Mount the VHD file — the Virtual Hard Disk vbox
I downloaded — on a real
Windows 7 drive letter! ... Right-click “Computer”,
“Disk management”, “Mount VHD”, and specify the
VHD file. But you gotta do it when the vbox system is off.
- Mutilate it to your heart’s content. Stick in all
“Bluechip” Caldor XT PC MSDOS 6.22 / Windows debris!
it — Vbox’ll just spit if you don’t. Right-click the
entry for the disk; in the numbered section, on the bottom of the disk
- And bob’s ur uncle! Files right in there. ...
- And you
mountable VHDs to the vbox system, which kind of thing we used to do
time in the
so-called real world back in the day when 100 megabyte hard drives were
ransom stuff. So ...
- Win7 didn’t
like the VHD vbox
however tolerated both a fixed and a dynamic VHD Win7
created (another disk management right-click option). The dynamic
a little easier; for me to zip/backup at least. Win7 says fixed is
“recommended” or something, probably because people’ll
a dynamic VHD on some limited storage etc. But who knows. But I could
14 megabytes of ancient basement DOS files onto it in Win7, and they
appeared inside vbox. Now I can use my beloved OwenView
for further mutilation!
- Sometimes, I had to exit Win 7 disk management
enter it again to detach
I created there; after I copied all my files. A little cranky. Like the
ways to get stuff in and even out-of Vbox MSDOS
— which the kind caring compassionate internetty mobs were forbidden
from revealing, because of their sacred vow to never
unless it’s useless.
look so much cooler
that way — and after all, they actually know
I can wait and
if I ever
to get anything
of this admirable fossil; doesn’t seem likely. The ISO
route’s pretty good for getting stuff in, and mounting
the VHD isn’t so horrible for getting stuff in or out.
a shared drive’d be more fun.
I am pretty sure
there is no VBOX MSDOS Win3 network share one can concoct, or
images. Lots of thoughtful caring compassionate twits do tell
of such marvels;
but never never never
them. Or produce the slightest evidence that they ever
Golden Age — NOT Win3
MSDOS/WIN3. Sorry, no gilded beauty. I mean, I can run my precious OwenView
in XP fine; it was just the
Windows 7 and
& etc. that obsoleted the poor innocent thing, and all the .com
and their little friends. Since the vbox
XP is so sprightly,
the more/better excuse is just Usux™, as usual, “encouraging”
with imaginary fairy tales, i.e. planned
obsolescence AKA a beguiling
in restraint of trade....
I think of some wonder, like my beloved ZMU
it’d run in my new-found emulated MSDOS 6 — but it’ll
run so much better
in the emulated
And so easy to get in/out with all the shared drives. So, therefore, XP is the golden
age in-a-vbox, the perfect Windows
operating system, never to return. ... The
MSDOS/WIN3 thing is the antique snow globe of my computery youth,
with the beautiful bits of 16-bitness drifting down down as we go
sleep, in the future....
— the enchanted
Set Your Hypervisor on Stun!
4/28/20. And then, after many a summer, along came another desktop and
virtualbox, after numerous bogus errors, managed to admit “Not in
hypervisor partition” which, googled, led me to the obvious solution
groveling in the dangerous BIOS where, indeed, the “Intel(R)
Virtualization Technology” was
disabled, until I foolishly enabled it.
Flight Simulator 2004 — the sorrow
5/20. So I did
install a game into VirtualBox! ... I installed my ebay $20 Microsoft Flight
Simulator 2004 in windows 10:
the install worked, but it refused to run
there. ... So then I mapped the flight simulator directory as read/write
into my vbox xp thing — and it ran
great! ... Oh, I had to let it see an actual CD drive, so I could put in
the copy-extortion disk 4. ... The point here
is to provide the poor aged computerist with the benign beauty of wandering
aerial landscapes without the
ridiculous modern gaming requirements.
... And so it does.
But then I reached for the stars, and tried to make a joystick
... First of all, vbox 6.0.22 wouldn’t let me set the usb to 2.0;
insisted on the lowest USB 1.1 setting. That was because I had
said I should somewhere probably presumably. Anyway the correct, matching,
ticket, and then I could gloriously set usb 2.0. I will say vbox was
perfectly happy to perform the “downgrade” — no doubt
experience. ... And whadda ya know!?!? I started my vbox XP and it said
“found new hardware” “game something” and installed
But no joystick. ... And antique Usux™ — from beyond 8/04!
— then complained that
my hardware has changed so much I’d have to go through “activation”
again. ... It was probably me wickedly clicking the “3d” checkbox
vbox — so the game would be happy! ... And so I bowed before
the Usux™ robot yet again, for 20 minutes or so; got screen shots
this time! — i.e., of the ridiculous 400-digit (approximate) number
had to laboriously enter, which the perky robot claimed I’d be able
use again the next time this happened....
The Kindly Internet Know-it-alls
once again, that the vbox twit standard is
puerile/ignorant. ... Pitifully trying to automate my DRM
obeisance, I googled how to turn-on the wireless, and in one forum an
idiot explained firmly it was impossible. Except apparently you just,
in the network settings, turn-on a second network adapter with a “NAT”
setting and it springs to life. Mumbo-jumbo, to be sure, but hardly
impossible. ... Of course the Usux™ robot refused to use
the wireless, so I had to grovel on the phone again.
following my own advice, I just kept googling and eventually found-out
the obvious stupid simple way to get my vbox XP joystick, as per the
beautiful illustration — which is to just click on the “+”
things I put
a red square around, and select the usb device you want to appear in
your beautiful virtual box. The vbox illuminati refer to this as a “filter”
in an effort to frighten/confuse....
vbox XP, (1.) command-line “joy.cpl”, (2.) “properties”,
“test” tab, and bob’s ur uncle. ... At least one “joytester.exe”
doesn’t work in XP or my
Win10, and “joysticktest.exe” worked in win10,
but crashed in XP. But joy.cpl is the path of wisdom in XP and
win10. ... Actually, joytester.exe kind-of works in win10 — although
it claims there is
no joystick, it nevertheless changes readings as I fiddled the stick.
But the existence of these programs is dubious, since joy.cpl is
available. Probably written for MSDOS or
... And so now I’m toying
with getting a more recent flightsim that might run in win10. But probably
is a “flight
simulator 2020”, probably unplayable
on my humdrum desktops and in any case probably too expen$ive
— or, wait, it’s non-existent: “available 2020”.
Which makes the most recent one 2006!
And the joysticks appear to be neglected in favor of “game pads”
whatever they are. ... So as is appropriate, my pitiful preoccupations
are once again obsolete. ... Somewhere along the line people got
bored with flight simulation — maybe the alarming
mortality of actual small planes and their pilots had something to do
with it. ... Perhaps, like me, they were unable to control the
sprightly joystick, and were constantly crashing into the grand
And thus in complete innocence I have blundered into
another useless antiquity, like the DSLR and
the silly cameras. And like them, it was conceivably
also sidelined by the all-conquering iphone,
so superior for playing stupid games....
FS 2006 aka “X” — works in Win10!
And so I pitifully attempted to install flight simulator 2006 which,
apparently, uninstalled the 2004 product without asking — well it
claimed it was uninstalling the “previous program” anyway —
Usux™’s been challenging the heights of mediocrity since at
after about 5 minutes “removing program” it settled-down to
industriously copying files from its space-age DVD
And I am too harsh; it didn’t uninstall Flight Simulator
2004, or at least fs2004 still works in virtualbox.
I guess the softies™
just wanted to frighten me. ... But most importantly, it works in
windows 10! ... Which, I assume, was specially-jiggered to do that. ...
all my labors, including the 20 minutes of durance vile submission to
another Usux™ robot on the
phone, were crowned with abysmal pointless victory...
the estimable flight simulator, microsoft
midtown madness has no late model successor that’ll work in win10.
But it worked
— kind-of — in the beloved vbox! The mouse
is totally gershtunk,
could start the “quick race”, “cruise” —
something or other
— with arrow keys, tab, ESC (exits stupid movie at the front), and
enter. And of course I got my joystick
in vbox, without which I suppose it wouldn’t be nearly as much fun,
but they’re probably keyboard thingeys....
But I suppose I
confess that all I do in the stupid game
is smash things — other
cars, lampposts, mail boxes, fire hydrants,
whatever — and that’s just as exhilarating as ever! ... I installed
it inside the vbox XP system from
its CD, which I have
to leave in the drive to implement the copy extortion.
... But once I start smashing those lamp
posts — watch out! ... I
haven’t managed to rouse the gendarmerie yet, but I remember I got
chasing me in the old days and I’m sure I will again. I’ve
a few police cars, that show-up after a few lamp posts....
Mon 4/27/20. So this fellow’s
got a “win95” app that runs
or the mac!, or probably other windows or who knows. It’s perhaps
little crankier than vbox,
and access to other or its own drives is tricky — but it’s
of usux® frontpage! ... It is
really slow because I suppose it’s
emulated, so the guy can run it on his
amiga or something. Vbox, in contrast, uses
the 386 et al
CPUs hidden inside our super-modern equipment....