## UpdCD FAQ

- Q1: How can I see which files are in those bundle files?
- A1: Run the enclosed script cdlist.cmd on your Warp CD. It will list all the plain files and the content of zipped or packed files. You should have unzip.exe in your PATH. You can find the listing of a US Warp 4 CD-ROM enclosed to see which CD I used to make the plug-ins included in UpdCD.

- Q2: MPTS fixpak 8610 looks quite different from the MPTS in directory CID\IMG\MPTS. Are you sure that this can be replaced with the fixpak?
- A2: Yes, it works. Just do it!

- Q3: Will the 32-bit MPTS work with the TCP/IP of Warp?
- A3: Yes, it seems to work OK. However, some people have some stability problems with this combination. Give it a try, but use the latest fixpaks available!

- Q4: I want to integrate TCP/IP 4.3. Should I use MPTS fixpak WR0862x?
- A4: No, just use MPTS (08700) included with TCP/IP 4.3. No other MPTS fixes are needed.

- Q5: What is the difference between MPTS fixes and updates?
- A5: MPTS updates like WR?08610 or WR?08423 can be used to fully replace MPTS. MPTS fixpaks (WR?08621, WR?08425) should be applied on top of MPTS installations or updates. If you see MPTS.EXE in an MPTS distribution that it is an MPTS update, otherwise it is a fixpak.

- Q6: I need to update the scsiadds file with newer SCSI drivers. How can I do that?
- A6: Copy the driver to the UPDCD\NEWINST directory and check the "Add (SCSI) ADD's" option on the graphical interface before you run the build process. The driver will be copied to the right place and the Config.Sys will be updated.

- Q7: Will the installation of OS/2 from the updated CD on top of an existing installation preserve the settings?
- A7: Yes, it will preserve the configuration files and will move the desktop objects to the Previous Desktop folder, as the original installation of Warp 4 did. However, there are some known problems with migrating multimeda. The information below comes from a readme file of MCP1:

          If you are installing over a previous version of the operating
          system, make sure the Multimedia Device Support field on the
          System Configuration panel is set to "None". Multimedia Support
          requires a second installation step, using Selective Install,
          after completing installation of the base operating system.
          See "Migrating Multimedia Support". This step is not necessary
          if you are doing a clean installation.

          To migrate Multimedia Support:

          Open the OS/2 System folder, then the System Setup folder,
          then the Install/Remove folder, then start Selective Install.

          On the first panel, System Configuration, click on the icon
          to the left of the Multimedia Device Support field. A list
          of available drivers will be displayed. If you find the
          driver you want to install, select it. If you don't, leave
          the selection blank. In either case, continue with Selective
          Installation to install the rest of the Multimedia Support.

          If the multimedia driver you wanted to install was not in
          the list, see "Manually Installing Multimedia Drivers" for
          information on how to install your driver.

          Click Next to continue with migration.

          Once you get to the OS/2 Setup and Installation panel (the
          third panel), select the checkbox labeled Multimedia Software
          Support.

          Select Next to continue with Selective Installation. Follow
          the directions as they appear on the screen.

          At the end of Selective Install, restart your system.
          The multimedia drivers should be working correctly.

- Q8: What is the difference between updates and fixes?
- A8: Update means complete replacement of a given product. Basically, you can fully replace the corresponding base product with it. A fixpak is just the opposite, because it does not contain all the files of the base product. It should be installed on top of the base product. For example, TCP/IP 4.3 is an update and OS/2 Fixpak 14 is a fixpak. Consult the documentation of the given component if you hasitate.

- Q9: Could you add a section to the readme that specifically lists which files I need to download?
- A9: No, because it is not possible for me to link all the components supported by UpdCD including all the NLS versions. However, on the main UpdCD page you can find a few links which might help you. If you are still unable to set up UpdCD correctly, than you might want to order the Warp 4 Update Kit.

- Q10: It takes a very long time to make the updated CD. Why?
- A10: First of all, check if the DELDIR environment variable is enabled in the config.sys of your system. Rem it out if it is active and reboot your system. Increasing the disk cache might also improve the performance significantly. If you have enough space, put UpdCD on an HPFS or JFS partition. Consult the readme to see how to use a virtual floppy drive with UpdCD.

- Q11: I get a lot of errors and warnings when I run UpdCD. What next?
- A11: Check if you have enough space on the UpdCD partition. Check if you use the right combination of fixpaks and updates. Do not use other REXX variant than the classis REXX delivered with OS/2.

