Local Files: Difference between revisions

From LEGO Island Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
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:
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===
==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.
The main executable. Creates the window handle, initializes most of the DirectX libraries, and also runs the main game loop. A fairly simple application, it largely passes off to the functions in LEGO1.DLL for the bulk of the game code.


===LEGO1.DLL===
==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.
The bulk of the game code and vast majority of the functionality. ISLE.EXE can be largely considered an entry point into this library.


===CONFIG.EXE and LEGOISLE.EXE===
==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).
Bizarrely, these two executables are completely identical despite being used for different purposes. On startup, both of them will check their filename. If it's "CONFIG", the Lego Island Configuration dialog is shown. Otherwise, it launches ISLE.EXE and exits. Their functions can be changed simply by renaming them.
 
The exact purpose of using LEGOIsle.exe instead of linking directly to ISLE.EXE is unknown, as is purpose of having the two be the same executable. All desktop and start menu shortcuts to LEGO Island actually launch LEGOIsle.exe, despite the fact that its only action is launching ISLE.EXE.

Revision as of 11:40, 23 October 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, initializes most of the DirectX libraries, and also runs the main game loop. A fairly simple application, it largely passes off to the functions in LEGO1.DLL for the bulk of the game code.

LEGO1.DLL

The bulk of the game code and vast majority of the functionality. ISLE.EXE can be largely considered an entry point into this library.

CONFIG.EXE and LEGOISLE.EXE

Bizarrely, these two executables are completely identical despite being used for different purposes. On startup, both of them will check their filename. If it's "CONFIG", the Lego Island Configuration dialog is shown. Otherwise, it launches ISLE.EXE and exits. Their functions can be changed simply by renaming them.

The exact purpose of using LEGOIsle.exe instead of linking directly to ISLE.EXE is unknown, as is purpose of having the two be the same executable. All desktop and start menu shortcuts to LEGO Island actually launch LEGOIsle.exe, despite the fact that its only action is launching ISLE.EXE.

Retrieved from "https://www.legoisland.org/index.php?title=Local_Files&oldid=169"