Archives

What is the Unix Compatibility Subsystem?

The Unix Compatibility Subsystem is built around a component known as kLIBC, which is itself a project hosted at OS/2 Netlabs. The subsystem consists of a collection of applications generally ported from Linux, and when built from source using the gcc compiler, become native OS/2 applications.

This subsystem brings a whole new world of modern, maintained applications to the OS/2 platform.

While this subsystem is installed as part of ArcaOS, earlier OS/2 Warp 4 distributions may take advantage of this environment and run these applications as well. All that is required to get started is to download and install Arca Noae Package Manager (ANPM), available from this page.

See this wiki page for more information about the Unix Compatibility Subsystem.

How can I tell if my current disk drive is compatible with ArcaOS?

Several factors affect suitability of a particular hard disk drive (HDD) or solid state drive (SSD) for use with ArcaOS. Here is a brief summary:

Capacity

ArcaOS can directly access HDDs and SSDs of up to 2 terabytes (TiB) in size. This means that a 6TiB drive may be used, but AcaOS will only “see” the first 2TiB of space on the drive, and the drive may be unsuitable for multi-boot configurations (surely, ArcaOS and any volumes accessed by ArcaOS will have to be created within the 2TiB boundary). In short, these larger drives should currently be avoided for use with ArcaOS.

Interface

ArcaOS includes disk drivers for IDE, AHCI, and SCSI controllers. (SATA “Legacy mode” utilizes the IDE driver, whereas SATA “Native mode” utilizes the AHCI driver. SCSI drivers are manufacturer and model-specific.)

Currently, SAS and NVMe are not supported. Unsupported disk devices will be silently ignored by ArcaOS, so in multiboot scenarios, it is possible to have another operating system boot from an unsupported device. ArcaOS, however, will be unable to access any data on such a device, even if the underlying filesystem would otherwise be readable by ArcaOS. In short, these devices are simply invisible to ArcaOS.

Hardware RAID devices which are driver-less are supported, as are SATA and SCSI RAID devices where a native driver is available (either provided with ArcaOS or available from a third party).

A note about connection types and device dimensions

HDDs and SSDs may connect to the system through a variety of methods. IDE uses a 40-pin connector, which is known as PATA (Parallel ATA), whereas SCSI will typically use a 50 or 68-pin connector. SATA (Serial ATA) uses a flat, 7-conductor connector.

Both HDDs and SSDs come in a variety of physical sizes. Generally, HDDs today are 3.5 inches wide for desktops and servers and 2.5 inches wide for laptops. SSDs may be packaged in 2.5-inch cases and connect just like a SATA HDD, or may come as circuit boards with exposed memory chips.

For internal connection, these boards generally utilize an M.2 (formerly known as Next Generation Form Factor, or NGFF) connector, which provides a slot into which the end of the SSD board is inserted. Note that the M.2 specification may be used for AHCI as well as NVMe devices. As stated earlier, ArcaOS currently does not support NVMe. An M.2-connected SATA drive should be recognized and work normally with ArcaOS, however.

It is often (wrongly) said that a system has an “M.2 drive.” M.2 is a form factor and connector specification, and not a drive specification.

Physical Format

ArcaOS requires disk devices to utilize 512 bytes per sector (traditional) formatting. Many new SSDs utilize Advanced Format (AF) which refers to sectoring larger than 512 bytes. SSDs which provide 4K native (4Kn) sectoring must provide 512-byte emulation (512e) to mimic a traditional drive. Most AF drives do provide this functionality. Check the manufacturer’s specifications if unsure.

Drive Geometry (CHS)

ArcaOS views hard disks in terms of Cylinders, Heads, and Sectors (CHS), instead of the alternative Logical Block Addressing (LBA) method. When a disk is larger than 512GB, ArcaOS uses a hard disk geometry which has a sectors per track (SPT) value larger than the usual 63 SPT. Depending on the size of the hard disk, the value for SPT may be 127 or 255. This extended value is recorded in the LVM information on the hard disk and it is usually not recognized by other operating systems or their partitioning tools.

Specifically, the SPT requirements for disks larger than 512GB for use with ArcaOS are:

  • Disks < 502GiB can use 63 SPT, 127 SPT, or 255 SPT
  • Disks > 502GiB and < 1TiB can use 127 SPT or 255 SPT
  • Disks > 1TiB must use 255 SPT

 

Windows-created disks use 63 SPT for all sizes, thus Windows-created disks larger than 502GiB are unsuitable for use by ArcaOS unless or until a full backup/wipe/repartition/restore is done. (See the section below on GPT vs MBR for further thoughts when considering this type of operation.)

Partitioning Scheme

If you are planning to add ArcaOS as an additional operating system to a PC which is running a version of Windows 7 or higher, it is possible that the disk has been partitioned using a GUID Partition Table (GPT) instead of a Master Boot Record (MBR) scheme. ArcaOS requires MBR partitioning, and will not install to a GPT disk. Further, ArcaOS cannot access data stored on GPT disks.

How to tell whether the current disk layout is GPT or MBR

Under Windows, the easiest way to tell is to open Disk Management, select the disk, right-click, and select Properties. On the Volumes tab, there should be an item labeled Partition style. This will indicate whether the disk is GPT or MBR.

For Linux installations, consult the documentation for your distribution.

