Installing ArcaOS (OS/2) on modern PC hardware (Asus X570 mobo with a Ryzen 5 CPU) – booting and installing from USB flashdrive

My AMD Ryzen 5 PC is hanging when booting the ArcaOS installer from a USB DVD drive, so I’ve moved on to trying a bootable USB flash instead. I’m following the steps here.

The install guide says to use:

\dfsanwin.exe -q run aosboot.dfs

… to create the USB, but this is prompting me to write to disk 1 which is my Windows 10 SSD. Dis 4 is showing up as my USB stick, so I ran it with

\dfsanwin.exe run aosboot.dfs 4

After initializing the USB the installer tells you to copy the .iso to the ARC-ISO dir:

Eject stick, reinsert, copy ArcaOS ISO to the ARCA_ISO directory on the stick as 'ARCAINST.ISO' to boot from it

Note that the .iso I have from my download is named ArcaOS-5.0.7.iso, so after copying it to the ARCA_ISO dir I also renamed is to ARCAINST.ISO to match the instructions.

Now I’m going for the reboot.

… and it wouldn’t boot. I couldn’t work out why it wouldn’t boot from the stick, I think I tried creating a couple more times with different USB sticks but every time the same issue, the PC just wouldn’t see the stick and boot from it.

(Thanks to for the SpongeBob Time Card generator!)

At this point I gave up and a few months passed before I decided to look more into why it wouldn’t boot. I know this PC will boot from a USB because that’s how I installed Windows 10 on it in the first place.

First I got side-tracked reading the FAQs and discussions about ArcaOS support for USB2.0 standards compliant controllers, and that attempting to use USB3.0/3.1 controllers and ports may have varied results. My Ryzen PC has a Asus X570 board with a mix of 3.0 and 3.1 USB ports. At one point I got it to boot from an ISO burned to a CDROM, but then it would hang on the installer where the graphical installer was loaded, so I suspected it was the USB3.0 lack of support.

Next I started reading more about how to configure the boot menu in the Asus BIOS and troubleshoot boot issues from USB devices. In short, the recommendation were to change the following in the BIOS settings:

  • disable Secure Boot
  • disable Fast Boot
  • change UEFI boot support to legacy spport

I couldn’t find how to disable Secure Boot since I think it’s required by Windows 10 that I have on another SSD, but this combination of options allowed a successful boot from the USB stick prepared earlier with the ArcaOS installer on it:

Successful boot of the installer!

Yes, graphical installer!

I bought and installed a cheap 1TB SATA SSD specifically for this install, since I have Windows 10 on the m2 SSDs. I partitioned a 40GB partition for the ArcaOS install:

I know the major selling point of ArcaOS is driver support for modern hardware, but it was eye opening to see this is action, detecting the Ethernet support on the motherboard and selecting a driver automatically:

Success! ArcaOS installed directly on modern hardware!

For those interested, here’s a quick summary of my hardware:

  • Asus X570 mobo with Ryzen 5 cpu
  • 32GB RAM
  • installed to a 40GB partition on a SATA SSD (there are other m2 SSDs on the mobo already with Windows 10)
  • Nvidia 3060 gpu

That’s some pretty hefty hardware for an operating system who’s last release/update was 21 years ago!

ArcaOS install on VirtualBox

My first job out of college was with IBM as a contractor, working in the IBM Software Center, Basingstoke, providing technical support for OS/2 and Communications Manager/2. I ran OS/2 on my own PC at home for a few years after this, before moving to Windows 95.

In the past few years I’ve installed various versions of OS/2 in virtual machines for nostalgic reasons. I’ve also kept an eye on Arca Noae’s ArcaOS as a current day commercial offering of OS/2 complete with updated drivers and hardware support for current day hardware. For a personal install though I’ve been reluctant to pay the $120 for a personal license, but recently decided to bite the bullet and buy a copy.

I like collecting screenshots of OSes during the install process, and this post is one of those 🙂

After the typical ‘white square’ top right and ‘OS/2’ text, we get to the first installer screen:

After accepting the license agreements, the next page is interesting, it prompts you to select a ‘personality’, a pre-configured set of features depending on how you intend to use this installation. I’ll select the default/first option for now. I don’t remember seeing options like this during a typical OS/2 install, maybe Warp 4 provided options like this (I’ll go check later):

I have a blank 2GB virtual disk on VirtualBox for this install, so I’ll select the option to format it. Later when I do a bare metal install I’ll be doing the same on a blank partition on a new SATA SSD:

Prompted to reboot:

The familiar shutdown compete dialog!

After rebooting, you’re back at the first page of the install again. Stepping through the same options we’re now prompted to select the install volume:

There’s no volumes in the dropdown yet, so press the Manage Volumes button:

I clicked on the Volume menu option, then ‘Create new’, then the ‘Standard/bootable’ option:

I kept the default C and named the volume:

I’m using all the free space on this volume, so kept the defaults:

Volume manager now looks like this:

Closing this dialog I’m prompted to save and now the volume is selected:

Next up, location settings. Huh, remember code pages? I set my timezone, DST, and internet time sync:

This next one is interesting and allows you to configure your hardware options. This is obviously where ArcaOS shines in it’s ability to support hardware of the time as well as updated support for current hardware:

Also interesting that support for VirtualBox is selected by default as the installer recognizes we’re installing on VirtualBox:

I kept all options as default for now. When I do a bare metal install next I’ll check out what the Display options are.

Network driver install next and prompted for machine name, workgroup, and username:

Ready to install – let’s go!

Off we go. Noticeably absent and the messages telling you about the various features that you get during a Warp install:

Time to reboot:

During the install there’s a couple reboots we are automatic if you leave the checkbox selected.

Done! Up and runnning!

Enabling serial tty login to a Raspberry Pi

Depending on what Raspbian version you are running on your Pi, the approach for enabling a serial tty login via a VT terminal differs, but on current/recent versions you can enable by enabling and starting this systemd service (steps from this post, and here):

sudo systemctl enable serial-getty@ttyUSB0.service

and then:

sudo systemctl start serial-getty@ttyUSB0.service

This assumes you are using a USB serial dongle and that it’s connected as /dev/ttyUSB0. You can check by doing a ‘ls /dev/ttyUSB*’ before you connect your USB serial adapter and after to check what device your USB dongle appears as.

If you’re running an older version of Raspbian not using systemd, you can add a line to /etc/inittab to initialize getty as described here.