Common searches

Search results

Display options

Re: DOSBox-X branch

There is an interesting list of differences between the 8086 and 386 cpu: https://pdos.csail.mit.edu/6.828/2008/readings/i386/s14_07.htm Examples: "The 80386 can generate the largest negative number as a quotient for the IDIV instruction. The 8086/8088 causes exception zero instead." "The setting of …

Re: DOSBox-X branch

I think so. Given the commit is reversed and the cpu=8086, then it seems reasonable to return to the following instruction for now. I would verify that the registers in idiv are handled correctly, too. I think any change should be attached to 8086, until more is known of the other cpu types. This …

Re: DOSBox-X branch

There is a recent commit to dosbox-x for "allowing borderline quotient values in IDIV": https://github.com/joncampbell123/dosbox-x/pull/3014 The above commit is a partial reversion to dosbox svn commit r2175, a change to the idiv instruction and related code. It may be worth testing whether any …

Re: WinHexen/WinHeretic

Can test compatibility of this port with hexen and heretic: https://github.com/drfrag666/ZDoom-CL/releases I believe that uses directdraw version 3. The PCX1 is probably a dx3-compatible video card.

Re: Armored Fist 2 ctd in dosbox

As a test of last resort for the use of the dynamic x86 core, it is possible to change a cache block setting from 32 to another value. I have not tested it, but a value of 16 may work. Here is one of the locations of the setting in core_dyn_x86.cpp: block=CreateCacheBlock(chandler,ip_point,32) If …

Re: DOSBox-X branch

I think this would better meet the implementation recommended by jmarsh and krcroft. Tested the values for unsigned 8-bit mono sound only. This saves the xor operation, but one report suggests that the xor may use less than a cpu cycle. I think that the data value should have a casting operator, but …

Re: DOSBox-X branch

If that was set to >127 instead of 128, then i = 128 would access the path for correcting the bias in the conversion. The way it is currently written, the i = 128 results in a table value of 0 which is expected.

Re: DOSBox-X branch

That is a good analysis. The table function runs at the start of emulation only, so it is not as crucial to optimize there. And as you said, the compiler may help where optimizing. I also had verified that function for accuracy in its calculation and then moved to the other part. That avoids the …

Page 1 of 20