Tried WIP20 on Windows 7 x64 with DX11-level GPU (nVidia Kepler) and default settings. The famous farbrausch - fr-08 intro (it uses DX8) shows two glitches. The cloud patterns in the sky are twisted as if showing crosses. The fractal-ish lattice floor opening in the cathedral is rendered in discrete …

Right and unless you actually test this you won't know if 8086 is closer to 80286 or 8088 for this feature. Don't know why you insist on this being a so interesting thing, but just go ahead and verify/falsify it, then post the results so they can be ignored because of missing relevance. Thank you …

Both are well known/can be found on various bug lists (didn't know they were officially documented), but they are irrelevant for this issue. item11 in http://www.logix.cz/michal/doc/i386/chp14-07.htm is the difference causing the bad behaviour, which was verified on 8088 compared to the 80286/ …

Nope, just that. Any interrupt on the 80286 will always leave the saved CS:IP value pointing at the beginning of the instruction that failed (including prefixes). On the 8086, the CS:IP value saved for a divide exception points at the next instruction. Here's another notable discrepancy, by the way: …

Qbix wrote: no, but a reference manual alone isn't enough for us to change things. Not only 4 manuals in this case, but also the observation that the game runs on 8088 and doesn't run on 286, which fits the information in manuals very well.

Then there's no evidence that the manuals (which documented that 286's divide overflow interrupt behaves not like 8086/8's as far back as in 1986) are wrong.

wd wrote: I don't know but given the FS tests on real hardware, the logics peter ferrie derived from this are much more interesting than citing official docs. So it has been confirmed that, contrary to manuals, the original unpatched game doesn't work on 8086 and works on 8088? Who tested that?

The same thing about int 0 handling is said in 4 Intel documents at the very least: two said PRMs, another 286 document and in 8086 Family User's Manual. Did peterferrie run hardware tests on 8086 and 8088 side-by-side? If no, then it's just his speculation vs. behavior meticulously documented by …

The problem is the different hardware behaviour between 8088 and 8086+ CPUs. I think it's incorrect. According to chapter 14.7 of 386 Programmer's Reference Manual and Appendix C to 286 PRM, int 0 handling is a difference between 8086/8088 and 286+. By the way, in these chapters of said Intel …

Is it possible to make Trucks work in DOSBox? I'm getting glitches like these with every DOSBox version, including official 0.73. I've also tried every machine= setting in .conf file. http://www.vogons.org/files/image1_830.png This was discussed once in 2005: http://www.vogons.org/viewtopic.php?t= …

Is there an option to turn off the new logo screen?

Thanks a lot! In 0.65 there was a useful feature that I used quite often: "1, 2, 4, 5 perform 100, 500, 1000, 5000 or 10000 CPU cycles then return to debugger mode". This is still reflected in the guide to the debugger but it seems that it disappeared in 0.70/0.72 heavy debug. Are these debugger …

I would be grateful if someone posted here 0.71 Heavy debug Windows binary. The reason is that I'm trying to find out why CodeView 3.11/3.14 crashes in DosBox. I debug programs written in Microsoft C 6.0 and they have symbolic information incorporated in them. This symbolic information is in NB02 …

GBA emulation is also possible under DosBox 0.71. Use no$gba 2.4c (DOS version). This emulator can be found here: http://nocash.emubase.de/gba.htm I recommend that you put the attached .CFG file in the same directory as the unpacked emulator for maximum performance. I must admit that compatibility …