NETWARE FOR MACINTOSH v3.12 RELEASE NOTES (c) Copyright 1993, 
Novell, Inc. All rights reserved.

Welcome to NetWare for Macintosh v3.12! This file contains 
information for the 5-user and 200-user versions of NetWare for 
Macintosh v3.12. The 5-user version comes with the NetWare 3.12 
operating system, and can run only with NetWare 3.12. The 200-user 
version must be purchased separately and will run with both 
NetWare 3.11 and NetWare 3.12. 

The file covers these topics:

I. System requirements and installation

II. Enhancements to APPLETLK.NLM (the AppleTalk protocol stack 
and router), ATCON.NLM (the AppleTalk console server module), and 
to SNMP support. 

III. Server administration

IV. Using VRepair with NetWare for Macintosh

V. Known problems

The NetWare for Macintosh Installation and Maintenance manual 
(Novell Part #100-001810-001) and the Using the NetWare for 
Macintosh Client manual (Novell Part #100-001796-001) document 
this release of the NetWare for Macintosh software. 

We recommend that you print this file and save it as a reference to 
this new release of NetWare for Macintosh.


I. SYSTEM REQUIREMENTS AND INSTALLATION 

== Supported LocalTalk Cards and Drivers ==

The DL/2 or DL2000 LocalTalk cards from Dayna Communications, 
Inc. are the only LocalTalk cards that support NetWare for 
Macintosh. Version 3.17 of the DL2000.LAN and DL2.LAN drivers are 
required for use with NetWare for Macintosh v3.12. When you install 
NetWare for Macintosh v3.12 on a NetWare v3.11 server, the process 
copies these drivers. When you install NetWare for Macintosh v3.12 
on a NetWare v3.12 server, the process does not install these drivers 
because they are already included in NetWare v3.12. 

You can obtain LocalTalk cards by contacting Dayna Communications:

Dayna Communications, Inc. 

Sorenson Research Park

849 W Levoy Dr.

Salt Lake City, Utah 84123-2544

Phone: 801-269-7200

Fax: 801-269-7363


== General Guidelines for Installing NetWare for Macintosh v3.12 ==

(1) If you are installing the 5-user version of NetWare for Macintosh 
from CD-ROM, be sure to install the on-line documentation set 
provided with NetWare v3.12 before attempting to install the 
product. The on-line documentation provided with NetWare v3.12 
includes the NetWare for Macintosh Installation and Maintenance 
guide. 

(2) The file ATCFG.NLM has been renamed ATCONFIG.NLM.

(3) This release of NetWare for Macintosh includes Version 3.07 of 
APPLETLK.NLM, Novell's implementation of the AppleTalk protocol 
stack and router. 

You should not replace the version of APPLETLK.NLM or ATCON.NLM 
that accompanies the NetWare Multi-Protocol Router, MPR Plus, or 
WAN Links with any version of APPLETLK.NLM that you receive 
with NetWare for Macintosh or with the NetWare AppleTalk Support 
Package. The version of APPLETLK.NLM accompanying the NetWare 
Multi-Protocol Router, MPR Plus, and WAN Links includes WAN 
capabilities that are not supported by APPLETLK.NLM v3.07. These 
products rely on the presence of those WAN capabilities.

Therefore, you should perform NetWare for Macintosh v3.12 
installation before NetWare Multi-Protocol Router, MPR Plus, and 
WAN Links installation. If any of these products have already been 
installed, the NetWare for Macintosh installation process displays a 
warning message and gives you the option of cancelling the 
installation. If you want to use MPR, MPR Plus, or WAN Links, 
remove them before installing NetWare for Macintosh. After you 
have installed NetWare for Macintosh, install these products again. 

If you have questions about the NetWare Multi-Protocol Router, MPR 
Plus, or WAN Links, please refer to the documentation for each 
product.


== Installing NetWare for Macintosh v3.12 on a NetWare v3.11 
Server (200-User Version Only) ==

When you install NetWare for Macintosh v3.12 on a NetWare v3.11 
server, the process copies AFTER311.NLM, SNMP.NLM, NWSNUT.NLM, 
DL2.LAN, and DL2000.LAN, in addition to its other operating system 
files. When you install NetWare for Macintosh 
v3.12 on a NetWare v3.12 server, the process does not install these 
files because the most current version of each file is already included 
in NetWare v3.12. 


== Installing NetWare for Macintosh v3.12 from CD-ROM (5-User 
Version Only)==

To install NetWare for Macintosh v3.12 from any disk format, you 
must load INSTALL.NLM, select the Product Options menu, press 
<Ins>, and either use the default path to the source media or provide 
the correct path. This path is either the path to the original media 
(such as A:, B:, or the CD-ROM path) or a path to a location where a 
copy of the original media has been made (such as 
C:\SERVER\NW_MAC or SYS:\NW_MAC). 

In the case of installation from CD-ROM, you must provide the path 
X:\NETWARE.312\ENGLISH\NW_MAC, where X: is the drive letter for 
the CD-ROM. (The drive letter is often D:). 


== Installing the NetWare for Macintosh Client from CD-ROM (5-User 
Version Only)==

If you install NetWare for Macintosh from CD-ROM, a DOS-format 
compressed file containing the NetWare for Macintosh client software 
is copied to the NW-MAC directory on the server volume where you 
installed NetWare for Macintosh; for example, if you installed 
NetWare for Macintosh on the SYS: volume, that is where the client 
software will be copied. You must uncompress the file from a DOS 
workstation before you can use it on a Macintosh. The following 
procedure explains how to uncompress this file. 

(1) Start the server.

The server must have MAC.NAM and AFP loaded and the volume 
containing the NW-MAC directory must have the Macintosh name 
space installed. You install the Macintosh name space by typing ADD 
NAME SPACE MACINTOSH TO <volume> at the server console. Type 
VOLUMES at the server prompt to verify that the name space has 
been added.

(2) Log in to the server from a DOS workstation.

(3) Change to the NW-MAC directory.

(4) Enter the following command:

macclnt

This command runs a file called MACCLNT.EXE. This is the archive file 
containing the NetWare for Macintosh client software in DOS format, 
so it can be stored on the CD containing NetWare for Macintosh. 
When you run MACCLNT.EXE, it converts the file into a compressed 
archive that can be run from a Macintosh workstation.

(5) Log in to the server from a Macintosh workstation.

(6) Locate the file MACCLIENT.SEA in the NW-MAC directory.

(7) Double-click on MACCLIENT.SEA.

The compressed files are extracted to the NW-MAC directory on the 
server.

(8) Continue the installation as instructed in the guide Using the 
NetWare for Macintosh Client. 


== Copying the Installation Files from CD-ROM to a Floppy Diskette 
(5-User Version Only) ==

If you copy the installation files from CD-ROM to a floppy diskette, 
you must give the floppy diskette the volume label NW_MAC. If you 
do not, you cannot use the floppy diskette to install NetWare for 
Macintosh.


== Installing ATTOKLLC.NLM ==

If you are running NetWare for Macintosh v3.12 on a NetWare v3.12 
server and you need Token Ring support, you do not use the file 
ATTOKLLC.NLM described in the NetWare for Macintosh Installation 
and Maintenance guide. Instead, you must install and load the file 
LLC8022.NLM. When you consult the manual, read all references to 
ATTOKLLC.NLM as LLC8022.NLM. 

If you are running the 200-user version of NetWare for Macintosh 
v3.12 on a NetWare v3.11 server, you must still copy and load the 
file ATTOKLLC.NLM as described in the NetWare for Macintosh 
Installation and Maintenance guide.


II. ENHANCEMENTS

== Router Enhancements ==

(1) We resolved a problem in which the sender's network number in 
the first two bytes of the RTMP data portion was byte-swapped in all 
but the first packet of responses that required more than one packet. 
This problem was caused by a condition in a Phase 1 network, in 
which a node that learned its network number by broadcasting 
RTMP requests could be dynamically configured with the wrong 
network number. The sender's network number is now set correctly 
when multiple RTMP data packets are sent in response to an RTMP 
router data request.

(2) In a previous release of APPLETLK.NLM, the last zone name of 
one reply packet and the first zone name of a subsequent reply 
packet for a multi-packet reply could be duplicated if routers 
without zones appeared in the routing table. Duplicate zones names 
sometimes appeared in the Chooser. This problem should no longer 
occur.

(3) We fixed a problem in which LOAD and BIND commands could fail 
when zone names included leading, trailing, or embedded spaces, or 
when certain keywords were used in the BIND or LOAD command 
line. LOAD and BIND commands with LOAD or BIND command line 
keywords are now allowed. LOAD commands that use zone names with leading 
or embedded spaces are now allowed; however, on the LOAD command line, 
the quotation marks in the zone name cannot be preceded with a space. 
For example, zone={ "MYZONE"} and zone={"MYZONE "} are NOT allowed. 
BIND commands that use zone names with leading, trailing or embedded 
spaces are now allowed. 


(4) Previously, the AppleTalk router advertised itself as a NetWare 
router through NBP using the name "NetWare AppleTalk 
Stack/Router" instead of the actual server name. Now the AppleTalk 
router correctly advertises itself as "<server name>: NetWare Router 
@ <zone name>."

(5) The periodic CPU utilization peaks caused by RTMP as observed 
on slower machines on large internets has been fixed. Formerly, the 
CPU utilization as seen in the Monitor utility went up to almost 100% 
about every 10 seconds. This is no longer the case.

(6) The message informing you that an RTMP router has gone down 
has been changed from a warning message to an informational 
message. It no longer appears on the console screen by default.


== Stack Enhancements ==

(1) We resolved a problem with the AppleTalk protocols in which 
some users reported difficulties maintaining idle ADSP connections. 
In the previous release of the APPLETLK.NLM, applications such as 
NetWare for SAA, NetWare SQL, and some third-party applications 
could lose their ADSP connections if the application did not receive 
transmitted data after a couple of minutes. For example, a backup 
application lost its ADSP connection to the Macintosh during the time 
it took to change a tape cartridge on the backup device. In this new 
release of APPLETLK.NLM, this problem should not occur.

(2) Previously, AFP sessions would hang under certain limited 
conditions. An ASP ATP request was checked to determine that it 
came from the correct remote endpoint. If this check failed for any 
reason, AppleTalk disregarded subsequent requests, causing the AFP 
session to hang. This problem was fixed in version 3.06 of the 
APPLETLK.NLM and should not occur in the latest release.


== SNMP Support Enhancements ==

(1) APPLETLK.NLM now loads SNMP.NLM v2.08 (the SNMP agent, 
which is included with the NetWare 3.12 operating system) when 
APPLETLK.NLM itself is initialized. This enhancement means that 
ATLKSNMP.NLM, provided with NetWare for Macintosh v3.011, is no 
longer required and is not included in NetWare for Macintosh v3.12.


== ATCON.NLM Enhancements ==

(1) The ATCON module now combines Router Statistics and Stack 
Statistics. The AppleTalk Statistics information includes both a router 
counter and a stack counter.

(2) ATCON now reflects NBP registration for the AppleTalk protocols. 
The NBP type of the stack is "NetWare AppleTalk Server."

 
== AFP.NLM Enhancements == 

(1) A problem reported with previous versions of NetWare for 
Macintosh is now fixed. If the "encrypt" option was used on the 
AFP.NLM command line, the Chooser gave users the option of 
choosing "Standard Apple UAMs," even though the Apple UAMs were 
not available on the server. If the user selected "Standard Apple 
UAMs," the Chooser would display this message: "This file server 
does not use a recognizable log on sequence." This anomaly was 
caused by a Macintosh client software problem.

This problem is now fixed in the following AppleShare Macintosh 
client software releases:

- AppleShare v3.5 (distributed with AppleShare v3.0 server and 
with the NetWare for Macintosh client software)

- AppleShare v7.1 (distributed with Macintosh System 7.1)

(2) A network administrator can specify that a DOS user log in from a 
particular workstation by including the hardware address of the 
machine in that user's account through SYSCON. In previous versions 
of NetWare for Macintosh, Macintosh users could still log in using 
that account, even though the address was restricted. In NetWare for 
Macintosh v3.12, if such a restriction for a DOS user exists, a 
Macintosh user cannot log in using that account. Restricting the 
address for a Macintosh workstation is not supported.


== Macintosh Client Enhancements ==

(1) The Macintosh Finder does not operate properly with 
server volumes larger than 2 gigabytes (GB). We have created a 
workaround to this problem. Formerly, if you attempted to 
copy files to a volume larger than 2 GB, the system displayed a 
message claiming that not enough free space was available on the 
volume. Our workaround causes the Finder to show that a volume 
contains fewer than 2 GB, even if it contains more. As a result, the 
incorrect error message is no longer displayed, and you can copy files 
to a volume larger than 2 GB. However, users will see inaccurate size 
information.


III. SERVER ADMINISTRATION ISSUES 

(1) When you configure or remove previous versions of NetWare for 
Macintosh by using the ATCONFIG or ATREM modules (called by 
INSTALL), the server's search path must include the directory 
containing these modules. These modules are installed in 
SYS:\SYSTEM. If you move them to another location, make sure you 
change or add a search path to include that location.

(2) If you edit the NetWare for Macintosh configuration files 
(ATZONES.CFG, ATPS.CFG, *.FNT) from a Macintosh workstation, note 
that NetWare for Macintosh expects a line feed character (0xA) 
between all lines of the file. Most Macintosh text editors use a 
carriage return (0xD) instead of a line feed to separate lines. 
Configuration files that lack line feeds are not read correctly by the 
module. NetWare installation and EDIT.NLM always use line feeds.

(3) When a Macintosh user deletes files from the server and empties 
the Trash while the Purge attribute on the files is turned OFF, the 
server volume does not report more space in the server volume 
immediately. This situation is normal; the file space is being moved 
from the "erased but not purgeable" to the "erased and purgeable" 
list. The amount of available space is updated when the files are 
purged.

(4) ATPS print queues for ImageWriter LQ printers can support a 
maximum of one paper bin. Therefore, print jobs sent to an 
ImageWriter LQ printer from an ATPS print queue access only the 
first paper bin.

(5) The maximum legal NBP name length is 32 characters. Therefore, 
if a printer name has 30 characters or more, you cannot use the 
default queue name "NW printer-name" because adding the three-
character string "NW "to "printer-name" would result in a default 
queue name longer than 32 characters.

(6) If you set up your Apple LaserWriter to be connected serially to 
a queue (using PSERVER), use the PostScript utility SERIAL.PS to 
enable your LaserWriter to use 8-bit serial communication; 
otherwise, all 8-bit characters in your print jobs are mapped to 
seven bits. SERIAL.PS is installed in SYS:PUBLIC. To install this utility 
on your printer, use NPRINT to send the file to the PostScript 
printer's memory.


IV. USING VREPAIR WITH NETWARE FOR MACINTOSH

To run VRepair on a volume supporting the Macintosh name space it 
is necessary to load an additional NLM, V_MAC. Follow these steps to 
load V_MAC. (V_MAC should reside in the same directory from 
which VRepair will run.)

1. Load VRepair at the system console screen by typing

LOAD VREPAIR

2. Press <Alt>+<Esc> to toggle to the ":" prompt on the system console 
screen.

3. Type

LOAD V_MAC

4. Press <Alt>+<Esc> to toggle back to the VRepair console screen.

VRepair is now set to run on any volume supporting the Macintosh 
name space. Refer to the NetWare System Administration Manual for 
additional VRepair information. Alternately, you can store 
VREPAIR.NLM and V_MAC.NLM on your DOS partition in the same 
directory where SERVER.EXE is stored, or on a floppy diskette. Then, 
when the SYS volume fails to mount, perform these steps:

1. Type

SEARCH ADD C:\NW # Specify the path to your SERVER.EXE directory

2. Type:

LOAD VREPAIR

NOTE: Be careful not to remove the Macintosh name space on a 
volume containing Macintosh files. The files will be corrupted.


V. KNOWN PROBLEMS

== Known Problems in NetWare v3.11 ==

NOTE: To the best of our knowledge, these problems persist in 
NetWare 3.12, EXCEPT Problem #1. 

PROBLEM #1: When you move a Macintosh application from one 
folder to another while that application is being run by a Macintosh 
workstation, the volume directory structure becomes corrupted. 
After this happens, workstations lock up when attempting to list the 
contents of the directory, attempts to dismount the volume from the 
server console never complete, and Monitor freezes if you attempt to 
clear the workstation's connection. These problems are fixed when 
the server is restarted and the volume is loaded again. The mount 
process generates this message:

Volume mount had the following error(s) that were fixed: Number of 
phantom files that were removed 2

The application that was moved may have a damaged resource fork 
and should be reinstalled on the file server.

CAUSE: This situation is caused by a problem in the NetWare v3.11 
operating system. However, this problem is fixed in NetWare 3.12.

SOLUTION: Do not move applications that are in use. To prevent users 
from moving applications, you can flag the application with the 
Delete Inhibit and Rename Inhibit attributes.


PROBLEM #2: The server might hang if IPX.COM or IPXODI.COM is run 
under DOS before the server is loaded. 

CAUSE: This situation occurs only when the server binds a protocol to 
the same network board that IPX.COM or IPXODI.COM is using. 
NetWare is not designed to share a network board with DOS. 

SOLUTION: Add another network board to the server for use by 
IPX.COM or IPXODI.COM. No server protocols should be bound to this 
board.


PROBLEM #3: Error messages are generated about lost hardware 
interrupts.

CAUSE: There are two possible causes for these error messages. If the 
server is a 486 system, there is a documented problem with lost 
hardware interrupts with the 486 chip. If the server is a 386 system 
and is using the NE/2 or NE2000 LAN driver, the messages result 
from a timing problem between the LAN driver and the NetWare 
operating system.

SOLUTION: There is no apparent operational side-effect to this 
problem, so you can ignore these messages. If they are generated 
frequently, you can instruct the system to stop displaying the 
messages by using this SET command line: 

SET Display Lost Interrupt Alerts = OFF


PROBLEM #4: When you restore Macintosh files using *some* 
versions of the SBACKUP utility and the restore path is different 
from the backup path, folders are restored with their DOS names 
only.

CAUSE: An SBACKUP software problem causes this situation to occur.

SOLUTION: Restore Macintosh files only to their original volume and 
directory.


== Known Problems in ATCON.NLM == 

PROBLEM #1: On very large internets, the "View RTMP Table" 
function of ATCON is practically unusable when you are using any 
machine earlier than a 486 model. When you select this function, the 
"Please Wait" message displays for several minutes, and ATCON 
responds sluggishly to keyboard input.

CAUSE: ATCON builds and displays an updated RTMP list every 5 
seconds. When the RTMP list is very large (covering several hundred 
or more networks), the time required for ATCON to retrieve data 
from the router and build the new list can be greater than 5 seconds. 
While it is building the new list, ATCON does not process keyboard 
input.

SOLUTION: Bring the system console to the screen; press <Alt>+<Esc> to 
make the colon prompt appear. From the system console, unload 
ATCON. This course of action is faster than waiting for ATCON to 
process an <Esc> keystroke to quit the "View RTMP Table" function.


== Known Problems in Macintosh Client Software ==

PROBLEM #1: Device names appear and disappear rapidly, or they 
don't appear at all in the Chooser when there are many instances of a 
single service in one zone.

CAUSE: A well-known limit on the number of services displayed in 
the pre-System 7.0 Macintosh Chooser causes this problem. It occurs 
when many devices of the same type reside in the same zone. This 
problem has been observed with a group of more than 15 device 
names whose average length is 12 characters. Information on device, 
zone, and name limitations in older versions of the Chooser can be 
found on AppleLink in the Apple Support/Training Icon. The search 
syntax under Tech Info Library is "Chooser Devices." The file name is 
"Chooser: Device, Zone, and Name Limits."

SOLUTION: One option is to upgrade client software to System 7.0 or 
later. Another is to reduce the total number of characters in the 
names of services of one type (e.g., the names of all AppleShare 
servers in a zone) in one zone. You can do this by shortening names 
or by redistributing service providers among zones so that fewer 
exist in any one zone, or by doing both.

If you configure many ATPS print spoolers on a server, you may 
have experienced this problem for the service "LaserWriter" (print 
queues or LaserWriters not appearing consistently in the Chooser). A 
new feature in NetWare for Macintosh allows for the registration of 
individual queues in one list of zones. 


PROBLEM #2: In System 7.x, when locating an item referenced by an 
alias, the Finder skips the NetWare UAM, even if it is installed in the 
Macintosh's AppleShare folder. As a result, the password is not 
encrypted. If the "encrypt" option is used on the AFP.NLM command 
line, the login attempt fails. 

CAUSE: A Macintosh system software problem causes this situation to 
occur.

SOLUTION: Log in to the server through the Chooser.


== Known Problems in APPLE IIGS Client Software ==

PROBLEM #1: Printing from the Apple IIGS to ATPS.NLM queues for 
the ImageWriter and ImageWriter LQ may work unreliably, causing 
corrupted data and incorrectly printed images.

CAUSE: The cause of this problem is not currently known, but the 
IIGS has shown similar behavior when printing to other print 
spoolers.

SOLUTION: Print directly to ImageWriter and ImageWriter LQ 
printers and not to queues when using the Apple IIGS.


== Known Problems in QuickMail for Macintosh (CE Software,Inc.) ==

PROBLEM #1: When files enclosed in a QuickMail message are 
retrieved 
to a NetWare volume, the files become corrupted.  

CAUSE:  This occurs with any version of QuickMail for Macintosh
(2.x - 2.6) when the client accesses a NetWare volume utilizing
NetWare for Macintosh 3.12.  QuickMail MHS for Macintosh is not
affected.

SOLUTION:  CE Software, Inc. is aware of this problem and is working
to provide a solution.  Please contact CE Software Technical Support 
at (515)224-1953 for more information.


== Known Problems in AFP.NLM == 

PROBLEM #1: When a Macintosh user attempts to overwrite a folder 
inside a parent folder in which the user has Create but not Erase 
rights (for example, by dragging a folder of name "XXX" to a parent 
folder that contains another folder named "XXX"), the user is warned 
that he or she does not have sufficient rights to perform the 
operation because he or she does not have the Erase right. However, 
because the user does have the Create right, the system offers the 
user the option to continue or cancel the operation. If the user 
cancels, no problem occurs. If the user continues, the system returns 
an error message numbered -1805, and the overwrite of the folder is 
disallowed. This problem is restricted to System 7.0 and later.

CAUSE: A conflict between NetWare rights and AppleShare 
permissions causes this problem.

SOLUTION: If possible, make sure the user acquires the Erase right in 
the parent folder where that user wants to perform the overwrite 
operation. Otherwise, the user must (a) rename the folder that he or 
she wants to place in the parent folder, (b) drag it into the parent 
folder, (c) have another user with Erase rights delete the folder that 
the original user wanted to overwrite, and (d) rename the new folder 
back to its original name after it is in the parent folder.

== Known Problems in ATPS.NLM == 

PROBLEM #1: Macintosh font-downloading programs and other 
printer utilities do not work with ATPS, and attempts to use these 
programs with ATPS often cause the Macintosh to hang.

CAUSE: These utilities are created to work directly with printers, and 
their design does not allow for the use of spoolers.

SOLUTION: Download fonts directly to AppleTalk printers. Novell is 
working with vendors so that future versions of their utilities may 
be able work with ATPS.


PROBLEM #2: Macintosh jobs submitted through ATPS to non-
PostScript printers with special options are incorrectly formatted on 
the page or printed on paper from the wrong source.

CAUSE: The ATPS print spooler does not support use of a sheet feeder 
with the ImageWriter II or ImageWriter LQ, and does not support 
use of multiple bins with the ImageWriter LQ. Envelope printing to 
HP DeskWriters and manual feed printing to the HPPaintWriter XL 
are also unsupported options.

SOLUTION: Do not use these printer options and configurations in 
conjunction with ATPS. Print directly to the printer instead.


PROBLEM #3: Warning messages about unreleased resources 
sometimes appear on the console when ATPS is unloaded.

CAUSE: When ATPS is unloaded, it may not release some of its 
resources, especially if printing is in progress. Instead, the release is 
performed by the operating system, which prints messages on the 
console.

SOLUTION: Ignore the messages.


PROBLEM #4: When print job logging and accounting are being used 
with some PostScript printers, the page count reported by ATPS and 
used as the basis for charging is inaccurate or is listed as "-1", which 
indicates an error.

CAUSE: In order to do accurate page-based logging and accounting, 
ATPS depends on the target printer to return its lifetimecount of 
printed pages using the PostScript "pagecount" statusdict operand. 
ATPS cannot accurately charge users for jobs if the target PostScript 
printer does not return the correct information. Some PostScript 
printers and nearly all spoolers do not support this operand. In 
addition, other printers may sometimes report inaccurate 
information.Additionally, anomalies in ATPS.NLM can intermittently 
lead to an extremely high positive or negative page count.

SOLUTION: If you use ATPS printer accounting or require that the 
page count reported in the ATPS printer logs is accurate, monitor the 
page count to make sure it is being reported accurately. If it is not, 
contact your printer vendor or consider using a different PostScript 
printer model.


PROBLEM #5: This problem can occur when using PageMaker 4.2 to 
print to a server that has never spooled jobs from an earlier version 
of PageMaker. When the PageMaker 4.2 jobs are submitted to a 
printer, they fail to print, and the following PostScript exception is 
returned:

[ Error: undefined; Offending Command: AldusDict2 ]

ATPS will return this error to the System Log and to the ATPS 
screen, if active:

ATPS: open dictionary file: no such file or directory

CAUSE: A change in the PageMaker AldusPrep dictionary causes 
ATPS to parse its version and revision information incorrectly when 
it is downloaded to the spooler, and the file into which ATPS saves 
the dictionary is named incorrectly. As a result, ATPS is unable to 
access the file when it is time for the job to be printed.

SOLUTION: If this problem occurs, go to the ATPS directory on the 
server (the default is SYS:SYSTEM\ATPS) and rename a file named 
either "ALD00.PRS" or "AL00.PRS" to "ALD20955.PRS." Taking this 
action will correct the problem permanently for all ATPS spoolers on 
this server, unless the file is later deleted or renamed, or the ATPS 
directory is changed. 


PROBLEM #6: When printing to an ATPS spooler using the Adobe 
Macintosh printer driver (also known as. PSPrinter, LaserWriter 8.0, 
or PostScript Level 2 driver), Macintosh clients do not receive all 
options or suffer poor printing performance.

CAUSE: Our testing with a pre-release version of the driver shows 
that it queries PostScript printers and spoolers for more information 
than NetWare for Macintosh 3.12 is able to provide. One result of this 
is that *all* fonts are downloaded with each print job by the driver. 
Also, certain options like fax printing may be unavailable.

SOLUTION: If this problem causes difficulties, print directly to the 
printer or go back to using the standard LaserWriter driver. 


PROBLEM #7: When printing to an ATPS spooler supporting a large 
font list (hundreds of fonts), spooling even small jobs can take a long 
time.

CAUSE: ATPS responds to font list queries in a format compatible 
with all LaserWriter drivers. Unfortunately, this format is very 
inefficient, and communicating the font list to the Macintosh takes 
about a minute for each hundred fonts.

SOLUTION: ATPS offers the -r configuration option to specify that the 
spooler respond the the font list query in a more efficient format 
understood by later versions of the LaserWriter driver. For example:

-o "Fast Spooler" -l -f hplaser -r -wb

Using this option can speed spooling by potentially several minutes 
per job, depending on how many fonts the spooler advertises. Do not 
use this option for spoolers that will be used for printing with 
LaserWriter 5.2 or below or Aldus PageMaker 4.2a.


PROBLEM #8: ATPS sometimes ABENDs the server when it is 
unloaded, with the following message displayed on the server 
console:

"RemoveFile called with invalid file handle."

CAUSE: This problem is caused by anomalies in NetWare and 
CLIB.NLM. The ABEND is extremely uncommon and is usually related 
to multiple spoolers using the same file with the -f ATPS.CFG option.

SOLUTION: If you experience this problem, make copies of each 
shared font list file for all the spoolers that access it, each with a 
different name. Make sure that no two spoolers reference a file with 
the same name.

For example, if ATPS has the following configuration:

-o "HP Spooler1" -l -f hplaser -wb

-o "HP Spooler2" -l -f hplaser -wb

go to the SYS:SYSTEM\NW-MAC\FONTS directory and execute the 
command:

COPY HPLASER.FNT HPLASER2.FNT.

Then, change your ATPS.CFG file to read:

-o "HP Spooler1" -l -f hplaser -wb

-o "HP Spooler2" -l -f hplaser2 -wb


PROBLEM #9: When printing in draft mode to an ATPS spooler using 
the HP DeskWriter v3.1 driver or DeskWriter color driver v2.0, the 
Macintosh hangs while printing the job. The hang persists until the 
job is cancelled.

CAUSE: This problem is caused by irregularities in ATPS emulation of 
DeskWriter printers. Other DeskWriter family drivers may be 
affected as well.

SOLUTION: Avoid using draft mode printing with affected drivers. 


PROBLEM #10: When printing in draft mode to an ATPS spooler using 
the HP DeskWriter 550C driver v1.0, the Macintosh hangs while 
printing the job. The hang persists until the job is cancelled.

CAUSE: This driver is not supported by NetWare for Macintosh 3.12.

SOLUTION: A possible workaround to this problem involves using the 
DW-C 2.0 driver included with the HP DeskWriter C printer. Although 
this driver is not officially supported by Novell or Hewlett Packard, 
we have experienced acceptable results using this driver to print to 
the DeskWriter 550C. To set up a spooler and printer server to accept 
DeskWriter C input and redirect it to a DeskWriter 550C, use a 
configuration like the one below:

-o "DeskWriter 550C" -t DeskWriter -c -wb

"My DW 550C:My Zone" -q DESKWRITER_550C -t "DeskWriter 550C" -
wf

The first line creates a spooler of type "DeskWriter" that you can see 
in the Chooser as "DeskWriter 550C." This spooler submits jobs to the 
queue "DESKWRITER_550C. The -c option specifies that the printer 
has a color cartridge available. The second line specifies the 
DeskWriter 550C printer "My DW 550C" in zone "My Zone" should 
service queue "DESKWRITER 550C."

One disadvantage of this workaround is that only one of the 550C's 
two ink cartridges can be accessed by the DW-C driver. Only the color 
cartridge is used when the spooler is configured with the -c option, 
and only the black ink cartridge is used when the -c option is 
omitted.

This configuration has not been extensively tested by Novell, and it is 
not guaranteed to work in all cases. 


PROBLEM #11: Sometimes the last page of a job printed to an 
AppleTalk printer is incomplete or missing.

CAUSE: This problem is caused by an anomaly in APPLETLK.NLM that 
causes problems very infrequently; however, the problems can be 
exacerbated by an unreliable network connection between the server 
running NetWare for Macintosh and the printer. The problem 
appears more often printing to non-PostScript printers.

SOLUTION: Make sure that your network connections to your printers 
are reliable. 


Problem #12: When you use the LaserWriter 7.2 driver, the 
automatic setup option for special printer features is not supported 
by NetWare for Macintosh v3.x spoolers. You can access this option 
by choosing the Setup button in the Chooser after selecting a printer. 
If you press the Setup button in the Automatic Setup dialog box, the 
Macintosh hangs for more than a minute, or until you click Cancel to 
discontinue the setup process. If the setup is not accomplished, 
special options for selecting paper trays and enabling and disabling 
Photograde and FinePrint will not be available when you print.

Cause: This problem is caused by irregularities in the query behavior 
of the Setup option.

Solution: You can manually set up the characteristics of the target 
printer so that the special options will be available in the Print 
dialog box. Hold down the Option key while clicking the Select button 
in the Chooser, and supply the required information about the target 
printer.



== Known Printing Problems with Third-Party Software ==

PROBLEM #1: Users may experience very slow printing performance 
or downloading of fonts that are already on the printer when 
printing from Aldus PageMaker 4.2 for the Macintosh to an ATPS 
print spooler for a PostScript printer.

CAUSE: PageMaker 4.2 expects a non-standard format when making 
a font list query of a printer or spooler. It does not recognize the 
standard query format returned by most print spoolers, including 
ATPS, so it downloads fonts unnecessarily, greatly increasing the 
time necessary to spool and print the job.

SOLUTION: Three different strategies for avoiding this problem are 
available.

a) The first and best solution is to obtain Aldus' update, PageMaker 
4.2a, which resolves this problem by accepting the font list query 
response in the standard format. However, you should not use the 
Fast Font Response (-r) spooler option for spoolers that will be 
printed to from PageMaker 4.2a unless you use a special font list, as 
discussed under the third strategy.

b) The second strategy involves using the Apple LaserWriter driver 
when you are printing from PageMaker 4.2. In order to do this, 
simply hold down the Option key when you choose the Print option 
from the File menu. Not all PageMaker features are supported when 
you print in this manner, but the majority of jobs should print 
correctly.

