Archives

How can I create an image of a CD, DVD, or Blu-ray Disc with ArcaOS?

An image file of a CD or DVD (or Blu-ray Disc) is commonly called an ISO file or ISO image. It is so named for the ISO 9660 filesystem used for CD media, but the term also applies to the other optical formats.

Sometimes, it is useful to not only burn ISO files to disc but go the other way around, for purposes of transmission or more portable archival storage.

DVD Tools as provided with ArcaOS does not include a direct ISO creation utility, however, the full DVD/CD Toys suite, does. This applet is called Save Image, and works similarly to the Copy Disc applet in both DVD Tools and DVD/CD Toys. (DVD/CD Toys includes a number of very useful features for handling audio discs as well as other handy functions.)

For occasional use or for those who are comfortable at the command line, ArcaOS does include CDRTools, which includes readcd.exe. To use readcd.exe to create an ISO image, open an OS/2 window and type:

readcd dev=0,1,0 -f=<filename.iso> -retries=32 <Enter>

where the value for dev corresponds to the address of your CD, DVD, or Blu-ray drive (you may get the address by using the Device Info applet in the DVD Tools directory) and <filename.iso> is the full path and filename of the ISO file to be created.

DVD/CD Toys is much more user friendly, and if image creation will be a regular activity, it is highly recommended.

How can I tell if I have a Unix Compatibility Subsystem installed?

The primary indicator of a usable Unix Compatibility Subsystem is the presence of a valid location for %UNIXROOT%. In general, this should be the root of a local volume (results may be unpredictable when this is directed to a network share or removable media which may not always be available). To test for this, open an OS/2 window and type:

set UNIXROOT <Enter>

This should return the value (if set) of the %UNIXROOT% variable. On that  volume, look for the directories as discussed on this wiki page. This is a good indication that there is a working subsystem in place.

What software can I install with ANPM today?

ANPM manages the installation, update, downgrade, and removal of software available as RPM (RedHat Package Manager) packages. RPM is a standard packaging method for Linux applications. These files end with a .rpm extension, and may only be extracted with a limited set of tools.

Whereas rpm (on OS/2, rpm.exe) itself is a standalone utility for installing, updating, downgrading, and removing such packages, YUM (Yellowdog Updater, Modified) provides the ability to store collections of RPMs in local or (more commonly) remote collections on the internet, called repositories.

Currently, the main repositories for ported applications for the OS/2 platform are located at Netlabs. Arca Noae also maintains repositories of varying types (see this wiki page for more information about available repositories, what types of packages they contain, and how to add them to ANPM to access their content).

It is important to note that the Netlabs and Arca Noae repositories may contain ported Linux applications and other software and/or documentation. In short, the RPM packaging structure is not limited to only ported Linux applications.

In terms of ported applications, there is quite a selection, and it is growing daily. From development tools to networking utilities to scripting engines to documentation readers, many well known and freely available apps are only a few clicks away from being useful to the average OS/2 user.

Should I update ANPM? It’s just an installer, right?

ANPM is much more than an installer, and has become much more than a graphical interface to YUM. ANPM should be updated when new versions are made available. These are announced in our blog.

Updates to ANPM ensure the highest level of stability and reliability, as well as ease of use of the utility. New features are being added after rigorous testing, and some of these new features may make it possible to manage software packages not previously handled.

Should I update my YUM-RPM Bootstrap?

By definition, the bootstrap is only that: something used to get up and running. Once running, the bootstrap itself is no longer useful. It is not a component to be updated and maintained. It is merely a barebones layout of the overall Unix Compatibility Subsystem, and the programs of which it is comprised will be updated by ANPM as updates for them become available.

We update the bootstrap from time to time to keep it more current with the latest package versions available. This is for logistical reasons, as it is less likely to be problematic when updating from one minor version of an included component to the next, than it is to have to upgrade to a version several major revisions newer. Thus, we try to ship a recent set of components in the bootstrap.

We do not generally announce the availability of new bootstrap builds. This is because such information is essentially irrelevant. ANPM will automatically download and apply the latest bootstrap available, anyway, and the bootstrap, as stated above, need only be applied once and only under very specific conditions.

What is the YUM-RPM Bootstrap, and why would I need it?

On systems with no existing RPM & YUM installation, ANPM should prompt to download and install the base package (the YUM-RPM Bootstrap) upon first program start. The bootstrap itself is a compressed archive of a basic Unix Compatibility Subsystem, with enough functionality for RPM and YUM to function, thus providing the required “back end” for ANPM to install, update, downgrade, and remove installed packages.

Once downloaded, you will be asked to select the drive to be designated as UNIXROOT, and the requisite directories and files contained in the bootstrap will be placed under the root of that volume.

ArcaOS includes a useful Unix Compatibility Subsystem, and does not require the bootstrap to be installed except in rare instances as directed by Support. Likewise, most later releases of eComStation already have a usable Unix Compatibility Subsystem. Early eCS versions and OS/2 Warp 4 which have not had a bootstrap applied to them will need this. Upon first run, ANPM will determine whether the bootstrap is needed, and will download and install it. The bootstrap does not need to be manually downloaded and extracted under any circumstances.

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.

What is Arca Noae Package Manager (ANPM)

Arca Noae Package Manager (ANPM) is a free utility designed to make the installation of certain software easier for OS/2 users.

Originally conceived as a graphical interface for YUM (Yellowdog Updater, Modified), a standard Linux package manager (a utility to install, update, downgrade, and remove software), ANPM is evolving to become the unified software manager for the OS/2 platform.

Users of OS/2 Warp 4 FixPak 13 and above, all versions of eComStation, and of course, ArcaOS have leveraged the convenience of ANPM to keep the Unix Compatibility Subsystem on their systems up to date. Soon, this same level of organization and access to remote repositories of software will be just as useful for software packaged in more traditionally-OS/2 methods (WarpIN).

ANPM is fully open source, licensed under GPLv3.

Learn more about ANPM here.

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.