home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
BOOTDK.FAX
< prev
next >
Wrap
Text File
|
1994-12-08
|
12KB
|
301 lines
Creating a single BOOT DISK in 2.1 (CP 6/24/94
OS2BOOT.FAX CREATING A BOOT DISK
****************************************************************
How to create a single bootable diskette for OS/2 2.1
Creating a 2.11 bootable diskette from the CSD XR6200
****************************************************************
CREATING A BOOT DISK FOR OS/2 2.1
----------------------------------------------------------------
There is a program available that automatically creates a
boot disk using your install disk and disk 1. The program is
named BOOTD21 (for OS/2 2.1), and is available on CompuServe, IBM
NSC BBS, and on many other OS/2 Bulletin Boards. Note the name
of file is BOOT21.ZIP on the BBS in Raliegh and/or other BBS's.
If you do not have access to these sources or do not have a
modem, you can manually create a single boot diskette using the
OS/2 installation diskette, diskette #1, and a blank formatted
floppy disk. The procedure is as follows:
1. Copy file named SYSINSTX.COM from Installation diskette to the
\OS2 subdirectory on your hard drive.
2. Make a temporary subdirectory on your hard drive called
BOOTOS2, and copy the files named KEYBOARD.DCP and
SYSINST1.EXE from OS/2 Diskette #1 to the newly created
BOOTOS2 subdirectory on your hard drive.
3. Prepare your blank floppy disk by placing it in the A: drive,
and from an OS/2 Command prompt, type:
SYSINSTX A:
This will transfer necessary boot files to the floppy. From
this point on, we will call this the boot disk.
4. Use following commands to show hidden system files on your
hard drive:
ATTRIB -S -H -R OS2KRNL
ATTRIB -S -H -R OS2LDR
ATTRIB -S -H -R OS2LDR.MSG
These commands will remove system, hidden, and read-only bits
from the OS2KRNL, OS2LDR, and OS2LDR.MSG files. This way, they
can be copied from disk to disk.
5. Copy OS2KRNL, OS2LDR, and OS2LDR.MSG from the root directory
of your hard disk to your new boot disk.
Example: COPY C:\OS2KRNL A:
Once you have copied all three files, you can place files back
to their original state using the 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 drive to boot disk.
Example: COPY C:\BOOTOS2\KEYBOARD.DCP A:
7. Copy following files from the \OS2\DLL subdirectory to your
boot disk:
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 disk.
9. Copy file named SYSLEVEL.OS2 from the \OS2\INSTALL
subdirectory to the boot disk.
10.Copy files named CMD.EXE, DOS.SYS, IBMINT13.I13, and
OS2DASD.DMD from \OS2 subdirectory on your hard drive to boot
disk. If you are using HPFS, copy the file named HPFS.IFS as
well.
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 drive to the boot disk.
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 disk 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 \OS2 subdirectory of your hard
drive. If NOT, copy IBM1S506.ADD to boot disk instead.
13.Now that all of the necessary files have been copied to boot
disk, you must create a CONFIG.SYS file on disk 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 disk prepared for use. To test disk,
shutdown your desktop, and place boot disk in the A: drive.
Once shutdown has completed, reboot your machine to test the
disk. It is also a good idea to copy CHKDSK.COM and UHPFS.DLL
(only if using HPFS) to another blank diskette which you can run
CHKDSK from.
=============================================================
Creating a 2.11 bootable diskette from the CSD XR6200
=============================================================
It is recommended that you create bootable disks for your
system prior to installing the Service Pack 1 (SP1).
Having the bootable disks will allow you to run such system
commands as CHKDSK, ATTRIB and others, if needed. Here are
the options for creating the OS/2 2.11 bootable disks for
your system:
You can create OS/2 SP1 bootable disks by using one of the
two (2) following methods:
A) Use this method if you have not applied the SP1 to your
system or have applied the SP1 and can boot to hard drive.
1) Boot OS/2 or any DOS version access to the ATTRIB and
DISKCOPY commands. If machine is up and running, boot
from the hard drive, and go to a command prompt.
2) Make a diskcopy of SP1 Disk #1 and Disk #2 by entering the
following command for each disk:
DISKCOPY a: a:
3) Insert the diskcopy of disk #2 and remove the read only
attribute from the config.sys file, Type,
ATTRIB a:\config.sys -r
4) Replace the following line in the config.sys:
SET OS/2_SHELL=FSERVICE.EXE
to
SET os2_shell=cmd.exe
This will change the shell statement in the config.sys,
and allow you to boot to the command prompt using the
SP1 disk #1 and the modified copy of SP1 disk #2.
You will be brought to an OS/2 a: drive command prompt
after booting these two (2) diskettes.
B) If you have already installed the SP1 on your system and
you are unable to boot from the harddrive:
1) Boot from the SP1 disk #1, and when prompted for disk
#2, insert OS/2 2.1 GA disk #1.
2) Escape to the command prompt from the welcome screen when
prompted to enter to continue or escape to cancel.
3) The prompt will state OS/2 2.1, but you will be able to use
2.11 system commands such as ATTRIB and DISKCOPY. It is
important to 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. At this point you should be able
to follow above steps A2-A4, to create correct boot disks.
CHKDSK Diskette (optional, but recommended)
-------------------------------------------
It is recommended that you make an additional diskette that
can be used to run CHKDSK when booted from the floppy
drive. You can easily do this once the SP1 has been
installed by the following steps:
1) Inserting 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 OS2 boot drive.
This diskette can be inserted into the A: drive and CHKDSK
can be run after you have booted from your 2.11 boot
diskettes.
================ Trouble Shooting =================
HPFS drive access -----------------
In cases where you cannot access an HPFS partition on the hard
drive and you are prompted to run CHKDSK, perform procedure A
above and use the optional CHKDSK diskette described above.
---> Error message: The name specified is not recognized
as an internal or external command.
This error message will occur when the command file is not
present in the current directory or any of the path defined
directories. For example if from the a: drive 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 would 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 booted do not match. You can
correct this by using the proper command file from the OS/2
version that is booted.
*************************************************************
DISCLAIMER: The information contained in this document is
distributed "AS IS" without any warranties of any kind either
express or implied. IBM will not be responsible for any direct,
incidental, consequential, special or indirect damages. IBM
EXPRESSLY DISCLAIMS ANY IMPLIED WARRANTY OF MERCHANTABILITY AND
ANY IMPLIED WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE.
The use of this information or implementation of any of these
techniques is sole responsibility of customer and depends on
customer's ability to evaluate and integrate this information or
implementation into the customer's operational environment.
-----------------------------------------------------------------
BOCA CBRX TEAM 02/94.
If you have any comments or suggestions concerning our Faxes,
please send a note to: IBM Corporation
Boca CBRX Team
P.O. Box 1328
Zip 1026
Boca Raton, FL 33429
12/31/99