CORE OPERATING SYSTEM

Q:   The file server (containing an IBM Token-Ring 16/4 Adapter/2
     and 16MB of RAM) ABEND's with a GPPE when loading TOKENBM.LAN. 
     How can I fix this?

A:   Add the "Set Auto Register Memory Above 16 Meg = OFF"
     parameter to the STARTUP.NCF file and reboot the file server. 
     This will return the message "384K of memory will not be
     used," which is only an informative message.  This message
     means that the file server had 384KB of memory addressed above
     16MB; however, it will no longer be used.

Q:   Recently, my older, almost full ESDI drives have been
     deactivating.  Why does this happen, and how can it be
     resolved?

A:   This problem has been seen with older, almost full ESDI
     devices, because the device is not responding quickly enough
     to error conditions.  The ISADISK driver has been changed to
     allow for a longer waiting period for the drive to respond. 
     The driver is contained in ISA311.ZIP found on NetWire NOVLIB
     04.

Q:   What is the difference between Private and Global VDMs?  How
     do I set them up?

A:   Global VDMs allow DOS to share the OS/2 login connection. 
     Drive mappings and port captures are shared, and any changes
     to one session affects the other session.
     
     Private VDMs allow DOS to have a separate login from the OS/2
     login.  This allows each session to have its own mappings,
     port capturing, etc.  Each VDM allows for only one DOS login,
     so if more than one DOS login is needed, multiple Private VDMs
     must be used.
     
     If more than eight concurrent sessions (OS/2 and DOS combined)
     are needed, the modifications listed below need to be made to
     the NET.CFG.

          NETWARE REQUESTER SESSIONS <number>

               (default=8, replace <number> with a value between 8
               and 20)

          PROTOCOL STACK IPX SOCKETS <number>

               (default=32, replace <number> with a value between
               32 and 128; three sockets per added session above
               eight)

     To set up VDMs, make the changes listed below in the DOS
     SESSION NOTEBOOK.

     PRIVATE SUPPORT

          DOS_LASTDRIVE            E
          NETWARE_RESOURCES        PRIVATE
          VIPX_ENABLED             ON
     
          When opening the session run NETX.EXE, found in the
          NETWARE subdirectory (a special NETX designed for use
          with the VDM), move to the F: drive and log in to the
          network.

     GLOBAL SUPPORT

          DOS_LASTDRIVE            Z
          NETWARE_RESOURCES        GLOBAL
          VIPX_ENABLED             ON

          Do not attempt to log in from this session.  The login
          should be made from the OS/2 session or desktop, or from
          NWTOOLS.

     NO NETWARE SUPPORT (used by applications with no network
     awareness, such as single user)

          DOS_LASTDRIVE            E (if using Private VDMs)
                              or
                                   Z (if using Global VDMs)

          NETWARE_RESOURCES        NONE
          VIPX_ENABLED             OFF

     Other properties in the DOS SESSION NOTEBOOK would be used to
     fine tune the DOS session.  Refer to the OS/2 documentation
     and Chapter 8 of the NetWare Requester for OS/2 v2.0 manual
     for more details on using the DOS SESSIONS NOTEBOOK.
     
Q:   What can I do if RPRINTER loses its connection or hangs when
     running under Windows?

A:   Use VIPX.386 found in WINUP7.ZIP on NetWire under the NOVFILES
     forum to fix this problem.

Q:   MS-DOS 6.00 does not work with the new NETX v3.32.  How can I
     fix this?

A:   The two ways to resolve this issue are described below:

     1.   Type the following statement at the command line:

               setver <path>\netx.exe /D

          This statement removes NETX from the SETVER table.

     2.   Do not load SETVER.EXE in the CONFIG.SYS.

          WARNING:  This prevents any other programs
          from using the SETVER utility.

Q:   How can trustees and bindery information be transferred from
     one server to another?

A:   Use NBACKUP to complete the steps below:

     1.   Select "Backup By Directory" from the "Backup Menu."

     2.   Change "Backup Binderies" and "Backup Trustees" to Yes.

     3.   Enter *.* and * for files to exclude.

     4.   Leave all other options at default.

     To restore this information to another server, make sure the
     server you are restoring to has the same server name as the
     server that was backed up.  Then restore as usual.

Q:   DOS 6.0 is seen as DOS 5.0 when I log in to the network.  How
     can I fix this?

A:   Delete NETX.EXE from the SETVER table by issuing "SETVER
     <path>\NETX.EXE /D" at the command line.

Q:   When the server is mounting the SYS: volume, the message
     "Problem with file q_xxxx.srv:  TTS file was not changed" is
     displayed.  What does this mean, and how can I prevent it?

A:   This message is informational only and will not appear after
     a new job is sent to that queue.  The XXXX corresponds to the
     first four characters of the print queue ID, which can be
     obtained from PCONSOLE, "Print Queue Information", "Queue
     Name", "Print Queue ID".  This message appears when a server
     is brought down abnormally, because Transition Tracking System
     (TTS) may need to back out the transactions in each queue that
     was in the process of being executed when the server went
     down.

Q:   While running Intel's LANPROTECT.NLM 1.53, the times and dates
     of files are being changed randomly.  This version of the NLM
     was supposed to fix this; however, I am still having problems. 
     How can I fix this?

A:   LANPROTECT.NLM 1.55 resolves this problem.  This file is
     available on Intel's BBS 503-645-6275.  Choose the following
     menu items to download the UPGRADE.EXE file: "download,"
     "network," "lan management," then "lanprotect."

Q:   The error "NLM could not be found" is returned when loading an
     NLM from the hard drive of an IBM Model 95 with IBM SCSI
     controllers.  Then, after shutting down the server and typing
     "EXIT" to return to DOS, the error "Invalid command.com" is
     returned.  Why is this happening?

A:   If the SCSI ID for the bootable device is set to something
     other than 6, what IBM expects, these problems will occur
     after NetWare is loaded.  To resolve this problem, physically
     set the SCSI DEVICE (containing the DOS bootable partition) to
     SCSI ID 6.  Then, run the Reference Disk to ensure that the
     software configuration for the SCSI channel reflects this
     change.

Q:   When installing VLMs from WSDOS1.EXE, WSWIN1.EXE, and
     WSDRV1.EXE, I get errors related to missing MSG files.  How
     can I fix this?

A:   Use the syntax "C:\WSDOS1 -d" when executing the self
     extracting files.  When executing these files, the information
     below will be displayed:

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

     To be sure all files are extracted use the "-d" option. (e.g.
     <Filename> -d)
     
     !!! By extracting the FILES, You AGREE to these TERMS AND
     CONDITIONS....
     **************************************************************
     Do you want to extract these files now (y/N)?                
       
     At this point, a user can answer "N" and start the process
     again.
 
Q:   After upgrading to VLMs, I cannot run the 4.0 DOS utilities
     (such as NETADMIN.EXE or NETUSER.EXE)  How can I fix this?

A:   Increase the FILES= statement in the CONFIG.SYS to 50.

     It was common, previous to VLMs, to set FILES in the
     CONFIG.SYS low and FILE HANDLES in the NET.CFG high.  The FILE
     HANDLES statement is no longer valid with the VLMs, so FILES
     need to be increased for the DOS utilities to load.

     Note:  The International UNICODE files are new to the DOS and
     Windows utilities.  These extra files require FILE HANDLES to
     be increased.

Q:   VLMs and Windows 4.0 support drivers were just installed on a
     workstation.  All other workstation's not yet updated receive
     a number of error messages causing Windows (running as a
     Network version) not to load.

A:   To work around this problem, complete the steps below:

     1.   Create a subdirectory under the network Windows
          directory.

     2.   Copy VIPX.386 and VNETWARE.386 from WINUP7.ZIP (NetWire
          under NOVFILES forum) into the above created directory.

     3.   Edit each workstation's SYSTEM.INI (386 Enh Section) to
          reflect the new path for VNETWARE.386, VIPX.386 and
          NETWARE.DRV.  For example, if the subdirectory was named
          NEW, the example below shows the syntax to add the path
          for the new files to the 386 Enhanced section of the
          SYSTEM.INI:

               network=*f:\windows\new\vnetbios,f:\window\new\
               vnetware.386,f:\windows\new\vipx.386

          This allows the NetWare v3.11 virtual drivers to be used
          instead of the NetWare 4.0 drivers.

Q:   Can I upgrade from NetWare 4.0 Beta to NetWare 4.0 Released?

A:   No.

Q:   The following error messages may occur during a 4.0 CD-ROM
     installation:

          "Error loading NETMAIN.IL$"

          "Cannot find file NETMAIN.IL$"

          "Invalid version of NETMAIN.IL$"

     What causes this, and how can I fix it?

A:   This problem occurs when the CD-ROM and the drive where
     NetWare 4.0 is being installed are attached to the same
     controller.  When the NetWare disk driver is loaded, the DOS
     driver is overwritten and the CD-ROM connection is lost.  The
     NetWare 4.0 Release Notes (found under the
     \DOC\ENGLISH\NW40\README directory on the 4.0 CD-ROM) describe
     six ways to work around this problem.

MACINTOSH

Q:   Recently, the name of a NetWare v3.11 file server (with
     NetWare for Macintosh v3.x) was changed.  When Macintosh users
     log in and mount volume SYS:, the old file server name is
     still displayed before the volume name (such as OLDNAME.SYS).
     What causes this and how can I fix it?

A:   VOLNAMES.AFP, a hidden file in SYS:SYSTEM, contains the volume
     names used by NetWare for Macintosh v3.x.  VOLNAMES.AFP,
     created by the AFP module, contains the statement

          SYS=server-name.SYS

     where server-name is the NetWare server name.

     To correct the problem, complete the following steps 

     1.   Log in to the file server as Supervisor.

     2.   Change to the SYS:SYSTEM directory.

     3.   Unhide the file by typing FLAG VOLNAMES.AFP -H.

     4.   Edit VOLNAMES.AFP with an ASCII text editor.

     5.   Replace the old server-name with the new server-name and
          save the file.

     6.   Hide the file by typing FLAG VOLNAMES.AFP H

     7.   Unload and reload AFP at the console prompt.

Q:   Macintosh Name Space Support was removed from a NetWare v3.11
     volume with VREPAIR and then added back to the same volume. 
     Now the Macintosh users cannot access their files by
     double-clicking them.  How can I fix this?

A:   Removing Macintosh Name Space Support deletes Macintosh
     specific attributes (File Type, Creator Type, longer Macintosh
     file name, and the resource fork) of the files that reside on
     the volume.

     When Macintosh Name Space is removed, these attributes can
     only be recovered by restoring the files from tape backup.

Q:   When a document containing Palatino bold is printed to a
     NetWare for Macintosh v3.x queue, it prints Palatino plain
     text.  The same document prints correctly if printed directly
     to the LaserWriter.  What causes this and how can I fix it?

A:   This happens when the PRNTR#.FNT, located in SYS:SYSTEM\ATPS,
     does not contain the printer's correct font list information. 
     To update this information complete the following steps:

     1.   At the console prompt, execute ATPSQUERY PRINTER_NAME.

     2.   Unload ATPS, delete the PRNTR#.FNT files, and reload
          ATPS.

     If you are using a non-AppleTalk PostScript printer with
     NetWare for Macintosh v3.01 or later, complete the following
     steps to correct the problem:

     1.   Change to the SYS:PUBLIC directory.

     2.   Use NPRINT to send the file named FONTLIST.PS to the
          queue.  FONTLIST.PS is a PostScript file that instructs
          the printer to print out its list of fonts in the correct
          format.

     3.   Use a text editor to create a font file, and type in the
          list of the printer's fonts as they appear on the printed
          output.

          *    The name of the file must use the ".FNT" extension.
          *    The file must reside in SYS:SYSTEM\NW-MAC\FONTS.
          *    The last item in the list of fonts must be a single
               asterisk (*).

     4.   On the line specifying this queue in the ATPS.CFG file,
          you must add a -f <fontlist filename (not including
          filename extension)> parameter.  For example, if you
          named your fontlist file "FONTS.FNT," the statement below
          would be included on the appropriate ATPS.CFG line:

               -f fonts

Q:   With NetWare for Macintosh v3.x, how do I know which zone my
     NetWare file server will be advertised in?  Which zone do my
     Macintosh workstation's reside in?

