From: kbs@ccr-p6.ccr.jussieu.fr (An OCR-IP fan)
Newsgroups: bit.listserv.novell,comp.sys.novell
Subject: [SUMMARY]:NW31,WIN31,MAC,PRINTING 2/2
Date: 26 Sep 92 21:54:25 GMT
Organization: Universites P. & M. Curie / D. Diderot


Subject: WINTIPS - Windows vs. NetWare Troubleshooting Tips

Originated By: Brett Warthen (BRETT @ INFINITE)


ett Warthen (Infinite Technologies)
                          July 15, 1992

The most important troubleshooting tip for solving conflicts
between Windows and NetWare is to remember to use logical
deduction and the process of elimination to isolate conflicts.

For example, if you are using a 3rd party memory manager like
QEMM or 386-to-the-MAX, de-install it and try your configuration
running Microsoft's HI(try wmemorysIf you are loading any additional TSRs or device drivers, try
your configuration without them loaded, and add them back into
your system one by one to determine which is causing the
conflict.

If you are using EMSNETX or XMSNETX, try using regular old NETX
instead.

While far from being a comprehensive guide to all possible
Windows and NetWare conflicts, this document contains some
troubleshooting tips for common problems running Windows in the
NetWare environment.  (Thanks to everyone in NOVB Section 15, the
Windows section of the Novell NetWire forums on CompuServe for
helping to compile this list.  Acknowledgements are presented at
the end of this document.)

Recommendations for ALL Systems:

     1.)  In the Windows SYSTEM.INI file, verify the following
          settings:

          Under the [boot] section header:
          network.drv=netware.drv

          Under the [386Enh] section header:
          network=*vnetbios,vnetware.386,vipx.386

          (NOTE: *vnetbios can cau                                       that remain on your system are 1992 dated versions.
          (The latest versions are on the Windows 3.1 diskettes,
          but you many have to manually expand them.  Or you can
          download WINUP6.ZIP from NOVLIB Library 5 on
          CompuServe/NetWire.)

     4.)  Verify that the NETWARE.DRV file is approximately
          125,000 bytes in size.  We've seen plenty of problems
          where installation routines did not properly expand
          this file.

          The NetWare DOS/Windows Workstation Kit NWSETUP
          installation procedure is particularly notorious for
          this type of problem.

     5.)  Use WINSTART.BAT with care.  There is a bug with
          WINSTART.BAT processing under Windows 3.1 on some PCs,
          which can cause Windows to hang-up when exiting.

          The NetWare DOS/Windows Workstation Kit NWSETUP
          installation procedure creates a dummy WINSTART.BAT
          which can trigger this problem.

     6.)  If you want to receive broadcast messages while in
          Windows, then make sure that NWPOPUP.EXE is included in
          the "load=" statement in your WIN.INI file.

     7.)  In your NET.CFG (or SHELL.CFG) file, be sure to
          allocate plenty of file handles.  FILE HANDLES=80 is a
          recommended minimum.

     8.)  In your NET.CFG (or SHELL.CFG) file, allocate
          additional stacks for IPX/SPX usage by specifying GET
          LOCAL TARGET STACKS = 5.

          The default setting is 1 stack, which can lead to
          system lockup problems when receiving NetWare broadcast
          messages.

          If you plan on making use of IPX/SPX applications on a
          regular basis, then you should increase this value to
          GET LOCAL TARGET STACKS = 10.

     9.)  If you are running DR-DOS 6, make sure that you have
          the April Business update installed for Windows 3.1
          compatibility.

          This file can be downloaded from DRFORUM on CompuServe,
          DR6UP     9                        with many LAN drivers.

