0: The SoftWindows CPU has encountered an illegal instruction. 

The PC application you are using has tried to execute an instruction that is not valid on the SoftWindows 486 CPU. This normally indicates a fault in the PC program, possibly due to a faulty installation.

Re-install your PC application and/or try running it on a real 486 PC.

4: The hard disk file cannot be found.

Verify the name of the hard disk file you have specified.

5: Floppy drive problem. The drive is already in use, so it cannot be used by SoftWindows.

The floppy drive which SoftWindows is attempting to access is being used by another Unix process.

Shut down the other program which is using the floppy drive and activate the drive by choosing Actions from the Activate menu.

6: The hard disk path name is invalid.

SoftWindows cannot find the directory you have specified for the hard disk file.

Verify and correct the directory name. If the path to the hard disk file contains an environment variable (such as $HOME), verify that it is set correctly in the environment when SoftWindows is started. If a change to the SoftWindows environment is required, SoftWindows must be restarted before the change will take effect.

7: The hard disk is not writable – please check file name and permissions.

You do not have write permission for the hard disk file.

Verify that you have both read and write permission for the hard disk file.

If necessary use the Unix chmod command to modify the permissions to ensure that the user has proper access to the file.

8: The hard disk file is not a valid hard disk (disk geometry incorrect).

SoftWindows does not recognize the specified file as a valid hard disk file.

Verify that the correct path and filename have been specified for the hard disk file. If these are correct, the hard disk file may have been damaged. You should restore your hard disk file from backups if possible or create a new hard disk file.

10: The new hard disk file could not be created.

SoftWindows could not create the specified hard disk file.

Verify that you have write permission for the directory in which the hard disk file is to be created and that the file system has sufficient free space. If necessary, change permissions on the directory or specify a different location for the hard disk file.

11: The hard disk has been mounted read only because you do not have write permission for the file. Check the file permissions if you need to write to the disk.

You do not have write permission for the hard disk file.

If you need to write to the disk, modify the hard disk file permissions. If you do not need to write to the disk, consider using the optional configuration parameter RO_DISK_PANEL_DISABLE in your SoftWindows configuration file.

12: Internal error in SoftWindows procedure.

Contact Insignia Technical Support.

13: The host filesystem directory cannot be found.

SoftWindows cannot access the directory specified for an FSA drive.

Verify that the specified directory exists and that you have appropriate permissions on it. If the path contains an environment variable (such as $HOME), verify that it is set correctly in the environment when SoftWindows is started. If a change to the SoftWindows environment is required, SoftWindows must be restarted before the change will take effect.

14: The host filesystem name must be a directory.

The path specified for an FSA drive does not specify a directory.

Verify and correct the path. It must specify a directory or a symbolic link to a directory, not a regular file or a special file.

15: The host filesystem must have read access.

You do not have read access for the directory specified for an FSA drive.

Verify that you have appropriate permissions for the directory.

16: Floppy drive problem. SoftWindows cannot access the floppy device.

Verify the device name specified for the floppy drive and that the floppy drive is not mounted under Unix.

17: SoftWindows does not support a ROM BASIC.

A PC program has tried to use the ROM BASIC interpreter which was available on some early PCs.

Use QBASIC supplied with SoftWindows or another BASIC interpreter.

20: Drive C: & Drive D: cannot be the same file:

You have specified the same hard disk file for both the C: and D: drives.

Select a different hard disk file for one of the drives or select no D: drive by deleting the hard disk file name from the configuration.

21: The file named below is not a valid keyboard file.

SoftWindows does not recognize the file as containing valid keyboard mapping information.

Verify the path and filename for the mapping file. Normally these should refer to a file in $SWIN2HOME/keyboard, and the filename should end in .kbd.

If these are correct, the mapping file may be corrupted and should be re-installed.

23: The file named below is not accessible to SoftWindows.

Verify the path and filename and the permissions on both the directory and the file. If the path contains an environment variable (such as $HOME), verify that it is set correctly in the environment when SoftWindows is started. If a change to the SoftWindows environment is required, SoftWindows must be restarted before the change will take effect.

24: A continuous RESET state has been entered.

A PC program has caused the PC to continually reset. This may indicate a fault in the PC program, possibly due to a faulty installation.

Re-install your PC application and/or try running it on a real 486 PC.

25: Invalid Extended Memory size.

The configured Extended Memory size is greater than the maximum value permitted by the MEMORY_EXTENDED_MAX_SIZE entry in the system configuration file (sys.swin2config).

Reduce the configured Extended Memory size or increase the value of MEMORY_EXTENDED_MAX_SIZE in the system configuration file.

