HP D7171A - NetServer - LPr User manual

1
IBM OS/2 Installation Guide
for all Hewlett-Packard NetServers
NOTICE: The information in this document was last updated for the HP NetServer Navigator CD-ROM version E.10.00 or
L.16.00. If you don't have the E.10.00 or L.16.00 version CD-ROM and you're obtaining this document from the HP NetServer
web site as a reference to install an operating system, be sure to also check the HP NetServer web site for the latest available
drivers.
©Copyright Hewlett-Packard Company
March 19, 1999
(This document is only available in English.)
Introduction
The objective of this document is to help Hewlett-Packard customers install OS/2 on a HP
NetServer system. For additional information on Hewlett-Packard NetServers refer to the HP
Information Assistant on the HP NetServer Navigator CD-ROM.
Table of Contents
Before You Begin
Section 1. Installation Tips and Considerations
Tip 1) Extended Translation Setting
Tip 2) Extending Disk Capacity Beyond 1 GB
Tip 3) Formatting Disk Partitions Larger than 2 GB
Tip 4) Device Allocation Under OS/2
Tip 5) RAM Greater Than 192 MB
Tip 6) Performance Tuning
Tip 7) Troubleshooting System Hangs When Loading CONFIG.SYS
Tip 8) OS/2 Warp Server Installation Issues
Tip 9) How to View the Resources Used by an Adapter
Tip 10) How to Run the HPVGSET.EXE Utility from the Navigator CD-ROM
Tip 11) 4GB RAM Support in OS/2
Tip 12) HPFS386 Drive cache size issue on systems with 4GB RAM
Tip 13) When using HP NetRAID install the driver MRAID.ADD
Tip 14) Getting Trap 00D when booting OS/2
Tip 15) Getting Trap 008 during extensive disk/network I/O
Tip 16) Specific to E Series NetServers: How to boot from a NetRAID adapter while a
2910Bui SCSI card is present on the system
Tip 17) IRQ sharing can cause system hangs
Tip 18) Adaptec driver AIC7870.ADD 133496 12-Jan-1998 or later is required for 2940UW
with rev B chip set

2
Tip 19) Configuring IDE drives as boot device
Tip 20) LPr CD-ROM must be configured as "Non-Listed IDE CD-ROM"
Tip 21) NetServer LH 3 Embeded SCSI and Raid Adapter Configuration
Tip 22) Installing multiple D5013 NICs
Tip 23) "Unable to Access the Hard Drive error" message during OS/2 installation
Tip 24) IBM's Recommended Procedure Installing OS/2 with New AIC78XX.ADD
Tip 25) Fixpak 40 Required for Memory Dump Functionality
Consideration 1: Choose the Booting Controller
Consideration 2: Selecting the Boot Drive Capacity
Consideration 3: Choosing the Boot Drive ID off Embedded Adaptec SCSI
Section 2. Creating the HP Drivers/Utilities diskette
Procedure One
Procedure Two
Section 3. OS/2 CD-ROM Installation Procedures
Installing Warp 3.0 or Warp Conn. 3.0 or Warp Server 4.0
Detailed Procedure for Installing Warp 3.0, Warp Conn. & Warp Server 4.0
Installing Warp 4.0 or Warp Server SMP 4.0
Section 4. Installing Hewlett-Packard NIC's
Installing OS/2 LAN Services for use with the HP J2973A or J2970A 10BaseT PCI LAN
Adapter (CD-ROM)
Installing LAPS Separately
HP J3171A/D5013A PCI Ethernet Adapters
General installation - LAN Server and OS/2 Requester (4.0 or 3.0)
Advanced Settings
Section 5. On-line Information and Software Sources
Before You Begin
It is critical to know which disk adapters or disk array adapter is in the system before you start
the installation. The following table will help you identify what adapter is implemented or
embedded on the system board for each HP NetServer. If you add any additional disk adapter,
please note it on this table for planning purposes.
NOTE: The IBM OS/2 operating systems are not supported on the HP NetServer E series
(E 30, E 40, E 45, E 50, and E 60).
Table 1a
Number Driver Path
of on Drivers SCSI
NetServer Channels Diskette Driver Name
LX 2 \7800 AIC7870.ADD

