
Refresh OS/2 or eCS CD-ROM's with fixpaks and updates (version 2.2)
-------------------------------------------------------------------


1. Introduction

Are you tired of reinstalling fixpaks after adding or reinstalling system 
components? Are you tired of updating installation diskettes of having 
problems with installing OS/2 on large hard disks? Are you tired of booting
and installing using installation diskettes? You can avoid these problems by 
updating your OS/2 Warp 3/4, WSeB, MCP/ACP and/or eCS installation CD-ROM 
with the latest fixpaks. UpdCD takes all the fixpaks and other updated 
components you supply together with your original installation CD-ROM and 
builds an updated installation CD-ROM on your hard disk with all the new 
components already integrated!


2. UpdCD installation

2.1 Installation under OS/2 or eCS

The installation of UpdCD itself is very easy, just copy the distribution zip
to a directory of your choice (say updcd) and unzip it. If you plan to update
eCS CD-ROM's UpdCD should be installed on a partition which supports long
file names (HPFS, JFS, etc.). Run Install.Cmd to create the UpdCD objects on 
your desktop and to create the default config file (Updcd.Cfg). If you already 
have a customized Updcd.Cfg file from an earlier installation of UpdCD you may 
copy it to the UpdCD directory before you run Install.Cmd. In that case the 
installation program will migrate your settings. Do not unzip the distribution 
zip in the directory of an older UpdCD installation. I cannot guarantee that 
the mixed version will work.

If Install.Cmd runs OK the UpdCD graphical interface will automatically start 
and this readme file will be displayed. Check and adjust the parameters to
match your needs. 

If you have Object REXX installed, Install.Cmd will ask you to switch to
classical REXX. Use the SWITCHRX command to switch back to classical REXX, 
reboot your system and run Install.Cmd again. Do not switch to Object REXX 
during the use of UpdCD. I also advice you not to install REXX extenders, 
like Personal REXX. 


2.2 Installation under DOS or Windows

UpdCD does not run under DOS or Windows. However, UpdCD can create an OS/2
maintenance environment under DOS which will enable you to build an updated 
CD-ROM. Unzip the distribution zip to a directory on a FAT, FAT32 or HPFS 
partition which is big enough to create an updated CD-ROM. Run the UpdCD BATCH
program Mkdisks.Bat from the command prompt and follow the instructions on the
screen. UpdCD will create 3 boot diskettes which will enable you to start your 
system and run UpdCD. The boot diskettes will also support FAT32 partitions. 
However, I do not recommend you to install UpdCD on such a partition because 
I seem to get very strange errors under heavy I/O conditions. It seems to me 
that the OS/2 FAT32 driver is buggy. The UpdCD maintenance system can only 
handle Warp 4 CD-ROM's at this time.


3. Setting up (optional) UpdCD tools

UpdCD is designed to make use of some third party tools. One of the most 
important tools is the virtual floppy. If you want to create bootable
CD-ROM's or if you want to build an updated eCS CD-ROM you must install
one before you can use UpdCD. Otherwise, its use is optional and you may
use a normal 1.44MB floppy (A:) instead. However, I strongly recommend you
to install it before you begin to use UpdCD, because it will speed up 
processing dramatically. There are 2 virtual floppy programs available
for OS/2 at this time: SVDISK 1.17 (shareware) and VFDISK 2.0 (freeware).
You can find them on hobbes.nmsu.edu. Be sure that the control programs 
(SVDC.EXE for SVDISK and VFCTRL.EXE for VFDISK) are in your PATH. Do not 
forget to specify the drive letter of the virtual floppy in the UpdCD 
configuration.

To be able to burn CD-ROM's you need a burning program. UpdCD supports RSJ 
CD Writer (commercial product) and the Chris Wohlgemuth port of CDRecord 
(free product). If you plan to build a bootable CD-ROM you must install one 
of them. Otherwise, you may use any other burning program. If you decide to 
install CDRecord be sure that you also install the EMX run-time and the
ASPI router. If you want to use an IDE CD-ROM with CDRecord you also need
to install the IDE and the FLT driver of Daniela Engert.