27: Invalid Autoflush Delay.

The configured Autoflush Delay is greater than the maximum value permitted.

Change the Autoflush Delay to a value in the range 1 to 300.

28: The window manager is not configured to display the requested video mode.

SoftWindows has been asked to display in a mode that is too large for the screen configuration.

If you are using a PC application that requests a high resolution video mode, configure it to use a lower resolution mode.

29: Serial Terminal problem. Graphics mode not available.

With SoftWindows running on a serial terminal, a PC application has attempted to use a graphics mode. Graphics modes are not available on serial terminals.

It may be possible to reconfigure the PC application to use text modes only. Otherwise you must use SoftWindows on an X display.

30: The SoftWindows resource file could not be created. (It will not be updated)

SoftWindows could not create the indicated file.

Verify that the directory is not write-protected. If necessary, change the permissions.

31: The SoftWindows resource file could not be updated. (Continuing will attempt to create the file in $HOME).

SoftWindows could not write to the indicated file.

Verify that the directory and file are not write-protected. If necessary, change the permissions.

32: The drive is not being used.

The NET USE X: /D command has been used on a drive which is not currently been configured as an FSA drive.

Verify that you have specified the intended drive in the NET USE command.

33: The drive is not a network drive.

The NET USE X: /D command has been used on a drive that is not an FSA drive.

Verify that you have specified the intended drive in the NET USE command.

34: The drive is already in use.

You have tried to set up an FSA drive which is already in use.

Verify that the intended drive is specified in the NET USE command. Use the NET USE X: /D command to disconnect the drive before setting it up.

Alternatively, use the Open Disk Drives dialog box to configure the FSA drive as required.

35: The host filesystem directory cannot be found.

SoftWindows cannot access the directory specified for an FSA drive.

Verify that the specified directory exists and that you have permission to access it. If the path contains an environment variable (such as $HOME), verify that it is set correctly in the environment when SoftWindows is started. If a change to the SoftWindows environment is required, SoftWindows must be restarted before the change will take effect.

36: The host filesystem directory must be a directory.

The path specified for an FSA drive does not specify a directory.

Verify the pathname and correct it if necessary. It must specify a directory, or a symbolic link to a directory, not a regular file or a special file.

37: The host filesystem directory must have read access.

You do not have read access for the directory specified.

Verify that you have appropriate permissions on the directory.

39: Illegal drive specification.

You have tried to set up an FSA drive beyond the value of LASTDRIVE set in CONFIG.SYS.

Change LASTDRIVE in CONFIG.SYS to a higher letter, or use a drive which is not greater that the value of LASTDRIVE.

40: The font files could not be opened by SoftWindows.

The X server cannot load fonts required by SoftWindows.

Make sure that the appropriate SoftWindows font directory can be read by the X server. To do this, execute the following commands before SoftWindows is started:

xset +fp $SWIN2HOME/fonts/dir R
xset fp rehash R

where dir is a directory which depends on the type of platform being used to display SoftWindows.

If you are displaying to a remote display or an X terminal, ensure that the appropriate font directory is mounted and can be read by the X server.

41: X Windows System compatibility problem. The visual class is other than StaticGray, GrayScale or Pseudocolor.

The X display does not support a visual class which SoftWindows requires for color or grayscale display.

Windows will operate in a monochrome mode only. This may be acceptable, depending on the application. For MS-DOS applications, you may be able to configure the application to operate in a mode that does not require color display. Otherwise, use an X display that provides an appropriate visual class.

43: Output error - SoftWindows was unable to write to the specified pipe. This was probably due to invalid parameters in the setup of a COM or LPT port. Selecting continue will disable this port to allow the problem to be corrected: 

SoftWindows failed to open a pipe and execute the command specified for the port.

Verify that the command is available to SoftWindows (via PATH or a fully specified directory), has appropriate permissions, and operates correctly when data is piped into its standard input.

44: The memory resources needed by SoftWindows could not be allocated. Select Continue to retry.

This is probably due to lack of available swap space. Shutting down other Unix programs may make more swap space available. If this message is often seen, consider increasing the swap space, or reducing the number of applications being run on the workstation.

46: SoftWindows cannot continue because the environment variable SWIN2HOME is not set.

Ensure that SWIN2HOME is set in the environment before SoftWindows is started. SWIN2HOME should be set to the full path of the directory in which SoftWindows is installed (such as /usr/SoftWindows2).

47: An installation file required by SoftWindows is missing, execution must terminate.

