Spice86 - Revision history

HerrNove at 14:42, 1 March 2025

2025-03-01T14:42:57Z

← Older revision		Revision as of 16:42, 1 March 2025
Line 2:		Line 2:
	Additionally, one must give the parameter <code>--InstructionsPerSecond 5000000</code>.		Additionally, one must give the parameter <code>--InstructionsPerSecond 5000000</code>.

	<small>The reason for this workaround is that Stunts activates interrupts in the middle of the int 8 handler (see [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3727 here]), so another int 8 can could be triggered in between. This interrupt corresponds to the programmable interrupt timer, which Stunts [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3514 sets at 100 Hz]. So if the int 8 handler needs more than 1/100 seconds to run, disaster ensues. This probably never happens on real CPUs, but might occur if the emulator's simulated CPU is too slow with respect to the simulated PIT.		<small>The reason for this workaround is that Stunts activates interrupts in the middle of the int 8 handler (see [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3727 here]), so another int 8 can could be triggered in between. This interrupt corresponds to the programmable interrupt timer 8253-5 (AT: 8254.2), which Stunts [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3514 sets at 100 Hz]. So if the int 8 handler needs more than 1/100 seconds to run, disaster ensues. This probably never happens on real CPUs, but might occur if the emulator's simulated CPU is too slow with respect to the simulated PIT.

	Here a dump the relevant snippets, which should eventually go elsewhere		Here a dump the relevant snippets, which should eventually go elsewhere

	<pre>		<pre>
	seg012.asm-3514- mov dx, 2E9Ch ; Frequency for the PIT. 1193182 / 0x2e9c ~= 99.998 Hz		seg012.asm-3514- mov dx, 2E9Ch ; Frequency for channel 0 of the PIT. 1193182 / 0x2e9c ~= 99.998 Hz
	[...]		[...]
	seg012.asm-3555- mov al, 0B6h ; Set up channel 2 (PC Speaker). Unrelated, included for reference.		seg012.asm-3555- mov al, 0B6h ; Set up PIT's channel 2 (PC Speaker). Unrelated, included for reference.
	seg012.asm:3556: out 43h, al ; Set channel 2 to opmode = 3 (square wave)		seg012.asm:3556: out 43h, al ; Set channel 2 to opmode = 3 (square wave)
	[...]		[...]
	seg012.asm-3582- mov al, dl		seg012.asm-3582- mov al, dl
	seg012.asm:3583: out 40h, al ; ~~Timer 8253-5~~ (~~AT: 8254.2~~).		seg012.asm:3583: out 40h, al ; Set PIT's channel 0 frequency, low byte (9C)
	seg012.asm-3584- mov al, dh		seg012.asm-3584- mov al, dh
	seg012.asm:3585: out 40h, al ; ~~Timer 8253-5~~ (~~AT: 8254.2~~).		seg012.asm:3585: out 40h, al ; Set PIT's channel 0 frequency, high byte (2E)
	--		--
	~~seg012.asm-3621- out 21h, al ; Interrupt controller, 8259A.~~
	~~seg012.asm-3622- sti~~
	seg012.asm-3623- mov al, 0 ; Reset frequency to 1193182 / 65536 ~= 18.2 Hz		seg012.asm-3623- mov al, 0 ; Reset frequency to 1193182 / 65536 ~= 18.2 Hz
	seg012.asm:3624: out 40h, al ; ~~Timer 8253-5~~ (~~AT: 8254.2~~).		seg012.asm:3624: out 40h, al ; send low byte (0)
	seg012.asm:3625: out 40h, al ; ~~Timer 8253-5~~ (~~AT: 8254.2~~).		seg012.asm:3625: out 40h, al ; send high byte (0)
	</pre>		</pre>

HerrNove at 14:40, 1 March 2025

2025-03-01T14:40:37Z

