VOGONS

Common searches


Search results

Display options

Re: Tandy DMA behavior

You're using machine=vga AND tandy=true. In this configuration the 2nd dma controller HAS to be disabled as there are port conflicts, and in order to get sound of the games which support vga video modes and tandy sound simultaneously the 2nd dma controller has to be closed. There won't be any …

Re: mouse is jumpy

in DOSBox General
Do regular 32bit x86 compiles work? Maybe i can send you a build that displays some information about the mouse SDL events. Guess that the SDL people would be interested in knowing about it if there's really a bug.

Re: mouse is jumpy

in DOSBox General
> i guess the issue is with SDL? Well i don't know, but i assume it is as two different programs are affected. You could test that by modifying the sources, maybe somebody else with the same system could do that as well.

Re: mouse is jumpy

in DOSBox General
As they're using the relative mouse motion fields as well, i guess the SDL_MouseMotionEvent->xrel and ->yrel is messed up on your system. You can try to output the fields of the motion-variable in HandleMouseMotion() of sdlmain.cpp

Re: DOSBOX's CDROM device name

in DOSBox General
The name is not changable, it's hardcoded into the sources. The name shouldn't matter as there are defined interfaces to the cdrom driver, and the regular file searching for a block dev works as well.

Re: Linux + SvgaLib = keyboard problem

in DOSBox General
In the file mentioned by Qbix, there's an adjustment for linux scancode keys (search for key-=8; ). Maybe that depends on xwindows though, if you're compiling the sources you can just remove that -=8. At least if you want/need it to be working with usescancodes=true as well.

Re: Dragonsphere Help

Guess they are accessing the DPB to query the freesize, but those tables are highly drive-geometry dependent which is impossible to implement for the directory mounting of dosbox. If you find that check, you might want to hack it out of the executable.

Page 399 of 445