MKMSGF ?HCause: The version of the base operating system currently installed is not compatible with the version of OS/2 Peer being installed. Action: Install OS/2 2.0 or above and then reinstall OS/2 Peer. HCause: The installation/configuration program is already running. You cannot start the installation/configuration program again at this time. Action: Run only one copy of the installation/configuration program at a time. HCause: The installation/configuration program is unable to continue because there is not enough hard-disk space on this workstation. Action: Make hard-disk space available on this workstation by moving or deleting files, and then try the installation again. HCause: The installation/configuration program is unable to open or read this required file, or you have not logged on with sufficient privilege to allow this required file to be copied. Action: Make a new copy of the product diskettes and try the installation again, or log on with sufficient privilege and then try the installation again. HCause: The installation/configuration program is unable to load this dynamic link library (DLL). Action: Make a new copy of the product diskettes and try the installation again. HCause: The locked-file device driver is unable to continue because there is not enough hard-disk space on this workstation. Action: Make hard-disk space available on this workstation by moving or deleting files, and then start the workstation again. HCause: This error code indicates that OS/2 Peer has detected a parameter that is not correct. The installation command syntax is: [d:\path\]LANINSTR {/PEER} [/R:d:\path\filename /G:d:\path /L1:d:\path\filename /L2:d:\path\filename] where: /PEER Specifies you are remotely installing OS/2 Peer code. /R Specifies the fully qualified file name of a response file. /G Specifies the fully qualified path of a directory containing files that are included by the response file. /L1 Specifies the fully qualified file name of an error log file. /L2 Specifies the fully qualified file name of a history log file. Action: Try the command again using the correct parameters. HCause: You have not logged on with sufficient privilege to allow the files to be copied to the fixed disk on this workstation. Action: Log on with sufficient privilege and then try the installation again. HCause: The value you specified for REMOTE_INSTALL_STATE is not valid. Action: SET REMOTE_INSTALL_STATE=. Then try the installation again. HCause: The installation/configuration program could not initialize history and error logging because it could not access the specified file. Action: Ensure that the file name specified is correct and that you have access privileges for the file. Then try the installation again. ?????????????????????????????????????????????????????????????????????????????????????????HCause: An error occurred while writing to the log file. Logging to that file was disabled, but the installation/configuration program was allowed to continue. The error may have been caused by the loss of LAN connectivity, lack of hard-disk space, or lack of access to the log file. Action: Verify that a LAN connection exists and that enough hard-disk space is available. Also make sure the user has the proper access permissions to the log file and that no other programs are trying to write to the log file at the same time. HCause: The module specified completed unsuccessfully with a return code. The return code may be module-specific. Action: Contact your network administrator for assistance. HCause: IBMLANLK detected errors while processing the following commands. The commands did not complete successfully. Action: Verify that there is enough hardd-disk space available and that the user has the proper access permissions to perform the commands listed; then try the installation again. HHHCause: The file specified on the /B parameter does not have the format required to restore ACLs. Action: Specify the correct file name on the /B parameter or correct the format of the specified file. HCause: An error occurred because of a request made to the operating system. Action: Type Help followed by the error number to determine the cause of the error. HCause: The APIs are not on this workstation or their path is not in LIBPATH in CONFIG.SYS. Action: Verify that the LIBPATH statement in CONFIG.SYS contains a pointer to the APIs. If you are using the 386 boot diskette, make sure that the APIs have been copied to the fixed disk. HCause: There is an error in the command syntax. Action: Type the command followed by a ? to display the proper syntax. HCause: The file or subdirectory specified on one of the command parameters could not be found. Action: Reissue the command with the proper file or subdirectory name. HCause: The operating system returned an error on a file request for the specified file. Action: Type Help followed by the error number to determine the cause of the error. HCause: A request to create the specified file or subdirectory failed. Action: Ensure that the proper file or subdirectory was specified and that you have the proper authority to create the file or subdirectory. HCause: The required amount of disk space is not available on the specified drive. Action: Move or erase files to increase the available disk space or specify a different drive.