Verify that the SWIN2HOME is set in the environment, and indicates the correct directory for the SoftWindows installation. Also verify that $HOME is set to indicate the user's home directory. If these are both correct, the SoftWindows installation may be damaged. The indicated file may have to be restored from backups or SoftWindows may have to be re-installed.

48: A configuration file entry is duplicated or there is an unrecognized entry. You may select Default to ignore this entry, or type a correct entry name and value, then select Continue.

There is an invalid entry in $SWIN2HOME/sys.swin2config or $HOME/.swin2config.

Enter the correct value in the dialog or exit SoftWindows and correct the file using a text editor. If the error is in $HOME/.swin2config, the new value entered will take effect the next time the SoftWindows configuration is saved.

If the error is in $SWIN2HOME/sys.swin2config, this message will be displayed each time SoftWindows is started. In this case $SWIN2HOME/sys.swin2config should be edited using a text editor to correct the entry.

Whenever $SWIN2HOME/sys.swin2config is edited verify that it is owned by root and has the SUID bit set.

49: Serial terminal problem. Communications error while writing to terminal.

Verify that the terminal is correctly connected to the workstation, is configured correctly, and that the device is not being used by another Unix application.

50: The configuration file is missing from your home directory. Select Default and a copy will be made from the system defaults.

The file $HOME/.swin2config does not exist. This is normal the first time SoftWindows 2 is launched by each user, even if a previous version of SoftWindows has been used. No action is required. The file will be created the first time the SoftWindows configuration is saved using the Actions menu, or when SoftWindows is exited.

The new file will use default values from the system configuration file ($SWIN2HOME/sys.swin2config). If you have used a previous version of SoftPC or SoftWindows, you may want to copy some entries from your previous configuration file.

If you have used SoftWindows 2 before, and believe you have saved a configuration, verify that the value of $HOME is set correctly when SoftWindows is started.

51: The configuration file in your home directory cannot be written to by SoftWindows.

You cannot write the file because of a permissions problem or lack of available disk space.

Verify that the value of $HOME is set correctly and that you have permission to write to the directory. If the indicated file already exists, verify that you have write permission for that file. Verify that the filesystem containing your home directory is mounted with write permission and has sufficient free space on it.

52: Serial terminal problem. The port to which your serial terminal is trying to attach is already in use.

Another Unix process is using the serial terminal which you are trying to access. Identify the relevant process and stop it or disable its connection to the serial port. Alternatively, you may be able to use a different serial port with SoftWindows. Verify that there is no getty process running on this port. If there is, disable it by modifying the /etc/inittab file.

53: Serial terminal problem. The serial terminal port could not be opened.

Verify that you have used the correct serial terminal port device name and that you have both read-write permission to it. On many systems, the system administrator must change permissions on the device before it can be used by most users.

54: Serial terminal problem. SoftWindows cannot open the term info file to get the information for $TERM.

The terminal description file in $SWIN2HOME/term is corrupted.

Re-install SoftWindows or restore the terminal description file from backups.

55: The communications name is invalid.

The given device cannot be opened or is incompatible with SoftWindows.

Verify that the correct special device name has been given and that it has appropriate permissions. Normally the user must have read-write permission on the device. Verify that the Device Type is set correctly on the SoftWindows Comms Ports or Printer Ports dialog.

56: The configuration file in your home directory has an option with a bad value.

Edit the configuration file in your home directory (.swin2config) to correct the value.

57: The system default configuration file has an invalid value.

Edit the system default configuration file ($SWIN2HOME/sys.swin2config) to correct the value. After editing the file, verify that the file is owned by root and has the SUID bit set.

58: The system default configuration file has a duplicate or unrecognized entry.

Edit the system default configuration file ($SWIN2HOME/sys.swin2config) to correct the value. After editing the file, verify that the file is owned by root and has the SUID bit set.

59: The system default configuration file has a missing entry.

Edit the system default configuration file ($SWIN2HOME/sys.swin2config) to add the required entry. After editing the file, verify that the file is owned by root and has the SUID bit set.

60: The configuration file entry shown below has an invalid value. You may select Default to replace it with the system default value, or type a correct value and select Continue.

A value in your configuration file ($HOME/.swin2config) is invalid. If the error is continually given, there are two possible causes:

If the configuration entry refers to a floppy drive, CD-ROM drive, or communications port, another process or another copy of SoftWindows may already have that device open. In that case, you should delete the device name, or type in an alternative device name (if available), and select Continue, or disable the use of that device in the other process.

Alternatively, the system default configuration file ($SWIN2HOME/sys.swin2config) may have an invalid value in it. If this is the case, edit the file to correct the value. After editing the file, verify that the file is owned by root and has the SUID bit set.