3
LS 2 \7800 AIC7870.ADD
LH Pro 2 \7800 AIC7870.ADD
LH 2 \7800 AIC7870.ADD
LD Pro 1 \7800 AIC7870.ADD
LC 1 \7700 AIC7770.ADD
LC 2000 2 \SYM897 SYM_HI.ADD
LF 2 \7700 AIC7770.ADD
LM 2 \7700 AIC7770.ADD
LE1NA
E 40 1 \7800 AIC7870.ADD
E 45 1 \7800 AIC7870.ADD
E 50 1 \7800 AIC7870.ADD
E 60 2 \7800 AIC7870.ADD
LPr 1 \sym895 SYM8XX.ADD
LH 3 1 \sym895 SYM8XX.ADD
LH 4 1 \sym895 SYM8XX.ADD
LH 3000 2 \SYM896 SYM_HI.ADD
" 1 \7800 AIC7870.ADD
Table 1b
Driver Path on Navigator SCSI
NetServer CD-ROM Driver Name
LX \periph\adp7800\os2\7800 AIC7870.ADD
LS \periph\adp7800\os2\7800 AIC7870.ADD
LH Pro \periph\adp7800\os2\7800 AIC7870.ADD
LH \periph\adp7800\os2\7800 AIC7870.ADD
LD Pro \periph\adp7800\os2\7800 AIC7870.ADD
LC \periph\adp7700\os2\7700 AIC7770.ADD
LC II \periph\adp7800\os2\7800\ver2.1 AIC7870.ADD
LF \periph\adp7700\os2\7700 AIC7770.ADD
LM \periph\adp7700\os2\7700 AIC7770.ADD
LE NA AHA152X.ADD
E 40 \periph\adp7800\os2\7800 AIC7800.ADD
E 45 \periph\adp7800\os2\7800\ver2.1 AIC7800.ADD
E 50 \periph\adp7800\os2\7800\ver2.1 AIC7800.ADD
E 60 \periph\adp7800\os2\AIC7870.ADD
LPr \periph\adp7800\os2\sym8xx\ver406 SYM8XX.ADD
LH 3 \periph\adp7800\os2\sym8xx\ver406 SYM8XX.ADD
LH 4 \periph\adp7800\os2\sym8xx\ver406 SYM8XX.ADD
Section 1. Installation Tips and Considerations
Tip 1) Extended Translation Setting
Enable "Extended Translation for Drives > 1 GB" in the SCSI-Select utility. To access SCSI-
Select, press Ctrl-A as soon as the Adaptec banner appears while the system is booting. You can
also set this option by using the ECU utility in the advanced mode.
Tip 2) Extending Disk Capacity Beyond 1 GB
For the D2078A/B EISA Fast SCSI-2 Host Adapter, you must enable the extended SCSI
translation feature (support for drives >1 GB) for hard drives with capacities greater than 1 GB,
including the HP D2077A 2 GB Fast SCSI-2 hard drive. Extended SCSI translation uses the

4
logical parameters of 255 heads and 63 sectors to support drives up to about 8 GB in capacity.
Standard SCSI translation, with 64 heads and 32 sectors, is limited to a maximum capacity of
1024 MB (1 GB). You can enable Extended SCSI translation in the BIOS Configuration section
of the EISA Configuration Utility options for the D2078A/B EISA Fast SCSI-2 Host Adapter.
This information also holds true for the embedded AIC7870 SCSI Host Adapter.
Tip 3) Formatting Disk Partitions Larger than 2 GB
If you need to format a disk partition larger than 2 GB, use the HPFS file system. Disk partitions
formatted with the FAT file system (also used by DOS) cannot exceed 2048 MB (2 GB), while
HPFS file system partitions can be as large as 64 GB.
NOTE: Boot drive partitions must be less than or equal to 2 GB, whether you use FAT or
HPFS.
On a hot-swap drive connected to an Adaptec 2940 SCSI adapter, a partition larger than 1024MB
cannot be formatted using the FAT file system. You should either connect hot-swap drives to an
embedded SCSI channel, or create smaller partitions when using the FAT file system.
Tip 4) Device Allocation under OS/2
If you install two device drivers (each using a different device manager) that attempt to access
the same device at the same time, a sharing conflict may result. The OS/2 SCSI device manager,
OS2SCSI.DMD, allocates a device at the drivers' request. Because there is nothing in the ASPI
specification regarding device allocation, OS2ASPI.DMD relies on other device managers to
share devices fairly. Allocation by OS2SCSI.DMD may prevent OS2ASPI.DMD from accessing
the device. For example, a problem could arise if a tape application using OS2SCSI.DMD and
another tape application using OS2ASPI.DMD attempt to access the tape at the same time.
Tip 5) RAM Greater Than 192 MB
In systems with more than 192 MB of RAM, a Trap E may occur during boot after LAN
Services is installed. To avoid this problem, do not select auto cache size for the HPFS file
system during installation of LAN Services. HP recommends an HPFS cache size of 16 MB or
less.
If this problem persists, boot from the OS/2 installation diskettes, exit to a command prompt, and
edit the CONFIG.SYS file. (You may have to copy the CONFIG.SYS file to a floppy disk, edit it
on another system, and then copy it back.) Ensure that the line starting with IFS= near the
beginning of the file contains the parameter /C:16000. An alternative is to remove RAM so that
the system has less than 192 MB, reboot and reconfigure LAN Services, and then shut down and
reinstall the RAM.
Tip 6) Performance Tuning
IBM publishes a performance White Paper, OS/2 2.1 Performance Tuning for End Users, that

