PC Plus SuperCD 12/12_pcplus_supercd.iso/COMUN/NWMAC/NLS/4/README.MAC

Text File | 1994-09-22 | 17.4 KB | 412 lines

ReadMe File
NetWare for Macintosh 4 v4.10
(C) Copyright 1994 Novell, Inc. All rights reserved worldwide.


Welcome to the latest release of NetWare for Macintosh. This version runs
only with NetWare 4 v4.1. NetWare 4 v4.1 includes the unlimited user
version of NetWare for Macintosh.

This readme file contains two sections. The first section covers NetWare
for Macintosh client software, and the second section covers NetWare for
Macintosh server software (NLMs). Each section addresses known
problems, and solutions where available.


CLIENT NOTES

NetWare UAM v4.00

PROBLEM #1: On a multiple script system, a long user name that requires
more than one line for display in the login dialog can line-break at blanks.

SOLUTION: None, but be aware that a blank in a user name could be
"hidden" by a line break.


MacNCP v1.0

PROBLEM #1: In Systems before 7.1, MacNCP does not work correctly with
the Virtual Memory feature in the Memory Control Panel turned on or with
System Extensions that add Virtual Memory (such as RamDoubler). In this
case, MacNCP will not load, and a message will be displayed at startup.

SOLUTION: Either turn off Virtual Memory or upgrade the Macintosh to
System 7.1.

PROBLEM #2: If MacIPX autoconfigures itself to an incorrect Ethernet or
Token Ring frame type, MacNCP will be unable to see any IPX services on
the network.

SOLUTION: Configure MacIPX explicitly to use the correct frame type.

PROBLEM #3: Network address restrictions for Macintosh Clients vary
according to the login method used by the Macintosh.

SOLUTION: For Macintosh clients that log in using Directory Services, use
the IPX address when you configure the network address restriction. If the
user logs in using Bindery Services, then the AppleTalk address is used for
network address restrictions.


~NetWare Aliases 1.0

PROBLEM #1: If ~NetWare Aliases is not installed on a Macintosh
workstation and an alias created by ~NetWare Aliases is used on that
workstation, the alias may be converted to a standard System 7 alias. An
alias converted in this manner may not work if the server to which it
points requires the NetWare UAM, even after~NetWare Aliases has been
installed.

SOLUTION: Delete the alias and recreate it after ~NetWare Aliases is
installed on the Macintosh.


MacIPX v1.2

PROBLEM #1: MacIPX may display an error message containing the error
code -94 when trying to use the Ethernet 802.3 frame type with certain
Ethernet adapters.

SOLUTION: Install AppleTalk version 58 or later on your Macintosh. To
obtain AppleTalk version 58 or later, contact your Ethernet adapter
vendor. You can also obtain AppleTalk from Apple's Network Software
Installer, version 1.3 or later.

PROBLEM #2: Some third-party applications use their own IPX protocol
stacks, and do not use MacIPX. MacIPX may not function properly in their
environments, depending on how MacIPX is configured.

SOLUTION: Contact the application vendor and request a version of the
application that works with MacIPX. If none is available, you can configure
MacIPX to use a different network interface setup from the network
interface setup used by the other IPX protocol stack. For example, if the
application's IPX protocol stack is using the Ethernet 802.3 frame type,
you can configure MacIPX to use a different frame type such as 802.2. If
this solution is impractica; in your situation, you can configure MacIPX to
use the LocalTalk network interface rather than the interface in use by
the other IPX stack (such as Ethernet). However, this solution requires you
to install and configure a MacIPX gateway somewhere on your network.
Instructions for MacIPX gateway installation and configuration are located
in the NetWare Operating System documentation.

PROBLEM #3: After copying the MacIPX Preferences file from one
Macintosh to a second Macintosh, the MacIPX Control Panel on the second
Macintosh does not reflect the same settings from the first Macintosh.

