Tag Archives: virtual box

ArcaOS 5.0.8 Part2

This is a quick continuation of my Part 1. One of my initial issues was this:

The scroll bars are always present for the Computer window every time it is opened and no matter the window size. As soon as I pull the window larger, they disappear.

So, the Drives on my desktop was a shadow and looking in the Computer widow I could not find the real Drives folder. It was out of the Computer window which still did not make sense because the scroll bars would go away. Long story short, I deleted the desktop shadow Drives and moved the real Drives to the Desktop. Problem solved. How? Not sure.

Some of my issues using Dynamic Icons:

  • The window upper corner icon does not always open with the Dynamic Icon thumbnail. Closing and opening the window almost always clears this up.
  • The trashcan defaults to a default icon occasionally when there is a trashcan action.
  • BIGICONS directory not changeable, see below.

The installation directory for the icons is “\sys\icons\BIGICONS”. In the config.sys there is this statement:

SET BIGICONS=C:\sys\icons\BIGICONS

However, I have tried setting BIGICONS, in the above statement, to another directory without luck. So, the way I install is to rename the BIGICONS directory to BIGICONS_ and copy the BIGICONS directory from this repo into \sys\icons.

My wish list items:

  • Globally turn the Menu Bar for Icon View off (Maybe there is and I do not know).
  • XCenter use the png icons rather than the defailts.

Anyway, my icon theme is here right now on my home Gitlab (Mybigcons). Here are some screen shot samples:

Time for a snapshot and to try and optimize and find the delay in the config.sys during startup/boot.

ArcaOS 5.0.8 Part1

My Confession … I was once an OS/2 user beginning in the mid to late 1990’s to around 2010ish. In the end I was using eComStation which, if I remember correctly, was based on OS/2 Warp 4 MCP 4.5. Currently there is Arca Noae. I have had Arca installed and played with it a little over the years, but I got into one of those rabbit holes recently with the release of Arca 5.0.8. As a note, I use Arca running on VirtualBox which in turn runs on my HP z820 Gentoo system. Just to provide context, the Neofetch output is below.

I installed with VBox set to use 1 CPU and that was based on several posts and the Arca Wiki. Not sure exactly why this is an issue.

Okay, I am starting with a fresh installation of ArcaOS 5.0.8. I just accepted the default values because I was not sure how deeply I was going to push this thing.

Virtualbox Additions

The first thing I did was to update the VBox additions. I did have the option check (or I assume I did) to install the additions, but they did not seem to get installed. That did not matter, I use VBox 7.0.8 and the Arca install said something like version 6.x.x, so I needed to do an update anyway.

I followed the readme.txt included with the additions and verified against Installing Oracle VM VirtualBox OS/2 Guest Additions on the Arca site. At the top of the Arca page it reads:

IMPORTANT: DO NOT BLINDLY FOLLOW THE INSTRUCTIONS IN THE README FOR THE ADDITIONS, AS THIS WILL RESULT IN UNNECESSARY DUPLICATION AND POSSIBLE BACKLEVELING OF CERTAIN CRITICAL SYSTEM FILES.

https://www.arcanoae.com/wiki/arcaos/post-install-tips-hints/installing-oracle-vm-virtualbox-os-2-guest-additions/

Missing from the Arca instructions, but in the additions readme:

copy libc06*.dll to C:\os2\dll

I was curious, so here is the issue. The additions instruction wants all the libc06* dlls in os2\dll , but he usr\lib directory is where Arca installs the lib06* dlls see below. It seems that in past Arca installs I made this mistake. So, when installing the VBox Additions do not copy the libc dlls.

Directory of C:\VBoxAdd

4-17-23 5:05p 48,179 0 a— libc06.dll
4-17-23 5:05p 48,179 0 a— libc061.dll
4-17-23 5:05p 157,161 0 a— libc062.dll
4-17-23 5:05p 157,161 0 a— libc063.dll
4-17-23 5:05p 157,213 0 a— libc064.dll
4-17-23 5:05p 157,213 0 a— libc065.dll
4-17-23 5:05p 1,361,666 0 a— libc066.dll