5
provides information on improving the performance of OS/2 systems. Contact IBM for more
details.
Tip 7) Troubleshooting System Hangs When Loading CONFIG.SYS
Reboot the system. When the "OS/2" prompt appears in white text at the upper left portion of the
screen, press the Alt and F2 keys simultaneously. Read the driver name on the bottom of the
display as they are loaded. The last driver displayed may be the one causing the system hang.
Try booting from diskette to edit CONFIG.SYS and remark out (using REM) the suspect driver.
Tip 8) OS/2 Warp Server Installation Issues
If you are installing OS/2 Warp Server, you may see one or more of the following messages
while the system is rebooting during installation. If so, follow the instructions below to complete
the installation of OS/2 Warp Server.
Issue 1: The CD-ROM drive is not readable.
Fix: Add the following line to the CONFIG.SYS file on the drive on which OS/2 Warp Server is
being installed:
IFS=x:\CDFS.IFS /Q
where xis the drive where OS/2 is being installed.
Issue 2: The system cannot create the DOS environment because of a faulty video driver.
Fix: Add the following line to the CONFIG.SYS file on the drive where OS/2 Warp Server is
being installed:
DEVICE=x:\OS2\MDOS\VVGA.SYS
where xis the drive where OS/2 is being installed.
Issue 3: A Trap D occurs in device driver SINGLEQ$.
Fix: Reboot the system. When the "OS/2" prompt appears in white text at the upper left portion
of the screen, press the Alt and F1 keys simultaneously. A screen of options appears. Press the
<v> key to reset the video to VGA mode. The system will reboot automatically.
Issue 4: System hangs during loading CONFIG.SYS
Troubleshooting process: Reboot the system. When the "OS/2" prompt appears in white text at
the upper left portion of the screen, press the Alt and F2 keys simultaneously. OS/2 will display
the driver that has been loaded at the bottom of the screen. This will help you identify the last
driver loaded when the system hangs. You can remark the suspect driver to isolate the reason for
the system hang.
Issue 5: System hangs with a GUI display indicating that system configuration is being updated.

6
Fix: This is caused by the wrong AIC7870.ADD driver. It is possible that you skipped one of the
steps where the driver and CONFIG.SYS are updated either manually or by using the
UPDATE.EXE utility.
Issue 6: After the first auto-reboot during the file and print installation section the system may
stop with an error when loading drivers in CONFIG.SYS the error will read like this "Invalid
path specified in line xy c:\cid\...".
Fix: This error usually occurs because the CD-ROM driver is not present in CONFIG.SYS.
Reboot the system. When the white box appears in at the upper left portion of the screen, press
Alt and F1 keys simultaneously. A screen of options appears. Press the <c> key to boot the
system to the command prompt. Edit CONFIG.SYS and add the embedded SCSI driver to enable
the CD-ROM for example:
BASEDEV=AIC7870.ADD
Issue 7: After Installing OS/2 2.11 for SMP on a Hewlett-Packard NetServer LS the system
hangs and traps intermittently.
Fix: If you have a dual-processor card installed, edit the CONFIG.SYS file on the root directory
of the hard drive where OS/2 is installed. (Note that this only applies to systems with a dual
processor card installed.) Change the line:
PSD=OS2APIC.PSD
to:
PSD=OS2APIC.PSD /APIC
Issue 8: After completing the OS/2 installation on a NetServer E40, the CD-ROM can not be
accessed by the system. Also, when you open the Drives object folder the CD-ROM object is not
present.
It is possible that during installation you did not select "Non-Listed IDE CD-ROM" as
recommended in the installation procedure. You can resolve this issue by editing CONFIG.SYS
to add the following line and then rebooting the system.
BASEDEV=IBMIDECD.FLT
Tip 9) How to View the Resources Used by an Adapter
The Navigator CD-ROM version G.00.10 or greater has a utility that will display the resources
used by an adapter. Use the following procedure to get the resource listing:
1) Boot Navigator CD-ROM
2) Select "Configuration Assistant"
3) Select "Custom Configuration"

7
4) Select "IBM OS/2"
5) Select "Warp Family"
6) Select "Continue"
7) Select "Show Configured Card"
8) Select "View Resources" It shows a table with the following column headings:
SLOT IRQ DMA MEMORY I/O PORTS
9) Select "Save to Disk" note that there is no printer support for the Navigator
10) Select "Continue"
11) Select "Continue"
12) Select "Exit"
13) Print the information saved to diskette in step 9 if you want a hard copy
Tip 10) How to Run the HPVGSET.EXE Utility from the Navigator CD-ROM
To run the HPVGSET.EXE utility from diskette you must create a driver diskette from the
Navigator diskette library section. Boot PC to DOS and type:
hpvgset.exe
1) Boot Navigator CD-ROM
2) Select "Configuration Assistant"
3) Select "Custom Configuration"
4) Select "IBM OS/2"
5) Select "Warp Family"
6) Select "Continue"
7) Select "Execute Card Utilities"
8) Select "Exit" when done.
Tip 11) 4GB RAM support in OS/2
Warp Server SMP 4.0 is the only version of IBM OS/2 that supports 4GB of RAM.
Warp Server 4.0 works fine with a max of 1GB. We experienced system hangs at the Warp red
logo when booting a NetServer LX with 4GB RAM running Warp Server 4.0

