The first official patch for MechWarrior 4: Vengeance.
Microsoft MechWarrior: Vengeance Readme File for the MechWarrior 4 Patch Ver. 1.5 April 2001 Microsoft Corporation, 1998-2001. All rights reserved. Welcome to Microsoft MechWarrior: Vengeance. This Readme file contains information about the most recent changes and improvements provided by the MechWarrior 4 Patch version 1.5. You must upgrade to the patched version 1.5 in order to see multiplayer servers that are running the patch 1.5. CONTENTS A. Installation B. Current Gameplay Issues C. Troubleshooting Error Messages During MechWarrior 4 Patch Installation This patch contains information to help you troubleshoot issues with MechWarrior: Vengeance. You can also find information about MechWarrior: Vengeance and Microsoft Product Support Services in the printed manual and on the MechWarrior: Vengeance Web site (http://www.microsoft.com/games/mechwarrior4/). A. Installation MechWarrior: Vengeance must be installed on the system before installing the patch. To install MechWarrior: Vengeance Patch, double-click on PatchApply.exe located in the folder where the patch files were extracted. B. Current Gameplay Issues This section lists gameplay issues previously found in MechWarrior: Vengeance and describes the solutions provided by the MechWarrior 4 patch. 1 Warping or Increased Lag: This Patch addresses the Warping or Increased Lag (also known as 1,2,3 warp) introduced while trying to defeat the speed hack. 2 FPU Exception Fix: Some servers/clients were occasionally experiencing an FPU Exception related to Long Tom use. This exception has been located and removed. C. Troubleshooting Error Messages During MechWarrior 4 Patch Installation The following error messages may appear during the installation of the MechWarrior 4 patch. • 0001: Illegal Input Option '<Option>' The specified option is either an invalid option, or the patch user does not have the appropriate user level to use the option. • 0002: Insufficient Memory PATCH needs more memory free for its internal tables. There is insufficient memory available when running the patch. • 0004: Specified Update Directory '<DirName>' does not exist The patch user specified a directory to update that does not exist. • 0005: Specified [Update|Backup] Directory '<DirName>' is not a valid directory The patch user specified a directory name for either the Update or the Backup directory that is not a valid directory name. An existing file with the same name as the specified directory could cause this message. • 0006: Cannot Find Patch File '<FileName>' PATCH was not able to locate the specified patch file. • 0007: Error Opening Patch File PATCH was able to locate the patch file but could not open the file to read it. This could be a DOS error or due to a corrupted disk. • 0008: PATCH.EXE and Patch File incompatible - Need to update PATCH.EXE PATCH.exe and the patch file are incompatible versions. PATCH.exe can update older versions of patch files but not those created with a newer version of the data file format. You need to obtain a later version of the Patch program to apply this patch. • 0009: Invalid Patch File '<FileName>' PATCH.exe was unable to read correct information from the specified patch file. The file is either not a patch file or has been corrupted. Obtain a new copy of the file and then rerun PATCH. • 0010: Failure Creating Backup Directory '<DirName>' PATCH was unable to create the specified backup directory. • 0013: Failure Opening Backup Destination File '<FileName>' PATCH was unable to open the new file to copy the original file to. • 0014: Failure Writing Backup File '<FileName>' PATCH was unable to write the original file to the backup version. • 0015: Old File does not exist PATCH needs bytes from the existing version of a file in order to build the new file; however, it was unable to locate the old file. • 0016: New File already exists A file with the same name as the new file being built already exists. The existing file will be copied to the backup directory if the Backup option is on. • 0017: Failure Opening Old File: 'filename' PATCH was able to locate the old version of a file but the open failed. This is probably caused by a DOS error. Try rerunning PATCH. • 0018: Failure Opening New File: '<FileName>' PATCH was unable to open the named file while attempting to open this file to create a file for the updated version of the system. This can be caused by a disk or network error or if a directory exists by the same name as the file that PATCH is trying to open. • 0019: Failure Writing to File An error occurred while PATCH was trying to write bytes to a new file. • 0020: Failure Reading from File An error occurred while PATCH was trying to read bytes from an old file. • 0021: Failure Seeking to Position in File PATCH was unable to seek to a position within a file. This is probably caused by a DOS error or a corrupted disk. Try rerunning PATCH. • 0022: Failure Renaming File PATCH was unable to rename a file. This is probably caused by a DOS error or a corrupted disk. Try rerunning PATCH. • 0024: New File already exists The specified file has already been patched. PATCH does not need to patch this file. • 0025: Verify of New File Failed. Possible Internal Error The file that PATCH built is not valid. Users should never see this message. • 0026: Failure Creating Overflow File: 'FileName' PATCH was unable to open a file for its overflow information. This is probably caused by a DOS error or by a full disk drive. • 0027: Overflow File Write Failure PATCH was unable to read from the overflow table it created to hold data that did not fit in its internal tables. This was probably caused by a DOS error or a corrupted disk, or there was insufficient room on the disk for the file. • 0028: Overflow File Read Failure PATCH was unable to read from the overflow table it created to hold data that did not fit in its internal tables. This was probably caused by a DOS error or a corrupted disk. • 0029: Insufficient Disk Space to Apply Patch - You need at least <Size> bytes free on drive <DriveLetter> for <Feature> PATCH needs at least the specified number of bytes to perform the patch process. If UNDO or BACKUP is ON, PATCH needs room to back up all of the files making up the original system and also the room needed to build the new system. If both BACKUP and UNDO are OFF, PATCH only needs room to back up the biggest of the files being patched. • 0030: Error opening serialization file '<FileName>' PATCH either could not find the serialization file or the open failed. If the open failed, the probable cause is a DOS error. Retry the operation. • 0031: Error reading serialization file '<FileName>' PATCH cannot seek to the correct position in the serialization file or read the correct number of bytes from the file. Possible causes are invalid positions and lengths specified while running PATCHBLD. • 0032: Failure Setting File's Time/Date Stamp PATCH was unable to set the time/date stamp for the updated file or for a freshly backed up file. This error should never occur; but if it does, it has probably been caused by a disk failure or network file-sharing problem. • 0033: Failure creating temporary file PATCH was unable to create a temporary file to hold the new file or to hold overflow information. Try rerunning PATCH and if it still does not work, reduce the number of temporary files required by disabling BACKUP and UNDO. • 0034: Neither command line parameter specified is an existing directory Multiple parameters were given on the PATCH command line that were neither valid PATCH options or existing directories. If the user specifies multiple parameters, at least one must be a valid existing update directory. • 0035: Only one file and one directory may be specified on command line The user specified more than one patch file and one update directory on the PATCH command line. • 0036: Old file not found. However, a file of the same name was found. No update done since file contents do not match PATCH was unable to locate an exact match for the original file to be updated, but PATCH was able to locate a file with the same name as the original file. However, the file found did not have either the same size or checksum as the actual original file that PATCH is seeking in order to perform the update. • 0037: Error opening error message file PATCH was unable to open the file PATCH.ERR for storing error messages. The probable cause is a DOS error. Retry the operation, or specify the NOERRORFILE option on the PATCH command line. If you experience an IPF (internal page fault) error while installing the patch on Windows 98, please make sure your virtual memory is active. This can be checked by right-clicking on My Computer, clicking on properties, clicking on the Performance tab, and clicking on Virtual Memory. You might experience a 0036 error when installing on a Swedish system. If you encounter this error, uninstall and reinstall MechWarrior: Vengeance, and run patchapply again.
There are no comments yet. Be the first!