- Q12: I have an older version of UpdCD included on the Warp Update Kit. Can I use the newer version of UpdCD?
- A12: Yes, of course. Firstly, copy and unzip the distribution zip of the new version to a new directory. Copy UpdCD.Cfg from the old UpdCD directory to the new UpdCD directory. Run Install.CMD. Copy the fixpaks, updates and addons directory trees from the old UpdCD directory to the new one. Be careful with the addons directory, sometimes the directory structure changes between versions. Do not overwrite the Addonins.Cmd files provided with the new version of UpdCD.

- Q13: Can I use RSJ CD-Writer with Update CD? I don't have a SCSI drive...
- A13: Yes, of course, Record.Cmd supports RSJ since version 1.8. Basically, you may use any CD-Writer software to burn the CD. Please note, cdrecord also works with IDE devices if you install the DANI ATAPI filter driver. In the UpdCD configuration file you need to specify the SCSI device ID. This is a 3 digit number, which specifies the number of SCSI buses, the SCSI ID of the burner and the LUN number. If you do not have a SCSI bus at all, only an IDE burner, you need to specify 0,1,0 as the value of the device parameter.

- Q14: Should I apply the Warp Update Kit on top of my existing Warp 4 installation?
- A14: No really. The Update Kit allows you to set up UpdCD on your system. With UpdCD you can create a new Warp 4 installation CD-ROM including all the components you selected on the WUK order page. This means you integrate those components (fixpak 15, ddfpk 2, etc) and you do not need to apply it on top of an existing system. UpdCD was tested on Warp 3, Warp 4, WSeB, MCP1, ACP1 and eCS.

- Q15: I created a bootable CD by following all the instructions given. The CD starts, the blue IBM screen appears, then the process hangs with the message: "OS/2 cannot operate your hard disk".
- A15: You might have a SCSI adapter which is not supported by Warp 4. If you have the correct driver for your system copy it to the UPDCD\NEWINST directory and check the Add ADD's option of the graphical interface before you run the update. If you need to manipulate the boot image by hand go to the burn\updcd\bootimg\DISK_0_1.IMG directory. This contains the boot image files which you can change before you create the boot image. If you change the Config.Sys do not forget to change the copy of it in the burn\updcd\bootimg directory. This Config.Sys is used after phase 1 of the installation. In other cases disabling hardware detection (F6) seems to help. If you have a SCSI CD-ROM check in the SCSI BIOS (CTRL-A) if the following settings (if present) are set to NO: Enable sync negotiation, Enable disconnection. The compressed DANI IDE driver (version 1.3.8) also seems to break the boot process, because it is not able to find the second boot image (Disk_2.IMG). In this case you might want to create and insert installation disk 2 in your floppy drive before booting from the CD. This should help the boot process to find the "missing" files and to finish the installation. For other tips, please visit the UpdCD discussion group and look for the messages 861 and 1062.

- Q16: Adding JAVA toolkit, samples, etc. fixes creates a lot of warnings.
- A16: This is a problem with those fixpaks :-). Unfortunately, the same file is called differently in the fixpak than in the original package, so UpdCD is not able to find and update those files. This will result in a lot of warnings (file xxx was not used). This is a fundamental problem, but I will try to find a solution. Until then, use only the run-time fix.

- Q17: Is it possible to use the fixpaks included on the Warp Update Kit to update an existing system?
- A17: Yes, of course. Copy the required fixpak from the CD (located in the fixes\xxx subdir) to your hard disk. You need to download and put the latest fixpak installation tool (csftool) to the same directory. After you copied the necessary files to your hard disk (let us say to c:\temp) you should issue the following commands to install it: set csfutilpath=c:\temp, set csfcdromdir=c:\temp, service. This will do it.

- Q18: I do not want to go through during installation all those extra installation questions. However, I would like to install some of the add-on products.
- A18: Sure. Before burning the CD replace burn\ibminst\npconfig.exe with npcfg2.exe. Check out the file burn\ibminst\tables\addons.cfg. This file contains the default installation parameters (directory, path) of the addons product. Create a file called npconfig.out in burn\ibminst containing something like this:

      E:\NETSCAPE
      runtime 1 D:
      unicode 0 D:
      ttengine 0 D:
      toolkit 1 D:
      tlktdoc 1 E:
      samples 1 E:
      debugger 1 E:
      swingruntime 1 E:
      swingtoolkit 1 E:
      rmiiioptoolkit 1 E:

  The first line defines the installation path of Netscape. The next lines define the JAVA installation drives. 1 before the drive means install the component. Burn the CD and create the installation diskettes. On disk 1 edit the config.sys and add something like to to it:

      SET ADDONINS_PRPRC=1
      SET ADDONINS_SCDDR=0
      SET ADDONINS_DNFLT=0
      SET ADDONINS_DNIDE=0
      SET ADDONINS_FAT32=1
      SET ADDONINS_EMXRT=0
      SET ADDONINS_USBDV=0
      SET ADDONINS_LVMJS=0
      SET ADDONINS_WRPIN=0
      SET ADDONINS_ODN32=0
      SET ADDONINS_XWPLC=0
      SET ADDONINS_NSPIP=1
      SET ADDONINS_BOS2A=0
      SET ADDONINS_FLOS2=0
      SET ADDONINS_ACRB3=0
      SET ADDONINS_NRAV2=0
      SET ADDONINS_FCOM2=0
      SET ADDONINS_OS2CM=0
      SET ADDONINS_XFR86=0
      SET ADDONINS_PSPRC=1

  Parameter 1 means install the component. Save the config.sys and start the installation.

