
                           README FILE -C.00.00
                      HP PC ARPA and Network Services
                    (MS-DOS, LAN Manager, and Netware)
                          Modified December 4, 1992
 
This README provides additional information about HP PC ARPA and
     Network Services.

This information is organized into the following areas:
 
    * Installation
    * Re-configuration
    * Removal
    * MS-DOS Workstation
    * Special notes for DOS 5.0 Users
    * MS Windows Support
    * MS-DOS Memory Managers
    * Troubleshooting Problems related to Windows and Memory Managers
    * Multiple Session VT Support
    * Terminal Emulators
    * Lan Adapter Cards
    * Demand Loading HP ARPA and NS
    * Making low density diskettes and installing on a low density PC
    * Domain Name Resolution Troubleshooting
    * Application Notes
    * Unload name change
 
You are encouraged to read this entire document since the information provided
in one section may apply to others.
 
#############################################################################
Note: The telephone assistance program called HP HelpLine is NOT available 
      for the HP PC ARPA and Network Services product.  If you have questions
      after reading the manuals, or experience problems with the product and
      are unable to resolve those problems using the manuals, please contact
      your HP Representative, per your support contract. If you do not have a
      support contract for the product, please contact your HP Sales
      Representative for assistance in obtaining an HP Support Contract 
      for the product.
#############################################################################


--------------------------------------------------------------------------
Installation
--------------------------------------------------------------------------

1. To start the installation program for HP PC ARPA and Network Services,
   type "a:\netsetup" at the DOS prompt.  If your PC has Netware, some other 
   steps are required.  See the HP PC ARPA and Network Services Installation
   Guide for details.
   
2. NETSETUP requires 225K of memory to run.  If this is unavailable, it will
   not load.  You can temporarily free memory via one of the following 
   methods:

    - If you are running Microsoft Lan Manager  you can use the
      Microsoft "unload" command to stop the Lan Manager workstation.
      Refer to your Microsoft documentation for additional information.
      
    - Run hpunload to unload any HP networking that may be in memory.

    - Edit your autoexec.bat and/or config.sys files and temporarily
      "comment out" software that gets loaded when you bootup.  Re-boot
      your PC and run netsetup.  Then uncomment the lines you commented
      and reboot.

    - Boot from your MS-DOS disk on the floppy drive and then run NETSETUP.

3. HP PC ARPA and Network Services is not supported with the 
   following products:

   - HP Lan Manager 1.0, 1.1 or 1.2
   - 3Com 3+Open (running any protocol, TCP/IP, NBP, etc)
   - Microsoft Lan Manager 2.0.
   - Microsoft LM using the DLC transport
   
4. HP PC ARPA and Network Services ships on two high density floppy diskettes.
   There is a procedure later on in this "README" file that explains how to
   convert high density floppies to low density (360KB) floppies.

5. Installing HP PC ARPA and Network Services on a PC with HP LAN Manager
   1.0, 1.1 or 1.2 will remove LAN Manager.

6. If you are updating from a previous HP PC ARPA/NS product to HP PC ARPA 
   and Network Services, the new HP PC ARPA and Network Services NETSETUP
   removes and replaces the previous HP PC ARPA/NS files; therefore, there 
   is no need to remove the previous HP PC ARPA/NS product.  By not removing
   the previous HP NS or ARPA product, your previous configuration values
   can be retained.
   
7. If you are planning to use Lan Manager with HP PC ARPA and Network Services,
   Lan Manager must be installed first.

8. If you plan to customize the network startup in CONFIG.SYS, PROTOCOL.INI,
   or NET_STRT.BAT then you should wait to do this customization until you
   have installed the HP PC ARPA and Network Services product.  Otherwise,
   this work may be lost when NETSETUP rewrites information into these files.

9. If HP PC ARPA and Network Services is being installed on a PC with Microsoft
   LAN Manager 2.1, the LAN Manager Computername will be used as the HP ARPA
   and NS computername.  This name uniquely identifies each host on a 
   sub-network. In the HP product, it is combined with the domain name to
   form the fully qualified name for each computer.  If you wish to use a 
   different name than the LAN Manager Computername, you can manually edit your
   protocol.ini file to change the HOSTNAME line in the [TCPGLOBAL] section. 
   See the HP PC ARPA and Network Services Installation Guide for more 
   information about protocol.ini.

10. If there are any blanks or tabs after the "=" in your path statement
    (in AUTOEXEC.BAT), NETSETUP may not correctly modify your path.  To
    fix this problem, remove all blanks and tabs from your path statement,
    either before or after running NETSETUP.
 
--------------------------------------------------------------------------
Re-configuration
--------------------------------------------------------------------------