61: The configuration file entry shown below is empty. You may select Default to use the system default value, or type a correct value and select Continue.

A required value is missing from your configuration file ($HOME/.swin2config).

If you enter a valid value and select Continue, or you select Default, the required entry will be automatically added to your configuration file the next time you save the SoftWindows configuration. If you select Exit, you should edit your configuration file ($HOME/.swin2config) to avoid the error recurring the next time SoftWindows is started.

62: SoftWindows cannot continue due to insufficient resources from the Native Language Support message catalogue.

SoftWindows cannot find the required text in its message catalogue.

The message catalog may be corrupted. The file should be restored from backups or SoftWindows should be re-installed. The message catalog file is $SWIN2HOME/nls/C/swin.cat. If the message catalog file is removed, SoftWindows will use English text by default.

65: SoftWindows could not find a lock daemon to protect the indicated file. We advise you to exit, and start the lock daemon. Continue only if you are sure that no other process will write to the file, and AT YOUR OWN RISK.

SoftWindows communicates with a lock daemon to ensure that files which it modifies are not being modified by another process, that is, another invocation of SoftWindows. This message indicates that SoftWindows failed to communicate with the daemon process.

Verify that the lock daemon, normally called lockd or rpc.lockd, is running on the workstation on which SoftWindows is running and on the workstation on which the indicated file is located.

If the indicated file is a hard disk file which SoftWindows must write to continually during normal operation, you should only continue if you are sure that it will not be modified by another process.

If a hard disk file is modified by two processes at the same time, it could be seriously damaged and you could lose the data on it. If the file is your configuration file ($HOME/.swin2config), which SoftWindows opens and writes to very quickly, then continuing is unlikely to damage the file, but it is still a possibility.

66: The date has been set forward, or the system frozen for a period. The PC date may be incorrect.

SoftWindows has detected that the time and date on the Unix system is significantly ahead of the time on the emulated PC. This may occur if the date on the Unix system has been changed, or if SoftWindows has been frozen by the Auto Freeze option for several hours.

If you are using an MS-DOS or Windows application that makes some use of the PC's time facilities, it may not operate as expected. This is not often a serious problem. If it causes difficulties with your application, avoid using the Auto Freeze option.

67: The date has been set backward. The PC date may be incorrect.

SoftWindows has detected that the time and date on the Unix system is behind the date on the emulated PC. This is usually due to the date having been changed backwards on the Unix system.

If you are using an MS-DOS or Windows application that makes some use of the PC's time facilities, it may not operate as expected. This is not often a serious problem. Restarting SoftWindows will synchronize the time again.

68: The file you have chosen for SoftWindows's floppy device is not a Character Special Device. All floppy device drivers must be Character Specials to work.

You have selected an invalid device name for the floppy drive.

Verify that the device name selected is correct. In particular, ensure that you have not selected a block special device name rather than a character special device name.

69: Could not allocate 256 colors for Windows.

You can try stopping other applications to free color resources, then press Continue or try to allocate 16 colors by pressing Default.

70: Could not allocate 16 colors for Windows.

You can try stopping other applications to free color resources, then press Continue or use another colormap by pressing Default.

71: The hard disk is being mounted read-only because it is being accessed by another user:

While a SoftWindows hard disk file is being used by a SoftWindows session, and can be written to, a lock is maintained on it. Only one SoftWindows process can hold the lock at any one time, thus preventing the hard disk file being corrupted.

If you must write to the hard disk, you must ask the other user to release the lock on it by exiting the SoftWindows session or by deactivating the drive by selecting Activate from the Options menu. Deactivating a SoftWindows hard disk causes it to release the lock and become read-only.

Now Activate the disk or restart SoftWindows on the session which must write to the disk.

72: The hard disk is being mounted read-only. Either it is being accessed by an unknown user or there is no lock daemon running on your machine.

SoftWindows could not identify the user who is using a hard disk file or cannot communicate with the lock daemon.

There may be a problem with the lock daemon. It may need to be restarted.

73: SoftWindows was unable to open the default terminal description file:

SoftWindows cannot open the file $SWIN2HOME/term/ansi (HP and SPARC products).

This file should be restored from backup, or SoftWindows should be re-installed.

74: SoftWindows was unable to open the terminal description file. Press continue to use the default below.

SoftWindows could not load the terminal description file for the type of terminal specified. An attempt can be made to continue, using a default terminal description file.

Verify that you have specified the correct terminal type on the SoftWindows command line and that the corresponding terminal description file is in the $SWIN2HOME/term directory.

75: A configuration file entry is duplicated or there is an unrecognized entry. You may select Default to ignore this entry, or select Edit to alter the configuration file.

