═══ 1. Introduction ═══ IBM LAN ADAPTER and PROTOCOL SUPPORT VERSION 2.20.2 Service Level WR07045 This package is a refresh of the NTS/2 LAN Adapter and Protocol Support (LAPS) program and is intended to replace (upgrade) only LICENSED instances of LAPS. As such, its use is limited to the license agreement under which you obtained the original licensed copy. The versions which are suitable for replacement are: Version Product in which LAPS was included "LAPS V2.00" "Extended Services 1.0" "LAPS V2.01" "LAN Server 2.0" "LAN Enabler 2.0" "LAPS V2.10" "TCP/IP 1.2.1" "LAPS V2.11" "LAN Server 3.0" "NTS/2 1.0" "LAPS V2.13" "TCP/IP 2.0" "LAPS V2.20" "Communication Manager/2 1.1" "LAN Distance 1.0" "NTS/2 ServicePak WR07020" Title to the contents herein and any copies made is retained by the International Business Machines Corporation, Armonk, New York, 10504. ═══ 1.1. OS/2 BBS User's Conference Facility ═══ The OS2LAN CFORUM includes issues, questions, and problems encountered during the installation, customization and use of NTS/2. The OS2LAN CFORUM is on the OS/2 Bulletin Board System (OS2BBS). For additional information call 1-800-547-1283; ask for the Welcome Package. ═══ 1.2. Affected SYSLEVEL Files ═══ SYSLEVEL.TRP IBM OS/2 LAN Adapter and Protocol Support ═══ 1.3. Trademarks ═══ The following are trademarks of IBM Corporation: o IBM o Extended Services o OS/2 o Operating System/2 o Presentation Manager o WIN-OS/2 The following are trademarks of other Corporations: o Microsoft (Microsoft Corporation) o Windows (Microsoft Corporation) o Rumba/400 (Wall Data Corporation) o Rumba/3270 (Wall Data Corporation) o Extra! (Attachmate Corporation) ═══ 2. Installation ═══ This ServicePak installs using the NTS/2 Program Product Installation Aid LAPS.EXE. Please refer to your original product documentation for complete Installation and Configuration details.. Sample files for unattended or redirected installation are included on Diskette #2 in the SAMPLE directory. The following procedure will work for manual (diskette based) installation. o With the LAPS refresh diskette (ServicePak Diskette #1) in drive A:, run LAPS by entering "A:\LAPS", and follow the prompts. o Shut Down and Reboot the system. ═══ 2.1. Installing Additional Network Drivers ═══ Additional network drivers may be found on other media. NTS/2 supplies the following network drivers: ELNKII.NIF 3Com 3C503 EtherLink II Adapter ELNKMC.NIF 3Com 3C523 EtherLink/MC Adapter IBMNET.NIF IBM PC Network II and Baseband Adapters IBMNETA.NIF IBM PC Network II/A and Baseband/A Adapters IBMTOK.NIF IBM Token-Ring Network Adapter IBMTRBM.NIF IBM Token-Ring Network Busmaster Server Adapter IBMXLN.NIF 3270 Adapter for 3174 Peer Communications MACETH.NIF IBM PS/2 Adapter for Ethernet Networks MACWDAT.NIF Standard Microsystems EtherCard PLUS Software-Configured Adapters MACWDMC.NIF Standard Microsystems EtherCard PLUS Micro Channel Adapters UBNEIPC.NIF Ungermann-Bass NIUpc Adapters UBNEIPS.NIF Ungermann-Bass NIUps Adapters Note: When the LAPS diskette (Diskette 1) cannot hold all the network drivers, they are placed in separate directories on a second diskette. You may use the techniques described in the following sections to install them. ═══ 2.1.1. Diskette Installation of Additional Drivers ═══ Once LAPS.EXE has installed the basic LAN Transport Files, selection of the Install button will bring up the Install Additional Network Drivers panel. Enter the drive and path information (d:\path) to the desired network drivers. The drivers may be in Final Form or Packed Form. Note: Alternatively, network drivers can be transfered (copied) directly to the target \IBMCOM\MACS subdirectory. ═══ 2.1.2. Unattended or Redirected Installation of Additional Drivers ═══ Copy the additional network adapter drivers and associated files, except message files, to the IBMCOM\MACS subdirectory of the LAPS diskette image on the code server. You must copy message files to the IBMCOM subdirectory. The additional network adapter drivers and associated files can be in Final Form or Packed Form. If they are in packed form they must have a File Name Extension of ZIP. Please refer to Chapter 3 of the LAN Adapter and Protocol Support Configuration Guide for additional details. To install additional drivers via response files after LAPS installation, you must specify INSTALL=ADDITIONAL in the LAPS response file. All required network driver files must be stored in a single subdirectory. The /S: parameter for LAPS specifies the source drive and directory of the drivers. The /T: parameter (or TARGET keyword in a response file) specifies the target drive letter where the drivers are to be placed. CAUTION: Files must be in Final Form when the INST_SECTION of the response file has INSTALL = ADDITIONAL. ═══ 2.2. Upgrading IBM LAN Server 2.0 to LAN Server 3.0 ═══ NTS/2 has two versions of NETBIOS.OS2. NTS/2 LAPS configuration utility determines the version of LAN Server (or Requester) and installs the appropriate version of NETBIOS.OS2. Using the wrong version of NETBIOS.OS2 can result in unstable LAN operation. Perform the following steps after changing versions of IBM LAN Server or Requester: 1. Select the LAPS Icon or run LAPS.EXE from the \IBMCOM subdirectory. 2. Select Configure from the LAPS logo window 3. With the Configure LAN transports radio button highlighted, Select Continue.... Note: The Configure Workstation panel appears. You may elect to alter your configuration at this time; LAPS automatically determines the LAN version and selects the appropriate NETBIOS.OS2. 4. Select OK. 5. At the LAPS logo window, select Exit 6. Select the drive on which CONFIG.SYS is located. 7. Select Continue... from the CONFIG.SYS Updates window. 8. Continue through the remaining panels and reboot the system. ═══ 2.3. Upgrading RIPL Servers ═══ LAPS does not install Transport Services to the \IBMLAN\RPL\IBMCOM directory. To service the RIPL tree: 1. XCOPY the entire tree structure of the Server's IBMCOM directory to the IBMCOM directory used for Remote IPL. ┌─────────────────── Example ───────────────────────┐ │ │ │ XCOPY /S C:\IBMCOM\*.* D:\IBMLAN\RPL\IBMCOM │ │ │ └───────────────────────────────────────────────────┘ 2. Run GETRPL to update Access Control Lists, etc. This requires that the RIPL server be started and that a LAN administrator be logged on. ═══ 2.4. Installing IBM Extended Services 1.0 Remote Data Services ═══ The Remote Data Services feature of IBM Extended Services Version 1.0 should be installed using the Basic Configuration and Installation Option from the Extended Services Installation Options menu. This will ensure that the all Extended Services internal data structures are setup to recognize the presence of NTS/2. ═══ 3. 802.2 Virtual Device Driver - Emulator Considerations ═══ To make your emulator easier to use, we recommend creating an icon on your OS/2 desktop for your emulator. In the discussions below relating to emulator settings, d:\EmulPath refers to the drive and path of where your emulator program is installed. CFGFILE refers to the name of your emulator configuration file. The path and configuration File Name of your particular emulator will be different from the examples below. Warning: The following problems may occur: o If a Windows emulator will not successfully start while another Windows emulator is running, it may be necessary to start the emulators in reverse order. o If a Windows emulator will not successfully start while another Windows emulator is running, it may be necessary to toggle (Ctrl-Esc) back and forth to the OS/2 desktop or minimize the running emulator session before starting the second emulator. o It is not possible to run two WINOS2 sessions while using XGA video mode. Refer to the OS/2 README for additional information on restrictions using WINOS2 and XGA. ═══ 3.1. PC/3270 for DOS emulator ═══ On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\CFGFILE.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen. o Before attempting to run PC3270 for DOS, edit your CFGFILE.BAT file adding COMMAND.COM as the last line in the file. This must be done every time you change your emulator configuration. Failure to add COMMAND.COM to your .BAT file will cause PC3270 to exit when it attempts to return control to DOS. ═══ 3.2. PC3270 for Windows emulator ═══ PC3270 for Windows can run either as a regular Windows program (inside a WIN-OS/2 session), or it can run 'seamlessly.' Seamless means the PC3270 windows appear on top of the OS/2 desktop directly, instead of appearing inside a WIN-OS/2 command prompt. To run PC3270 as a WIN-OS/2 application: o Create a file called CFGFILE.BAT. This file should look like this: @ECHO OFF COPY d:\EmulPath\CFGFILE.CNF d:\EmulPath\$$TEMP$$.BAT > NUL CALL d:\EmulPath\$$TEMP$$.BAT ERASE d:\EmulPath\$$TEMP$$.BAT CALL d:\EmulPath\SOMEFILE %1 %2 %3 %4 %5 %6 %7 %8 %9 o Create another file called SOMEFILE.BAT (this file is referenced in CFGFILE.BAT: @ECHO OFF C:\OS2\MDOS\WINOS2\WINOS2 d:\EmulPath\PCSPDOS.EXE -END o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\CFGFILE.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen. To run PC3270 Seamlessly: o Create a file called CFGFILE.BAT. This file should look like this: @ECHO OFF COPY d:\EmulPath\CFGFILE.CNF d:\EmulPath\$$TEMP$$.BAT > NUL CALL d:\EmulPath\$$TEMP$$.BAT WINOS2.COM PCS3270.EXE o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\PC3270W.EXE Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select WIN-OS/2 window, click on Separate Session, then click on WIN-OS/2 Settings. o On the WIN-OS/2 Settings panel, add the following to the end of the DOS_SHELL statement: /C d:\EmulPath\CFGFILE.BAT Note: If you start PC3270 for Windows, and get a message saying there is invalid TSR information, then edit the CFGFILE.CNF file and change the line 'REM TSR=N' to 'REM TSR=Y'. ═══ 3.3. Attachmate's Extra! Extended for DOS ═══ o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\CFGFILE.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen. o Before attempting to run Extra! for DOS, you must edit your CFGFILE.BAT file, and add COMMAND.COM as the last line in the file. This must be done every time you change your emulator configuration. Failure to add COMMAND.COM to your .BAT file will cause Extra! to exit when it attempts to return control to DOS. Note: It may be necessary to run the VDM configuration utility, LTSVCFG, with the P=x parameter where x is a nonzero value indicating the number of half seconds the deadman timer will wait before expiring. This will be necessary if the emulator looks like it is hung. Typically this value should be set to 2 if needed. ═══ 3.4. Attachmate's Extra! Extended for Windows ═══ o Create a file called EXTRA.BAT. This file should look like this: @ECHO OFF C:\OS2\MDOS\WINOS2\WINOS2 o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\EXTRA.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen. Note: The Extra! for Windows installation program normally modifies the AUTOEXEC.BAT file to add its directory to the PATH statement, and to add a DLCINTFC statement if Lan support is used. This information is also needed when running under OS/2. We suggest you keep this information in your AUTOEXEC.BAT file, exactly as Extra! for Windows placed it. Alternatively, you can add the DLCINTFC statement to your EXTRA.BAT file instead of adding it to AUTOEXEC.BAT. ═══ 3.5. PC Support/400 ═══ PC Support will not run correctly in DOS Emulation mode. To run PC Support, you must start a version of DOS (such as DOS 5.0, etc.) that will run PC Support. Please refer to the Master Help Index of OS/2 for information on how to start a specific version of DOS. Search for 'Starting DOS.' When you create a diskette or diskimage for a specific version of DOS, you must insure the CONFIG.SYS file for that DOS version loads the following device drivers: DEVICE=C:\IBMCOM\PROTOCOL\LANVMEM.SYS DEVICE=d:\EmulPath\EIMPCS.SYS DEVICE=d:\EmulPath\ECYDDX.SYS In addition, you may want to create an AUTOEXEC.BAT file for your specific DOS version that automatically starts PC Support. To do this, invoke STARTPCS.BAT from your AUTOEXEC.BAT file. o On the Program panel, set the following parameters: Path/Filename = * Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen, then click on DOS Settings. o On the DOS Settings panel, set the following parameters: DOS_STARTUP_DRIVE = A:\ KBD_CONTROL_BYPASS = ALT_ESC In this example, DOS_STARTUP_DRIVE is set to A:\ with the assumption you are loading the specific DOS version from diskette. If you load the specific DOS version from a diskette image file on your hard drive, update the DOS_STARTUP_DRIVE accordingly. Warning: Some known problems: The PC Support installation program may update the CONFIG.SYS file and add two device drivers 'EIMPCS.SYS' and 'ECYDDX.SYS.' If these statements are in your CONFIG.SYS, remove them. Under OS/2, these statements will instead be loaded from your bootable DOS diskette. Each Virtual DOS Machine (VDM) will need a separate APPC controller on the AS/400. The controllers can be exactly the same except for the LAN destination service access point (LAN DSAP: 08). A line in the CONFIG.PCS needs to contain a matching TRSS entry (TRSS 08). It is necessary to run the VDM configuration utility, LTSVCFG, with the P=x parameter where x is a nonzero value indicating the number of half seconds the deadman timer will wait before expiring. Typically this value should be set to 1 for using a single VDM and increased to 4 if additional VM Boot sessions are active. When additional VM Boot sessions are active it is recommended to decrease the MAXWAIT parameter in CONFIG.SYS to 1 second. When running more than 2 sessions in a stress environment it may be necessary to obtain OS/2 2.0 Service Pak (XRx6055). For valuable information required for operating PC Support/400 in a VDM, please reference IBM publication GG24-3856 entitled "Using DOS PC Support/400 in OS/2 V2 Virtual DOS Machines". ═══ 3.6. Wall Data's Rumba/400 emulator ═══ o Create a file called RUMBA.BAT. This file should look like this: @ECHO OFF D:\PCS\STARTRTR D:\PCS\CONFIG.PCS C:\OS2\MDOS\WINOS2\WINOS2 In this example, D:\PCS is the directory where PC Support is installed. Rumba/400 requires PC Support in order to run. o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\RUMBA.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen ═══ 3.7. Wall Data's Rumba/3270 emulator ═══ o Create a file called RUMBA.BAT. This file should look like this: @ECHO OFF d:\EmulPath\WDTOKTSR.EXE /R=16 /T=8 C:\OS2\MDOS\WINOS2\WINOS2 WDTOKTSR.EXE is required by Rumba/3270 in order to use Lan support. Refer to the Rumba program documentation for more information about command line parameters. The above parameters work in most cases. o On the Program panel, set the following parameters: Path/Filename = d:\EmulPath\RUMBA.BAT Parameters = blank Working Directory = d:\EmulPath o On the Session panel, select DOS Full Screen. ═══ 4. TCP/IP for DOS - Considerations ═══ Before you can use TCP/IP under OS/2 2.0, you must set up certain DOS settings. To create an icon and initialize the DOS settings, follow these steps: o On the Program panel, set the following parameters: Path/Filename = * Parameters = Blank Working Directory = C:\TCPDOS (Assuming TCP/IP was installed on C:\TCPDOS) o On the DOS Settings panel, click on 'Session' and set the following parameters: DOS_DEVICE = C:\TCPDOS\BIN\NETDEV.SYS (Assuming TCP/IP was installed on C:\TCPDOS) LTSVCFG.COM must be run with parameter D=1 before TCP/IP can run in a VDD. This is necessary because TCP/IP uses the direct station link of the 802.2 protocol. A slash is used to signify the adapter number. Adapter Number Command to Run Adapter 0 LTSVCFG D=1 Adapter 1 LTSVCFG / D=1 Adapter 2 LTSVCFG / / D=1 LTSVCFG can be included in the AUTOEXEC.BAT file to execute automatically. or run manually from a DOS command prompt. When running TCP/IP's file transfer application FTPD and FTP it is necessary to clear the APPEND environment variable on both the server and client machines. This can be done by commenting out the LOADHIGH APPEND C:\OS2;C:\OS2\SYSTEM statement in the AUTOEXEC.BAT file, or by entering APPEND=* at the DOS command prompt. This is necessary because if the files being transferred appear in the APPEND path of the destination machine, the APPEND path will override the specified destination path. ═══ 5. Applets, Include Files, and CID Utilities ═══ The second diskette of this ServicePak includes the following subdirectories: SRVIFS Updated SRVIFS Files LCU Updated LCU Files APPLETS Sniffle and NetPing Utilities. IBM does not provide support for these programs. SAMPLE Assorted examples. IBM does not provide support for these. INCLUDE C header and MASM include files for developing 802.2 and NETBIOS applications. Refer to Chapter 6 of the "Supplement to the Local Area Network Technical Reference" publication (SD21-0049-00) for a brief description of each file. ═══ 5.1. SNIFFLE ═══ SNIFFLE is a standalone utility that is intended to aid in the development of network information files (NIFs). Invoked against one or more NIFs, SNIFFLE ensures that the NIF sections, keywords, and values are consistent both with the extended NIF format definition and with each other. For more information on the extended NIF format definition, see the "IBM OS/2 NDIS Driver Implementation Package". If an error is detected, SNIFFLE indicates the location of the error and provides a description of the error condition. An example of its use for the IBMTOK.NIF would be to type the following at an OS/2 command prompt: SNIFFLE IBMTOK.NIF ═══ 5.2. NETPING ═══ NETPING is a NETBIOS utility that executes a NETBIOS NCB.FIND.NAME. Command line options provide the capability of searching for various application's NETBIOS names, such as LAN Server and DB2/2. If the NETBIOS name is present on the LAN, the following information will be displayed. o NETBIOS name type o Node Address o Routing Information (if name was not found on local segment) NETPING is case sensitive and the command line options are: /a# Specifies adapter, where # can be 0|1|2|3 (default is 0) /n Name is NOT padded with blanks but with 0x00 /m IBM LS messenger name /q IBM LS requester name /v IBM LS server name /rxy IBM DB2/2 requester name x can be: s (sql name); i (interrupt name) y can be: p (primary); s (secondary) /sxy IBM DB2/2 server name x can be: c (catcher name); b (callback name) y can be: 0 (adapter 0); 1 (adapter 1) An example of its use for LS Server NETBIOS name SERVER1, searching on adapter 1 is: netping SERVER1 /a1 /v ═══ 6. Things that Changed ═══ The following sections describe changes that have been made to the product's executables, publications, and messages/helps. ═══ 6.1. New Features ═══ The following sections explain new and enhanced NTS/2 features. ═══ 6.1.1. TRACENAMES - New Parameter for NETBIOS Traces ═══ The TRACENAMES parameter is used to limit tracing activity to the interaction between specified machines. Prior to the offering of this parameter, tracing at the transport level picked up all frame activity on the line, causing the trace buffer to quickly fill with irrelevant frame records. This parameter is ideal for isolating a problem between a server and requester on a large network. Tracing is limited by selecting NETBIOS names on remote machines using the TRACENAMES parameter. Names can be specified as either a 16-byte ASCII or 32-byte Hex value. Up to four names can be selected in either format. The asterisk wildcard character (*) can be used in the ASCII format for ease of use, or to increase the number of remote names traced if machines have similar names. All names must reside on the same line as the TRACENAMES parameter. Incorrect length or invalid hex numbers cause an error and NETBEUI will not load. TRACENAMES works in conjunction with the OS2TRACEMASK parameter and the TRACEOFF parameter already available for NETBEUI in NTS/2 version 1.0 and LAN Server 3.0. The OS2TRACEMASK must be set to the necessary nonzero values to activate any NETBIOS traces. The recommended setting is 0x07FF. NDIS activity will not be filtered if the NDIS bits are activated in OS2TRACEMASK. The TRACENAMES parameter must be inserted into the PROTOCOL.INI file using an editor and is not yet a part of the LAPS config and install tool. TRACENAMES must be placed only in the NETBEUI_nif section. The following example shows the general location and format of the parameter: PROTOCOL.INI [NETBEUI_nif] DriverName = netbeui$ Bindings = IBMTOK_nif ... ... DLCRETRIES = 5 OS2TRACEMASK = 0x07FF TRACENAMES = "req1 " "req2 " "req3 " Other valid TRACENAMES formats are: TRACENAMES = "72617131202020202020202020202000" "req2 *" TRACENAMES = "req*************" "72617131202020202020202020202020" Activity relevant to the remote NETBIOS is traced. This includes NCBs issued with that remote name, as well as all session activity related to that remote name. All statuses from the lower layers are reported whether related to the remote station or not. Frame activity between the remote and local machines is traced by LSN number after the session is established with the remote machine. A maximum of 12 active sessions is traced. Some NCBs are not associated with a remote name or LSN and are not traced: o Add Name o Add Group Name o Delete Name o Cancel o LAN Status o Session Status o Receive Broadcast Datagram o Send Broadcast Datagram NCB.Reset is traced even though it is not related to sessions or specific names. Datagrams and other UI frames are traced if they contain a remote name specified in TRACENAMES. RECEIVE.ANY type commands are traced on completion if they report a session event related to a specified remote machine. ═══ 6.1.2. ODI2NDI Obtains Universal Address Automatically ═══ For ODI2NDI.OS2(V1.0), configuration of the NETADDRESS parameter was required, even if the user wanted to use the Network adapter universally administered address. This requirement is necessary because ODI2NDI must provide the NETADDRESS to the ODI protocol (IPX) before ODI2NDI can obtain the adapter netaddress through the NDIS interface. ODI2NDI.OS2(V1.1) will now attempt to automatically obtain the Network adapter's permanent universal address from the MAC if the NETADDRESS parameter is not configured in the ODI2NDI.OS2 section of PROTOCOL.INI. This presumes that the physical adapter supports the required programming interface. The following modifications to CONFIG.SYS enable this enhancement: 1. Configure ODI2NDI for a Network adapter MAC using the LAPS configuration. 2. Manually perform the following updates to CONFIG.SYS: a) Locate the Network adapter MAC device driver statement in CONFIG.SYS. For example, for IBM Token Ring Network Adapters, the MAC device driver statement is: DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2 b) Position the the MAC device driver statement after the PROTMAN.OS2 device driver statement, but before the ODI2NDI.OS2 device driver statement in the CONFIG.SYS file. An example CONFIG.SYS fragment is: : DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM : : DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2 : : REM --- NetWare Requester statements BEGIN --- DEVICE=C:\NETWARE\LSL.SYS RUN=C:\NETWARE\DDAEMON.EXE device = C:\ibmcom\protocol\odi2ndi.os2 : : c) Save the modified CONFIG.SYS. You must restart your computer for the change to take effect. The manual updates to the CONFIG.SYS file need to be done only the first time the ODI2NDI protocol is configured for a Network Adapter MAC. Modifying ODI2NDI or MAC parameters does not require additional updates to CONFIG.SYS. Note: This enhancement does NOT work with ALL Network adapters. If the enhancement does not work with your Network adapter, message LT80227 is displayed when you start your computer. This message is also logged in the LANTRAN.LOG file located in the IBMCOM subdirectory. If message LT80227 occurs, use the LAPS configuration utility to configure the NETADDRESS for ODI2NDI.OS2. ═══ 6.1.3. LAPS Icon on the Desktop ═══ After NTS/2 LAN Adapter and Protocol Support (LAPS) has been installed and configured on an OS/2 2.x system, a LAPS icon is placed in the System Setup folder. Double clicking on the icon brings up the LAPS installation/configuration utility. ═══ 6.2. NETBIOS Protocol Stack Defects ═══ Files that changed: \IBMCOM\PROTOCOL\NETBEUI.OS2 \IBMCOM\PROTOCOL\NETBEUI.NIF \IBMCOM\PROTOCOL\NETBIOS.OS2 \IBMCOM\LT0.MSG \IBMCOM\LT0H.MSG ═══ 6.2.1. Fixed APARs ═══ o IC04951 - UNC Name failures with IBM Ethernet References to a resource by UNC names failed with error code SYS0240 on the server that was working on the NETBEUI stack with IBM Ethernet. o IC05402 - SOURCE ROUTING FIXES IN NETBEUI Fixes were required for receiving frames on a link that crosses source-routing bridges - the route of the incoming frame should not be assumed to be the same as the route used for outgoing frames. For TEST frames received with 2 bytes of Routing Information, the TEST response was built incorrectly. o IC05486 - TRAP IN NETBEUI ON A VALUEPOINT MACHINE Residual code from an OS/2 EE 1.3 environment remained in NETBEUI. Residual code caused the Trap D. o IC05526 - HPFS386 SIDEBAND TRAP D ON ETHERNET When running HPFS386 on Ethernet and attempting to copy a file from a redirected drive, a Trap D occurred at CS:C08 EIP:8A5. o IC05551 - TRAP D IN NETBEUI - INITDS CORRUPTED Trap D was caused by an invalid selector for low memory data segment. o IC05673 - Four Separate Symptoms o IC05673 - 1) SESSION NOT ESTABLISHED IF SABMES ARRIVE AT WRONG TIME If sessions were being brought up simultaneously on two machines, SABMEs and UAs can conflict causing session establishment to fail. The data area is then corrupted because the link state is wrong. o IC05673 - 2) RECEIVE BROADCAST LOOPING When two or more applications have a receive_broadcast NCB outstanding, issue the next receive_broadcast on appendage. NETBEUI goes into a loop processing the appendage NCB as an additional receive on the receive_broadcast queue. o IC05673 - 3) SESSION_ALIVE SENT WITH INCORRECT LSN NUMBER CAUSES CORRUPTION Session_Alive sent with incorrect LSN number causes corruption of the NTE Listen queue. Links can drop afterward. Fix was to correct sending of Session_Alive frame to have correct LSN number only from links in Normal state. o IC05673 - 4) ADJUST ORDER OF SABME/UA RESPONSES Reordered processing of link establishment and closing prevents case of extra receive ready, or FRMR. o IC05780 - STARTING LS 3.0 WHILE 3270 COMING UP CAUSES COM505 ERROR - If starting LAN Server and Communications Manager 3270 feature at the same time, Communications Manager 3270 will hang with COM505 Error. o IC05794 - NETBIOS RESET RETURNS RC=23 Applications on Token Ring Network can issue "Reset" before NETBIND has completed. When this occurs, NETBIOS returns RC=38 (Requested Resource Not Available) and then RC=23 (Invalid LAN Adapter Number). Serialization of the NETBIND execution process can solve the problem. This fix increases the number of "Reset Retries" which should mask any such race condition. o IC05869 - TRAP E IN NETBEUI Trap E occurs during Remote IPL of OS/2 2.0 or OS/2 2.1. o IC05902 - XMIT_TEST_CMD RESPONSE LOST BY NETBEUI Under certain circumstances Transmit_Test_Cmd is rejected by Netbeui and passed to the next protocol stack. o JR06350 - Redirector failing to Reset NETBEUI was clearing a flag bit whether it actually issued the hard reset or not. Clearing this flag bit when a different flag bit was set prevented NETWKSTA.SYS from issuing the reset. o JR06550 - WCMME - CLIENT REMOTE BUSY STATE CAUSED SERVER HANG Client remote busy state caused server to stack up I frames of session alive. o IC06115 - Duplicate LAA Causes Errorous Server Name-In-Conflict Two LAN requesters with the same LAA causes a name-in-conflict frame to be sent indicating that the Server's name is in conflict. The name-in-conflict frame caused the Server to remove it's NETBIOS name, shutting down the Server. o IC06224 - NETBEUI Stack Corruption Causes Various Session Control Problems Corrupted NETBEUI stacked caused session abends and Trap E. o IC06398 - Pulled PC-NET Cable Fails To Provide Proper NETBIOS Return Code When executing NETBIOS applications and the PC-NET cable is pulled, all NETBIOS commands appeared to be executing (no return code to indicated a NETBIOS reset was needed). A pull PC-NET cable causes a network status of NO CARRIER and the adapter is NOT closed. NETBIOS now waits 60 seconds before returning a return code to indicate that a NETBIOS reset is needed. o IC06414 - NETBIOS Reset Returns Incorrect Resource Information When a NETBIOS reset is issued to an adapter that is not being used by LAN Server, the reset returns incorrect resource information and completes with a return code 0x09. This problem was introduced in NTS/2 CSD WR07020. o JR06550 - Requester RemoteBusy Causes Server To Hang Requester workstations were in a ReMoteBusy state. This caused the Server to fill up the I-Frame buffer with SessionAlive frames. Eventually this caused the Server to hang if the requester workstations remained in a ReMoteBusy state. o JR07633 - NETBIOS Fails To Detect Bad PC-NET Card During Initial Adapter Open During IPL, NETBIOS failed to execute a check on the hardware status bits during the initial open adapter. If the PC-NET card was open but the hardware status bits indicated a problem, NETBIOS never detected it. ═══ 6.2.2. Other Fixes ═══ o NETBEUI INITIALIZATION FAILS Some configurations caused NETBEUI to fail to initialize. o INCORRECT PACKET SIZE BROUGHT DOWN LAN SERVER 3.0 An Ethernet-only requester reaching a token-ring Busmaster server through an 8209 bridge eventually caused the server to have multiple sessions and then the server could not communicate with the Ethernet requester or the token-ring requesters. The packet size was being altered by the 8209 bridge. o NETBEUI WAS NOT LOOKING FOR 2 IN MINOR NDIS VERSION IN THE COMMON CHARACTERISTICS TABLE To determine if a MAC driver supports an extension to the MAC Service-Specific Characteristics, NETBEUI should be looking for a 2 in the Minor NDIS Version in the Common Characteristics table. o ILLEGAL FRAME SIZE CAUSED TRAP D When an illegal frame size was checked, it caused a Trap D in NETBEUI. o TRAP D WHILE RUNNING NETSERV.EXE A Trap D occurred in CS:OC78 EIP:EC9 o NETBIOS FAILED TO INITIALIZE ON ANY OS/2 VERSION GREATER THAN 2.0. Install NTS/2 on OS/2 2.1 and configure for NETBIOS. During IPL, NETBIOS failed to initialize. This indicated the wrong version of the operating system. o AFTER RUNNING A LONG PERIOD OF TIME, NETBIOS RETURN ERROR 22 Too many outstanding NCBS (un_freed) cause NETBIOS to return "to Many Commands Pending" (RC=22). This occurs over a varying period of time depending on LAN activity. o Access Denied Copying a 583120 Byte File To Server When attempting to copy a 583120 byte file from a requester to a HPFS386 server, an access denied was caused by NETBEUI. o NETBIOS NCB.STATUS Failed To Return Correct Datagram Size The datagram length was calculated incorrectly causing data to be lost. o NAME-IN-CONFLICT Message When a NAME-IN-CONFLICT occurs, a NAME-IN-CONFLICT message LT00102 will be logged to the LANTRAN.LOG file indicated the NETBIOS name-in-conflict and the node address of the workstation sending the NAME-IN-CONFLICT frame. When a NAME-IN-CONFLICT occurs with a LS Server name, the message will also pop-up to the screen. o Prevent NETBIOS Timers From Wrapping NETBIOS timers are now set to maximum value if wrapping occurs. o NETBIOS returns FF Return Code As Final NETBIOS Return Code A NCB.SEND command completed on interrupt before the NCB.SEND was put on a queue with a FF pending code. The final return code was overwritten with FF. Some NETBIOS applications received a NETBIOS return code 13 due to this problem. o Configuration Of Different Netbios Transports Causes Trap D A trap D occurred in NETBIOS.OS2 when two different NETBIOS transports were configured with one of them having insufficient resources configured in protocol.ini for what was requested in ibmlan.ini file. The trap occurred on the first NETBIOS command issued other than a reset. ═══ 6.3. IBM Token Ring MAC Driver Defects ═══ Files that changed: \IBMCOM\MACS\IBMTOK.OS2. ═══ 6.3.1. Fixed APARs. ═══ o IC07131 - XMIT_STATUS Field Incorrect In a SCION TransmitConfirm. The xmit_status field in a SCION TransmitConfirm subsequent to a bridge frame forward indicates the status of the transmitted frame. Incorrect values were being stored in this field. ═══ 6.4. IBM Token Ring Busmaster MAC Driver Defects ═══ Files that changed: \IBMCOM\MACS\IBMTRBM.OS2. ═══ 6.4.1. Fixed APARs. ═══ o JR05729 - BUSMASTER DOES NOT RECOVER FROM LOBE FAULT. LAN Server/Requestor 2.0 could not be restarted on machines equipped with Busmaster cards after the cable was unplugged and replugged. o JR06486 - BUSMASTER TRAP D UNDER HEAVILY STRESSED NETWORK The Busmaster driver was performing a call that was not legal at the time. This caused a Ring 0 Trap D. ═══ 6.4.2. Other Fixes ═══ o BUSMASTER UNABLE TO RE-ENTER RING AFTER DUPLICATE ADDRESS One machine booted and got a particular token ring address. Another machine (with Busmaster) booted requesting the same address, and got a duplicate address indication, closing the adapter. The first machine left the ring, freeing the address. Any attempt to reopen the previously failed busmaster adapter using Communication Manager failed, still indicating a duplicate address. o WRONG FILTER VALUE USED Prior to deleting an address, the first byte of the address was checked against 80h, which is the equivalent of universal group. It should be checked against C0h, which is local group. This caused what was accepted in the add to be rejected in the delete. Making this change created consistency with the add address. ═══ 6.5. IBM Token Ring 16/4 Adapter II (IBM16TR.OS2) ═══ Files that changed: \IBM16TR\IBM16TR.OS2 (Additional Driver Diskette) \IBM16TR\IBM16OS2.NIF (Additional Driver Diskette) ═══ 6.5.1. Fixed APARs. ═══ There are no fixed APARs for IBM Token Ring 16/4 Adapter II ═══ 6.5.2. Other Fixes ═══ o IBM Token Ring 16/4 Adapter II MAC Driver Upgraded to Version 3.0 The IBM Token Ring 16/4 Adapter II MAC Driver found on the NTS/2 Additional Driver Diskette has been upgrade from Version 1.0 to Version 3.0. ═══ 6.6. Install & Configuration Defects (LAPS) ═══ Files that changed: \IBMCOM\DLL\LAPSPM.DLL \IBMCOM\DLL\ LAPSCID.DLL \IBMCOM\DLL\IBMLXCFG.DLL \IBMCOM\IBMLXCFG.HLP \IBMCOM\LAPS.EXE \IBMCOM\XI1.MSG \IBMCOM\LAPSICON.EXE \IBMCOM\LAPSRSP.EXE \IBMCOM\THINLAPS.EXE \IBMCOM\LAPSDISK.EXE ═══ 6.6.1. Fixed APARs ═══ o IC04997 - USING ADAPTER NUMBERS TO GUARANTEE UNIQUENESS FOR LANVMAC LANVMAC requires that its upper boundary be strictly defined; the Media Access Control (MAC) for adapter 0 can only be defined for adapter 0. o IC04999 - LAPS CONFIGURATION NEEDS TO TREAT LANVMAC NETADDRESS LIKE LANDD Function was added that treats the LANVMAC netaddress field the same as the LANDD netaddress field. o IC05159 - MAINTENANCE INSTALL OF LAPS DURING CID FAILS ON OS/2 2.1 When running maintenance LAPS installation using CID on OS/2 2.1, LAPS failed while attempting to update the IBMLVL.INI file. o IC05553 - NTS/2 INSTALL DID NOT PUT LANVDD AND LANPDD IN THE CONFIG.SYS FILE (LAPSPM.DLL) On OS/2 2.1, the NTS/2 install did not place statements for LANVDD.OS2 and LANPDD.OS2 in the CONFIG.SYS file. o IC06187 - Proper Version Of NETBIOS Is Not Copied For CID /E:PREP Install When CID installing LAPS using the /E:PREP option, NETBIOS.LS? was not copied to NETBIOS.OS2 based on the version of LAN Services installed. This problem was introduced with NTS/2 CSD WR07020. o IC06413 - CID Install Of Long File Name Fails CID install using HPFS Long File Name caused a LAPS return code XI00041. o IC07132 - Invalid Driver IBMTOK02$ When Configuring for 2 Token-Ring Adapters This problem was introduce in LAPS version 2.20.1. When configuring for two NDIS or NDIS_MULT type drivers, the numeric digit 02 was appended to the driver name in the protocol.ini. During IPL, the second MAC driver failed to bind because the driver name was incorrect. The numeric digit 2 is now appended to the driver name. ═══ 6.6.2. Other Fixes ═══ o ERROR IN NIF VALIDATION WHEN CHECKING DEFAULT AGAINST RANGE (LAPSCID.DLL LAPSPM.DLL IBMLXCFG.DLL) The NIF validation code was incorrectly handling the case in which a default value of type HexString was being checked against the arguments of the Range keyword. The check failed if the default value was enclosed with double quote characters or specified with a "0x" prefix. The problem only occurred in the situation where the parameter was of type HexString, had a default value, had a specified range, and the default value had quotes and/or a prefix. o VDD/PDD CONFIG.SYS PROBLEM Eliminates LANVDD and LANPDD device statements from the CONFIG.SYS file if 802 or NETBIOS are not configured. o FIX REDIRECTOR STATEMENT Fixed redirector statement position in the CONFIG.SYS file. o LAPS CONFIGURATION GENERATES DIFFERENT RESULTS Upon configuring the LANVMACs, LAPS configuration set the drivername on entries 2-n to LANVMA2 and the module names for entries 2-n end in "_nif2". o CREATING RESPONSE FILE FROM LAPSRSP.EXE - IMPROPER TARGET KEYWORD Specifying a target using LAPSRSP.EXE generates a response file containing "target_drive" instead of "target". o TAB Function Fails With LAPS Configuraton Utility Pressing the TAB key selected the OK pushbutton instead of moving to next configurable parameter within the LAPS configuration utility. o CONFIG.SYS Drive Is Not Correct When Copying NETBIOS.OS2 The wrong CONFIG.SYS drive was used to copy NETBIOS.LS2 or NETBIOS.LS3. This caused NETBIOS.LS3 to always be copied when installed on the non-boot drive. This problem was introduced with NTS/2 CSD WR07020. o LAPS Able To Configure 64 Logical Adapters LAPS configuration utility increased the number of configurable logical adpaters from 16 to 64. o NLS LAPS CID Install Causes Trap D LAPS CID install on various NLS verions caused a Trap D when XI1.MSG message file was used. ═══ 6.7. 802.2 Protocol Stack Defects ═══ Files that changed: \IBMCOM\PROTOCOL\LANDD.OS2 \IBMCOM\PROTOCOL\LANDLLDD.OS2 \IBMCOM\\LANMSGDD.OS2 ═══ 6.7.1. Fixed APARs ═══ o IC04923 - MULTICAST ADDRESS SUPPORT FIX The multicast address support functions in 802.2 fixes to loopback path, error codes, and command codes. o IC05000 - TRAP D IN LANDD CODE RUNNING 75+ WORKSTATION GATEWAY (LANDD.OS2) Each time the links were deactivated, the downstream emulators reactivated the link and the LU-LU sessions were automatically reestablished. A Trap D occurred. o IC05001 - COMMUNICATIONS MANAGER (CM) UNABLE TO STOP NORMALLY OR ABNORMALLY CM was unable to exit because it cannot close the token-ring link to the AS400. The hang was due to the Close.Station being issued on the completion appendage for a Transmit.I.Frame, resulting in a DISC sent to the MAC, the T1 timer started and the Link state set to disconnecting. When the completion appendage returns to NETBEUI, it continues processing the I-frame completion which stops T1. o IC05003 - UNABLE TO REOPEN BUSMASTER ADAPTER AFTER LOBE FAILURE (LANDLLDD.OS2) o IC05360 - TRAP D IN LANDLL; CS=0C38; Attempting to bring up LAN Net Manager (LANDLLDD.OS2) results in TRAP=000D with the CS register at x'0C38' o IC05753 - LANDD INCORRECT FRAME CAUSED TRAP D (LANDD.OS2) The Trap D occurred when remotely configuring a LAN-attached printer. A pop-up said the action was successful, then there was an OK button. If the button was not clicked, after about 20 seconds, a Trap D occurred. o IC06177 - SNA Gateway Loses Its LU Connections The problem Workstations intermittedly lost their 3270 LU connections to the Gateway machine. The Gateway eventually recovered on its own and the Workstation's LU connections were re-established. The problem occurred because extended registers were not used and caused a memory index problem. o JR07531 - Trap D In LANDD When LAN Station Manager Is Installed A Trap D occurred when LAN Station Manager device driver (LSMMIB2) was loaded. LAN Station Manager declared itself as an NDIS Extension application but did not provide the data structure corresponding to an NDIS Extension. LANDD will now check the length of the data structure to see if it has a NDIS Extension length. o IC07133 - LANDD Loops while MAC Adapters Initialize DMA LANDD was looping while various MAC Adapters were initializing their DMA. This cause the system to appear to be hung for approximately 30 seconds. LANDD thread is now blocked during initializing time. ═══ 6.7.2. Other Fixes ═══ o RECEIVE COMMAND WITH RETURN CODE = 20 SHOULD ZERO OUT THE BUFFER POINTER (LANDLLDD.OS2) When the receive command completed with return code = 20 (lost data, no buffers), the buffer pointer should be 0 since there were no partial buffers. o SERVER ACCESS POINT POOL SIZE OF 1000H NOT HANDLED (LANDD.OS2) When the maximum size, 0x1000 was used for pool_length in a DIR.OPEN.DIRECT, a return code of 0x16 was returned. The value should work appropriately. o NDIS 2.0.1 EndReset Supported In LANDD.OS2 LANDD.OS2 was not supporting NDIS 2.0.1 EndReset and was fixed to support the NDIS 2.0.1 EndReset function. ═══ 6.8. 802.2 and NETBIOS Virtual Device Driver Defects. ═══ Files that changed: \IBMCOM\LTSVCFG.COM \IBMCOM\PROTOCOL\LANVDD.OS2 ═══ 6.8.1. Fixed APARs ═══ o JR06756 - DIR.INTERUPT RETURNS 0 IF ADAPTER NOT OPEN (LANVDD.OS2) Attempting to run an Ethernet packet driver for TCP/IP. It failed when it attempted to initialize, because the executable ran a dir.interrupt command to see if the adapter was open. VDD returned a return code = 0 if the adapter was not open. It should have returned a bad return code. o IC06434 - Attempting To Load PCSUPPORT Router In a VDM Causes Trap D Attempting to load PC-Support (connection for AS/400) in a VDM caused a trap D in the LANVDD.OS2 module. The fix was to restore an index register after returning from a procedure call. o IC06017 - Attachmate Extra For Windows 3270 Causes LANVDD Trap D Stopping a 3270 Attachmate session and starting a new session caused a trap D in the LANVDD.OS2 module. The fix zeroes out various structures on exit. ═══ 6.8.2. Other Fixes ═══ o THE DOS 8209 BRIDGE UTILITY CAN NOT FIND ADAPTER WITH VDD The DOS version of the 8209 Bridge Utility could not find the adapter when running under the VDD. o LTSVCFG ALWAYS RETURNS NONZERO When LTSVCFG was run, an error code environment variable was always set to nonzero. Even though LTSVCFG executed successfully, a nonzero return code was always returned. o NETBIOS and 802.2 SUPPORTS ONLY 8 DOS SESSIONS DOS Virtual Device Support for Netbios and 802.2 should support 16 sessions, not just eight. ═══ 6.9. Protocol Manager Defects ═══ Files that changed: \IBMCOM\PROTMAN.OS2 ═══ 6.9.1. Fixed APARs ═══ There are no fixed APARs for Protocol Manager. ═══ 6.9.2. Other Fixes ═══ o PERFORMANCE AND NDIS SUPPORT IN PROTMAN PROTMAN supports the GET_PPATINFO IOCTL for the NDIS requirements and the GET_MODULE_CHAR_ TABLE IOCTL for the Monitor product. ═══ 6.10. IBM Netware Requester Support Defects ═══ Files that changed: IBMCOM\PROTOCOL\ODI2NDI.OS2 IBMCOM\NWFIXUP.EXE IBMCOM\LT8.MSG IBMCOM\LT8H.MSG ═══ 6.10.1. Fixed APARs ═══ o IC05437 - LOTUS NOTES RUNNING ODI2NDI OVER ETHERNET LOST SESSION While running Lotus Notes over ODI2NDI Ethernet, the session between the server and client was eventually lost. o IC05577 - NWFIXUP Utility Failed To Order Device Driver Statements Properly System configured with ODINSUP. NTS/2 was installed with ODI2NDI device driver and the NWFIXUP utility was executed. During IPL, a LT80221 error occurred. NWFIXUP failed to properly move PROTMAN.OS2 and LANMSGDD.OS2 within the config.sys. o IC06212 - Trap D in ODI2NDI.OS2 Device Driver A Trap D occurred in ODI2NDI.OS2 device driver. This problem was introduced in NTS/2 CSD WR07020. ═══ 6.10.2. Other Fixes ═══ o ODI2NDI FAILS WHEN TCP/IP USES DIRECT STATION OF IEEE 802.2 A NetWare Requester for OS/2 over ODI2NDI stops working when an application using the direct station interface of IEEE 802.2 is started. ═══ 7. LAN CID Utility Changes - On Diskette 2 ═══ Fixes to the Utilities are found on Diskette 2 of the ServicePak. There is no installation tool for these, they are simple file replacements. ═══ 7.1. LAN CID Utility (LCU) Defects ═══ Files that changed: LCU\CASAGENT.DLL LCU\CASAGENT.EXE LCU\CASPREP.CMD LCU\CAS.MSG LCU\CASH.MSG ═══ 7.1.1. Fixed APARs ═══ o IC05437 - CASPREP Does Not Remove All Comments From Output File CASPREP did not remove comments from all of the lines found in an input file when creating the output file. The comment was appended to the input file data on that line. A line was changed to increase the line count of the file being read and remove the comment. o IC05671 - LCU Logs Erroneous error When Setboot Is Executed A LCU message was added to say 'SETBOOT returned to the REXX program.' o IC05761 - LCU Command File Message Causes Confusion The message 'the command file %1 was not found' was displayed when casagent couldn't find the client specific command file. If the /d parameter was specified, then casagent will run the default command file and a LCU message was added to indicated this. o IC07130 - LCU Logging Stopped at EOF Marker LCU logging routine did not check to see if the last byte in the log file was a 0x1a. When the file pointer was moved to the end of the file and written to, the text after the EOF marker was not viewable with a text editor. LCU now checks for the EOF marker and if present, it will overwrite it with the new log text. ═══ 7.1.2. Other Fixes ═══ o New Return Codes Added To LCU In order to be compatible with NVDM/2, the following return codes were added: o 00 04 Successful Program Termination -Warning Messages Logged - No Reboot o 00 08 Successful Program Termination -Error Messages Logged - No Reboot o 00 12 Successful Program Termination -Severe Error Messages Logged - No Reboot ═══ 7.2. SRVIFS Defects ═══ Files that changed: SRVIFS\IFSDEL.EXE SRVIFS\THINIFS.EXE SRVIFS\THINSRV.EXE SRVIFS\SERVICE.EXE SRVIFS\SRVATTCH.EXE ═══ 7.2.1. Fixed APARs ═══ o IC04918 - Removal Of IFSDEL Target Directory IFSDEL was changed to remove all SRVIFS files from the target directory (except XI1.MSG on OS/2 2.0 due to OS/2 2.0 problem), attempt to remove the target directory if empty, and update the path/dpath statements in the config.sys if the path was removed. o IC04965 - CID SRVATTCH Fails With Return Code = 250 SRVATTCH received error XI10066: Attach failed with rc=250 during bootup on a HPFS machine. SRVATTACH was attempting to execute prior to netbind.exe finishing. o IC05559 - Line Number Not Present In Error Message For SERVICE.EXE An error within the service ini file caused an error message without the line number. Error message now provides the line number where the error occurred. o IC05819 - Trap D in SERVICE.EXE Trap D occurred while executing SERVICE.EXE. ═══ 7.2.2. Other Fixes ═══ o Trap D in IFSDEL.EXE Trap D occurred while executing IFSDEL.EXE. ═══ ═══ The item in the title line is a trademark of IBM Corporation ═══ ═══ The item in the title line is a trademark of Microsoft Corporation ═══ ═══ The item in the title line is a trademark of Wall Data Corporation ═══ ═══ The item in the title line is a trademark of Attachmate Corporation ═══ ═══ Flat files ready for use; needing no additional processing such as Unpacking or Expanding from a Metafile format. For example: LAPS.EXE IBMTOK.NIF IBMTOK.OS2 ═══ ═══ Files compressed into a Metafile that must be preprocessed by PKUNZIP2.EXE before use. Generally these files have a File Name Extension of ZIP.