OSDIBOOT - CREATING A STARTUP DISKETTE FOR OS/2 2.1 AND OS/2 2.11 02/09/96 ======================================================================= Creating a Startup Diskette for OS/2 2.1 and OS/2 2.11 ======================================================================= Please Read Entire Document for Full Explanation of Procedures -------------------------------------------------------------- DESCRIPTION This document describes how to create a single startup diskette for OS/2 2.1, and an OS/2 2.11 startup diskette from the corrective service diskette (CSD) XR6200. RESOLUTION Creating a Single Startup (Boot) Diskette ----------------------------------------- The BOOTD21 program for OS/2 2.1 automatically creates a startup (or boot) diskette using the Installation Diskette and Diskette 1. The BOOTD21.ZIP file is available on CompuServe, the IBM PCC BBS, and other bulletin boards. If you do not have access to these sources or do not have a modem, you can create a single startup diskette using the OS/2 Installation Diskette, Diskette 1, and a blank formatted diskette. 1. Copy the file SYSINSTX.COM from the Installation Diskette to the \OS2 subdirectory on your hard disk. 2. Make a temporary subdirectory on your hard disk called BOOTOS2; then copy the files KEYBOARD.DCP and SYSINST1.EXE from OS/2 Diskette 1 to the new BOOTOS2 subdirectory. 3. Insert a blank diskette in drive A; then at an OS/2 command prompt, type SYSINSTX A: and press Enter. This transfers the necessary startup files to the diskette. This is now the boot diskette. 4. Type the following and press Enter after each to show hidden system files on your hard disk: ATTRIB -S -H -R OS2KRNL ATTRIB -S -H -R OS2LDR ATTRIB -S -H -R OS2LDR.MSG These commands remove system, hidden, and read-only bits from the OS2KRNL, OS2LDR, and OS2LDR.MSG files, so they can be copied from disk to diskette. 5. Copy OS2KRNL, OS2LDR, and OS2LDR.MSG from the root directory of your hard disk to your new boot diskette. For example: COPY C:\OS2KRNL A: After copying the three files, you can return files to their original state with the ATTRIB command. Type the following and press Enter after each: ATTRIB +S +H +R OS2KRNL ATTRIB +S +H +R OS2LDR ATTRIB +S +H +R OS2LDR.MSG 6. Copy the files KEYBOARD.DCP and SYSINST1.EXE from the \BOOTOS2 subdirectory on your hard disk to the boot diskette: For example: COPY C:\BOOTOS2\KEYBOARD.DCP A: 7. Copy the following files from the \OS2\DLL subdirectory to your boot diskette: ANSICALL.DLL DOSCALL1.DLL NLS.DLL NPXEMLTR.DLL BKSCALLS.DLL KBDCALLS.DLL OS2CHAR.DLL BMSCALLS.DLL MOUCALLS.DLL QUECALLS.DLL BVHINIT.DLL MSG.DLL SESMGR.DLL BVSCALLS.DLL NAMPIPES.DLL VIOCALLS.DLL 8. Copy the files HARDERR.EXE and COUNTRY.SYS from the \OS2\SYSTEM subdirectory to the boot diskette. 9. Copy the file SYSLEVEL.OS2 from the \OS2\INSTALL subdirectory to the boot diskette. 10. Copy the files CMD.EXE, DOS.SYS, IBMINT13.I13, and OS2DASD.DMD from the \OS2 subdirectory on your hard disk to the boot diskette. If you are using HPFS, also copy the file HPFS.IFS. 11. The remainder of files depend on type of system you have: * If you have an ISA-bus or EISA system: Copy the files CLOCK01.SYS, KBD01.SYS, PRINT01.SYS, SCREEN01.SYS, and IBM1FLPY.ADD from the \OS2 subdirectory to the boot diskette. * If you have a Micro Channel bus system (IBM PS/2): Copy the files CLOCK02.SYS, KBD02.SYS, PRINT02.SYS, SCREEN02.SYS, and IBM2FLPY.ADD from the \OS2 subdirectory to the boot diskette. Also, for the PS/2 system, create an ABIOS.SYS file on the boot diskette by typing the following at the command line and pressing Enter: ECHO . > A:\ABIOS.SYS 12. The last file depends on whether or not you have a SCSI hard drive in your system. If so, you also need to copy IBM2SCSI.ADD from the \OS2 subdirectory. If not, copy IBM1S506.ADD to the boot diskette. 13. When the necessary files have been copied to the boot diskette, create the following CONFIG.SYS file on the diskette: IFS=HPFS.IFS /CACHE:64 BUFFERS=32 IOPL=YES MEMMAN=NOSWAP SET PROMPT $P$I$G PROTSHELL=SYSINST1.EXE SET OS2_SHELL=CMD.EXE DISKCACHE=64,LW PROTECTONLY=YES LIBPATH=.;\; PAUSEONERROR=NO CODEPAGE=850 DEVINFO=SCR,EGA,\OS2\VTB850.DCP DEVINFO=KBD,US,KEYBOARD.DCP DEVICE=\DOS.SYS SET PATH=.;\ SET DPATH=\; SET KEYS=ON BASEDEV=PRINT01.SYS (or PRINT02.SYS) BASEDEV=IBM1FLPY.ADD (or IBM2FLPY.ADD) BASEDEV=IBMINT13.I13 BASEDEV=OS2DASD.DMD If you have a SCSI hard disk, also add: BASEDEV=IBM2SCSI.ADD. If you do not have a SCSI hard disk, add: BASEDEV=IBM1S506.ADD You now have a single boot diskette ready to use. Shut down the system and insert the boot diskette in drive A; then restart the system. It is a good idea to copy CHKDSK.COM and UHPFS.DLL (only if using HPFS) to a blank diskette so you can run CHKDSK, if necessary. Creating a 2.11 Startup Diskette from CSD XR6200 ------------------------------------------------ It is recommended that you create startup diskettes for the system before installing Service Pak 1 (SP1). These diskettes let you run system commands, such as CHKDSK, ATTRIB, and others, if needed. You can create the startup diskettes in two ways: 1. Use this method if you have not installed SP1 on your system, or have installed it and can start from the hard disk. a. Start OS/2 or any DOS version to access the ATTRIB and DISKCOPY commands. If the system is running, start from the hard disk and go to a command prompt. b. Make copies of Diskette 1 and Diskette 2 from the Service Pak by inserting each one in drive A and typing the following, pressing Enter after each: DISKCOPY A: A: c. Insert the copy of Diskette 2 and remove the read-only attribute from the CONFIG.SYS file by typing the following and pressing Enter: ATTRIB A:\CONFIG.SYS -R d. Edit the CONFIG.SYS file. Change: SET OS/2_SHELL=FSERVICE.EXE To: SET OS2_SHELL=CMD.EXE This changes the SHELL statement and lets you to start at the command prompt using the SP1 Diskette 1 and the modified copy of SP1 Diskette 2. An OS/2 drive A command prompt appears after the diskettes are started. 2. If you have already installed SP1 on your system and you cannot start from the hard disk: a. Start from the SP1 Diskette 1. When prompted for Diskette 2, insert OS/2 2.1 GA Diskette 1 instead. b. Press Esc at the Welcome screen to go to a command prompt. Notes: * The prompt states OS/2 2.1, but you can use OS/2 2.11 system commands, such as ATTRIB and DISKCOPY. * At this point you are using a mix level of code (2.1 and 2.11). This is only a work-around for using the ATTRIB and DISKCOPY commands. Other commands, such as CHKDSK, should not be run. Follow steps 1a through 1d in "Creating a 2.11 Startup Diskette from CSD XR6200" to create startup diskettes. Creating a CHKDSK Diskette -------------------------- It is recommended that you make an additional diskette to use to run CHKDSK when starting from the diskette drive. You can do this after SP1 is installed: 1. Insert a formatted diskette in drive A. 2. Type the following and press Enter to copy the OS/2 2.11 file CHKDSK.COM to diskette (x is the OS/2 startup drive): COPY x:\OS2\CHKDSK.COM A: 3. Type the following and press Enter to copy the OS/2 2.11 file UHPFS.DLL to diskette: COPY x:\OS2\DLL\UHPFS.DLL A: Insert this diskette in drive A to run CHKDSK after starting from the OS/2 2.11 startup diskettes. Troubleshooting --------------- Cannot Access an HPFS Partition ------------------------------- When you cannot access an HPFS partition on the hard disk and are prompted to run CHKDSK, do step 2a above and use the optional CHKDSK diskette above. Error Message: The name specified is not recognized as an internal or external command. This error message occurs when the command file is not present in the current directory or any of the directories defined in PATH statements. For example, if from the A: prompt, ATTRIB CONFIG.SYS -R gave this error, the system cannot find either the ATTRIB command or the CONFIG.SYS file. To correct this error, you must include a path to where the command can be found, or make sure the file that the command is acting upon is in the drive. Error Message: SYS1210: You are using an incorrect version of the operating system. This error indicates that the command file and the version of the operating system that is running do not match. You can correct this by using the correct command file from the OS/2 version that is running. ______________________________________________________________________ IBM disclaims all warranties, whether express or implied, including without limitation, warranties of fitness and merchantability with respect to the information in this document. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright (c) 1994, 1996 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.