Advanced File and Print Server Installation and Release Notes

Known limitations

The known software limitations that apply to this Advanced Server release are:

For the latest information regarding updates and supplements, visit the SCO Advanced File and Print Server home page at:

Integration with SCOadmin managers

With this release, it is not possible to administer Advanced Server using the UnixWare SCOadmin Network Configuration Manager, User Manager, Filesystem Manager and Printer Manager.

NetBEUI support

NetBEUI protocol support is not included with this release of Advanced Server.


8-bit character support in user names

UNIX does not support 8-bit characters in user names. If an Advanced Server user account includes 8-bit characters, no equivalent UNIX account will be created. The solution is to manually create a UNIX user with a similar name to the AFPS user and to use the mapuname utility to associate the UNIX user with the Advanced Server user.

UNIX file locking

To best support concurrent access to a file by both UNIX and Windows users, set the Registry key UseOplocks to the value 0 (do not use opportunistic locks). When UseOplocks is set to 1 (the default value), Windows 95 and Windows NT users will not see file changes made by UNIX applications because, as the result of being granted an opportunistic lock, Windows clients assume that no other user has write access to the file.

Use ASU Administrator to set UseOplocks in the Registry. See SCO Advanced Server Administrator Guide, Appendix A, Advanced Server Registry, for details on changing server configuration parameters.

Printer support

Print administration

See also:

Client printing

Support for the redirection of UNIX spooled print jobs to printers attached to Windows client or server systems is not provided in this release of Advanced Server.

Cancelled job mail

In some circumstances, Advanced Server sends mail to the administrator account (root) saying the printer request was cancelled by the administrator.

The print jobs complete successfully and the messages can be disregarded.

This may occur when using:

VisionFS and Advanced Server incompatibility

VisionFS and Advanced Server cannot run concurrently on the same system. VisionFS incorporates its own TCP/IP NetBIOS which conflicts with the in-kernel TCP/IP NetBIOS used by Advanced Server.

To run Advanced Server on a system with VisionFS already installed, first stop VisionFS with the command:

  visionfs stop
then start the TCP/IP NetBIOS and Advanced Server using the commands:
  netbios start
  net start server

To run VisionFS on a system with Advanced Server installed, first stop the Advanced Server and the TCP/IP NetBIOS using the commands:

  net stop server
  netbios stop
then start VisionFS with the command:
  visionfs start
You can prevent Advanced Server and the TCP/IP NetBIOS from starting at boot time by renaming the files /etc/rc2.d/S74netbios and /etc/rc2.d/S99ms_srv to /etc/rc2.d/s74netbios and /etc/rc2.d/s99ms_srv respectively.

To avoid any conflict between VisionFS and Advanced Server, it is recommended that you remove VisionFS from the system before installing the Advanced Server product.

Windows NT compatibility

Security features in Windows NT 4.0 Service Pack 3

Windows NT 4.0 Service Pack 3 introduces a new security feature that can result in Advanced Server failing to communicate with an NT 4.0 server or workstation. By default, Service Pack 3 does not introduce any incompatibilities but, if the registry is subsequently modified to enable the SMB signing security feature, the NT system can no longer communicate with Advanced Server.

Building applications using API libraries

When building application using the Advanced Server API libraries, if the compiler reports errors similar to the following:
    Undefined                       first referenced
     symbol                             in file
    __builtin_delete                    /usr/lib/
    __builtin_new                       /usr/lib/
then you need to include the Advanced Server compatibility library, on the compiler command line. For example:
    cc program.c -o program -I/usr/include/lmx \
       -llmx -lnsl -ldl -lc -lasulang -lasusec -lsam -lthread \
       -lcrypt -lmsrpc -ltask -lrpcapi -llmxcomp

© 2004 The SCO Group, Inc. All rights reserved.