home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
diboot.fax
< prev
next >
Wrap
Text File
|
1995-01-25
|
10KB
|
279 lines
OSDIBOOT - CREATING A BOOT DISK
11/10/94
================================================================
CREATING A BOOT DISK
================================================================
Please Read Entire Document for Full Explanation of Procedures
----------------------------------------------------------------
- Creating a single bootable diskette for OS/2 2.1
- Creating an OS/2 2.11 bootable diskette from the CSD XR6200
================================================================
CREATING A BOOT DISK FOR OS/2 2.1
================================================================
The BOOTD21 program for OS/2 2.1 automatically creates a boot
diskette using the Installation Diskette and Diskette 1. The
BOOTD21.ZIP file is available on CompuServe, 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 boot diskette using the OS/2
Installation Diskette, Diskette 1, and a blank formatted
diskette.
PROCEDURE:
1. Copy file named SYSINSTX.COM from Installation Diskette to
the \OS2 subdirectory on your hard disk.
2. Make a temporary subdirectory on your hard disk called
BOOTOS2, and copy the files named KEYBOARD.DCP and
SYSINST1.EXE from OS/2 Diskette 1 to the newly created
BOOTOS2 subdirectory.
3. Prepare a blank diskette by placing it in the A: drive,
and from an OS/2 command prompt, type:
SYSINSTX A:
This transfers the necessary boot files to the diskette. This
is now the boot diskette.
4. Use following commands 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.
Example: COPY C:\OS2KRNL A:
After copying all three files, you can place files back to
their original state, on the hard disk, using ATTRIB command:
ATTRIB +S +H +R OS2KRNL
ATTRIB +S +H +R OS2LDR
ATTRIB +S +H +R OS2LDR.MSG
6. Copy files named KEYBOARD.DCP and SYSINST1.EXE from \BOOTOS2
subdirectory on your hard disk to the boot diskette.
Example: COPY C:\BOOTOS2\KEYBOARD.DCP A:
7. Copy 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 files named HARDERR.EXE and COUNTRY.SYS from \OS2\SYSTEM
subdirectory to the boot diskette.
9. Copy file named SYSLEVEL.OS2 from the \OS2\INSTALL
subdirectory to the boot diskette.
10.Copy files named CMD.EXE, DOS.SYS, IBMINT13.I13, and
OS2DASD.DMD from \OS2 subdirectory on your hard disk to
boot diskette. If you are using HPFS, also copy the file
named HPFS.IFS.
11.The remainder of files depend on type of machine you have. If
you have an ISA-bus or EISA system:
Copy files named CLOCK01.SYS, KBD01.SYS, PRINT01.SYS,
SCREEN01.SYS, and IBM1FLPY.ADD from \OS2 subdirectory on
your hard disk to the boot diskette.
If you have a Microchannel bus system (IBM PS/2):
Copy files named CLOCK02.SYS, KBD02.SYS, PRINT02.SYS,
SCREEN02.SYS, and IBM2FLPY.ADD. Also, for PS/2 system,
create an ABIOS.SYS file on boot diskette by typing from
the command line:
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 of your hard
disk. If NOT, copy IBM1S506.ADD to boot diskette.
13.After the necessary files are copied to boot diskette, you
must create a CONFIG.SYS file on diskette to include
the following statements:
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 drive, add the following line:
BASEDEV=IBM2SCSI.ADD
If you do not have a SCSI hard drive, add the following line:
BASEDEV=IBM1S506.ADD
You now have a single boot diskette ready to use. Shutdown
the system and insert boot diskette in the A: drive. Restart
the system. It is a good idea to copy CHKDSK.COM and UHPFS.DLL
(only if using HPFS) to blank diskette so you can run CHKDSK
if necessary.
================================================================
CREATING A 2.11 BOOTABLE DISKETTE FROM THE CSD XR6200
================================================================
It is recommended that you create bootable diskettes for the
system prior to installing the Service Pack 1 (SP1). These
diskettes lets you run system commands, such as CHKDSK, ATTRIB
and others, if needed.
You can create OS/2 SP1 bootable diskettes two ways:
1. Use this method if you have not applied the SP1 to your
system or have applied the SP1 and can start from hard disk.
A. Start OS/2 or any DOS version to access the ATTRIB and
DISKCOPY commands. If machine is running, start from
the hard disk, and go to a command prompt.
B. Make a DISKCOPY OF SP1 Diskette 1 and Diskette 2 by typing
the following command for each diskette:
DISKCOPY A: A:
C. Insert the copy of Diskette 2 and remove the read only
attribute from the CONFIG.SYS file. Type:
ATTRIB A:\CONFIG.SYS -R
D. Replace the following line in the CONFIG.SYS:
SET OS/2_SHELL=FSERVICE.EXE
to
SET OS2_SHELL=CMD.EXE
This changes the shell statement in the CONFIG.SYS,
and lets you to start at the command prompt using the
SP1 Diskette 1 and the modified copy of SP1 Diskette 2.
At OS/2 A: drive command prompt appears after starting
these two diskettes.
2. If you have already installed the SP1 on your system and
you cannot start from the hard disk:
A. Start from the SP1 Diskette 1, and when prompted for
Diskette 2, insert OS/2 2.1 GA Diskette 1 instead.
B. Press Esc at the Welcome Screen to for to a command prompt.
C. The prompt states OS/2 2.1, but you can use 2.11 system
commands such as ATTRIB and DISKCOPY.
NOTE: 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.
You should follow steps A-D, in "Creating a 2.11 Bootable
Diskette from the CSD XR6200" to create boot diskettes.
================================================================
CHKDSK Diskette (optional, but recommended)
================================================================
It is recommended you make an additional diskette to use to run
CHKDSK when booting from the diskette drive. You can do this
after the SP1 is installed:
1. Insert a formatted diskette into the A: drive.
2. Copy OS/2 2.11 file CHKDSK.COM to diskette. Type:
COPY X:\OS2\CHKDSK.COM A:
3. Copy OS/2 2.11 file UHPFS.DLL to diskette. Type:
COPY X:\OS2\DLL\UHPFS.DLL A:
NOTE: X: is your OS/2 boot drive.
Insert this diskette into the A: drive to run CHKDSK after
starting from 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 the steps in 2-A 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 path defined
directories. For example, if from the A: prompt, ATTRIB
CONFIG.SYS -R gave this error, the system cannot find the
ATTRIB command or the CONFIG.SYS file.
To correct this error you need to include a path to where the
command could be found or make sure the file the command is
acting upon is located on 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 running do not match. You can
correct this by using the proper command file from the OS/2
version that is running.