Force 2003 - Revision history

Xeon3D at 12:03, 10 August 2025

2025-08-10T12:03:04Z

@@ Line 22: / Line 22: @@
 |EB
 |}
 ==== Booting Force 2003.5 on non Megatouch Hardware: ====
@@ Line 54: / Line 61: @@
 |}
 This is what it should look like if you open it in Ghidra and choose the ForceChk1__fv Function:[[File:Force 2003 HDD and Touch Patch.png|thumb|640x640px|left]]

Xeon3D at 12:02, 10 August 2025

2025-08-10T12:02:04Z

← Older revision		Revision as of 12:02, 10 August 2025
Line 54:		Line 54:
	\|}		\|}
	This is what it should look like if you open it in Ghidra and choose the ForceChk1__fv Function:[[File:Force 2003 HDD and Touch Patch.png\|thumb\|640x640px\|left]]		This is what it should look like if you open it in Ghidra and choose the ForceChk1__fv Function:[[File:Force 2003 HDD and Touch Patch.png\|thumb\|640x640px\|left]]

Xeon3D at 12:01, 10 August 2025

2025-08-10T12:01:52Z

← Older revision		Revision as of 12:01, 10 August 2025
Line 54:		Line 54:
	\|}		\|}
	This is what it should look like if you open it in Ghidra and choose the ForceChk1__fv Function:[[File:Force 2003 HDD and Touch Patch.png\|thumb\|640x640px\|left]]		This is what it should look like if you open it in Ghidra and choose the ForceChk1__fv Function:[[File:Force 2003 HDD and Touch Patch.png\|thumb\|640x640px\|left]]

Xeon3D at 12:01, 10 August 2025

2025-08-10T12:01:42Z

@@ Line 24: / Line 24: @@
 ==== Booting Force 2003.5 on non Megatouch Hardware: ====
-Force 2003.5 checks to see if you're running an official Merit Hard Disk and a Force SMT-4 Touchcontroller (similar to SMT-3, but with a black container instead of white), and if it detects it's not, it will boot the game as MAXX.
+Force 2003.5 checks to see if you're running an official Merit Hard Disk (it has a MERIT0011 model string) and a Force SMT-4 Touchcontroller (similar to SMT-3, but with a black case instead of white), and if it detects it's not, it will boot the game as MAXX.
 To fix this, decrypt /usr/local/bin/start, open up the file in a Hex Editor, and replace the following:
@@ Line 54: / Line 54: @@
 |}
 This is what it should look like if you open it in Ghidra and choose the ForceChk1__fv Function:[[File:Force 2003 HDD and Touch Patch.png|thumb|640x640px|left]]

Xeon3D at 16:11, 27 July 2025

2025-07-27T16:11:24Z

@@ Line 6: / Line 6: @@
 === Patches: ===
-==== Booting Force 2003/2003.5 on non Megatouch Hardware: ====
+==== Patching Force 2003.5 to boot on non-Merit Motherboards ====
-Force 2003/2003.5 checks to see if you're running an official Merit Hard Disk and a Force SMT-4 Touchcontroller (similar to SMT-3, but with a black container instead of white), and if it detects it's not, it will boot the game as MAXX.
+Force 2003.5 checks to see if it's booting on an official Megatouch Force Motherboard (aka the [https://theretroweb.com/motherboards/s/pcchips-m771lmr-2-0 ECS P6IWP-Fe 2.0 / PCChips/Hsin Tech M771LMR 2.0]). If not, it'll show an "Invalid Motherboard Detected!!!" error message and stop booting.
-To fix this, decrypt /usr/local/bin/start, open up Ghidra, find the ForceChk1 function and make it so it always returns 1.
+To fix that, decrypt /usr/local/bin/start, open up the file in a Hex Editor and replace the following:
-Check the picture blow for what to patch. The left side should look exactly like that.
+==== Booting Force 2003.5 on non Megatouch Hardware: ====
-Do note, that it might have an additional Motherboard check. This patch doesn't do anything regarding that.
+To fix this, decrypt /usr/local/bin/start, open up the file in a Hex Editor, and replace the following:
-[[File:Force 2003 HDD and Touch Patch.png|center|thumb|800x800px]]
+{| class="wikitable"

Xeon3D: /* Booting Force 2003/2003.5 on non Megatouch Hardware: */

2025-07-27T15:33:44Z

Booting Force 2003/2003.5 on non Megatouch Hardware:

← Older revision		Revision as of 15:33, 27 July 2025
Line 11:		Line 11:

	To fix this, decrypt /usr/local/bin/start, open up Ghidra, find the ForceChk1 function and make it so it always returns 1.		To fix this, decrypt /usr/local/bin/start, open up Ghidra, find the ForceChk1 function and make it so it always returns 1.

			Check the picture blow for what to patch. The left side should look exactly like that.

	Do note, that it might have an additional Motherboard check. This patch doesn't do anything regarding that.		Do note, that it might have an additional Motherboard check. This patch doesn't do anything regarding that.
			[[File:Force 2003 HDD and Touch Patch.png\|center\|thumb\|800x800px]]

Xeon3D at 15:29, 27 July 2025

2025-07-27T15:29:49Z

← Older revision		Revision as of 15:29, 27 July 2025
Line 11:		Line 11:

	To fix this, decrypt /usr/local/bin/start, open up Ghidra, find the ForceChk1 function and make it so it always returns 1.		To fix this, decrypt /usr/local/bin/start, open up Ghidra, find the ForceChk1 function and make it so it always returns 1.

			Do note, that it might have an additional Motherboard check. This patch doesn't do anything regarding that.

Xeon3D: Created page with "=== Description === === Notes: === === Patches: === ==== Booting Force 2003/2003.5 on non Megatouch Hardware: ==== Force 2003/2003.5 checks to see if you're running an official Merit Hard Disk and a Force SMT-4 Touchcontroller (similar to SMT-3, but with a black container instead of white), and if it detects it's not, it will boot the game as MAXX. To fix this, decrypt /usr/local/bin/start, open up Ghidra, find the ForceChk1 function and make it so it always return..."

2025-07-27T15:28:56Z

Created page with "=== Description === === Notes: === === Patches: === ==== Booting Force 2003/2003.5 on non Megatouch Hardware: ==== Force 2003/2003.5 checks to see if you're running an official Merit Hard Disk and a Force SMT-4 Touchcontroller (similar to SMT-3, but with a black container instead of white), and if it detects it's not, it will boot the game as MAXX. To fix this, decrypt /usr/local/bin/start, open up Ghidra, find the ForceChk1 function and make it so it always return..."

New page

=== Description ===

=== Notes: ===

=== Patches: ===

==== Booting Force 2003/2003.5 on non Megatouch Hardware: ====
Force 2003/2003.5 checks to see if you're running an official Merit Hard Disk and a Force SMT-4 Touchcontroller (similar to SMT-3, but with a black container instead of white), and if it detects it's not, it will boot the game as MAXX.

To fix this, decrypt /usr/local/bin/start, open up Ghidra, find the ForceChk1 function and make it so it always returns 1.