1. When HP PC ARPA and Network Services is installed along with Microsoft 
   LAN Manager 2.1, HP NETSETUP should be used to re-configure HP PC ARPA
   and Network Services and Microsoft SETUP should be used to re-configure
   LAN Manager.  NETSETUP must always be run after SETUP to restore the HP 
   PC ARPA and Network Services configuration that SETUP takes away.  If 
   you do not need to change any HP NS or ARPA configuration values, you 
   can run NETSETUP silently by typing "netsetup /u".

2. When HP PC ARPA and Network Services is installed with Novell ODI, 
   HP NETSETUP must always be run after changes to Novell ODINSUP or
   NET.CFG to restore the HP PC ARPA and Network Services configuration.
   If you do not need to change any HP NS or ARPA configuration values, 
   you can run NETSETUP silently by typing "netsetup /u".

3. Manual edits to the network configuration (PROTOCOL.INI for example)
   should be made to the template files (PROTOCOL.SYM for example) to
   avoid the changes being lost if NETSETUP is used to re-configure the
   network.  NETSETUP will still modify some of the values in the
   PROTOCOL.SYM file, so it may not work for all kinds of network tuning.

--------------------------------------------------------------------------
Removal
--------------------------------------------------------------------------

1. To remove HP PC ARPA and Network Services in a Microsoft Lan Manager 
   2.1 environment, you must use the remove function in Lan Manager SETUP.  
   This will also remove Microsoft Lan Manager.

2. Using NETSETUP to remove networking files will remove all network
   files, not just a specific service.  Therefore, it is important to
   backup any files that you would like saved such as your HOSTS file.

--------------------------------------------------------------------------
MS-DOS Workstation
--------------------------------------------------------------------------

1. Use the command WHAT.EXE to get the software version information instead
   of NETDIAG.EXE.  This information is required by HP Support to answer
   networking questions.

2. The HP PC networking is started on your PC by the batch file NET_STRT.BAT.
   The location of NET_STRT.BAT is different for different environments.
   
   If HP PC ARPA and Network Services is installed with Microsoft LAN 
   Manager 2.1, then the network directory structure where NET_STRT.BAT is
   located is \LANMAN.DOS.

   If HP PC ARPA and Network Services is installed with Netware or as a 
   standalone product (i.e. Lan Manager is not installed) then the network 
   directory structure where NET_STRT.BAT is located is \HPNET.
   
3. Some network adapter cards return incorrect card statistics to NETDIAG.
   Use the card manufacturer's diagnostic utilities to locate card problems.

4. HP PC ARPA and Network Services provides a utility that can be used to
   configure PC workstations so that they can access remote hosts that are
   not on the same logical LAN as the PC workstation.  This utility is INETNAME.
   See appendix C in the HP PC ARPA and Network Services Services Installation
   Guide for more information.

   You may use INETNAME to create permanent hosts files on the PC workstation
   to access ARPA hosts when using FTP or Telnet.

   Additionally, you may also use any text editor to create/modify the
   PC workstation's hosts file.

5. The MS-DOS environment space must be able to accommodate the added path
   statements for the HP networking products.  Enter the following line
   into your CONFIG.SYS file:

     SHELL=command.com /p /e:<size>

   The value for "size" (160 bytes by default) should be increased by the
   number of characters added to your path by NETSETUP.  If you use the
   default network path, this is approximately 17 bytes.  You also need to
   add 15 bytes for the ARPAUSER environment variable, and 8 bytes
   for the DMDL environment variable.

6. Installing HP networking products may cause your PATH to exceed the MS-DOS
   limit of 128 characters.  If this occurs, reduce its size so your system
   operates normally.

--------------------------------------------------------------------------
Special notes for DOS 5.0 Users
--------------------------------------------------------------------------

1. HP PC ARPA and Network Services supports DOS 5.0.

2. The networking software must be started before running the MS-DOS 5.0
   DOSSHELL program.  Hence demand loading of the network is not supported
   after the MS-DOS 5.0 DOSSHELL program is started.