SOLUTION: After copying the MacIPX Preferences file from one Macintosh
to a second Macintosh, you must restart the second Macintosh before using
the MacIPX Control Panel on the second Macintosh reflects the MacIPX
settings from the first Macintosh.


SERVER NOTES

PINSTALL.NLM and ATCONFIG.NLM

PROBLEM #1: Removing a previous version of NetWare for Macintosh 4
(such as v4.01) from the NetWare server installation program may delete
needed files.

CAUSE: The NetWare for Macintosh 4 v4.1 product no longer contains the
AppleTalk protocol stack; the AppleTalk stack is now shipped as part of
the NetWare 4.1 operating system. If NetWare for Macintosh 4.01 is
installed on your NetWare v4.01 server and you are upgrading to version
4.1, and if you try to delete the NetWare for Macintosh 4.01 product, the
new files are deleted because they are assumed to be part of the NetWare
for Macintosh 4.01 product.

SOLUTION: *DO NOT* remove NetWare for Macintosh v4.01 from the
NetWare server installation program. Install NetWare for Macintosh 4 v4.1
over the current installation as an upgrade. The NetWare for Macintosh
installation program will carry out the upgrade so that the files are not
deleted.

PROBLEM #2: When you configure the stack in the NetWare for Macintosh
Configuration window before you configure the file or print services,
AppleTalk does not bind when it is loaded automatically.

CAUSE: This results from the program design. The installation program
does not automatically bind AppleTalk because the user should be aware of
any problems encountered when the console "initialize system" command
is executed.

SOLUTION: Refer to the AppleTalk for NetWare Reference Guide for
instructions on configuring and binding the stack before configuring the
file or print services.


AFP.NLM

PROBLEM #1: You cannot back up the Desktop database files
"Desktop.AFP\appl.btv" and "Desktop.AFP\icon.btv."

CAUSE: AFP.NLM normally has these files open while running.

SOLUTION: You can always rebuild the Desktop database using
AFPCON.NLM, so there is no need to back up the files. If a catastrophic
failure requires restoring a large number of files on a server volume,
rebuild the desktop database using AFPCON after the restore is complete.

PROBLEM #2: Administrators may not be able to remove the directory tree
from a scanned Macintosh CD-ROM when the CD-ROM files are no longer
required.

CAUSE: The root of the scanned CD-ROM is flagged "invisible" on the
NetWare volume.

SOLUTION: To delete the entire tree and remove the CD from the Chooser
volume list, clear the Hidden, System, RenameInhibit, and DeleteInhibit
flags on the CD-ROM root using NETADMIN from a DOS workstation (or
SYSCON if you are logged in to a NetWare 3 server). The root of the CD-ROM
can be found in the HFSCDCON.NLM Disc Status screen in the Disc Root Path
field. Next, make sure that no users have the CD volume mounted,
preferably by disabling the pseudo-volume in the Volume menu in AFPCON.
Then, mount the NetWare volume from a Macintosh and drag the folder that
corresponds to the Disc Root to the Trash. You should be able to delete all
the CD-ROM files from the pseudo-volume in this way.

PROBLEM #3: Objects created in NetWare Directory Services that are of
the type "AFPServer" have no effect on NetWare for Macintosh servers.

CAUSE: NetWare for Macintosh 4 v4.1 does not use these Directory
Services objects.

PROBLEM #4: Locked files on a NetWare volume cannot be dragged to the
Trash from a Macintosh.

CAUSE: This problem is caused by an anomaly in AFP.NLM.

SOLUTION: You must unlock the file first, using the Get Info command
in the Finder, before the file can be deleted.

PROBLEM #5: "Btrieve not accessible" messages appear.

CAUSE: AFP autoloads BTRIEVE.NLM, which asks for a certain amount of
cache (configurable) when it begins running. If the cache is unavailable,
BTRIEVE stays loaded but does not accept requests from AFP. BTRIEVE
sends a console message at load time indicating that this is the problem.

