The RESERVE.SYS statement can be used in cases where the install process has trouble detecting hardware because of IO address conflicts. Usually this is related to having a card in your system (such as a network card) which has an IO address range that is commonly used by another type of card (such as a sound card) OR if the network card itself cannot be properly "sniffed" by the install program. In these cases, you can insert the RESERVE.SYS into the CONFIG.SYS file to prevent the install program from attempting to determine what card is using the specified IO address range.
The following fragment from a CONFIG.SYS file shows the usage of the RESERVE.SYS device statement. It should be positioned at the top of the file and includes the IO address (hex) and number of addresses to reserve. It is useful for commonly mistaken addresses such as x300.
BASEDEV=RESERVE.SYS /IO:300,32 SET COPYFROMFLOPPY=1 IFS=H:\OS2\HPFS.IFS /CACHE:1024 /CRECL:4 /AUTOCHECK:GHIJK PROTSHELL=H:\OS2\PMSHELL.EXE SET USER_INI=H:\OS2\OS2.INI SET SYSTEM_INI=H:\OS2\OS2SYS.INI SET OS2_SHELL=H:\OS2\CMD.EXE SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,WARPCENTER SET RUNWORKPLACE=H:\OS2\PMSHELL.EXE SET COMSPEC=H:\OS2\CMD.EXE
In some cases you need to use a different version of a device driver that is normally included in the OS/2 installation set. For example, the FD16-700.ADD driver does not work correctly on certain combinations of the FD1680 controller and Micropolis 2217 SCSI disk drive (this problem first appeared in Warp 3.0) but the OS/2 2.11 driver does work ok. For this install, it was necessary to copy the install diskette 1 and then overlay the driver with the 2.11 version.
To make sure that the non-standard driver is used throughout the install process, you add the following statement to the CONFIG.SYS file:
With this statement, you will be prompted to reinsert
diskettes 1 and 2 at the end of the first install phase.
NOTE:You should still verify at the end of all install
phases that the correct driver is present on your hard drive in
the apprpriate directory (usually OS2\BOOT).
Modifying Install Diskettes
There are several reasons for why you might need to modify the install diskettes. Among them are:
BE SURE TO MAKE A COPY OF ANY DISKETTE THAT YOU ARE GOING TO MODIFY!
How and Why to Make Diskettes
There are several situations in which you might need to make diskettes before/during/after your installation. A few of the most common are listed below together with how to make the necessary diskettes (and, more importantly, where to find the .CMD file that does it for you).
|Reason for diskette(s)||How to make them|
|You have lost/destroyed the install diskettes and need to remake them||Execute CDINST.CMD from root directory of your CD. It prompts for each of the three diskettes. You can also execute CDINST.BAT in DOS environment.|
|You want to install the basic system from diskettes rather than CD. (Are you sure about this??)||Execute MAKEDSK.CMD from root directory of your CD. It prompts for each of the several dozen diskettes. You can also run MAKEDSK.BAT in DOS environment.|
|You want to use a response file to install the base system. This requires that you make the 3 diskette installation diskettes. DO NOT do this process using the CD install diskettes.||Execute MAKEDSK.CMD from root directory of your CD for the first three diskettes only. You can also run MAKEDSK.BAT in DOS environment.|
|You want to install networking components on a machine without a CD and on which you cannot use remote install.||Execute PRODDSK.CMD from root directory of your CD This shows a dialog box from which you can select the component to build diskettes for (NOTE: this can also be used to create the Warp diskettes.)|