Some of the UpdCD scripts use ATTRIB.EXE which is part of the optional
system tools delivered with OS/2. Be sure it is in your PATH.


4. Setting up fixpaks and updated components

Before you can start building a refreshed installation CD-ROM you should 
download and prepare the components you wish to incorporate. You need to
have all the components which are obligatory. The following products are 
supported by UpdCD:

Warp 4:
- Obligatory components:
  Base Fixpak 12/13/14/15/16, Device Driver Fixpak 1/2, Feature Installer 
  update 1.25, Netscape 4.61 update, Java 1.1.7/1.1.8 run-time update
- Optional components:
  MPTS fixpak 8424/8425/8620/8621, PEER fixpak 8402/8406/8412/8413/8414, 
	TCP/IP fixpak 0980/2001, JAVA 1.1.8 run-time fix, printer fixes 
	(laserjet*.exe, omni*.exe, pscript*.exe, plotters*.exe), MPTS update 
  8423/8610/8700, TCP/IP update 4.1/4.2/4.3, Java update 1.1.8/1.3 (run-time, 
  toolkit, samples, etc.), Netware Requester 2.12 fixpak, IBM installation 
	diskettes update and PMFax Lite 3.2 update. 

Integrating other JAVA fixes than the run-time fix is NOT SUPPORTED at this
time. All of the printer driver fixes should be expanded in the same 
subdirectory.	Do not use the TCP/IP 2001 fixpak without the TCP/IP 4.1
update.

Warp 3:
- Obligatory components:
  Base Fixpak 38/39/40/41/42/43, Device Driver Fixpak 2 
- Optional components:
  MPTS fixpak 8424/8425/8620/8621, TCP/IP fixpak 0959+0980, MPTS 
  update 8423/8610/8700, PEER fixpak 8196 (Connect) or LS fixpak 8532 (Server)

Warp Server SMP is not supported. Older base fixpaks (like 29) seems not
to work. One user reported that plane Warp 3 (blue spine) does not work.
I need more feedback on this!

WSeB:
- Obligatory components:
  Base Fixpak 1/2/3, Device Driver Fixpak 2, Netscape 4.61
- Optional components:
  MPTS fixpak 8621, MPTS update 8700, TCP/IP update 4.3, Warp 4 Feature 
  Installer products (Voice Type, Bonus Pack applications, etc.), LAN
  Server fixpak IP08603, JAVA update (1.1.8/1.3), JAVA run-time fix, printer 
	fixes (laserjet*.exe, omni*.exe, pscript*.exe, plotters*.exe)

MCP1/ACP1:
- Obligatory components:
  CP fixpak 1/2, Device Driver fixpak 2
- Optional components:
  Warp 4 Feature Installer products (Voice Type, Bonus Pack applications, 
  etc.), all the add-on components (see later) are integrated too
	TCP/IP 4.3 update, MPTS update included with TCP/IP 4.3 update, Netscape
  Communicator update

eCS:
- Obligatory components:
  eCS fixpak 2 (xr_c002?.zip), eCS utilities (update ecsutil.zip), eCS update 
	tool (update ecsupdt.zip), Serenity update 1 (ss?45011.zip), Serenity update
	2 (ss?45012.zip)
-Optional components:
	Kernel fixes (w4????.zip)