Your configuration file ($HOME/.swin2config) has an invalid entry.

Select Edit to correct the error. If you do not correct the error now, the configuration file will be corrected the next time the configuration is saved.

76: An error occurred processing the configuration file entry shown below. You may select Default to replace it with the system default value, or select Edit to alter the configuration file.

Your configuration file ($HOME/.swin2config) has an invalid entry.

If the system default value is acceptable, select Default. Otherwise select Edit to correct the configuration file entry.

77: The configuration file entry shown below is empty. You may select Default to use the system default value, or select Edit to alter the configuration file.

The indicated entry is missing from the configuration file ($HOME/.swin2config).

If the system default value is acceptable, select Default. Otherwise select Edit to enter a suitable configuration file entry.

78: SoftWindows requires 256 modifiable colormap entries for full emulation of PC graphics adaptors. On this display, SoftWindows can provide only a black and white approximation, which may make some graphics programs hard to use.

Your display does not have sufficient colors available for SoftWindows to correctly emulate PC graphics adaptors.

If you are using a color display and have other Unix applications running which use many colors, close down those applications before starting SoftWindows. This may allow sufficient colors to be made available to SoftWindows for normal color operation.

If your PC application is difficult to use in SoftWindows' black and white mode, it may be possible to configure the PC application to use a monochrome display mode, making it easier to use. Alternatively, use a different X display workstation.

80: An unexpected file system error occurred while reading from a container file. Pressing Continue will retry the operation that failed.

SoftWindows is unable to read the hard disk file used as the C: or D: drive.

In a Unix terminal window, verify that the file is still accessible. If the hard disk container file is on a file server, not the workstation, verify that the file server has not crashed and is operating correctly. Also verify that the network connection between the workstations is operating correctly.

81: An unexpected file system error occurred while writing to a container file. Pressing Continue will retry the operation that failed.

SoftWindows is unable to write to the hard disk file used as the C: or D: drive.

In a Unix terminal window, verify that the file is still accessible. If the hard disk container file is on a file server, not the workstation, verify that the file server has not crashed and is operating correctly. Also verify that the network connection between the workstations is operating correctly.

82: SoftWindows has encountered a problem with the licensing system.

SoftWindows cannot find a valid license.

User: Verify that LM_LICENSE_FILE is set in your environment when SoftWindows is started. The value should normally be install/FLEXlm/license.dat, where install is the SoftWindows installation directory, although a different value may be required depending on how the licensing system is configured. Verify the correct value with your system administrator.

Administrator: Verify that you have a valid SoftWindows license and that it has not expired. Your FLEXlm license file should contain a FEATURE line for Insignia_SoftWindows, and a DAEMON line for the insignia daemon. If you are using local licensing, verify that both lmgrd and insignia daemons are running, and are using the correct license file. Verify that the value of LM_LICENSE_FILE indicates this same license file when SoftWindows is started.

If you are using a remote license server, verify that both lmgrd and insignia daemons are running on it and are using the correct license file.

Verify that when SoftWindows is started, the value of LM_LICENSE_FILE indicates the correct license server name and TCP port number in the form port@host, for example, 744@licserv. Verify that the network connection is operating correctly between the license server and workstation.

Verify that the date and time are set correctly on both the license server and the workstation on which SoftWindows is to be run.

83: Your current SoftWindows license has expired. Apply to your SoftWindows dealer for a full license.

A SoftWindows 2 license has been found, but it has expired.

Apply to your SoftWindows dealer for a full license.

84: This copy of SoftWindows has lost its license. It will run for a further 5 minutes to allow you to save your work, and will then exit.

The connection to the license server daemon has been lost. This normally indicates that the license server has crashed or the network connection to it is not operating correctly.

Immediately save work and exit from your Window or MS-DOS applications. Quit the applications cleanly, and exit from Windows. This will minimize the possibility of data being lost.

The system administrator should verify operation of the license server, the lmgrd and insignia daemons, and the network connection between the license server and the workstation on which SoftWindows is being run. It will not be possible to restart SoftWindows until the licensing server can be accessed correctly.

88: All licensed SoftWindows are already running. Please contact your Customer Service Representative.

You are already running the full number of copies of SoftWindows for which you have licenses installed.

Purchase and install additional SoftWindows licenses or close down an existing invocation of SoftWindows before starting the new one.

89: A concurrent license must be installed on the server machine.

You are installing a concurrent license, but you are not running SoftWindows on the license server. Run SoftWindows on the license server in order to install the license or enter the license information by editing the license file directly.

90: Failed to start the lmgrd daemon. Please run again to retry.