3. The EMM386.EXE memory manager provided with MS-DOS 5.0 is supported by
   HP PC ARPA and Network Services.  The following section gives the steps
   required to set up EMM386.EXE to provide EMS and UMB memory on your
   MS-DOS 5.0 system.

   	a) Modify CONFIG.SYS to load HIMEM.SYS.  For example:
	
		device=c:\dos\himem.sys

	b) Add a "dos=umb" command to CONFIG.SYS.  If your CONFIG.SYS
	   already contains a "dos=high" command, then you can just add
	   the "umb" option to that command.  For example:

	   	dos=high,umb	or
		
   		dos=umb

	c) Add a device command for the EMM386.EXE memory manager.  EMM386.EXE
	   works in conjuction with HIMEM.SYS to provide EMS and UMB memory
	   to DOS programs.  The device command to load EMM386.EXE must
	   contain either the "noems" or the "ram" option in order for UMB
	   memory to be made available.  Since HP PC ARPA and Network Services
           can make use of EMS memory we suggest that you use the "ram" option
           so that the network can load into both EMS and UMB memory.

	   	device=c:\dos\emm386.exe ram

	d) By default EMM386.EXE selects the segment address
	   D000h for the page-frame segment base used by EMS.  If you will
	   be using EMM386.EXE to provide UMB memory along with EMS memory
	   then this value on many PCs will fragment the available UMB
	   memory into smaller pieces.  It is always best when possible to
	   make UMB memory contigous so that large device drivers/TSRs will be
	   able to be loaded into UMB memory.  Consequently a better value on
	   many PCs is to place the page-frame segment at the address
	   E000h.  This can be done by placing the following option on
	   your EMM386.EXE device command in CONFIG.SYS:
		
	   	device=c:\dos\emm386.exe ram frame=E000
   
   For further information on the use of EMM386.EXE, see the "Microsoft
   MS-DOS Users's Guide and Reference", version 5.0.
   
   See the "MS-DOS Memory Managers" section of this document for further
   information on EMM386.EXE and other supported memory managers.

-----------------------------------------------------------------------------
MS Windows Support
-----------------------------------------------------------------------------
 
1. HP PC ARPA and Network Services supports all modes for Microsoft Windows
   3.0a and 3.1.

2. When Windows 3.1 is in use, use a different LAN card interrupt value than
   3.  Interrupt value 3 seems to have some unresolved conflict problems with
   MS Windows 3.1.  Interrupt 3 is the factory default for many LAN cards,
   so change to a different value if possible.

3. If Windows 3.1 is in use on a Compaq PC, a different version of W3IPC.DLL
   is required.  This W3IPC.DLL can be found on the HP PC ARPA and Network
   Services Supplemental Diskette.  Find the already installed version of
   W3IPC.DLL and copy the supplemental diskette version over it.  The already 
   installed W3IPC.DLL will be in one of the following places:
       C:\LANMAN.DOS\NETPROG   (if your PC has Enhanced LM installed)
       C:\LANMAN.DOS\BASIC     (if your PC has Basic LM installed)
       C:\HPNET\NETPROG        (standalone and netware cases)
 
4. MS Windows 3.0 users who will be using the HP PC ARPA and Network Services
   product must upgrade to Windows 3.0a.  Use the Windows Help About box to 
   determine which version of Windows you have.
 
   Customers that have already purchased Windows 3.0 may obtain a maintenance
   upgrade from Microsoft by calling Microsoft Product Support at
   (206) 637-7098.
 
   Customers with over 50 Windows 3.0 units may execute a maintenance
   agreement which permits them to copy and distribute the Windows 3.0a
   release via network servers. Qualifying customers should contact Microsoft
   Corporate Accounts at (800) 227-6444.

5. If you will be running Windows 3.x in Enhanced Mode, then HP PC ARPA 
   and Network Services must be started before running Windows.  Loading 
   HP PC ARPA and Network Services while inside Windows 3.x Enhanced Mode
   is not supported.

6. When you run Windows 3.x in enhanced mode, network device drivers must not
   be configured to use DMA. Drivers that use DMA are likely to fail during
   Windows 3.x initialization and loading.

   Refer to your networking card's manual for specific setup information.

7. A problem exists in Windows 3.0 Real Mode with handling of 10 program 
   manager groups.  When starting Windows in Real Mode a popup window will
   appear displaying an error message.  This message may contain garbage 
   rather than properly identifying the failed group file.  Click on the OK
   bar of the window or press Enter and Windows will start properly, but the 
   tenth Program Manager group will not appear in the display.

   The HP utility WINFIX.EXE adds a program manager group for ARPA Services.
   If this is the tenth Program Manager group it will not appear properly.
   To allow this group to be displayed properly you must reduce the number 
   of groups to 8 or fewer.  Consolidate icons in Program Manager using the 
   "File Move" menu bar and delete groups using the "File Delete" menu bar.

   In order to allow WINFIX.EXE to add the ARPA Services program group delete
   the file ARPA.GRP in your windows directory and either run WINFIX from the 
   DOS prompt or reboot your computer.

   If you wish to use ten or more program groups contact Microsoft support
   for any new information on solutions or work-arounds.

8. For more information concerning networks and Windows 3.0 consult the
   NETWORKS.TXT file included with Windows 3.0.  In addition, Microsoft
   has an Application Note available entitled "Windows 3.0 and Networks" that 
   contains additional information about using networks with Windows 3.0.
 
