44.891 bytes |
Preloaded Software Information |
Document ID: DDSE-3VKP3N |
Netfinity 5500 / 5500 M10 - Installing OS/2 Warp Server v4.0 Advanced SMP
Applicable to: World-Wide
Revision: 1.00
Updated: 6/10/98
Follow the Network Operating System (NOS) instructions provided in this document sequentially unless you are instructed differently. Windows and messages might differ from those in this document.
This document contains the following:
1.0 What You Will Need
2.0 Where to Download Device Drivers/Files
3.0 Quick Installation Instructions for Experienced Users
4.0 Detailed Installation Instructions
4.1 Setting Up the Hardware for NOS Installation
4.2 Setting Up the BIOS
4.3 Configuring Arrays Using the Integrated PC ServeRAID II Adapter
4.4 Running the OS/2 Warp Server v4.0 Installation Program Using the Integrated PC ServeRAID II
Appendix A: Installing FixPak 35, MPTS FixPak WR08504, and LANServer FixPak IP08506 on OS/2 Warp Server v4.0 Advanced SMP
A.1 Where to Find FixPak 35 and Related Necessary Fixes
A.2 Where To Find CSF (Corrective Services Facility)
A.3 Creating FixPak Diskettes
A.4 Installing FixPak 35 (OS/2 Warp Server Advanced 4.0 FixPak XR_W035)
A.4.1 Before Installing
A.4.2 Installing from a Booted OS/2 Partition
A.5 Installing MPTS FixPak WR08504
A.6 Installing LANServer FixPak IP08506
A.7 Backout Instructions
Appendix B: Installing the S3 TRIO V2/GX Device Driver
Appendix C: Installing the Advanced Service Processor Adapter Driver
1.0 What You Will Need
A Phillips head screwdriver (for removing thumbscrews).
Supported hard disk drives. Refer to http://www.pc.ibm.com/us/compat/ for a list of supported options and part numbers for your server.
A licensed copy of OS/2 Warp Server v4.0 Advanced SMP.
IBM Netfinity and PC Server Ethernet Controller and Netfinity 10/100 Fault Tolerant Device Driver, v2.03 (filename: 33L3918.EXE) or later.
The on-board IBM ServeRAID II Adapter requires:
IBM ServeRAID Device and Utilities Driver Diskette, Version 2.82 (filename 24L8051.EXE) or later.
IBM ServeRAID Configuration Diskette, Version 2.82 (filename 24L8048.EXE) or later.
If the ServeRAID II Adapter BIOS is not Version 2.70 (or later), you will need:
IBM ServeRAID II BIOS Firmware, Version 2.82 (filename 24L8047.EXE) or later.
IBM Netfinity 5500 Device Driver for Advanced Remote Manager Diskette, v1.00 (filename 24L8031.EXE) or later.
IBM Netfinity 5500 S3 Trio V2/GX Device Driver for OS/2 Diskette, v3.03.26 (filename 24L8036.EXE) or later.
OS/2 FixPak 35 or later. This is available from the sites listed in Appendix A.
MPTS FixPak WR08504. This is available from the sites listed in Appendix A.
LANServer FixPak IP08506. This is available from the sites listed in Appendix A.
2.0 Where to Download Device Drivers/Files
IBM BBS (U.S.): 1-919-517-0001
IBM FTP site: ftp://ftp.infania.net/pccbbs/pc_servers/
IBM U.S. web site: http://www.pc.ibm.com/us/searchfiles.html
For IBM PC sites in other countries, begin at http://www.pc.ibm.com
If you are very familiar with SCSI, hardware, and the installation process, continue with '3.0 Quick Installation Instructions
for Experienced Users'. If not, continue with '4.0 Detailed Installation Instructions'.
3.0 Quick Installation Instructions for Experienced Users
IMPORTANT: OS/2 currently only supports one CD-ROM device installed in the server during NOS installation. Additional CD-ROM devices can be installed in the server after completion of the NOS installation. Refer to APAR PJ24628 for more information. Verify that there is only one CD-ROM device in the server before continuing.
1. If you plan to use an external DASD enclosure, refer to the documentation provided with the external enclosure for proper set up.
2. Configure arrays on the hard disk drives using 'PC ServeRAID Configuration Diskette, Version 2.82'.
3. If any ISA devices are installed (or will be installed) that need IRQs or other system resources reserved, go into the BIOS settings and select 'Plug and Play'; then, select the desired resource type you want to reserve. Change the desired resource from 'Plug and Play' to 'ISA Legacy'.
4. On a separate machine using a standard text editor, copy IPSRAID.ADD from the 'PC ServeRAID Device Driver and Utilities Diskette, Version 2.80' onto the 'OS/2 Diskette 1 for CD-ROM'. Also, add the following lines to the top of config.sys on the 'OS/2 Diskette 1 for CD-ROM'.
set copyfromfloppy=1
basedev=ipsraid.add
5. After formatting, OS/2 will perform an operating system file copy. When the file copy is complete, the system will beep and display a panel asking you to press Enter to restart (reboot) or F3 to exit to a command prompt. Press F3 to exit to a command prompt. Copy the IPSRAID.ADD driver for the PC ServeRAID II Adapter to the C: drive; then, remove 'OS/2 Diskette 1 for CD-ROM' and restart the server. Failure to copy this driver file to the hard disk drive might result in data corruption.
6. Select 'Video Graphics Array (VGA) video driver' and click on 'OK'; then, click on 'OK' again at the 'System Configuration' window.
Note: If you plan to use the S3 TRIO 64V2/GX device driver that is shipped with the system on the 'IBM Netfinity 5500 S3 Trio V2/GX Device Driver for OS/2 Diskette, v3.03.26' (filename 24L8036.EXE) to allow higher video resolutions, use the VGA video driver during NOS installation. You can only install this new video driver after the NOS installation is complete. Review Appendix C for full driver installation details.
7. At the 'Configuration' window, click on the bottom check mark for Adapter and Protocol Services. Add any additional network adapters and necessary protocols. If you are using the integrated 10/100 Mbps Ethernet adapter, select 'Change Adapter'; then, select 'Other Adapter'. Insert 'IBM Netfinity 'PCNet Ethernet Controller Device Driver, v1.00' (filename 24L8035.EXE) into the diskette drive and click on 'OK'. Select 'AMD PCNet Family Ethernet Adapter', and under 'Type of LAN', select 'Ethernet' and click on 'OK'.
8. Install FixPak 35 (or later), MPTS FixPak WR08504, and LANServer FixPak IP080506. See Appendix A for details.
Note: OS/2 does not provide necessary support required to support hot-plug PCI operations.
4.0 Detailed Installation Instructions
4.1 Setting Up the Hardware for NOS Installation
1. Looking at the rear of the server, loosen the two thumbscrews on the top back of the server and remove the top access panel by pushing it toward the rear of the server.
2. For the initial installation, remove all adapters and devices that are not required to get the base operating system installed. For example, if installing multiple network adapters, only install one at this time. If a tape drive or external SCSI devices will be used, disconnect them temporarily. After the operating system is starting (booting) without errors, add these devices one at a time. This procedure streamlines the installation process.
3. Verify that the SCSI cable (part number 76H3452) runs from the on-board RAID controller to the top of the hot-swap backplane.
4. Install the desired number of hot-swap hard disk drives into the hot-swap bays beginning at the top and proceeding downward.
IMPORTANT: OS/2 currently only supports one CD-ROM device installed in the server during NOS installation. Additional CD-ROM devices can be installed in the server after completion of the NOS installation. Refer to APAR PJ24628 for more information. Verify that there is only one CD-ROM device in the server before continuing.
4.2 Setting Up the BIOS
1. Power-on the server; then, press F1 when the IBM logo appears to enter 'Configuration/Setup'.
2. When the 'Configuration/Setup Utility' menu appears, move the highlighted selection to 'Load Default Settings' and press Enter. Press Enter again to return to the 'Configuration/Setup Utility' menu.
3. Verify that you are at the latest level of BIOS.
a) Find the latest level by checking the IBM web, ftp, or bbs site.
b) Determine the version of BIOS running on your server by highlighting the menu option 'System Information'; then, selecting 'Product Data' and pressing Enter. The 'Flash EEPROM Revision Level' field contains the BIOS version. The numbers in position 5, 6, and 7 of the level are the current BIOS level. For example, KIE146AUS is BIOS level 46A, U.S. English.
c) Press Escape twice to return to the 'Configuration Utility' menu. If you determine that your BIOS does not need to be updated, continue with step 6.
4. If your BIOS needs to be updated, download the appropriate image and build the diskette image by running the .EXE file. Answer 'Y' on the last page of the licensing agreement. The current diskette image is KIJT46A.IMG and is labeled 'IBM Netfinity 5500 Flash BIOS Update Diskette'.
5. Start (boot) with the BIOS diskette in the server and answer the question appropriately. After the BIOS update is complete, you might receive a '162 Configuration has changed' error on startup (boot). Ignore this message. Setup will start and you can continue with step 6.
Note: If you do not see the '162 Configuration has changed' message at startup (boot) time, you will need to press F1 when the IBM logo appears to enter Setup.
6. Move the highlighted selection to 'Start Options' and press Enter.
7. Verify that the 'Primary Startup Sequence' is set to the following (change if necessary):
First Startup Device |
Diskette |
Second Startup Device |
Hard Disk 0 |
Third Startup Device |
CD-ROM |
Fourth Startup Device |
Disabled |
8. Press Escape to return to the 'Configuration/Setup Utility' menu.
9. If you do not have any ISA devices installed in the server, continue with step 14. Otherwise, continue with the next step.
10. Move the highlighted selection to 'Plug and Play' and press Enter.
11. Determine the I/O, Memory, DMA, and Interrupt resources that each ISA adapter will require.
12. Select the appropriate resource type and press Enter.
13. Scroll through the selections to the value that matches the ISA Legacy Resource and use the arrow key to change the value from 'Available' to 'ISA Legacy'. Press Escape to return to the 'Configuration/Setup Utility menu' and continue with step 15.
14. Press Escape twice to return to the 'Configuration/Setup Utility' menu.
15. Move the highlighted selection to 'Exit Setup' and press Enter.
16. At the 'Exit Setup' menu, select the menu option 'Yes, save and exit the Setup Utility' and press Enter.
4.3 Configuring Arrays Using the Integrated PC ServeRAID II Adapter
1. Insert the RAID Configuration diskette into drive A:
Upon initial startup (boot), an error message similar to the following might occur:
' - Following drives not responding (oldstate:newstate:ch:bay)
(ONL:DDD:2:1)(ONL:DDD:2:2)
Identifiers for the following drives do not match configuration ...'
Press F5 - to accept any configuration changes that might occur. The drives will be set up later in this section to match your configuration.
2. Start (boot) to the 'PC ServeRAID Configuration Diskette, Version 2.82'. Select 'Advanced Functions'; then, select 'Init/View/Synchronize Config' and finally, select, 'Initialize Configuration'. Press any key to continue. Confirm the initialization request with a 'Yes'.
3. After initializing, press Escape three times to exit to the 'Main Menu'; then, select 'Create/Delete/Copy Log Drive'.
4. Select 'Create Disk Array'.
5. Use the arrow keys to select 'RDY' drives for each new array. Press Enter on each highlighted drive to change the status to 'ONL' which adds it to the array.
6. Press Esc when finished selecting drives; then, press any key to continue.
7. Select 'Define Logical Drive'.
8. Select an array to define a drive on and press Enter.
9. Specify the RAID level for the new logical drive and press Enter.
10. Specify size for the new logical drive and confirm with a 'Yes'.
The maximum size for a logical drive under OS/2 Warp Server v4.0 is 64GB for HPFS386 and 26GB for HPFS. The minimum recommended size for a partition is 500MB. This amount might vary depending on the selections made during the installation process.
11. When the message stating that 'All logical drives must be INITIALIZED after being created' appears, press Enter. Confirm the command to initialize the new logical drive with a 'Yes'; then, press any key to continue.
If a RAID-5 logical drive was defined, a message stating that 'All RAID-5 logical drives must be SYNCHRONIZED after initialization' appears. Press any key to confirm synchronization of the new logical drive. The synchronization process will complete in the background. After synchronization has started, press Escape to return to the 'Main Menu'.
Note: The server can be restarted (rebooted) during the synchronization process. The ServeRAID II adapter is designed to suspend synchronization during a restart; then, continue after the restart has completed.
12. Select 'Advanced Functions'; then, select 'Backup IPS ServeRAID Config'.
13. Verify that the 'PC ServeRAID Configuration Diskette, Version 2.80' is not write-protected.
14. Enter the file name where you want to save the Configuration or press Enter to accept the default; then, select 'Yes' to confirm.
15. Exit the utility. Ignore the message to back up the RAID configuration and confirm with a 'Yes'. Remove the diskette.
4.4 Running the OS/2 Warp Server v4.0 Installation Program Using the Integrated PC ServeRAID II
1. On a separate machine, copy IPSRAID.ADD from the 'PC ServeRAID Device Driver and Utilities Diskette' to the 'OS/2 Diskette 1 for CD-ROM'. Using a standard text editor, also add the following lines to the top of CONFIG.SYS on the 'OS/2 Diskette 1 for CD-ROM'.
set copyfromdiskette=1
basedev=ipsraid.add
IMPORTANT: The order of drivers in CONFIG.SYS is very important. The driver for the SCSI device that is being used to start (boot) the operating system must be the first SCSI driver found in CONFIG.SYS. Failure to verify this will result in a system that will hang at the OS/2 Warp startup (boot) window. The best way to verify this is to put the driver for your startup device at the top of CONFIG.SYS before any other BASEDEV or DEVICE statement.
2. Insert 'Installation Diskette for CD-ROM' into the diskette drive and the 'OS/2 Warp Server Version 4 Advanced SMP' CD into the CD-ROM drive and start (boot) the server.
3. Insert 'OS/2 Diskette 1 for CD-ROM' when prompted.
4. At the 'Welcome' window, press Enter. After reading the 'Important Licensing Information' window, press Enter again.
5. Select 'Advanced Installation'.
6. Select '2. Specify your own installation partition'.
7. Press Enter twice; then, select 'Create Partition...'. Enter the size of the partition. The boot partition must be on the first logical drive created (either the first physical drive for non-array configurations or the first logical drive on the first RAID array for RAID configurations) and must not exceed 2000MB in size. All other partitions can be up to 64GB in size when using HPFS386, and 2048MB for FAT partitions. The minimum size needed to install all components of Warp Server Advanced is 500 MB. Please consult the 'Up and Running' manual for more information about minimum system requirements.
8. Select 'Primary Partition' for the first partition and select 'Extended Logical Drive' for all others.
9. Select 'Create at Start of FreeSpace'.
10. Repeat until all space on the drive has been allocated to partitions.
11. Press Tab to change to different logical drives and repeat steps 7 through 10 until all logical drives are allocated.
12. Go back to the first logical drive and use the arrow keys to select the partition you want to contain the operating system.
13. Press Enter to bring up FDISK options again and select 'Set Installable'.
14. Name the partition.
15. Press F3 twice to exit the FDISK program.
16. Reinsert 'Installation Diskette for CD-ROM' into the diskette drive and press Enter to restart (reboot) the server.
17. Insert 'OS/2 Diskette 1 for CD-ROM' when prompted.
18. At the 'Welcome' window, press Enter. After reading the 'Important Licensing Information' window, press Enter again.
19. Select 'Advanced Installation'.
20. Select '1. Accept the drive'.
21. Select 'High Performance File System' or select 'FAT file system'; then, press Enter to format the installation partition.
22. After formatting, OS/2 will perform an operating system file copy.
23. When the file copy is complete, the system will beep and display a panel asking you to press Enter to restart (reboot) or press F3 to exit to a command prompt. Remove 'OS/2 Diskette 1 for CD-ROM' and press Enter to restart the server.
24. You will receive a Virus Warning message on restart, this is normal. Select 'Change is expected'.
25. At the 'System Configuration' window, click on 'OK', or select any items you want to configure (although these might be added after installation) and click on 'OK'.
26. Select a default printer or accept no default printer; then, click on 'OK'.
27. Select 'Video Graphics Array (VGA) video driver' and click on 'OK'; then, click on 'OK' again at the 'System Configuration' window.
Note: If you plan to use the S3 TRIO 64V2/GX device driver to allow higher video resolutions, use the VGA video driver during NOS installation. You can only install this new video driver after the NOS installation is complete. Review Appendix B
for full driver installation details.
The S3 TRIO 64V2/GX device driver is shipped with the system on the 'IBM Netfinity 5500 S3 Trio V2/GX Device Driver for OS/2 Diskette V3.03.26' (filename 24L8036.EXE).
28. At the 'OS/2 Setup and Installation' window, uncheck any additional products you will not need and click on 'Install'. By default, all items are selected.
Note: If you plan on installing with multiple CD-ROM drives, do not select the 'MMOS/2' option.
29. Under 'Advanced Options', select 'Add existing programs to your Desktop' and click on 'OK'.
30. At the 'Information' window, type your personal information and click on 'OK'. This step is optional.
31. At the 'OS/2 Warp Server Setup and Installation' window, check any additional services you require and click on 'OK'.
32. At the 'Configuration' window, click on any red arrows and configure necessary options. All gray checks denote default settings that you might accept or change (review all default values at this time). Teal checks represent acceptably configured and reviewed options.
33. Click on the bottom check mark for 'Adapter and Protocol Services'. Add any additional network adapters and necessary protocols. If you are using the integrated 10/100 Mbps Ethernet adapter, select 'Change Adapter'; then, select 'Other Adapter'. Insert the 'IBM Netfinity PCNet Ethernet Controller Device Driver, v1.00' diskette into the diskette drive and click on 'OK'. Select 'AMD PCNet Family Ethernet Adapter' and under 'Type of LAN' select 'Ethernet' and click on 'OK'.
34. When all options are correctly configured, click on Install; then, click on 'OK' to complete the installation.
35. The primary copy then begins. The installation of Warp Server, v4.0 is complete. The server will restart (reboot) twice before file copying is complete.
36. Prior to the second restart (reboot), replace the OS/2 Installation diskette in the drive and then the OS/2 disk 1 for CD-ROM when prompted. When asked to continue with installation or to press F3 to exit to a command prompt, be sure to press F3 to exit to a command prompt. Copy the IPSRAID.ADD driver for the PC ServeRAID II Adapter to the C: drive by typing: copy a:\ipsraid.add c:\os2\boot
Type EXIT and press Enter. Remove the diskette from the diskette drive and restart (reboot) the server.
37. Install FixPak 35 or later, MPTS FixPak WR08504, and LANServer FixPak IP08506. See Appendix B for further details.
Appendix A: Installing FixPak 35, MPTS FixPak WR08504, and LANServer FixPak IP08506 on OS/2 Warp Server v4.0 Advanced SMP
A.1 Where to Find FixPak 35 and Related Necessary Fixes
- FixPak 35 (OS/2 Warp Server Advanced 4.0 FixPak XR_W035): ftp://ftp.software.ibm.com/ps/products/os2/fixes/v3.0warp/english-us/xr_w035/
- MPTS FixPak WR08504: ftp://ftp.software.ibm.com/ps/products/mpts/fixes/english-us/wr08504_smp/
- LANServer FixPak IP08506: ftp://ftp.software.ibm.com/ps/products/lan/fixes/lsv5.0_smp/english-us/ip08506/
Note: The above filenames and directories might vary slightly depending upon the language you choose to use. To enable
choosing different language FixPaks, begin at: ftp://ftp.software.ibm.com/ps/products/PRODUCT/fixes/ (where PRODUCT is one of the three products listed in the above FTP sites).
A.2 Where To Find CSF (Corrective Services Facility)
(A.2 is an excerpt from README.1ST of FixPak 35.)
The Corrective Service Facility disk images are available in the WKICKR.ZIP file from many places, including, but not limited to, the following:
Source |
How To Access |
CompuServe |
Subscribers can download from the OS/2 Support Forum (GO OS2SUPPO), in Library 23, IBM FILE. |
IBM OS/2 BBS |
Subscribers can download from the Software Download Library. U.S. customers who are not subscribers can call 1-800-547-1283 for information on how to subscribe. Internet(FTP) Anonymous FTP to ftp.software.ibm.com (IP Address 198.17.57.66) in the /ps/products/os2/fixes directory. Internet(WWW) Point your Web Browser at ftp://service.boulder.ibm.com/ps/products/os2/fixes |
Prodigy |
Subscribers can download from the OS2CLUB in the Download Library, IBM Files, Fixes area. Files are updated weekly and are available on Friday. |
PCC BBS |
Customers can call the IBM Personal Computer Company BBS In Raleigh NC, and download from the public area. You can access this BBS at 1-919-517-0001. |
AOL |
America OnLine subscribers can download from the OS/2 Area. |
Follow the instruction contained in the WKICKR.TXT file to create the Corrective Service Facility disks. Label them as:
CSF DISK Diskette 1 (SP DISK 1)
CSF DISK Diskette 2 (SP DISK 2)
A.3 Creating FixPak Diskettes
Use LOADDSKF.EXE to create the diskettes. For each disk image, insert a 2MB HD (1.44MB formatted) diskette into drive A:.
IMPORTANT: Do not use a 1MB (720KB formatted) diskette because you might have problems when installing this FixPak.
For each diskette image in the FixPak, do the following:
Enter LOADDSKF XR_W035.xDK A: /F (x in .xDK can be A through Z, 1 through 9). Label the diskette as FixPak XR_W035 Corrective Service Diskette x (CSF DISK x)
Note: For diskette images ADK through ZDK (if they exist), use the numbers 10 through 36.
Examples:
XR_W035.ADK = Corrective Service Diskette 10 (CSF DISK 10)
XR_W035.BDK = Corrective Service Diskette 11 (CSF DISK 11)
XR_W035.CDK = Corrective Service Diskette 12 (CSF DISK 12)
XR_W035.DDK = Corrective Service Diskette 13 (CSF DISK 13)
and so forth...
A.4 Installing FixPak 35 (OS/2 Warp Server Advanced 4.0 FixPak XR_W035)
A.4.1 Before Installing
Before installing any FixPak, run CHKDSK /F against all drives on your system to correct any file system errors that might be present. You cannot do this while OS/2 is active. You must shut down OS/2 and run CHKDSK by one of the following methods:
- Start (boot) using the Installation and DISK 1 diskettes you used to install OS/2. If your file system is HPFS, then insert the diskette with CHKDSK and UHPFS.DLL into your A: drive before issuing the CHKDSK command.
- Start (boot) using the Utilities disk you created via the 'Create Utility Diskettes' icon in the System Setup folder.
- Start (boot) from a different OS/2 partition.
A.4.2 Installing from a Booted OS/2 Partition
Note: You can use a diskette drive other than A: with this method. If your 3.5-inch diskette drive is B:, use B: where A: is mentioned in the following steps (this method only).
1. Insert CSF DISK Diskette 1 into drive A.
2. Open an OS/2 window or a full-screen session.
3. Type A:\SERVICE and press Enter.
Note: You can also use the 'Drives' object for A: and double click on the 'SERVICE.EXE' Icon to start the installation.
4. Follow the instructions that appear. When prompted to insert Corrective Service Diskette 1 (not CSF DISK Diskette 1), insert FixPak XR_W035 Corrective Service Diskette 1 into drive A. Repeat for the remainder of the FixPak disks when requested to do so.
Note: It can take a considerable length of time for the Corrective Service Facility to scan your hard disk for serviceable files. In some cases, it has taken as long as 40 minutes. Please be patient and allow this process to complete.
5. If this is the first OS/2 Warp FixPak you have applied to this system, then type the path to the ARCHIVE directory where a copy of replaced files will be stored (for example, D:\ARCHIVE).
Notes:
a) This ARCHIVE directory is not related to the ARCHIVES directory built into OS/2 Warp 3.0. Please specify a different path. You must specify a different ARCHIVE directory for each product to be serviced. If this is not the first OS/2 Warp FixPak, then type the path to the BACKUP directory where a copy of replaced files will be stored (for example, D:\BACKUP).
b) You must specify a different BACKUP directory for each product to be serviced.
c) For the ARCHIVE directory and the BACKUP directory, make sure there is sufficient space available on the drive you specify. Even though these files are kept in compressed (PACK2) format, they require between 7 MB and 12 MB of disk space.
6. Click on 'OK'.
7. You will see an 'Application in use' panel box showing a list of locked files that cannot be serviced while the system is running. You are given two choices - to 'Continue' or 'Reboot'. Select 'Continue'.
8. During the installation process you might see messages about Archiving, Updating, and Deferring Service.
- Archiving: Saves a compressed copy of the original file in the ARCHIVE or BACKUP path you specified.
- Updating: Means the original files are replaced with the new ones from this FixPak.
- Deferring Service: Means the file to be updated is currently in use by the system and cannot be updated. The new files from the FixPak are placed in unpacked format in the \IBMCSFLK\FIX directory on the drive with the most free space. They are processed by the locked file device driver during restart (reboot) after you shut down the system.
9. Select 'No' for a redisplay of the 'Product List' after the first part of the FixPak application process has completed if this message appears.
10. Click on 'Cancel'; then, click on 'Exit' to close the 'Corrective Service Facility' window if necessary.
11. Shut down and restart (reboot) your server.
You will see the following during restart (reboot) of the system if you applied service to the OS/2 partition you were started from.
The locked file driver is loaded.
Processing locked files
Processing complete
The system will do one automatic restart (reboot) after the 'Locked File Device Driver' has completed.
A.5 Installing MPTS FixPak WR08504
This FixPak is installed via the INSTALL.CMD file. Once downloaded, diskettes can be made in the same manner as the CSF diskettes using LOADDSKF.
1. Insert the first diskette into the server, change to the A: drive and type INSTALL; then, press Enter. Press Enter on the first panel if required.
NOTE: This step might be optional if you have banner pages set to time out.
2. Select 'Install' on the Multi-Protocol Transport Services Screen.
3. When prompted, select the Target Drive. A panel will appear stating that 'You requested to install a new version of MPTS on your workstation'. Select 'OK' to install the newer version of MPTS.
4. When prompted, change diskettes. You only need to install the first four diskettes unless you are doing CID related installations.
5. After the diskette copy is complete, select 'OK'.
6. Even if no changes are to be made to your configuration, you must select 'Configure', followed by 'Configure' on the next menu to verify your MPTS configuration; then, select 'OK' to save the configuration and any changes you might have made.
7. Select 'Close', 'Close', 'Exit', and 'OK' to exit MPTS.
8. Remove the diskette, shut down the system, and restart (reboot) the server after installation is complete.
A.6 Installing LANServer FixPak IP08506
IP08506.INF, located on the first FixPak diskette, contains installation, and other useful information about this FixPak. Please review before installation of service. The CSF2-B is used for installation of this FixPak. README and Installation instructions for DOS LAN Services, V5.0 are included on the first DOS LAN Services diskette. Once downloaded, diskettes can be made in the same manner as the CSF diskettes using LOADDSKF.
A.7 Backout Instructions
If you need to backout these fixes, you can do this only if you have chosen to backup the files during the installation (that is, you answered 'Yes' to the backup question).
If you have chosen to back up the files, the old files will be in the \IBMLAN\NETPROG directory with a .P2K extension. Copy the .P2K files in this directory (LSERROR.P2K, LSAUDIT.P2K, and NET.P2K) to .EXE files with the same name. Backout is complete.
For example, if you ran the installation from C:\TEMP and your IBMLAN directory is on D:, you would use the following commands:
- d:
- cd ibmlan\netprog
- copy lserror.p2k lserror.exe
- copy lsaudit.p2k lsaudit.exe
- copy net.p2k net.exe
Appendix B: Installing the S3 TRIO V2/GX Device Driver
(Appendix B is an excerpt from the README.TXT on the 'IBM Netfinity 5500 S3 Trio V2/GX Device Driver for OS/2 Diskette, v3.03.26'.)
1. Start (boot) the server in VGA mode. If the server was not installed in VGA mode, this can be accomplished by pressing ALT+F1 when the OS/2 logo appears in the upper left hand corner of the monitor during startup (boot). From the 'Recovery Choices' window, press V to reset the primary video display to VGA and restart (reboot) the server.
2. Insert the 'OS/2 Device Driver for S3 TRIO 64V+ Diskette' (part number 4306788) into diskette drive A (or any other diskette drive). In the following sequence the A: drive is assumed.
3. Open an OS/2 full-screen or OS/2 window session.
4. At the OS/2 command prompt, type A:SETUP to copy all necessary files to the OS/2 drive (where A: is the diskette drive that contains the device driver installation diskette); then, press Enter. Due to the limitations with a single pass installation. A dialog box might come up during installation with the message, 'The installed adapter does not support the selected display driver. Do you wish to continue-'. Please continue the installation by selecting the 'Yes' button.
5. When the 'Monitor Configuration/Selection Utility' window appears, the 'Install Using Defaults for Monitor Type' choice is preselected. Select 'OK'. Do not select 'Install Using Display Adapter Utility Program' since this method of setting refresh rates is not supported anymore.
NOTE: DSPINSTL determines the hardware configuration by creating the \OS2\SVGADATA.PMI file. If the \OS2\SVGADATA.PMI file has not been created, the adapter will not be supported. This process can take several seconds and it will black-out the screen.
6. When the 'Source Directory' pop-up window appears, insert the prompted graphics-accelerator driver diskettes into drive A. At this point the source directory must specify the drive containing the installation diskette (for example, A:). If necessary change the source directory, then select 'Install'.
7. When the installation is complete, shut down your system, remove the diskette, and restart your server.
8. When the server has restarted:
a) Open the OS/2 System folder.
b) Open the System Setup folder.
c) Open the System object.
d) When the Settings notebook appears, select the 'Screen' tab.
If your monitor has been detected as Plug-and-Play (DDC) compatible, continue with step 10.
9. On 'Screen page 2', select your display from the display list. If your monitor does not appear in the list, select 'Default'. It might be necessary to restart your server to have all refresh rate options available.
10. When the system has restarted:
a) Open the System object and select 'Screen page 1', as in step 8.
b) Select a screen resolution and a screen refresh rate.
c) Close the Settings notebook.
d) Perform a shutdown and restart your computer.
Notes:
a) If the selected vertical refresh rate is not supported by your monitor, delete \OS2\VIDEO.CFG file and restart (reboot). This
will set the refresh rate to the default value. A new refresh rate can now be selected using the procedure described above.
b) During the installation of this driver, DISPLAY.LOG and DSPINSTL.LOG files are created in the OS/2\INSTALL directory. These files identify the OS/2 system files that were updated and indicate whether the installation was successful. The contents of these files might be useful if you need to report an installation problem.
c) If the video memory size is changed after the device driver is installed, the device driver must be reinstalled in order for the system to recognize the change. Not reinstalling the driver can result in serious system problems.
d) When starting a Windows session from a DOS command line, use the WINOS2 command rather than the WIN command. Additionally, you must modify the C:\AUTOEXEC.BAT file. Place the following line anywhere after the '@ECHO.OFF' line in the AUTOEXEC.BAT:
COPY C:\WINDOWS\WINOS2.COM C:\WINDOWS\WIN.COM
Appendix C: Installing the Advanced Service Processor Adapter Driver
1. Open an OS/2 window. At the command prompt type A:; then, press Enter. Type CD OS2 and press Enter. Type SETUP and press Enter.
2. Select 'N' to select the default path for installation.
3. Press any key to exit; type EXIT at the command prompt and press Enter.
4. Select 'Shutdown' from the OS/2 desktop and restart the server.
Note: Service Processor is designed to be used with Netfinity software for System Monitoring.
Software Product:
Version:
Vendor:
EDOC Number:
Announce Date:
GA Date:
Service End Date:
Program Services:
Search Keywords |
| |
Document Category |
OS/2 | |
Date Created |
18-06-98 | |
Last Updated |
16-12-98 | |
Revision Date |
16-12-99 | |
Brand |
IBM PC Server | |
Product Family |
Netfinity 5500, Netfinity 5500 M10 | |
Machine Type |
8660, 8661 | |
Model |
ALL | |
TypeModel |
| |
Retain Tip (if applicable) |
| |
Reverse Doclinks |