SoftWindows could not start up the license daemon lmgrd.

Verify that the license daemon executable ($SWIN2HOME/FLEXlm/lmgrd) is installed and has read and execute permissions set correctly. The daemon may have failed to start due to some general resource problem on the workstation, such as the maximum number of processes being exceeded or the workstation memory or swap space being full. If you suspect that may be the case, try shutting down other processes before starting SoftWindows.

91: Failed to update the /etc/inittab file.

SoftWindows must update the file /etc/inittab to ensure that the licensing daemon starts when the workstation is booted. It was unable to do so.

Edit the /etc/inittab file or another startup script to ensure that the licensing daemon is started when the workstation starts up. The SoftWindows line in /etc/inittab is:

isl:234:respawn:install/FLEXlm/lmgrd -c install/FLEXlm/license.dat >> install/FLEXlm/license.log 2>&1

where install is the SoftWindows installation directory.

92: Failed to update the license file.

SoftWindows was unable to create or modify the license file $SWIN2HOME/FLEXlm/license.dat.

The Unix error message indicating the type of problem is displayed. This information should enable the system administrator to address the problem.

93: This version of the SoftWindows display driver cannot run in Enhanced mode. Please install the version supplied with SoftWindows.

The file SPCMSWD.DVR in your Windows installation is incompatible with the version of SoftWindows you are using.

Update SPCMSWD.DVR to the version supplied with your SoftWindows distribution ($SWIN2HOME/windows).

94: Too many programs EXEC'ing other programs. (Max depth:10)

SoftWindows has a fixed limitation on the number of licensed MS-DOS applications which can be nested. This limit has been exceeded. This occurs when the application has been used to start another licensed MS-DOS application, which may be a copy of itself, which in turn starts another application, and so on.

If there are several executables forming a single application which have all been licensed separately, licensing must be removed from one or more of the executables to enable the application to operate correctly.

95: The license for this application is out of date.

The expiry date for a licensed MS-DOS or Windows application has passed.

Update the license for the application to have a new expiry date. Alternatively, restrict users from using that application, or that version of the application.

96: All licensed copies of this application are already running.

The maximum number of licensed copies of the MS-DOS or Windows application are already in use.

User: Have another user of the MS-DOS or Windows application quit the application before you try to start it. Otherwise, contact your system administrator.

Administrator: Update the license for the application to have a new maximum number of users. Depending on your reasons for licensing the application, this may require you to purchase further licenses from the application vendor.

97: Failed to update the /etc/rc.local file.

SoftWindows must update the file /etc/rc.local to ensure that the licensing daemon starts when the workstation is booted. It was unable to do so.

Edit the /etc/rc.local file or another startup script to ensure that the licensing daemon is started when the workstation starts up.

The required section in /etc/rc.local is of the form:

#
# Start up the SoftWindows FLEXlm license Server
#
if [ -f %s ]; then
echo Starting SoftWindows FLEXlm license service server >/dev/console
install/FLEXlm/lmgrd -c install/FLEXlm/license.dat | logger -p auth.notice &
fi

where install is the SoftWindows installation directory.

98: Cannot overwrite the current C: drive.

The filename entered for the new hard disk already exists and is being used as the C: drive.

The C: drive hard disk file must not be overwritten in this manner. Select another filename for the new hard disk or use a different file for the C: drive when creating the hard disk.

99: This exists and is a directory, please enter a file name.

The name given for a new hard disk file exists and is a directory. Select another name for the new hard disk.

100: There was an error starting the Help system. Help is unavailable.

SoftWindows could not start up the HyperHelp On-line Help system.

Verify that the help system is installed in $SWIN2HOME/hyperhelp, and that $SWIN2HOME/hyperhelp/bin/hyperhelp has suitable read and execute permissions.

If SWIN_USEHHENV is set in the environment, verify the values of other environment variables used by HyperHelp, and ensure that there is a valid HyperHelp installation in the directory indicated by $HHHOME.

101: The Help package has not been installed. Help is unavailable.

SoftWindows cannot find the HyperHelp viewer executable.

Verify that the help system is installed in $SWIN2HOME/hyperhelp, and that $SWIN2HOME/hyperhelp/bin/hyperhelp has suitable read and execute permissions.

If SWIN_USEHHENV is set in the environment, verify the values of other environment variables used by HyperHelp, and ensure that there is a valid HyperHelp installation in the directory indicated by $HHHOME.

102: The environment variable SWIN2HOME points to an insecure installation. $SWIN2HOME/sys.swin2config must be owned by root and have the Set User ID bit set.

The SoftWindows system configuration file does not have correct ownership and permissions. This indicates that the SoftWindows installation has been copied or modified.

