VOGONS

Common searches


Search results

Display options

Re: DOSBox debugger

There's a guide for the debugger in the guides section, but it's rather ancient, so might not be 100% accurate now. The guide is not in-depth; some familiarity with concepts found in other debugging environments is assumed. You can refer to the debugger source code for specifics that aren't obvious, …

Re: DOSBox-X branch

The MSCDEX emulation would ideally not be involved with Win9x. Mapping ATAPI commands through MSCDEX seems wonky, although it might be expedient to do that initially. Ideally there would be ATAPI frontend code that accomplishes the same thing for Win9x (and real DOS + real MSCDEX + real cdrom device …

Re: I hate the keymapper...

I am actually debating writing a normal keymapper for my front-end that will allow a user to select a key, then assign key-presses to it, then write that data into the mapper file. Much easier than the one built-in. That sounds like what DOSBox already does: select an *emulated* key (event) and …

Re: I hate the keymapper...

I am skeptical about your assertion that there are "tons" of DOS games that use Ctrl-F1; my experience is that very few of them do. Applications are another matter, but DOSBox is not intended for them. In any case, it seems your approach is incorrect, you simply need to delete or reassign the …

Re: DOSBox debugger

Debugger builds provided by Qbix are probably "heavy"; few bother with the middle ground. However, if you want to know for sure in any debugger build, there will be memory-change breakpoint commands (BPM/BPPM/BPLM) and CPU logging commands listed when you use the HELP command in the debugger.

Re: DOSBox .74 Keyboard getting stuck issue

Installing any kind of software can silently install unexpected support stuff that has implications for other software. Do you get automatic updates? What might have updated without you realizing that it happened? Also, beyond the task tray, are any unfamiliar services running that you can try …

Re: Adding arbitrary ROM images to the memory map

Make sure you've mounted an A: or C: drive and that it is the current drive before trying to start 123, because it will be confused if Z: is the current drive. Other than that, it should work if your cart dumps are not bad. As I mentioned before, it won't run stable when executed from the BOOT …

Re: Adding arbitrary ROM images to the memory map

Lotus 1-2-3 for the PCjr. also doesn't work because DOSBox doesn't support the two cartridge design for that program. DOSBox does support two cartridges, and you can run Lotus 1-2-3 with the command: boot 123A.JRC 123B.JRC -e 123 However, as with ColorPaint, it's likely to be unstable because the …

Re: Moraff's World High Resolution

in DOS
When I start the game, I choose the mode indicated (A-1). The loading text appears in yellow, and then goes grey. Nothing more happens until I press Escape, when I'm dumped back to the prompt. That is what happens when the machine type is still the default svga_s3, so you apparently haven't changed …

Re: Buffer overflow

Yes, and in the 8-loop there is a typo where the first stick is initialized twice, leaving the second stick uninitialized. The issues were reported on SourceForge: http://sourceforge.net/p/dosbox/patches/257/ Because the struct is initialized with false and zero values, memset() should work nicely …

Re: Monkey Island 1 CD door closing sound

The door opening sound is 4500 samples long, but the closing sound is a mere 88 samples long. Can't cram much detail in such a short clip, and the wave cuts off abruptly rather than trailing off. So, the closing effect is understandably a bit pop-ish, and a better quality source clip would …

Re: .mod files that push the limits

I like the laid-back style of Sound o'da lunatic. Dunno if it's pushing any limits of the format, but it's easy to forget that you're listening to a 4-channel MOD, which I think is an accomplishment in itself.

Page 78 of 186