home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
DICSDB.FAX
< prev
next >
Wrap
Text File
|
1994-12-08
|
6KB
|
152 lines
Version Error / Bootdisks for XR06200 7/26/94
TITLE: Creating bootable diskettes from OS2 2.1 ServicePak.
DESCRIPTION OF SYMPTONS:
An 'Incorrect Version' error is received when trying to run
comands such as ATTRIB or DISKCOPY on a system on which the
XR06200 (or XR06300) ServicePak has been applied. This happens
after booting to a command prompt from the 2.1 GA diskettes.
SUMMARY OF RESOLUTION:
It is recommended that you create bootable disks for your system
prior to installing the ServicePak 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
following methods:
A) Use this method if you have not yet applied the SP1 to your
system or you have applied the SP1 and can boot to the hard drive:
1) Boot OS/2 or any DOS version access to the ATTRIB and
DISKCOPY commands. If your machine is up and running, boot
from the hard drive and go to a command prompt.
2) Make a diskcopy of SP1 Disk #2 by entering the
following command:
DISKCOPY a: a:
3) Insert the diskcopy of disk #2 and remove the read only
attribute from the config.sys file by entering:
ATTRIB a:\config.sys -r
4) Change the following line in the config.sys:
SET OS2_SHELL=FSERVICE.EXE
to
SET OS2_SHELL=CMD.EXE
This can be accomplished by using an editor, or by typing the
following at the a: command prompt with ServicePak disk #2 in
the a: drive:
ECHO SET OS2_SHELL=CMD.EXE >> CONFIG.SYS
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.
B) If you have already installed SP1 on your system and you are
unable to boot from the hard drive:
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.
3) The prompt will state OS/2 2.1 but you will be able to use
the 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 workaround 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 the above steps A2-A4 to create the 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 the OS/2 2.11 file CHKDSK.COM to the diskette by
entering:
COPY X:\OS2\CHKDSK.COM A:
3) Copy the OS/2 2.11 file UHPFS.DLL to the diskette by
entering:
COPY X:\OS2\DLL\UHPFS.DLL A:
If SP1 has not yet been installed then UHPFS.DLL will have to
be unpacked from disk6 of SP1:
a) Create a temporary directory (ie, x:\temp) and copy
UNPACK.EXE from disk1 of SP1 into the temp directory on
the hard drive.
b) Insert disk6 of SP1 into the drive a: and from the x:\temp
prompt type:
UNPACK A:\FIX\OS2\FILE409.___ X:\TEMP
c) Copy UHPFS.DLL from the x:\temp directory to your diskette
with OS/2 2.11 CHKDSK.COM.
If SP1 is installed on the system but you are unable to boot to the
hard drive, then steps a, b, and c above will have to be executed
on another system running OS2 2.1.
Note: X: is your OS2 boot drive.
This diskette can be inserted into the A: drive and CHKDSK can be
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 do not match. You can correct this by using the
proper command file from the OS/2 version that is booted.
12/31/99