Set up USB on OS/2 Warp

[ghr]

Introduction

According to the USB readme: supported OS/2 versions include for example:

• Warp 3
• Warp 4
• Warp 4.5

Warp 3 is the interesting one here, even more so because the Guest Additions don't support it (yet ?).

I tested Warp 4.5 (VM and metal) and Warp 3 with FixPak 40 (VM only).

USB guide:

• USB1: OHCI
• USB2: EHCI + OHCI

USB 3 is not supported.

Prerequisites

Prerequisites (see e.g. Hobbes):

• usb10162.zip
• usbs10162.zip (s for mass storage)
• usbk10162.zip (k for keyboard)

These are the latest drivers from IBM.

How to set up for mass storage / USB flash drives (and this is similar for Warp 3 and 4):

• unpack all zips in one common directory
• run hcimonit to see the available controllers
• edit config.sys (see below)
• copy to os2\boot\ directory: usb*.sys, usb*.add
• reboot

Edit config.sys: insert (Warp 3) or activate (Warp 4) these lines:

Code: Select all

BASEDEV=USBOHCD.SYS /V
BASEDEV=USBEHCD.SYS /V
BASEDEV=USBD.SYS /REQ:USBOHCD$,USBEHCD$ /V
BASEDEV=USBMSD.ADD /FLOPPIES:0 /V

Note the /V switches for Verbosity. I use /FLOPPIES:0 because I don’t expect USB floppies…
You will need one matched BASEDEV line for each controller (OHCI, EHCI, UHCI); followed by USBD.SYS which requires in this case the two drivers being loaded before. If one of those fails then the rest will fail too.

Once all works correctly you can remove the /V switches.

Note on Warp 4: this typically comes with USBUHCD.SYS which is an Intel-specific driver, not required for VirtualBox.

Usage

How to use in Warp 3:

• there’s no way to see if a USB device is inserted or not
• there’s (sometimes) no Eject

Erroneous access will be handled in standard OS/2 manner.

How to use in Warp 4.5:

• click Drives > Refresh Removable Media
• this shows your USB flash drive if all went well
• Context menu has Eject Disk option

Erroneous access will be handled in standard OS/2 manner.

Adding support for long filenames

Next step is to add support for long filenames. Simplest way to do this on Warp 4 up:

• if you don’t have WarpIN: install it
• use WarpIN to install FAT32 support from here: https://trac.netlabs.org/fat32 (get the WPI package).

The recommendation for yet another package can be skipped but you are warned!

The second step, use WarpIN to install the FAT32 support failed in my case on Warp3 + FP40. I installed it manually and it worked fine. How to:

• get the same wpi as zip
• unzip and copy the os2 tree into your existing one on C:\
• you can put FAT32FS.IFS into a separate directory if you like, see below

Add two lines to config.sys:

Code: Select all

ifs=c:\fat32fs\fat32.ifs /cache:2048 /h /q /ac:* /largefiles /fat /exfat
call=C:\OS2\cachef32.exe /f /p:2 /m:50000 /b:250 /d:5000

When done you should have a config.sys that starts as follows:

Code: Select all

IFS=C:\OS2\JFS.IFS /AUTOCHECK:*
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:4 /AUTOCHECK:C
….
ifs=c:\fat32fs\fat32.ifs /cache:2048 /h /q /ac:* /largefiles /fat /exfat
call=C:\OS2\cachef32.exe /f /p:2 /m:50000 /b:250 /d:5000
….
PROTSHELL=C:\OS2\PMSHELL.EXE
....

so load FAT32 support after the already available ones and before PROTSHELL. In this case FAT32.IFS is in directory C:\FAT32FS.

And reboot.