Changing partitioning schemes generally involves a complete backup/wipe/repartition/restore procedure. Often, this is a good time to consider the age of the disk, its capacity, and whether it might be easier to copy the existing partitions to a new MBR device using a suitable utility, such as DFSee.

Partition Alignment

The Logical Volume Management (LVM) system of ArcaOS expects partitions to be CHS-aligned, a requirement which may not be met if the disk was originally (or last) partitioned by foreign (non-OS/2-aware) partitioning software.

Many modern systems often come with hard disks partitioned using MiB alignment and accompanying partitioning tools often use the MiB alignment method as the default. This alignment method is not compatible with ArcaOS. To correct this, a full backup/wipe/repartition/restore is required. (See the section above on GPT vs MBR for further thoughts when considering this type of operation.)

How do I switch back to the standard OS/2 File Open Dialog from the new File Open Container?

If you prefer the standard OS/2 File Open Dialog, or perhaps a different replacement than the File Open Container provided with ArcaOS by default, you may easily switch back.

To disable FOC and switch back to the original OS/2 file open dialog:

  1. Open an OS/2 command prompt.
  2. Change to the \sys\INSTALL\FOC directory on the boot volume.
  3. Type “filedlgtofocdlg /U” and press <Enter>.
  4. Restart the system.

To reenable FOC (any previous settings should be restored):

  1. Open an OS/2 command prompt.
  2. Change to the \sys\INSTALL\FOC directory on the boot volume.
  3. Type “filedlgtofocdlg /I” and press <Enter>.
  4. Restart the system.

What installation media do I need to install ArcaOS? Will it install from diskettes?

As delivered from our server, ArcaOS will install from a single DVD, the mounted ISO file itself (for a virtual machine), from a local (FAT) disk partition, or from a USB stick (flash drive). (See this wiki page for more detailed information.) There is no facility provided with ArcaOS or available from Arca Noae to produce floppy diskette images of the DVD content suitable for installation, or to split the DVD content down into pieces suitable for installation from CD-ROM.

While support for connecting floppy disk drives is still included with ArcaOS as part of the IBM OS/2 Warp 4 component, no effort has been expended to make ArcaOS installable from such media.

Keep in mind that while IBM’s OS/2 offerings were installable from floppy disk, that was quite some time ago, for a product much smaller in overall size than ArcaOS.

If you have a need for special installation media, we suggest you contact one of our partners to see about a solution.

Does ArcaOS really run OS/2 applications, like Mesa/2 and dbExpert and other well-known titles?

Yes.

ArcaOS runs OS/2 applications natively because it is OS/2. Your favorite, classic OS/2 applications, such as Lotus Smartsuite, Mesa/2, dbExpert, Relish, Describe, and so forth install and should run under ArcaOS just as they installed and ran under classic OS/2 Warp 4 – only better.

ArcaOS provides better memory management and hardware support for newer systems than OS/2 Warp 4. This means that applications which may have been somewhat “resource constrained” on older systems are now “set free” under ArcaOS to realize their full performance potential.

Be productive again. Put that great software in which you invested years ago back to good use.

Does ArcaOS include REXX support?

Yes.

ArcaOS includes both Classic REXX and Object REXX. Because the core component in ArcaOS is OS/2 Warp 4.52, REXX applications written to run under OS/2 should work as they always have.

Where can I find user-to-user help for how-to information and tips?

OS/2 has been around for a long time, and one of the great strengths of the platform is a strong user-to-user community of professionals and power users willing to assist in solving problems and giving quality advice.

Several good places exist on the internet, depending upon the type of information desired and one’s preferred method of communication (mailing list, newsgroup, or forum). Here is a sampling of links to get started:

OS/2 VOICE (see the Resources menu)
OS/2 World (see the forums)
eComStation mailing list at Yahoo! Groups
eCS-Technical mailing list at Yahoo! Groups

Why can’t my DOS and Win-OS/2 sessions see more than 2GB of free space?

This is a known issue for DOS and 16-bit Windows sessions (Win-OS/2) under OS/2, eComStation, and ArcaOS (and probably more). It is not a defect in ArcaOS, and is in fact due to a number of limitations in DOS itself (which can’t normally see disks larger than 2GB, anyway).

The workaround is to install a small TSR in your AUTOEXEC.BAT which limits the amount of free space exposed to DOS to 2GB. The file is 2GBFIX.COM, and is available from the excellent Hobbes file repository:

https://hobbes.nmsu.edu/?search=2gbfix

Download the file, unzip, and read the very simple directions in the included 2GBFIX.TXT.

While you’re downloading that file from Hobbes, be sure to browse other great software available there, and consider donating. Hobbes is a true resource for any OS/2 user, and is completely free for all.

An alternative solution is to download and install the V2GB.SYS driver in CONFIG.SYS:

http://www.tavi.co.uk/os2pages/v2gb.html

The advantage of this solution is that it does not take up additional space in the VDM (Virtual DOS Machine).

Note that neither of these solutions is developed nor supported by Arca Noae. References here are for convenience, only. Unintended side-effects may occur with the use of either of these suggested workarounds (e.g., in the case of V2GB.SYS, running “dir” in a DOS session while this driver is active will close the session once the command completes). Be certain to disable any workarounds for this before opening a trouble ticket for the DOS subsystem itself.