9. We have encountered problems when using the FTP.EXE program to transfer 
   files (with the FTP "HASH" function enabled) when running Windows 3.0 in
   Enhanced Mode.  There appears to be a Windows defect related to the way
   FTP.EXE displays data when used with certain display hardware 
   configurations.  Systems using Paradise VGA boards, 3rd party display 
   adapters based on Paradise (such as HP VGA), and the HP SVGA display 
   adapter experience this problem.

   This "HASH" function is disabled by default, which causes no problems.  If 
   you desire to use the "hash" function, the only work around is to use a 
   different display adapter, or to run  FTP.EXE Full Screen instead of in a 
   Window.

10. When Windows 3.1 sets up existing applications, you will be prompted
    to specify the manufacturer for some or all of the following applications:
      <network path>\RSH.EXE
      <network path>\RCP.EXE
      <network path>\FTP.EXE
      <network path>\TN.EXE

    Chose the option, "Select none of the above" for all of these.
    The proper icons for HP ARPA services will automatically be installed.

11. If your PC has NetWare, which NetWare shell are you using?  HP has seen
    stability problems with NetWare and Windows when using XMSNETx or EMSNETx 
    as your NetWare shell.  HP recommends using only the NETx NetWare shell.

-----------------------------------------------------------------------------
MS-DOS Memory Managers
-----------------------------------------------------------------------------

1. With HP PC ARPA and Network Services certain networking modules will 
   automatically load into upper memory blocks (640KB-1MB) when a supported
   memory manager is installed on your PC workstation.  See chart below. 

   To disable the automatic high loading feature, add the /NoUMB option
   to the NEMM.DOS command line in CONFIG.SYS:
	
        C:\<network path>\NEMM.DOS /NoUMB

   Networking modules not automatically loaded high may be manually loaded
   into available upper memory blocks by using the load high program
   included with your memory manager.

   The following chart summarizes the supported memory managers and the
   various modes of Windows 3.x supported for each.


                            Supported Memory Managers
   
                              Operating Environment
                      ------------------------------------
                      | DOS | Win3 |   Win3   |   Win3   |
                      | 3.1 | real | standard | enhanced |
                      | or  | mode |  (286)   |  (386)   |
                      |later|      |   mode   |   mode   |
          ------------------------------------------------
          Qualitas    | OK  |  NO  |    NO    |    NO    |
          3ComEMM     |     |      |          |          |
          386 systems |     |      |          |          |
          ------------|-----|------|----------|----------|
          Qualitas    | OK  |  OK  | Note (3) | Note (1) |
          386MAX 5.10 |     |      |          | Note (2) |
	  or later    |     |      |          |          |
          386 systems |     |      |          |          |
          ------------|-----|------|----------|----------|
          Quarterdeck | OK  |  OK  | Note (4) | Note (1) |
          QEMM 5.11   |     |      |          |          |
          386 systems |     |      |          |          |
          ------------|-----|------|----------|----------|
          Quarterdeck | OK  |  OK  |    OK    |    OK    |
          QEMM 5.12   |     |      |          |          |
	  or later    |     |      |          |          |
          386 systems |     |      |          |          |
          ------------------------------------------------
          Quarterdeck | OK  | Note | Note (5) | Note (5) |
          QEMM 6.0    |     | (5)  |          |          |
          386 systems |     |      |          |          |
          ------------------------------------------------
	  Microsoft   | OK  |  OK  | Note (6) |    OK    |
          MS-DOS 5.0  |     |      |          |          |
	  EMM386.EXE  |     |      |          |          |
	  386 systems |     |      |          |          |
          ------------------------------------------------
          Qualitas    | OK  |  OK  |    OK    | Note (7) |
          Move'Em     |     |      |          |          |
          286 systems |     |      |          |          |
          ------------|-----|------|----------|----------|
          Other       | NO  |  NO  |    NO    |    NO    |
          Memory      |     |      |          |          |
          Managers    |     |      |          |          |
          ------------------------------------------------
   

   NOTES:
     1) - When using 3rd Party memory managers such as QEMM and 386MAX,
          DOS based HP ARPA Services (such as DSCOPY) must be run in full 
	  screen exclusive mode when running Windows 3.x in Enhanced Mode.
	  To configure your PC for this windowing mode, use the following 
	  Window 3.x Enhanced mode settings:

                   Display Options = Full Screen
                   Tasking Options = Exclusive

	  The above restriction is required due to problems introduced by
	  the 3rd Party memory managers and their interactions with Windows.

	  The above problem is fixed by QuarterDeck in version 5.12 or later
	  of QEMM-386.
	  
     2)   If the network is loaded into EMS memory and you attempt to
          load Windows 3.x in enhanced mode, Qualitas 386MAX 6.0 will
          display an error message and fail to load Windows.  To override
          this error, you must set the DOS environment variable "EMSCACHE":
                   set EMSCACHE=ok

     3)   Qualitas 386MAX 5.10 and later does not support standard mode.

     4)   If you try to use QEMM-386 5.11 in standard mode, Windows 3.0
          immediately exits back to the DOS prompt. HP recommends against
          using standard mode with QEMM-386 5.11.  This problem is fixed
	  in QEMM-386 5.12 or later.

          If you are running Windows 3.1, QEMM-386 version 5.13 is required.

     5)   QEMM-386 version 6.0 will make more high memory available than
          previous versions of QEMM-386 by using a feature referred to as
          "Stealth" by QuarterDeck.  Stealth will hide your PC's ROM code
          and make its memory addresses mappable as high memory.  The ROMs
          that Stealth looks for are your system (BIOS) ROM, a video ROM,
          and a disk ROM if you have one.

          Testing has shown that Stealth is incompatible with our network
          if the network is loaded into EMS and you attempt to start
          Windows 3.x.  The only work around is to not load the network in
          EMS. To disable the loading of the network into EMS, add the
          /NoEMS option to the NEMM.DOS command line in CONFIG.SYS:
	
                   C:\<network path>\NEMM.DOS /NoEMS

          For more information on the Stealth feature of QEMM-386 v6.0 refer
          to your QEMM-386 v6.0 documentation.

     6)   Windows 3.x running in standard mode is not compatible with
          EMM386.EXE
	  
     7)   Move'Em is a 286 solution and is not supported with Windows 386
          enhanced mode.  
  
          If you are using Move'Em on a 286 PC in Windows 3.x standard 
          mode, you may experience problems using a LA card with shared
          memory.  In this case, try using the /NoOpt option on the NEMM.DOS 
          command line in config.sys.  The line would look like this:
               DEVICE=C:\<network path>\NEMM.DOS /NoOpt