Login as root on the workstation where SoftWindows is installed. Set ownership and permissions on the file as follows:

cd $SWIN2HOME
chown root sys.swin2config
chmod 4644 sys.swin2config

103: The SoftWindows processor has halted. Please Restart SoftWindows

An MS-DOS or Windows application has caused the emulated 80486 processor to enter a state in which it cannot process further instructions for example, an HLT instruction with all interrupts disabled. On a real PC this would lock up the PC.

Restart SoftWindows from the Actions menu.

1001: Unable to open Native Language Support catalog, defaulting to English.

SoftWindows cannot access the file $SWIN2HOME/nls/C/swin.cat. This file is the Native Language Support Catalog, required for SoftWindows messages.

Verify that $SWIN2HOME/nls/C/swin.cat is installed and readable by SoftWindows. If you have LANG set in your environment, set it to C before starting SoftWindows.

1002: Serial terminal problem. SoftWindows cannot communicate with the terminal.

SoftWindows cannot access the terminal you are using.

Verify that you have read and write permissions on the serial terminal device.

1003: Serial terminal problem. SoftWindows cannot select the terminal. Fatal problem with communications to the serial terminal.

SoftWindows cannot access the terminal you are using.

Verify that you have read and write permissions on the serial terminal device.

1004: The device specified is not a valid special character device.

The file name given as the CDROM device or COM port is not a character device.

Verify that you have specified the correct device name.

1005: Command not found

SoftWindows cannot execute the Unix command you have specified as a pipe command.

Verify that the command name is spelled correctly, and that it has read and execute permissions. Verify that the command is accessible through the PATH set in your environment.

If the command is not accessible, either modify the PATH before starting SoftWindows or specify the full Unix path to the command in the SoftWindows Comms Port or Printer Port dialog box.

1006: The file needed by the port adapter is already being accessed.

The file name given for use with a comm port or printer port is already in use by a Unix process and cannot be used by SoftWindows. This may occur if you have specified the same filename for more than one comm port or printer port or if you have another invocation of SoftWindows using the same filename.

Close down the Unix process using the file or select an alternative filename.

1007: SoftWindows does not have access to the CDROM device name.

The user does not have read permission for the CD-ROM device.

Verify that you have read permission for the CD-ROM device. If necessary, use the Unix chmod command to modify the permissions. Verify that you have specified the correct device name.

1008: Your system is low on swap space.

Continuing without increasing available memory may make programs fail unexpectedly.

Increase the swap space or shut down some Unix applications to increase the available memory.

1009: Your system is running a version of OpenWindows prior to 3.0. SoftWindows is only supported on 3.0 and may behave incorrectly if you continue.

The X Server used to run SoftWindows is not supported by SoftWindows.

Upgrade your X server to the recommended version or run SoftWindows on another display.

1010: The Unix command linked to a COM or LPT port has failed. All port operations are halted.

The process being used for a COM port or printer has died and no more data can be output to this process.

Verify that the command being used is valid and that it is functioning correctly.

To verify the operation of commands being used to pipe comms or printer port information, it may be useful to first configure the comms or printer port to write to a file, output the required data (for example print data) to the file, then run the required pipe command at a Unix shell prompt, using the file as input. This also allows you to examine the data in the file to verify that it appears as expected.

Using this method, ensure that all of the data is flushed to the file. To do this enable automatic flushing from the Options menu, flush the port from the Actions menu, or exit SoftWindows.

1021: Unable to open the host's network interface.

The SoftWindows ODI driver has tried to access the host's low level networking device and has been unsuccessful. The network device is either not installed or SoftWindows does not have the correct permissions to open the device. SoftWindows will be unable to use PC networking if this error occurs.

Verify that the host's network device is installed and configured correctly.

Verify that no other Unix applications are using the network device.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

1022: Unable to configure the host's network interface.

The SoftWindows ODI driver has tried to configure the host's low level networking device and has been unsuccessful. SoftWindows will be unable to use PC networking if this error occurs.

Verify that the host's network device is installed and configured correctly.

Verify that no other Unix applications are using the network device.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

1023: Unable to enable packet filtering.

The SoftWindows ODI driver could not enable the low level network packet filtering algorithms needed. SoftWindows will be unable to use PC networking if this error occurs.

Verify that the host's network device is installed and configured correctly.

Verify that no other Unix applications are using the network device.

Verify that the SoftWindows NET.CFG file has no illegal PROTOCOL entries.

1024: Unable to flush the host's network interface.

The SoftWindows ODI driver could not flush the low level network device. SoftWindows may not be able to use PC networking if this error occurs.