8
Tip 12) HPFS386 Drive cache size issue on systems with 4GB RAM
The installation procedure of IBM OS/2 defaults to calculating the disk cache size based on the
amount of memory installed on your system. It appears that this calculation does not work
properly when the system has a 4GB of RAM installed. In this case the disk cache is set to the
lowest value of 256K. Hewlett-Packard reported this issue to IBM. As a workaround you can
edit the file C:\IBM386FS\HPFS386.INI. Locate the line that reads "cachesize=256". This means
that the cache is set to 256K bytes. You can read the text provided below this line to determine
which is the best value to use. Please keep in mind that this parameter will impact your system
performance.
Tip 13) When using HP NetRAID install the driver MRAID.ADD
If you are using a HP NetRAID it is possible to complete the installation of OS/2 using the IBM
IBMINT13.I13 driver provided on the Diskette1. This generic driver has limitations on the
number of drives and on the maximum drive size that it can handle. For example in our test
IBMINT13.I13 showed a limit of 8 drives and a maximum drive size of 8Megabyte.
Tip 14) Getting Trap 00D when booting OS/2
We have observed situations where these traps during system boot are cause by a device driver.
The following is a list of things to check:
1) Verify that you don’t have a duplicate driver name in your config.sys. For example the
HPDA.ADD driver is provided by IBM in the OS/2 CDROM under the name DAC960.ADD.
Hewlett Packard recommends that you use the HPDA.ADD driver unless there is a specific
reason why you must use the DAC960.ADD driver.
2) If you are using the Netfinity server management tools it installs a driver called
NFDASD.FLT. The Hewlett Packard NetRAID driver MRAID.ADD version 1.06 ( date:
11/05/96 size: 24430) has a compatibility issue with the NFDASD.FLT driver. The new driver
MRAID.ADD version 1.07 (date: 1/30/97 size: 24624) resolved this problem. There are two
ways to verify if this old driver is causing your problem. (a) Place a Remark in front of the
NFDASD.FLT driver. (b) Replace the MRAID.ADD driver with the IBMINT13.I13 driver. If
one of these two steps resolves the Trap D while booting then obtain the new MRAID.ADD
driver immediately.
Tip 15) Getting Trap 008 during extensive disk/network I/O
It is possible to experience intermittent Trap 008 during extensive disk/network data transfer
when using the following configurations:
Configuration #1:
Four NIC's of any topology
Two HP NetRAID disk array cards with drives connected to all three ports

9
Configuration #2:
Four HP NetRAID disk array cards
Two NIC's
To resolve this issue ServicePack 29 is required. You can obtain this update by contacting your
IBM representative.
Tip 16) Specific to E Series NetServers: How to boot from a NetRAID adapter
while a 2910Bui SCSI card is present on the system
The following steps are involved during system boot to install boot partition on NetRAID
adapter disk arrays.
1. Disable Host Adapter BIOS by using <Ctrl A> during boot-up. Host Adapter BIOS
settings are within SCSI Select utility -> Advanced Control Options.
2. Apply consideration number one listed below to keep the appropriate boot order.
Tip 17) IRQ Sharing can cause system hangs
Avoid sharing IRQ’s between NICS, between HBA and DAC to avoid hang problems caused
during heavy system usage.
Tip 18) Adaptec driver AIC7870.ADD 133496 12-Jan-1998 or later is required
for 2940UW with rev B chip set
We have seen intermittent hangs caused by the AIC7870.ADD driver. The problem can happen
with any version of the Adaptec adapter that uses this driver. However, the problem is more
pronounced with an Adapter that has Rev B of the 7870 chip. Hewlett Packard recommends that
you use the driver dated 12-Jan-1998 or later.
Tip 19) Configuring IDE drives as boot device
When installing an IDE drive on your E series NetServer you must follow the following notes.
1. You must order an IDE cable 5183-2103 which is not included with the system.
2. The IDE drive must be the boot drive.
3. The boot partition must be less than 2GB.
4. It is possible to install a boot-manager utility on the IDE drive and the target NOS on a SCSI
drive.
5. When Installing OS/2 on a Quantum 4.3GB (Fireball) drive the drive capacity reported by
FDISK is 57MB. IBM is aware of this issue. Please contact IBM’s web site for a driver
update. This issue was experienced with driver IBM1S506.ADD 54326 26-Jan-1996.

