Post-install Tips & Hints

Wikis > ArcaOS > Post-install Tips & Hints

The following are presented in no particular order, and may eventually be migrated to separate pages. In such an event, the content here will link to any new pages to help maintain the consistency and functionality of any bookmarks.

Mouse and Pointing Device Issues

Recommended Mouse Driver for ThinkPads

Although AMouse (Advanced Mouse Driver) is the recommended mouse driver for all systems, some people don’t like the way it operates the built in TouchPoint device on Thinkpads. If you are one of these people then you can use the old IBM Single Mouse driver (MOUSE.SYS) instead. The old IBM Single Mouse driver also has specific configuration pages for TrackPoint and TrackPad devices. There are no issues with AMouse and the TrackPad device on Thinkpads, only the built-in TouchPoint device.

To switch to the old IBM Single Mouse driver (MOUSE.SYS) if you already have AMouse installed, simply uninstall AMouse using the uninstall instructions on the AMouse wiki page. The old IBM Single Mouse driver (MOUSE.SYS) itself is already present on the system.

Network Adapter Issues

It may be necessary to add a new driver to those installed with ArcaOS in order to support current or changed hardware. To do this, open Network Adapters and Protocols in the System Setup | Network folder. To change an existing driver, select it, and right-click. From the context menu, select Change driver…, and in the Select Adapter dialog, click the Other Adapter… button to browse to the location of the driver to be added. Select the .NIF for the new driver and click OK. Select the newly added driver and click OK. Finally, exit Network Adapters and Protocols, saving your changes, and reboot to use the newly added driver.

For GenMac drivers where GenMac has not already been installed, see this sub-wiki.

Generally, for updated MultiMac drivers, the MultiMac WarpIN installer will simply update the already-installed driver (or add the selected driver, if not previously installed). If the driver is new, it should appear in the Select Adapter dialog in Network Adapters and Protocols after running the WarpIN installer.

Storage Adapter Issues

SCSI Adapter Drivers require BOOTDLY.SYS

When adding a SCSI adapter driver after installation, Arca Noae recommends adding the following line to CONFIG.SYS:



The purpose of the BOOTDLY.SYS base device driver is to provide enough time for certain other base device drivers to properly initialize, namely SCSI adapters.

Symptoms of needing BOOTDLY.SYS are apparent loading of the SCSI adapter driver but no attached SCSI devices are visible (reported present) on the BUS.

BOOTDLY.SYS is installed with ArcaOS, and it should only be necessary to add the above line to CONFIG.SYS, save the file, and reboot.

Package Management Issues

How to (Re)Install a Package from the ArcaOS On-Disc Repository

Certain RPM packages are installed from the on-disc repository located on the ArcaOS installation medium. Upon successful operating system installation, this (temporary) repository is disabled, though remains present in the Arca Noae Package Manager list of configured repositories.

Sometimes, it may be advisable to install (or reinstall) a package which is located in the on-disc repository. To do this, it is first necessary to enable the repository as follows:

  1. Insert the ArcaOS installation disc in the system’s DVD drive.
  2. Start Arca Noae Package Manager from its object or the shadow located in the System Setup folder.
  3. From the YUM menu, select Repositories… to open the Manage YUM Repositories window.
  4. Select the arca_inst repository, right-click, and from its context menu, select Enable.
  5. Close the Manage YUM Repositories window using its window control.

The package list will refresh. Packages which were delivered with ArcaOS are now available for installation.

It is advisable to disable the on-disc repository when done, or you will be required to insert the ArcaOS installation medium every time Arca Noae Package Manager starts (which may be inconvenient).

Desktop issues

Icon “creep”

It is possible that after several system reboots or desktop restarts that icons on the desktop appear to move closer the top of the screen, eventually leading to a scrollbar on the right side of the desktop. At shutdown, the XCenter closes, and the workarea expands, moving everything up. This position is saved, because the INI files are written after this takes place. At next Desktop start, that’s where everything starts (higher than the previous starting position), and the process repeats. After a few starts, everything has crept up, resulting in the presence of a visible scrollbar on the right side of the desktop. Scrolling moves everything back into position – until the next Desktop start.

