Messages

it seems to be related to free memory or something

i've installed stunts under

latest fake86 (http://sourceforge.net/projects/fake86)
DosBox 0.74 (dosbox.com)
VMWare Player 7 + MsDos 6.22

and i've get different start positions when just starting the game and fo directly to race

fake86/VMWare showing equal start screen, dosbox a different

why is that - is it a bug?

FYI: i've developed a small tool that integrates the adlib sound-driver into the combined/cracked exe - so no dynamic code loading

latest version is attached a the end of this thread

http://forum.stunts.hu/index.php?topic=3019.15

Did you solve the DosBox debugging issue?

yupp - ripsaw8080 patch works in realmode (but not in pmode) - but stunts is realmode so no problem

attached is my current version of the sound-integration tool

Question: Can I use Zapper's engine sounds with this .exe file and how I can change the sound options while setup.exe is gone?

you can't change the sound device due to the adlib/sdblaster driver integration - what other sound options?

Your future plans are...?

(0. get more time)

1.build a simple emulator: my idea is to reduce http://sourceforge.net/projects/fake86/ down to stunts needs and
grab most of the fake assembler functions from this real-mode and 16bit only and well tested codebase

2. try to replace parts of the emulated code with real code - hope that is easy copy&paste

remove more and more of the emulated code - until finished

I think I did. This crashes were so random that game_drv.exe seems to be not responsible.
About the graphics - the same thing happens with the original files also with game_drv.exe when nothing is deleted... Strange game

so i get it right that game_drv.exe is as buggy as the original - or?

very unexpected errors

1. The game does not remember the options in Graphic Levels - FULL,
Slow video mgmt ON, Fast simulation speed.

that could be maybe a problem with missing files - does that also happen with an full-install with just added game_drv.exe

2. The game seems to be stable but for some reason from time to time it crashes when I'm on the track (DEFAULT) and pressing Esc at the same time.

my only idea is that dosbox can be responsible for the problem - stunts crashes for example more often when using the haevydebug version of dosbox

did you saw anything like that ever with the normal stunts executable?

I can test this, it's not a big deal

does the game_drv.exe run fine?

but I can not do other useful stuff for this project.

testing is always the biggest thing to do

So this driver integration is not directly in relation with re-stunts?

partialy - i use the exe combiner from clvn to get the combined mcga stunts exe (base of the re-stunts project)
and my own program to integrate the sound-driver

32/64 bit Stunts sounds more than amazing.

currently the re-stunts project suffering of beeing kept in the
16 bit dos evironment that means debugging in DosBox or old TurboDebugger etc. it makes
the ultra hard reversing even harder so my hope is to convert the original 16 Bit
asm source code to something like 16Bit-asm-behaving like C-Functions
inside of an 32/64 Bit C/C++ Projekt
this way the reversers can mix C and fake-asm and do the analyse and stuff under
linux/windows with the prefered development environments

but it sounds much easier than it is in real

i try to release the stuff in small steps with the hope that someone give it a try and find bugs - because
due to the reverse nature of the project its very hard to find bugs the way like in normal source based projects

Hmm, that's good but where is the deal? Thanks to this we can delete safely ad15.drv and/or pc15.drv and still the game will run fine? Which .exe file is involved?

the attached game_drv.exe is the mcga,soundblaster version of stunts1.1 (kalpen version)

so the following files are not needed to run stunts using game_drv.exe
   AD15.DRV
   CGA.COD
   CGA.DIF
   CGA.HDR
   EGA.CMN
   EGA.COD
   EGA.HDR
   LOAD.EXE
   MCGA.COD
   MCGA.DIF
   MCGA.HDR
   MT15.DRV
   MT32.PLB
   [MTENG1.VCE] - not loaded anymore
   [MTSKIDMS.VCE] - not loaded anymore
   PC15.DRV
   [PCENG1.VCE] - not loaded anymore
   [PCSKIDMS.VCE] - not loaded anymore
   SETUP.DAT
   SETUP.EXE
   [SETUP.PIF]
   ST.COM
   STUNTS.COM
   stunts_k.exe
   TD15.DRV
   [TDENG1.VCE] - not loaded anymore
   [TDSKIDMS.VCE] - not loaded anymore
   TDY.COD
   TDY.DIF
   TDY.HDR

and the game_drv.exe does not load any code dynamicaly - that
means its easier to reverse

And what about the in progress re-compiled .exe file?

its an side/alternative project of re-stunts - my hope is to statical recompile stunts
to 32/64bit sometime - to reduce dynamic code loading is one of the steps to ease the process

i talk about the exe result of clvns execombiner - so no code modification

i don't know if it is a known problem also with unmodified stunts - but i get sometimes (svn version) dosbox debuger illegal instruction breakdowns
or my vmware player (v6) totaly crashed with illegal instructions message

it mostly happens when you start a race and directly crash into a wall - anyone else got this problem (very rare)?

i've developed a tool that combines the stunts game.exe with the ad15.drv (adlib/soundblaster) driver (but pc15.drv is also possible)
parts of the game getting patched for disableing the driver (un)loading

why (still same reasons):
-for fun
-reduce the amount of runtime loaded code down to 0% (hope that is reached now) - IDA likes it more then

seems to work perfectly - someone want to try?

just copy the attached game_drv.exe into your stunts1.1 directory and start without commandline parameters

it seems to be a dosbox bp-cmd regression that i can't use different segment/offset values pointing to the same 32-bit location

http://www.vogons.org/viewtopic.php?f=32&t=37854#p336691

i've got dosbox (not heavy) debugger running, dynamic_core is disabled, try to debug game.exe from execombiner

if i just do

debug game /ssb and press then F5 in dosbox debugger the game starts with sound

if i set a breakpoint at 0x299a:0x000a - LoadAudioDriver and press F5 i get the error message "can't load driver"

what does setting the breakpoint change?