SOLUTION: You can choose any of these solutions:

1. Reconfigure BTRIEVE to use less cache memory; then, unload and reload
BTRIEVE.

2. Your cache memory may be fragmented if you have been loading and
unloading other NLMs; it may appear that you have plenty of memory, but
BTRIEVE cannot get an adequately-sized contiguous piece of memory.
Reboot the server to free the required memory.

3. Shutdown the Desktop database for each Volume using AFPCON. AFP
no longer makes BTRIEVE calls, though BTRIEVE.NLM is loaded.


PROBLEM #6: When the Find option is used on a Macintosh running System
7.5 to search for items located on NetWare for Macintosh volumes, the list
of "found" items is unstable. The first item on the list will be grayed out,
followed by the remaining items, which are selectable. If you select one
of the items, a message is generated: "The item <file name> is missing and
was probably deleted. Other items may be affected; checking them now."
When you select the OK button, the remaining items in the "found" list will
become grayed out.

CAUSE: The Find feature included in the 7.5 operating system expects files
to use file reference ids, which many third party vendors, including
NetWare, do not use.

SOLUTION: As an immediate workaround, hold down the <Shift> key as you
select Find from the File menu. This enables the old Find option from,
previous versions of the Macintosh System software. Apple is currently
working on a solution.


AFPCON.NLM

PROBLEM #1: AFPCON changes are not saved.

CAUSE: AFPCON cannot save its changes if the SYS:SYSTEM/GLOBDATA.AFP
file is set to Read Only.

SOLUTION: Do not set the GLOBDATA.AFP file to Read Only.


HFSCD.NLM and HFSCDCON.NLM

PROBLEM #1: Discs inserted into a CD-ROM drive do not appear in the
HFSCDCON.NLM disc list.

CAUSE: The CDNASPI.DSK and PS2SCSI.DSK drivers have problems
recognizing when a new disc is inserted into a CD-ROM drive.

SOLUTION: Once the new disc is in the drive, display the HFSCDCON disc
list and press <Ins> several times to "kick-start" the driver. If this
strategy proves unsuccessful, unload and reload the problem driver.

PROBLEM #2: EISA or MicroChannel machines with more than 16MB of
memory may ABEND with "invalid opcode" errors.

CAUSE: Some SCSI device drivers, including CD-ROM device drivers, need
to be informed that they are running on servers with more than 16MB.
Otherwise, they may inadvertently corrupt server memory and cause
server failure.

SOLUTION: See the SCSI device driver reference manual for correct
installation on EISA and MicroChannel servers.

PROBLEM #3:  SFT III server abends when loading ASPICD.DSK. Using
Adaptec 2742 SCSI Adapter and loading AIC7770.DSK on primary and
secondary I/O engines, loading ASPICD.DSK on top of the SCSI Driver
causes abend.

CAUSE: This problem occurs when attempting to load all the driver
modules before loading HFSCD.NLM on SFT III servers.

SOLUTION: None at present. Adaptec has been informed of the need to
make ASPICD.DSK compatible with SFT III OS.

PROBLEM #4: The SYS volume gets dismounted when multiple CD players
are on the same SCSI bus as the internal hard drive (SYS). Accessing
multiple CD players can cause the SYS volume to dismount, and
consequently dismounts all other NetWare volumes.

CAUSE: Accessing multiple CDs over the same SCSI channel as the SYS
volume dismounts the volume because of the load over the SCSI bus.

SOLUTION: Do not include the SYS volume in a SCSI bus configuration if
multiple CDs are being accessed. This problem will not occur if the SYS
volume is separated from the controller adapter that is used for the
external CD-ROM players.


PRINTING PROBLEMS WITH THIRD-PARTY SOFTWARE AND DEVICES

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: 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" advanced PostScript
option for spoolers that will be printed to from PageMaker 4.2a unless you
use a custom font list as discussed under the third strategy.

