home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
i06200b1.dsk
/
IP06200.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1996-03-08
|
39KB
|
1,008 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
OS/2 LAN Server for Macintosh Version 1.0 ServicePak IP06200
IBM PTF IP06200
The versions of LS-Mac that can be serviced with this ServicePak are
LAN Server For Macintosh V1.0 - IP06000
This ServicePak includes all previously available LSM corrective service
(LSMMOD9), plus fixes for two new APARs.
There is one change in this service level which can not be fully implemented by
the SERVICE tool and must be completed manually after the ServicePak is
applied. It can be performed before the first reboot or at a later time. This
step involves editing the CONFIG.SYS file on the server as described in the
Post Installation section of this document.
Another visible change in the product is the addition of the "LSM
Administrator's Guide" in online form. Other changes, as a result of applying
this ServicePak, are documented in the updated "Administrator's Guide." You
can access and view the book by following the instructions in the
Documentation Changes section.
Warning: 1 - Archiving is not enabled for this ServicePak. Before installing
this ServicePak, ARCHOFF.EXE (located on the Service Tool diskette) must be
executed to rename any ARCHIVE logs that have been created by previously
installed LS 4.0 FixPaks. This ServicePak WILL NOT install properly if
ARCHOFF.EXE is not run prior to starting SERVICE. With the Service Tool
diskette in the A drive, type A:ARCHOFF at an OS/2 command prompt to execute
this pre-install program.
Warning: 2 - This ServicePak has a new method of installation using Corrective
Service Facility (CSF) Version 2-B. Although the installation instructions
look similar to previous ServicePaks, there are significant differences.
Please review the entire Installation section before proceeding. Service to
Servers which use "Advanced Features" can be complex.
Good Insurance!
Have appropriate Bootable Standalone Service Diskettes.
ΓòÉΓòÉΓòÉ 1.1. Affected SYSLEVEL Files ΓòÉΓòÉΓòÉ
After installing this ServicePak, the CURRENT CSD level of the following
SYSLEVEL file(s) will indicate IPx6200 (where x indicates the country code.)
SYSLEVEL.LSM IBM OS/2 LAN Server for Macintosh Product
ΓòÉΓòÉΓòÉ 1.2. Trademarks ΓòÉΓòÉΓòÉ
The following are trademarks of IBM Corporation:
o IBM
o LAN Server
o LAN Streamer
o Operating System/2
o OS/2
The following are trademarks of other Corporations:
o Adobe (Adobe Systems Incorporated)
o Excel (Microsoft Corporation)
o Microsoft (Microsoft Corporation)
o Netware (Novell Incorporated)
o Pagemaker (Aldus Corporation)
o PostScript (Adobe Systems Incorporated)
o QuarkXpress (Quark Incorporated)
o Stuffit (Aladdin Systems Incorporated)
o Tiff (Aldus Corporation)
o WordPerfect (WordPerfect Corporation)
ΓòÉΓòÉΓòÉ 2. Installation ΓòÉΓòÉΓòÉ
This ServicePak uses Corrective Service Facility (CSF) Version 2-B (provided on
the tool diskette of this ServicePak) for installation.
Complete instructions for the use of the updated SERVICE and FSERVICE commands
are provided with the CSF Version 2-B README.INF file on the Service Tool
Diskette. Please read the CSF instructions for information on the use of CSF
Version 2-B backup and restore capabilities.
Note: - Archiving is NOT enabled for this ServicePak.
Installing the ServicePak is essentially a three phase process:
Phase 1 - Stop applications on the Target System
Stop all running applications so that LAN Server/Requester is not
in use. (This includes doing a 'net stop server').
Phase 2 - Install the ServicePak
Use one of the following methods to replace system files with those
provided on this ServicePak:
Selective Install
Redirected (CID) Install
Phase 3 - Return the Serviced System to Normal Operation
Perform a normal system boot.
ΓòÉΓòÉΓòÉ 2.1. Selective Install ΓòÉΓòÉΓòÉ
This method will apply fixes to selected subsystems, partitions, and
directories: The Corrective Service Facility will handle Locked Files
automatically so boot diskettes are not required before applying service.
1. At an OS/2 command prompt, perform a 'net stop server'.
2. Insert Service Tool diskette in the A drive.
3. At an OS/2 command prompt, type "A:ARCHOFF" to execute this pre-install
program (if you haven't already done so).
4. At an OS/2 command prompt, type "A:SERVICE" and press Enter.
5. Insert ServicePak diskette 1 when prompted.
6. Follow the prompts to the CSF SERVICEABLE PRODUCTS panel. Review the
serviceable products selected on the panel and deselect any products that
you do not want to service at this time. Then choose the SERVICE push
button.
7. Enter (optional) backup path then choose the OK push button.
8. If the APPLICATION IN USE locked files panel is presented, choose CONTINUE.
9. Follow prompts to complete the process.
10. Remove the diskette from drive A:
11. Insert ServicePak diskette 1.
12. At an OS/2 command prompt, type "A:LSMLKLST" to execute this post-install
program.
13. Remove the diskette from drive A:, then perform the system Shutdown
procedure.
14. Reboot the system normally.
If the system to be serviced is a multiboot system with LAN Advanced Server
using IBM386FS on a drive other than the "C" drive, use the Special Situation
Install method to complete the installation on each bootdrive.
When problems such as insufficient disk space are encountered when performing
the Selective Install, use the Special Situation Install method to perform
service.
ΓòÉΓòÉΓòÉ 2.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 MPTS. The Selective
Install method is recommended for Servers exploiting 386 HPFS function, Fault
Tolerance, and/or Local Security.
CAUTION:
Before using FSERVICE to apply corrective service, review the sample response
file (RESPONSE.FIL) located on the Service Tool diskette. Edit the
RESPONSE.FIL, if necessary, to ensure the service logfile is created in the
correct location on the target workstation.
:LOGFILE d:\os2\install\service.log
where d:\os2\install is the drive and location for the service logfile.
While setting up a CID server is beyond the scope of this document, we have
provided a sample LAN CID Utility REXX Command file segment (IP_6200.CID) that
may prove useful in setting up a CID server for this ServicePak.
The sample IP_6200.CID assumes the following:
o The Service Tool diskette files are placed on the code server using "XCOPY
A:\*.* /S" (or equivalent) in 'x:\img\csd\lsm\ip_6200' where 'x:' is the
drive seen by the client.
o The ServicePak files are placed on the code server using "XCOPY A:\*.* /S"
(or equivalent) in 'x:\img\csd\lsm\ip_6200.'
o The sample RESPONSE.FIL (or equivalent) is placed on the code server in
x:\rsp\csd\lsm\ip_6200.
o The following CID server directory structure contains the contents of the
ServicePak and the Service Tool diskette.
img\csd\lsm\ip_6200 * Root directory of ServicePak diskette 1
img\csd\lsm\ip_6200 * Service Tool diskette files
img\csd\lsm\ip_6200\FIX * No files
img\csd\lsm\ip_6200\FIX\LSM.1 * LAN Server for Macintosh fixes
rsp\csd\lsm\ip_6200 * RESPONSE.FIL (from sample on Service
tool diskette)
o A log directory exists at 'x:\log\csd\lsm\ip_6200' for the log files.
ΓòÉΓòÉΓòÉ 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 and Diskette 1 of OS/2 2.x or OS/2 3.x. Escape to A:
o Create custom Bootable Standalone Service Diskettes from your licensed
materials. The makeup of these is dependent on the system to be serviced.
Instruction is available for:
Requesters and Entry Version Servers.
Advanced Version Servers.
CAUTION:
LAN Servers that utilize the Advanced features such as Local Security and Fault
Tolerance must use custom Bootable Standalone Service Diskettes. Regular HPFS
boot diskettes, such as the OS/2 Installation diskettes, CANNOT mirror changes
to Fault Tolerance partitions or access files/directories which are controlled
by local security.
ΓòÉΓòÉΓòÉ 2.3.1. Making OS/2 Bootable Diskettes ΓòÉΓòÉΓòÉ
Instructions for creating OS/2 bootable diskettes for Requesters and Entry
Version Servers are dependent on the OS/2 version.
o For OS/2 2.x versions:
1. Make a copy of the OS/2 2.x Installation Diskette and Diskette 1. Call
them SA1 and SA2 respectively.
2. Delete SYSINST2.EXE from Diskette SA2.
3. Delete BUNDLE from Diskette SA2 (this will be on OS/2 versions 2.1 or
greater).
4. Modify CONFIG.SYS on SA2 as follows:
buffers=50
memman=noswap
protshell=a:\cmd.exe
protectonly=yes
libpath=a:\;
ifs=hpfs.ifs /c:64
set path=a:\;
set dpath=a:\;
5. Copy UHPFS.DLL from OS/2 Diskette 2 or C:\OS2\DLL to SA2.
o For OS/2 3.x versions:
Use the Install diskette and Diskette 1 of OS/2 3.x. Escape to A:
ΓòÉΓòÉΓòÉ 2.3.2. Making Advanced Server Bootable Diskettes ΓòÉΓòÉΓòÉ
MAKEDISK is an Advanced Server utility designed to make the necessary Bootable
Standalone Service Diskettes used in periodic maintenance of 386 HPFS systems.
1. Make a copy of the OS/2 2.x or 3.x Installation Diskette and Diskette 1.
Call them SA1 and SA2 respectively.
2. Delete SYSINST2.EXE from Diskette SA2.
3. Delete BUNDLE from Diskette SA2 (this will be on OS/2 versions 2.1 or
greater).
4. With Boot Diskette SA2 in drive a: or b: run MAKEDISK from an OS/2 prompt.
Note: Syntax is MAKEDISK /BOOTDRIVE:d where d is the OS/2 boot drive.
For additional Information see the Network Administrators Reference:
Creating a 386 HPFS Boot Diskette, or LAN Server Utilities.
5. If using Fault Tolerance, add the Fault Tolerance files to the Bootable
Diskette SA2.
6. Ensure the country code, codepage, and the keyboard information in the
config.sys file on the boot diskette matches the corresponding information
on the target workstation's config.sys. Verify that the 386 HPFS Bootable
Standalone Service Diskettes work properly and that, after rebooting, Local
Security and Fault Tolerance are working as expected.
ΓòÉΓòÉΓòÉ 2.3.3. Adding Fault Tolerance to 386 HPFS Bootable Standalone Service Diskettes ΓòÉΓòÉΓòÉ
386 HPFS Bootable Standalone Service diskettes require additional customizing
in order to properly update files on partitions which are mirrored.
The following steps may have to be done for each LAN Server with Fault
Tolerance since the configuration information transferred in step 3 can be
unique for each such system.
1. Copy the following four Fault Tolerance files from the first diskette of
the LAN Server 4.0 ServicePak to your Bootable Standalone Service Diskette
SA2.
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 SA2.
DEVICE=DISKFT.SYS
3. At an OS/2 command prompt, make the current drive A:, and have the 386 HPFS
Bootable Standalone Service Diskette SA2 in drive A. Type "FTCOPY" to copy
the customized Fault Tolerance configuration information to the 386 HPFS
Bootable Standalone Service Diskette SA2.
Warning: Ensure the country code, codepage, and the keyboard information in
the config.sys file on the boot diskette matches the corresponding information
on the target workstation's config.sys. Test your 386 HPFS Bootable Standalone
Service Diskettes 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.
ΓòÉΓòÉΓòÉ 2.4. Special Situation Install ΓòÉΓòÉΓòÉ
This method will apply all fixes to all partitions and directories:
FSERVICE is used for CID installation of this ServicePak, for multiboot systems
with IBM386FS on a drive other than the 'C' drive, or when problems, such as
insufficient memory for the locked file device driver or corrupted disk drives,
are encountered using the Selective Install method. It does require booting
from diskette to insure that there are no Locked Files during the install
phase.
Warning: - Ensure that all drives to be updated are clean by performing a
CHKDSK /F on each drive before FSERVICE is invoked. There will be no
opportunity to clean up the drives after FSERVICE is invoked.
1. Review the FSERVICE Response File (RESPONSE.FIL on the Service Tool
diskette) and modify as needed to reflect the configuration of the system
to be serviced. Ensure the service logfile is created in the correct
location on the target workstation.
:Logfile d:\os2\install\service.log
where d:\os2\install is the drive and location for the service logfile.
2. Boot from the Bootable Standalone Service Diskettes.
3. Establish A: as the Current Directory.
4. Replace the Boot Diskette with the Service Tool Diskette.
5. At an OS/2 command prompt, type "A:ARCHOFF" to execute this pre-install
program (if you haven't already done so).
6. From the A: prompt, type "FSERVICE" and press Enter. Click here for
additional steps needed for multi-boot systems.
7. At the panel titled "Installing this Service Pak" press Enter (Option 1).
8. Follow the prompts provided by the Corrective Service Facility.
9. Remove the diskette from drive A:
10. Insert ServicePak diskette 1.
11. From the A: prompt, type "LSMLKLST" and press enter to execute this
post-install program.
12. Remove the diskette from drive A:
13. Reboot the system normally.
ΓòÉΓòÉΓòÉ 2.4.1. Updating IBM386FS Directory on a Multiboot System ΓòÉΓòÉΓòÉ
A new parameter has been added to the FSERVICE command to enable servicing the
IBM386FS directory when it resides on a bootdrive other than C:. Specify the
bootdrive containing the IBM386FS directory to be serviced as the /b parameter
on the FSERVICE command:
FSERVICE /b:d
(where d is the drive letter assigned to bootdrive)
Note: There is NO colon after the bootdrive 'd'.
Two methods are available for servicing the IBM386FS directories on multiple
bootable drives:
1. Run FSERVICE iteratively. That is, run FSERVICE /b: for each bootable drive
containing an IBM386FS directory.
2. Edit the RESPONSE.FIL (on the Tool diskette of this ServicePak) to add the
following parameter set after the :SYSLEVEL label:
:DIRLIST
d1:\IBM386FS where d1 = a bootable drive requiring IBM386FS service,
d2:\IBM386FS and d2 = another bootable drive requiring IBM386FS service.
:ENDDIRLIST
ΓòÉΓòÉΓòÉ <hidden> Locked Files ΓòÉΓòÉΓòÉ
Sometimes it is essential that programs own (become the master of) system
resources such as Memory Blocks, Communication Ports, and Files. When a program
stakes claim to a file, that file is said to be Locked; no other program is
allowed to alter (replace or write to) it until the owning program explicitly
removes the lock.
.DLL Files can become Locked by residing in a directory that is included in
the LIBPATH string of CONFIG.SYS.
For example, NETAPI.DLL can be locked when \MUGLIB\DLL exists in the LIBPATH of
CONFIG.SYS.
ΓòÉΓòÉΓòÉ <hidden> Escape to A: from OS/2 Install Diskettes ΓòÉΓòÉΓòÉ
To obtain the A: prompt when using the OS/2 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. (F3 for OS/2 3.x)
The A: prompt should appear. OS/2 Programs, including FSERVICE.EXE, can be run
from here.
ΓòÉΓòÉΓòÉ <hidden> Creating a 386 HPFS Boot Diskette Refer to ΓòÉΓòÉΓòÉ
Appendix H in:
Operating System/2 Local Area Network Server
Network Administrator Reference Volume 1: Planning and
Installation
Version 4.0
ΓòÉΓòÉΓòÉ <hidden> LAN Server Utilities ΓòÉΓòÉΓòÉ
Refer to Appendix B, Miscellaneous Utilities MAKEDISK in:
Operating System/2 Local Area Network Server
Network Administrator Reference Volume 3: Network Administrator
Tasks
Version 4.0
ΓòÉΓòÉΓòÉ 3. Post Installation Action Required ΓòÉΓòÉΓòÉ
This section contains important installation procedures that need to be done
after you apply the LSM ServicePak.
ΓòÉΓòÉΓòÉ 3.1. Editing CONFIG.SYS ΓòÉΓòÉΓòÉ
This service level of LSM introduces a file, ATALK.NIF, which allows the
AppleTalk protocol stack to be configured using LAN Adapter and Protocol
Support (LAPS or MPTS). This NIF file must reside in the \IBMCOM\PROTOCOL
subdirectory and will be placed there during ServicePak installation. The
device driver ATALK.SYS must also reside in the same subdirectory, but was
previously placed in \IBMLAN\NETPROG. After application of this ServicePak,
ATALK.SYS will exist in both places.
Your current CONFIG.SYS referencing \IBMLAN\NETPROG will continue to work until
the first time LAPS or MPTS is executed on the system. After that time the
line invoking ATALK.SYS from its new location will be present in CONFIG.SYS.
Your system startup may pause displaying an error message indicating a problem
with ATALK.SYS or PROTOCOL.INI. In order to avoid this situation, you should
edit your CONFIG.SYS after applying this ServicePak. Using a text editor of
your choice, edit CONFIG.SYS using the following steps:
1. Start the editor and open the CONFIG.SYS file which is on the OS/2 boot
drive.
2. Determine on which drive IBMCOM is installed by finding the line which
reads "DEVICE=y:\IBMCOM\PROTOCOL\NETBIOS.OS2", where y can be any letter.
3. Find the line which reads "DEVICE=x:\IBMLAN\NETPROG\ATALK.SYS", where x can
be any letter.
4. Change the line to read "DEVICE=y:\IBMCOM\PROTOCOL\ATALK.SYS"
5. Save CONFIG.SYS
6. Check the y:\IBMCOM\PROTOCOL subdirectory to ensure ATALK.SYS and ATALK.NIF
are present.
If you have not rebooted the system since applying this ServicePak, do so now.
Otherwise it is not necessary to reboot now, although you may to ensure that
the CONFIG.SYS change is correct.
ΓòÉΓòÉΓòÉ 3.2. Initializing Extended Attributes ΓòÉΓòÉΓòÉ
The fix for APAR IC09775 is implemented by adding OS/2 extended attributes to
all files and directories used by Macintosh clients. Background and normal-use
information for this enhancement can be found in the revised LSM
"Administrator's Guide" described in Documentation Changes and Online
Documentation. This section provides additional information for those who are
upgrading an existing system.
An existing LSM 1.0 system has the Macintosh-specific information stored in the
FLDIRDB.DAT file. After installing this ServicePak, the LSMFILE program writes
extended attributes whenever updating the FLDIRDB.DAT file, and therefore, the
information exists in two places. The LSMFILE program also reads these
extended attributes when adding new files to its database. This design allows
files to be moved or restored from backup under OS/2 without losing the
Macintosh information.
Files already on your server do not have the extended attributes yet and are
not protected by them. The LSMBACK utility has been modified to correct for
this now and as may be needed in the future. LSMBACK reads the database copy
it makes, and writes LSM extended attributes for any file or directory which
does not have them. To get full protection from the extended attribute
processing in LSMFILE, you should run LSMBACK soon after applying this
ServicePak.
ΓòÉΓòÉΓòÉ 3.3. Estimating the Extra Disk Space Needed for LSMBACK ΓòÉΓòÉΓòÉ
While LSMBACK is running, it temporarily requires four times as much disk
space. If your free disk space has been marginal in the past, you may need to
address the problem before running LSMBACK.
LSMBACK copies the index files along with the data files, then rebuilds the new
index files just as LSMFIX does for the main files. In doing so, LSMBACK has a
complete copy of the database for the duration, and a second copy of each .DAT
and .IDX pair for a brief time. You can estimate how much free space you need
by adding the sizes of all the .DAT and .IDX files, plus two times the largest
file (usually the FLDIRDB.DAT file).
ΓòÉΓòÉΓòÉ 4. Documentation Changes and Online Documentation ΓòÉΓòÉΓòÉ
The documentation changes for this ServicePak are all present in the updated
"Administrator's Guide." To see these changes, view the new online book, then
be guided by the summary of changes that follows.
ΓòÉΓòÉΓòÉ 4.1. Accessing the Online Documentation ΓòÉΓòÉΓòÉ
One of the changes in the LSM product is the addition of the "Administrator's
Guide" in online form. To read this file, enter the following command
VIEW x:\IBMLAN\NETPROG\A3A72MST.INF
where x is the drive on which LAN Server
and LSM are installed.
You may also want to create a desktop object for this file to accompany the one
already in place for the LSM Administration utility.
1. Open the Templates folder on the desktop.
2. Drag a copy of the Program template and drop it on the LAN Services program
group icon. (This group container was created when LSM was installed. If it
does not exist because you moved the icon for the LSM Administration
utility, substitute any container you choose.)
3. In the Program - Settings Path and file name input box, key in "VIEW.EXE".
4. Using the Tab key or the mouse, move the cursor to the Parameters input
box.
5. Key in "x:\IBMLAN\NETPROG\A3A72MST.INF", substituting the correct drive
letter for x.
6. Click on the "General" tab with the mouse.
7. Use the Delete key to remove the Title of "Program".
8. Key in "LAN Server for Macintosh" and press Enter.
9. Key in "Administrator's Guide".
10. Close the settings window.
ΓòÉΓòÉΓòÉ 4.2. Viewing the Changed Documentation ΓòÉΓòÉΓòÉ
The following list is a guide to the changed documentation. For each topic the
chapter and section containing the information is identified.
o LAN Server Service Level Considerations for use with LSM.
Getting Started (Chapter 2)
System Requirements
LAN Server Service Level Considerations
o LSM restrictions with LAN Server 4.0 long names for user IDs and passwords.
Getting Started (Chapter 2)
System Requirements
Compatibility with LAN Server 4.0 and Later
o Changing LSM parameters in IBMLAN.INI and PROTOCOL.INI, including the use of
LAPS instead of an editor to change PROTOCOL.INI.
Installation (Chapter 3)
Reconfiguring LSM
o Home Directory support.
Files, Folders, and Privileges (Chapter 4)
Using Shared Directories
Home Directories
o Clarification on the use of encrypted passwords.
The Administration Utility (Chapter 6)
Configuration Management Functions
Changing Encrypted Passwords
o Changes in LSM operation and utilities due to the use of OS/2 extended
attributes to keep Macintosh specific information.
LSM System File Maintenance (Chapter 8)
o New configuration parameters and expanded explanation of old parameters for
the file server.
Configuration Parameters (Appendix A)
IBMLAN.INI Parameters
o New configuration parameters and expanded explanation of old parameters for
the AppleTalk protocol stack.
Configuration Parameters (Appendix A)
PROTOCOL.INI Parameters
Note: This information is the same as the context sensitive help when
running LAPS or MPTS configuration.
o Additional file creator and type information (the 13 new entries as
identified in the table which follows).
File Creator Reference (Appendix C)
Table1. Addendum to File Creator Reference
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé APPLICATION Γöé TYPE Γöé CREATOR Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Aldus FreeHand Γöé EPSF Γöé FHA2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Aldus PageMaker 5.0-data Γöé ALB5 Γöé ALD5 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Microsoft Excel-addin macrosheet Γöé XLS Γöé XCEL Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Microsoft Excel-chart Γöé XLC Γöé XCEL Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Microsoft Excel-macrosheet Γöé XLM Γöé XCEL Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Microsoft Excel-spreadsheet Γöé XLS Γöé XCEL Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Microsoft Excel-template Γöé XLT Γöé XCEL Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Microsoft Excel 4.0 Γöé XLS4 Γöé XCEL Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé QuarkXpress 3.1 Γöé XDOC Γöé XPR3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Stuffit Self Extracting Archive Γöé APPL Γöé aust Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TIFF files Γöé TIFF Γöé Anon Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TeachText-picture Γöé PICT Γöé ttxt Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé WordPerfect 3.0 Γöé WPD3 Γöé WPC2 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
o Documentation for CID installation.
CID Installation (Appendix G)
o Reference information for LSM extended attribute values
LSM Extended Attributes (Appendix H)
ΓòÉΓòÉΓòÉ 5. Reinstalling LAPS or MPTS without first removing LSM ΓòÉΓòÉΓòÉ
LSM requires OS/2 LAN Server for installation and operation. This requirement
implies that LAPS or MPTS must be installed and running before LSM. In the
past it was possible to remove and reinstall LAPS or MPTS without disturbing
LSM files.
With the introduction of the ATALK.NIF file and the relocation of the ATALK.SYS
file under \IBMCOM\PROTOCOL, removing the \IBMCOM directory tree now presents a
problem. If you find you need to remove LAPS or MPTS, you must first copy the
ATALK.SYS and ATALK.NIF files to a safe place not under IBMCOM (\IBMLAN\NETPROG
would be good since ATALK.SYS is already there as well). After reinstalling
LAPS or MPTS, copy the two ATALK files back under \IBMCOM\PROTOCOL. Then use
LAPS or MPTS configuration to restore the IBM AppleTalk instance required by
LSM.
ΓòÉΓòÉΓòÉ 6. APARS and other fixes ΓòÉΓòÉΓòÉ
This section describes the APARs (ICxxxxx) and other defects (d xxxxx) fixed by
this ServicePak.
ΓòÉΓòÉΓòÉ 6.1. Fixes new in IPx6200 ΓòÉΓòÉΓòÉ
IC09775 Macintosh Finder information is lost when files are moved under OS/2.
Extended attributes will now be stored with each file so LSM can
restore the information in the datbase.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
\IBMLAN\NETPROG\LSMBACK.EXE
\IBMLAN\NETPROG\LSM.MSG
\IBMLAN\NETPROG\LSMH.MSG
IC11978 Mac user can delete files without D permission. When a Macintosh
user drags a file to the trash, the operation performed is actually a
move. LSMFILE was allowing this without checking for Delete
permission.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
d 27140 LSMFILE gets SYS3175 error on some rename operations. This happened
when a Mac user renamed a file or folder, but the name as stored on
OS/2 didn't change.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
ΓòÉΓòÉΓòÉ 6.2. Fixes from previous levels. ΓòÉΓòÉΓòÉ
IC06015 Applications on LSM server aren't found by Macintosh Finder. LSM
application data base entries with duplicate names but different
paths were being deleted.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC08223 Message LSM0229 appears for every extra file name in database.
Files affected: \IBMLAN\NETPROG\LSMFIX.EXE
IC08271 Trap 000d in ATALK$ under some error and retry conditions. Under some
conditions frame buffers were incorrectly being freed and then later
referenced to retry the operation.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC08564 Intermittent login failures through NetWay routers on Token-Ring with
bridges. LSM was replying to an All Routes Broadcast frame with a
routed frame which incorrectly had the type set to broadcast.
Bridges did not forward these frames.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC08631 Trap 000d in IBMTOK$ caused by ATALK error recovery problems. Under
some conditions frame buffers were incorrectly being freed and then
later referenced to retry the operation.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC08645 Changing password from a Macintosh is unreliable when LSM is on an
additional server. Under some conditions LSM attempts a domain logon
in order to change a password. At times the Macintosh user ID would
be left logged on at the server.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC08725 Drop folder file access rights problem with LSM and HPFS386. When LSM
moves a file on behalf of a Macintosh, HPFS386 creates an access
profile for the file. Macintosh users can not see or manipulate file
profiles so LSM will now delete them.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC08764 LSMFIX with LS 4.0 requires diskette in drive A: LSMFIX has been
changed to suppress hard error popups when scanning drives. Diskette
and CDROM drives no longer need media in the drive.
Files affected: \IBMLAN\NETPROG\LSMFIX.EXE
IC08815 Trap 000d in ATALK$ with new LanStreamer card and driver. Under some
conditions frame buffers were incorrectly being freed and then later
referenced to retry the operation.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC09282 Adobe Illustrator save replace fails to LSM server. LSM does not
support the AFP exchange files command, but had set the flag
indicating it does. The command is still not supported but the flag
state has been corrected.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC09313 Macintosh users get the wrong message when password expired.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC09317 LSM requires a shared CD-ROM drive to have a CD inserted. LSMFILE has
been changed to suppress hard error popups when scanning drives.
Diskette and CDROM drives no longer need media in the drive.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC09337 Macintosh Publish/Subscribe fail when files are on LSM server. This
is another symptom of the unsupported AFP exchange file command. See
APAR IC09282 description.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC09774 LSM does not associate fork files when created on OS/2. LSM provides
file extension mapping to set Macintosh creator and type, but
provided no way to associate data and resource fork. A properly named
file with a suffix of .#Res on HPFS will now be associated as a
resource fork.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC09865 LSM allows resource fork files to show on the Macintosh. There were
erroneous file entries when the file name was longer than 26
characters.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
d 12562 Print jobs from Macintoshes show the wrong user ID. A print job
sitting in the OS/2 print queue will now show the Macintosh Owner as
the user ID. Previously this was empty or the ID of a user logged at
the server.
Files affected: \IBMLAN\SERVICES\LSMPIN.EXE
IC04538 LSM sets file date and time to system clock instead of using values
supplied by the Macintosh.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC05135 LSM doesn't work with a Locally Administered Address (LAA) on
Token-Ring. The AppleTalk protocol includes the hardware LAN address
as data in an AARP packet. The Universally Administered Address (UAA)
was always being put there.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC05154 Trap 000D in LSMFILE for long list of volume (share) names. This can
happen when more than 22 shares are defined on the LAN Server. When
the aggregate length of the LAN Server share descriptions is greater
than about 600 bytes, multiple frames are required to send the
information to the Macintosh.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC05327 LSM file server performance is inadequate for complex folder
operations and deteriorates rapidly as more users log in and open
shared volumes. Additional Lan Server fixes will be required as well.
Lan Server 3.0 servers will require either IP07040 or 7045.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
\IBMLAN\SERVICES\LSMFILE.EXE
IC05415 LSM doesn't always work with the IBM Token-Ring Busmaster Server
Adapter /A. Net Start command will never complete. Window will fill
up with dots until window is closed. Net Start command shows it is
started but cannot be stopped or started. Message LT40009 will
appear in the \IBMCOM\LANTRAN.LOG file.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC05455 PhoneNet PC user can't log in to LSM. PhoneNet PC can see LSM
machine in the Chooser, but receives an error message when attempting
to link. File requests have been sent out on a different socket,
other than the socket used to create the session. LSM has been
changed to send responses to the socket that originated the request.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC05586 LSM was setting the Token-Ring functional address to an incorrect
value when many routers were on network. After Starting LSM, Lan
Server would quit working. The Netbios protocol configured on the
server would stop functioning as would Lan Server itself. This has
also happened with a Madge Token-Ring card when no routers were
present.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC05639 Printing from a Macintosh to LSM only works the first time. This may
also be accompanied by message LSM0000 internal errors which will be
recorded in your net error log. Various network problems are
associated with these errors, including failed printing and the
LSMFILE not starting.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC05643 LSM fails with IBM LANStreamer Token-Ring card. The same problem
occurs with the EtherStreamer card. LSM machine is NET started. The
command will never complete. The window the command was issued in
will fill up with dots. Subsequent Net starts will show the system
thinks that LSMFILE has started, but cannot be started or stopped.
The Lantran.log will reveal no errors. This is similar to IC05415,
which will not resolv LANStreamer problems.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC05777 Message LSM0030 gives wrong solution under OS/2 2.1. The message
states to decrease MAXOPENFILES, whereas the value had to be
increased to get around the problem. In OS/2 2.1 with MMPM2
installed, documented MaxFileHandles is incorrect. LSMFILE was
changed to account for the actual behavior of OS/2.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC05846 LSM doesn't support Macintosh LaserWriter driver version 8.
Previously the Macintosh sent query jobs starting with
"%]PS-Adobe-2.0 Query". In LaserWriter driver version 8 Apple
changed it to "%]PS-Adobe-3.0 Query". LSM was changed to compensate
for this.
Files affected: \IBMLAN\SERVICES\LSMPIN.EXE
IC06100 Logon to LSM fails through Wellfleet and NetWare Routers on Ethernet.
These routers were incorrectly including Ethernet frame padding in
the data length for the AppleTalk Datagram Delivery Protocol (DDP).
LSM was changed to be consistent with other implementations and will
now ignore the extraneous data.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC06121 LSM servers appear in multiple zones in the Macintosh Chooser.
AppleTalk zones are assigned to functional addresses for efficient
broadcast handling. These addresses are not unique with respect to
zone names. LSM was responding to the functional address without
checking the zone name and so appeared in all zones with the same
address.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC06160 LSM servers disappear and get selected wrong in the Macintosh
Chooser. An error in LSM allowed two systems separated by a
Token-Ring bridge to come on the LAN with the same AppleTalk address.
The Macintosh would only show and select one at a time. This would
change from time to time depending on the relative timing of
broadcasts and responses on the network.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC06206 LSM files restored to a new disk are missing Macintosh unique
information (name, creator, type). When an OS/2 disk was replaced
with a new one having a different Volume Serial Number (VSN), LSM was
treating it as a new disk. LSMFIX and LSMFILE have been changed to
recognize this type of change and retain the original information.
Files affected: \IBMLAN\NETPROG\LSMFIX.EXE
\IBMLAN\SERVICES\LSMFILE.EXE
IC06240 LSM server crashes when Token-Ring disrupted. LSM was trying to free
memory during interrupt time, which is not allowed. The free
operation will now be deferred.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC06269 LSM to PhoneNet PC session drops when through a router. LSM was
sending Tickle packets as 'exactly once' transactions instead of 'at
least once'. After four minutes the session dropped because both
sides stopped sending Tickles.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
IC06349 IO error 8200 on Word Perfect Office with LSM. When WPO stores large
data items, it creates a new file and sets a pointer to it. When the
Macintosh WPO tried to use this pointer, LSM could not find the file
because it had never been encountered through the Finder and was not
in the LSM database.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
IC07011 Incomplete AppleTalk printer output from OS/2 or DOS applications.
PostScript printer output from a source other than a Macintosh was
generating error messages faster than LSM could read them in. This
caused LSM and the printer to end up waiting for each other. After
about ten minutes the printer would time out and close the session.
Files affected: \IBMLAN\SERVICES\LSMPOUT.EXE
IC06346 LSM stops taking logins when ATALK runs out of memory. Under heavy
cc:Mail traffic, LSMFILE was ceasing to function with no error
message. The actual problem was caused by memory leaks in ATALK.SYS
and out of resource errors from the Token-Ring driver.
Files affected: \IBMLAN\NETPROG\ATALK.SYS
\IBMLAN\SERVICES\LSMFILE.EXE
d 6346 LSM needs to hide $ shares for LAN Server 4.0. In LS 4.0 the NET
SHARE command was changed to show all shares, including those ending
in $, which were previously hidden. These shares should not be seen
by Macintosh users so the hiding function was put into LSM.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
d 6944 A Macintosh user can not change his password through LSM on an
Additional Server. The password change would work if an administrator
was logged on at the AS, but not otherwise. LSM was changed to log on
the server as the user to change the password, then log off again.
Files affected: \IBMLAN\SERVICES\LSMFILE.EXE
ΓòÉΓòÉΓòÉ 7. Appendix ΓòÉΓòÉΓòÉ
Appendix of other interesting topics.
ΓòÉΓòÉΓòÉ 7.1. Printing Information from this On-line Document ΓòÉΓòÉΓòÉ
The OS/2 view function provides a print capability to the printer defined as
the "default" printer for your system. From the "Services" popup, selecting
print provides several options; Print All, Marked, or This Section(s),
Contents, or Index.
All but the Print Marked Sections are fairly self explanatory. To Print
"Marked" sections one must first know how to "Mark". It is best to do this with
the contents window fully expanded, ie. every section shows up in the content
panel. Then simply press the space bar when the section you chose is
highlighted or point and click the left mouse button while also holding the
ctrl key to "mark" a section for print.
The highlighting for "marked sections" is slightly larger than normal
highlighting. To notice the difference, select an item in the contents and
repeatedly press the space bar.