← Older revision		Revision as of 16:40, 1 March 2025
Line 9:		Line 9:
	seg012.asm-3514- mov dx, 2E9Ch ; Frequency for the PIT. 1193182 / 0x2e9c ~= 99.998 Hz		seg012.asm-3514- mov dx, 2E9Ch ; Frequency for the PIT. 1193182 / 0x2e9c ~= 99.998 Hz
	[...]		[...]
	seg012.asm-3555- mov al, 0B6h		seg012.asm-3555- mov al, 0B6h ; Set up channel 2 (PC Speaker). Unrelated, included for reference.
	seg012.asm:3556: out 43h, al ; ~~Sets~~ channel 2 ~~(PC Speaker)~~ to opmode = 3 (square wave)		seg012.asm:3556: out 43h, al ; Set channel 2 to opmode = 3 (square wave)
	[...]		[...]
	~~seg012.asm-3580- out 21h, al ; Interrupt controller, 8259A.~~
	~~seg012.asm-3581- sti~~
	seg012.asm-3582- mov al, dl		seg012.asm-3582- mov al, dl
	seg012.asm:3583: out 40h, al ; Timer 8253-5 (AT: 8254.2).		seg012.asm:3583: out 40h, al ; Timer 8253-5 (AT: 8254.2).
Line 21:		Line 19:
	seg012.asm-3621- out 21h, al ; Interrupt controller, 8259A.		seg012.asm-3621- out 21h, al ; Interrupt controller, 8259A.
	seg012.asm-3622- sti		seg012.asm-3622- sti
	seg012.asm-3623- mov al, 0 ; Reset frequency to ~18 Hz		seg012.asm-3623- mov al, 0 ; Reset frequency to 1193182 / 65536 ~= 18.2 Hz
	seg012.asm:3624: out 40h, al ; Timer 8253-5 (AT: 8254.2).		seg012.asm:3624: out 40h, al ; Timer 8253-5 (AT: 8254.2).
	seg012.asm:3625: out 40h, al ; Timer 8253-5 (AT: 8254.2).		seg012.asm:3625: out 40h, al ; Timer 8253-5 (AT: 8254.2).

HerrNove at 14:38, 1 March 2025

2025-03-01T14:38:41Z

← Older revision		Revision as of 16:38, 1 March 2025
Line 21:		Line 21:
	seg012.asm-3621- out 21h, al ; Interrupt controller, 8259A.		seg012.asm-3621- out 21h, al ; Interrupt controller, 8259A.
	seg012.asm-3622- sti		seg012.asm-3622- sti
	seg012.asm-3623- mov al, 0		seg012.asm-3623- mov al, 0 ; Reset frequency to ~18 Hz
	seg012.asm:3624: out 40h, al ; Timer 8253-5 (AT: 8254.2).		seg012.asm:3624: out 40h, al ; Timer 8253-5 (AT: 8254.2).
	seg012.asm:3625: out 40h, al ; Timer 8253-5 (AT: 8254.2).		seg012.asm:3625: out 40h, al ; Timer 8253-5 (AT: 8254.2).

HerrNove at 14:33, 1 March 2025

2025-03-01T14:33:50Z

@@ Line 1: / Line 1: @@
-'''[https://github.com/OpenRakis/Spice86 Spice86]''' is an experimental emulator, whose support for Stunts is being worked on as of 2025. At present (2025-03-01) it can start the game, but no sound is played (start with <code>-a ns</code> to avoid wasting cycles on that)
+'''[https://github.com/OpenRakis/Spice86 Spice86]''' is an experimental emulator, whose support for Stunts is being worked on as of 2025. At present (2025-03-01) it can start the game, but no sound is played (start with <code>-a /ns</code> to avoid wasting cycles on that)
 Additionally, one must give the parameter <code>--InstructionsPerSecond 5000000</code>.