Directory of D:\usr\lib

8-26-21 9:26a 45,363 124 a— libc06.dll
8-26-21 9:26a 45,364 124 a— libc061.dll
8-26-21 9:26a 153,497 124 a— libc062.dll
8-26-21 9:26a 153,497 124 a— libc063.dll
8-26-21 9:26a 153,563 124 a— libc064.dll
8-26-21 9:26a 153,563 124 a— libc065.dll
8-26-21 9:26a 316,306 124 a— libc066.dll

I did have to change the “Host Audio Driver” manually to ALSA Audio from default in the VBox settings for the VM. It was default and I am not sure what default is, but I am using pipewire. Anyway, I get sound with ALSA and ICH AC97.

Here is a confusing point. The Arca Install Wiki states, “IDE The IDE storage emulation is the highest performance option, higher than both the AHCI emulation and the NVME emulation.” Then the instructions go on to replace IDE with SATA.

Monitor Resolutions

There was an issue I had to (yet again) relearn with video. My problem is that I am not a multi-monitor person. Instead, I use an Ultra-Wide Monitor (unfortunately not one of the fancy monitors). The Arca install would not allow greater than 1600 width and I wanted 3440, specifically 3440 x 1327 like my ReactOS VM. I found the tweak/fix on the Arca Site and more info on the VBox site. The Arca instructions just briefly repeated here:

VBoxManage setextradata global GUI/MaxGuestResolution any <Enter>
VBoxManage setextradata "<VM-name>" "CustomVideoMode1" "<custom resolution>" <Enter>

FYI, I am using the Panorama Video Driver. Everything worked, now tweaks and eye candy.

Tweaks

Just to ramble, a few changes I made as I remembered my OS/2 days:

  • Status Bars – turn off default for Icon View
  • Icon Size->Icon View: Set dynamic on as default and layout as gridded
  • Desktop manually select “As Placed”
  • I shadow the Drives folder to the Desktop and set single column
  • Drives: Remove the A and B drive icons Wiki
  • Drives: Remove the reserved drive selection
  • Drives: Drive letter before drive letter
  • Deselect “Display Folder Menu Bars” for main windows
  • Solid Color Palette to change default window solid color
  • Various XCenter tweaks
  • Styler changes to the title bar

Finally, I installed my Buuf icon theme. I think a Buuf theme might not be agreeable to everyone, but I used a modified Buuf theme on OS/2 and eCS. The ArcaOS Dynamic Icons makes it extremely easy to construct a theme.

Desktop, Computer, Network, Programs, and Drives Buuf windows

Arca Setup Window

My Issues

During the install and setup, I experienced one Desktop hang while I was adding my network drives.

  1. Is there a way to globally turn the Menu Bar for Icon View off?
  2. Turning on Dynamic Icons did not turn on for Templates folder – I did it manually
  3. The window upper corner icon does not always open with the Dynamic Icon thumbnail. See previous Setup window pic and Command Prompts below.
  4. The scroll bars are always present for the Computer window every time it is openned and no matter the window size. As soon as I pull the window larger, they disappear. See below.

Top corner icon not changing to correct thumbnail

Computer window scroll bars

The end … for now

As for me, I am still waiting for ArcaOS 5.1 and UEFI support. I have an old Intel NUC I would like to try it on …

Full VBox window running Arca 5.0.8 after install and tweaks

ReactOS as a 32bit Open Watcom Dev Environment

I was having problems with the old Windows XP VM I use to compile Open Watcom (OW) boot projects. This VM is an image of my original XP Desktop install that I have IDA and a lot of unused junk, so I decided to build a barebones VM for just using OW compiling. Initially, I was going to use a Windows 7 install as a lightweight single purpose solution; however, that turned out to be a real pain. Even using a real DVD on Windows 7 seemed to be more trouble than it was worth, so I looked for another option. I finally settled on setting up and giving a ReactOS VM.