-----------------------------------------------------------------------------
Troubleshooting Problems related to Windows and Memory Managers
-----------------------------------------------------------------------------

 The following is a brief summary of HP PC ARPA and Network Services 
 troubleshooting information which should be reviewed when experiencing
 networking problems while using MS Windows or a supported Memory Manager. 
 You should review the sections "MS Windows Support" and "MS-DOS Memory 
 Managers" first to see if the problem you are experiencing is discussed there.
 
 1. Make sure this is a networking related problem.  Does it occur when the
    network is not loaded?

 2. If you made any changes recently to your system prior to experiencing the
    problem, then those changes should be carefully inspected since they are
    the most likely cause.

 3. Verify that you are using MS Windows version 3.0a or 3.1.  Refer to the
    "MS Windows Support" section in this document.

 4. For standalone and Netware configurations, verify that NETBIND is 
    loaded in your AUTOEXEC.BAT file before networking that requires it.  
    The network may not load properly if this is not the case.  In 
    standalone and Netware IPX environemtns, NETBIND should be the 
    first thing loaded in AUTOEXEC.BAT.  In Netware ODI environements, 
    NETBIND should be loaded immediately after lsl and the odi driver.

 5. Ensure that you are using a supported memory manager as documented in the
    "MS-DOS Memory Managers" section of this file.

 6. Ensure that your Windows directory is in your path and run the WINFIX.EXE
    program in the NETPROG subdirectory.

    If running Windows 3.x in Enhanced Mode check to be sure WINFIX updated
    your SYSTEM.INI file correctly.  The information WINFIX adds to SYSTEM.INI
    is described in Appendix A of the ARPA Installation Guide.

 7. If you are having MS-DOS application problems, try running the application
    in Windows full screen exclusive mode as described in the "MS-DOS  Memory
    Managers" section of this document.

 8. Inconsistent operation and system crashes typically indicate memory
    conflicts.

    Verify that the PC workstations memory configuration does not have any
    memory conflicts (e.g. memory used by multiple programs or hardware
    cards).  High memory (e.g. buffers) may need to be reserved for use by
    the hardware and need to be "excluded" from use by your memory manager.
    Refer to your memory manager documentation for additional information.

    Solving problems of this type is difficult.  Here are some basic
    procedures:

      - Try to find a sequence of steps that will replicate the problem.

      - If you are running Windows 3.0a, try forcing Windows to run in real
        mode (win /r) to see if you are running into an extended memory
        usage problem.  This type of problem is not networking related.
    
      - Verify that you are not using a network card that requires Shared Ram
        in the area between 640K and 1MB.  If your network card does use
        Shared Ram, is your memory manager "excluding" this area so that it
        doesn't try and use it?  If running Windows 3.x in Enhanced Mode,
        do you have an "EMMExclude" entry in SYSTEM.INI so that Windows
        doesn't try and use this memory?

      - Simplify your system until the problem disappears then focus your
        analysis on the change that corrected the problem.  Simplification
        examples are:

           * Force your networking to not use EMS or UMB memory by adding the
             switches  /NoEMS  and  /NoUMB  to the driver NEMM.DOS in the
	     CONFIG.SYS file.  The NEMM.DOS command line should like the 
	     following:
	     
                 C:\<network path>\NEMM.DOS /NoEMS /NoUMB

	     In addition, if you are using your memory manager to load high
	     other networking modules out of conventional memory, then undo
	     these changes so that all networking modules are being loaded
	     into conventional memory.

           * If you are using hardware that uses high memory (e.g. a high
             resolution graphics card), try to eliminate it from your
             configuration (e.g., run in VGA mode).

           * Reduce the configuration parameters used with your memory
             manager to the absolute minimum.  Verify that each parameter is
             required and if possible allow the memory manager to determine
             the default value to use.

    For some users it may be easier to strip the PC workstation back to a
    simple MS-DOS system and slowly add complexity.

      - Try to find someone who is not having the problem.  Compare your
        system's memory configuration to theirs.