eCS fixpak 1 is not supported any more. Do not unpack the original zip files.
Unfortunately, the structure of the eCS fix tooling still changes very often. 
It means that a new version of the update tool can easely breake the eCS 
support in UpdCD at any time, so do not blame me if it does not work. :-((((

The current version of UpdCD was tested with the following update files:

Name:         Version:   Size:    Date newest file in archive:
ecsupdt.zip   1.09.10    161840   04/26/2002
ecsutil.zip   N/A        307467   04/01/2002
ss045011.zip  N/A        729845   04/10/2002
ss045012.zip  N/A        663938   02/10/2002

Create separate directories for every fixpak under the directory updcd\fixes, 
like updcd\fixes\fp15 for fixpak 15. Copy the fixpak here. If you have the rsu 
version (.zip extension) then you would use unzip to uncompress it. If you 
have the dsk version, use dskxtr12.zip from http://hobbes.nmsu.edu to unpack 
the files or let UpdCD to unpack them. Do not change the directory structure 
of the fixpaks! 

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 applicable (Java, Netscape, FI), unzip/uncompress the 
distribution file. All of the JAVA components should be placed in the same 
directory under update. The updated IBM boot diskettes should be placed in 
separate subdirectories under updates (e.g. updates\disk\disk1 and 
updates\disk\disk2). Expand the distribution files of all of the updated 
components if applicable. 

Example directory structure for Warp 4 fixes and updates:

e:\updcd\fixes
[...]
e:\updcd\fixes\XRYM015
e:\updcd\fixes\XRYM015\FIX
e:\updcd\fixes\XRYM015\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
[...]
e:\updcd\updates\disk\disk1
e:\updcd\updates\disk\disk2
[...]
e:\updcd\updates\pmfax

You can find a more detailed sample directory listing of the fixes and updates 
directories for typical configurations on the UpdCD homepage.

Use the "Test" buttons of the UpdCD interface to test if UpdCD correctly 
recognizes the components you have prepared. Be sure to select the correct 
OS/2 version from the combo-box before you run the test.


5. Additional options

Open GL 1.1 can also be integrated with Warp 4. Download the oglgold.zip from 
IBM, unpack it in a temp directory and add the WAVE.EXE, RASTER.DLL, 
OPENGL.DLL, LIBTK.DLL, GLUT.DLL and GLPIPE.DLL files to the subdirectory of 
the Feature Installer component update. 

The installation files on the boot disks (0,1,2) can be compressed with LxLite.
This way you can gain more space on the disks and you may add your personal 
fixes to them. Unfortunately, on some systems the compressed boot disks might 
not work correctly. You can enable compression by checking the "Compress disk" 
checkbox (General options) on the UpdCD interface. Furthermore, Lxlite can be 
configured via the LxLite.cfg file located in the UpdCD directory. You can gain
more space on the disks by adding *.add to the [pdd] section of this file. 
However, doing so might lead to traps on some systems during installation. 

UpdCD replaces most of the SCSI drivers on boot disk 1 with a dummy driver 
made by Daniela Engert. This is done in order to gain even more space on the 
disk. This will give you an additional 300K of free space, so you may easily 
add SCSI driver you need. 

SCSI drivers (*.ADD files) placed in the UPDCD\NEWINST directory will 
automatically be included in the boot image and on disk 1 if the "Add ADD's" 
option on the interface is checked. You should not add more than a few of these
drivers, because the space is limited on disk 1. 

The Warp 4 Feature Installer products (Bonus Pack, Voice Type, etc.) can also
be integrated with WSeB and MCP/ACP. To do so, create a directory called FI 
under the directory of UpdCD (e.g. UPDCD\FI) and copy the FI products from the 
Warp 4 installation CD here. They are located under the directory OS2IMAGE\FI. 
To save space avoid the products you do not need. The Bonus Pack applications 
and Voice Type are located in the directories OS2IMAGE\FI\BONUSPAK and 
OS2IMAGE\FI\VT. So if you want to integrate only these 2 applications with 
your MCP/ACP CD you would need to create the following directory structure:

[...]
e:\updcd\fi\bonuspak
e:\updcd\fi\vt
[...]

You also have to copy PACKAGE.CTL and FIBASE.RSP to the UPDCD\FI directory. 
FIBASE.RSP is located in the OS2IMAGE\DISK_11\BUNDLE file of the Warp 4 CD. 
You can extract it with the following command: UNPACK BUNDLE . /N:FIBASE.RSP
Do not modify the original FIBASE.RSP file.

The FI applications will be copied to the updated CD and can be installed
after installing WSeB or MCP/ACP by starting the Install Object program from 
the Selective Install folder.

You may also integrate kernel updates. To do so you need to create a directory
called addons under the base fixpak directory and copy the files from the 
kernel update zip here. The files you put here will overwrite the files 
contained in the base and device driver fixpaks. The directory addons should 
not contain any subdirs and the files should not be packed or zipped:

[...]
e:\updcd\fixes
[...]
e:\updcd\fixes\XRYM015
e:\updcd\fixes\XRYM015\addons\os2krnl
e:\updcd\fixes\XRYM015\addons\OS2LDR
[...]
e:\updcd\fixes\XRYM015\FIX
e:\updcd\fixes\XRYM015\FIX\OS2.1
[...]

You may also integrate SMP kernel updates with WSeB and ACP. To do so create 
an SMP subdir under ADDONS and place the SMP files contained in the 
distribution zip here:

[...]
e:\updcd\fixes\XRYM015\addons\smp\os2krnl
e:\updcd\fixes\XRYM015\addons\smp\OS2LDR
[...]

To integrate a kernel update with eCS simply copy the distribution zip 
(w4*.zip) to the CP2 fixpak directory. Do not unzip the zip!

MPTS and TCP/IP hotfixes (IC*.EXE) can also be integrated. To do so create the 
addons directory under the directory of the MPTS or TCP/IP fixpak, copy the 
hotfix files here and run/unpack the EXE to get the hotfix files:

[...]
e:\updcd\fixes\WR08621\addons\NSUPDATE.EXE
[...]
e:\updcd\fixes\UN_2001\addons\TCPCOEX.EXE
[...]

By putting the *.OS2 and the *.NIF files of network drivers (NIC's) in the 
MPTS addons directory you will add those drivers to the installation CD. UpdCD
will recognize those types of files and will add them to the MPTS drivers zip.
This way, the drivers will be available during installation:

[...]
e:\updcd\fixes\WR08621\addons\rtl8139.nif
e:\updcd\fixes\WR08621\addons\rtsnd.os2
[...]

If you have the Resource Compiler installed on your machine (RC.EXE, included 
with Warp 4 or higher, the EXE should be in the PATH) and UpdCD is installed 
on a partition which supports long file names, it is also possible to replace 
the resources (icons, bitmaps, text, etc.) attached to base OS/2 files. To do 
so, copy the replacement resource files to the base OS/2 fixpak addons 
directory:

[...]
e:\updcd\fixes\XRYM015\addons\SCENTER_dll.res
e:\updcd\fixes\XRYM015\addons\PNPMRI_dll.res
e:\updcd\fixes\XRYM015\addons\PMWPMRI_dll.res
[...]

As you can see, the resource files should be named after the correspondig base 
OS file. For instance, if you want to replace the resources included in 
SCENTER.DLL you must call the resource file SCENTER_dll.res (replace the
. with _ in the original file name and add the .res extension). Currently, 
this feature is only available for Warp 4.

It might be useful to know that there are a lot of resources included in
recent eCS fixtools (ss?45011.zip->dlgxr?4501enr.zip). If you have access
to the www.ecomstation.com site you may want to download this file. Be sure
that you are entitled to use eCS if you decide to integrate these resources. 
You can also extract existing resources using resource decompilers. I have
successfully used RDC2 for this job (example: RDC2 PMSHLTKT.DLL PMSHLTKT.RES). 
Once the resources (.RES files) are extracted you may manipulate them using 
any dialog editor (DLGEDIT from VAC or Warp Toolkit, WORKSHOP.EXE from Borland
C for OS/2). To get some of the tools mentioned above please see the following 
page: http://xenia.sote.hu/~kadzsol/fixpak. 

There is an updated Warp 4 DOS/Windows program database included with UpdCD. 
You may customize the database by editing the file NEWINST\DATABASE.TXT before 
building the updated CD. Thanks for Massimo for sending me this file!


6. Incorporating third-party products (add-ons)

You may also add third-party products to the updated CD of Warp4, WSeB or 
MCP/ACP. They will be selectable during the installation process. Each  
product is placed in its own subdirectory under the ADDONS directory of 
UpdCD. See the READ.ME file in that directory to see which add-on products 
are supported. Read the header of the install scripts (ADDONINS.CMD) to see 
which files you need to copy to that directory to enable the installation 
of the product. Please see the file UPDCD\NEWINST\ADDONS.CFG for the default 
installation options, like installation directory, version number, etc.

The incorporated add-on products can also be installed later by starting the 
Selective Install for Add-On products from the System Setup->Install/Remove
(Selective Installation) folder. They can also be uninstalled by starting the 
Selective UnInstall for Add-On products.

Please be aware that the (un)installation program does not take care of product
dependencies. For example, it will allow you to uninstall products which may be
needed by other programs which are still installed. For instance, it will allow
you to uninstall WarpIn, even if XWorkPlace is installed. If you still do this,
you will not be able to uninstall XWP any more using this program. At this 
time, the uninstallation program is not very sophisticated. In some cases, it 
simply starts a general uninstallation program like WarpIn and you have to 
manually select the components you want to uninstall. If this is the case, 
simply follow the instructions on the screen and close the uninstallation 
program when it is ready. In other cases, the IBM Feature Installer (FI) is 
used to uninstall programs. Most of the time, the Feature Installer needs a 
reboot to be able to remove locked files. Please do not uninstall more than 
one FI product without a reboot. Otherwise, the specified programs might not 
be uninstalled correctly. It is a good (and safe) practice to uninstall 
programs one by one and to reboot between the uninstallation steps.

Some add-on products (like PMMail/2, SDD) cannot be selected for installation
during the initial installation because they do not support unattended (CID) 
installation. You can install them later by starting the Selective Install for 
Add-On products program.

If you have install scripts for other products please send me a copy. I may 
include it in the next version of UpdCD. Thanks for Thorolf Godawa for sending 
me a few very useful scripts. Thanks for Jeffrey Smick for the Object Desktop 
installation script.


7. Building an updated CD-ROM on the hard disk

If you have correctly installed and configured UpdCD and the optional tools,
adequately prepared all the required fixpaks, updates and third-party 
products, then you are ready to build the updated CD-ROM on your hard disk.

Before you start the build process you should insert the original installation
CD-ROM in your CD drive. Be sure that no other process accessing the files
(fixes, updates, burn directory, CD-ROM, etc.) used by UpdCD. You should also 
insert a formatted 3.5 inch blank floppy in drive A: and specify A: at the 
drive letter if you are not using a real virtual floppy. Otherwise, just 
select the virtual floppy program you have installed and click on "Insert" 
to load a floppy. 

If the floppy loads correctly you may start the build process by clicking
on the "Build" button. The UpdCD build process should start. It will scan the
fixes and updates directory and it will ask you if you want to unpack any 
*.DSK file it finds. If you need to keep those DSK files be sure to backup 
them before running the build procedure because it will remove every 
successfully processed DSK file. If it is not the first time that you have 
run the build process it will clean up any temporary file left from the 
previous run. After that it will automatically list the detected fixes and 
updates. The language of your CD-ROM, the number of addon components are also 
reported. Although UpdCD does some limited checking, it is still you who 
should ensure that an appropriate set of fixes and updates are going to be 
integrated. With other words you should choose the right language and the 
right fixpak version matching the version of your OS. If you are unsure then 
you might consult the appropriate directory listing file found in dirlists.zip.

If you are satisfied with the detected components, then you may press ENTER 
to go on with the build process. The update procedure takes about 20 minutes
on my 500MHz PIII desktop. Your mileage may vary. If you have unchecked the 
"Expert mode" option before starting the build process it will pause between 
steps and you will have to press ENTER to continue. The updated CD-ROM files
will be placed in the UPDCD\BURN directory. During update the log file 
UPDCD.LOG is created which lists 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 build process. Check the 
log file to see what those warnings exactly mean. Files which are present in 
fixpaks but not used during update because they are not needed will also be 
logged as warnings. However, you should not expect hundreds of warnings.


8. Making the CD bootable

If the build process finishes without errors the menu of the burning process 
will automatically start. Otherwise, start it using the "Burn" button of the 
interface. If you have installed a virtual floppy you can build the boot image 
files necessary to make a bootable CD-ROM with option 2. This option does not 
exists for eCS, because UpdCD reuses the boot images supplied with eCS. If you 
do not want to make the CD bootable you may skip this option. 

If you start boot from such a bootable CD-ROM you will first get a boot menu 
which will enable you to continue to boot from the CD-ROM or to boot from the 
hard disk. If the CD does not boot check if the file CD_BOOT.FLT is present
in the updcd\bootimg\DISK_0_1.IMG directory. This file was released in DD fp2.
You may replace the driver with DANIBOOT.FLT by simply overwriting it before
creating the boot images.

UpdCD uses the CDBoot/2 package of Roman Stangl to create the boot images. 
Thanks Roman!


9. Burning the updated installation CD-ROM

If you have selected CDR/2 (CDRecord) on the interface to use you have to 
create a raw image file before you can actually burn the CD. This can be done 
by selecting option 3 from the burn menu. This option calls MKISOFS.EXE from
the CDRecord package to create the raw (ISO) image file. The name and the 
location of this temporary file can be set via the UpdCD interface, where
you must also specify the CdRecord directory, the burn log file, the burning
speed and the SCSI ID of your burner. If you have selected RSJ you do not
need to create a temporary image file, just skip option 3. The burning speed
and the other burning parameters you have to specify using the RSJ program
interface.

If you use a CD-RW you can blank it using option 4, otherwise go ahead with
option 5 which actually burns the CD-ROM. You may also run the previously 
mentioned commands in batch mode using option 6.

If you use other packages to burn the CD, please be sure that you disable the 
ISO9660 file name translation option. Otherwise, all file names containing 
- (minus) sign will be renamed and the CD will be useless!!! 

Be sure that the capacity of the blank CD-ROM is enough to hold the content of 
your burn directory! See the UpdCD FAQ how to create a second CD for add-on
products which cannot be placed on the first installation CD because of the
limited disk space.


10. Creating updated installation diskettes

If you did not make the CD-ROM bootable you need to create the installation 
diskettes. To do so, run the program CDINST from the updated CD to create the 
installation diskettes. Do not use the original installation diskettes with 
the updated CD-ROM. It will not work! 


11. Limitations, known problems

Installing the LVM add-on will automatically disable the VFAT, EXT2 and NTFS 
file system support, because the VFAT.IFS driver seems to hang the machine 
when LVM is installed.

UpdCD does not update floppy images (except the 3 images for the installation 
diskettes) 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 disks 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
UpdCD must delete some files needed for the floppy installation process, PS/2 
computers or old SCSI cards.

It seems that incorporating MPTS fixpak 8424/8425 breaks the CID installation
of MPTS. UpdCD must backlevel the file IBMCOM\DLL\LAPSCID.DLL to enable the
installation of the updated MPTS.

When booted from the CD the installation may complain about FAT32 or other
hidden drives which cannot not be found (SYS0038 error: Unable to find device).
By selecting "Return error code to program" a few times you should be able 
to continue with the installation.

When the installation program ask you to remove the disk from drive A: and 
press ENTER to continue, press CTRL-ALT-DEL instead if booted from the CD. 
Do not boot from the CD, but boot from the installation partition to continue 
with the installation. 

During installation of the updated FaxWorks the file FX002.LOP is not copied
to the hard disk. Copy it manually from OS2IMAGE\FI\BONUSPAK\FAXWORKS. It will
be fixed in a future release of UpdCD. 

Before burning the updated Warp 3 CD check if all of the directories are 
copied from the original CD. Directories which are not updated might not
copied to the burn directory. Copy them manually before burning the CD.

XFree86 3.3.6 traps or hangs the system in combination with Amouse 1.01. 
Use Amouse 2.0 or higher.

Since I have no original MCP1 I have tested with the eCS CD 2, which is 
in fact MCP1. Should not be a problem...

Use WarpIn 0.9.9 or higher, otherwise selecting ODIN and XWP addons will hang 
the installation. Do not use WarpIn and XWorkPlace 0.9.14 or higher. They 
cannot be installed unattended at this time.

When creating the ISO image from the updated eCS files some of the file names
are truncated. Here is an example from the burn log:

"Using os!2 essentials addition000.dat for 
L:/TVOICE/WiseProg/Desktop/OS2Essentials/os!2 essentials additional 
progra.dat (os!2 essentials additionalpro000.dat)"

On memory constrained systems (64MB or less) SVDISK sometimes gives problems 
(Drive not ready) when IMAGE.EXE tries to write a 2.88MB image file to the 
virtual floppy. Freeing some memory by closing running applications and 
restarting the build process seems to help.

Inserting a 2.88MB floppy using VFDISK might fail with the following message:
"Error: Could not allocate memory!". Specifying parameter 4 for VFDISK.SYS in 
Config.Sys and rebooting the system seems to help. 

eCS Pro and Warp Server SMP are not supported at this time.


12. Miscellaneous information

It is possible to tune the Config.Sys of Warp 3/4 or WSeB systems during
installation. For instance you can add extra lines to it or change existing
lines, like the PATH or LIBPATH. UpdCD uses this feature to add some new 
environment variables to the Config.Sys. Those actions are defined in the
file NEWINST\TUNECFG.CFG. You may add your own actions to it. Please see the 
the header of the file for more information. Tuning the OS/2 INI files is also
possible. Please see the file NEWINST\TUNEINI.CFG for details.

If you have added the DANI IDE driver to its add-on directory (21_DNIDE), you
may replace the IBM IDE driver (IBM1S506.ADD) everywhere in the updated CD
by checking the "Add DANI driver" General option. Since the DANI driver is 
somewhat bigger than the IBM driver we may run out of space on install disk 1
and when UpdCD tries to copy the driver we may get an error. You may solve 
the problem by enabling compression ("Compress disk") or by using the 
compressed version of the DANI driver. If you have also added the DANIBOOT.FLT 
driver to the 21_DNIDE directory and the DANIDASD.DMD to the 22_FAT32 
directory, checking this option will also replace the CD_BOOT.FLT and 
OS2DASD.DMD files with the DANI version of those files. This option might be 
useful if you have install problems on very large IDE hard disks. OS2DASD.DMD
will not be replaced on LVM-enabled systems.

If you do not like the "viewer" program used to display the burn log you may
specify your own choice by editing the viewer = 'more <' line of UpdCD.Cfg.

Check the UpdCD homepage and discussion group for the latest information. 
Before you ask questions, please read the latest UpdCD FAQ on the UpdCD 
homepage and the messages in the discussion group. Do not email me directly, 
please post to the UpdCD discussion group instead: 

http://groups.yahoo.com/group/updcd

If you cannot find some components you want to integrate try these pages:

http://groups.yahoo.com/group/updcd/links
http://www.warpupdates.mynetcologne.de/english/site_contents.html

If you still find it to difficult to download all the fixpaks and configure 
UpdCD you might want to order the Warp 4 Update Kit. The Warp 4 Update Kit 
contains all the fixes and updates you order and will automatically install 
UpdCD on your system including the optional tools. Currently, English, German,
Brazilian and Hungarian versions are available (the installation program is 
only in English). Check the UpdCD homepage for details. Please let me know if 
you are interested in buying an Update Kit for an other language or for other 
versions of OS/2 (WSeB, Warp 3).


13. Disclaimer, Copyright

This program is free, and provided as is. I am not responsible for any damage
caused by this package. I can only perform limited testing and UpdCD seems to 
work OK for me. It might work for you too. If it is not the case, you might 
try to post your problem to the UpdCD discussion group: 

http://groups.yahoo.com/group/updcd

Before you post, try to reproduce the problem. Quite often problems with the
CD-ROM media (like bad sectors) might cause a lot of trouble. Please be as 
specific as you can! Do not forget to save the UpdCD log and cfg files!

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. They are
only for your own use.

The various OS/2 versions and some of the components which can be integrated 
are copyrighted, commercial or shareware products. Please be sure that you are 
entitled to use them when working with UpdCD.


Zsolt Kadar
07.02.2002
email: kadzsol@xenia.sote.hu
UpdCD homepage: http://xenia.sote.hu/~kadzsol/rexx/sajat/updcd.htm