c) The third strategy involves setting up a separate ATPS spooler 
that returns the font list query expected by PageMaker v4.2. A new 
font list file, PM42.FNT, is provided to assist you with this process. 
Here is an example of a configuration:

"Marketing LW:M-Zone" -o "Marketing Q (all others)" -q 
MARKETING_Q -o "Marketing Q (PM 4.2 only)" -q MARKETING_Q -f 
PM42 -wb

These two configuration lines specify that the MARKETING_Q queue, 
is to be serviced by the printer <Marketing LW:LaserWriter@M-
Zone>. The queue is advertised by two spoolers, one visible in the 
Chooser as "Marketing Q (all others)" and one visible as "Marketing Q 
(PM 4.2 only)." *Only* when printing from PageMaker 4.2, users 
should select the latter spooler. When printing from *all* other 
applications, including earlier versions of PageMaker, users should 
select the former spooler. Choosing the wrong spooler for the 
application from which the user is printing will result in slower 
printing performance and possible substitution of fonts by 
bitmapped images in the final printed output.

The file PM42.FNT should suffice as a default font list for Apple 
LaserWriters (except the original LaserWriter) or HP LaserJets. To 
create customized font lists (for printers with downloaded fonts or 
third-party printers) that conform to PageMaker 4.2 syntax 
requirements, follow the instructions in the Chapter 8 of the NetWare 
for Macintosh Installation and Maintenance manual, but precede 
each font name in the list with a forward slash (/). Refer to 
PM42.FNT as an example. 