- Q19: I get the following error: "Error: @copy addons\21_DNIDE\DaniS506.ADD x:\ibm1s506.add (rc=1)"
- A19: Please use the compressed version of the DANI driver. It is included in the distribution zip. You may also try to enable compression (Compress disk) and replace old SCSI drivers with a dummy driver (check the Add (SCSI) ADD's option).

- Q20: I did not receive the WUK, the WUK is damaged, the WUK does not work...
- A20: Contact me and I will send you a replacement free of charge.

- Q21: I payed but you did not received my payment. What next?
- A21: Please resend the payment. You might want to email me for my bank account or pay using paypal.

- Q22: I have installed XFree86 but it does not work. Why?
- A22: Before running XFree86 you must configure it. Run the "X-Server Configuration" program form the XFree86 folder and answer the questions. If the configuration file is succesfully created, check the installation with running the program "Check XFree86 Configuration". If it returns only warnings you might try to start XFree86 with clicking on "Start X". If it is still does not work you might need to install an other X-server. UpdCD installs the SVGA server, because it supports quite a lot of chipsets. Refer to the XFree86 documentation on how to install an other X-server. If you want UpdCD to install an other X-server you need to edit the line containing xserver.exe = 'XF86_SVGA.exe' in the addonins.cmd of XFree86. One more thing: it will never work without TCP/IP installed...

- Q23: My language is not supported by the WUK. Can you make a special version for me?
- A23: No. Unless there are at least 4 more people who want to have the same version.

- Q24: How can I add new addon products?
- A24: Go to the updcd\addons directory and create a subdirectory for your product. The name should start with a 2 digit number followed by an underscore and 5 characters. Place the installation files here and the installation script which should be called addonins.cmd. Go to newinst\addon.cfg and add a section for your product. The section name of the product should be the same as the name of the addon directory holding your files. The variables under the section XX_GLOBAL are public variables. It means that all of the installation scripts can access them. The product variables overrides the global variables. The variables can be used from the addonins.cmd by referring to environment variables having the same name. For example, referring to %PRODUCT_NAME% in a batch addonins.cmd belonging to 32_XWPLC would have the value XWorkPlace. In this way you can specify in addon.cfg the installation parameters your script should have. During installation a graphical interface is used to select which addon components are installed. As you can see, adding a new product is not easy. Probably you want to add your stuff to the pre- or postprocessing scripts (00_PRPRC, 99_PSPRC) instead. These scripts are called every time the (selective addon) installation runs.

- Q25: How can I make a bootable CD with RSJ?
- A25: Start Record.Cmd (Burn button) and create a boot image using option 2 if you are building a non eCS CD-ROM. Use option 5 to burn the CD.

- Q26: When I run Xfree86 I get a TRAP or my machine hangs.
- A26: You are right. It seems that if AMOUSE 1.01 is installed XFree86 3.3.6 traps. Upgrade to version 2.0 of Amouse.

- Q27: I have an LS210 drive as drive A: which does not seem to work with UpdCD.
- A27: Unfortunately, the FLT driver of the LS120 drive does not work with some of the tools UpdCD is using. Install VDISK or SVDISK and specify the drive letter of the virtual floppy in UPDCD.CFG as the value of the flpdrv parameter.

- Q28: When I try to insert a 2.88MB virtual disk using VFDISK I got memory a memory allocation error.
- A28: In the config.sys append the parameter 4 after the line of VFDISK.SYS (e.g. `DEVICE=C:\OS2\BOOT\VFDISK.SYS 4`). In this way VFDISK will start with a 2.88MB disk inserted and will reserve enough memory to handle every virtual disk type.

- Q29: During installation INSTALL.EXE crashes and the file POPUPLOG.OS2 is created in the root of the boot drive.
- A29: Go to X:\OS2\INSTALL and find the file INSTALL.LOG. Open the file in an editor and find the last line. Issue the command described by this line and see what happens. If the command cannot be executed you might need to burn an other CD, because the problematic one contains an error (bad block).

- Q30: I would like to use an older OS/2 fixpak with UpdCD, but it does not recognize it, even if it is correctly unpacked in the fixes directory.
- A30: UpdCD detects OS/2 fixpaks by looking up a special string in the SRV_PROD.OS2 file. Unfortunately, some older fixpaks (older than fp 12) does not always seem to contain the string UpdCD is looking for. You can bypass this problem with replacing the SRV_PROD.OS2 file with the same file from a newer fixpak (fp 12 or higher).

- Q31: I do not have a CD burner. Can I still use UpdCD?
- A31: Yes, of course. Even without a CD burner you can create an updated CD image on your hard disk. After that, you can transfer the image to an other computer which does have a burner or you can try to install from hard disk. To do so, you need to edit the Config.Sys on boot disk 1 and add the directory which contains the OS/2 files to the line of SET OS2_SHELL as a parameter. It seems that you also have to define the SOURCEPATH variable which should point to the same directory. Example:

      SET OS2_SHELL=SYSINST2.EXE X:\UPDCD\BURN\OS2IMAGE
      SET SOURCEPATH=X:\UPDCD\BURN\OS2IMAGE

- Q32: I get one error when I try to build: Error: X:\SYSINST2.EXE <- D:\UPDCD\FIX\SYSINST2.EXE rc=1. Is it a problem?
- A32: Yes, it indicates that there is not enough space on the 1.44MB (virtual) floppy. You may try to enable compression, remove unnecessary ADD drivers from the NEWINST directory or disable addition of ADD's.

- Q33: Can you send an updated CD-ROM to me? I will pay you $$$ for it...
- A33: No. I am not entitled to sell OS/2 CD-ROM's. If you email me with this question I will not respond. Check out the Warp Update Kit (WUK) instead.

- Q34: I get a TRAP in VFDISK during the burn process. How can I fix it?
- A34: If you have the FAT32 driver installed rem the driver out from the Config.Sys and reboot your system before running the burn procedure. Furthermore, on FAT32 aware OS/2 systems, the line loading VFDISK must be placed after every other line involving file systems, otherwise VFDISK will be installed with wrong drive letter.

- Q35: I get an error message during loading VFDISK stating that the driver cannot reserve a drive letter. What next?
- A35: It seems that you have reserved the last drive letter available using the RESERVEDRIVELETTER option in your Config.Sys. Check if there is a free drive letter for VFDISK to reserve.

- Q36: If I run Record.Cmd I get the following message:

      This command file records a wave file using the MultiMedia
      REXX string interface.

      record filename

- A36: You you are running Record.Cmd belonging to Multimedia (\mmos2\record.cmd). Run Record.Cmd from the UpdCD directory to be sure that you run the script belonging to UpdCD. If you are already running it from the UpdCD directory be sure that Record.Cmd exists in that directory.

- Q37: I would like to add more add-on products to the CD but it is full. I already use a 700MB CD-ROM...
- A37: You may want to add the additional add-on products to a second CD. If you do so you will be able to install these products after the installation of the first CD starting Selective Install for Add-On products from the System Setup, Install/Remove folder. The best way to create the second CD is to reuse the image of the first CD. After burning the first CD go to the burn directory and delete everything except the burn\updcd directory. Go to the burn\updcd\addons directory and delete the add-ons products which are already added to the first CD. Be sure that you do not delete the 00_PRPRC and 99_PSPRC directories and the read.me file. Add the new add-ons. Be sure that the addons.cfg file used for the creation of the first CD (see newinst\addons.cfg and/or burn\ibminst\tables\addons.cfg) contains the add-on definitions for both CD-ROM's. Leave the other directories and files alone in the burn\addons directory.

- Q38: I don't like the Internal Revision Number displayed during booting. Is it possible to supress it?
- A38: Of course. Go to the burn\os2image\disk_0 directory before burning. Create a file os2norev.$$$ in that directory. Issue the following command (replace e:\updcd with your UpdCD installation directory):

      e:\updcd\bin\pack2 os2norev.$$$ bundle /H:\OS2\BOOT\os2norev.$$$ /A

  Delete os2norev.$$$ and start the burning process.

Updated on 06.22.2002 by Z. Kadar (kadzsol@xenia.sote.hu)