Other builds contain only a custom dosbox executable binary (e.g. Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Also, see replies to this post from the maintainers for additional info on their builds. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Consult the list below to see which features the different builds contain and decide which one you want to try first. You may also want access to the new features or optimizations if you are having compatibility or performance issues. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. At the time of this writing, the last official release (0.74) is several years old, and is therefore missing a significant amount of work performed by the developers. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.Įvery so often a new official version of DOSBox is released. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on in something called an SVN repository. 3.6 Snapshot of latest DOSBox SVN source code.1.6 Where can I go to talk about SVN builds? (forum thread).1.5 What do I do if I find bugs in an SVN build?. Back in the days, I remember finding and tweaking the "loiter a while" 3 hours time limit in less than 30 minutes. I used it like 20 years ago and never found any other debugger as powerful as this one was. To be honest, I really missed good old SoftICE. So, did some of you manage to use it successfully? I'm pretty sure I'm not doing things right but even after looking for information on the internet, I can't understand why DOSBox debugger is behaving like it does with DF. And then, if it does, I can only hope current CPU registers will give me enough information. It's quite frustrating and the only solution I came into is to set breakpoints on a dozen function instructions, hoping DOSBox will eventually break into one of them. But then, either DOSBox never breaks (even if it goes through the code) or if it does, I'm unable to step over/through the following instructions using F10/F11. I'm able to locate the exact instruction where I want DOSBox to stop and put a breakpoint there. Even if I managed to understand some very useful functions and translate them from decompiled C code to DFU C# engine (see my recent PR related to NPC greetings), the main problem I have is I can't manage to use DOSBox debugger properly. However, my current method of doing it is essentially static. During the last months, I've gathered some experience at reverse engineering classic mechanics.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |