LANSpool V3.50C Package Documentation

          INSTRUCTIONS FOR REPLACING/INSTALLING LANSpool

    This package replaces LANSpool on ICLAS version 1.41
    with ship level LANSpool version 3.50c.

    Use the following steps to upgrade and replace LANSpool
    on your ICLAS network:

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

    B.  Performing the upgrade to the latest LANSpool.

    1) If desired, run the LANSpool removal utility (LSREMOVE) at this
    time.  Use the utility according to LSREMOVE instructions that come
    with the package.  The LSREMOVE program will completely remove all of
    the current LANSpool version without destroying any ICLAS files.  After
    the program has downed the server and completed use steps 2 thru 5 to
    install LANSpool and CLSPRTST.

    2) Boot a workstation using ICLAS.  Login to that workstation as
    ADMIN or SYSOP.

    3) After logging in use one of the following procedures:

       Escape to DOS from ICLAS using the escape sequence.
       Change the current drive to the CD-ROM drive. Run Install.
       When the Patch Update Main Menu appears, select option 3 -
       Selectively Install Updates.  A menu of all patches will appear,
       select Install LANSpool 3.50C Updates and press Enter.  When the
       installation has started you will see a menu with three items,
       select option 1 - Install LANSpool by typing 1 and pressing enter.
       Read the messages and respond to any instructions during
       installation screen.  In order to activate the new LANSpool the
       server must brought down AFTER the installation has completed.
       Installation will be complete when you are returned to the 
       Selectively Install Updates Menu.

    NOTE***NOTE***NOTE***NOTE***NOTE***NOTE***NOTE***NOTE***NOTE***NOTE
    
        After installation you must change the NODE command in the
        AUTOEXEC.BAT for the workstation from "NODE /A" to plain "NODE".

   *********************************************************************
    
    
    After completion remove the diskette from drive A:.  Down the server
    if it is a 286 server to restart the LANSPOOL.VAP or unload and reload
    the LANSPOOL.NLM on a 386 server.

    Replacement of LANSpool is now complete.  If you have used
    the LSREMOVE package you will have to remake all of the previous
    PrintStation assignments.

LANSpool Notes from Intel:

    This is the latest LANSpool Printer Drivers.  They have support
    for Windows 3.0 and 3.1 functionality.

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

    Windows 3.0 and Windows 3.1

    To run Windows 3.0 with Netware, get the latest WINUP?.ZIP file
    from NetWire and install all of the fixes in that package.
    WINUP?.ZIP has Novell's latest code with needed bug fixes for
    NetWare/Windows functionality.  LANSpool need a special device
    driver to function properly with windows when in Enhanced 386
    mode.  The following line must be added to the SYSTEM.INI file:

    DEVICE=VSPLD.386

    This line should go right after the line:

    DEVICE=*VPICD for windows 3.1

    and right after the line:

    DEVICE=VPICDA.386 for windows 3.0

    Examples for each are below.

    Windows 3.0:

    DEVICE=VPICDA.386
    DEVICE=VSPLD.386

    Windows 3.1:

    DEVICE=*VPICD
    DEVICE=VSPLD.386

    The version of the VSPLD is v3.53 To check your version, from a
    DOS Box in windows, run VXD_CHK This will show what version of
    VSPLD is loaded on the machine.  If this causes a PageFault error,
    VSPLD v3.0 is loaded.  Copy VSPLD.386 from this release to the
    window's system directory.

    Example:  COPY VSPLD.386 C:\WINDOWS\SYSTEM

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

    Note:
    DO NOT USE THE "loadhigh" option of NODE when using windows.

    This current release does NOT allow the drivers to be loaded into
    HighDOS memory when running with windows.

    LANSpool has been slowed-down while in Windows.  The LANSpool
    print speed has been capped to 4.5 KBytes per second while in
    windows.  In DOS, no such cap exists and LANSpool can print over
    20 KBytes per second.  The windows cap was placed to keep the
    forground windows response crisp and active.

    Novell has had troubles with their IPXODI.COM files and SPX
    communications.  Since LANSpool uses SPX, ODI drivers still do not
    work reliably with LANSpool.


    LANSpool v3.X Printer Intervention Notification

    LANSpool is designed to alert certain people when a parallel
    printer goes OFF-LINE, OUT-OF-PAPER, or PAPER-JAM.  When any of
    these conditions exists, a 25th line message is sent to all
    QUEUE_OPERATORs for every queue which the printer services.
    Notification will only be sent to USERS in the QUEUE_OPERATOR
    list.  USER_GROUP members of the QUEUE_OPERATOR list will not
    receive notification.  If you wish to have lot's of people in the
    QUEUE_OPERATOR list, but do not want them to receive this
    notification, create a USER_GROUP, assign the users to this group
    and then assign this group to the QUEUE_OPERATOR list.  (NOTE:Some
    printers momentarily signal OUT_OF_PAPER when the printer really
    does have paper.)

    It is also possible to totally eliminate these notification
    messages on a per-printer basis.  If the DOS environment variable
    LS_NO_NOTIFY=YES exists before running the NODE program,
    notifications from this printer will be disabled.

    To set this variable, add this line to your print station's
    autoexec file:

    SET LS_NO_NOTIFY=ON


    The NODE VERBOSE Option:

    The NODE now comes with a /verbose option that details the actions
    of the NODE while it is trying to load.  This is helpful when
    problems are encountered while NODE is loading and it is necessary
    to locate the cause and correct the problem.  The syntax is:

    NODE ps=printserver /verbose

    Known problems:

    1. When a COM2 printer is re-attaching, it seems to "freeze" the
    work-station for about 10 seconds.

    2. Novell has stopped fixing SPX bugs in their IPX.COM program.
    Novell is currently only fixing things in the ODI drivers.  Use
    only the latest ODI drivers for your workstations.  Beware that
    the ODI drivers which shipped with Novell 3.11 are not the latest
    drivers and have known bugs in them.  Always get the latest
    drivers from the ESMS tools disk or NetWire.