-----------------------------------------------------------------------------
Multiple Session VT Support
-----------------------------------------------------------------------------

1. HP PC ARPA and Network Services will now support up to 8 VT sessions 
   via a single copy of VT.EXE.  Earlier versions of HP NS required VT to 
   be loaded multiple times to support more than 1 VT session.  Consequently 
   NET_STRT.BAT will now load VT.EXE only once.  VT.EXE will read the
   "NSESSIONS" parameter from PROTOCOL.INI (set by NETSETUP) to determine 
   how many VT sessions are required.  This new scheme will result in 
   reduced memory usage when more than 1 VT session is requested via NETSETUP.

-----------------------------------------------------------------------------
Terminal Emulators
-----------------------------------------------------------------------------
 
1. If you are using HP AdvanceLink for Windows/NewWave with HP PC ARPA and 
   Network Services you need to have the HP AdvanceLink for Windows/NewWave
   Version A.03.02 or later.

2. If you are using a release of HP AdvanceLink for DOS prior to B.02.20 
   as a terminal emulator with HP ARPA Services, do not use the AdvanceLink 
   file transfer.  Use the FTP utility to transfer files instead.  You can 
   run FTP as a DOS command while in AdvanceLink, or exit AdvanceLink to run 
   FTP.  The release of AdvanceLink for DOS B.02.20 includes an enhancement 
   to provide file transfer. 

3. HP took the standard Kermit 3.0 and changed it to allow for multiple 
   connections.  If you replace the Kermit 3.0 installed by NETSETUP, you will 
   lose the ability to have multiple connections through Kermit 3.0.

-----------------------------------------------------------------------------
Lan Adapter Cards
-----------------------------------------------------------------------------

1. When using NETSETUP be sure the information given for the lan adapter card
   matches the hardware settings on the card.  Wrong information will cause
   the network to not function correctly and in some cases cause the PC to
   hang.
   
   In particular problems have been seen with the Western Digital lan adapter
   cards when the "Interrupt Level" given to NETSETUP didn't match the actual 
   "Interrupt Level" setting on the card.

2. When using an Etherlink II (3C503) network adapter card, set the card
   to an interrupt level other than 7 since spurious networking problems
   have been seen with this value.

3. When using the HP Ethertwist PC LAN Adapter/Plus TP(HP27247B), do not 
   use the auto configuration feature in the HPLANSET program.  HPLANSET is 
   the program shipped with the card, which is used to set the configuration 
   of the card.  The value for LAN Connector must be set by hand to either 
   twisted pair or AUI.

4. Interrupt value 3 seems to have some unresolved conflict problems with
   MS Windows 3.1.  Interrupt 3 is the factory default for many LAN cards,
   so change to a different value if possible.
 
5. If HP PC ARPA and Network Services is being used on a PC with Microsoft
   LAN Manager 2.1 and Microsoft LAN Manager is not configured for TCP/IP, 
   then HP TCP/IP will be used for ARPA services.  In this case, HP TCP/IP 
   will run over the Microsoft configured LAN card.  In the unlikely event
   that more than one card is configured for Microsoft LAN Manager, HP 
   TCP/IP uses the first of these cards.  If this is not the card you would 
   like used, you can manually edit your protocol.ini file to change the
   BINDINGS line in the [TCP/IP] section.  See the HP PC ARPA and Network
   Services Installation Guide for more information about protocol.ini.

6. If you plan to use an HP LAN card in the Netware ODI Environemt with  
   HP PC ARPA and Network Services, you need an ODI client driver for 
   the LAN card.  Given below is a summary of the HP LAN Adapters and 
   their ODI drivers which were successfully tested with the HP PC Network 
   and ARPA Services product.
       HP Ethertwist PC LAN Adapter/8 (27245A) driver = HPISAODI.COM
       HP ThinLAN PC LAN Adapter/8 (27250A) driver = HPISAODI.COM

   If the above driver is not available on the support disk shipped with 
   the HP LAN Adapter that you purchased, please contact your HP Authorized
   dealer to get a copy of the new support disk.  You may also download 
   the drivers from CompuServ on the HP Network forum.

7. We are still working to get HP PC Network and ARPA Services with the 
   following HP LAN Cards to operate reliably in the Netware ODI environment 
   (w/ the HPISAODI.COM ODI driver):
       HP Ethertwist Adapter/16 TP Plus (27247B)
       HP Ethertwist Adapter/16 TL Plus (27252A)      
   As of this product release, we recommend using the Netware IPX
   environment (w/ NDIS card driver) with these cards.

8. Our testing showed problems with the following NDIS LAN card drivers
   in a dual-stack environment:
      IBM Token Ring 1 or 2
      Novell NE2000
   Therefore, for Netware environments, we recommend using Netware ODI 
   with these two LAN cards.

9. Due to lack of on-card buffering, the following cards do not work well 
   in a dual-stack environment:
       HP27210A/B ThinLAN
       3Com 3C501
   Therefore, we recommend the use of these cards only in a single-stack
   environment, such as standalone.  Their use is not recommended in
   Netware IPX or Netware ODI environments.

10. In the LAN Manager environment, supported LAN cards are any card
    that is certified with Microsoft LAN Manager 2.1 running over TCP/IP.
    For a dual-stack environment (ie MS NetBEUI and HP or MS TCP/IP), 
    supported cards are any card that is certified with Microsoft LAN 
    Manager 2.1 in the same dual-stack environment (ie LM running over 
    NetBEUI and MS TCP/IP simultaneously).

11. Do not use HP Ethertwist Adapter/16 Plus cards in a dual card situation
    with the HP PC ARPA and Network Services software.  Our testing indicated
    a lack of robustness for this configuration with LAN Manager.
       

-----------------------------------------------------------------------------
Demand Loading HP PC ARPA and Network Services 
-----------------------------------------------------------------------------

1. When Demand Loading is chosen, the networking files for HP PC ARPA and 
   Network Services are not loaded automatically.  HP PC ARPA and Network 
   Services provides demand loading BAT files for all its services (ftpd,
   rshd, rcpd, telnetd) that load the networking files and execute the desired 
   service.  The name of the file is the service name with a 'd' (for demand
   loading) added (i.e. ftpd).

--------------------------------------------------------------------------------
Making low density diskettes and installing on a low density PC
--------------------------------------------------------------------------------

1. HP PC ARPA and Network Services allows you to make low density diskettes 
   from a PC which has installed HP PC ARPA and Network Services with a high
   density floppy disk drive.  To make these low density diskettes and to 
   install HP PC ARPA and Network Services  follow these steps:

	- Install HP PC ARPA and Network Services on a PC that has a high
          density diskette drive.
	- Format 4-5 low density diskettes.
	- Use the MS-DOS BACKUP command to copy all the files that have been
          installed on the PC to the low density diskettes.  Be sure to tell
          BACKUP which directory the network has been installed into.
	- Place first low density diskette in the target PC to be installed.
	- Enter command "RESTORE a: c: /s".
	- Enter disks as prompted.
	- Change directories on the hard disk to the directory which contains
          NETSETUP.  NETSETUP can be found in one of the following places:

HP PC ARPA and Network Services 
                (w/ Netware or standalone)  --> C:\HPNET\NETPROG

HP PC ARPA and Network Services 
    (w/ MS Lan Manager 2.1,Enhanced client) --> C:\LANMAN.DOS\NETPROG

	
 HP PC ARPA and Network Services 
      (w/ MS Lan Manager 2.1, Basic client) --> C:\LANMAN.DOS\BASIC
		   
	- Enter command NETSETUP.
	- Use the "Reconfigure Network Software" option from the "Main Menu"
	  of NETSETUP to complete the configuration of the low density PC.

-----------------------------------------------------------------------------
Domain Name Resolution Troubleshooting
-----------------------------------------------------------------------------

If you are using the Domain Name Resolver, you may receive the message
"Remote computername cannot be resolved" or that you entered an
"invalid or unknown host."

You can verify whether the desired remote machine actually is on the
network by running the PING command to the node from another source node.
If PING is able to resolve the computername through DNR, your local PC may
have insufficient resources configured to be able to resolve the name 
consistently.

These resources are managed by the transport and are configurable in the 
TCPIP section of the PROTOCOL.INI file.  You can "tune" the resources to 
allow DNR to work.  You primarily want to increase the number of small buffers
to the point where DNR will work.  (Note that changes to PROTOCOL.INI will not 
take effect until you reboot your system and bring up the network again.)

The following is a typical TCPIP section from a PROTOCOL.INI file (comments 
explaining certain keywords appear to the right of any semi-colons):


[TCPIP]
  DRIVERNAME      = TCPIP$
  IPADDRESS0      = 15 2 112 230
  SUBNETMASK0     = 255 255 248 0
  DEFAULTGATEWAY0 = 15 2 112 1
  TCPCONNECTIONS  = 11			; affects pool size
  TCPWINDOWSIZE   = 1450		;    "     "    "
  TCPSEGMENTSIZE  = 1450
  TCPCONNTIMEOUT  = 30
  TCPKEEPALIVE    = 600
  LOADFACTOR      = 120			;    "     "    "
  LBUFSZ          = 1530
  MBUFSZ          = 600
  SBUFSZ          = 256			; directly affects small buffers
  LBP             = 51			;    "        "    "   "      "
  MBP             = 31			;    "        "    "   "      "
  CLIENTOD        = 6
  CLIENTBD        = 31
  CLIENTMSG       = 20
  CLIENTAMSG      = 10
  IPSOCKETSIZE    = 3
  ARPTBLSIZE      = 28
  BINDINGS = "ELNKII"

You have two ways to increase the number of small buffers:

1.  Increase the total size of the memory pool.  To accomplish this, increase 
only the load factor; do not change the number of connections and the window 
size.  (The load factor is interpreted as a percentage -- in the example above,
it is 120% or 1.2.)  The disadvantage to increasing the load factor is that 
more memory is needed by the transport; less memory will be available for 
applications.  In addition, if you increase it too far, the transport will 
request so much memory that it will not even be able to load.  You want to 
increase the loadfactor just enough to allow DNR to operate properly, but no 
more.  No specific recommendation can be given since the memory requirements
vary depending on how you have configured other parameters.  The size of the
complete memory pool is related to the product of the number of TCP connections,
the TCP window size, and the loadfactor.  

Overall performance should remain stable or may even increase in some cases.

2.  Increase the percentage of the memory pool given to small buffers. Do this 
by decreasing either the values for LBP or MBP, or both.  Within the pool, a
certain percentage is allocated to the large buffers (given by LBP), another
percentage to medium buffers (given by MBP), and the rest to small buffers.
In the above example, 51% of the pool is given to large buffers, 31% to 
medium buffers, and the rest (18%) to small buffers.  (Using the above 
example, decreasing LBP to 41 and MBP to 21 largely eliminated the DNR problem, 
and decreased performance by between 5 and 10 percent in a few large-transfer
cases -- ftp and NetBIOS file copies.  Other applications -- such as telnet -- 
were unaffected.)  The advantage of this method is that the amount of memory 
consumed remains essentially the same as before.

-----------------------------------------------------------------------------
Application Notes
-----------------------------------------------------------------------------

1. Set the HP ARPA Services "Sockets Buffer Pool Size" netsetup parameter to
   9600 when you use VisionWare XVision.  If you do not increase this
   parameter interactive X clients will terminate immediately.

2. When using Lotus 1-2-3 configure the printer interface as a DOS LPT
   device and not a Parallel Port.  Otherwise, print jobs will not be spooled 
   until you exit the application.

3. To use WRQ Reflections with HP PC ARPA and Network Services Services 
   change the Port value to "Bridge" on the Basic Configuration screen.
-----------------------------------------------------------------------------
Unload name change
-----------------------------------------------------------------------------

The name of the unload command has been changed to hpunload.  This is to
avoid confusion with the Microsoft unload command.

------------
HP LAN Manager is based on Microsoft OS/2 LAN Manager and on 3+Open.
MS and Microsoft are registered trademarks of Microsoft Corporation.
3+Open is a trademark of 3Com Corporation.
3Com is a registered trademark of 3Com Corporation in the U.S.
   and other countries.
QEMM-386 is a registered trademark of Quarterdeck Office Systems.
3ComEMM is a registered trademark of Qualitas, Inc.
386MAX is a registered trademark of Qualitas, Inc.
Move'Em is a registered trademark of Qualitas, Inc.

