3+0pen LAN Manager Version 1.0 Release Notes
3+0pen
LAN
Manager
Release
Notes
Contents
Hardware Requirements
Disk and RAM Requirements
Supported
Supported
Configuring an EtherLink
Before Installing 3+Open LAN Manager
Pre-Release
Compaq
Running Installation and
Upgrading from Entry
Building
Disabling the
Using
Running Installation and
Installation and
Checking
PC Servers Using OS/2 DOS Compatibility Mode
Creating Generic
Logging on With a
Performance Notes
OS/2 Disk Caching
OS/2 Filesystem Directory Caching
OS/2 Cache Program Requires LAN Manager Installation
3+ Compatibility Notes
3+MENUS Program
3F
& 3P
Token Ring Network Upgrade
3+Name Service
IBM Application Notes
IBM LAN Manager Program
IBM 3270 Emulation Program
IBM
PC Network Program 1.3
3Com
Software Developer Notes
Network Administration Notes
DOS
Programs Using High Memory
CONFIG.SYS Entry Format
Conflicts with Memory Mapped Devices
3ComIBM Token Ring Adapter
3Com EtherLink
3Com EtherLink II Adapter Configured with Memory Mapping
NetWkstaSetUid API Change
Named Pipes With Multiple Threads
User Shares Ending in $
Adapter/Protocol Configurations ............................................... 1
Server and Netstation Platforms
DOS 3.31 Disk Format Incompatible With OS/2 ............................... 3
360K DOS Boot Diskettes
DOS APPEND Command
NETSETUP to Modify a Remote Server
Setup Notes
for
LINK/DIR
Maximizer/386
TokenLink Adapter
..........................................................................
...................
Plus
or
TokenLink Plus Adapter Card
1.0
Software
Overlayed
DOS Netstation Diskettes
DOS Netstation Diskette
................................................................................
...........................................................................
...........................................................................
..............................................................................
Plus Adapter
.........................................................................
Setup Under DOS
System to Advanced System Software .......................... 3
........................................................
Setup in DOS Mode
.....................................................................
Drive
.........................................................................
.........................................................................
..............................................................
..........................................................................
................................................................
...............................................................
Notes
................................................................
...................................................................
....................................................................
..............................................................
.......................................................................
...............................................................
..................................................................
IDs .......................................................... 4
........................................................
.............................................................
...............................................................
.................................................•...........
.......................................................
..................
'.'
..........................................
...............................................
..................................................
...............................................
...................................................
..........................................
of
OS/2 ................................... 3
.......................................
...............................................
..............................................
........................
'.'
.................................................
Version
......................
..............................
.;
.........................
.......................
1.0
1
1
2
2
2
2
3
3
3
3
4
4
4
5
5
5
5
5
6
6
6
6
6
7
7
7
7
7
8
8
8
8
9
9
9
10
10
10
10
10
3+0pen
Part
10/7/88
LAN Manager Version 1.0
Number 4814-00
3+0pen LAN Manager Version 1.0 Release Notes
Logging
NET ADMIN Error Messages Missing
NET ADMIN Sharing
Remote NET ADMIN Adding Users
Remote
NET ADMIN User Count
NET AD MIN Error Count
DOS Netstations Auto Reconnection
General
IBM PS/2 Model 80 ESDI Controller Problem
OS/2 DOS Compatibility Mode
MS-DOS
DOS
of
Server Out
of
Resources Errors
...............................................
....................................................
of
COMM devices
.................................................
.......................................................
Admin
Function Disabled after Network Errors ................................. 10
...................................................................
...................................................................
.......................................................
Notes
......................................................................................
...........................................
.............................................................
Net
Popup Video Incompatibilities ..............................................
NET
Command Failure When Invalid Drives in Path ..............................
Universal Name Convention (UNC) Names Invalid with Printer
Floppy Drive Access Problems Under OS/2
Expanded Memory Not Supported
.........................................................
..............................................
......................
10
10
10
10
11
11
11
11
11
11
11
11
11
12
12
3+0pen
Part
LAN Manager Version 1.0
Number 4814-00
10/7/88
3+0pen
LAN
Manager Version 1.0 Release Notes 1
Hardware
Disk
and
The following table lists the disk and RAM requirements for installing 3+Open
Advanced
Supported
The
following table shows the adapter card/protocol combinations supported in this release.
Requirements
RAM
Requirements
System:
Machine
OS/2 Server
OS/2 N etstation
DOS Netstation
DOS Netstation with 3Com DlJS
Maximizer/386
Adapter/Protocol
DLC/NetBEUI
Adapter Cards
EtherLink
EtherLink Plus (3C505)
EtherLink Plus with LPO
EtherLink II (3C503)
EtherLink/MC (3C523)
TokenLink
TokenLink Plus (3C605)
TokenLink Plus with LPO
IBM
Token Ring
IBM
Token Ring 2
IBM
Token Ring
Configurations
Protocols
(3C501)
(3C603)
/A
OS/2
Server
'\f
--:;;r
--:;;r
"\
,
,
Disk Drive
8MB
2MB
360K
1.2MB
OS/2
Netstation Netstation
'\f
'\f
'\f
'\f
,
,
,
2.5MB
DOS
....;
'\f
'\f
....;
"\
"\
"\
LAN
RAM
4MB
640K
1MB
Manager
XNS
3+0pen
Part
10/7/88
LAN
Number 4814-00
Protocols
Adapter Cards
EtherLink
EtherLink Plus (3C505)
EtherLink Plus with LPO
EtherLink II (3C503)
EtherLink/MC (3C523)
TokenLink (3C603)
TokenLink Plus (3C605)
TokenLink Plus with LPO
IBM
IBM
IBM
Manager Version 1.0
(3C501)
Token Ring
Token Ring 2
Token Ring
/A
OS/2
Server
....;
'J
,
,
"oJ
'\f
'\f
OS/2
Netstation Netstation
'\f,
'\f
'J
'J
'J
'J
"oJ
'\f
'\f
'\f
,DOS
'\f
'\f
'\f
,
,
,
'J
'J
'\f
'\f
'\f
3+0pen LAN Manager Version
1.0
Release Notes 2
Supported
For information on supported PC and PS/2 server and net station platforms, refer to the 3 +Open
LAN
Manager Installation
Configuring
To
support the Link Plus Optimizer (LPO) onboard protocol processing, EtherLink Plus and
TokenLink Plus network cards require 256K
256K
of
128K and require the addition
nanosecond chips may be substituted). Memory upgrade kits are available through 3Com resellers
as 3Com product number 3C505-B-128K.
These cards must be inserted into a 16-bit
I/O base address, and DMA channel settings (especially
slot). The recommended settings are listed here:
Server
an
memory soldered on the board. Revisions shipped prior to October 1987 came with
and
Netstation
and
Setup Guide.
EtherLink
Setting Value
Interrupt 3
I/O base address 300
DMAchannel
Plus
of
Platforms
or
TokenLink
four (64K by 4) 18-pin, 150 nanosecond DRAM chips (120
5
Plus
Adapter
of
onboard memory. Currently, the cards come with
PC
bus slot. This may require changing the interrupt,
if
the card has previously been in an 8-bit
Card
or
Be sure to check that these settings do not interfere with other peripheral
may have installed in your machine.
Refer to the manual for your EtherLink Plus or TokenLink Plus for installation instructions and
additional information.
Before
Before you begin the installation process make backup copies
DISKCOPY utility), label each disk, and use the backups for the installation process. Writeprotect all
to itself during the installation process.).
Pre-Release
There have been a number
versions
vendors. Due to these software changes, it is highly recommended that you perform a complete
installation
drive.
Installing
of
the backup 3+Open installation disks except OS/2 Installation (this disk writes back
3+0pen
LAN
Manager
of
each
1.0
Software
of
changes and additions to this product from various SDK and Beta
of
3+0pen
of
LAN Manager from 3Com and OS/2 LAN Manager from Microsoft and other
the
3+0pen
LAN Manager 1.0, beginning with reformatting
memory cards that you
of
them (using the
of
the server hard disk
3+0pen
Part Number 4814-00
10/7/88
LAN
Manager Version 1.0
3+0pen
LAN
Manager Version 1.0 Release Notes 3
Compaq
The hard disk format created with the Compaq DOS 3.31 is not compatible with OS/2.
a disk formatted this way and you are installing
under
Running
The Installation and Setup program requires that the FILES= entry in CONFIG.SYS be at least 10
in
order to execute under DOS. The default for many versions
less than
Upgrading
If
you are upgrading your server from
Manager Advanced
existing software on the server before installing the new software. Remove the software by
selecting the Remove
Building
Some DOS Netstation installations may fail due to disk size limitations
problem is found, we recommend using a
DOS
3.31
Disk
OS/2.
Installation
10, edit the files= line
FILES=20
from
Entry
System (or changing from Advanced to Entry System), you must remove the
LAN
360K
DOS
Boot
Format Incompatible
and
Setup
System
Manager software option from the Installation and Setup program.
Under
of
CONFIG.SYS to be at least 10 and reooot:
to
Advanced
DOS
3+0pen
With
OS/2
OS/2, save the data on the disk, and then reformat
of
DOS is
System
LAN
Software
Manager Entry System to 3+Open LAN
8.
If
your machine has
Diskettes
of
a 360K disk.
720K
or
1.2MB disk drive.
If
you have
If
this
Disabling
Due to a problem in the DOS APPEND command (all versions prior to 4.0), APPEND should not
be used while running the Installation and
been invoked prior to an installation, disable before running the Installation and
typing:
Using
Use
of
supported in this release. In particular, the "target" path cannot
Running
In order to run in the DOS mode
ANSLSYS and EGA.SYS drivers be specified in the CONFIG.SYS.
missing, the program will not be able to display its output. These files are not required to run
under
the
DOS
APPEND
APPEND;
NETSETUP
the Installation and Setup program to modify server configuration settings remotely is not
Installation
DOS
or
under the protected mode
to
Modify a
and
Command
Remote
Setup
of
OS/2 Installation and Setup Program requires that the
in
Setup
DOS
of
OS/2.
program
Server
Mode
of
If
the APPEND command has already
Setup program by
be
'a
remote server.
OS/2
If
either
of
these files is
3+0pen
Part Number 4814-00
10/7/88
LAN
Manager Version 1.0
Installation and Setup Notes
3+0pen
LAN
Manager Version 1.0 Release Notes 4
Checking
After your 3+Open installation to an OS/2 server, OS/2 netstation,
check to be sure that
AUTOEXEC.BAT (for DOS) file overlays a disk partition
For
example
would attempt to overlay it. To avoid this situation, edit to appropriate file to change the E:
NET
PC Servers Using
The
3+Open
mode only. Compatibility mode (also known as
DOS applications under OS/2.
using the following steps:
1. Change line
for
Overlayed Drive IDs
no
NET
USE commands in the STARTUP.CMD
if
you had an E: partition on your hard drive, the command:
NET
USE
E:
\\SERVER\OS2APPS
USE command to another letter (such as G: ).
OS/2
OS/2
Installation and Setup program sets up servers to operate in
17
The
line currently reads protectonly=yes.
DOS Compatibility Mode
To
turn the compatibility mode on, change the CONFIG.SYS file
of the
file
to protectonly=no.
DOS environment and as 3.x box)
or
DOS netstation is complete,
on
your hard disk.
(for
OS/2)
OS/2
or
protected
is
used to run
2. Restart the server hardware.
in
the
The
server now restarts with the compatibility mode turned on.
Creating Generic DOS Netstation Diskettes
The
3+0pen
be customized for individual network users. In many network environments, it
generate generic netstation startup diskettes. These diskettes can
LAN
because they prompt for required information.To create a generic DOS net station startup
diskette:
1. Follow the instructions in the
2.
Installation and Setup Program can create DOS netstation startup diskettes which can
may
be
used in any netstation on the
3+0pen
creating a
To
edit the AUTOEXEC.BAT file remove the (DOS environment variables)
HOME_SERVER= and HOME_SERVER_SECURITY. The resulting DOS netstation
diskette provides a generic logon and network access. All necessary information will be
prompted for
DOS netstation diskette.
by
the logon process.
LAN
Manager Installation
and
Setup Guide
be useful to
3+0pen
Part
Number
10n/88
LAN
Manager Version 1.0
4814-00
3+0pen
LAN
Manager Version 1.0 Release Notes 5
Logging
When the NET LOGON command is issued from the AUTOEXEC.BAT flie, a program called
DLMLOGON is automatically started. This program validates the user name and password and
initiates communication with the network. The
• Prompts for a user name.
• Looks for a DOS environment variable called HOME_SERVER.
• Looks for the DOS environment variable called HOME_SERVER_SECURITY.
•
on
With a DOS
not exist, the
HOME_SERVER environment variable accordingly.
HOME_SERVER_SECURITY environment variable is not set, the DLMLOGON program
prompts the user for the type
for User
If
user security is specified, the DLMLOGON program also asks for the user's password.
In user security mode a link to the user's home server is made using the user name and
password to force a validation
valid information and the server to which they are linking has them listed with a valid
account, drive
If
the administrator has not created an account on the server for the user, the user logon is
not allowed and an "Access denied" message displays at the user's netstation.
supplies an invalid password, an "Invalid password" message is displayed.
DLMLOGON program prompts for the name
or
S for Share.)
Netstation
H:
on their local netstation is linked to the USERDIRS shared directory.
Diskette
DLMLOGON program does the following:
If
HOME_SERVER does
of
the home server and sets the
of
security used at their home server. (Valid responses are U
of
the user name and password.
If
the user has provided
If
If
the
the user
Performance
Notes
OS/2 Disk Caching
The OS/2 supplied with this release includes disk caching as an option. The installation
turns caching on as the default. The caching can be tuned to suit your network requirements. You
should refer to the
OS/2
Filesystem
Included with this release is a program which improves server performance by caching flie system
directory information. The program,
the cache in number
provided with this release.
and add as the last entry to the
DEVICE=\30PEN\SERVER\LANMAN\NETPROG\FASTOPEN.SYS
OS/2
Cache
The cache program included with OS/2 in this release and installed by the OS/2 installation requires
LAN
Manager to be installed with the NETSETUP program before it will execute.
installed and restarted prior to the installation
program is invoked during startup.
Update to Microsoft OS/2 Setup Guide
Directory
of
Program
directories. The program will operate only with the version
Caching
FASTOPEN.SYS takes one parameter which is the size
To
invoke this program, modify the CONFIG.SYS file for the server
flie:
Requires
LAN
Manager Installation
of
If
this happens, ignore the error and install
for
LAN
Manager Servers.
32
LAN Manager, an error will occur when the cache
LAN
of
of
OS/2
If
OS/2 is
Manager.
OS/2
of
3+0pen
Part
10/7/88
LAN
Number 4814-00
Manager Version 1.0
3+Open
3+
Compatibility
3+
and
3+0pen
Networks:
3+MENUS Program
The
3+Menus program versions 1.3.1 and earlier require an update to ensure compatibility with
3+0pen.
if
run.
the
If
An
\APPS\DOSAPPS directory on the server.
networks can operate and coexist together. The document Managing Combined
3+0pen
a DOS workstation has links open
updated version
and
Notes
3+
describes how to
of
this program has been included with this release, and is located in
do
this.
to a 3+0pen
LAN
Manager Version
server, 3+Menus hangs the netstation
1.0
Release
Notes
6
3F & 3P
The
error in a directory listing
command. Updated versions
Technical
netstations do not have this problem.
Token Ring Network Upgrade
The
drivers. Because
unless
standards.
\30PEN\DOSWKSTA\LANMAN\DRIVERS directory. These drivers will also work with
should be used to upgrade your
and are:
To
upgrade your
directory
file name entry, such as:
LINK IDIR
3F
and
3P
programs included with 3+Share versions 1.3.1 and earlier will report an internal
if
a link to a
of
Support at (415) 969-2099. The 3F2 and
3+Open Token Ring drivers follow an IEEE addressing standard which differs from
of
this, a combined
3+
netstations and servers upgrade to drivers which are compatible and conform to the IEEE
The
3+Open drivers
TOK603B.SYS
TOK605B.SYS
TOK1060B.SYS
TOKIBMB.SYS
3+
computers with the new drivers, copy the new driver to the appropriate
of
the computer's boot volume and then modify the CONFIG.SYS file to replace the old
do
3+
3+0pen
these programs are available through your reseller
3+0pen
conform to the IEEE standard and are in the
netstations and servers.
server has been made with the
3P2
programs included with
and
3+
Token Ring network will not interoperate
The
drivers have a letter B at the
NET
3+
USE
or
from 3Com
for OS/2
3+
3+
end
and
TOK603.SYS
with a B version, such as:
TOK603B.SYS
3+Name Service
3+Open Servers
the 3+Name service.
unable to log in
name which is not already present in the 3+ Name service.
3+0pen,
to
3+0pen
Part
10/7/88
LAN
Number
must
have server names which are not registered as server names
If
a server name conflict exists, then OS/2 and DOS netstations will
or
link to the 3+Open server.
be sure to delete its 3+Name service entry.
Manager Version 1.0
4814-00
When
selecting a name for a
or
aliases with
be
3+0pen
If
you are upgrading a 3+Share server
server, use a
3+0pen
LAN
Manager Version 1.0 Release Notes 7
IBM
Some
the DOS boot disk as follows:
IBM
When
SAPS parameter
IBM
When
3Com
IBM
IBM's
Base
Application
of
the following notes suggest changes to the file PROTOCOL.IN!. This file is located
\3
OPEN\DOSWKSTA \LANMAN\DRIVERS\PROTOCOL.IN!
LAN
Manager
using the 3Com DOS Netstation
[DLC]
SAPS = 254
3270
Emulation
using DOS
EtherLink and TokenLink adapter cards must
PC
Network
PC
Network Program 1.3 and the
or
Extended services.
Program
in
the
DLC
Program
Notes
DLC
Program
with the
DLC
DLC
section
of
the PROTOCOL. IN! file
IBM
3270 Emulation Program the interrupt level used on any
1.3
3Com
should be configured
protocol with the
be
set to 2.
DOS
DLC
can
in
the following way:
IBM
must
run
on a 640K
LAN
Manager Program, the
be
set to 254:
machine with either
on
[DLC]
STATIONS = 32
SAPS = 32
The
NET
START
the following parameters:
/CAC:O
If
Extended services is to provide Remote IPL support, then the machine should be dedicated due
to memory limitations.
3Com
The 3+Open
using parameters which are designed to work for the widest range
The
program is highly configurable, and a technical reference containing tuning information
provided in 4 text files included with this release. These files are installed
DOS
'30PEN\DOSDRV\1COMEMM\README.LOD
'3
OPEN\DOSDRV\1COMEMM\README.EMM
'30PEN\DOSDRV\1COMEMM\XBIOS.DOC
'30PEN\DOSDRV\1COMEMM\UL TIMATE.DOC
command
/RQB:512
Maximizer/3SS
LAN
Manager Installation and Setup program installs the 3Com DOS Maximizer/386
in
AUTOEXEC.BAT
/REQ:2
/PC1:128 /PC2:128
of
the
Notes
PC
Network Program 1.3 should contain
/PC3:128
of
combinations
/USN:l
on
the server
of
hardware.
as
is
3+0pen
Number
Part
10/7/88
LAN
Manager Version 1.0
4814-00
3+0pen
Some
of
the following notes suggest changes to the files CONFIG.SYS
These files are created by the Installation and Setup program
follows:
\CONFIG.SYS
\3 OPEN\DOSWKSTA \LANMAN\DRIVERS\PROTOCOL.IN!
LAN
Manager Version
or
PROTOCOL.IN!.
on
the DOS netstation boot disk as
1.0
Release
Notes
8
Programs
The
DOS Maximizer/386 program
themselves. This includes programs such as MS
CONFIG.SYS
The
DOS Maximizer/386 program requires that there be exactly one space between each parameter
entry
in
ignored.
Conflicts
The
3Com
address space
this, the Installation
mapped
your
hardware, you
editing the CONFIG.SYS file.
After installation, enter the proper start
adapter
memory
values should
The
3Com
various parameters.
specified to the right
particular setting
are following the correct procedure listed for both your adapter card
your
workstation.
Using
the CONFIG.SYS file.
with
DOS Maximizer/386 software does
locations,
card
in
saving software more than
DOS Maximizer is designed to avoid conflicts with memory
High
Memory
is
incompatible with programs which use all
Entry
Memory
used
question using the
be
Format
If
there is more than one space, the remainder
Mapped
by
any add
and
Setup program will always reserve the most frequently used
COOO
to
C600, for memory
must
specify the address space to the
entered in paragraph numbers.
The
parameters are listed below
of
the adapter name).
when
run with
Devices
on
devices, including
and
RAM
XNS,
keyword. In the case
one
RAM
and
Windows
not
know
3Com
mapped
length
For
another setting when run with DLC.
of
the memory I/O addressing space
keyword should
for
example; the
2.1 and
the location
network adapter cards. Because
devices.
3Com
of
each adapter (the applicable protocol is
TRM
of
high memory
MS
Windows
of
the
memory
If
this is
memory
multiple cards conflicting.with the
be
used.
Token ring adapter requires one
not
saving software by
The
mapped
and
the protocol running
386
1.0
of
the line will be
mapped
memory
the location used
of
address parameter
devices
Take
care that you
the
by
I/O
of
by
setting
on
The
lines below identify which CONFIG.SYS/ lines
by
NETSETUP. Only the parameter changes indicated need to
3Com
If
This
PROTOCOL.
3+0pen
Part
10/7/88
TokenLink
this adapter
is
done by adding
[TokenLink]
drivername=TLNK$
dmachannel=O
LAN
Number
Adapter
is
used in a 16
IN!
file:
Manager
4814-00
bit
slot, the driver must
or
changing the
Version 1.0
DMACHANNEL=
must
be
be modified.
be
loaded so
entry in the TokenLink section
The
line itself is installed
made manually.
it
uses
DMACHANNEL
of
O.
the
3+0pen
LAN Manager Version 1.0 Release Notes 9
There
IBM
If
is
no
change required
Token
Ring
any IDM Token
(PS/2 only) entries
IDM Token Ring Adapter
ffiM
Token Ring Adapter 2 ram=C800-D600
ffiM
Token Ring Adapter
For
example, with an
entries
With
would
DEVICE=\30PEN\DOSWKSTA\LANMAN\DRIVERS\3comemm.sys
an IDM
DEVICE=\30PEN\DOSWKSTA\LANMAN\DRIVERS\3comemm.sys
be:
ems=O
Token
ems=O
if
a TokenLink adapter
Adapter
Ring
adapter is used then the
in
CONFIG.SYS must be changed
XNS
Protocols
ram=C800-0600
ems=O ems=O
ems=O
ram=D800-DCOO
/A
ems=O
rom=CCOO-CEOO
IBM
Token
Ring
/A
rom=CCOO-CEOO
Ring 2 adapter
adapter and the
OLC
is
installed
3COMEMM.SYS
or
in
an 8 bit slot.
RAM=,
added according
OLC
Protocols
ram=C800-
EMS=,
to
the following table:
DOOO
ram=C800-DOOO
ems=O
ram=D800-DCOO
ems=O
rom=CCOO-CEOO
and
the
DLC
protocols,
the
CONFIG.SYS
ram=CSOO-DOOO
protocols, the CONFIG.SYS entries
ram=DSOO-DCOO
and
ROM=
would
be:
If
these values
you
may
and
round
be
CCOOO-CDFFF the value
DEVICE=\30PEN\DOSWKSTA \LANMAN\DRIVERS\3comemm.
3Com
The
EtherLink
combination
However, this should
leave
most
3Com
Some
These
name
jumper
EtherLink
combinations
will
not
on
do
not
work
have to
the EtherLink
boot
the reference diskette for the PS/2, examine the
up those values
ems=O
Plus
of
3COMEMM.SYS
of
the workstation memory available.
II
of
be
obsetved
found
(DLC) after
to
rom=CCOO-CEOO
Adapter
not
pose
Adapter
video
by
II
produce the same messages.
correctly
the nearest paragraph.
used
display cards
getting the messages
NETLOGON
to
the DISABLE position. Note that other circumstances
on
PS/2
computers with the
in
the CONFIG.SYS line for
and
adapter-based protocols is
a memory space
Configured
problem
with
Memory
and
the EtherLink
Locator
To
fix this problem, change the
IBM
Token
For
example
if
ROM
the
and
ROM
3COMEMM.SYS
sys
ram=DS"OO-DCOO
not
supported in this release.
because the adapter-based protocols
Mapping
II
can
produce address conflicts.
not
responding
(XNS)
memory
Ring
Adapter
RAM
/ A,
addresses,
address is found
becomes
and
networ]{
address
may
also
to
3+0pen
Part
Number
10n/88
LAN
Manag~r
4814-00
Version 1.0
3+0pen
LAN
Manager Version
1.0
Release
Notes
10
Software
NetWkstaSetUid
The netwkstasetuid API was changed to not allow a servername parameter. The value must be
NULL.
Named
If
a process does a DosBufReset in one thread and a DosAsyncRead in another thread on named
pipes it could get blocked in the file system forever. The process must assure that the
DosBufReset is serialized across the threads
Pipes
Network
User
Shares
Net Profile
not create shares that end in a $.
Logging
When the server runs out resources (i.e. NUMBIGBUF)
stop and restart the server this does not get reset. You must stop and restart the workstation to get
the logging reset.
Developer
API
Change
With
Multiple Threads
Administration
Ending
or
NetProfileSaveO will not save user shares that end in a $. Therefore, you should
of
Server
Out
in
$
of
Notes
Resources
if
the DosBufReset is being issued on a named pipe.
Notes
Errors
it
will log the error only once.
If
you
NET
ADMIN
If
you use NET ADMIN program prior to starting the workstation, the help
acannot
before entering NET ADMIN to get the help commands to work.
NET
ADMIN
The
NbT
permissions, where in fact it should create
share from the command line,
creating the share.
Remote
If
the NET ADMIN program is used remotely to add users it will remove access rights previously
granted for the user home directory root, causing subsequent netstation logins to fail.
this, you should restore the group USERS read and execute (RX) access rights to the user home
directory root,
Remote
The OS/2
errors, usually occurring under heavy network load.
Error
find
Sharing
ADMIN program does not share COMM devices correctly.
NET
Admin
LAN
Messages
help
file
of
ADMIN
\30PEN\USERS.
Adding
Function
Manager Remote Admin function may be disabled
Missing
message. You need to do a NET START WORKSTATION
COMM devices
it
with all pennissions. The workaround is to create the
or
to use NET ADMIN to set the permissions on the share after
Users
Disabled
after
Network
Errors
if
(Fl
key) will fail with
It
creates the share without
If
you
do
there are excessive network
3+0pen
Part
10/7/88
LAN
Number 4814-00
Manager Version 1.0
..
3+0pen
NET
ADMIN User Count
The NET ADMIN program does not include administrators in its user count.
NET ADMIN Error Count
When a log file is reset, the error count is not reset to 0, causing the error count not to agree with
of
the number
DOS Netstations Auto Reconnection
If
the administrator deletes a session or removes a share name, and then restores the share, DOS
netstations may be unable to reconnect automatically. In this case the user will have to do a NET
USE to restore the linle
General
IBM PS/2 Model
Some older versions
corruption problem which occurs under heavy load. The problem is fixed by updating the
fmnware on the board.
contact your dealer or
entries in the log file.
Notes
SO
ESDI Controller Problem
of
the PS/2 Model 80 computers with ESDI disk controllers have a data
If
you are having problems with a PS/2 which has an ESDI controller,
IBM
support (1-800-IBM-PROD) for a firmware upgrade.
LAN Manager Version 1.0 Release Notes
11
OS/2 DOS Compatibility Mode
Some versions
mode. This may occur while running some applications.
MS-DOS Net Popup Video Incompatibilities
The MS-DOS Net Popup program included with this release does not work with some video
boards.
DOS NET Command Failure When Invalid Drives in Path
The NET command will not operate correctly under DOS
encountered before
Universal Name Convention (UNC) Names Invalid with Printer
Use
of
UNC names for redirected printers is not supported in this release. Use the
command and the device name:
NET
COpy
instead
of
COpy
of
vendor OS/2 have stability problems while running in the DOS compatibility
if
invalid drives in its search path are
it
finds its configuration control file, LANMAN. IN!.
NET
USE
file.txt
file.txt
LPT1:
\\Server\Printername
LPT1:
\\Server\Printername
USE
3+0pen
Part
10/7/88
LAN
Number 4814-00
Manager Version 1.0
3+0pen LAN Manager Version 1.0 Release
Notes
12
Floppy
Some floppy drives have hardware problems under OS/2, especially when network adapter cards
are used with burst mode DMA.
server
burst mode. Refer to the 3 +
of
Expanded
The OS/2 supplied with this release does not recognize expanded memory.
Drive
or
the supported network adapters.
Access
netstation, check the DMA mode
Memory
Problems
If
Open Network System Guide for information on changing parameters
Not
Supported
Under
you are having problems with the floppy drive on an OS/2
OS/2
of
the network adapter and make sure
it
is not using
3+0pen
Part Number 4814-00
10/7/88
LAN
Manager Version 1.0
Loading...