MONTANA DEPARTMENT HSH, WILDLIFE, AND PARKS 

 MRIS Reporting Program 



the amount of free space on each of your hard disk drives. If one or more of the drives has 

 sufficient space to create the MRIS Reporting Program programs and data, you will be prompted 

 to supply a target directory name. If the target directory does not already exist INSTALL will ask 

 you if you want to create it. During the installation, INSTALL will place the MRIS Reporting 

 Program programs and data in the target directory (labeled MRIS unless you have choose to 

 change it) with the exception of the data index files that will be created the first time you run the 

 MRIS Reporting Program software. If INSTALL determines there is insufficient space on your 

 hard disk for the software, the installation is stopped and the amount of disk space needed is 

 displayed. 



Altering CONFIG.SYS 



To run properly, the MRIS Reporting Program software requires that the FILES statement in 

 CONFIG.SYS be set to a minimum of 147. You have the option of changing the FILES statement 

 automatically during the installation process. You will be asked if you want to change the FILES 

 statement. If you respond yes, INSTALL will create a backup of the current CONFIG.SYS named 

 CONFIG.MSL and will modify the current CONFIG.SYS. If the HLES statement is akeady set 

 at or above 147, the CONFIG.SYS will not be altered. 



If no CONFIG.SYS file exists at all, INSTALL asks you if you want to create one. If you 

 respond yes, INSTALL creates CONFIG.SYS in the root directory of the C drive with the 

 statements needed to run MRIS Reporting Program. 



If you respond no to either of the scenarios above INSTALL creates a sample file named 

 CONFIG.SMP in the target directory. You can use this sample to see how your CONFIG.SYS file 

 needs to be altered to run the MRIS Reporting Program. 



Altering AUTOEXEC.BAT 



The MRIS Reporting Program report utility also requires that a SET CLIPPER statement with 

 255 or more files be included in AUTOEXEC.BAT. INSTALL also checks for the presence of 

 a file named BASE501B.PLL on the hard disk. If BASE501B.PLL is already present, a second 

 copy need not be created but a SET PLL statement may have to be added to the AUTOEXEC.BAT. 

 If AUTOEXEC.BAT already exists with the needed statements no action is taken by INSTALL. 



If AUTOEXEC.BAT exists but one or more above required statements are absent or need to 

 be changed, INSTALL asks you if you want to modify AUTOEXEC.BAT. If you respond yes, 

 INSTALL will create a backup of the current AUTOEXEC.BAT named AUTOEXEC.MSL and 

 modify the current AUTOEXEC.BAT as needed. 



If no AUTOEXEC.BAT file exists INSTALL asks you if you want to create one. If you 

 respond yes, INSTALL creates the AUTOEXEC.BAT in the root directory of the C drive widi the 



A-2 