-<small>The reason for this workaround is that Stunts activates interrupts in the middle of the int 8 handler (see [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3727 here]), so another int 8 can could be triggered in between. This interrupt corresponds to the programmable interrupt timer, which Stunts [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3514 sets at 100 Hz]. So if the int 8 handler needs more than 1/100 seconds to run, disaster ensues. This  probably never happens on real CPUs, but might occur if the emulator's simulated CPU is too slow with respect to the simulated PIT.</small>
+<small>The reason for this workaround is that Stunts activates interrupts in the middle of the int 8 handler (see [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3727 here]), so another int 8 can could be triggered in between. This interrupt corresponds to the programmable interrupt timer, which Stunts [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3514 sets at 100 Hz]. So if the int 8 handler needs more than 1/100 seconds to run, disaster ensues. This  probably never happens on real CPUs, but might occur if the emulator's simulated CPU is too slow with respect to the simulated PIT.
 [[Category:Game]] [[Category:Internals]]

HerrNove at 01:58, 1 March 2025

2025-03-01T01:58:51Z

← Older revision		Revision as of 03:58, 1 March 2025
Line 1:		Line 1:
	~~Stunts works well under many emulators.~~		'''[https://github.com/OpenRakis/Spice86 Spice86]''' is an experimental emulator, whose support for Stunts is being worked on as of 2025. At present (2025-03-01) it can start the game, but no sound is played (start with <code>-a ns</code> to avoid wasting cycles on that)

	'''Spice86''' is an experimental emulator, whose support for Stunts is being worked on as of 2025. At present (2025-03-01) it can start the game, but no sound is played (start with <code>-a ns</code> to avoid wasting cycles on that)
	Additionally, one must give the parameter <code>--InstructionsPerSecond 5000000</code>.		Additionally, one must give the parameter <code>--InstructionsPerSecond 5000000</code>.

HerrNove at 01:26, 1 March 2025

2025-03-01T01:26:44Z

← Older revision		Revision as of 03:26, 1 March 2025
Line 1:		Line 1:
	Stunts works well under many emulators.		Stunts works well under many emulators.

	~~===DOSBox===~~

	* '''Vanilla DOSBox''' supports the game without particular problems.
	* '''DOSBox Staging''' No problems are to be expected, since this emulator is used by one of [[Restunts]]' main contributors.
	* '''Dosbox-X''' also works but tends to allocate less conventional memory, which has led to issues when using demanding car models. The problem can be prevented by disabling <code>xms</code> and set <code>minimum mcb free</code> to 1.


	~~===Spice86===~~

	'''Spice86''' is an experimental emulator, whose support for Stunts is being worked on as of 2025. At present (2025-03-01) it can start the game, but no sound is played (start with <code>-a ns</code> to avoid wasting cycles on that)		'''Spice86''' is an experimental emulator, whose support for Stunts is being worked on as of 2025. At present (2025-03-01) it can start the game, but no sound is played (start with <code>-a ns</code> to avoid wasting cycles on that)

HerrNove: HerrNove moved page Emulators to Spice86: Dosbox infos moved to corresponding page

2025-03-01T01:26:32Z

HerrNove moved page Emulators to Spice86: Dosbox infos moved to corresponding page

← Older revision	Revision as of 03:26, 1 March 2025
(No difference)

HerrNove at 01:18, 1 March 2025

2025-03-01T01:18:02Z

← Older revision		Revision as of 03:18, 1 March 2025
Line 14:		Line 14:

	<small>The reason for this workaround is that Stunts activates interrupts in the middle of the int 8 handler (see [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3727 here]), so another int 8 can could be triggered in between. This interrupt corresponds to the programmable interrupt timer, which Stunts [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3514 sets at 100 Hz]. So if the int 8 handler needs more than 1/100 seconds to run, disaster ensues. This probably never happens on real CPUs, but might occur if the emulator's simulated CPU is too slow with respect to the simulated PIT.</small>		<small>The reason for this workaround is that Stunts activates interrupts in the middle of the int 8 handler (see [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3727 here]), so another int 8 can could be triggered in between. This interrupt corresponds to the programmable interrupt timer, which Stunts [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3514 sets at 100 Hz]. So if the int 8 handler needs more than 1/100 seconds to run, disaster ensues. This probably never happens on real CPUs, but might occur if the emulator's simulated CPU is too slow with respect to the simulated PIT.</small>

			[[Category:Game]] [[Category:Internals]]

