═══ 1. Introduction ═══ IBM OS/2 LAN Server 2.0 ServicePak IP06030 IBM PTF IP06030 This ServicePak applies to: IBM OS/2 LAN Server Version 2.0 - Entry For use with OS/2 1.30.2, OS/2 1.3 at service level 5050, or OS/2 2.0 IBM OS/2 LAN Server Version 2.0 - Advanced For use with OS/2 1.30.2 or OS/2 1.3 at service level 5050 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. ═══ 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.DLR PC/DOS LAN Requester Note: Updates to SYSLEVEL.DLR are not reflected in the output of the SYSLEVEL command. ═══ 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 Microsoft Corporation: o Microsoft o Windows ═══ 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 Three Installation Approaches to apply service. In this phase system files are replaced by those contained in the ServicePak. Phase 3 - Return the Serviced System to Normal Operation Perform a normal system boot. Remember to restore any files that were altered in phase one. Note: LAN Server 2.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. Three Installation Approaches ═══ The chosen approach is dependent on environment and personal preference. All approaches perform the three essential Installation phases but employ different techniques. o The Diskette Boot Method is the simplest and safest approach. It is ideal for a few centrally located systems. o The Redirected Method is dependent on having a Code Server and a method to perform the redirection. We will discuss the IBM Network Transport Services/2 - CID technique. o The CONFIG.SYS Alteration Method is difficult and risky. It may be useful in special situations where the first two are impractical. Extreme care should be taken on systems that use 386 HPFS with Access Control Lists and/or Fault Tolerance. Good Insurance! Have appropriate Bootable Standalone Service Diskettes. ═══ 2.1.1. Diskette Boot Method ═══ This method is the simplest and safest method to Install ServicePaks. It requires manual diskette manipulation, but almost no preparation time. Apply all fixes to all partitions and directories: 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. Apply fixes to selected subsystems, partitions, and directories: 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. Select the Reboot push button when informed that Locked Files exist. 6. Perform the system Shutdown procedure. 7. Boot from the Bootable Standalone Service Diskettes. 8. Establish A: as the Current Directory. 9. Replace the Boot Diskette with ServicePak diskette #1. 10. At the A: prompt type "FSERVICE" and press Enter. 11. Follow the prompts provided by the Installation Aid. 12. Reboot the system normally. ═══ 2.1.2. 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 Diskette Boot method is 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, the following may prove useful for setting up a CID server to handle the ServicePak: o Create a directory urdir on the CID Server for the ServicePak contents o For each ServicePak diskette XCOPY A:*.* urdir /S The following directory structure should contain all the ServicePak fixes. urdir/FIX/SRV urdir/FIX/REQ urdir/FIX/DLR urdir/FIX/MUG urdir/FIX/UPE o Prepare the CID Response File. The default Response File RESPONSE.FIL and sample Command File CIDCSF.CMD can be found on ServicePak Diskette #1. o Perform CID Install for each System to be serviced. ═══ 2.1.3. Alter CONFIG.SYS Method ═══ This method requires a good technical understanding of CONFIG.SYS and how its entries affect the system. It assumes that a Minimal CONFIG.SYS file has been produced that allows access to the target file system leaving no Locked Files. 1. Backup (Rename or Copy) CONFIG.SYS from the Root Directory of the Boot Drive. 2. Replace CONFIG.SYS on the Root Directory of the Boot Drive with the Minimal CONFIG.SYS. 3. Reboot the System from fixed-disk. 4. Insert ServicePak Diskette #1 in drive-A. 5. Run SERVICE.EXE 6. Replace CONFIG.SYS with the Backup Copy 7. Normal Boot ═══ 2.2. Upgrading DOS LAN Requesters (DLR) ═══ This ServicePak will update DLR files on LAN Server 2.0 systems providing DOS LAN Requester and DOS Image Support are present. The DLR files located in \IBMLAN\DOSLAN\NET can subsequently be copied to DLR workstations using UPGRDLR.BAT. For detailed information see Network Administrators Reference Volume 1 "Upgrading DOS LAN Requester". ═══ 2.2.1. Make UPGRDLR.BAT Public ═══ o Define an alias for \IBMLAN\DOSLAN\NET o Set up the Access Control Profile for the alias as Read (R) access o Define UPGRDLR.BAT as a public DOS application using the Create DOS Application panel. o Using the Manage DOS Applications panel: - Make a working directory for UPGRDLR. - Select the User IDs (or All) that are to have access to UPGRDLR. ═══ 2.2.2. Upgrading the DLR Workstations ═══ o Type "Net Start" and press Enter o Type "Initfsi" and press Enter o Type "Net" and press Enter o Log onto the Domain o Select the upgrade application from the Served Applications panel. o Restart the workstation after all disk activity has stopped. ═══ 2.3. 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 from OS/2 1.3. Escape to A: o Use the Install diskette and Diskette #1 of OS/2 2.0. Escape to A: o Create custom Bootable Standalone Service Diskettes from your licensed materials. The character of these is dependent on the system to be serviced. Instruction is available for: OS/2 1.3 + Entry Requester or Server, OS/2 2.0 + Entry Requester or Server, OS/2 1.3 + Advanced Server. 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.3.1. Making OS/2 1.3 Bootable Diskettes ═══ 1. Make a copy of the OS/2 1.3 Installation Diskette. Call it SA#1 2. Modify CONFIG.SYS 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:\; ═══ 2.3.2. Making OS/2 2.0 Bootable Diskettes ═══ 1. Make a copy of the OS/2 2.0 Installation Diskette & Diskette #1. Call them SA#1 and SA#2 respectively. 2. 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:\; 3. Delete SYSINST2.EXE form Diskette SA#2. 4. Copy UHPFS.DLL from OS/2 Diskette #2 or C:\OS2\DLL to SA#2 ═══ 2.3.3. Making OS/2 1.3 - 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 1.3 Install Diskette. 2. Using a (backup) copy of the OS/2 1.3 Boot diskette, run MAKEDISK from an OS/2 command prompt. For additional Information see the Network Administrators Reference: Creating a 386 HPFS Boot Diskette, or LAN Server Utilities 3. If using Fault Tolerance, add the Fault Tolerance files to the Bootable Diskette. 4. 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.3.4. 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 last diskette of the LAN Server 2.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. ═══ 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. ═══ 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. ═══ 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 Enter o At the Welcome Screen - Press Enter o At the Introduction Screen - Press Enter o At the File System Screen - Press Enter o At the Fixed Disk Required Space Screen - Press F3 to Exit. The A: prompt should appear. OS/2 Programs, including FSERVICE.EXE, can be run from here. ═══ 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. ═══ 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 ═══ 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 ═══ 3. Things that Changed ═══ The following sections describe changes that have been made to the product's executables, publications, and messages/helps. ═══ 3.1. LAN Server / Requester ═══ o IC01119: DXMAID.045 missing from U.K. LAN Server When installing the LAN Support Program from U.K. LAN Server 2.0, onto Danish DOS 5.0, an error message appears: DXMAID.045 does not exist. DXMAID.045, as well as other modules, is missing from the diskette when it has been present in previous versions of LSP. There are many situations where NLS countries use U.K. code, and some of them will be running NLS versions of DOS, thus causing the above error. DXMAID.045 needs to be packaged with the U.K. LAN Server code. o IC01122: XCOPY File system Sub-dir hangs HPFS386 Server During migration from LS 1.3 CSD 5050 to LS 2.0 Advanced with HPFS386, serious integrity problems were experienced. The problem is reproducible during a migration process from backup of the involved Domain controller's C: disk. During the migration process, the initial BACKACC C: \ /S of the 1.3 LS gives the NET3569 message, but the BACKACC completes successfully. After LS 2.0 Advanced is installed, the RESTACC C: \ /S hangs the system (Forced to (POR)Power on reset the system). Further investigation revealed that each time a particular file is accessed, the system hangs. If the file is copied to another HPFS386 server, that Server immediately hangs. The system also hangs if you issue a DIR command showing the file. o IC03454: SYS3175 error after disconnecting LAN cable SYS3175 in NETAPI.DLL was actually a server problem, and a trap 0C, stack overflow fault. When the cable unplugged, the Server would start NCB errors and begin to log them. This forced NCBs to be reissued for the ones that completed. During the process the Server took a recursive path that ended up causing it to run out of stack space just as it called the NetErrorLogWrite() function in NETAPI.DLL, where it trapped. o IC03578: DOS ERROR VECTOR INT24 not called In DOS applications running in an OS/2 V2 VDM, DOS ERROR VECTOR INT24 was not called during I/O requests to redirect drives on a Server machine if the LAN cable was broken, or there was a MSAU failure, or if the Server machine was powered down. o JR03853: 1.3 Gateway/LAN Server logs ACS0448W messages Gateway/Server continuously logs ACS0448W Messages. The LAN workstations are still able to access the Host via the Gateway, and are still able to access the LAN Server application. o IC03862: OS/2 32Bit API DOSSetFileLocks now supported The OS/2 2.0 API call, DOSSetFileLocks, was not supported on the GA release of LS 2.0. Applications using the older 16 bit API calls, DOSFileLocks and DOSFileIO, are not affected. Applications issuing the 32 bit DOSSetFileLocks saw a return code of 174. o IC03994: DOSOPEN of a Named Pipe fails with Trap D After creating a pipe with the DosMakeNmPipes API, attempting to open the pipe via the DOSOPEN API fails with a TRAP D. At the time of the TRAP the Server is attempting a DOSConnectNmPipe. o IC04002: NET8204 Error when logging off 2.0 Requester Logging off from an OS/2 2.0 Requester with External Resources to an OS/2 1.30.2 (WR05050) defined as Logon Assignments causes one NET8204 error to be logged in the OS/2 2.0 Requester's Error Log for EACH OS/2 1.30.2 (WR05050) External Resource defined as a Logon Assignment. The NET8204 does NOT occur if the External Resource is not a Logon Assignment. The NET8204 gets logged whether the External Resource is ever accessed or not. o IC04025: Trap D Rebooting after FDISKPM used A Trap D occurred after Rebooting using FDISKPM to create a Logical Drive on Fault Tolerant machines. o IC04026: NET3196 error when OS/2 2.0 Requester with PCLP Attempting a Copy or Xcopy of a file from an OS/2 2.0 Requester to a PCLP server would generate a NET3196 error indicating a write error had occurred. o IC04027: Reinst of a broken install not marking CONFIG If exiting LS/2.0 install at the "install DLR diskette 1" stage, and then reinstalling later to continue, the Server, HPFS386, and DLR do not ask to be reinstalled. This information is not stored on the hard drive. o IC04028: Problem with install LS/2.0 Req and 1.3 Domain Controller On panel 81, buttons for installing API structures, the on-line reference, and command reference did not operate correctly when installing LS 2.0 Requester over a LS 1.3 Domain Controller. o IC04040: ERR_MSG_COUNT and MAXMSGSIZE in two places Currently ERR_MSG_COUNT and MAXMSGSIZE are defined in two places providing the possibility of a future problem. The locations are /PBINC/PBCOM.INC for HPFS.386 and /LDR/MSGS.C for HPFS386.IFS. o IC04045: Start Requester error NET2186 with COMPAQ 386 OEM COMPAQ 386 S20 Machine with 360 drives caused requester to time out on startup, giving a NET2186 error. o IC04062: DOS Based NETBIOS application runs slow in RIPL The DevHlp_VMFree (58H) service takes 10 seconds in a RIPL environment. Traces show that the issuing thread gets blocked until it times out, at which time the service returns with a 57H return code. The same service works in a non-RIPL environment. o IC04097: Net Use/Workstation: * Does not replicate When any of the text based fields such as Comment, Usercomment, workstations, etc., would try to be nullified by using the ("") ( double quotes ), i.e. Net User User1 /Workstations: "", the field would be cleared at the Domain Controller, but it never cleared at the Additional Server. The problem was in the unpacking algorithm in the replicator function of the additional server NETLOGON.EXE module. If the field was "" ( a NULL string ), it considered this to mean "don't change this field". This was corrected. o IC04149: With OPLOCK 2nd user can't open with 1st lock on Problem was that the Redirector would not issue the OPLOCK locking request to the Server when the file was opened in deny write sharing mode. Depending on if OPLOCK was on or not, the second open of the same file, but with deny none read access, would or would not cause the lock to flow. Either way, the problem was the locks not being sent, or if the lock was sent, the unlock was never sent. The Redirector was corrected to flow the locks and unlocks properly. o IC04196: Unlock error running Borland App from Redirected Drive When executing an app, which attempts to create Database files on a redirected drive, the following error is returned DATABASE ERROR: Unlocking a file. This is an incorrect error message. o IC04197: Server won't start on OEM with Low Density Drive Problem is that, when the server attempts to set the current Dir of all the system drives to the root when it gets to 360K drive, and no diskette is in the drive, the Server ends up timing out in its initialization code. The timeout is changed to wait up to two minutes for slow drives to respond. o IC04199: Unable to set remote print job priority An application submitting a job to a remote print queue cannot always set the job priority. If the DevOpenDC DEVOPENSTRUCT-> pszSpoolerParms field is set to prty=45, the DevOpenDC may fail, causing the print request to fail. o IC04207: SYS3175 when PM Logon panel up behind another PM Window If a logon is initiated and then a new logon panel is brought up by clicking on a network object, then a SYS3175 error occurs. o IC04215: CHKSTOR /ALL Cmd returns false Alerts Issuing the command CHKSTOR /ALL will return a false Alert message for every user, and indicate that they have exceeded their maximum storage limit, even if they have not. The fact that it states that they have exceeded when they have not is incorrect. o IC04225: On Rewrite of large file, sort program ends On Rewrite of large (41 MEG) files, the sort program terminates with a sharing violation error, and ABORT,RETRY,FAIL pop-up. Small files or large files on standalone systems work fine. o IC04228: Can't log back on Server after NET PAUSE PRDR When logging onto Server and connecting to network printer. User performs a NET PAUSE PRDR, then logs off. At this point unable to Log back on - UPM error says USERID and PASSWORD are invalid. The NET USE shows still connected to network printer. NET USE LPTx: /D results in error message - NET2250 - connection cannot be found, NET CONTINUE results in logon box, but still cannot logon. If a Copy is performed to the network printer the operation is successful, even though Not logged onto the Network. Must reboot to recover. o IC04239: USERID Delete and Add cause Resync failure When an ID that is a User/Group is deleted and then added back as a Group/User a full resync will fail. Ordinary replication of Deltas will work. o IC04248: Second write not received in DOS Named Pipe A Dos Named Pipe application that will accept data from multiple workstations has a problem when a write is followed very closely by a write from a second workstation(within one clock tick). The second write is never seen by the Server, or is ignored. o IC04272: Net Stat RDR giving incorrect Data Net Stats command returns incorrect total value in the Network error total field. o IC04274: Incorrect error displayed in Net User/Time When specifying a "net user /time: " command, specifying times in both 12-, and 24-hour format should return a NET3765 error, not a NET3769 error. o IC04276: Server sends incorrect response for write When trying to copy a 60K file to a redirected drive, to a Server that had 40K left on the drive, the copy did not copy anything but it said 1 file(s) copied. On the server drive was the filename with 0 bytes. o IC04279: Low battery message Pop-Up appears if not used Problem found that low battery message would be issued even if it is used, ie. even if signal=101, voltlevel=101. First connect a UPS interface cable to serial port (COM1) of a PS/2. Then boot the system, and start LAN Server by issuing 'NET START SERVER'. Then disconnect the power supply from UPS and wait to see the Pop-Up message. It was also found that before the shutdown message was issued, the Low Battery message was also wrongly issued. o IC04290: ACP does not include "A" permission A copy to a directory on a Server without the "A" permission would generate the message "Incorrect function, 0 file(s) copied". The incorrect function was return code "1", which the OS/2 Redirector was incorrectly returning for the permission violation of copy trying to set the file attributes. The return code should have been "SYS0065" which is "Network Access Denied". The Redirector has been corrected to now return SYS0065. o IC04298: UPS does not provide graceful recovery 1.30.2 MOD 95 with LS 2.0 ADV. utilizing UPS service. With a RS-232 Signal Detector, force low signal voltage readings on DCD CTS and DSR. Once the voltage indicator is set, the UPS service (The PROTOCOL.INI parameter BATTERYLOW is set to WARNING) does not allow a graceful recovery if power is returned to the machine without IPL'ing the machine. o IC04302: HPFS386 Server returns errors SYS0089, SYS0008 The LS 2.0 386HPFS Advanced Server will fail any OS/2 application's DOSFindNext with RC=89 on Server's one GIGA+ Drive. The Requester's Window will hang, but user can switch over to other Windows and continue. o IC04304: Drive A or B not released after RIPL Drive not ready error accessing drive A: or B: if machine is booted from RIPL diskette. o IC04318: Misspell "Shipped" in LS OS/2 RIPL pop-up Path to the pop-up that contains the error: D: LANINST + advance + D: + install or remove a component + OS/2 RIPL + install + ok, then config a component + OS/2 RIPL service. An info pop-up will be displayed with the title "OS2 Remote IPL" The last line of the second paragraph states "which is shiped with 2.0". The word 'shiped' is misspelled (it should be "shipped") o IC04355: RIPL SWAPPER.DAT reconnects bad file handles If a Lan Requester session to the Server was dropped, and the OS/2 2.0 RIPL client was using remote swapping (SWAPPER.DAT stored on the server, and not on a drive in the RIPL client), LAN Requester automatically reconnected the LAN Server. However, it does not properly re-establish the 4 Read/Write file handles to SWAPPER.DAT that the OS/2 SE 2.0's paging system uses. The first R/W file handle gets re-established OK, but the R/W handle to SWAPPER.DAT fails, with LAN Server reporting a sharing violation. o IC04356: OS/2 RIPL workstation hangs in NETWKST.200 OS/2 RIPL workstations hang in NETWKSTA.200 during RIPL error description. This is not prevalent in "Non-RIPLed" OS/2 2.0 Requesters. o IC04395: Logon after Reboot without logoff gets NET8014 error User logs on to Domain X and uses a Public application via an icon. Then the machine is shutdown after logging off. After rebooting the machine and logging on to domain Y, an attempt to use a public application results in an error (NET8014), as the icon still references the old app from the previous Domain. o IC04414: Wrong access control profiles on OASAS Incorrect access control profiles on OASAS 1.0 product, on an HPFS386 drive, on OS/2 1.30 LS. o IC04422: Cannot format diskette in drive B When booting a DLR machine from an image stored on the Domain Controller, placing a diskette in drive B: and issuing "FORMAT B: " command, an error message appears; "Invalid Parameter". When the workstation is booted as a standalone DOS based machine, the FORMAT B: works perfectly. o IC04442: RIPL workstation will not save file in mixed case Server with OS/2 2.0 Base and LS 2.0 Entry server formatted HPFS. If a file is saved from the Requester to the Server with a file name in mixed case, the file name will save correctly. If the OS/2 Requester is a RIPL workstation (using RPLENABL), and performs the same operation to the same Server resource, the file will be saved in upper case only. o IC04469: Error "LOG NCB/SNB_ERR: NO SRV_list!!" wrong Errors containing the message "Log_NCB/SMB_Err: No SRV_list!!" were being incorrectly generated by the OS/2 Redirector on sessions that had been dropped, and had expected to still exist. o IC04470: SRVHEURISTIC 11 did not change compatibility When processing compatibility mode opens for HPFS386, if the SRVHEURISTIC 11 is set to 3, it does not get changed to a deny none sharing mode. This will cause the HPFS386 Advanced Server to be incompatible with the way the normal Entry Server works, which is to change all compatibility mode opens to deny none sharing mode when SRVHEURISTIC 11 is set to 3. o IC04492: XCOPY fails attempting to XCOPY *.CMD Files Two files resources on OS/2 2.0 Base and Entry LS 2.0 Server. Connecting the two files resources on the Server from an OS/2 2.0 Base, with a 2.0 Requester. One of the redirected drives contains many *.CMD files in several sub-directories. When attempting an XCOPY of the *.CMD files from one redirected drive to the other, the operation fails with SYS1186 error, and no files are copied. o IC04508: DOSSetFileLock call with IC03862 causes Hang Call to network drive with DosSetFileLocks having the Unlock range or Lock range set to Null, causes the Requester to hang. The flag for Atomic lock is set on. System has IC03862 installed to support the Atomic lock. o IC04516: DOSFindNext problem on LAN Redirected Drive Problems using the DOSFindNext API. When setting the Parameter for DOSFindNext to search 30 files at a time, if there are 300 files, it will search 30, then 30, then 30, then 10, then random grabbing... maybe 40, then 51 etc... . If DOSFindNext is done with increments of 100 this all seems to work fine. o IC04529: 2.0 RIPL SYS0055 disconnected connection OS/2 LAN Server 2.0 ADV on top of OS/2 1.3.2. Requesters are RIPling OS/2 2.0. Requesters are connected to the Server initially with no errors. When the requesters get their connections disconnected they are not able to reconnect successfully. A SYS0055 error "Access denied" message is received. However, when doing a NET USE, this list erroneously says the connections are OK. To reconnect, the user must do a NET USE /D and a new NET USE to the Network resource. o IC04532: App invoking NETAPI.DLL doesn't Invoke An application that is a set of appls that invoke NETAPI.DLL, then, in turn invoke NETBIOS, will not terminate properly. The application, which is really a set of apps, hangs and won't terminate properly after their DLL system (which calls the NETBIOS interface) is called. Problem seems to occur on LS 2.0, but works fine under 1.3 systems. o IC04541: DOS Named Pipe Server traps with Remote Client An application using 32 bit DOSNamed Pipe application Traps when passed through the Redirector. The NPCLIENT.EXE (Named Pipe Client), and the NPSERVER.EXE (Server component) application runs locally with no problem. But, when access to the pipe is made through the Redirector (NPCliENT -S \\), the NPSERVER app fails with a SYS3175 Trap error. o IC04559: Invoke FSI via "NET" cmd gets NET2762 error Perform a NET USE D: \\Server\Netname to a files resource for which the USERID has no access rights. Using the OS/2 full screen, modify the path with the command - PATH D: \;%PATH% - to add the redirected drive letter to the path. When still in the full screen session invoke the Requester FSI with the Net command. This results in a NET2762: The system could not find the file DMPC.EXE. The Cause is the DMPC.EXE file is either not in the \OS2\SYSTEM, or it is not included in the current path. o IC04578: Booting OS/2 2.0 Icons appear on RIPL workstation When booting OS/2 2.0 on a Diskless RIPL workstation, the Icons and folders that are supposed to be on the desktop are sometimes missing. The Icons appear very briefly, and then disappear, leaving nothing but a gray screen. This is an intermittent problem. o IC04598: Access control specifies wrong user with FIXACC Access control occasionally specifies the wrong user after running FIXACC. o IC04631: Case Tool, IEF problem printing from 2.0 Requester When printing from an application, IEF, which is a case tool, the first job prints but the second job never spools or prints from a 2.0 Requester to a 2.0 Server. It works fine printing locally with a 2.0 Requester, from a 1.3 Requester printing to a 2.0 Server, and from a Requester printing to a 1.3 Server. The customer is using a TI Omnilaser 2115, with HP Laserjet Classic, and HP Plus drivers. It is using the 16-bit API from OS/2 1.3 PM. o IC04661: NET SEND Cmd creates Trap D A CMD file was created that uses NET SEND to send four long messages (greater than 250 characters). The CMD generates a TRAP000D CSliM=0A42 CS= 0127 IP= 0784, SYS1811, SYS3175, and NET3504 error messages. o IC04693: Server writes fail but returns successful RC Under a high stress period of continuous large writes, occasionally one of the writes will not make it to disk on the Server, but returns successfully to the user. This seems to happen on Ethernet, and only on a drive being serviced by NETSERVR (i.e. FAT volumes or FAT and HPFS if HPFS386 server is not installed). o IC04694: File PTR problems when WRITEMPX fails Program does approx 1 billion reads/writes, and verifies the file ptr after a write. Occasionally, the file ptr is 4396 bytes farther in the file than appropriate. o IC04741: Low Battery message default is wrong When the low battery parameter is omitted, the default is set to disable. It should be set to warning. The symptom experienced will be no popups or alerts. o IC04750: TRAP000D in NETWKSTA.200 System fails with TRAP000D in NETWKSTA.200 with the following info. TRAP 000D ERRCD=0000 ERACC=**** ERliM=******** EAX=00000054 EBX=00000035 ECX=00000000 EDX=00000002 ESI=0009000C EDI=00090124 EBP=000952E0 FLG=00012207 CS: EIP=2260: 00000032 CSACC=009B CSliM=0000B931 SS: ESP=0030: 000052B4 SSACC=1097 SSliM=000047EF DS=3080 DSACC=0093 DSliM=000001A1 CR0=8001001B ES=0158 ESACC=C093 ESliM=FFFFFFFF CR2=00180483 FS=0000 FSACC=**** FSliM=******** GS=0000 GSACC=**** GSliM=******** LOCATION ##0160: FFF6453F - 000D: A53F 60000, 9084 o IC04761: GREP from C Set/2 cause Hangs, and Traps When using GREP (from the IBM C Set/2 Compiler examples) across a Network, the system will Hang, Trap or IPL randomly. All who have experienced this problem are using the OS/2 2.0, 6055 ServicePak. o IC04769: Server gets a RC=12(ERROR_INVAliD_ACCESS) Server receives a return code 12 (ERROR_INVALID_ACCESS) when trying to open a shared COMM Port, and does not set the device to error status. Result is all incoming requests are queued up waiting for the port. The device is left in an open condition when viewed with the NET DEVICE command, and can not be cleared or reset. o IC04811: DOS App "Consumer Transaction" file corrupted The problem is with IBM's Consumer Transaction program that runs in an OS/2 VDM. It issues a file lock INT 21 FUNC 50 SUBFUNC 0, and then gets the file length as one value. Then it re-positions the file pointer and reads some data, and then tries to read the file length again. This time it gets a different value. At this point, another Consumer Transaction, running on another machine, has appended data to this supposedly locked file, causing data corruption. o IC04940: TRAP 3 for XGA support on Server with ServicePak Trap 3 when user tries to RPL, using XGA device drivers, after the OS/2 2.0 ServicePak(6055) has been applied to the RPL tree. Occurs on both LS 2.0 and LS 3.0. o IC04943: DOSFSCTL to HPFS386 to get EA size causes Trap NVDM/2 was tested with LS 3.0 Advanced. During the reboot after installing NVDM/2, HPFS200.386 trapped. Their IFS issues a DOSFSCTL to HPFS386 to get the max EA size, and max EA list size supported. This is Function=2 of the DOSFSCTL. o IC04963: Details View of Network Icon Traps the Server Open the setting for the Icon NETWORK, select details view. From the details view, select LAN Server, open settings select details. From the LAN Server details, select current Server, open settings, and select details view. From the Server details view select CONTROLLER SHARE, open settings, select details view. and a TRAP000D appears. TRAP 000D ERRCD= 0000 ERACC= **** ERliM= ******** EAX= 907c9057 EBX= 7d340000 ECX= 0000ffff EDX= 7d3d0003 ESI= 01290054 EDI= 012d0000 EBP= 0129536c FLG= 00012202 CS: EIP= 0aa0 : 00006f90 CSACC= 009b CSliM= 0000f583 SS: ESP= 0030 : 00005330 SSACC= 1097 SSliM= 00004877 DS= 1d88 DSACC= 0093 DSliM= 000005ff CR0= 8001fffd ES= 0000 ESACC= **** ESliM= ******** CR2= 012df000 FS= 0000 FSACC= **** FSliM= ******** o JR06198: Unwanted messages with Logon MS LAN MGR REQ/ 2.0 Sevrer MS LAN Manager Requester logging on to LS 2.0 Server gets unwanted error messages, but logon completes. ═══ 3.2. Dos Lan Requester - DLR ═══ o IC03600: Warning missing from install Doc in DLR 2.0 A warning message is needed in the DOS LAN Requester 2.00 installation Documentation. If the PATH statement in the CONFIG.SYS exceeds 255 characters, and is added to the path statement for the DLR, the installation will fail. Changes were made to truncate the the new path at the max DOS allows (127). modified, thus producing an error and exiting. o IC03852: DLR failed to start after DLRINST The requester displayed an error message: "NET074 The network cannot be started. Network adapter resources are depleted." o IC03976: "FILE NOT FOUND" error after Windows setup After setting up DLR Windows with LOAD=WINPOPUP and WINSETUP, starting DLR before Windows causes "FILE NOT FOUND" error message. o IC04107: Incorrect message with installing DLR in Windows When using WINSETUP to update Windows configuration, the step that asks if you want the Windows.INI to be updated is answered NO (do not update ). The install returns with an error message saying that the Windows configuration files have been updated successfully, when actually no update has taken place. o IC04123: DLR/Windows start problem if not Logged on Users trying to start DLR/Windows 3.0 Application without being logged on, are forced to double click on the Icon to start the package. The Logon profile will run, the program will not start, however, the Icon is on the screen. User must click on the Icon to start the program. o IC04124: DLR/Windows 3.0 system error with Charisma DLR/ Windows 3.0 gets a system error when attempting to run a shared application called Charisma, terminating the application with an error message: 'Application Terminated'. o IC04129: DLR/Windows running out of environment space DLR/Windows has a Wordperfect shared application problem with the DOS Windows session running out of environment space. o IC04192: Panel Not Found Error-C371 Max Users Reached Misleading error occurs when a maximum number of users attempting to access an application is exceeded. The "PANEL NOT FOUND" C371 error message should be changed to accurately indicate that maximum number of users attempting to access an application has been exceeded. o IC04205: RIPL Server receives access denied at logon RIPL Server receives access denied when RIPL workstations logon. During execution of certain DLR net commands, permission violations are logged in the audit log. o IC04206: Print Screen of Emulation Session does not print The print screen of Emulation sessions does not print unless HOT-KEY to DOS Session. The DLR was waiting on the INDOS flag to go off for an interrupt 28H. In the AS400 host session this flag was never off, and there was no interrupt 28H until Hot-Keying back to DOS. o IC04210: Printer setup string omitted when using DLR The problem is that the DLR re-director does not always pre-pend the printer set-up string. It works correctly only if the total length of the setup string and the file to be printed is less than the value of the /NBS parameter. This problem occurs in the absence of big buffers. o IC04364: Missing Icons in Public Applications When doing a shutdown, and then logging back on, about half of the Icons in the public applications folder are missing.This is usually an intermittent problem. When they logoff, and then Log back on, the problem is gone. Also when this happens, clicking on some Icons opens other Icons (e.g. clicking on Lotus opens Wordperfect). The Icon that is actually opened was in the place of the clicked on Icon now. o IC04366: Second user Logon Hang with Semantics, and DLR Second concurrent user logging on and attempting to use the Semantics Q and A Application fails during a print operation. A HANG condition usually occurs. o IC04368: Print job from DLR printer prints garbage A Redirected print from Chalke application on DLR to a 5015 or 5050 Server results in garbage being printed out to a 4019 printer. Apparently, data is being read from the Server's Hard disk into the spool file. o IC04370: NET003 after upgrade to L/S 2.0 DLR After upgrading a DLR to L/S 2.0, a NET003 error message appears. /WRK in DOSLAN.INI is missing the last five parameters. o IC04374: DLR Hangs on install or logon with append /X DLR cause PC to hang on install or logging on with append /X in the AUTOEXEC.BAT. There is a conflict with DOS APPEND and DLR in the DMPC.EXE program. o IC04380: Update MSGPOPUP.EXE to set minimum RAM size When there is contention for the Upper Memory Block (DOS 5.0) for resources, MSGPOPUP.EXE fails to load properly and will result in a NET201 error at NET START time. o IC04384: RPL from diskette can't Logon if SIZEREQBUF>/NBS RPL From Diskette unable to Logon if the SIZEREQBUF parameter on the Server is > /NBS parameter on the net start command. o IC04386: Receiving a Message on a DLR Mouse pointer locks When a message is received in Lotus 123 R3.1 and ESC key is pressed, two mouse cursors are displayed, but only one is moveable. o IC04388: DLR locks with WP 5.1, and Windows with DOS 5.0 Starting WP 5.1 in Windows 3.0 with DLR 2.0, causes machine to hang. when the hourglass is displayed. o IC04392: DOS 5.0 DLR Hang Hot-keying FBSS App DLR receiver hangs when running with FBSS and Hotkeying between a 3270 Emulator session and DOS 5.0. o IC04393: DLR: Net Copy command fails, system hangs Net copy from, and to, a redirected drive causes system to hang. o IC04429: REDIR49.EXE after 920723-RIPL-Printer wrong A RIPL workstation using DLR 2.0 and REDIR40.EXE from 920723 onwards, corrupts the printer setup strings. o IC04496: NET START from DOSSHELL yields NET011 When Booting from a DOS 5.0 system which has 2.0 DLR, and invoking the DOSSHELL, select 'RUN' from the pull down menu, and type in NET START. At this point the DLR will attempt to start the DLR code but gives the following errors, and the machine hangs. - NET011: Network Services cannot be started, or stopped in a DOS Session or in a Windows enhanced DOS virtual machine (VM). - NET201: An initialization error occurred 01FF. The DLR should simply error out, then return the user to either the DOS prompt or to the DOSSHELL. o IC04534: NET248 trying to Logon to MS LAN Manager 2.0 A NET248 error appears trying to log on to a MS LAN Manger Server 2.0, or 2.01, with 2.0 DLR. This problem also appears in the 3.0. DLR. MS DLR code and IBM's OS/2 2.0 Requester can Logon fine. o IC04562: DLR @ 5050 can't create file on Network Drive An in house developed application that uses INT21 to create a file on a network drive at 5050 is unable to create a file. The file can be opened and written to. But when attempting to close the file, a message states that the file already exists. The file can eventually be closed by going through the Server's FSI, and closing open files. The file can then be saved successfully. o IC04689: Current.D file created on DLR Hard Drive, app Hangs If a user on a DLR is working in an application, and the app hangs the DLR, the DLR has to be rebooted. This leaves a CURRENT.D file on the Hard Drive of the DLR. When the System comes back up, the NET START, INITFSI, and NET COMMANDS process. When the NET COMMAND processes and an ID and password are entered, they are not able to get in. Sometimes the screen will blank and a 'RUNTIME ERROR' msg is received that just keeps flashing in the upper left hand corner of the screen. If the CURRENT.D file is deleted before starting, the DLR code works fine. ═══ 3.3. User Profile Management - UPM ═══ o IC03995: Trap C on Korean build Logon A Trap C on Korean Build Logon. The stack size for MUGLEXEC.EXE, LOGON.EXE, and MUGACCTS.EXE is not sufficient for the Korean build, traps are intermittent. o IC04110: Server allows Operator in UPM to add users When giving " SERVER " privilege to an operator, the operator can go into UPM and ADD users. Adding users should be restricted to the operators with " ACCOUNTS " privilege only. o IC04427: Bad error message displayed logging on to LAN OS/2 2.0 and LAN Requester 2.0 installed without optional system Utilities, and LAN Requestor 2.0. When attempting to Logon a SYS0317: error message is received: The system cannot find message 61520 in message file OSO001.MSG. A smiling face symbol is also shown. o JR05733: Multiple Node Logon DBM Client not working The second logon to the same Node from the same OS/2 process confuses UPM. UPM will only return the useri, and password entered on the first logon, even though a different userid and password has been entered on the second logon. The search algorithm in MUG_GET_UID was always finding the RAT entry from the previous logon. o JR05878: UPM Logoff does not function after Boot After logon, selecting UPM - LOGOFF displays copyright info only. o JR05893: Move Logoff Window from DBCS countries Logoff Window is out of place, placed to the far left of the screen. This occurs only in a DBCS environment. o JR05912: UPMACCTS stays up after Logging on another User The UPMACCTS interface stays active after logging on another user. Logon locally as an admin, start UPMACCTS, then logon locally with a user that has USER privilege. If multiple local logon option has not been set, the ADMIN has now been logged off and replaced by the USER, but UPMACCTS is still active with ADMIN flow. The USER can now create new ADMINs etc thru UPMACCTS. A similiar situation exists with Domain logons, but the USER will receive ERROR_ACCESS_DENIED when trying to add or modify user accounts. o JR05917: SQL 1024 When a fast Requester starts A test case, which partly runs on a model 90 Requester system, returns an error message saying user is not logged on. The User has to be logged on because other process are running, thus the error message is wrong. o JR06074: Fix typo in UPM.H The line "#pragma linkage (UPMELCOL, far16 pascal)" should be "#pragma linkage (UPMELOCL, far16 pascal)" o JR06130: No Icons in UPM OS/2 ES 1.0 displays standard Icons in the User Profile Management Services folder instead of 'keys'. The 'Logon', 'User Profile Mgmt', and 'Logoff' objects have empty Icons when the UPM Services folder is opened. However if UPM object is opened, the correct Icon (3 very small keys) is seen at the top left of the 'UPM - User Profile' PM Window. Also if the PM Window is then minimized, the correct 3 Keys are clearly displayed in the Minimized Window Viewer. o JR06434: UPM0004C LAN Enabler return code 17 Error message (UPM0004C), when using UPM to change logon password. ═══ 3.4. Publications ═══ o REFERENCES TO COM02.SYS IN "NETWORK ADMINISTRATOR REF VOL. 1" Any references to the file named COM02.SYS that are found in the "Network Administrator Reference Vol. 1: Planning and Installation" should be read as COM.SYS. o LSCLIENT PARAMETERS IN "NETWORK ADMINISTRATOR REF VOL. 2" In the "Network Administrator Reference Vol. 2: Performance Tuning," the description of the LSclient section of the IBMLAN.INI file (page 3-56) does not include two of the LSclient parameters. The two omitted parameters are "logonwarningmsgs" and "logonverification." The descriptions of these parameters follow. The value for the "logonverification" parameter can be one of the following: local the userid and password are validated using the local copy of the accounts database (NET.ACC) domain the userid and password are sent to a domain controller or backup server to be validated using the domain copy of the accounts database (NET.ACC) none no verification is performed; the userid and password are only stored. The value for the "logonwarningmsgs" parameter can be one of the following: all all warning and error messages are displayed nols no LAN Server-specific messages are displayed none no warning or error messages are displayed. o AUTODISCONNECT PARAMETER IN "NETWORK ADMINISTRATOR REF VOL. 2" In the "Network Administrator Reference Vol. 2: Performance Tuning," the description of the "autodisconnect" parameter (page 3-22) should say that setting this parameter to 0 will cause unpredictable results. o PROCEDURE FOR RESYNCHRONIZING INTERNAL PASSWORDS The procedure for synchronizing passwords when they have become unsynchronized is in the "Network Administrator Reference Vol. 2: Performance Tuning," on page 3-48 under the heading "Netlogon Section." o CORRECTION TO NOTE IN "NETWORK ADMINISTRATOR REF VOL. 3" In the "Network Administrator Reference, Vol. 3: Network Administrator Tasks," the first paragraph of the note at the top of page 5-7 should say: Use C: to give default permissions to all files in all subdirectories. Use C:\ to only give access to files in the root subdirectory. o ASSIGNED DRIVE FIELD IN "NETWORK ADMINISTRATOR REF VOL. 3" In the "Network Administrator Reference, Vol. 3: Network Administrator Tasks," under the heading "Setting a Working Directory for System Editor" on page 7-11, the value for the Assigned drive field should be an *. If the field is left blank, an error will occur. o CORRECTION TO "NETWORK ADMINISTRATOR REF SUPPLEMENT" To install OS/2 2.0 RIPL in a subdirectory other than the default subdirectory, use the following procedure. (For related information, see page 4-4 of the "Network Administrator Reference Supplement for OS/2 2.0.") 1. Change DEFAULT.20 FIT to reflect the new subdirectory name. 2. Change all OS2XXX.cnf files (IBMLAN\RPL) to reflect the new subdirectory name. The statement that needs to be changed starts "ldr ". There are 6 of these files. 3. Rerun "GETRPL" to reset the Access Control Points. You can now start the RIPL service. o "COMMAND REFERENCE" CHANGE FOR NET SEND COMMAND Messages that are sent using the NET SEND command in the "NET SEND name message" format can contain a maximum of 241 characters. Any additional characters are truncated or lost. Neither the sender nor the receiver receives an error message to indicate that the message was truncated. The receiver will see up to 241 characters of the message on the popup screen. o APPLICATION PROGRAMMER'S REFERENCE CORRECTION In the "LAN Server 2.0 Application Programmer's Reference," "Appendix A. Include Files" has two errors in the Use and User categories. The USE.H include file declares information pertinent to the Use category, and the ACCESS.H include file defines the User category. DCDB.H is correctly listed under the User category. On page A-4, the Use and User entries should read as follows: API Category Include Files Purpose Use USE.H Declares structures, constants, and functions that examine or control connections (uses) between requesters and servers. User ACCESS.H Declares structures, constants, and functions that retrieve or control user information. Used also with functions in the access permissions and group categories. ═══ 3.5. Messages ═══ o Logging on to a Microsoft LAN Manager Server A workstation running DOS LAN Requester can now log on to a LAN Manager server. o Configuring Environment Variables For Windows Applications Certain applications manipulate resources and store data in ways that require you to alter the network environment to accommodate them. Generally, these applications require more environment space than the default. A larger environment space can be allocated to the DOS Windows environment. DOS LAN Requester Windows allows you to specify the amount of environment space by setting the WLRENV environment variable. The default for WLRENV is 2048 bytes. Applications may require more or less than this amount. The format of the environment variable is: SET WLRENV=nnnn where nnnn equals any value allowed by DOS. If a value other than the default is required, it must be set prior to starting Windows. For example, the WLRENV environment can be manually set to a value other than the default from the command line: 1. At the DOS prompt, type SET WLRENV=1024. 2. Start Windows by typing WIN. o DosMakeMailSlot API The messagesize parameter of the DosMakeMailSlot API cannot be larger than 65471 bytes. Mailslots cannot accept messages larger than 65471 bytes. o Message NET2250 The help information for message NET2250 should read: NET2250: The connection cannot be found. Cause: Either this network connection does not exist or it is paused. Action: To display a list of shared resources that your workstation is connected to, type: NET USE If the connection is paused, continue the connection by typing: NET CONTINUE REQUESTER o Message NET011 If you receive error message NET011 when trying to start or stop DOS LAN Requester, you should exit the DOS 5.0 shell or Windows and then stop or start DOS LAN Requester. ═══ 4. Appendix ═══ Appendix of other interesting topics. ═══ 4.1. Printing Information from this On-line Document ═══ The OS/2 view function provides a print capability to the printer defined an 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. ═══ 4.2. Restarting ServicePak Installation ═══ If the installation procedure stops after selecting the OK 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. ═══ Start Service ═══ ┌──┬───────────────────────────────────────┐ │--│ Start Service │ ├──┴───────────────────────────────────────┤ │ │ │ The service process cannot be │ │ interrupted. After this point │ │ you will not be able to quit the │ │ service process. │ │ │ │ Do not attempt to start the programs │ │ being serviced. │ │ │ │ Do you wish to continue? │ │ │ │ ╔════════╗ ╔════════╗ ╔════════╗ │ │ ║ OK ║ ║ Cancel ║ ║ Help ║ │ │ ╚════════╝ ╚════════╝ ╚════════╝ │ └──────────────────────────────────────────┘ ═══ ═══ The item in the title line is a trademark of IBM Corporation ═══ ═══ The item in the title line is a trademark of Microsoft Corporation