ReactOS System About
VirtualBox ReactOS VM

I was incredibly surprised that this worked very well. The VM is lightweight, and I have not had many issues of concern. The VM does not seem to restore correctly from a VirtualBox save, but loading is so fast it really does not matter. My work setup for this project is to code in Visual Studio Code for Linux with the source on a Synology NAS share. The share is mounted (systemd automount) in my home directory. The ReactOS VM shares this directory for access to the source and the VM mounts a FAT16 vdi which is my test image that gets booted using Bochs emulator running from a bash shell on my Linux system.

VS Code About GUI

The workflow is to code in VS Code (on Linux), compile and copy the binary to the FAT16 vdi image using the ReactOS VM, and run the test system using Bochs (Linux) using its internal debugger.

VSCode and ReactOS VM on Gentoo Desktop

Virtual Box VERR_VM_DRIVER_NOT_ACCESSIBLE error.

I saw this in the logs of both VB 4.3.30 and 5+:

Failed to open “/dev/vboxdrvu”, errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE

Which based on this post (Ref) is caused by having the wrong permissions, resulting in:

ls -l /dev
 
crw------- 1 root root 10, 57 Oct 2 05:58 vboxdrv
crw------- 1 root root 10, 56 Oct 2 05:58 vboxdrvu
crw------- 1 root root 10, 55 Oct 2 05:58 vboxnetctl
drwxr-x--- 4 root vboxusers 80 Oct 2 05:58 vboxusb

The fix is to create /lib/udev/rules.d/20-virtualbox2.rules and add:

KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="vboxusers", MODE="0660"
KERNEL=="vboxdrvu", NAME="vboxdrvu", OWNER="root", GROUP="vboxusers", MODE="0660"
KERNEL=="vboxnetctl", NAME="vboxnetctl", OWNER="root",GROUP="vboxusers", MODE="0660"

Then restart the system and the permissions are now:

ls -l /dev
 
crw-rw---- 1 root vboxusers 10, 57 Oct 5 06:00 vboxdrv
crw-rw---- 1 root vboxusers 10, 56 Oct 5 06:00 vboxdrvu
crw-rw---- 1 root vboxusers 10, 55 Oct 5 06:00 vboxnetctl
drwxr-x--- 4 root vboxusers 80 Oct 5 06:00 vboxusb

I am not sure how correct this is by including vboxdrv, but it does prevent the errors in VB logs.

Virtual Box 5.0 in Portage!

I guess just in time for Windows 10???

vb5

emerge –unmerge -p virtualbox

Same old catch if you want the BIOS compiled then Open Watcom is needed.  To be specific, I have had to use Open Watcom 1.9.  The emerge output if OW is not found:

>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-emulation/virtualbox-5.0.0/work/VirtualBox-5.0.0 …
Checking for environment: Determined build machine: linux.amd64, target machine: linux.amd64, OK.
Checking for kBuild: found, OK.
Checking for gcc: found version 4.8.4, OK.
Checking for Open Watcom:
** Open Watcom was not found!
Checking for iasl: found version 20130117, OK.
Checking for xslt: found, OK.

After installing Open Watcom and “export WATCOM=/usr//bin/watcom19”, running emerge should result in:

>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-emulation/virtualbox-5.0.0/work/VirtualBox-5.0.0 …
Checking for environment: Determined build machine: linux.amd64, target machine: linux.amd64, OK.
Checking for kBuild: found, OK.
Checking for gcc: found version 4.8.4, OK.
Checking for Open Watcom: found version 1.9, OK.
Checking for iasl: found version 20130117, OK.
Checking for xslt: found, OK.

Also had to “emerge -v virtualbox-extpack-oracle app-emulation/virtualbox-additions” separately.