PROBLEM #2: Independent of Problem #1 discussed above, Aldus 
PageMaker for Macintosh users experience slow printing 
performance or frequent "VMError" PostScript exceptions when 
printing via NetWare for Macintosh, particularly when using fonts 
not available on the printer.

CAUSE: PageMaker does not deal well with spoolers like the ones in 
NetWare for Macintosh 3.12, which do not report the available free 
memory in the printer.

SOLUTION: If you are experiencing this problem, you may wish to 
consider printing directly to the target printer. The problem has been 
reported to Aldus so they can address it in a future release. 


PROBLEM #3: When printing to spoolers for the HP DeskWriter 
family, the HP PaintWriter XL, and the HP PaintJet XL300, Macintosh 
clients whose printing requests are rejected (because queue security 
is enabled and they are not logged into the server or are not a queue 
user) hang or crash.

CAUSE: This problem is caused by anomalies in how the Macintosh 
drivers for these printers react to having their printing session 
terminated.

SOLUTION: Do not use the queue security option with spoolers for 
these printers if it is important to not adversely affect Macintosh 
clients. The problem has been reported to Hewlett Packard so that 
their future drivers can be made more robust.


PROBLEM #4: When printing to an ATPS spooler using the Adobe 
Macintosh printer driver (also known as PSPrinter, LaserWriter 8.0, 
or PostScript Level 2 driver), the client Macintosh crashes or hangs, 
and displays a message like this one:

"Creating Screen Font: Helvetica"

CAUSE: Our testing with a pre-release version of the driver shows 
that it sometimes crashes when downloading some fonts that are 
seldom downloaded because they are widely available on printers; 
one such font is Helvetica-Oblique. Because NetWare for Macintosh 
3.12 does not fully support the Adobe Macintosh driver, *all* fonts 
are downloaded with each print job.

SOLUTION: Avoid using fonts that cause this problem, or go back to 
using the standard LaserWriter driver.


PROBLEM #5: When printing to an AppleTalk printer from Windows, 
jobs that should be returned by ATPS to the queue (because the keep 
option is enabled, printer accounting is enabled, or an error in 
contacting the printer occurs) are discarded rather than kept in the 
queue.

CAUSE: This problem is caused by an anomaly in NetWare support 
submits print jobs under Windows.

SOLUTION: Make sure that the latest version of NETWARE.DRV -- 
v3.01 -- is installed on your Windows workstation. This version of 
the file is included in NetWare 3.12.


****************************************************

DISCLAIMER

Novell, Inc. makes no representations or warranties with respect to 
this update, and specifically disclaims any express or implied 
warranties of merchantability, title, or fitness for a particular 
purpose. Distribution of this update is forbidden without express 
written consent of Novell, Inc. 