HerrNove at 01:09, 1 March 2025

2025-03-01T01:09:24Z

← Older revision		Revision as of 03:09, 1 March 2025
Line 3:		Line 3:
	===DOSBox===		===DOSBox===

	* '''Vanilla DOSBox''' supports it without particular problems		* '''Vanilla DOSBox''' supports the game without particular problems.
	* '''DOSBox Staging''' ~~no reports~~, ~~but~~ this emulator is used by ~~at least~~ one ~~modder, so no problems are to be expected~~		* '''DOSBox Staging''' No problems are to be expected, since this emulator is used by one of [[Restunts]]' main contributors.
	* '''Dosbox-X''' also works but tends to allocate less conventional memory, which has led to ~~some problem~~ when using demanding car models. The problem can be ~~avoided~~ by disabling <code>xms</code> and set <code>minimum mcb free</code> to 1.		* '''Dosbox-X''' also works but tends to allocate less conventional memory, which has led to issues when using demanding car models. The problem can be prevented by disabling <code>xms</code> and set <code>minimum mcb free</code> to 1.


Line 11:		Line 11:

	'''Spice86''' is an experimental emulator, whose support for Stunts is being worked on as of 2025. At present (2025-03-01) it can start the game, but no sound is played (start with <code>-a ns</code> to avoid wasting cycles on that)		'''Spice86''' is an experimental emulator, whose support for Stunts is being worked on as of 2025. At present (2025-03-01) it can start the game, but no sound is played (start with <code>-a ns</code> to avoid wasting cycles on that)
	Additionally, one must give the parameter --InstructionsPerSecond 5000000. The reason for this workaround is that Stunts activates interrupts in the middle of the int 8 handler (see [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3727 here]), so another int 8 can could be triggered in between. This interrupt corresponds to the programmable interrupt timer, which Stunts [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3514 sets at 100 Hz].		Additionally, one must give the parameter <code>--InstructionsPerSecond 5000000</code>.

			<small>The reason for this workaround is that Stunts activates interrupts in the middle of the int 8 handler (see [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3727 here]), so another int 8 can could be triggered in between. This interrupt corresponds to the programmable interrupt timer, which Stunts [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3514 sets at 100 Hz]. So if the int 8 handler needs more than 1/100 seconds to run, disaster ensues. This probably never happens on real CPUs, but might occur if the emulator's simulated CPU is too slow with respect to the simulated PIT.</small>

HerrNove: Created page with "Stunts works well under many emulators. ===DOSBox=== * '''Vanilla DOSBox''' supports it without particular problems * '''DOSBox Staging''' no reports, but this emulator is u..."

2025-03-01T01:04:30Z

Created page with "Stunts works well under many emulators. ===DOSBox=== * '''Vanilla DOSBox''' supports it without particular problems * '''DOSBox Staging''' no reports, but this emulator is u..."

New page

Stunts works well under many emulators.

===DOSBox===

* '''Vanilla DOSBox''' supports it without particular problems
* '''DOSBox Staging''' no reports, but this emulator is used by at least one modder, so no problems are to be expected
* '''Dosbox-X''' also works but tends to allocate less conventional memory, which has led to some problem when using demanding car models. The problem can be avoided by disabling <code>xms</code> and set <code>minimum mcb free</code> to 1.

===Spice86===

'''Spice86''' is an experimental emulator, whose support for Stunts is being worked on as of 2025. At present (2025-03-01) it can start the game, but no sound is played (start with <code>-a ns</code> to avoid wasting cycles on that)
Additionally, one must give the parameter --InstructionsPerSecond 5000000. The reason for this workaround is that Stunts activates interrupts in the middle of the int 8 handler (see [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3727 here]), so another int 8 can could be triggered in between. This interrupt corresponds to the programmable interrupt timer, which Stunts [https://github.com/4d-stunts/restunts/blob/89400488cf40086447a13afb19722225ee0ad094/src/restunts/asmorig/seg012.asm#L3514 sets at 100 Hz].