Windows hangs while loading:

     1.)  For Windows 3.0, is your network card set to IRQ 2 or
          9, 10 or higher?  If it is, then you will need to
          install the VPICDA.386 patch (included in WINUP6.ZIP in
          NOVLIB on CompuServe).  Copy VPICDA.386 into your
          Windows\SYSTEM directory, and edit your SYSTEM.INI,
          replacing the line "device=*vpicd" with
          "device=vpicda.386".

          NOTE:  VPICDA.386 is not required for Windows 3.1, you
          should specify "device=*vpicd" instead.

     2.)  Try loading Windows with a command-line parameter of
          /D:XSV (e.g., WIN /D:XSV).

          Each of the letters following the /D: are equivalent to
          placing the following statements under the [386Enh]
          section header in SYSTEM.INI, one time only:

          X -> EMMExclude=A000-EFFF
          S -> SystemRomBreakpoint=OFF
          V -> VirtualHDIrq=OFF

          If Windows now works, use a process of elimi          determine which of the parameters was the key to your
          succ          WIN /D:X is most often the solution to these types of
          problems, which indicates that the shared RAM area used
          by your network adapter is not properly excluded from
          your memory manager, or the Windows internal memory
          manager.

          For Windows internal memory manager, you exclude this
          memory range with an EMMExclude=xxxx-xxxx statement
          under the [386Enh] section header of your SYSTEM.INI.
          If you are unsure of this range, use EMMExclude=A000-
          FFFF while troubleshooting.  As an example, to exclude
          a 16KB range of memory at segment D000h, you would
          specify EMMExclude=D000-D3FF.

          For the Microsoft EMM386.EXE memory manager, use a
          /X=xxxx-xxxx parameter to tell it what range of memory
          to exclude for your network card.

     3.)  Are you loading MS-DOS 5 SHARE or running MS-DOS 4 (DOS
          4 automatically loads SHARE if you have a hard disk
          larger 
          If you can avoid loading SHARE, do so.

          If you cannot, load SHARE before IPX and NETX.  Place
          the statement "FILES=XXX" in your CONFIG.SYS file.  XXX
          is 255 minus 2 (reserved handles) minus the number of
          files handles defined in your NET.CFG (or SHELL.CFG)
          file.  The default is 40.  Therefore, if you are using
          the default, you would set FILES=213 in your
          CONFIG.SYS.

     4.)  There are known conflicts between the IBM LAN Support
          drivers for Token Ring and the "*vnetbios" driver
          supplied with Windows.

          If you can use the NetWare drivers that talk directly
          to the Token Ring adapter, this should work.
          Otherwise, do not include "*vnetbios" on the "network="
          line under the [386Enh] section header of your
          SYSTEM.INI file, and avoid running any applications
          that use NE     5.                           contact the software manufacturer for other possible
          work-     6.)  There could be an interrupt or I/O conflict between
          your network card, and Windows searching your COM ports
          for a mouse.

          These are the default COM port interrupt (IRQ) & I/O
          assignments:

          COM1 = IRQ 4, I/O 3F8h
          COM2 = IRQ 3, I/O 2F8h
          COM3 = IRQ 4, I/O 2E8h
          COM4 = IRQ 3, I/O 2E0h

          (NOTE:  On IBM PS/2s, the settings for COM3 or COM4 are
ecify COM#Irq=-1 to disable a particular port.  For
          example, specify COM2Irq=-1 to disable COM2.

          You could also specify MaxCOMPort=2 under the [386Enh]
          section header to ensure that COM3 and COM4 are not
          being used.

System Hang-ups running RCONSOLE or other IPX/SPX applications
under Windows:
IPX/SPX under Windows.

          A minimum version level of IPX v3.10 or IPXODI v1.20 is
          required.

          For Windows in 386 Enhanced Mode, make sure that you
          have VIPX.386 v1.10 or v1.11.  (Use the NetWare VERSION
          utility to run against VIPX.386 to determine the
          version.)  Make sure that you do not have duplicate
          copies of VIPX.386 elsewhere in your path.  In
          particular, check both the Windows and Windows\SYSTEM
          directories for duplicates.  Furthermore, ensure that
          VIPX.386 is included in the "network=" statement under
          the [386Enh] section header of your SYSTEM.INI.

          For Windows in Standard Mode, make sure that TBMI2 is
          loaded before going into Windows, but this will not be
          sufficient for many IPX/SPX applications.

     2.)  Place the statement GET LOCAL TARGET STACKS = 10 in
          your NET.CFG (or SHELL.CFG) file to allocate additional
          stacks for IPX/SPX multi-tasking.

     3.)  For RCONSOLE, if all servers do not show up in the
          display, you need RCONSOLE v2.9, which is available for
          download   Syste                            problems associated when network activity is generated
          fromCannot locate NETWARE.DLL error when loading NetWare Tools or