Novell reserves the right to discontinue distribution of this update. 
Novell will not be responsible for any data loss that may result from 
implementing this update. Novell strongly recommends a backup be 
made before any update is implemented. Technical support for this 
update is provided at the discretion of Novell. 


APPLE WARRANTY DISCLAIMER

Apple Computer, Inc. ("Apple") makes no warranties, express or 
implied, including without limitation the implied warranties of 
merchantability and fitness for a particular purpose, regarding the 
AppleTalk software. Apple does not warrant, guarantee or make any 
representations regarding the use or the results of the use of the 
AppleTalk software in terms of its correctness, accuracy, reliability, 
currentness or otherwise. The entire risk as to the results and 
performance of the AppleTalk software is assumed by you. The 
exclusion of implied warranties is not permitted in some states. The 
above exclusion may not apply to you.

In no event will Apple, its directors, officers, employees or agents be 
liable to you for any consequential, incidental or indirect damages 
(including damages for loss of business profits, business interruption, 
loss of business information, and the like) arising out of the use or 
inability to use the AppleTalk software even if Apple has the 
exclusion or limitation of liability for consequential or incidental 
damages, any cause whatsoever, and regardless of the form of the 
action (whether in contract, tort (including negligence), product 
liability or otherwise), will be limited to $50. 

