VOGONS

Search

Common searches

Search results

Display options

Display options

Re: Feature Request: Innovation SSI-2001 Support

Posted on 2006-11-06, 09:01

Innovation driver file in U6 is one of the smallest audio drivers there (the only smaller driver is Roland). The file itself is barely 1K binary, should not be that difficult to analyze. Also, the game does not check for the card presense. Just setting that card and watching port 280 (or whatever …

Re: Unable to set sound in Dark Legions

Posted on 2006-10-16, 08:04

I cannot confirm your issues, everything seems to work fine, at least to the copy protection screen which I currently cannot bypass because I don't have access to the manual. I'm however using a somewhat modified cvs version. Also I find it weird that there isn't any error message. There should be …

Re: Floppy Images & Copy Protection (Lemmings)

Posted on 2006-10-14, 16:23

I've once seen a very sophisticated copy protection sheme that also checked whether the floppy disk drive was actually working by hooking the FD IRQ (0eh) to find out whether it is being called during int 13h service calls. DOSBox does not imitate this behaviour. (Note: this isn't fixed by booting …

Re: Animated cursor capture

Posted on 2006-10-09, 14:29

in DOSBox General
> In the general case you might have to trace back your way from the mouse handler to drawing routine Yes, this situation is the most likely one and can be easy or hard depending on the game. I just wanted to point out that there's no simple debugger switch to separate the mouse drawing from the …

Re: Animated cursor capture

Posted on 2006-10-09, 13:15

in DOSBox General
No, because memory access (and drawing a pixel is such an operation) is not attributed with a "i'm a mouse cursor pixel" flag ;) The only case where the mouse cursor is in a way independent from the rest is when the default cursor is used, as then dosbox itself has to draw that cursor. But this one …

Re: Animated cursor capture

Posted on 2006-10-06, 15:59

in DOSBox General
Just a though and maybe a stupid idea, but you could record the anim a few times just with different backgrounds. The common overlap is then the desired cursor. It's probably best to write a little program to do the frame comparisons and extract the images. Or you hack the program to display only …

Re: Invalid opcode handling

Posted on 2006-09-21, 08:51

> All those things would result in a huge slow down, so they'll never be added. I fully agree there, can't think of any efficient way either besides using virtualization. Paging slows down things already enough. Is paging support actually fully compatible? That's the part I'm currently about to …

Re: Invalid opcode handling

Posted on 2006-09-20, 09:20

Undocumented opcodes are present, besides some 286-only ones. You guys are really doing great work :) That's exactly what should be done (and already was done for some antidebugging stuff): trying to understand if it IS intentional or just hits some bug in dosbox. If we'd throw an int6 always for …

Re: Invalid opcode handling

Posted on 2006-09-20, 08:09

> that there is a game/program that is not considered is always greater than zero. I'm quite sure about that as well, but it's a lot better imo to really check each case if it really forces an int6 (win3.x does that for example to install some of its exception handlers). And some of those invalid …

Re: FPU bug

Posted on 2006-09-19, 17:40

wd wrote: Yes, the timing (PIC_Ticks logic) mainly, which leads to a lot of dependent code (sound blaster, pcspeaker, timer). That's the tricky part of it 😉 Just wondering, maybe it's possible to replace it by 64 bit integer arithmetics, but I don't know about the accuracy needed.

Re: Invalid opcode handling

Posted on 2006-09-19, 17:38

> The current behavior of DOSBox when encountering an invalid opcode is > to exit with an error message. No, those cases which are used by games/programs raise an int6. Most others are, as you said, considered to be the result of executing rubbish, thus exit dosbox to avoid damage. I see, but the …

Invalid opcode handling

Posted on 2006-09-19, 15:11

The current behavior of DOSBox when encountering an invalid opcode is to exit with an error message. The expected behavior on a real CPU is to raise exception 6 with the (E)IP on the stack pointing to the unrecognized instruction. Now, I've come across a program which actually uses this to create a …

Re: FPU bug

Posted on 2006-09-19, 14:58

Makes sense actually to do so. Does DOSBox itself contain code that compiles into FPU instructions? I guess not, can't think of any place where it would make sense (unless some fancy scaler)

Re: FPU bug

Posted on 2006-09-19, 10:18

There's a stack-wrapping missing in dyn_fpu_esc6(), FCOMPP (that is case 0x03) should look like this: gen_load_host(&TOP,DREG(EA),4); gen_dop_word_imm(DOP_ADD,true,DREG(EA),1); gen_dop_word_imm(DOP_AND,true,DREG(EA),7); ( the DOP_AND line added). I think i'll upload those fixes even though the …

Re: FPU bug

Posted on 2006-09-12, 07:29

It was easy to narrow this bug down to a faulty fnstsw ax instruction. Try this patch: http://session-x.net/dosbox_fnstsw_fix.patch The problem was simply that dosbox zeroed out the high word of EAX when in fact it should only alter the low word (ax).

Page 1 of 2

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