1. pushhptx.exe Driver
2. HP_PUSH.TXT File Contents

HP_PUSH.TXT Driver File Contents (pushhptx.exe)

Windows 95 Push Installation with Microsoft Client                   v1.0
     
     
Files Used
----------
PUSH\NETJ3171.INF        INF install file for the HP 10/100 TX drivers 
PUSH\MSBATCH.INF         INF configuration file used for PUSH install
     
Overview
--------
This process requires advanced network administration skills. You should be 
thoroughly familiar with Windows 95 setup procedures in a network environment 
prior to performing the push installation.
     
These files are sample configuration files that allow a basic
Windows 95 unattended push installation using the HP 10/100 TX with the NDIS3 
miniport driver.  The push installation allows Windows 95 to be installed 
from a Network server.  This assumes that the Windows 95 source files have 
been copied to the server using the NETSETUP.EXE utility.  For more 
information on NETSETUP.EXE see the Windows 95 Resource Kit, Chapter 4.
     
     
General Instructions
--------------------
     
1. Integrate the above NETJ3171.INF to your Windows 95 source files on the serve
r. 
   Replace the NETJ3171.INF file on the HP 10/100 TX support disk
   with the NETJ3171.INF file included in this archive (you may want to rename 
   the original NETJ3171.INF to save it).  Run the INFINST.EXE utility.
   When asked for an INF file, insert the HP 10/100 TX support disk and point
   to the NETJ3171.INF. This process integrates the HP 10/100 TX driver files in
to
   the Windows 95 source on the server.  For more information on the INFINST.EXE
     
   utility  see Chapter 5 of the Windows 95 Resource Kit.
     
2. Go to the root directory where the Windows 95 source files reside, 
   and rename the existing MSBATCH.INF to MSBATCH.BAK. Copy the
   MSBATCH.INF located in this archive (PUSH\MSBATCH.INF) to the root directory 
   of the Windows 95 source on the server.  When you run SETUP,  it will use 
   this MSBATCH to control the setup.
     
3. Once you have a basic push install then modify the MSBATCH.INF as
   you desire. For more information on MSBATCH please see the Microsoft 
   Resource Kit, Chapter 5 and Appendix D.
     
     
============================================================================ 
Windows 95 Push Installation with Novell's Client 32   
     
Files used
----------
PUSHCL32\NETJ3171.INF     INF install file for the HP 10/100 TX drivers 
PUSHCL32\MSBATCH.INF      INF configuration file used for PUSH install 
PUSHCL32\PUSHFIX.EXE      Executable for Client 32 fix
     
Overview
--------
These files address a problem in the Novell Client 32 installation. This 
fix keeps the entire push installation fully automated.
     
This assumes that the server has been setup for Windows 95 push installation 
and the Novell Client 32 installation files has been integrated into the 
base Windows 95 push installation files on the server. (See Novell Technical 
document TID2905964 for more information). This routine will ensure that
the registry entry STATICVXD=NWLINK2.VXD is set correctly to allow
the HP 10/100 TX Windows 95 workstation running Client 32 to attach to 
NetWare server.
     
With out this patch the registry entry will be set to STATICVXD=NWLINK.VXD 
which will prevent the workstation from attaching to a NetWare server.
     
     
General Instructions
--------------------
     
1. Add/Merge the lines below to your MSBATCH.INF.
     
[Install]
addReg=fixcl32.Reg
     
[fixcl32.Reg]
HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce,,,"FIXCL32.EXE"
     
NOTE: We recommend using the example MSBATCH.INF included in the archive.
      It's been modified specifically for the HP 10/100 TX adapter.
     
2. Add/Merge the lines below to the push install version of NETJ3171.INF
     
[PCIe100B.ndi]
CopyFiles=fixcl32.install
     
[fixcl32.install]
fixcl32.exe
     
[DestinationDirs]
fixcl32.install=10
     
NOTE: The sample NETJ3171.INF in this archive has incorporated these changes.
     
     
3. Integrate the above NETJ3171.INF to your Windows 95 source files on the serve
r. 
   Replace the NETJ3171.INF file on the HP 10/100 TX adapter support
   disk with the NETJ3171.INF file included in this archive (you may want to 
   rename the original NETJ3171.INF to save it).
     
   Run INFINST.EXE.  When asked for an INF file, insert the HP 10/100 TX support
    disk and point to the NETJ3171.INF. For more information on the INFINST.EXE
   utility, see Chapter 5 of the Windows 95 Resource Kit
     
4. Copy the FIXCL32.EXE file to your server Windows 95 installation directory.
   (Ex. Z:\PUBLIC\WIN95 and Z:\PUBLIC\WIN95\SYSTEM)
     
5. Update LAYOUT.INF to tell Windows 95 Setup the location
   of FIXCL32.EXE to automate this. The line in LAYOUT.INF for FIXCL32.EXE 
   should look like this:
     
        FIXCL32.EXE=1,,11
     
   Update all 3 LAYOUT.INF locations:
   (ex. Z:\PUBLIC\WIN95, Z:\PUBLIC\WIN95\SYSTEM, Z:\PUBLIC\WIN95\SUWIN)
     
     
NOTE: Currently, the Windows 95 Push installation with Novell Client 32 will
      only work using the NDIS driver.
     
     
============================================================================= 
Additional Information
     
If you have devices on your system that Windows 95 is being installed on, 
such as a sound card or CD ROM, it may be necessary to ensure that
Windows 95 scans for these devices and pushes them before the first reboot. 
This can be done by using a SETUP.EXE command with the /p c option for class 
detection or /p c- to disable safe class detection and do the most complete 
examination. For more information about setup switches see the Microsoft 
document Q-128400, Windows 95 Setup Switches.
     
Example: SETUP /p c
This switch enables class detection. Class detection is a mechanism 
for finding hints for a certain class of devices. For example, adapter 
class detection looks for hints in the config.sys and system.ini files 
for CD-ROM drivers. If it does not find any, Setup displays a CD-ROM 
check box asking if you have a CD-ROM drive.
     
The default during Setup is enabled. The default when you use the 
Add New Hardware tool and docking/undocking detection is disabled.
     
Example: setup /p c-
Setup /p c- disables safe class detection. For example, this switch 
tells Setup to always search on all network adapter cards, sound 
cards, and CD-ROM drives.