Verify that the host's network device is installed and configured correctly.

Verify that no other Unix applications are using the network device.

1025: Unable to read the host's network address.

The SoftWindows ODI driver could not access the host's network address. SoftWindows will be unable to use PC networking if this error occurs.

Verify that the host's network device is installed and configured correctly.

Verify that no other Unix applications are using the network device.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

1026: Unable to enable a SIGIO handler.

The SoftWindows ODI driver could not redirect the host's SIGIO interrupt vector. SoftWindows can be used to access PC networks if this error occurs, but the overall networking performance will be poor.

Verify that the host's network device is installed and configured correctly.

Verify that no other Unix applications are using the network device.

1027: Unable to bind to the host's network provider.

The SoftWindows ODI driver has tried to configure the host's low level networking device but has been unsuccessful. SoftWindows will be unable to use PC networking if this error occurs.

Verify that the host's network interface is installed and configured correctly.

Verify that no other Unix applications are using the network device.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

1028: Unable to attach to the host's network provider.

The SoftWindows ODI driver has tried to configure the host's low level networking device and has been unsuccessful. SoftWindows will be unable to use PC networking if this error occurs.

Verify that the host's network interface is installed and configured correctly.

Verify that no other Unix applications are using the network device.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

1029: Unable to enter host network's promiscuous SAP mode.

The SoftWindows ODI driver could not enter Promiscuous SAP mode. SoftWindows will be unable to use PC networking if this error occurs.

Verify that the host's network device is installed and configured correctly.

Verify that no other Unix applications are using the network device.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

1030: Unable to retrieve the host interface's physical location (PPA).

The SoftWindows ODI driver could not find the correct network device to use. SoftWindows will be unable to use PC networking if this error occurs.

Verify that the host's network device is installed and configured correctly.

Verify that no other Unix applications are using the network device.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

1031: Unable to close host's network interface.

The SoftWindows ODI driver could not close the host's network device. SoftWindows may not be able to use PC networking when next used.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

1032: Unable to add protocol to network interface.

The SoftWindows ODI driver could not assign the requested protocol. SoftWindows will be unable to use PC networking if this error occurs.

Verify that the SoftWindows NET.CFG file has no illegal PROTOCOL entries.

Verify the supported protocols for this SoftWindows platform.

Verify that no other Unix applications are using the network device.

1033: Unable to delete protocol from network interface.

The SoftWindows ODI driver could not remove the previously assigned protocol. SoftWindows may not be able to use PC networking when next used.

Verify that the SoftWindows NET.CFG file has no illegal PROTOCOL entries.

Verify the supported protocols for this SoftWindows platform.

Verify that no other Unix applications are using the network device.

1034: Unable to transmit packet onto network cable.

The SoftWindows ODI driver could not transmit a packet onto the network. SoftWindows may be unable to use PC networking if this error occurs.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

Verify that the host's network device is configured correctly.

Verify that no other Unix applications are using the network device.

Verify that the protocol that you are using is supported by SoftWindows on this platform.

1035: Partial packet received from host's network interface.

The SoftWindows ODI driver did not receive a full packet when one was expected. Network based files/data may become corrupted if this error occurs.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

Verify that the host's network device is configured correctly.

Verify that no other Unix applications are using the network device.

1036: Unable to enter promiscuous mode.

The SoftWindows ODI driver could not enter Promiscuous mode. This could be due to a limitation of the host's network device, or a runtime system error. SoftWindows can continue to use PC networking, but the application which requested promiscuous mode may not work as expected.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

Verify that the host's network device is configured correctly.

Verify that no other Unix applications are using the network device.

1037: Unable to exit promiscuous mode.

The SoftWindows ODI driver could not leave Promiscuous mode. SoftWindows can continue to use PC networking, but the overall networking performance will be poor.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

Verify that the host's network device is configured correctly.

Verify that no other Unix applications are using the network device.

1038: Unable to add multicast address.

The SoftWindows ODI driver could not assign the requested multicast address. SoftWindows can continue to use PC networking but the application which requested the particular multicast address may not work as expected. This could be due to the multicast address already being enabled, or to a general inability to assign these addresses.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

Verify that the host's network device is configured correctly.

Verify that no other Unix applications are using the network device.

1039: Unable to delete multicast address.

The SoftWindows ODI driver could not remove the requested multicast address. SoftWindows can continue to use PC networking but will continue to receive all packets for that particular multicast address.

Verify that the SoftWindows executable is owned by root and has the SUID bit set.

Verify that the host's network device is configured correctly.

Verify that no other Unix applications are using the network device.