User manual MAXTOR APPTIMIZER2

[. . . ] 10 **NoSurround= / **Surround=. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Game Data to modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 *[END]*. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Game Data Modifications methodology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Simple replacement strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] 4) Now select "Edit" from the main menu, then select "Copy Key Name". 5) Finally go to the MtxCfg. ini file, right click and select "Paste" and the full registry file name will be copied. If "GameLoc=" is left blank or the registry value could not be found, the browse and scan buttons will automatically be enabled and user will have the option to press the browse or scan button in order to search for the game. When the game has been located the actual game path (not the registry path) will be saved next to this value, thus replacing the registry location text or blank field ­ which ever is the case. NOTE: If no registry key can be provided it is manditory that you leave this field blank. NOTE: DO NOT PLAY WITH THE WINDOWS REGISTRY IF YOU DO NOT UNDERSTAND HOW IT WORKS OR WHAT YOU ARE DOING! **SubFolderName= This is used to tell the `Apptimizer' app that the configuration file is not in the same location as the games EXE location, but rather one or several folders below. In the example; **SubFolderName=baseq3 the subfolder name is only one level below and is thus represented as <game. exe_path>\baseq3\*. cfg . Should the game configuration file be located several folders below, it should be written like this: **SubFolderName=FolderName1\FolderName2\FolderName3. . . . . do not forget to put the `\' between each folder name otherwise it will be interpreted as a single file name. **CfgIniFileName= This section has three parts: 1) Most games contain only one initialization file. This file name should be written in the same fashion as the Quake 3 sample above, specifying the exact CFG or INI file name. This filename will be used to compare and validate the user supplied path. Sample Entry: (single configuration files) *[Duke Nukem: Manhattan Project]* **SubFolderName=duke\base **CfgIniFileName=config. cfg **GameExeName=DukeNukemMP. exe **ShortCutName= DukeNukemMP Optimized **ShortCutParameters= **LatestPatchReq= **MSG1= **NoSurround=False **Surround=True uset g_cam_fov ||"110" uset r_device ||"gl" uset r_mode ||"2400x600x32" *[END]* 2) In some cases a game will contain more that one configuration file. If this is the case, it is necessary to use the key word `MULTIPLE' with no extension as the **CfgIniFileName. The app will interpret this to mean that it will be modifying several configuration files. It is then necessary to add `**CFG1=', `**CFG2=', `**CFG3=', `**CFG4='. . . . . Each configuration file has its specific modifications listed directly below it. Note how the Quake 3 sample above does not have `**CFG1= and **CFG2=' written in it. Sample Entry: (multiple configuration files) *[Clive Barker's Undying]* **SubFolderName= **CfgIniFileName=MULTIPLE **GameExeName=Undying. exe **ShortCutName=Undying Optimized **ShortCutParameters= **LatestPatchReq=http://www. matrox. com/mga/3d_gaming/enhanced_games/cbundying. cfm **MSG1= **NoSurround=False **Surround=True **CFG1=user. ini DesiredFOV=||132 DefaultFOV=||132 ZoomFOV=||30 **CFG2=system. ini FullscreenViewportX=||1920 FullscreenViewportY=||480 *[END]* 3) Where actual games (i. e. : "Saved Games") need to be updated, of which there could be many saved games bearing the same file extension. Cases like this need to have the `*. [FileExtension]' specified as the **CfgIniFileName. The app will interpret the `*. ' to mean that it will be modifying several saved game files and will omit certain functions like creating a desktop shortcut to the game and omit the restore option. The original saved games will not be altered because a new game file will be created bearing a similar name. Also, unlike the configuration routine, any strings that are not found DO NOT get added to the end of the configuration file. With games it might be necessary to prefix the header name to the search string ( Ex: [Window. 1] ). [. . . ] It is assumed that there are no duplicate names in the file, and will be handled in a similar manner as the configuration file function routines specified above. Saved games usually contain a unique title for identification purposes. It is necessary to modify this title, so that it too, can have a unique name when displayed with the games restore/load feature. A "+" symbol placed at the end of a line indicates that this is a game title search string, since a title within the saved game file, can be called anything (EX: Caption=, GameName=, . . . . ). [. . . ]