another application:

     1.)  See the "Recommendations for ALL Systems" section.
          There is no NETWARE.DLL, it is actually NETWARE.DRV,
          which is either not specified as
          "network.drv=netware.drv" under the [boot] section of
          SYSTEM.INI, or the NETWARE.DRV file is corrupt.

Remote Boot PCs cannot find WINA20.386:

     1.)  WINA20.386 is a DOS 5 file that is required for running
          Windows 3.0 in enhanced mode with DOS=HIGH in the
          CONFIG.SYS.  (It is supposedly no longer used by
          Windows 3.1.)

          Windows looks for WINA20.386 when it is loading in the
          root of the boot drive *UNLESS* you include SWITCHES=/W
          in your CONFIG.SYS file, and specify
          "device=d:\path\WINA20.386" under the [386Enh] section
          header of SYSTEM.INI to tell Windows where to find this
          driver.

Remote Boot PCs cannot find EMM386.EXE:

     1.)  If you are using the Microsoft EMM386.EXE device driver
          to provide expanded memory emulation, then be aware
          that Windows needs to reload EMM386.EXE when Windows is
          started to load a virtual device driver for upper
          memory management in 386 enhanced mode.

          Windows looks for EMM386.EXE in the drive/directory
          that it was loaded from in CONFIG.SYS.  If you need to
          specify an alternate path, include a
          /y=d:\path\EMM386.EXE parameter when loading EMM386.EXE
          in CONFIG.SYS.  This path should be a path that will be
          valid when Windows is later started.

Broadcast Messages do not display when in Windows applications:

     1.)  Verify that NWPOPUP.EXE is included in the "load="
          statement of your WIN.INI file.

     2.)  In the Windows Control Panel, Network Options, ensure
          that the "Messages Enabled" button is clicked.

     3.)  See the "Recommendations for ALL Systems" section.

Broadcast Messages lock up Windows:

     1.)  See the "Recommendations for ALL Systems" section.  In
          particular, focus on the GET LOCAL TARGET STACKS
          statement that should be placed in your NET.CFG (or
          SHELL.CFG) file.

          Ensure that this statement is echoed to the screen when
          IPX or IPXODI is loaded.

DOS DIR Command Shows No Files when used on Network Drives:

     1.)  See the "Recommendations for ALL Systems" section.  In
          particular, focus on the GET LOCAL TARGET STACKS
          statement that should be placed in your NET.CFG (or
          SHELL.CFG) file.

          Ensure that this statement is echoed to the screen when
          IPX or IPXODI is loaded.

How do I update to IPX.COM v3.10?:

     1.)  If you installed Windows 3.1 for a Novell network, it
          should have copied an IPX.OBJ file to your
          Windows\SYSTEM directory.

          Copy this file to your WSGEN or SHGEN dis  EN                        process, and are generally more up-to-date, as Novell
          is no longer certifying new drivers for the linkable
          IPX.COM.

          The IPX ODI drivers are included in the DOSUP5.ZIP file
          in NOVLIB Library 5 on CompuServe/NetWire, and
          documentation is included in ODIDOC.ZIP in this same
          library.