A:   The file server will always be advertised in the first
     internal zone (the first zone listed in the LOAD APPLETLK
     statement in the AUTOEXEC.NCF).

     AppleTalk entities can only reside in one zone at a time. 
     Macintosh workstation's can only reside in a zone associated
     with the cable segment to which they are physically connected. 
     These zones are defined in the BIND APPLETLK statement in the
     AUTOEXEC.NCF file.  

     A Phase 1 network has only one zone on the cable segment.  A
     Macintosh workstation can only reside in that zone.

     A Phase 2 network, can have more than one zone on the cable
     segment.  A zone is selected by accessing the CONTROL PANEL, 
     selecting NETWORK, and double-clicking on the Phase 2 driver. 
     This displays a list of all zones associated with the cable
     segment to which the Macintosh workstation is attached;
     however, only one of these zones may be selected.

Q:   What LocalTalk network boards are supported and certified with
     NetWare v3.11 and NetWare for Macintosh v3.x?

A:   The Dayna DL2000 and DL/2.

SUNNYVALE

Q:   Can I use a 486 machine with Access Server?

A:   Yes.  Many 486 machines have been tested and certified.  End
     users have also reported successful installations on 486/50
     and 486/66 machines.

Q:   Can the Access Server be installed on a machine with a
     built-in Super VGA?

A:   No.  Access Server does not support Super VGA.  Either disable
     the Super VGA mode or substitute another video adapter.

Q:   After I started running NACS 3 (or NetWare for SAA v1.3), my
     NetWare v3.11 server occasionally abends.  Is there a
     connection?

A:   Yes.  The SPXFIX NLM, required for both NACS 3 and NetWare for
     SAA v1.3, which ships with the two products, may cause server
     abends.  SPXFIX2, contained in STRTLI.ZIP found on NetWire
     NOVLIB 9, resolves the issue.  STRTLI.ZIP also contains other
     files that need to be used with SPXFIX2.

Q:   I am using the Novell Synchronous Adapter for SAA with NetWare
     for SAA v1.3.  When R3SDLC is loaded, the following message is
     displayed:

          DLCI Error: Unable to Attach Logical Board.

     What am I doing wrong?

A:   NetWare for SAA v1.3 requires the use of a logical board name. 
     When a host connection is configured in CSCON, one of the
     parameters (for Ethernet, Token Ring, and SDLC) is the Logical
     Adapter Name.  This Logical Adapter Name should match the
     NAME= statement in the "LOAD <driver>" statement in the
     AUTOEXEC.NCF.  For example, if the LOAD statement in the
     AUTOEXEC.NCF is "LOAD R3SDLC NAME=BOARD_NAME," then BOARD_NAME
     would be entered in CSCON as the Logical Adapter Name.

Q:   I am trying to use the LU6.2 API that ships with the NetWare
     3270 LAN Workstation; however, am confused about what APIs are
     available.  What is the difference between CPI-C and APPC?

A:   NetWare 3270 Workstation's and NetWare for SAA implement two
     LU6.2 API interfaces: CPI-C and APPC.  Both of these APIs have
     been implemented on NetWare for SAA and WSLAN (both DOS and
     Windows).

     NetWare for SAA, supports both API interfaces in PU2.0 and
     PU2.1 profiles.

     Which API to use and where to load it depends on the
     Application Program Interface (API) your application is
     written to and where that application is run.  For example, if
     the application is written for CPI-C and runs on DOS, then the
     CPI-C interface needs to be loaded under DOS (CPIC_SAA.NLM is
     not required).

     The CPI-C API runs on top of the APPC/LU6.2 protocol boundary. 
     Therefore, to run a CPI-C application, the APPC/LU6.2
     interface is the required.

     To set up the CPI-C interface, run the SIUTIL.EXE to configure
     a Side Information File.  This file is needed by the CPI-C
     Application Subsystem to negotiate an LU6.2 session.

Q:   I want to use the OS/2 2.0 Communication Manager to provide
     3270 terminal emulation to my OS/2 2.0 workstation's.  I have
     heard that NetWare for SAA v1.3 can be configured to support
     these clients as downstream PUs (DSPUs).  How is this
     configured?

