# Linux install notes

For WorkMan to function you will need a kernel-supported CD-ROM drive which uses the Sun-style ioctls for audio control. Most SCSI drives should work now. Please report any non-working drive.

[explanation has to be inserted here] You can also use WorkMan's SCSI passthrough code, enabled by defining LINUX_SCSI_PASSTHROUGH at compile time. This will cause WorkMan to send SCSI-2 audio commands directly to the drive rather than going through the Sun-style audio ioctls.

Do not use LINUX_SCSI_PASSTHROUGH if you have an IDE drive -- it won't work!

You will need the X libraries and XView (including "development stuff" like include files), version 3.0 or higher. The supplied Makefile should produce WorkMan without any problems. Your mileage using "xmkmf" may vary. Be sure to backup "Makefile" before desperately trying "xmkmf"...

If you want to use the online help, you'll need to pick a key to act as the XView "Help" key, since PC keyboards don't tend to have Help keys. F1 is a typical choice. Tell the X server about it with xmodmap, like:

> `xmodmap -e "keysym F1 = Help"`

You'll also have to install the workman.info file in the right place as described in the Makefile. ($OPENWINHOME/lib/help/)

### Special notes on fvwm2

If you use fvwm2 or fvwm95-2, you cannot use some widgets of WorkMan as expected. This is definately not a WorkMan bug. I use fvwm2 myself and dislike the behaviour, but I don't feel like patching fvwm2...

- WorkMan's main window will never look like "active".
- No matter how you set up fvwm2, you have to click on the main window's border or title bar to get WorkMan into foreground.
- The "Help" function does not work in the main window
- The selectors for the play mode in the main window won't stay in foreground if dropped down. You'll see your choices for a short time, then the selection hides behind WorkMan's main window and is inaccessible (right mouse button). If you only cycle through the list of options (left button), everything is okay.
- NO, you can't change this behaviour by re-configuring fvwm2.
- And NO, you can't change this behaviour by recompiling fvwm2 yourself.

fvwm1, twm, ctwm, KDE, amiwm and ol(v)wm are working correctly.

[install page] [WorkMan home page]

##### $Date: 1999/01/15 08:47:36 $