Local Files: Difference between revisions
(Created page with "To accommodate limited hard disk space of the era, Lego Island by default installs only a few files locally and streams the rest off the CD. The locally installed files are as...") |
No edit summary |
||
| Line 2: | Line 2: | ||
===ISLE.EXE=== | ===ISLE.EXE=== | ||
The main executable. Creates the window handle and does some basic initiation and runtime work. Also contains the configuration window that can be accessed through CONFIG.EXE. | The main executable. Creates the window handle and does some basic initiation and runtime work, but otherwise largely passes off to LEGO1.DLL for the bulk of the game code. Also contains the configuration window that can be accessed through CONFIG.EXE. | ||
===LEGO1.DLL=== | ===LEGO1.DLL=== | ||
Revision as of 01:35, 24 April 2019
To accommodate limited hard disk space of the era, Lego Island by default installs only a few files locally and streams the rest off the CD. The locally installed files are as follows:
ISLE.EXE
The main executable. Creates the window handle and does some basic initiation and runtime work, but otherwise largely passes off to LEGO1.DLL for the bulk of the game code. Also contains the configuration window that can be accessed through CONFIG.EXE.
LEGO1.DLL
The bulk of the game code and most of the functionality. ISLE.EXE can be largely considered an entry point into this library.
CONFIG.EXE and LEGOISLE.EXE
Glorified shortcuts - these two executables are identical in code. When run, they check their filenames to determine what way to open ISLE.EXE. CONFIG.EXE will run the Lego Island Configuration stored in ISLE.EXE and LEGOISLE.EXE will open it normally. There is no known difference between running LEGOISLE.EXE and running ISLE.EXE directly, however renaming LEGOISLE.EXE to CONFIG.EXE will make it run the configuration instead of the regular game (and vice-versa).