VOGONS

Search

Common searches

Search results

Display options

Display options

Re: Open with: DOSBox

Posted on 2020-02-19, 13:31

mounting support for zip files is what I had in mind. An experimental patch was made for it: https://www.vogons.org/viewtopic.php?t=9591 I think some version of it is in the Daum build, but both Daum and the patch are more than a little out of date now. Also, I don't know how well it might co-exist …

Re: DIGPLAY sample player inverse stereo

Posted on 2020-02-16, 16:07

the SB16 driver i hacked looks like this: MOV [0479],80 MOV [0487],00 MOV [0495],00 MOV [04A3],00 Eh, those instructions don't exist in either of the driver files in your attachment. However, the MOV instructions that put 4 0x80 bytes into sequential memory as samples DO exist in both driver files, …

Re: DIGPLAY sample player inverse stereo

Posted on 2020-02-16, 15:35

(caugh) your patch didn't warns if the driver has different addressing? It looks for a specific code sequence, and it changes nothing and displays "File unrecognized" if the sequence is not found. The addresses we're discussing here have no bearing on how the program works because, as I mentioned …

Re: DIGPLAY sample player inverse stereo

Posted on 2020-02-16, 14:10

Gernot66 wrote on 2020-02-16, 13:59: […] Show full quote Copy code to clipboard 1 MOV [0479],80 2 MOV [0487],00 3 MOV [0495],00 4 MOV [04A3],00 That looks even worse than original for 16-byte samples, because it's 0x0080 not 0x8000. Remember that PCs are little-endian for most things. 😀 Edit: oh, …

Re: DIGPLAY sample player inverse stereo

Posted on 2020-02-16, 13:09

Do you got an idea why the SB16 driver (or the player when on a sb16 board) opens with an audible click only on the left channel while the SBPRO won't do that? And maybe one how to fix that? My fix program didn't bother with the click/pop because it only happens when the SB16.DIG driver is …

Re: Rules of Engagement 2 IGS

Posted on 2019-12-10, 06:08

Woah. I've cleaned up the thread a bit. Please don't attach a bunch of Clipper stuff just because it *might* have some reference to the linker in question. That's not really helpful. What I'm interested in knowing about *specifically* is RTLink/Plus published by Pocket Soft, and the "smart vectoring …

Re: Rules of Engagement 2 IGS

Posted on 2019-12-10, 03:03

Might be useful to find the documentation for RTLink, as it could reveal clues. My recollection is that overlay linkers (PLink86, ALink, BLinker, etc.) where more commonly used for real-mode DOS application development, such as with Clipper, than for games; although the software here could be …

Re: Rules of Engagement 2 IGS

Posted on 2019-12-09, 16:56

Device drivers, such as HIMEM and HIMEMX, only work properly in DOSBox if you boot real DOS with a disk image (i.e. the BOOT command). As part of my prior investigation I tried ROE2 1.08 with MS-DOS 5.0 and 6.22, which did not make the program any more stable when sound is enabled. HIMEMX is part of …

Re: Rules of Engagement 2 IGS

Posted on 2019-12-08, 10:09

ROE2 1.08 is unstable with sound enabled; more memory will not help, and there is no known workaround. However, 1.07 works fine with sound enabled. I spent some time investigating it awhile ago, and both 1.07 and 1.08 use the RTLink/Plus linker, but only 1.08 has any reference to "smart vectoring" …

Re: DOSBox-X branch

Posted on 2019-12-04, 21:30

I believe the register/flag name parsing was originally intended to be for SR only, not for SM. Does it work to write register values into memory (e.g. SM 0000:0200 AX)? If so, it may have been intended as a feature, but the collision between flag names and hex values could have been overlooked.

Page 1 of 171

Go to top of page Go to top of page
Close window
Close window