To recover, and to prevent this from happening:

  1. Move your icons where you want them on the desktop.
  2. Right-click the desktop and select Properties.
  3. Go to the Desktop tab.
  4. Uncheck Save Desktop properties.

Note that if you make other desktop changes, you’ll need to toggle that setting before and after in order to keep the “new” Desktop layout. Note that installing new programs is another matter, as is rearranging folder content below the Desktop itself. So, if you relocate the trash can, set the checkbox, move the trash can, then unset it (you should not have to reboot or restart the Desktop before unchecking it again, just make sure it’s checked before the move/change, and unchecked before shutdown/reboot).

Shadows in Tree view folders are not immediately rendered at desktop startup

There is a longstanding issue with folders set to display as Tree view by default, where some of their content does not immediately render (shadows of objects are missing, as well as connecting lines – if so configured – expand icons for branches containing only these objects, and so forth).

To work around this issue:

  1. Note the name and location in the local filesystem of the folder (e.g., c:\Desktop\Datafiles).
  2. Create an object named “Refresh my Datafiles folder” in your Startup folder which runs OO (installed with ArcaOS by default, and available from any command line) to list the contents of the folder:
    Path and file name: oo.exe
    Parameters:         /L c:\Desktop\Datafiles > nul

    (Be sure to use the actual name of the folder location, and if the path contains spaces, enclose the entire string in quotes.)

  3. On the Session page, set this to start minimized and close on exit.
  4. Reboot.

Listing the contents of the folder should force a refresh, and this will be done at every system start.

Tip: Use an ArcaOS Desktop Startup folder, and create this object there. When restarting the desktop, ensure that the option for the ArcaOS Desktop Startup folder is checked to start folder content at every desktop restart and this object will be called to ensure that the tree view is populated at each desktop restart.

Tip: It is also possible to specify the folder’s object ID instead of its location in the filesystem. This has the advantage of not being dependent upon the folder remaining in the same location, so if it is dragged, for example, to another folder nested one or more levels deep, you will not have to update the object in the Startup folder. To get the object ID, if ArcaOS Desktop is installed, go to the Icon page for the folder, and click the Details… button. Look for the Object handle (e.g., 0x3924D). Use this as the value for the /L parameter for OO. Alternatively, OO can return the object ID. Using the example above:

[c:\] oo /I c:\Desktop\Datafiles <Enter>

will return the object ID (without the “0x” prefix) in the leftmost column:

3924D  ----  WPFolderEx  "C:\Desktop\Datafiles"

In this case, the parameters for the “Refresh Mydatafiles folder” object will be:

/L 0x3924D > nul

and the folder itself may be moved about the desktop or renamed freely.

Software issues

InnoTek Font Engine for OS/2 (FT2LIB)

FT2LIB is still required by some packages (namely, Apache OpenOffice, though there are several others). This Freetype 2-based font engine is installed with ArcaOS as an RPM. Unlike the original installer from InnoTek, however, the RPM does not create the base registry entries for this component. Thus, it may be necessary to import them in order to be able to customize the component for specific applications (see %UNIXROOT%\usr\share\doc\ft2lib\readme.txt).

Copy the following and paste into your favorite text editor:



[HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine]

[HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine\Hinting]

[HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine\AntiAliasing]

[HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine\Fonts]

[HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine\Fonts\Helv]

[HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine\Fonts\Tms Rmn]
Mapping="Times New Roman"

[HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine\Applications]

[HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine\Applications\mozilla.exe]

[HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine\Applications\firefox.exe]

[HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine\Applications\os2web.exe]

[HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine\Applications\Thunderbird.exe]

Save the file as ft2lib.reg.

In the System Setup folder, open the Registry Editor, and form the menu, select File | Import Registry File. Browse to the location where you saved ft2lib.reg earlier, and click OK. You should receive a confirmation that the import completed successfully.

Note: References to Firefox, SeaMonkey, and Thunderbird in the above code do not imply that current versions of these applications require the InnoTek Font Engine or have any need for these entries to be present. The above is simply the default content created by the original installer from InnoTek.