Controlling Windows Swap Files:

     1.)  The following statements under the [386Enh] section
          header of SYSTEM.INI control the creation and placement
          of Windows temporary swap files in 386 enhanced mode:

          Paging=Off (disables paging)
          MaxPagingFileSize=xxxx (max size of temporary swap file
          in KB)
          PagingDrive=d (paging files will be placed in the root
          of this drive)
          PagingFile=d:\path\SWAPFILE (Windows 3.1 only: name to
          use for swap file, overrides PagingDrive entry)

     2.)  The following statement under the [NonWindowsApp]
          section of SYSTEM.    
                      also use for controlling where they create temporary
          files), or the root directory of your first hard disk
          if the TEMP variable is not defined.

     3.)  The following statements under the [386Enh] section
          header of SYSTEM.INI control the location of permanent
          swap files (Windows 3.1 Only):
ize of permanent swap
          file)

Windows is very slow while loading:

     1.)  This is probably due to Windows creating a temporary
          swap file when loading, possibly to a network drive.

          Under NetWare 2.x, this process is much slower than
          with NetWare 3.x.  See "Controlling Windows Swap Files"
          above for more information.

Printing to a NetWare Print Queue results in 65,535 copies
requested:

     1.)  There are problems with the drivers for the current
          line of Intel 32 bit EISA network adapters.  Contact
          Intel to see if a fix is available, or use a different
          network adapter.
Loading disp               
Garbage when printing from Windows to a network printer:

     1.)  Are you running PSERVER?  If you are, then you need the
          latest and greatest version, v1.22.  PSERV1.ZIP can be
          downloaded from NOVLIB Library 6 on CompuServe/NetWire.

     2.)  What is your CAPTURE statement that you execute before
          going into Windows?  You need to specify the NT (no tab
          expansion) flag, and I recommend a timeout of at least
          60 seconds (TI=60).  For PostScript printers, NB (no
          banner) and NFF (no form feed) are also necessary.  NA
          (no autoendcap) is also required in some Windows
          configurations.

          The NA flag will cause you some problems if you are
          printing to LPTx.OS2 (or LPTx.DOS in Windows 3.1)
          instead of LPTx.  While previous recommendations were
          to print to LPTx.OS2, these recommendations have been
          superseded because of updated Novell drivers.

          If you are using all Wi                 3.)  In the Windows Control Panel/Printers/Configure menu,
          disable the print manager if it is not already
          disabled.  (Since NetWare print jobs are spooled to
          disk anyway, using the print manager when spooling to a
          network printer is redundant and can slow things down.)

     4.)  Make sure that you have the latest NetWare drivers for
          Windows.  For Windows 3.1, the drivers that ship with
          the product are satisfactory.  For Windows 3.0, you
          need VNETWARE.386 v2.0, the version that is included in
          the WINUP6.ZIP file in NOVLIB Library 5 on
          CompuServe/NetWire.

     5.)  Type CAPTURE SHOW in a DOS Window after going into
          Windows, and make sure that these settings are the same
          as what were set before going into Windows.  A Windows
          "permanent list" setting can override the CAPTURE that
          you set before going into Windows.  Check the [network]
          section of           6      Window              loaded:  "network.drv=netware.drv" under the [boot]
          section of SYSTEM.INI, and for 386 enhanced mode,
          "network.drv=vnetware.386" (*vnetbios & vipx.386 may
          also be specified in this command) under the [386Enh]
          section of SYSTEM.INI.

     2.)  For Windows 3.0, is your network card set to IRQ 2 or
          9, 10 or higher?  If it is, then you will need to
          install the VPICDA.386 patch (included in WINUP5.ZIP in
          NOVLIB on CompuServe).  Copy VPICDA.386 into your
          Windows\SYSTEM directory, and edit your SYSTEM.INI,
          replacing the line "device=*vpicd" with
          "device=vpicda.386".

          NOTE:  VPICDA.386 is not required for Windows 3.1, you
          should specify "device=*vpicd" instead.

     3.)  You may be running out of file handles.  Increase the
          value specified in the FILE HANDLES statement in your
          NET.CFG (or SHELL.CFG) file.

     4.)  You may be experiencing swap file corr              
     5.)  A TSR that you are running may require that you specify
          "TimerCriticalSection=10000" under the [386Enh] section
          header of your SYSTEM.INI