10
6. The default IDE configuration is usually set to automatic which reports the following
parameters:
Cyl = 14848
Head = 9
Sector = 63
Workaround: Run setup to apply the following IDE configuration values:
Cyl = 8174
Head = 16
Sector = 63
Final Fix: Contact IBM or connect to the following web site to obtain the new IBM IDE
driver:
http://service.software.ibm.com/os2ddpak/html/os_2comp/
Tip 20) NetServer LPr, LH 3 and LH 4 CD-ROM must be configured as
"Non-Listed IDE CD-ROM"
When installing OS/2 Warp Server make sure you configure the CD-ROM as "Non Listed IDE".
Otherwise you may experience system hangs after the second reboot during the installation
process. Also, see issue number seven listed above.
Tip 21) NetServer LH 3 Embeded SCSI and Raid Adapter Configuration
The Hewlett Packard NetServer LH 3 can be configured to use either SYM8XX.ADD or
MRAID.ADD or both cuncorrently. See Tip 13 listed above and Consideration 3 listed below for
information related to installing OS/2. Consult the NetServer user’s guide for information on
how to configure the embeded SCSI or Raid ports.
Tip 22) Installing Multiple D5013 NICs
If you are installing more than one PCI adapter:
1. Complete the configuration process with the MPTS configuration utility, but leave the Slot
field blank for each driver;
2. Restart the system and record the list of Slots that each driver displays;
3. Complete the configuration by assigning one of the values from the list to the Slot parameter
of each driver. Leave the field blank if you have only one adapter installed.

11
Tip 23) "Unable to Access the Hard Drive" error during the OS/2 installation.
(Also, see Tip #24)
This error usually occurs due to one of the following reasons.
1. The basedev stament for the target driver is not present in config.sys.
2. The target disk driver is not present on diskette one. For example there is a new Adaptec
driver aic7870.add required for new systems that support Ultra Wide SCSI like in the
NetServer E 60. In this case you must replace the original driver on the diskette #1 with the
aic7870.add driver provided on the Navigator CD-ROM (See the section called "Creating the
Driver’s Diskette" listed above.).
3. Even after you apply the proper driver as listed on step 2, the installation can fail with the
"Unable to access hard drive" error message after the first or second reboot. This happens
because the installer copies the old driver from the OS/2 CD-ROM to the hard drive. To
address this problem you must either boot from diskette or use the F3 or (Alt-F1) key to get
to the command prompt. Next copy the new driver to the boot drive. Please note that this
driver must be copied to the root and to the \os2\boot directory. For example:
a:> copy a:\aic780.add c:\aic7870.add
a:> copy a:\aic7870.add c:\os2\boot\aic7870.add
Tip 24) IBM's Recommended Procedure Installing OS/2 with New
AIC78XX.ADD
Follow this Warp Connect and Warp V4 procedure for installing OS/2 whenever the Adaptec
7800 Family Manager Set v2.1 for OS/2 driver is required for the boot drive.
1. Type cdinst from CDROM drive to create the boot diskettes.
2. Remove the following files from Disk 1
aha152x.add
aha154x.add
aha164x.add
aha174x.add
aic7770.add
aic7870.add
3. Rename the new Adaptec driver to AICNEW.ADD and copy to Disk 1.
4. Note: Follow this step only if installing Warp V4
Remove the file called bundle from Disk 2 and copy aicnew.add to Disk 2.
5. Edit config.sys (In Disk 1) and remark out the basedev statements for all of the above deleted
drivers.

12
6. Add a new Basedev statement in config.sys
BASEDEV=AICNEW.ADD
7. In config.sys make sure the following statement is present
SET SAVECONNECT=1
By default, this statement is inserted by cdinst.
8. At the end of installation, aicnew.add gets copied to the root partition of the boot drive, and
the config.sys will have a corresponding BASEDEV statement. You can choose to copy this
driver to the c:\os2\boot directory. Do not rename this driver back to AIC7870.ADD.
Reference:
http://service.software.ibm.com/os2ddpak/html/FCF6C3F9EF462CCC86256449006F9599.html
Tip 25) NetServer E 60 - Fixpak 40 Required for Memory Dump
Functionality
The Fixpak 40 is required to be able to take a memory dump on the E 60 running Warp Server
SMP 4.0. If you don’t apply this fixpack the system will hang with a character mode display
indicating that a memory dump will be taken. To recover from this mode you have to power off
and on.
Considerations
Before installing OS/2 you must keep in mind the following considerations
Consideration 1: Choose the Booting Controller
If you are using multiple disc controllers it is important to determine which is going to be the
boot controller since OS/2 uses the order or sequence of the "BASEDEV= xxxx.yyy" driver
definition statement in CONFIG.SYS to determine the drive letter assignment. The first
BASEDEV declared in CONFIG.SYS will be assigned to the boot drive. For clarity purpose it
helps to place the "BASEDEV= xxxx.yyy at the beginning of CONFIG.SYS. It is recommended
that you remove the IBMINT13.I13 from config.sys when using NetRaid or SCSI drivers.
It is also important to pay attention to system specific boot ordering. Many systems bios setup
programs allow the user to set the boot priority of the disk controller(s).
NOTE: You must create a partition < 2GB for the boot drive. (See Tip 3)
Please complete the following table for planning purposes:
Table 2a
Driver
Adapter Driver Name Provider

