Search \ VOGONS

Re: Sending video output and receiving keyboard input over the network

Posted on 2020-05-06, 15:31

I had the same idea years ago, but never got around to actually implementing something. I’d like to be able to play Micro Machines 2 over the network.

Re: clear Keyboard Buffer

Posted on 2020-04-08, 19:10

by Ringding

in DOSBox Development

There is a ring buffer somewhere in the BIOS area, whose head and tail positions can be set. I forgot the details. But how does your application handle keyboard input? Does it handle int 9 itself? If it does it on its own, then there should be no need to call the original int 9 handler, thus nothing …

Re: Can't allocate more than 64K under DOSBox and Turbo C (malloc fail) [FIXED]

Posted on 2020-04-06, 12:11

by Ringding

in DOSBox Development

I guess the same will be true for Turbo C++ 3.1. I’ve just never seen it.

Re: Can't allocate more than 64K under DOSBox and Turbo C (malloc fail) [FIXED]

Posted on 2020-04-06, 07:26

by Ringding

in DOSBox Development

Borland C++ 3.1 was still DOS and Windows, like 3.0.

Re: Can't allocate more than 64K under DOSBox and Turbo C (malloc fail) [FIXED]

Posted on 2020-04-05, 19:34

by Ringding

in DOSBox Development

So this is already a DOS-extended version. This means that there should easily be more than 500 KB available for the program.

Re: Can't allocate more than 64K under DOSBox and Turbo C (malloc fail) [FIXED]

Posted on 2020-04-01, 19:19

by Ringding

in DOSBox Development

There should be a menu item "Get Info" – in Turbo C 2 it’s in the Compile menu – that shows the amount of available memory. For me it shows 295K (under qemu). This would be roughly the amount of memory you can expect to be able to allocate from your program.

Re: PowerPC Dynamic Recompiler (patch)

Posted on 2019-10-05, 17:22

by Ringding

in DOSBox Development

Isn’t this dead since 10.5?

Re: Dynrec (x86_64 linux) problems with win3.11

Posted on 2019-04-15, 16:18

by Ringding

in DOSBox Development

The problematic instruction is pop dword [eax+0x87], where [eax+0x87] points into a non-present page. The normal core handles this quite differently from the dynrec core by using mem_writed_inline which spawns a nested run loop via PAGING_PageFault to run the exception handler and then continues …

Re: Dynrec (x86_64 linux) problems with win3.11

Posted on 2019-04-05, 17:57

by Ringding

in DOSBox Development

Ringding wrote: Yes. Setting the translation block size to 1 does not make any difference. Not with and not without the pop_ev commented out. Rereading my own report from earlier, I have to correct this. It does make a difference with the pop_ev left alone. Then it exits Windows when I try to run …

Re: Dynrec (x86_64 linux) problems with win3.11

Posted on 2019-04-05, 17:50

by Ringding

in DOSBox Development

Is that fixed with commenting out the pop_ev instruction block ? As that was the bug I am trying to fix. Yes. Then it works. Also imgmount. So windows does boot if you set the instructions to 1 (and not apply the push_imm commenting) ?, exit windows happens at my place during startup, so I don't …

Re: Dynrec (x86_64 linux) problems with win3.11

Posted on 2019-04-04, 20:06

by Ringding

in DOSBox Development

The dynrec problem seems to be caused by the S3 video driver wanting to switch into text mode. It does not happen with: - Standard VGA - S3 driver with windowed DOS Prompt Driver: S3 Trio64V 1.70.04 1024x768 64K C SF I can imgmount an iso file without a problem.

Re: Dynrec (x86_64 linux) problems with win3.11

Posted on 2019-04-04, 09:45

by Ringding

in DOSBox Development

What I don’t get: In the other thread you mentioned that just starting the DOS Prompt caused the dynrec error, same as for me. How come that you are reporting a different experience now?

Re: Dynrec (x86_64 linux) problems with win3.11

Posted on 2019-04-03, 22:30

by Ringding

in DOSBox Development

Last update: I missed the part about this being about 0.74-2. I used the trunk version previously, but it makes absolutely no difference.

Re: Dynrec (x86_64 linux) problems with win3.11

Posted on 2019-04-03, 22:18

by Ringding

in DOSBox Development

No, also not with Win 3.11. 1. imgmount works (at least, does not crash) 2. Windows starts and seems to run normally.

Re: Dynrec (x86_64 linux) problems with win3.11

Posted on 2019-04-03, 21:41

by Ringding

in DOSBox Development

Uh, so you're talking about Windows 3.11, not Windows for Workgroups. Is that right? I used WfW. I'll have to reinstall anyway, as I just removed my image accidentally with an incautious usage of git clean -dfx 😉. 🙁

Re: Dynrec (x86_64 linux) problems with win3.11

Posted on 2019-04-03, 21:34

by Ringding

in DOSBox Development

I cannot, neither of them. For 1., I don't get so far, because it crashes when I start the DOS prompt: Exit to error: DynrecCore: illegal option in dyn_mov_seg_ev For 2., I don't see a difference, except that it does not crash anymore when I start the DOS prompt, but instead seems to exit Windows …

Re: DOSBox-X branch

Posted on 2018-12-23, 12:39

by Ringding

in DOSBox Patches

FYI The patch in svn r4177 referenced from this other thread is also required for DosBox-X and works (tested on Fedora 29 x86_64).

Re: DOSBox bug OS X regression

Posted on 2018-12-12, 13:02

by Ringding

in DOSBox Development

macOS is very troublesome regarding frame updates. The problem is that DOSBox wants to update its screen 70 times per second, but macOS doesn't like this, because it considers it wasteful, and throttles DOSBox, which leads to the sound stuttering problem. Unfortunately, the exact behavior varies …