home *** CD-ROM | disk | FTP | other *** search
- OSDICSDB - Creating a 2.11 bootable diskette from XR6200
- 10/19/94
-
- ================================================================
- Creating a 2.11 bootable diskette from XR6200
- ================================================================
-
- Please Read Entire Document for Full Explanation of Procedures
- ----------------------------------------------------------------
-
- It is recommended that you create bootable diskettes for your
- system before installing the Service Pack 1 (SP1). With bootable
- diskettes, you can run CHKDSK, ATTRIB and other commands if
- necessary.
-
- You can create OS/2 SP1 bootable diskettes using one of the
- following methods:
-
- METHOD A.
- ----------------------------------------------------------------
- Use this method if you have not installed the SP1 or have
- installed SP1 and can start the system from the hard disk.
-
- 1. Start OS/2 or DOS and access the ATTRIB and DISKCOPY
- commands. If your machine is running, start from the
- hard disk and go to the command prompt.
-
- 2. Make a diskcopy of SP1 Diskette 1 and Diskette 2 by
- typing the following for each diskette:
-
- DISKCOPY a: a:
-
- 3. Insert the diskcopy of diskette 2 and remove the read only
- attribute from the CONFIG.SYS file by typing:
-
- ATTRIB A:\CONFIG.SYS -R
-
- 4. Change the following line in the CONFIG.SYS:
-
- From: SET OS/2_SHELL=FSERVICE.EXE
- To: SET OS2_SHELL=CMD.EXE
-
- This lets you start at the command prompt using SP1
- diskette 1 and the modified copy of SP1 diskette 2.
-
- You go to the OS/2 drive A: prompt after starting from
- these diskettes.
-
-
- MEHTOD B.
- ----------------------------------------------------------------
- Use this method if you have installed the SP1 on your system and
- cannot to start the system from the hard disk.
-
- 1. Start the system from the SP1 diskette 1 and when prompted
- to insert diskette 2, insert OS/2 2.1 GA diskette 1.
-
- 2. Press Esc at the Welcome screen to go to the command
- prompt.
-
- The prompt states OS/2 2/1, but you can use the 2.11 system
- command such as ATTRIB and DISKCOPY.
-
- NOTE: At this point, you are using a mix level of code (2.1 &
- 2.11). This is only a work around for using the ATTRIB
- and DISKCOPY commands. Other commands, such as CHKDSK
- should not be run.
-
- 3. Follow steps 2-5 in Method A to create the correct book
- diskettes.
-
- ----------------------------------------------------------------
- CHKDSK DISKETTE
- ----------------------------------------------------------------
-
- It is recommended, but optional, that you create a diskette
- to be used to run CHKDSK when the system is started from
- a diskette drive. After installing the SP1:
-
-
- 1. Insert a formatted diskette in drive A:.
-
- 2. Copy the OS/2 2.11 file CHKDSK.COM to the diskette by
- typing:
-
- COPY X:\OS2\CHKDSK.COM A:
-
- 3. Copy the OS/2 2.11 file UHPFS.DLL to the diskette by
- typing:
-
- COPY X:\OS2\DLL\UHPFS.DLL A:
-
- Note: X: is the drive where OS/2 resides.
-
-
- You can insert this diskette in drive A: and run CHKDSK after
- starting the system with the 2.11 boot diskettes.
-
- ----------------------------------------------------------------
- Trouble Shooting
- ----------------------------------------------------------------
-
- HPFS drive access: When you cannot access an HPFS partition
- on the hard disk and are prompted to run
- CHKDSK, follow Method A, decsribed above,
- and use the optional CHKDSK diskette.
-
-
- Error message: The name specified is not recognized
- as an internal or external command.
-
- This message appears when the command file is not present in
- the current directory or any of the path defined directories.
- For example: From the A: prompt, ATTRIB config.sys -r gave this
- error, the system cannot find the ATTRIB command or the
- CONFIG.SYS file.
-
- You need to include a path where the command can be found or
- ensure the file the command is referring to is on the correct
- drive to correct the error.
-
-
- Error message: SYS1210: You are using an incorrect
- version of the operating system.
-
- This message indicates the command file and the version of the
- operating system that is running do not match.
- Make sure you are using the command file from the version of
- the operating system you are running on the system.
-