13
Embedded Adaptec AIC7870.ADD HP
Adaptec 2740A AIC7770.ADD HP
Embedded IDE IBM1S506.ADD IBM
HP DAC Adapter HPDA.ADD HP
HP NetRAID MRAID.ADD HP
HP Symbios SYM8XX.ADD HP
Embedded NetRAID MRAID.ADD HP
Other NAME.ADD
Table 2b
Boot Adapter BOOT Drive Size
Adapter (YES/NO) XMbytes and Notes
Embedded Adaptec
Adaptec 2740A
Embedded IDE
HP DAC Adapter
HP NetRAID
Other
NOTE: When you are configuring the hardware, make sure that the booting controller
will take precedence over any other devices that may be bootable. Both the User Guide
for your NetServer and the Installation Road Map contain lists showing the boot device
priorities for all of the slots and embedded controllers in the system. The hardware and
the operating system must agree as to which controller is the booting controller.
Consideration 2: Selecting the Boot Drive Capacity
If you are installing OS/2 onto a drive connected to a Disk Array Adapter (for example the HP
DAC or HP NetRAID) or connected to a very large hard drive, you should create a logical disk
smaller than 2047 MB on which you will install OS/2. While running the Navigator utility during
system configuration. You can run the appropriate utility to setup the disk array adapter. The
disk array setup utilities are JetSet for the HP DAC and the "NetRAID Assistant" for the HP
NetRAID. These utilities will help you set logical disk sizes in the Disk Array configuration
process.
To ensure that the OS/2 boot partition is not larger than 2047 MB, create at least two logical
drives with the disk array setup utility. Create the first logical drive to less than or equal to 2047
and the second for the rest of the available space. Install OS/2 on the first logical drive, and use
the other logical drive(s) for all applications and data.
If OS/2 must be added to an existing logical drive configuration of the disk array, use FDISK
during OS/2 installation to create an installable partition within the first 2GB of an existing
logical drive. Use the other partition(s) for applications and data. You can use this same
procedure to partition a large drive when installing OS/2 to a large drive connected to the
embedded SCSI.
Consideration 3: Choosing the Boot Drive ID off Embedded Adaptec SCSI
If you are installing OS/2 onto a drive connected to the embedded Adaptec SCSI controller or a
non-disk array SCSI adapter, make sure that the drive has the lowest SCSI ID, or install Boot

14
Manager on the drive with the lowest SCSI ID. The system will boot from the drive with the
lowest SCSI address among the drives connected to the first controller in the boot order. HP
recommends SCSI ID 0 for the boot drive. If you configure the boot drive with another SCSI ID,
your system may not boot when additional SCSI drives are installed later.
Section 2. Creating the HP Drivers/Utilities Diskette
The "Drivers/Utilities" diskette is referred to in the HP NetServer Navigator CD-ROM and other
HP documentation as the "Drivers Diskette." The purpose of this diskette is to accomplish the
following three tasks:
Task 1) To backup one (or more) of your OS/2 installation diskettes. For OS/2 Warp and later
products, only Diskette 1 is backed up. We will refer to this backup copy of OS/2 Diskette 1 as
the "Work Diskette 1". When you install OS/2, you will use the backup copies in place of the
original diskettes that came in the OS/2 box.
Task 2) Identify the unused drivers on "Work Diskette 1" to make room for new drivers. Delete
the unwanted drivers from the "Work Diskette 1".
Task 3) Identify the required drivers for the system. Based on the boot setup the following
drivers may be needed. Example:
AIC7870.add
SYM8xx.ADD
MRAID.ADD
AIC78U2.ADD
Make a list of drivers that are neede and order them based on boot priority.
Task 4) Create HP Drivers/Utility Diskette by stepping through one of the following procedures.
There are two ways to create the drivers diskette.
•Podedure One: Uses the OS/NOS icon section of the Navigator CDROM.
•Pocedure Two: Uses the "Library diskette" section of the Navigator CDROM.
NOTE: Starting March 1997 the OS/2 drivers were split into two diskettes as follows.
Diskette #1: Contains the SCSI - DAC drivers and utility. Diskette #2: Contains the NIC
drivers.
Procedure One
1. Boot with the HP Navigator CD-ROM.
2. From the Main Menu, select "Configuration Assistant".
3. Select Custom.

15
4. Select OS/2.
5. From the menu, select the version of OS/2 that you want to Install. Select "Warp 3.0"
for any version of Warp that you want to install. (Starting with Navigator CD-ROM
version G.00.10 this selection button is called "Warp Family".
6. Read the information provide on the "Configuration Advisor" panel. Save it to disk if
you desire.
7. Select Continue.
8. From the "Custom Configuration" menu select "Create Drivers Diskette".
Starting March 1997 the OS/2 drivers were split into two diskettes as follows.
Diskette #1: Contains the SCSI - DAC drivers and utility.
Diskette #2: Contains the NIC drivers.
To create the Driver Diskettes:
A) Select "COPY ALL" to create the two driver diskettes.
B) Insert Diskette when prompted and follow the instructions.
C) Click exit when done.
D) Click Yes, to reboot the system
9. Label a blank diskette "HP NetServer IBM OS/2 Warp Drivers/Utilities Diskette".
Insert this diskette in drive A and select "Execute".
10. Remove the HP Navigator CD-ROM. Keep the newly created "Drivers/Utilities"
diskette in the floppy drive.
11. Click on Exit. Select Yes to reboot system. Continue to Task 5.
Procedure Two
This is an alternate procedure for Creating the "Drivers/Utilities" diskette using a section
called "Diskette Library" on the Navigator CDROM.
The following example lists the steps required to create the two drivers diskette for a
NetServer E 40. The same steps apply to other models.
NOTE: Starting March 1997 the OS/2 drivers were split into two diskettes. Diskette
#1: Contains the SCSI - DAC drivers and utility. Diskette #2: Contains the NIC
drivers
Keep in mind that if you need high resolution video, you will need to create a third video
driver's diskette.

16
Use this procedure to create a "Drivers/Utilities" diskette using the "Diskette Library" on the
Navigator CDROM:
1. Boot Navigator
2. Click. NetServer Utilities
3. Click, More Utilities
4. Click, Diskette Libraries
5. Select "NOS Drivers - OS/2 Warp Family" and then click execute (see the following
note).
NOTE: Only "OS/2 Warp Family" is supported on the E40. There is no
OS/2 2.11 support for the E40.
6. Select "COPY ALL" to create the two driver diskettes. If you wish to make only one
diskette just select the one you need from the list provided on the screen. You can
create the video driver by selecting video from the list provided on the screen.
7. Insert Diskette when prompted and follow the instructions.
8. If needed, create the video driver by following the same procedure.
9. Click exit when done.
10. Click Yes, to reboot the system. Continue to Task 5.
Task 5) Copy the required drivers (which are identified in Task3) from "HP Diskette #1: SCSI -
DAC drivers and utility" to the "Work Diskette 1".
Task 6) Edit Config.sys file in "Work Diskette 1" to include the drivers entry which are added in
Task 5 and delete drivers entry which are removed in Task 2.
Task 7) Include "set copyfromfloppy=1" as the first line in config.sys in "Work Diskette 1" to
allow the installation process to copy drivers from floppy than from OS/2 Installation CDROM.
Section 3. OS/2 CD-ROM Installation Procedures
Be sure to check the considerations and tips listed above before starting the installation process.
Also, complete the planning table listed in "Consideration 1".
Note that this document was written using the Adaptec driver AIC7870.ADD. However if your
system uses a different SCSI driver, just use your driver name in place of the one listed in this
document. For example, since the HP NetServer LC uses the AIC7770.ADD driver, you must
replace the AIC7870.ADD driver entry with AIC7770.ADD everywhere in this document.
On the following pages you will find separate procedures for:

17
•Installing OS/2 Warp 3.0, OS/2 Warp Connect 3.0 and Warp Server 4.0
•Installing OS/2 2.11 for SMP
•Installing Service Pack S.631 (or later) manufacturing refresh for OS/2 2.11 for SMP
Installing Warp 3.0 or Warp Conn. 3.0 or Warp Server 4.0
Overview for Installing Warp and Warp Connect
If you are an experienced OS/2 user you can follow this overview to complete the product
installation. However Hewlett-Packard recommends that you follow the detailed step by step
process to complete the installation. The installation process for Warp 3.0, Warp Connect 3.0 or
Warp Server 4.0 consists of five phases.
Please read the information provided in Section 1 of this document before starting the
installation.
Phase 1: Create copy of IBM "Diskette 1" label it "Work Diskette 1"
1. Create the Drivers/Utilities diskette using the HP Navigator CD-ROM. (See "Section 2" of
this document.)
2. Create a copy of IBM "Diskette 1" and label it "Work Diskette 1".
Phase 2: On "Work Diskette 1" update CONFIG.SYS and copy new drivers
3. Edit CONFIG.SYS on "Work Diskette 1" to add the HP SCSI and driver for disk array
adapter if one is present.
4. Copy required drivers to "Work Diskette 1".
Phase 3: Start Installation
5. Start installation of OS/2 using IBM "Installation" Diskette and the IBM OS/2 CD-ROM.
6. Insert "Work Diskette 1" when prompted for IBM Diskette 1.
7. Continue the Installation process as suggested on the Install screen.
Detailed Procedure for Installing Warp 3.0, Warp Conn. & Warp Server 4.0
NOTE: If you completed all the steps listed above in "Section 2," then you can skip
Phase 1 and 2 listed below. You can go to Phase 3, step 5.
Introduction
In this section you will see some steps that precede a section called "Manual Process". The intent
is that if you run into any errors or issues with the automatic / utility procedure you can try using
the "Manual Process" to circumvent any issues or to troubleshoot the error. Also if you are a

