![]() ![]() Section 13: The configuration (options) fileįULLSCREEN: How do I change to fullscreen? The commands present there are run when DOSBox starts, so you can use this section for the mounting. In the DOSBox configuration file is an section. If everything went fine, DOSBox will display the prompt "C:\>".ĪUTOMATION: Do I always have to type these commands? To change to the drive mounted like above, type "C:". In Linux, "mount c /home/username" will give you a C drive in DOSBox which points to /home/username in Linux. For example, in Windows "mount C D:\GAMES" will give you a C drive in DOSBox which points to your Windows D:\GAMES directory (that was created before). You have to make your directories available as drives in DOSBox by using the "mount"Ĭommand. My Build game(Duke3D/Blood/Shadow Warrior) has problems.Īt the beginning you've got a Z:\> instead of a C:\> at the prompt. The game/application does not run at all/crashes! The game/application runs much too slow/too fast! The character/cursor/mouse pointer always moves into one direction! Right Shift and "\" doesn't work in DOSBox. The sound stutters or sounds stretched/weird. What sound hardware does DOSBox presently emulate? The game/application can't find its CD-ROM. If you have your game on a cdrom you may try this guide:ĭo I always have to type these "mount" commands? "How to start?" as well as the description of the MOUNT command (section 4: "Internal Programs"). It is essential that you get familiar with the idea of mounting, DOSBox does not automatically make any drive (or a part of it) accessible to the emulation. DOSBox can be configured to run a wide range of DOS games, from CGA/Tandy/PCjr While we are hoping that one day DOSBox will run all programs ever made for the PC, we are not there yet.Īt present, DOSBox running on a high-end machine will roughly be ![]() Back in the days, I remember finding and tweaking the "loiter a while" 3 hours time limit in less than 30 minutes.(always use the latest version from DOSBox v0.74-3 Manual = 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. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |