1. Changes The version of mild in this package, version 1.02b, differs from the previous version, version 1.02, in that the following options have been added and the problems described below have been fixed. Options added: -B 0 Option included when creating a startup game using the restart feature. -B 1 Option included when creating a started game using the restart feature. Problems fixed: In version 1.02a and earlier versions of mild, specifying a segment without code or a nonexistent segment for the XXXX value of lba after XXXX resulted in a stack error. The program was modified so that an error message is displayed and the program is exited. This fix was introduced with version 1.02b of mild. This change does not affect games that do not use the N64 Disk Drive. 2. What is restarting? Restarting refers to starting a game stored on disk from a game on Game Pak, for example. This became possible with the release of patchNg981021. A game that starts another game is called the "startup game," while the game that is started is called the "started game." As was mentioned in section 1. above, mild must be executed using the -B 0 option when creating a startup game and using the -B 1 option when creating a started game. 3. Items to Note Because a started game must always be stored on disk, the -B 1 option should always be used with the -DD64 option. 4. Installation The version of mild included in this patch is currently (02/01/1999) the newest version. When using version 1.20 or older versions of exeGCC, replace the older version of mild with the version in this patch. Using a file manager such as Explorer, copy mild.out and exew32.exe to the exeGCC installation directory, where the executable files are stored. The default directory is c:\ultra\gcc\mipse\bin. When versions of exeGCC newer than version 1.20 are released by Kyoto Microcomputer in the future, they will include new versions of mild, and this patch will be unnecessary.