18
power user, it is OK to use the "Manual Process" to complete the installation.
Phase 1: Create copy of IBM "Diskette 1" label it "Work Diskette 1"
1. Create the Drivers/Utilities diskette using the HP Navigator CD-ROM.
Follow the steps described in "Section 2" of this document.
2. Create a copy of IBM "Diskette 1" and label it "Work Diskette 1".
Follow the Step by Step procedure described in Section 2 of this document.
Manual Process:
You can also use a spare PC running DOS, OS/2 or NT to make a copy of the original IBM
Diskette. Label your copy diskette "Work Diskette 1". Insert master IBM "Diskette 1" in
drive A and enter the following command:
DISKCOPY A: A:
Phase 2: On "Work Diskette 1" update CONFIG.SYS and copy new drivers
3. Edit CONFIG.SYS on "Work Diskette 1" to add the HP SCSI and driver for disk array
adapter if one is present.
Follow the step-by-step procedure described in Section 2 of this document.
Manual Process:
You can also use a spare PC running DOS, OS/2 or NT to complete the following tasks.
Please read "Consideration 1" in Section 1 of this document and complete the table in that
section before you proceed with this step.
A) If you have an HP DAC, add three lines to the start of CONFIG.SYS as follows:
basedev=ibm1s506.add
basedev=hpda.add
basedev=aic7870.add
If you have an HP NetRAID, add three lines to the start of CONFIG.SYS as follows:
basedev=ibm1s506.add
basedev=mraid.add
basedev=aic7870.add
B) While editing CONFIG.SYS locate and delete any lines that look like the one's you've

19
already added which are calling the same drivers. You don't want duplicate driver names.
This can cause Trap 00D or Trap 00E during the OS/2 boot process.
C) While editing CONFIG.SYS on the "Work Diskette 1". Locate the section with all the
IBM type 2 drivers, they will read as follows...
basedev=ibm2flpy.add
basedev=ibm2adsk.add
basedev=ibm2scsi.add
You will need to remark out these lines by adding the REM command so they read as
follows...
REM basedev=ibm2flpy.add
REM basedev=ibm2adsk.add
REM basedev=ibm2scsi.add
D) While editing CONFIG.SYS file, locate the Adaptec drivers section with the following
Adaptec driver lines:
basedev=aha154x.add
basedev=aha164x.add
basedev=aha174x.add
You will need to remark out these lines by adding the REM command so they read as
follows...(make sure you have no need for any of these drivers before implementing this
step).
rem basedev=aha154x.add
rem basedev=aha164x.add
rem basedev=aha174x.add
4. Copy required drivers to "Work Diskette 1"
Follow the Step by Step procedure described in Section 2 of this document.
Manual process:
You can also use a spare PC running DOS, OS/2, or NT to complete the following tasks:
A) Create a temporary directory on the hard disk of the workstation you are using, by
entering the following commands (if you created the C:\HPTEMP directory in step 13 of
"Section 2" then skip the MD HPTEMP command):
C:

20
MD HPTEMP
CD HPTEMP
B) Insert the "Drivers/Utilities" diskette in drive A of the workstation, and enter the
following copy commands:
COPY A:\7800\AIC7870.ADD
COPY A:\7700\AIC7770.ADD
COPY A:\HPDA\HPDA.ADD
COPY A:\NETRAID\MRAID.ADD
COPY A:\UPDATE.EXE
C) Remove the Drivers Diskette from drive A, and insert the "Work Diskette 1". Delete the
following files to make room on "Work Diskette 1" for new drivers by entering the following
commands:
DEL IBM2FLPY.ADD
DEL IBM2ADSK.ADD
DEL IBM2SCSI.ADD
DEL AHA*.ADD
Copy new drivers to "Work Diskette 1," by entering the following command:
COPY *.* A:\
You may delete all the files in the C:\HPTEMP directory and also delete the C:\TEMP
directory.
Now you are ready to start the OS/2 Installation.
Phase 3: Start Installation
5. Start installation of OS/2 using IBM "Installation" Diskette.
To begin installing OS/2 Warp or OS/2 Warp Connect, place the Installation Diskette in
drive A, insert the IBM OS/2 CD-ROM and boot the system.
6. Insert "Work Diskette 1" when prompted for IBM Diskette 1.
When you are prompted to insert Diskette 1 and press Enter, insert the copy of "Work
Diskette 1" created with the Drivers/Utility diskette, then press Enter. An OS/2 logo appears,
and after some time you will see a screen titled "Welcome to OS/2". Press Enter again to
continue.
Select "Advanced Installation" if you want to partition your drives. Follow the prompts to
create partitions as needed.