CONFIG.DOC This file explains the changes Setup makes to your operating system configuration files so that Word operates properly. For DOS, the configuration files are CONFIG.SYS and AUTOEXEC.BAT; for OS/2, they are CONFIG.SYS, STARTUP.CMD, AUTOEXEC.BAT, and possibly others. Normally, you don't need to modify these files yourself. Setup automatically prepares them for Word. Before making the changes, Setup first backs up the existing configuration files and gives them the extension .OLD (.OL2 for CONFIG.OS2). Changes to DOS Configuration Files ---------------------------------- CONFIG.SYS: . If no FILES= statement exists, Setup adds one. . FILES= is set to 20 unless it's already more than 20. . If you choose to install the mouse driver, and the statement DEVICE=MOUSEPATH\MOUSE.SYS (or MOUS8514.SYS) doesn't exist (where MOUSEPATH is the location of your old mouse driver), Setup adds the statement, with MOUSEPATH set to the root directory of your startup drive. . If you choose the IBM 8514 video configuration, Setup adds the command DEVICE=MOUSEPATH\EGA.SYS, where MOUSEPATH is the same path as in the DEVICE=MOUSEPATH\MOUS8514.SYS command. AUTOEXEC.BAT: . On a hard disk or workstation, if no PATH= statement exists, Setup adds one. . On a hard disk or workstation, Setup adds the Word directory you specified to the PATH= statement. . On a workstation, Setup adds the server directory where Word and Setup exist to the PATH= statement. Setup also adds the statement SET MSWNET=LOCALPATH, where LOCALPATH is the local Word directory you specified on the workstation (A:\ for a floppy workstation). Changes to OS/2 1.1 Configuration Files on a Non Dual-Boot System ------------------------------------------------ CONFIG.SYS: . If no IOPL= statement exists, Setup adds one. If IOPL= exits, Setup ensures it's set to YES. . Setup adds WORD to the IOPL statement, unless it's already set to YES. . If no SET PATH= statement exists, Setup adds one. . On a hard disk, Setup adds the Word directory you specified to the SET PATH= statement. . On a workstation, Setup adds the server directory where Word and Setup exist to the SET PATH= statement. Setup also adds the statement SET MSWNET=LOCALPATH, where LOCALPATH is the local Word directory you specified on the workstation. STARTUP.CMD (and any batch file following the /k switch in the PROTSHELL statement in CONFIG.SYS): . On a hard disk, if a PATH= statement exists, Setup adds the Word directory you specified to that statement. . On a workstation, if a PATH= statement exists, Setup adds the server directory where Word and Setup exist to that statement. Also, if a SET MSWNET= statement exists, Setup changes it to SET MSWNET=LOCALPATH, where LOCALPATH is the local Word directory you specified on the workstation. AUTOEXEC.BAT (for the DOS compatibility box): . If no PATH= statement exists, Setup adds one. . On a hard disk, Setup adds the Word directory you specified to the PATH= statement. . On a workstation, Setup adds the server directory where Word and Setup exist to the PATH= statement. Setup also adds the statement SET MSWNET=LOCALPATH, where LOCALPATH is the local Word directory you specified on the workstation. Changes to OS/2 1.0 Configuration Files on a Non Dual-Boot System ------------------------------------------------ CONFIG.SYS: . If no IOPL=YES statement exists, Setup adds one. STARTUP.CMD (and any batch file following the /k switch in the PROTSHELL statement in CONFIG.SYS): See AUTOEXEC.BAT under "Changes to OS/2 1.1 Configuration Files on a Non Dual-Boot System," above. AUTOEXEC.BAT (for the DOS compatibility box): See AUTOEXEC.BAT under "Changes to OS/2 1.1 Configuration Files on a Non Dual-Boot System," above. Changes to DOS & OS/2 1.0 Configuration Files on a Dual-Boot System (when both CONFIG.OS2 and CONFIG.SYS exist) ----------------------------------------------------- To install Word on a DOS and OS/2 dual-boot system, you should run Setup under OS/2 so that it can create an OS/2 compatible version of Word. Setup does not modify your DOS CONFIG.SYS file. You must update this file yourself, as described in "Changes to DOS Configuration Files," above. For mouse support under DOS, you must manually copy the DOS mouse driver MOUSE.SYS from Utilities disk 3 (or MOUS8514.SYS and EGA.SYS from Program disk 1) to your hard disk and update your DOS CONFIG.SYS file as described in "Changes to DOS Configuration Files," above. CONFIG.OS2: See CONFIG.SYS under "Changes to OS/2 1.0 Configuration Files on a Non Dual-Boot System," above. CONFIG.SYS (for DOS): Setup does not make any changes. You must update this file yourself, as described in "Changes to DOS Configuration Files," above. STARTUP.CMD (and any batch file following the /k switch in the PROTSHELL statement in CONFIG.SYS): See AUTOEXEC.BAT under "Changes to OS/2 1.1 Configuration Files on a Non Dual-Boot System," above. AUTOEXEC.BAT (for DOS and the DOS compatibility box): See AUTOEXEC.BAT under "Changes to OS/2 1.1 Configuration Files on a Non Dual-Boot System," above. Changes to DOS & OS/2 1.1 Configuration Files on a Dual-Boot System -------------------------------------------------- To install Word on a DOS & OS/2 dual-boot system, you should run Setup under OS/2 so that it can create an OS/2 compatible version of Word. When Setup runs under OS/2 1.1, it operates as under "Changes to OS/2 1.1 Configuration Files on a Non Dual-Boot System," above. For mouse support under DOS, you must manually copy the DOS mouse driver MOUSE.SYS from Utilities disk 3 (or MOUS8514.SYS and EGA.SYS from Program disk 1) to your hard disk and update your DOS CONFIG.SYS file as described in "Changes to DOS Configuration Files," above. On a Zenith OS/2 1.1 dual-boot system, run Setup under OS/2, but do not let Setup change the configuration files. You should change CONFIG.OS2, CONFIG.SYS, AUTOEXEC.OS2, and AUTOEXEC.BAT manually. On other OS/2 1.1 dual-boot systems (for example, COMPAQ), you must make some changes yourself. Setup modifies the configuration files only for the active operating system. For example, when you start your system under OS/2, Setup updates only CONFIG.SYS and AUTOEXEC.BAT for OS/2. You must change CONFIG.DOS and AUTOEXEC.DOS yourself, as described in "Changes to DOS Configuration Files," above. NOTES ----- For a workstation, SET MSWNET= sets the unique path to the user's Word customization files (MW.INI, SCREEN.VID, etc.) If Setup needs to add a statement to a configuration file that doesn't exist, it creates the file. Setup makes some assumptions about which drive your system uses as the startup drive: If you install Word on a hard disk or server, Setup assumes that your startup drive is the first drive available with a letter later than B: (usually C:). If you install on a floppy disk, Setup assumes that your startup drive is A:. If you start your hard disk system (DOS or OS/2) from a floppy disk, and you install Word on the hard disk, you must update the configuration files on the floppy disk yourself, as described above. Do not let Setup update the configuration files. If you were to tell Setup to update the configuration files, it would not ask for your startup floppy disk, but would (incorrectly) create or modify configuration files on the hard disk. Setup modifies the configuration files only if Word has been installed in the same session. If you run Setup a second time in order to install the mouse support, and you do not install Word, a new DEVICE= statement is not added. You should either add this statement yourself, or install Word again the second time you run Setup. If you want to install Word a second time (so that Setup can create a second SCREEN.VID or modify configuration files), you must have about 2 megabytes of disk storage free (to install Word on a hard disk), or sufficient blank floppies, as required the first time you ran Setup. Setup does not count the space occupied by files it will overwrite as free storage. To obtain free storage on a hard disk or server, you may have to delete WORD.EXE and other files before you install Word the second time. Executable (.EXE) files copied or created by Setup are given the read-only attribute. To delete an executable file created by Setup, you must first use the DOS or OS/2 ATTRIB command to remove the read-only attribute.