A:   Currently, only downstream PUs with the following topologies
     are supported: LLC8022 over Token Ring, Ethernet, and QLLC
     over X.25.  For downstream PU support, only one card of the
     three listed above can be used.

     One Netware for SAA profile performs all SNA communications
     through one adapter only.  The upstream system and any
     downstream PUs to be supported by this profile must be
     accessible by NetWare for SAA through that one adapter. 
     Boards and protocols cannot be mixed.

     For example, if NetWare for SAA is attached to the upstream
     system through QLLC, all downstream PUs may only be attached
     through QLLC.  NetWare for SAA also must be able to
     communicate with both the upstream system and downstream PUs
     using the same X.25 adapter.

     This information is discussed on pages 4 and 5 in the SAA 1.3
     Planning Guide.

PRODUCT INFORMATION

Q:   Will LAN WorkPlace for DOS do IP Tunneling through PPP to an
     IP router and on to a NetWare v3.11 server?

A:   Yes.  When using ODI, however, the first LAN driver needs to
     bind to PPP and the second to IP Tunneling.  Burstmode is
     recommended for this configuration.

Q:   What is the maximum password length in NetWare v3.11?

A:   127 characters.

Q:   I cannot upgrade from Link/X.25 to WAN/Links.  Why?

A:   The boards used with Link/X.25 do not work with WAN/Links.

Q:   Can Multi-drop modems be used with WAN/Links?

A:   No.  Multi-drop modems use multi-drop lines, which is not
     supported in WAN/Links.

Q:   Does NetWare SFT III v3.11 support NetWare Global MHS?

A:   Yes.

Q:   What is the maximum number of volumes that can be mounted with
     NFS Client?

A:   The maximum number of volumes that can be mounted with NFS
     Client is 26.  However, because each volume must be mapped to
     a drive, this maximum is dependent on what is already mapped.

     For example, if A:, B:, and C: drives are mapped to local
     drives, and F:, G:, and H: drives are mapped to network
     drives, 20 drive letters are left.  Therefore, 20 volumes may
     be mounted.

Q:   What Tape Backup units are compatible with DataClub (Classic
     and Elite)?

A:   Anything that is AppleTalk Filing Protocol (AFP) compliant.

Q:   Can a Macintosh user access a plotter on the network?

A:   No.  Drivers are not available to allow a Macintosh user to
     see the plotter.  A plotter must be directly connected to the
     machine for the user to access it.

Q:   Will LAN Workplace for Macintosh v1.3 recognize a Quadra's
     built-in Ethernet card?

A:   Yes.

Q:   In LAN WorkGroup are the user connections concurrent or
     defined?

A:   IP addresses are assigned to the hardware and not to the
     users.  Addresses are assigned in LWGcon and during the first
     login bootP assigns the machine the first available IP
     address.  Each time after the first login, the machine is
     given the same address whenever it requests IP services. 
     Remove the users name from LWGcon when needed to free up the
     address so it can be reassigned by BootP.

Q:   Can a Null Modem be used to connect to a file server running
     Novell's messaging products?

A:   Yes.  During the installation of MHS, Null Modem is an
     available menu option when configuring communications between
     boxes.

Q:   In NetWare v3.11, print job configurations created in PRINTCON
     are stored in each users' mail directory.  Where are these
     print job configurations stored in NetWare 4.0?

A:   This information is stored in the users' object as part of the
     Directory Services database.  A print job configuration can be
     created for an OU container object and will be used by default
     for any user object contained in the OU.

Q:   Has the accounting feature of printing in NetWare 4.0 been
     enhanced to allow for charging a user on a per page printed
     basis?

A:   No.

NETWARE LITE

Q:   Separate copies of NetWare Lite are installed on each
     machine; however, I am still getting a software violation
     message.  Why?

