Showing posts with label virtualbox. Show all posts
Showing posts with label virtualbox. Show all posts

Sunday, August 28, 2022

First UFO sightings

So, Max finally did it. He found the HW to read our old floppy disks and got our 1985/86 software back and onto proper modern media ;) 

And then we both separately tried to get a good old DOS to run. My attempt was in a virtualbox on my PC... Tricky to get the program/files into that DOS box because you can't mount a folder from the host then (DOS doesnt have vbox extensions), nor do you have networking on it... so I had to dreate a disk image file, put the files on that, and mount it as disk 0 ("A:") to the DOS vm. And this worked.

Ladies and Gentlemen ... I give you... 

UFOS


Please don't ask me what UFOS stood for... the U was most surely "Unterricht" (=education), but I can't remember wha tthe F would be for. I guess I need to try and find that in the sources.

Speaking of which, we did some wonderful stuff - and remember that was two 17y/o kids in high school working on 4.77MHz PCs with just 2 floppy disk drives, natively in x86 Assembler (Macro Assembler if that makes a difference to you, it doesn't to me, because I always considered the "marco" part a primitive pre-processor, not a different language) .

Core architecture was the base module (a .com file), that would load the various modules from disk when needed, and supply a bunch of common functions (a core library, if you will) as a  service interrupt. So when a module wanted to do some windowing/output stuff it would  - as was common practice under DOS - load a function code into the AH register (the AH part of the accu, ok) and call INT F0h, like you would do for a DOS or BIOS function.

The rest seems to be pretty awful, not only because of the lack of documentation.

The above-mentioned interrupt handler, utilized a jump table, i.e. use the function code in AH as an index into an array of function addresses to call those functions (pretty cool for 17y/o, right?) but I didn't check any boundaries... I probably thought I wouldn't need to, because only us two boys would ever call this interrupt... pretty stupid.  (And when I say I, I'm pretty sure that I wrote this piece of code at that time, and looking at the source, it look remarkably like my code)

Thursday, May 20, 2010

VirtualBox 3.2 released

Apart from the kind of obligatory yearly re-branding attempts[1] by the respective new owner, VirtualBox finally comes with some cool new features...

  • Latest Intel hardware support
  • Large Page support
  • In-hypervisor Networking
  • New Storage I/O subsystem
  • Remote Video Acceleration
  • Multiple Virtual Monitors
  • Hot-plug CPU's
  • Virtual SAS Controller
  • Online Snapshot Merging
Details and explanations here, download here.
and, as they guys from ElReg say in their article,

With VirtualBox 3.2 (and no one is ever going to call it Oracle VM VirtualBox, so let's get that straight), the software engineers have tweaked the type 2 (meaning hosted) hypervisor so it can run on all the latest "Westmere" variants of Intel's Core i5 and i7 processors for desktops and the Xeon 5600s for servers and high-end workstations.

VirtualBox 3.2 also sports acceleration for the Remote Data Protocol if you are using a Windows 7 client in a VM, and the hypervisor can emulate an LSI Logic SAS controller for storage as well, which is common in high-end x64 workstations and entry servers and midrange x64 servers.

VirtualBox supports just about any x64 operating system you can imagine: Windows NT all the way back to 4.0 and Windows all the way back to 3.0, plus DOS, OS/2, Linux 2.4 and 2.6, Solaris, and BSD Unix - and now Oracle Enterprise Linux 5.5 and Canonical Ubuntu 10.04 are added to the long list.

So, away with the just-installed v3.1.8 and lets got 3.2...
----
[1] Sun Virtualbox, Sun xVM Virtualbox, Oracle VM VirtualBox, ... come to mind

Tuesday, July 14, 2009

XP/centrino crashes under Vbox 3.02

Just installed the newly released VirtualBox 3.02 today, and my (guest) XP started to crash after I de-installed the "old" (2.2.x) guest additions and installed the 3.02 additions.
Turned out that this is a known windows virtualization problem on Centrinos [1] like documented here.

So I rebooted (for the umpteenth time), F8-ed and selected the last known working settings, regedited the

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm

to the value 4.

Rebooted, and voila... works again.


---
[1] yes, this was on my beloved laptop.

Saturday, May 09, 2009

OpenOffice 3.1 is available - really ?

and ready for download.

However, after installing OOo 3.1 I could not longer work with Calc. Neither thru starting scalc.exe or opening a .ods document, or creating a new spreadsheet from within a running openoffice instance.

Through the UNO/Java API I saw that there is a problem in loading the SCMI.DLL library, but no further indication on what exactly fails there.
Removing and re-installing did not help.
Using the US English version instead of German didn't help either (could've been a build problem with the German build). No hint on google either.

Had to revert back to 3.0.1 - calc now works again.

I'm quite angry - mostly at myself, because I usually test new versions in my virtualbox... This time I did not,.... argh!!!

Saturday, April 18, 2009

24 bit RDP under Windows XP

Just recently during (probably my last) Sunray/VDI demo installation I ran into the problem that we could not get 24bit color depth on the virtualized Windows XPs.

The SunRay part of the installation (i.e. the Desktop Unit (DTU, aka. ThinClient) itself could not be the problem, because they always are 24bit (incl their respective X session on the SunRay Server),
we also ran the RDP client (uttsc) with the -A 24 option to force it to 24bit (which it would default to anyway) ... but to no avail.

Of course as always google is your friend; several people have posted and blogged this already: under Windows XP you have to explicitely enable 24bit for RDP. So in the Windows XP image (or template) open the registry and change

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\ColorDepth

to the value 4.
Not sure if you have to reboot the virtual machine (VM) then, but since rebooting a virtualized XP is quite fast anyway, just reboot it...

Saturday, February 07, 2009

VirtualBox networking on Windows

I guess this was the third time I fell into this trap, so I document it here (mainly for myself):

As long as you have any kind of LAN type interface/adapter active under Windows VirtualBox will try to use this[1] to do its networking (NAT in my case). This is true for LAN/Ethernet as well as WLAN/Wifi.
This also happens quietly, so you don't get an error message (from VBox), just the errors from the guest OS, usually DNS errors, because thats likely the first thing to fail.

In my case I frequently run on 3G/HSPDA only, but still have an active (yet disconnected) LAN and WiFi interface. In order for VirtualBox to work properly, those two have to be disabled.

Annoying...
Hope I remember it next time.

-----
[1] or so it seems.