User Guide

Novell Native File Access Protocols 79
NetWare 6 Readme
103-000171-001
October 25, 2001
Novell Confidential
Manual 99a38 July 17, 2001
Mac OS 8.x Will Not Mount Volumes Checked to Mount at Startup
Mac OS 8.x will not mount volumes checked to mount at startup. To resolve
this, add the server volume's alias to the StartUp Items folder inside the
System Folder on the Mac's local startup disk.
Drag a NetWare Folder to the Trash and Errors Occur
When you drag a NetWare folder to the trash, an error occurs because it is
unable to leave the item in the trash and it will delete it immediately.
This happens on Mac OS 8.1 with NSS volumes. Also, Mac OS X running
with network volumes does not support the functionality associated with the
Trash icon.
0x01 Filenames and NSS Volumes
Certain extensions and control panels (such as MacAdministrator) use
filenames beginning with 0x01 to ensure that they load first. These filenames
will not work correctly on an NSS volume.
Unloading AFPTCP.NLM and WSPDSI.NLM Programs
The Winsock component used by the Macintosh Native File Access NLM
does not always clean up all open sockets. If you unload AFPTCP.NLM and
then explicitly unload WSPDSI.NLM, it might give you the following
warning in flashing red text:
WARNING!!!
1 active Winsock 2 DSI socket session(s)
Unloading WSPDSI.NLM with active session(s) will abend the
server.
Unload all Winsock 2 apps with active SSL socket session(s).
Unload module anyway?
Do not unload the module or the server will abend.
The warning is correct. WSPDSI thinks there are still active AFP sessions and
it will abend the server if you unload it. The last line of the warning should
read "Unload AFPTCP.NLM" but, because AFPTCP is already unloaded,
unloading AFPTCP will have no effect.
There is no need to unload WSPDSI manually. AFPTCP.NLM loads it
automatically on startup and AFPSTOP.NCF does not unload it. It remains
loaded. Under normal use, you should not see this warning.