PROBLEM #2: 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 may 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 not to affect Macintosh clients adversely. The
problem has been reported to HP so their future drivers can be made more
robust.

PROBLEM #3: When printing to an ATPS spooler using the Adobe Macintosh
printer driver (PSPrinter 8.0, or LaserWriter 8.0), Macintosh clients crash
or hang, perhaps displaying a message like the following:

         "Creating Screen Font: Helvetica"

CAUSE: Our testing with the driver shows that it sometimes crashes when
downloading some common fonts that are seldom downloaded because
they are widely available on printers, such as Helvetica-Oblique.

SOLUTION: Upgrade to LaserWriter/PSPrinter 8.1 or later.

PROBLEM #4: When printing to an ATPS spooler using QuickDraw GX, the
messages

        "Dictionary file <ATPS DIRECTORY>\App710.PRS not present."

and

        "Discarded unwanted ExitServer data."

are generated by ATPS with each spooled Macintosh job. In addition,
the PostScript GX printing via ATPS may be unreliable in environments
where pre-7.0 Laser Prep versions are in use.

CAUSE: QuickDraw GX v1.0.1 does not follow the Laser Prep management
conventions used by earlier versions of the LaserWriter driver.

SOLUTION: The spooling messages are informational and may safely be
ignored. Alternately, they can be eliminated by a printing a single job to
the server using LaserWriter 7.x. If unreliable LaserWriter GX printing is
detected, make sure all Macintosh users of the printer use LaserWriter 7.x
or higher.

PROBLEM #5: ATPS printer servers and ATXRP printers intermittently hang
while communicating with the HP PaintJet XL300 PS printer, particularly
if ATPS logging or accounting are in use.

CAUSE: The PaintJet XL300 has problems responding to the PAP end-of-
file indication.

SOLUTION: A hung session can be terminated by power-cycling the printer,
or by unloading and reloading ATPS or ATXRP. Do not enable ATPS logging
or accounting for use with the HP PaintJet XL300 PS. If occasional hangs
cannot be tolerated, consider using another printer.

PROBLEM #6: When logging or accounting are in use, ATPS may be
consistently unable to determine accurately the page count of some
printers. The printer log always has a number too low (including zero) or
"Unknown" for the "Total Pages" field of print job entries.

CAUSE: Not all PostScript-compatible printers properly support the
"pagecount" operator that ATPS uses to obtain page counts from printers
defined as PostScript devices. Non-Adobe PostScript implementations
vary in this regard. Usually, the problem is that the value is not promptly
updated, so that, for instance, ATPS reports that a job consumed zero
pages when it actually consumed one or two.

SOLUTION: If accurate page counts are important to you (for instance, if
you use ATPS printer accounting to charge users for printing), monitor the
page counts obtained from the printer when it is first set up for use with
ATPS. If the results are inaccurate, consider using another model of
printer. If the printer supports PJL page counting, make sure the printer
server's configured model reflects this. ATPS can obtain more accurate
page counts from the HP LaserJet 4Si using PJL than it can via PostScript,
for instance.


KNOWN PROBLEMS WITH 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 problem occurs with any version of QuickMail for Macintosh
(2.x - 2.6) when the client accesses a NetWare volume using NetWare
for Macintosh 4.10. QuickMail MHS for Macintosh 1.0 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
[phone] for more information.


LOCALTALK CARDS AND DRIVERS

The DL/2 or DL2000 LocalTalk cards from Dayna Communications, Inc. are
the only LocalTalk cards that work with NetWare for Macintosh. These
cards and drivers are not certified by Novell in the NetWare 4.1
environment. You can obtain LocalTalk cards and drivers by contacting
Dayna Communications:

Dayna Communications, Inc.
Sorenson Research Park
849 W Levoy Dr.
Salt Lake City, Utah 84123-2544
Phone: [phone]
Fax: [phone]
BBS: 801-269-7398

Please contact Dayna Communications regarding technical support issues.