A:   This can be caused by one of two things:

     1.   Additional copies of SERVER.EXE or CLIENT.EXE are located
          outside the NWLITE directory.

     2.   The same copy of NetWare Lite is installed on more than
          one computer.

     This can be resolved by doing the following:

     1.   Type "tree server.exe" from the root to locate additional
          copies of SERVER.EXE on the system.  Repeat this for
          CLIENT.EXE.

          If more than one copy of either SERVER.EXE or CLIENT.EXE
          are found, delete any copies residing outside the NWLITE
          directory.

     2.   If only one copy of each of these files is found, use DOS
          compare to verify unique NetWare Lite copies on each
          machine displaying the error.

          a.   Place the NetWare Lite installation disk in the
               floppy drive.

          b.   Execute the following at the command line for the
               SERVER.EXE file (if the floppy diskette is in the
               A: drive):

                    comp a:\server.exe c:\nwlite\server.exe 

          c.   Repeat Step b for the CLIENT.EXE file.

          If the files are unique, there will be a 4 byte
          difference in the message returned by the compare
          command.  If the files are the same, check the other
          machine by following steps a through c above.  There
          should be a match.  Find a copy that does not match any
          systems, and reinstall that copy on one of the offending
          systems.

Q:   The message "Can't print to LPT1" continues to appear when
     printing.  What should I do?

A:   Apply GETATRIB.PAT from L11U03.ZIP found on NetWire NOVLIB 10.

Q:   A print job was sent to the printer but never printed.  The
     NetWare Lite print queue was also empty.  What should I do?

A:   Apply LPTSTAT.PAT from L11U03.ZIP found on NetWire NOVLIB 10.

Q:   While using a database program, the client machine locks.  Now
     when the program is run I get a "file already open" error. 
     What should I do?

A:   Apply CLOSEFIL.PAT from L11U03.ZIP found on NetWire NOVLIB 10.

Q:   I have printing problems where either the print job does not
     print correctly or my machine locks.  What can I do to resolve
     this problem?

A:   Apply INT28FIX.PAT from L11P03.ZIP and CLPRINTR.PAT from
     L11U03.ZIP found on NetWire NOVLIB 10.

DRDOS

Q:   Is DR DOS 6.0 compatible with QEMM386 and other third-party
     memory managers?

A:   Yes.  DR DOS 6.0 works well QuarterDeck QEMM386, Qualitas
     386MAX and BlueMAX, and Microsoft HIMEM.  Further details and
     examples can be found in the DR DOS 6.0 Optimization and
     Configuration Tips booklet, page 38-40.  This booklet is
     shipped with every package of DR DOS 6.0.

Q:   What commands can you get help on?

A:   All of them.  Type in the command as it would appear on the
     command line, but add a /H or /? after it.  This information
     can also be accessed using an electronic version of the manual
     called DOSbook.  DOSbook can also provide assistance if you
     are not certain of how to configure your system using SETUP
     and batch file commands.

Q:   Can the SuperStor compression driver from DR DOS 6.0 be used
     with other versions of DOS?

A:   No.  A DR DOS 6.0 SuperStor compression driver should not be
     used with other versions of DOS, including DR DOS 5.0, MS-DOS
     5.0, or MS-DOS 6.0.  Drive compression is an integral part of
     DR DOS 6.0, requiring built in special awareness of the host
     operating system.

Q:   Why does the DR DOS FDISK take so much longer than other DOS
     versions to prepare my hard drive?

A:   DR DOS not only tests and prepares the drive for use, but also
     formats the drive.  As with other DOS versions, after using
     the DR DOS FDISK utility on a drive, there is no need to
     FORMAT the drive.

Q:   Can I change the way the DIR command displays a directory
     listing?

A:   Yes.  There are several DR DOS switches that change the
     appearance of the DIR listing.  For example, /2 displays the
     listing in double column format, /P pauses with each full
     screen, and /C instructs DR DOS to use these parameters as the
     defaults.  For example, if the command "DIR /2PC" is used,
     every time a DIR is executed, the DIR listing will display in
     double column format and pause with each full screen.  If the
     "DIR /2PC" statement is added to the AUTOEXEC.BAT file, the
     new DIR options will be set on bootup.

Q:   Why does CHKDSK show PENDING DELETE files after DELPURGE *.*
     is run?

A:   DELPURGE acts only on the current directory if executed
     without additional switches.  To purge all deleted files from
     the current directory and all subdirectories, use the
     following command from the root directory:

          DELPURGE *.* /S