There are two different types of Startup folders available in ArcaOS:

• the traditional Workplace Shell Startup folder, by default named “Startup” and located in the Computer folder on the desktop; and, if ArcaOS Desktop has been installed,
• the ArcaOS Desktop Startup Folder (default name) which is created on the desktop when the Create ArcaOS Desktop Startup folder button has been used on the Startup page of the desktop Properties notebook (by default, this folder will present a status bar during desktop initialization).

The procedure for interrupting each of these is different.

To prevent the traditional Startup folder from processing its content during boot, edit CONFIG.SYS to change:

SET RESTARTOBJECTS=STARTUPFOLDERSONLY,REBOOTONLY

to read:

SET RESTARTOBJECTS=NO

Reboot the system.

To stop the ArcaOS Desktop Startup Folder from processing its content:

At desktop init, before the wallpaper or any objects have been rendered, but just as the background color is presented, press and hold a <Shift> key to bring up the Startup panic dialog. Disable the folder processing from there.

Note that timing is critical for the keypress to be processed. Too soon, and IFX may interpret this as the menu request before the desktop is started; too late, and the Startup panic dialog will be missed. Also, generally, if the key is pressed during boot and then released and pressed again, it will be ignored. Likewise, if the key is pressed and held and another key is pressed, it will be ignored. (There are exceptions based upon what type of keyboard is attached to the system; these are general guidelines.)

These two types of folders (and there may be multiples of each type; these directions will stop all instances of either one from running) operate completely independent of one another.

ArcaOS includes a powerful SMP (Symmetric MultiProcessor) kernel with support for up to 64 physical processors or physical processor cores. Processor hyperthreading is not recommended under ArcaOS.

Yes. In addition to supporting internal floppy disk drives for those systems which still have them, the USB mass storage device driver (USBMSD.ADD) provided with ArcaOS includes support for a range of removable disk devices, including external hard drives and solid state drives, USB flash drives (USB sticks or thumb drives), cartridge drives (Zip/Jazz, etc.), and floppy drives (5¼”, 3½”, LS-120, LS-240, etc.).

More information regarding configuration of this support may be found in the ArcaOS wiki, specifically, here and here.

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.)