Arawak OS/2 Shareware

home *** CD-ROM | disk | FTP | other *** search

/ Arawak OS/2 Shareware / PAKLED.ISO / network / lanserv / us7001d1.dsk / IP07001.INF (.txt) < prev next >

Wrap

OS/2 Help File | 1993-07-27 | 46.7 KB | 1,452 lines

ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ IBM OS/2 LAN Server 3.0 ServicePak IP07001 IBM PTF IP07001 This ServicePak applies to: IBM OS/2 LAN Server Version 3.0 - Entry For use with OS/2 2.0, OS/2 2.0 with XR06055, or OS/2 2.1 IBM OS/2 LAN Server Version 3.0 - Advanced For use with OS/2 2.0 with XR06055 or OS/2 2.1 It also includes fixes for OS LAN Requester, DOS LAN Requester, and DOS LAN Requester Windows Warning: The Installation procedures for this ServicePak are significantly different from previous Corrective Service Diskettes. Please review the entire Installation section before proceeding. Service to Servers which use "Advanced Features" can be particularly arduous. Good Insurance! Have appropriate Bootable Standalone Service Diskettes. ΓòÉΓòÉΓòÉ 1.1. Affected SYSLEVEL Files ΓòÉΓòÉΓòÉ SYSLEVEL.SRV IBM OS/2 LAN Server SYSLEVEL.REQ IBM OS/2 LAN Requester SYSLEVEL.MUG IBM OS/2 User Profile Management SYSLEVEL.UPE IBM OS/2 User Profile Management - Extended SYSLEVEL.RPL IBM OS/2 LAN Server - Remote IPL Service ΓòÉΓòÉΓòÉ 1.2. Trademarks ΓòÉΓòÉΓòÉ The following are trademarks of IBM Corporation: o IBM o OS/2 o Operating System/2 o Presentation Manager The following are trademarks of other Corporations: o AppleTalk (Apple Computer) o Lotus 1-2-3 (Lotus Development Corporation) o Macintosh (Apple Computer) o Microsoft (Microsoft Corporation) o Windows (Microsoft Corporation) o Ungerman-Bass (Ungerman-Bass, Inc.) ΓòÉΓòÉΓòÉ 2. Installation ΓòÉΓòÉΓòÉ Installing the ServicePak is essentially a three phase process: Phase 1 - Quiesce the Target System Render the system serviceable by insuring that there will be no Locked Files during the install phase. Phase 2 - Install the ServicePak Select one of the following methods to replace system files with those provided on this ServicePak. Full Install Selective Install Redirected (CID) Install Phase 3 - Return the Serviced System to Normal Operation Perform a normal system boot. Also, Post Installation Procedures may be necessary to update Remote IPL images or DOS LAN Requester clients. Note: LAN Server 3.0 may have installed files in \MUGLIB with directory entries reflecting the installation time and date. When the Corrective Service Facility prompts for permission to overwrite a "file that has a later date than the file supplied with the service diskettes", select "Replace the file". ΓòÉΓòÉΓòÉ 2.1. Full Install ΓòÉΓòÉΓòÉ This method will apply all fixes to all partitions and directories: It is the simplest and safest method to Install ServicePaks to systems that do not have multiple versions of the product being serviced. It does require booting from diskette to insure that there are no Locked Files during the install phase. 1. Boot from the Bootable Standalone Service Diskettes 2. Establish A: as the Current Directory. 3. Replace the Boot Diskette with ServicePak diskette #1. 4. At the A: prompt type "FSERVICE" and press Enter. 5. At the panel titled "Updating Default Directories" press Enter (Option 1) 6. Follow the prompts provided by the Installation Aid. 7. Reboot the system normally. ΓòÉΓòÉΓòÉ 2.2. Selective Install ΓòÉΓòÉΓòÉ This method will apply fixes to selected subsystems, partitions, and directories: The Installation Aid will check for Locked Files. 1. Boot the system from fixed-disk. 2. Insert ServicePak diskette #1 in the A drive. 3. Establish A: as the Current Directory. 4. At the A: prompt type "SERVICE" and press Enter. 5. Make selections from the panel. If the Locked Files panel with the Reboot push button is presented, continue with the following steps. Otherwise go to the last step. 6. Chose "Reboot". 7. Perform the system Shutdown procedure. 8. Boot from the Bootable Standalone Service Diskettes. 9. Establish A: as the Current Directory. 10. Replace the Boot Diskette with ServicePak diskette #1. 11. At the A: prompt type "FSERVICE" and press Enter. 12. Follow the prompts provided by the Installation Aid. 13. Reboot the system normally. ΓòÉΓòÉΓòÉ 2.3. Redirected Installation (CID) Method ΓòÉΓòÉΓòÉ This method is useful for those who are using the CID (Configuration, Installation, and Distribution) Services as provided by IBM NTS/2. The Full Install or Selective Install methods are recommended for Servers exploiting 386 HPFS function; Fault Tolerance and/or Access Control Lists. While setting up a CID server is beyond the scope of this document, we have provided a sample LAN CID Utility REXX Command file (LS30SP.CMD) that may prove useful in setting up a CID server for this ServicePak. The sample LS30SP.CMD assumes the following: o LS30SP.CMD must reside in the ..\CLIENT subdirectory. o The ServicePak files are place on the code server using "XCOPY A:\*.* /S" (or equivalent) at 'x:\csd\ls30' where 'x:' is the drive seen by the client. o The following directory structure contains the ServicePak contents. csd\ls30\ * Root directory of ServicePak csd\ls30\FIX * No files csd\ls30\FIX\SRV * Server Fixes csd\ls30\FIX\REQ * Requester Fixes csd\ls30\FIX\MUG * User Profile Management Fixes csd\ls30\FIX\UPE * Extended UPM fixes o A log directory exists at 'x:\log\csd\ls30' for the log files ΓòÉΓòÉΓòÉ 2.4. Bootable Standalone Service Diskettes ΓòÉΓòÉΓòÉ Sometimes it becomes necessary to boot from diskette in order to perform certain operations on fixed-disk, like installing this ServicePak or running CHKDSK /f. All necessary files must be contained on diskette. Files from the fixed-disk should not be referenced in A:\CONFIG.SYS or A:STARTUP.CMD. Otherwise Locked Files can still exist on the fixed-disk. Should the need arise to boot from diskette for any reason, you may: o Use the Install diskette and Diskette #1 of OS/2 2.x. Escape to A: o Create custom Bootable Standalone Service Diskettes from your licensed materials. The makeup of these is dependent on the system to be serviced. Instruction is available for: Requesters and Entry Versions Servers. Advanced Version Servers. CAUTION: LAN Servers that utilize the Advanced features, Access Control Lists or Fault Tolerance must use custom Bootable Standalone Service Diskettes. Regular HPFS boot diskettes, such as the OS/2 Installation diskettes, CAN NOT mirror changes to Fault Tolerance partitions or access files/directories which are controlled by access control profiles. ΓòÉΓòÉΓòÉ 2.4.1. Making OS/2 2.x Bootable Diskettes ΓòÉΓòÉΓòÉ 1. Make a copy of the OS/2 2.x Installation Diskette & Diskette #1. Call them SA#1 and SA#2 respectively. 2. Delete SYSINST2.EXE from Diskette SA#2. 3. Delete BUNDLE from Diskette SA#2 (this will be on OS/2 2.1 only) 4. Modify CONFIG.SYS on SA#2 as follows: buffers=50 memman=noswap protshell=a:\cmd.exe protectonly=yes libpath=a:\; ifs=hpfs.ifs /c:64 set path=a:\; set dpath=a:\; 5. Copy UHPFS.DLL from OS/2 Diskette #2 or C:\OS2\DLL to SA#2 ΓòÉΓòÉΓòÉ 2.4.2. Making Advanced Server Bootable Diskettes ΓòÉΓòÉΓòÉ MAKEDISK is an Advanced Server utility designed to make the necessary Bootable Standalone Service Diskettes used in periodic maintenance of 386 HPFS systems. 1. Create a Backup copy of the OS/2 2.x Install Diskette. This is Boot Diskette and is used unaltered. 2. Create a Backup copy of OS/2 2.x Installation/Diskette 1. This is Boot Diskette 2. 3. With Boot Diskette 2 in drive a: or b: run MAKEDISK from an OS/2 prompt. Note: Syntax is MAKEDISK /BOOTDRIVE:d where d is the drive on which OS/2 2.x is installed. For additional Information see the Network Administrators Reference: Creating a 386 HPFS Boot Diskette, or LAN Server Utilities 4. If using Fault Tolerance, add the Fault Tolerance files to the Bootable Diskette. 5. Verify that the 386 HPFS Bootable Standalone Service Diskette works properly. o Shutdown the system o Insert the Bootable Standalone Service Diskette in the A drive. o Reboot the system (Ctrl+Alt+Del, or other method) o Determine if Local Security is working o Determine if Fault Tolerance is working. ΓòÉΓòÉΓòÉ 2.4.3. Adding Fault Tolerance to 386 HPFS Standalone Boot Diskette ΓòÉΓòÉΓòÉ 386 HPFS Standalone Boot diskettes require additional customizing in order to properly update files on partitions which are mirrored. The following steps may have to be done for each LAN Server with Fault Tolerance since the configuration information transferred in step 3 can be unique for each such system. 1. Copy the following four Fault Tolerance files from the first diskette of the LAN Server 3.0 ServicePak to your Bootable Standalone Service Diskette. 1) DISKFT.SYS 2) FTD.MSG 3) FTATTRIB.EXE 4) FTCOPY.CMD 2. Add the following line to the CONFIG.SYS on the Bootable Standalone Service Diskette. DEVICE=DISKFT.SYS 3. At an OS/2 command prompt, make the current drive A:, and have the 386 HPFS Bootable Standalone Service Diskette in drive A. Type "FTCOPY" to copy the customized Fault Tolerance configuration information to the 386 HPFS Bootable Standalone Service Diskette. Warning: Test your 386 HPFS Bootable Standalone Service Diskette before you make any alterations to your system. This Diskette is the Master Key should your system ever fail to boot from its hard drive. ΓòÉΓòÉΓòÉ 3. Post Installation Procedures (Optional) ΓòÉΓòÉΓòÉ Servers used for Remote IPL or DOS Lan Requester Image Support need additional consideration. ΓòÉΓòÉΓòÉ 3.1. Updating Remote IPL Servers ΓòÉΓòÉΓòÉ If the Server is intended to Remote IPL OS/2 2.00.1 or OS/2 2.1, then the following steps are necessary. 1. Run RPLS7001.CMD from Diskette 1 of the ServicePak to: o Create the Remote IPL directories and files used to RIPL OS/2 2.00.1 (DEFALT2A). o Create the Remote IPL directories and files used to RIPL OS/2 2.1 (DEFALT21). o Update the DEFALT21.FIT file to reflect the server name. o Update and copy the OS/2 2.1 WINOS2 *.INI and *.GRP files to the correct default directory o Create the OS/2 2.1 RIPL configuration files (*.CNF) o Update RPL.MAP to add server records for the new *.CNF files 2. Start the Server 3. Logon On with Administrator Authority 4. Run GETRPL.EXE to: o Migrate RPL.MAP workstation and server records from previous levels of LAN Server into the RPL.MAP on the current Remote IPL Server. o Move DOS Remote IPL users from previous levels of LAN Server into a group called RPLGROUP and create an access control profile for RPLGROUP granting all privileges to the users in that group. o Ensure that new OS/2 and DOS Remote IPL users added with LAN Server 3.0 are added to the group. o Create the default OS2.INI, OS2INI.20, OS2SYS.INI and OS2SYINI.20 files. CAUTION: DO NOT run RPLSETD.CMD until the steps above have been completed. ΓòÉΓòÉΓòÉ 3.2. Upgrading DOS LAN Requesters (DLR) ΓòÉΓòÉΓòÉ A SelectPak (IP07003) is available for DOS LAN Requester. It can be used to update the DLR files located in \IBMLAN\DOSLAN\NET which can subsequently be copied to DLR workstations using UPGRDLR.BAT. For detailed information see Network Administrators Reference Volume 1 "Upgrading DOS LAN Requester", ΓòÉΓòÉΓòÉ <hidden> Locked Files ΓòÉΓòÉΓòÉ Sometimes it is essential that programs own (become the master of) system resources such as Memory Blocks, Communication Ports, and Files. When a program stakes claim to a file, that file is said to be Locked; no other program is allowed to alter (replace or write to) it until the owning program explicitly removes the lock. .DLL Files can become Locked by residing in a directory that is included in the LIBPATH string of CONFIG.SYS. For example, NETAPI.DLL can be locked when \MUGLIB\DLL exists in the LIBPATH of CONFIG.SYS. ΓòÉΓòÉΓòÉ <hidden> Minimum Config.Sys ΓòÉΓòÉΓòÉ A Minimal CONFIG.SYS must contain sufficient information to start the desktop, access the file system, and little more. o Keep the IFS=386HPFS. o Remove any cache statements. o Remove all DEVICE statements that refer to files that are not on the \OS2... path; that is \MUGLIB, \IBMLAN, etc. o Remove all LIBPATH entries except those on the \OS2... path. o Remove the IFS statement for LAN (NETWKSTA.SYS). The intent is to boot to an environment where Locked Files will not be encountered during ServicePak installation. SERVICE.EXE inspects the target system for locked files before beginning the file replacement process. If you get the "Locked File" panel while running SERVICE.EXE, recheck CONFIG.SYS and try again. ΓòÉΓòÉΓòÉ <hidden> Getting the A: Prompt from OS/2 1.3 Install Diskettes ΓòÉΓòÉΓòÉ To obtain the familiar A: prompt when using the OS/2 1.3 Product installation diskettes as Bootable Standalone Service Diskettes: o Boot the system with Install Diskette in drive A. o At the IBM Logo Screen - Press Esc to Exit The A: prompt should appear. OS/2 Programs, including FSERVICE.EXE, can be run from here. ΓòÉΓòÉΓòÉ <hidden> Getting the A: Prompt from OS/2 2.0 Install Diskettes ΓòÉΓòÉΓòÉ To obtain the familiar A: prompt when using the OS/2 2.0 Product installation diskettes as Bootable Standalone Service Diskettes: o Boot the system with Install Diskette in drive A. o At the IBM Logo Screen - Insert Diskette #1, press Enter o At the Welcome Screen - Press Esc to Exit The A: prompt should appear. OS/2 Programs, including FSERVICE.EXE, can be run from here. ΓòÉΓòÉΓòÉ <hidden> Creating a 386 HPFS Boot Diskette ΓòÉΓòÉΓòÉ Refer to Appendix F in: Operating System/2 Local Area Network Server Network Administrator Reference Volume1: Planning and Installation Version 2.0 ΓòÉΓòÉΓòÉ <hidden> LAN Server Utilities ΓòÉΓòÉΓòÉ Refer to Appendix C, Miscellaneous Utilities MAKEDISK in: Operating System/2 Local Area Network Server Network Administrator Reference Volume3: Network Administrator Tasks Version 2.0 ΓòÉΓòÉΓòÉ 4. Existing Problem ΓòÉΓòÉΓòÉ Below are descriptions of some problems the are under investigation but could not be fixed in this ServicePak. o IC05662 HPFS386 is not caching random small I/O requests of 512 to 1K bytes. o No APAR D001715 Temporary loss of disk space. HPFS386 incorrectly updating size for the page file. This can cause CHKDSK to incorrectly free the allocation tree structures and cause temporary loss of disk space. D002300 Trap in Pbr$Init with Cache chunks less than 64K. D001693 Traps when using split caches and greater than 16 meg memory. ΓòÉΓòÉΓòÉ 5. Things that Changed ΓòÉΓòÉΓòÉ The following sections describe changes that have been made to the product's executables, publications, and messages/helps. ΓòÉΓòÉΓòÉ 5.1. Remote IPL Support for OS/2 2.1 (APAR IC05198) ΓòÉΓòÉΓòÉ OS/2 2.1 implements several system changes that require significant changes to the LAN Server Remote IPL service. This section describes how to update the remote IPL client definitions for different display types and how to support multiple versions of the OS/2 operating system in the remote IPL directory structure. This is new function introduced as a result of APAR IC05198. Note: The term remote IPL client used in this document is equivalent to the term remote IPL requester used in the OS/2 LAN Server documentation. ΓòÉΓòÉΓòÉ 5.1.1. Valid OS/2 Remote IPL Configurations ΓòÉΓòÉΓòÉ The following table identifies valid OS/2 and remote IPL configurations: ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Server Γöé Operating System to be Remote IPLed Γöé Γöé OperatingΓöé 2.0 + Γöé Γöé System Γöé 1.3.2 Γöé 2.0 Γöé ServPak Γöé 2.00.1 Γöé 2.1 Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé 1.3.2 Γöé Yes Γöé Yes Γöé Yes Γöé Yes Γöé Yes Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé 2.x Γöé No Γöé Yes Γöé Yes Γöé Yes Γöé Yes Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Note: ServicePak XR06055 introduced the 32 bit Graphics Engine for OS/2 2.0. ΓòÉΓòÉΓòÉ 5.1.2. LAN Server Remote IPL Service Upgrades ΓòÉΓòÉΓòÉ The following changes and additions have been made to the Remote IPL service: o The full-screen interface has been updated to default the File Index Table to model parameter to DEFALT21.FIT when an OS/2 2.1 server record is selected. Changes were also made to remove the Read attribute on the OS/2 2.1 client .INI files before attempting to delete them. The client file AUTOEXEC.20 was updated to reflect the boot drive ID. o The RPLSETD.CMD REXX procedure has been updated to support the following OS/2 remote IPL client upgrades: Current Client New Client Operating System Operating System ---------------- ---------------- 1.3.2 No updates supported 2.0 2.0+SP, 2.00.1, or 2.1 2.0+SP 2.1 2.00.1 2.1 The following option changes and additions have been made to the RPLSETD.CMD file: /D No longer a required parameter. /O If not specified, the operating system directory is determined for the client being updated. /B New. Specifies the bus type of a client (MCA or ISA/EISA). /S New. Specifies whether the SWAPPATH is on a local drive or on the remote IPL server. The RPLSETD.CMD file has been moved from the \IBMLAN\RPL directory to the \IBMLAN\NETPROG directory so that it can be located using the PATH statement and run from any directory. The LANINST program requires that a copy of RPLSETD.CMD be located in \IBMLAN\RPL. For this reason, a dummy version of RPLSETD.CMD is installed in the \IBMLAN\RPL directory. This dummy version invokes the version in \IBMLAN\NETPROG. o Several new routines have been added to support the new RPLSETD.CMD procedure: - RPLRXUTL.EXE - RPLUCC20.CMD - RPLUCFIT.CMD - RPLSDMSG.CMD o Default 2.1 WINOS2 *.INI files are provided that are preconfigured for VGA display support. XGA and 8514 support statements are also present but commented out. When the /D option is specified on RPLSETD.CMD, the client copy of the SYSTEM.INI file is updated to reflect the display type specified. The /S option also causes the client copy of the SYSTEM.INI file to be updated. ΓòÉΓòÉΓòÉ 5.1.3. OS/2 2.1 RIPLINST Utility ΓòÉΓòÉΓòÉ The RIPLINST utility used to install the OS/2 2.1 code for OS/2 LAN Server remote IPL is located (in packed format) on diskette 7 of the OS/2 2.1 Installation diskettes. Use one of the following procedures to install and run RIPLINST. o If your operating system is OS/2 2.1: 1. Insert the OS/2 2.1 Install diskette 7 into drive A. 2. Install RIPLINST by typing: UNPACK A:\RIPLINST The RIPLINST files will be unpacked to the \OS2\INSTALL directory. 3. To start the RIPLINST program, go to an OS/2 window or full-screen session and type: RIPLINST 4. Press Enter to remove the title window. 5. The Change Source/Target window is displayed. The source path should be left as A:\. If necessary, the target directory can be updated to change the drive ID of the target. Only the drive ID should be changed; do not change the default directory paths. The OS/2 2.1 code must be installed on the same drive where the OS/2 remote IPL support was installed during LAN Server installation. 6. Select Install. 7. Insert diskettes as prompted. o If your operating system is OS/2 1.3.2, 2.0, 2.0+Service Pak, or 2.00.1: 1. Create a temporary subdirectory by typing: MD TEMPRIPL 2. Change to the temporary subdirectory by typing: CD TEMPRIPL 3. Insert OS/2 Install diskette 2 into drive A. 4. Copy UNPACK.EXE to the TEMPRIPL directory by typing: COPY A:UNPACK.EXE 5. Check OS/2 2.1 Install diskette 2 for the file UNPACK2.EXE. If it is present, copy UNPACK2.EXE to the TEMPRIPL directory by typing: COPY A:UNPACK2.EXE Note: UNPACK2.EXE may not be present. If it is not on diskette 2, you do not need it. 6. Insert OS/2 Install diskette 7 into drive A. 7. Install the RIPLINST files by typing: UNPACK A:\RIPLINST d:\TEMPRIPL where d is the drive ID where TEMPRIPL is located. 8. Start the RIPLINST program by typing: RIPLINST Note: The OS/2 2.1 version of RIPLINST must use the OS/2 2.1 version of UNPACK and UNPACK2. Failure to do so will result in one of the following error conditions: - RIPLINST will trap while copying the W0F0000.BIO file. - The system will lock up after displaying the copy window. You must reboot if this occurs. 9. Press Enter to clear the title window. 10. The Change Source/Target window is displayed. The source path should be left as A:\. If necessary, the target directory can be updated to change the drive ID of the target. Only the drive ID should be changed; do not change the default directory paths. The OS/2 2.1 code must be installed on the same drive where the OS/2 remote IPL support was installed during LAN Server installation. 11. Select Install. 12. Insert diskettes as prompted. Previous versions of RIPLINST had a default target installation directory of: d:\IBMLAN\RPL\OS2.20 (OS/2 2.0 and Service Pak) or d:\IBMLAN\RPL\OS2.20a (OS/2 2.00.1) where d: indicates the drive where OS/2 is installed. The RIPLINST utility for OS/2 2.1 has a new default target installation directory. The new default target installation directory is: d:\IBMLAN\RPL\OS2.21 This prevents an existing ..\OS2.20 directory tree from being overwritten automatically. If you want to upgrade an existing ..\OS2.20 directory tree, the target installation directory must be updated before starting the installation process. The target directory must be on the same drive where OS/2 remote IPL support was installed (this can be different from where LAN Server was installed). After using RIPLINST to install OS/2 2.1 for remote IPL, run the updated version of the LAN Server utility, GETRPL.EXE. Refer to the IBM OS/2 LAN Server Version 3.0 Administrator Reference Volume 3: Administrator Tasks for information on running GETRPL. ΓòÉΓòÉΓòÉ 5.1.4. RPLSETD.CMD REXX Procedure ΓòÉΓòÉΓòÉ The RPLSETD.CMD procedure provides the following functions: o Upgrades existing remote IPL clients that use 16-bit display drivers to use the new 32-bit VGA and XGA, and 16-bit 8514 display drivers provided in OS/2 2.00.1 and in 2.0+Service Pak. It also supports the 32-bit 8514 display driver in OS/2 2.1. o Can be used in some cases to change the display type (32-bit VGA, XGA, or 8514) that a remote IPL client is using. RPLSETD does not support conversion from the new 32-bit drivers back to the old 16-bit display drivers. If an OS/2 desktop exists for the remote IPL client, changing to a higher resolution display type can cause unpredictable results. If an OS/2 desktop exists, it is highly recommended that the client definition be deleted and recreated, using RPLSETD to change to the higher resolution display type. Restart the client to create a new OS/2 desktop. o Can be used to update a remote IPL client to boot a different version of OS/2 2.x. The OS/2 2.x code must be installed in the remote IPL directory structure. Conversions for the following OS/2 2.x versions are supported: OLD VERSION NEW VERSION 2.0 2.00.1 2.0+Service Pak 2.1 2.00.1 2.0+Service Pak 2.1 2.0+Service Pak 2.1 Note: There is no support for converting any of the newer versions back to the original OS/2 2.0 version. After a client is converted to OS/2 2.1, RPLSETD cannot be used to convert back to 2.0+Service Pak or 2.00.1. o Can be used to update a remote IPL client to change the bus type (for example, MCA or ISA/EISA). o Can be used to update a remote IPL client to specify whether the SWAPPATH and WIN-OS2 PagingFile parameter will be on a local hard disk or on the remote IPL server. Requester definitions can be updated individually or in a group (grouped by common attributes such as display type, bus type, and operating system). The client name DEFALT20 is a special name used by OS/2 remote IPL support as a default when creating a new client (not modelling an existing client). If you are supporting prior versions of OS/2 (2.0, 2.00.1, or 2.0+Service Pak) in the remote IPL directory tree, do not update DEFALT20 to support OS/2 2.1. You must leave DEFALT20 at its current level to support the prior versions of OS/2. To support OS/2 2.1 remote IPL clients, do the following: 1. Create a new remote IPL client, for example, MODEL21, using the defaults. 2. Use RPLSETD to update MODEL21 to support OS/2 2.1. Then use MODEL21 as a model to create all future 2.1 clients. 3. You may need to create multiple 2.1 models, one for each LAN type you support. The client name DEFALT21 is reserved. Do not create a client with this name. DEFALT21 is not a complete client definition like DEFALT20. It is used in conjunction with DEFALT20 to support OS/2 2.1 clients. Do not attempt to update the DEFALT21 client with RPLSETD.CMD. If the only version of OS/2 that will be installed in the remote IPL directory is OS/2 2.1, you should update the client DEFALT20. Then all future default clients will automatically support OS/2 2.1. The syntax of RPLSETD.CMD is: RPLSETD [/H] [/C:client[,client2,client3,...]] [/D:display_driver] [/O:current_OS2] [/N:new_OS2] [/B:bustype] [/S:swaptarget] [/L:logfile] [/R:response_file] The descriptions of the parameters are described below. /H Displays the syntax on screen. If specified, it must be the first parameter. /C:client1,client2,client3... (CLIENT or CLIENTLIST) The name of one or more OS/2 remote IPL client workstations that are to be updated. If multiple names are specified, each name must be separated with a comma. Embedded blanks are not allowed. The response file keywords CLIENT and CLIENTLIST are equivalent to each other. They may be specified as many times as necessary. This is a required parameter if the /R parameter is not specified. When specified, at least one other parameter must also be specified. /D:display_driver (DISPLAYDRIVER) The new display type for the client definition. The following display types are valid: o IBMVGA32 32-bit VGA display driver o IBMXGA32 32-bit XGA display driver o IBM8514 16-bit 8514 display driver (2.0+SP or 2.00.1) o IBM8514 32-bit 8514 display driver (2.1) o 8514_32 Alternate 32-bit 8514 display driver name (2.1) This parameter is normally optional; however, it must be specified when an existing 2.0 or 2.00.1 remote IPL client is converted to 2.1 by specifying the /N parameter. When upgrading the display type of an existing remote IPL client (it has booted at least one time and has an OS/2 desktop) from VGA to XGA or 8514, you must delete and recreate the remote IPL client and then run RPLSETD.CMD. If you update the existing client to a higher resolution display type, many of the display sizing characteristics in OS2.INI do not get updated. As a result, you end up with some objects in VGA resolution and some in the higher resolution. If no OS/2 desktop exists for the client, it can be updated to change to a higher resolution. When the OS/2 desktop is created during the first boot, it will reflect the display characteristics for which it is configured. /O:current_OS2 (CURRENTOS2DIR) The root directory under \IBMLAN\RPL for the current version of OS/2 2.0 that the requester is using. This parameter is case-sensitive. The /O parameter should only be specified when you want the requester operating system type verified before updating to a new operating system type. If /O is not specified, the current operating system being used by the remote IPL client is determined from the client.FIT file. If the /O parameter is specified, then the /N parameter must also be specified. /N:new_OS2 (NEWOS2DIR) The root directory under \IBMLAN\RPL for the version of OS/2 2.0 that the client is to be switched to. This parameter is case-sensitive. The default is OS2.21. The /O and /N parameters should only be specified when you need to switch a client from one OS/2 version to another OS/2 version. When an existing remote IPL client is updated to OS/2 2.1, the client's WINOS2 *.INI and *.GRP files must be replaced with the 2.1 versions of these files. The old files are renamed to *.IBK and *.GBK. When you are satisfied that these old files are no longer needed for reference, you can delete them. /B:bustype (BUSTYPE) The type of I/O bus used by the remote IPL client. Valid types are: MCA MicroChannel* ISA AT compatible EISA AT compatible /S:swaptarget (SWAPTARGET) An indicator of where the SWAPPER.DAT file will reside. Valid values are: L File will reside on the local hard disk of the remote IPL client S File will reside on the remote IPL client This parameter also controls the location (local or server) of the PagingFile parameter in the OS/2 2.1 WIN-OS2 SYSTEM.INI file. /L:logfile (LOGFILE) The drive, path, and file name of a file to which all messages and errors are to be logged. If this parameter is specified, the only errors displayed on the screen will be for a failure to open the log file or for missing required parameters in the response file. /R:response_file The drive, path, and file name of a file that contains the command inputs in keyword form (keyword=value). The valid keywords are indicated above in parentheses () following each parameter. Only one keyword can be specified per line in the response file. The CLIENT or CLIENTLIST parameter and at least one other parameter are required when using a response file. If the /R parameter is specified, all other parameters specified on the command line are ignored. Examples: To update the DEFALT20 client to use the 32-bit VGA display driver and switch the operating system from OS2.20 to OS2.21, type: RPLSETD /C:DEFALT20 /D:IBMVGA32 /N:OS2.21 This will update the default files to support OS/2 2.1 and the new VGA display driver. These files are used when defining clients using the default configuration. Note: If you plan to also support previous versions of OS/2 ( 2.0, 2.00.1, or 2.0+Service Pak), do not update the DEFALT20 client. To update the MACH001 client to use the 32-bit XGA display driver and switch the operating system to OS2.21, type: RPLSETD /C:MACH001 /D:IBMXGA32 /N:OS2.21 To update the MACH001 client to use the 32-bit XGA display driver, verify the current operating system is OS2.20a, and switch the operating system to OS2.21, type: RPLSETD /C:MACH001 /D:IBMXGA32 /O:OS2.20a /N:OS2.21 To update the MACH001 client to specify a bus type of ISA and set the SWAPPATH PagingFile parameter to the remote IPL server, type: RPLSETD /C:MACH001 /B:ISA /S:S To update the MACH001 client to use the 32-bit VGA display driver, verify the current operating system is OS2.20, switch the operating system to OS2.21, specify a bus type of ISA, and set the SWAPPATH PagingFile parameter to the remote IPL server, type: RPLSETD /C:MACH001 /D:IBMVGA32 /O:OS2.20 /N:OS2.21 /B:ISA /S:S To update multiple clients (MACH001 and MACH002) to use the 32-bit VGA display driver and switch the operating system to OS2.21, type: RPLSETD /C:MACH001,MACH002 /D:IBMVGA32 /N:OS2.21 ΓòÉΓòÉΓòÉ 5.1.5. RPLSETD Response File Keywords ΓòÉΓòÉΓòÉ The valid response file entries and keywords are: o ; (comment line) o [GROUP] (this statement is optional for the first group and required for all subsequent groups) o DISPLAYDRIVER= o CLIENT= o CLIENTLIST= o CURRENTOS2DIR= o NEWOS2DIR= o BUSTYPE= o SWAPTARGET= A semicolon (;) in column 1 indicates the line is a comment. Leading blanks are allowed on keyword statements. The keywords are described in the RPLSETD syntax description. [GROUP] designates the start of a remote IPL client or a group of clients that share the same configuration characteristics. When the [GROUP] statement is encountered, the workstations in the previous group are updated according to the specified keywords. Multiple [GROUP] statements can appear in the response file. This allows a single response file to process a number of different configurations. The [GROUP] statement is optional for the first group in the response file but is required for all subsequent groups. The CLIENT and CLIENTLIST keywords are equivalent, and multiple entries can be specified on either one. Multiple CLIENT and CLIENTLIST keywords can be specified per group. Only one of each of the other keywords is allowed per group. Example: To use the response file option, do the following: 1. Create an ASCII file that contains the appropriate keyword values. For example: [GROUP] (optional) ; Update existing clients to support the IBMXGA32 display driver, ; switch from OS2.20 to OS2.21, support the MCA bus, and put the ; swappath on a local hardfile. CLIENT=DEFALT20 CLIENT=MACH001,MACH002 CLIENTLIST=MACH003,MACH004 DISPLAYDRIVER=IBMXGA32 CURRENTOS2DIR=OS2.20 NEWOS2DIR=OS2.21 BUSTYPE=MCA SWAPTARGET=L [GROUP] (required) ; Update client for ISA bus and put the swappath on the remote IPL ; server (no local hardfile). no hardfile CLIENT=MACH005 BUSTYPE=ISA SWAPTARGET=S 2. Type the following command: RPLSETD /R:d:\path\response_filename where d:\path\response_filename is the fully qualified file name of the response file. ΓòÉΓòÉΓòÉ 5.1.6. Creating New OS/2 2.1 Remote IPL Clients ΓòÉΓòÉΓòÉ The menu interface has been updated to automatically select the FITS\DEFALT21.FIT entry when a new client is created using an OS/2 2.1 server record ID. However, the master CONFIG.20 files have not been updated to OS/2 2.1 so that back-level versions of OS/2 can also be supported. The differences between an OS/2 2.0 and OS/2 2.1 CONFIG.20 file are minor, mainly new SET statements. In most cases the CONFIG.20 file will work for OS/2 2.1 as is. However, if you want to convert the client CONFIG.20 to the OS/2 2.1 level, run the RPLSETD command against the client and specify the /D parameter. RPLSETD will update the CONFIG.20 file to the OS/2 2.1 level. A new remote IPL client created using the defaults will be configured to support the IBMVGA32 display drivers. If the client has an XGA or 8514 display attached, RPLSETD must be run against the client to reconfigure the client for the correct display type. ΓòÉΓòÉΓòÉ 5.1.7. Updating Master Workplace Shell OS2.INI Files ΓòÉΓòÉΓòÉ Some users have a master customized OS2.INI file that is copied to the client directory each time the client is remote IPLed. This master file must also be updated to identify the type of display driver that the client workstation is using. Clients with different display types (VGA, XGA, 8514) must use different master OS2.INI files. To update a master OS2.INI file, type: RPLRXUTL /D:display_driver /C:ini_filename Where /D:display_driver is the same as for RPLSETD and /C:ini_filename is the drive, path, and file name of the master OS2.INI file to be updated. Example: RPLRXUTL /D:IBMVGA32 /C:E:\IBMLAN\RPL\MASTER\VGAOS2.INI The RPLRXUTL utility will not display any error information. It does return with a non-zero return code if an error occurs. If you need to verify error information, run RPLRXUTL from a CMD procedure (batch file or REXX) so that the return code can be tested. ΓòÉΓòÉΓòÉ 5.1.8. Supporting Multiple Levels of the OS/2 Operating System ΓòÉΓòÉΓòÉ It is possible to install and support multiple levels of the OS/2 2.x operating system on a remote IPL server. This section documents the correct procedure to use to support this environment. It is assumed that the OS/2 2.1 remote IPL support updates have already been installed. The basic procedure is as follows: 1. Run the OS/2 utility RIPLINST to install the OS/2 code in the remote IPL directory tree. You must be careful to use the version of RIPLINST that matches the level of code to be installed. RIPLINST is located on diskette 7 of all OS/2 2.x installation diskettes. RIPLINST is unique for each version of OS/2. 2. After running RIPLINST, run the LAN Server utility GETRPL. GETRPL uses information stored in the OS2SYS.INI file by RIPLINST. It is very important that GETRPL be run before using RIPLINST to install another version of OS/2. 3. Repeat steps 1 and 2 for each version of OS/2 that will be remote IPLed. 4. Check the \IBMLAN\RPL\RPL.MAP file. Look for the OS/2 server records. They start with yyyyyyyyyyyy or ;yyyyyyyyyyyy and field 2 will contain a name such as OS220*.CNF, OS22A*.CNF, or OS221*.CNF. A comment in column 1 indicates the record is disabled. Make sure that the appropriate records are enabled or disabled based on what OS/2 versions you have installed. 5. Determine whether the special remote IPL client, DEFALT20, should be updated by RPLSETD. This depends on what OS/2 versions are installed. OS/2 2.0 uses 16-bit display drivers. OS/2 2.00.1, 2.0+Service Pak, and 2.1 use 32-bit display drivers for VGA and XGA support. However, there are slight differences in the XGA support between 2.00.1 and between 2.0+Service Pak and 2.1. If OS/2 2.0 is present, DEFALT20 must not be updated. It must remain as is to allow the creation of future 2.0 clients. If OS/2 2.0 is not present, then DEFALT20 could be updated with RPLSETD to support either 2.00.1 or 2.0+Service Pak and 2.1. To update DEFALT20 to support 2.0+Service Pak, type: RPLSETD /D:IBMVGA32 /C:DEFALT20 To update DEFALT20 to support 2.00.1, type: RPLSETD /D:IBMVGA32 /C:DEFALT20 /N:OS2.20a The /N parameter indicates that the new default target operating system will be \IBMLAN\RPL\OS2.20a. The RIPLINST for OS/2 2.00.1 defaults to a target directory of \IBMLAN\RPL\OS2.20a. To update DEFALT20 to support 2.1, type: RPLSETD /D:IBMVGA32 /C:DEFALT20 /N:OS2.21 The /N parameter indicates that the new default target operating system will be \IBMLAN\RPL\OS2.21. The RIPLINST for OS/2 2.1 defaults to a target directory of \IBMLAN\RPL\OS2.21. 6. Since the special remote IPL client DEFALT20 must be associated with a specific OS/2 version, it is recommended that model clients be created for the other OS/2 versions installed in the remote IPL tree. RPLSETD can be used to update the model client definitions to point to the correct operating system. Then these model clients can be used to create future clients for each operating system type. ΓòÉΓòÉΓòÉ 5.2. LAN Requester ΓòÉΓòÉΓòÉ The following list describes APARs for the Requester component that are fixed by this Service Pak. o IC04248 Applications using a remote named pipe hang. o IC04475 Programs cannot edit hidden files on a PCLP server. o IC04492 An XCOPY of multiple files with an extension of .CMD or .BAT fails. On the server, the NET ERROR log shows MAXSESSOPENS exhausted. o IC04532 Programs using the NETBIOSSUBMIT application interface may hang. o IC04600 The LAN Management Utilities/2 (LMU/2) product or other programs that use DOSMAKEMAILSLOT() may fail with return code 87. o IC04667 A NET3190 error displays the following message: MSG incomplete in redir NCB 0600 Another symptom is that data is damaged on the requester. These symptoms can appear when the requester accesses large files or programs from the server. o IC04697 A trap 0D screen displays with an unrecoverable system abend. o IC04698 A page fault (Trap 0E) occurs when shutting down or rebooting a remote IPL client. o IC04750 A trap 0D screen shows EIP=00000032. o IC04761 A 32-bit GREP program and other programs using the 32-bit DOSFINDFIRST() DOSCALL may hang. o IC04834 Programs running on a requester receive errors on file operations (copying files, reading files, writing files). If errors disappear when you set bits 9 and 23 to 0 in the WRKHEURISTICS parameter in IBMLAN.INI, you are likely to need this fix. o IC04865 A remote IPL client hangs or stops with trap 8. In the case of the hang, after the machine is rebooted, there should be some entry in the NET ERROR logs stating that some resource has been exhausted (for example, NUMWORKBUFS, MAXCMDS, or MAXTHREADS). o IC04963 A trap 0D occurs on the requester when the server uses a FAT file system. o IC05170 This is a workaround for a Microsoft Windows for Workgroup problem. A copy from the IBM OS/2 LAN Requester to a Windows for Workgroup machine can fail. The OS/2 requester was changed to avoid encountering this problem. This APAR also included a fix for updating the date and time of files stored on OS/2 LAN Servers that were modified by Lotus 1-2-3**. Another customer reported a different symptom. The 16-bit DOSSETPATHINFO() call for a remote file on a server running OS/2 2.0 or later could receive error code 87. o IC05275 A damaged NETBIOS table causes programs using NETBIOS to receive error 0x13. o IC05298 Logon is unsuccessful after a SPM/2 program is started, or after other programs which use remote path names are started. o Other fixes: - OS/2 LAN Requester is unable to run with Ungermann-Bass** NETBIOS transport code. ΓòÉΓòÉΓòÉ 5.3. LAN Server ΓòÉΓòÉΓòÉ The following list describes APARs for the Server component that are fixed by this Service Pak. o IC04302 Users receive SYS0008 (out of memory) messages when trying to perform operations (for example, DIR X:) on remote drives. The following message is also logged. NET3186E: The 386 HPFS Server ran out of the following resource: 64KB Work Buffers o IC04424 A trap 0 occurs in the Ring 3 server (NETSERVR.EXE) when the requester sends an SMB read command with the number of read bytes set to 0. o IC04430 A trap often occurs in the 386 HPFS server when using Microsoft Windows 3.1 clients with the server. o IC04431 The system traps because the Ring 3 server fails to release space that has been allocated for renaming or moving files with access control profiles. o IC04710 Requirement to improve performance in deleting subdirectories and in handling lock requests at the server. Some applications also receive ERROR_LOCK_VIOLATION error messages that end processing prematurely. o IC04769 The server receives an error return code when trying to open a shared COM port and does not set the device to error status. The result is that all incoming requests are queued up for the port. The device is left in an open condition when viewed with the NET DEVICE command and cannot be cleared or reset. o IC04943 A trap occurs in the 386 HPFS server after installing NVDM/2. o IC04973 If a DOS LAN Requester workstation performs a DIR command on an empty directory, no volume label information is returned. o IC04992 A trap 003 occurs when remote IPLing a client with an XGA display. o IC05010 HFS0102 messages display while running the CHKDSK command, especially on larger drives (for example, 1GB). o IC05058 A trap occurs in the 386 HPFS server when starting from either a boot partition or boot diskettes. This problem may occur on machines that previously ran with DBCS code pages using OS/2 1.2 or OS/2 1.3. o IC05073 A trap occurs in the 386 HPFS server when doing a hotfix on an already hot-fixed sector. This problem usually occurs when a drive fails (especially on a machine with an IBM 3515 disk subsystem). o IC05075 Excessive access-denied violations accumulate in the server statistics, causing alerts to be sent. The permission violations in the server statistics do not match the audit entries in the audit log. This may cause confusion for users who have auditing enabled and get alerts indicating permission violations but when the audit log is viewed, there are no audit entries. o IC05106 The 386 HPFS server returns a return code of 0 when doing a DosCopy and duplicate files are encountered. o IC05112 A trap occurs in the 386 HPFS server when TRACE code 154 is enabled and the server tries to break an Oplock on a file. Setting TRACE=ON or TRACE=ON 154 (when using SPM/2) could cause the problem. o IC05129 A trap occurs in the 386 HPFS server when trying to write to a file that has become extremely fragmented. This requires a file of at least 240KB in size, but happens more frequently with larger files. o IC05141 The last update time for a 386 HPFS file is being updated in a DosOpen DosRead, DosBufReset combination. o IC05182 A trap occurs in the 386 HPFS server (or in the OS/2 kernel) during paging when 386 HPFS is handling paging and the page file (SWAPPER.DAT) becomes fragmented. o IC05184 Include MAKEDISK updates that will handle out-of-disk-space errors when trying to build boot diskettes. This will also verify that UHPFS.DLL exists on the boot diskettes so that AUTOCHECK can be run. Note: When building boot diskettes for OS/2 2.1, delete A:BUNDLE from backup diskette 1 before running MAKEDISK. o IC05188 Possible deadlock condition occurs when multiple programs try to read uninitialized file data simultaneously from the same file. o IC05190 The 386 HPFS server returns an ERROR_FILE_NOT_FOUND message instead of an ERROR_ACCESS_DENIED message when trying to delete a directory using DosDelete. o IC05200 A trap occurs in the 386 HPFS server when trying to set attributes on a directory whose sector is not accessible because of disk read/write errors. o IC05240 A trap occurs in the 386 HPFS server when using the Replicator service to import to a 386 HPFS drive. o IC05256 The 386 HPFS server will not correctly release space when the page file (SWAPPER.DAT) size is decreased by OS/2. o IC05327 Improve performance for servers running LAN Server for Macintosh. o Additional fix without APAR: OS/2 LAN Server is unable to run with Ungermann-Bass NETBIOS transport code. o IC05662 HPFS386 does not cache small (512 to 1K byte) I/O requests. This causes a performance problem. ΓòÉΓòÉΓòÉ 5.4. User Profile Management (UPM) ΓòÉΓòÉΓòÉ The following list describes APARs for the UPM component that are fixed by this Service Pak. o IC04427 Logon using the LAN-aware workplace shell returns a SYS0317 error when the OS/2 optional utilities are not installed. The code has been changed to return a SYS0002 error. o IC04904 Responding with a N to the Y/N prompt at logoff when there are open files or active drives on the network results in the logoff continuing instead of canceling. o IC05694 An application invoking USER or GROUP API's on a workstation without the Server service started, would be left in a "critical section". All other threads of a process besides the calling thread are "frozen". o JR06434 User Profile Management (UPMACCTS) may fail to start and will return a UPM0004C or UPM0010C error if the logon domain consists of Microsoft LAN Manager servers. o JR06710 User Profile Management (UPMACCTS) will fail with a UPM0062C reason code 2140 error when attempting to open group or user management. The failure occurs when the domain controller in the domain is LAN Server 1.3 or 1.3 with CSD5015. o JR06859 Initialization of UPM (upon first logon) may result in the display of a SYS0039 drive-not-ready error message when an access control profile has been put on a removable-media drive. ΓòÉΓòÉΓòÉ 5.5. Fault Tolerance ΓòÉΓòÉΓòÉ The following list describes APARs for the Fault Tolerance component that are fixed by this Service Pak. o IC04815, IC04824, IC05414 Provide Fault Tolerance support for large disks having more than 1.2GB or more than 1024 cylinders. If a mirror partition has already been created, use FDISK to remove all partitions on the disk. Then use FTSETUP or FTREMOTE to remirror the drives. o IC05409 Support for hot-replaceable disks. When a failed disk is replaced without booting, this fix enables the Verify function to restore the data from the good partition to the replaced partition. o Defect 1652 A trap occurs when mirroring a drive with FTSETUP or FTREMOTE if the target disk containing the mirror partition has damaged sectors. o Modification to DISKFT.SYS This fix makes it possible to install the Service Pak on a mirrored drive. Refer to the installation instructions in this document for information on installing the Service Pak on a mirrored drive. ΓòÉΓòÉΓòÉ 6. Appendix ΓòÉΓòÉΓòÉ Appendix of other interesting topics. ΓòÉΓòÉΓòÉ 6.1. Printing Information from this On-line Document ΓòÉΓòÉΓòÉ The OS/2 view function provides a print capability to the printer defined as the "default" printer for your system. From the "Services" popup, selecting print provides several options; Print All, Marked, or This Section(s), Contents, or Index. All but the Print Marked Sections are fairly self explanatory. To Print "Marked" sections one must first know how to "Mark". It is best to do this with the contents window fully expanded, ie. every section shows up in the content panel. Then simply press the space bar when the section you chose is highlighted or point and click the left mouse button while also holding the ctrl key to "mark" a section for print. The highlighting for "marked sections" is slightly larger than normal highlighting. To notice the difference, select an item in the contents and repeatedly press the space bar. ΓòÉΓòÉΓòÉ 6.2. Restarting ServicePak Installation ΓòÉΓòÉΓòÉ If the installation procedure stops after selecting the "Continue" button on the Start Service Panel and before service is complete, the system may be in an indeterminate state. To complete the service process: o Insert the Bootable Standalone Service Diskette o Restart the system - Ctrl+Alt+Del or Power On. o From the A: Prompt type "FSERVICE" and Enter. ΓòÉΓòÉΓòÉ <hidden> Initiating Service ΓòÉΓòÉΓòÉ ΓöîΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé--Γöé Initiating Service Γöé Γö£ΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Continuing at this point will cause all selected Γöé Γöé directories to be updated. If you want to change the Γöé Γöé selected directories, click on Cancel and then click Γöé Γöé on Select Directories. Γöé Γöé Γöé Γöé The application of service cannot be interrupted. Γöé Γöé After this point you will not be able to exit the Γöé Γöé service process. Γöé Γöé Γöé Γöé Do not start those applications being serviced Γöé Γöé Γöé Γöé Do you want to continue? Γöé Γöé Γöé Γöé ΓòöΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòù ΓòöΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòù ΓòöΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòù Γöé Γöé Γòæ Continue Γòæ Γòæ Cancel Γòæ Γòæ Help Γòæ Γöé Γöé ΓòÜΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¥ ΓòÜΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¥ ΓòÜΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¥ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ The item in the title line is a trademark of IBM Corporation ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ The item in the title line is a trademark of Microsoft Corporation ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ The item in the title line is a trademark of Apple Computer ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ The item in the title line is a trademark of Lotus Development Corporation ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ The item in the title line is a trademark of Ungerman-Bass, Inc.