home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 28 Fixes4x
/
28-Fixes4x.zip
/
updcd10.zip
/
HTM.ZIP
/
readme.eng
< prev
next >
Wrap
Text File
|
2000-11-13
|
12KB
|
261 lines
Update your OS/2 installation CD-ROM with fixpaks and updates (version 1.0)
---------------------------------------------------------------------------
1. Introduction
Are you tired of reinstalling fixpaks after adding or reinstalling system
components? Are you tired of updating installation floppies of having
problems with installing OS/2 on large hard disks? You can avoid these
problems by updating the OS/2 Warp 4 or WSeB installation CD-ROM with
public fixpaks. How? Read on!
2. Installation
The installation of this program is very easy, just copy the files contained
in the zip to a directory of your choice (say updcd) and change to that
directory when you run the scripts. Running them from an other location will
not work!!!
3. Preparing to update
Before you can refresh an installation CD-ROM you should download and prepare
some fixpaks and updates. At a minimum, you should download Fixpak 12 (or
higher), Feature Installer 1.25 and Device Driver fixpak 1 (or higher) for
Warp 4 or Fixpak 1 for WSeB (see the UpdCD homepage for the URL of these
packages). Optionally, you can integrate MPTS, PEER, TCP/IP and printer fixes
and the updated version of MPTS, TCP/IP, Netscape Communicator or Java 1.1.x.
Create separate directories for every fixpak under the directory updcd\fixes,
like udpcd\fixes\fp14 for fixpak 14. Copy the fixpak here. If you have the rsu
version (.zip extension) than you should use unzip to uncompress it. If you
have the dsk version, use dskxtr12.zip from http://hobbes.nmsu.edu to unpack
the files. Do not change the directory structure of the fixpaks! The following
fixpaks have been tested with this version of UpdCD: Warp 4 Fixpak 12, 13, 14,
Device Driver 1, 2, MPTS 8424/8425 (16-bits), MPTS 8620/8621 (32-bits), PEER
8402/8412/8413, TCP/IP UN_0980 (16-bits), Netware Requester 2.12, printer
driver fixes (laserjet*.exe + omni*.exe + pscript*.exe + plotters*.exe). Create
a separate directories for every update under the directory updcd\updates, like
updcd\updates\java for Java 1.1.8. Copy the updated package here. If it is
needed (Java, Netscape, FI), unzip/uncompress the distribution file. The
following updates have been tested with UpdCD: MPTS 8423 (16-bits), MPTS 8610,
8700 (32-bits), Feature Installer 1.25, Netscape Communicator 4.61, Java 1.1.7,
1.1.8, TCP/IP 4.1, 4.2 and 4.3.
Example directory structure for fixes and updates:
e:\updcd\fixes
[...]
e:\updcd\fixes\XRYM012
e:\updcd\fixes\XRYM012\FIX
e:\updcd\fixes\XRYM012\FIX\OS2.1
[...]
e:\updcd\fixes\XR0DD02
e:\updcd\fixes\XR0DD02\FIX
e:\updcd\fixes\XR0DD02\FIX\BDD.1
[...]
e:\updcd\fixes\IPY8402
e:\updcd\fixes\IPY8402\FIX
e:\updcd\fixes\IPY8402\FIX\REQ.1
[...]
e:\updcd\fixes\UN_0980
e:\updcd\fixes\UN_0980\FIX
e:\updcd\fixes\UN_0980\FIX\TCP.1
[...]
e:\updcd\fixes\WR08621
e:\updcd\fixes\WR08621\FIX
e:\updcd\fixes\WR08621\FIX\MPT.1
[...]
e:\updcd\fixes\NW212
e:\updcd\fixes\NW212\ENGLISH
e:\updcd\fixes\NW212\LOGIN
[...]
e:\updcd\fixes\printer
[...]
e:\updcd\updates
[...]
e:\updcd\updates\WR08610
e:\updcd\updates\WR08610\IBMCOM
e:\updcd\updates\WR08610\MPTN
[...]
e:\updcd\updates\FI125
[...]
e:\updcd\updates\NS461
[...]
e:\updcd\updates\JAVA
e:\updcd\updates\JAVA\EN
e:\updcd\updates\JAVA\DE
e:\updcd\updates\JAVA\PACKAGE
[...]
Before starting the update you should insert your original installation CD-ROM
in your player and a formatted 3.5 inch blank floppy in drive A:. If you have
a 1.44MB virtual floppy drive (VDISK, SVDISK) than you might edit the following
line in UpdIF.CMD in order to enable UpdIF.CMD to use it:
flpdrv = translate('k:') /* <----- change it match your virtual floppy */
In this case you do not need the blank floppy and you can gain about 20
minutes processing time. Do not forget to insert a media in the virtual
drive before starting the update! You can get Super Virtual Disk (SVDISK)
from hobbes.nmsu.edu.
4. Incorporating third-party products (DANI, FAT32, SDD)
Since version 1.0 you can add third-party products to the updated CD. They
will be installed during the installation of OS/2 Warp. You have to provide
the installation files and a REXX of a BATCH program that will install the
product. Each product should be placed in its own subdirectory under the
ADDONS directory of UpdCD. The install script must be called install.cmd
and must be placed in the subdirectory of the third-party product. I have
included with this version of UpdCD installation scripts for the DANI IDE and
FILTER drivers, the FAT32 IFS and for the Schitech Display Drivers. Read the
header of the install scripts to see which files you need to copy to the
CD. If you make install scripts for other products please send me a copy. I
will include it in the next version of UpdCD.
5. Build an updated Warp 4 CD-ROM image
Simply run Go4It.Cmd from the UpdCD directory with the drive letter of your
CD-ROM player as parameter (example: Go4It.Cmd h:). It will automatically
detect and list the correctly prepared fixes and updated. The language of your
CD-ROM is also detected. Go4It.cmd does some limited checking, but it is you
who should ensure that an appropriate set of fixes and updates will be
integrated. With other words you should choose the right language and the
right fixpak version matching the version of your Warp. If you are unsure than
you might visit the UpdCD homepage for receipts of recommended setups.
If you are satisfied with the detected components, than you may press
ENTER to start the build process. The update procedure takes about an hour on
my 500MHz PIII desktop. Your milage may vary. The updated CD-ROM image will be
created in the updcd\burn directory.
During update the log file updcd.log will be crated which will list all the
actions performed by the build process followed with a return code. It should
always be 0. Besides error situations UpdCD logs warning messages as well.
A warning message does not automatically mean that there is a problem with
the update. Check the log file to see what those warnings exactly mean.
Files which are present in fixpaks but not used during update will also be
logged as warnings.
6. Making the CD bootable
UpdCD will put all the files necessary to make the CD bootable in the directory
updcd\bootimg of the new CD image (burn directory). However, to create a 2.8MB
boot image you need a 2.8MB (virtual) floppy drive. Check SVDISK if you do not
have one. Insert a media in the floppy drive and change to the directory
updcd\bootimg\DISK_0_1.IMG. Run sysinstx with the drive letter of the floppy
(e.g. sysinstx k:). Copy all the files from the current directory to the
floppy. Change to the diskimgs subdirectory of the burn directory. Run
image.exe to create a 2.8MB boot image called DISK_0_1.IMG from the floppy in
the root of the burn directory (e.g. image.exe k: ..\DISK_0_1.IMG). Insert a
1.4MB floppy in the drive and copy all the files from updcd\bootimg\DISK_2.IMG
to it. Go to diskimgs and create a second image in the root called DISK_2.IMG
from the floppy (e.g. image.exe k: ..\DISK_2.IMG). Use DISK_0_1.IMG as the
boot image when you burn the CD (see Chapter 7 too). The boot image will only
work if you incorporate Device Driver Fixpak 2 or higher.
If you boot from the CD the OS/2 installation program will start. You can
go to command prompt with F3. Unfortunately, the installation seems not to
work at this time (crashes with internal error after formatting or accepting
the installation partition).
7. Build an updated WSeB CD-ROM image
Building an updated WSeB CD-ROM is possible too. However, this is only a
preliminary support! I did not have time to test the updated CD at all. The
update process seems to complete OK, but I have no idea if installing from
the new CD will work. I release this functionality because I want to see if
there is enough demand for this. Please test it and report your experience!
Here comes the update process. There is no automated install script, you
should do everything manually. Create a directory called FIX in the directory
of UpdCD. In this directory create a subdirectory called SMP. Extract the
files from WSeB fixpak 1 and Device Driver fixpak 2. Copy the files from the
WSeB fixpak directory OS2.1, OS2.2 and OS2.4 to updcd\FIX. Copy the files
from OS2.3 and OS2.5 to updcd\FIX\SMP. MOVE all the files with the extension
.SM_ from updcd\FIX to updcd\FIX\SMP. Copy the files from BDD.1 and BDD.4 to
FIX. If there are conflicting files just overwrite them. Run PrpFP.Cmd from
the UpdCD directory with FIX as parameter. Create a directory BURN in the
directory of UpdCD and copy the WSeB CD here. Backup BaseFpk.Pin and replace
it with BaseFpk.W01. Start the update process with the following command:
UpdCD BURN FIX. Insert a floppy in drive A: and update the installation floppy
images with running UpdIF BURN FIX. Burn a CD from the directory BURN (see
chapter 6) and try the install.
8. Burning the new OS/2 installation CD-ROM
I have included with UpdCD the REXX script record.cm_ that I use to burn the
CD using mkisofs and cdrecord. If you rename this script to record.cmd than
Go4It will call it automatically when it finishes the build process. If you
use other packages to burn the CD, please be sure you disable the ISO9660 file
name translation option. Otherwise, all filenames containing - will be
renamed and the CD will be useless!!!
Use the enclosed recordb.cmd if you want to burn a bootable CD with cdrecord.
9. Creating updated installation floppies
Run CDINST from the new CD to create the installation floppies. Do not use
the original installation floppies with the new CD. It will not work for
Warp 4!
10. Limitations, known bugs
This program does not update floppy images (except the 3 images for the
installation floppies) or other than previously mentioned products.
Installing OS/2 from HDU using the updated image did not work for me. Others
reported that it works fine. Tell me if you succeed.
The installation floppies created from the new CD can only be used to install
OS/2 from the updated CD-ROM. To be able to incorporate Device Driver fixes
Go4It must delete some files used only by the installation from floppies and
installation on PS/2 computers.
Installing the 16-bits TCP/IP in combination with the updated 32-bits MPTS
backlevels TCPIPDLL.DLL and deletes NSLOOKUP.EXE. Restore them manually.
It seems that incorporating MPTS fixpak 8424/8425 breaks the CID installation
of MPTS. Go4It must backlevel the file IBMCOM\DLL\LAPSCID.DLL to enable the
installation of the updated MPTS.
Installing with the updated CD on partition bigger than 2GB fails.
I do not know what to do with the *.fmf files in the printer driver fixpak.
If you do, please tell me! (They are not on the original Warp CD, so I just
delete them.)
11. Miscellaneous information
Check the header of the REXX files for customizable parameters. Check the
UpdCD homepage for the latest information.
12. Disclaimer, Copyright
This program is free, and provided as is. I am not responsible for any damage
caused by this package. I have tested it only a few times, and it worked for
me. It might work for you too. If it does not, you might try to email me or
visit the page of UpdCD: http://xenia.sote.hu/~kadzsol/rexx/sajat/updcd.htm.
This package is a copyrighted freeware. It means that you are free to use
it, even in a business environment. However, you might not sell the package
or a modified version of it, or the CD-ROM's produced with UpdCD.
Zsolt Kadar
10.11.2000
email: kadzsol@xenia.sote.hu
URL: http://xenia.sote.hu/~kadzsol/rexx/sajat/updcd.htm