Please read the ReadMe before installing and using this software.
Reporting bugs and requesting new features is done through the ticket system. You can view existing tickets, add comments to them and create new tickets using the corresponding buttons at the top of every page. If you want to submit a new bug or request a feature, please use the Search function first to make sure there is no ticket for the same problem already created.
Prior to ArcaOS 5.0.3, ArcaOS included the Netlabs FAT32 driver. The following caution applies to all versions of ArcaOS prior to 5.0.3, and any subsequent versions where the Netlabs driver has been installed.
THE ARCA NOAE FAT32 DRIVER IS NOT AN UPGRADE TO THE NETLABS DRIVER. Switching from the Netlabs FAT32 driver to the Arca Noae FAT32 driver using the WarpIN installer requires first uninstalling the Netlabs driver, and then installing the Arca Noae driver. No reboot is necessary in between these two operations, however, NOTE THAT THE NETLABS FAT32 DRIVER IS KNOWN TO REMOVE CRITICAL CONFIG.SYS ENTRIES UPON UNINSTALLING IT. There are two workarounds to this situation:
- When selecting the Netlabs FAT32 driver for removal, carefully review the CONFIG.SYS changes listed, and deselect the removal of the PATH= and LIBPATH= entries. Manually edit CONFIG.SYS after removal to ensure that these statements are correct.
- Alternatively, restore CONFIG.SYS from a backup copy after uninstalling the Netlabs FAT32 driver and before installing the Arca Noae FAT32 driver. Again, you should review CONFIG.SYS prior to rebooting the system.
When uninstalling, be sure to allow WarpIN to unlock any files in use so that they may be properly deleted from the system. Be sure that no FAT32-formatted devices are active until after the reboot following a successful installation of the Arca Noae FAT32 driver.
The initial release of the Arca Noae FAT32 driver was version 5.0.0. This is the version included in ArcaOS 5.0.3. If you already have ArcaOS 5.0.3, you do not need to upgrade the FAT32 driver until a version greater than 5.0.0 is released. Like all Arca Noae driver and software updates, we will announce when an update is available.
5.0.0 was chosen specifically as the initial release version for two reasons:
- it coincides with the major revision number of ArcaOS (5); and
- it is sufficiently offset from the Netlabs version series so as to avoid confusion between the two different drivers.
Differences between Arca Noae and Netlabs drivers
While both drivers share a common ancestor, the Netlabs FAT32 driver has been expanded to included non-FAT32 filesystem support, including replacing the OS/2 kernel’s built-in FAT12 and FAT16 support, as well as support for VFAT and exFAT. In addition, support has been added to the Netlabs driver for mounting filesystem images. Arca Noae’s approach is fundamentally different, in that we view the FAT32 filesystem driver to be just that: an installable filesystem driver to support FAT32 volumes; nothing more, nothing less. Thus, excess has been removed from the Arca Noae FAT32 driver. Great effort has been made to ensure that the Arca Noae FAT32 driver contains no potentially patent-infringing code.
Both drivers support formatting and disk checking of FAT32 volumes, as well as maintaining a CHKDSK log akin to the one produced by the HPFS CHKDSK.
Some command line utilities (F32STAT.EXE, as an example) are not included with the Arca Noae FAT32 driver distribution. Other utilities (CHKDSK, in the case of F32STAT) should provide reasonable functionality without duplication. It should also not be expected that these utilities, taken from a Netlabs FAT32 distribution, will work at all or will work without negative effects with the Arca Noae FAT32 driver.
The Arca Noae FAT32 driver includes fully re-written documentation and support by Arca Noae. The Netlabs driver includes additional material which may be of interest to developers.
Both drivers are open source, licensed under the same LGPL v2.1. Certain components of the IBM Developer Connection Device Driver Kit for OS/2 (the “DDK”) are required in order to build the FAT32 driver. These components are not part of the Arca Noae FAT32 repository, as they are not publicly available nor legally redisttributable in source form. More information concerning the DDK may be found at EDM/2. Anyone wishing to build the FAT32 driver from source must have the necessary DDK headers.
The source code for the Arca Noae FAT32 driver may be accessed via svn:
Caching (both read and write) is disabled in this version. It is anticipated to be enabled in the next release. As a result, opening and saving or copying to or from FAT32 volumes may take considerably longer than expected. If editing files on FAT32, the suggested workaround is to first copy the file(s) to a local JFS or HPFS volume, edit, save, and copy back (if necessary) the final version(s) to the FAT32 volume. Large PDFs may present similar challenges and may be worked around similarly by copying to a local JFS or HPFS volume and opening from there, instead.
Disk checking is limited at this time, and may not be able to repair all possible errors to the FAT32 filesystem. When damage is detected which cannot be fixed, you will be advised to check the volume using Windows Scandisk or Chkdsk. Arca Noae is looking at solutions to obviate the need for using foreign systems to fully correct FAT32 filesystems.
Changing codepages requires also changing the FAT32 codepage, separately, via the CACHEF32 utility. This is a limitation of the driver architecture. The filesystem driver is not otherwise notified of a change in codepage for a given session.
There is currently no known OS/2 utility to defragment FAT32 volumes. To work around this, Arca Noae recommends that for local volumes located on mechanical media which seem to be badly fragmented (poor read/write performance, beyond lack of caching), files should be copied off of the volume(s), the volume(s) should be reformatted, and the files may then be copied back. Defragmenting non-mechanical media (SSD or USB-attached flash drives) is unnecessary and will cause additional wear to the memory in these devices. It is not recommended to defragment such media.
This entry last updated: by