Search \ VOGONS

Login

Login

Username

Password

2FA token (optional)

Remember me

Hide my online status this session

Lost password
Send activation email

or Create a new account
Create a new account

Common searches

Active topics

Search results

Display options

Re: Redirecting stdout/stderr from within DOSBox outside of it?

Posted on 2021-02-06, 15:03

in DOSBox General

in DOSBox General

It really depends on your setup. I can understand that compiling LibreOffice on a 2009 laptop, even with SSD and maxed out RAM can take at least 10 hours... but with a current-day Ryzen and 32GB RAM you can do it in 40-50 minutes if you know what you're doing. I was talking specifically about e_ …

Re: Redirecting stdout/stderr from within DOSBox outside of it?

Posted on 2021-02-05, 15:08

in DOSBox General

in DOSBox General

There is also WiseUnpacker, which should be up to the task (not tested yet) and might be portable enough.

Re: Redirecting stdout/stderr from within DOSBox outside of it?

Posted on 2021-02-05, 15:01

in DOSBox General

in DOSBox General

Between line 30 and 40 there's a considerable amount of time taken. It would be nice to let us know what's exactly happening. Normally when e_wise is run in DOSBox, it looks like in the attachment. Now that I’ve seen it myself, I know what you’re talking about. However, IIRC without ansi.sys, DOS …

Re: Redirecting stdout/stderr from within DOSBox outside of it?

Posted on 2021-02-05, 14:30

in DOSBox General

in DOSBox General

moog wrote on 2021-02-05, 02:53: Everyone who uses Gentoo is patient. 😁 This is really really slow, though…

Re: Redirecting stdout/stderr from within DOSBox outside of it?

Posted on 2021-02-05, 12:53

in DOSBox General

in DOSBox General

Where would be the fun in that? 😜

Re: Redirecting stdout/stderr from within DOSBox outside of it?

Posted on 2021-02-05, 08:48

in DOSBox General

in DOSBox General

Going by the files in the source archive, it seems to have been built with Virtual Pascal. Which I don't know, but I had experience with Turbo Pascal back then. And I speak German, so I can at least easily understand all the messages, comments and identifier names in there.

Re: Redirecting stdout/stderr from within DOSBox outside of it?

Posted on 2021-02-05, 08:37

in DOSBox General

in DOSBox General

Are there free data files available somewhere that I could test e_wise on?

Re: Redirecting stdout/stderr from within DOSBox outside of it?

Posted on 2021-02-04, 19:27

in DOSBox General

in DOSBox General

I’ve recently seen a very similar usage of DOSBox in the open-watcom-v2 build. I did not check what they did exactly, but superficially, it would be mostly the same. Do you really need stdout? Don’t you just need to get out some files? After you have a mount, that would happen automatically anyway. …

Re: DOSBox ECE (for Windows & Linux)

Posted on 2021-01-29, 16:06

in DOSBox Development

in DOSBox Development

No. This code is just not compatible with Windows x64, apparently. Because on Windows, longs are 32 bit and thus not large enough to hold a pointer.

Re: DOSBox ECE (for Windows & Linux)

Posted on 2021-01-16, 08:18

in DOSBox Development

in DOSBox Development

Interesting. The vgaonly setting should not have anything to do with the output side, as it only specifies what is being emulated. So the fact that it manages to mess up a shader is somewhat surprising.

Re: DOSBox ECE (for Windows & Linux)

Posted on 2021-01-14, 15:29

in DOSBox Development

in DOSBox Development

Original resolution is 640 x 400, but you can see that the game itself already has pixels of 2 x 2 (see attachment "original"). 640 x 400 would have been considered high resolution at that time, which Lemmings definitely was not. Is "640 x 400" not just an artifact of how DOSBox handles this …

Re: 2x scaling by averaging in DOSBox. Is it possible?

Posted on 2020-12-29, 12:24

in DOSBox General

in DOSBox General

Bilinear is basically averaging. Thinking about the positioning of the picture, it will most likely be offset by half a pixel compared to your method, so no original lines will remain, as every one will be a linear combination of two input lines. I have not played with the shaders myself, although …

Re: dynrec vs. secure platforms - opinions wanted

Posted on 2020-12-05, 15:38

in DOSBox Development

in DOSBox Development

Apparently rather than discussing possible solutions, other people just want to be told what works so they can slap it in their project and take credit for figuring it out. :D I'm generally interested in this topic, but really short on time currently. And it seems you are the master of code …

Re: DOSBox-X branch

Posted on 2020-11-28, 17:10

in DOSBox Patches

in DOSBox Patches

Here is a hint about x86_64 builds running in Apple M1: "The system prevents you from mixing arm64 code and x86_64 code in the same process. Rosetta translation applies to an entire process, including all code modules that the process loads dynamically." Yes, obviously. I doubt anyone would expect …

Re: DOSBox-X branch

Posted on 2020-11-11, 18:55

in DOSBox Patches

in DOSBox Patches

Which compiler do you use for building? If it works on a Pentium 4, it’s likely built for SSE2 (-mfpmath=sse in gcc, might be set by default in recent mingw releases).

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

Posted on 2020-05-06, 15:31

in DOSBox Development

in DOSBox Development

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

in DOSBox Development

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

in DOSBox Development

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

in DOSBox Development

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

in DOSBox Development

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.

Page 7 of 9

Go to top of page Go to top of page