TeamDUKE Patching System: 0.61 to 0.62

NOTE: You must have TeamDUKE 0.61 already installed, otherwise it will
      not patch.

INSTRUCTIONS:
-------------
1. Extract CTFPATCH.GRP, TDSETUP.BAT, TEAMDUKE.BAT and USRFILES.BAT
   from this ZIP file and place it into the directory where TeamDUKE is
   installed.

2. Run TEAMDUKE.BAT or TDSETUP.BAT as if you were running TeamDUKE
   normally.

3. A setup screen should appear asking if you wish to continue with
   the installation - Press Enter to continue, or Esc to Exit.  If
   the screen doesn't appear, go to "TROUBLESHOOTING".

4. It's patched!  Easy, isn't it?

5. For information on what was changed, view UPDATE.TXT after patching
   is complete.

TROUBLESHOOTING:
----------------

Q. The Patching Setup Screen didn't appear when I ran TEAMDUKE.BAT
   and/or TDSETUP.BAT

A. Check that you have CTFPATCH.GRP in the same directory.  If you do,
   then extract all the files from it (TEAMDUKE.BAT and TDSETUP.BAT
   do it automatically) and run PATCHER.EXE.  The error message will
   be displayed here.  The error message will also appear when you run
   TEAMDUKE.BAT and TDSETUP.BAT, but it only lasts for a split second,
   which by far isn't long enough for you to read.

Q. I got the message "Bad command or filename" while running
   TEAMDUKE.BAT and/or TDSETUP.BAT - but TeamDUKE ran immediately
   after the message was displayed.

A. There may be a bug in CTFPATCH.GRP, TEAMDUKE.BAT or TDSETUP.BAT.
   If this happens, try extracting the files from CTFPATCH.GRP
   manually, and then run PATCHER.EXE.

   If the message "Bad command or filename" still appears, or you get
   an error while extracting the files from CTFPATCH.GRP, try
   re-downloading the patch from Garjen.  If it still happens, inform
   me at "gareth@garjen.co.uk" and I'll look into it.  Include
   attachments of CTFPATCH.GRP and your copies of TEAMDUKE.BAT and
   TDSETUP.BAT with your e-mail.
   
Q. I got the message "Bad command or filename" while running
   TEAMDUKE.BAT and/or TDSETUP.BAT", and TeamDUKE didn't run.

A. Chances are that either TeamDUKE or EDuke has become corrupted.
   Reinstall.