Local Files - Revision history

MattKC: Reverted edit by PawPatroler (2025) (talk) to last revision by MattKC

2026-03-06T05:49:18Z

Reverted edit by PawPatroler (2025) (talk) to last revision by MattKC

← Older revision		Revision as of 05:49, 6 March 2026
(No difference)

PawPatroler (2025): PawPatroler (2025) changed the content model of the page Local Files from "wikitext" to "JavaScript"

2026-03-05T19:11:17Z

PawPatroler (2025) changed the content model of the page Local Files from "wikitext" to "JavaScript"

← Older revision		Revision as of 19:11, 5 March 2026
(No difference)

MattKC: Undo revision 1084 by Fuckyou (talk)

2026-01-03T06:06:10Z

Undo revision 1084 by Fuckyou (talk)

← Older revision	Revision as of 06:06, 3 January 2026
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:

		==ISLE.EXE==

		{{Main article\|ISLE.EXE}}

		The main executable. Creates the window handle, handles window events, and 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. Due to its importance, much of the modding and research work is centralized on 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.

		==NOCD.SI==
		{{Main article\|NOCD.SI}}

		The only [[Interleaf File]] installed to the hard drive rather than streamed from the CD-ROM. Contains a video instructing the player to insert the CD if the game cannot find the rest of its assets.

Fuckyou: Blanked the page

2026-01-01T12:44:30Z

Blanked the page

← Older revision		Revision as of 12:44, 1 January 2026
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:~~

	~~==ISLE.EXE==~~

	~~{{Main article\|ISLE.EXE}}~~

	The main executable. Creates the window handle, handles window events, and 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. Due to its importance, much of the modding and research work is centralized on 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.

	~~==NOCD.SI==~~
	~~{{Main article\|NOCD.SI}}~~

	~~The only [[Interleaf File]] installed to the hard drive rather than streamed from the CD-ROM. Contains a video instructing the player to insert the CD if the game cannot find the rest of its assets.~~

MattKC: /* ISLE.EXE */

2023-05-31T06:29:22Z

ISLE.EXE

← Older revision		Revision as of 06:29, 31 May 2023
Line 2:		Line 2:

	==ISLE.EXE==		==ISLE.EXE==

	{{Main article\|ISLE.EXE}}		{{Main article\|ISLE.EXE}}

	The main executable. Creates the window handle, handles window events, and 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.		The main executable. Creates the window handle, handles window events, and 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.

MattKC: /* ISLE.EXE */

2023-05-31T06:29:16Z

ISLE.EXE

← Older revision		Revision as of 06:29, 31 May 2023
Line 2:		Line 2:

	==ISLE.EXE==		==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.		{{Main article\|ISLE.EXE}}
			The main executable. Creates the window handle, handles window events, and 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==

MattKC: /* LEGO1.DLL */

2020-06-05T17:44:41Z

LEGO1.DLL

← Older revision		Revision as of 17:44, 5 June 2020
Line 5:		Line 5:

	==LEGO1.DLL==		==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.		The bulk of the game code and vast majority of the functionality. ISLE.EXE can be largely considered an entry point into this library. Due to its importance, much of the modding and research work is centralized on this library.

	==CONFIG.EXE and LEGOISLE.EXE==		==CONFIG.EXE and LEGOISLE.EXE==

MattKC at 14:05, 21 December 2019

2019-12-21T14:05:06Z

← Older revision		Revision as of 14:05, 21 December 2019
Line 13:		Line 13:

	==NOCD.SI==		==NOCD.SI==
	~~<span style="padding-left: 2em">''~~Main article~~: [[~~NOCD.SI~~]]''</span>~~		{{Main article\|NOCD.SI}}

	The only [[Interleaf File]] installed to the hard drive rather than streamed from the CD-ROM. Contains a video instructing the player to insert the CD if the game cannot find the rest of its assets.		The only [[Interleaf File]] installed to the hard drive rather than streamed from the CD-ROM. Contains a video instructing the player to insert the CD if the game cannot find the rest of its assets.

MattKC at 11:46, 23 October 2019

2019-10-23T11:46:12Z

← Older revision		Revision as of 11:46, 23 October 2019
Line 11:		Line 11:

	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.		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.

			==NOCD.SI==
			<span style="padding-left: 2em">''Main article: [[NOCD.SI]]''</span>

			The only [[Interleaf File]] installed to the hard drive rather than streamed from the CD-ROM. Contains a video instructing the player to insert the CD if the game cannot find the rest of its assets.

MattKC at 11:40, 23 October 2019

2019-10-23T11:40:51Z

← Older revision		Revision as of 11:40, 23 October 2019
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.