DOS Environment Missing or Corrupt in DOS windows:

     1.)  Make sure that you have the NetWare drivers for Windows
          loaded:  "network.drv=netware.drv" under the [boot]
          section of SYSTEM.INI, and for 386 enhanced mode,
          "network.drv=vnetware.386" (*vnetbios & vipx.386 may
          also be specified in this command) under the [386Enh]
          section of SYSTEM.INI.

     2.)  Verify that your NetWare drivers are up to date.
          Review "Recommendations for ALL systems" in this
          document.

Changing directories on a network drive in one window affects all
windows:
 of your WIN.INI file, then this is what is
          causing the problem.

     2.)  If you have a TASK MODE = statement in your NET.CFG (or
          SHELL.CFG) file, then this is what is causing the
          problem.

NetWare wou      
R
     1.)  These don't peacefully co-exist at this time, and the
          best solution is to purchase a 3rd party alternative.
          Alternatives include hardware based solutions like
          network cards installed in laser printers, as well as
          the Castelle LanPress and Intel NetPort.  Software
          solutions like Fresh Technologies Printer Assist and
          Intel's LanSpool are also reported to work.

          If you want to try RPRINTER, you can also experiment
          with the following suggestions.

     2.)  Run Windows in Standard Mode (WIN /S) on PCs that are
          running RPRINTER.

     3.)  Disable the Windows print manager.

     4.)  Try increasing the SPX timeout values specified in your
          NET.CFG (or SHELL.CFG).  For example:

          SPX ABORT TIMEOUT = 4000
          SPX LISTEN TIMEOUT = 2500

     5.)  Try installing Microsoft's VPD.386 driver as
          "device=vpd.386" under the [386Enh] section header of
          SYSTEM.INI.  T      P
        Undocumented Option for Changing Drives and Printers Built into
NetWare Drivers
      There is an undocumented option built into NETWARE.DRV that
      gives you hot-key access to a dialog that allows you to
      change drive mappings, print queue assignments, and
      attach/detach to other servers in your network.

      Under the [options] section of your NETWARE.INI file,
      include a statement "NetWareHotKey=123".

      Restart Windows and press F12.  Any time you press F12, it
      will pop-up a selection menu that gives you access to a
      menu of NetWare functions.  Do not minimize this window or
      switch away from it while active, or the application that
      you popped this window up over will no longer be able to
      receive keystrokes.

Where to Go For More Information
Networking Windows: NetWare Edition" by Howard Marks,
      Kristin Marks and Rick Segal from Sams Books

      "Microsoft Windows Resource Kit" from Microsoft

      "Windows 3.1 Secrets" by    
+----| Com|      | Address comments via e-mail...                                   |
|                                                                  |
|         MHS:  Brett @ Infinite (via CSERVE or NHUB)              |
|  CompuServe:  >MHS:Brett@Infinite (or 76704,63 if you must)      |
|    Internet:  Brett@Infinite.mhs.compuserve.com                  |
|         FAX:  +1-410-363-3779                                    |
|      Others:  > NUL                                              |
|                                                                  |
+------------------------------------------------------------------+

Special thanks to all of those who participate and contribute in
NOVB Section 15 on the NetWire forums on CompuServe, including:

Jimmy Wright, Novell
Rich Adams, volunteer NetWire Sysop
Dennis Beach, volunteer NetWire Sysop
Sandra Duncan, Novell
Jon Hunt, Novell
Mickey, Dave, Andy & Deb on NetWire
Stephen Saxon, Author "Running Windows on NetWare" on M&T Books
 (1-800-533-4372 to order)
Howard MarkRiGreg McGovern
David Chamberlain
Alan Woolfson
Barry St. John
Peter O'Rourke
Peter Hauptmanns
Michael Hader
Jim Reese
...and the original cast & crew of Gilligan's Island


-- 
=============================================================================
Laboratoire d'Electrochimie - Universite Paris 7  |Khac Binh Su
4, place Jussieu, Tour 44/45, 75005 PARIS. FRANCE |e-mail: kbs@ccr.jussieu.fr
=============================================================================