Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Volkert via Freedos-devel
@Eric Auer Basically he was pretty sure that it would simply be too much work. See the discussion in this other GitHub thread: https://github.com/volkertb/temu-vsb/issues/4#issuecomment-703362672 On Mon, Aug 9, 2021 at 2:36 AM Volkert wrote: > > On Mon, Aug 9, 2021 at 2:26 AM Volkert > wrote:

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Volkert via Freedos-devel
On Mon, Aug 9, 2021 at 2:26 AM Volkert wrote: > > On Mon, Aug 9, 2021 at 1:36 AM Eric Auer wrote: > >> >> Hi Volkert, >> >> which worries does Japheth have regarding accepting I/O trap patches? >> > > He wrote: *"My experiences - so far - with patches from unknown people > are "mixed". So I'm ra

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Volkert via Freedos-devel
Hi Eric, On Mon, Aug 9, 2021 at 1:36 AM Eric Auer wrote: > > Hi Volkert, > > which worries does Japheth have regarding accepting I/O trap patches? > He wrote: *"My experiences - so far - with patches from unknown people are "mixed". So I'm rather sceptical."* Source: https://github.com/Baron-vo

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Eric Auer
Hi Volkert, which worries does Japheth have regarding accepting I/O trap patches? What are the pros and cons of supporting the QEMM API for I/O traps, compared to the MS EMM386 API? I think SB Live PCI soundcard drivers only support the MS API? How hard would MS API support for VSB be? > In po

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Steve Nickolas
On Sun, 8 Aug 2021, Volkert via Freedos-devel wrote: As you can see in his existing repositories on GitHub ( https://github.com/sudleyplace ), Bob seems partial to the GPLv3, so I guess that would be acceptable to FreeDOS, right? 🙂 My understanding is GPL3 is fine. Anyway, I opened an issue

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Volkert via Freedos-devel
On Sun, Aug 8, 2021 at 9:43 PM Steve Nickolas wrote: > > :O > > If 386^MAX could be released under suitable terms (for example the 4DOS > terms are problematic) then that would be something major to add to > FreeDOS. > As you can see in his existing repositories on GitHub ( https://github.com/su

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Steve Nickolas
On Sun, 8 Aug 2021, Volkert via Freedos-devel wrote: It turns out that writing another EMM386 reimplementation from scratch might not be necessary after all. Do you remember this thread from 2012? I see you participated in it as well: https://sourceforge.net/p/freedos/mailman/freedos-devel/thr

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Volkert via Freedos-devel
Hi Eric, On Sun, Aug 8, 2021 at 8:20 PM Eric Auer wrote: > > How about letting the SoftMPU maintainers write a patch for JEMM? > If they're not interested in maintaining a fork of their own project, I think it will be very unlikely to convince them to contribute such a patch to JEMM. Also, Jap

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Eric Auer
Hi Volkert, > Firstly, JEMM doesn't have a port trapping API that is compatible with > Microsoft's EMM386 memory manager. Yes, JEMM can offer similar > functionality using JEMM Loadable Modules (JLMs), but the programming model > of JLM is considerably different than the API in EMM386, or even Q

[Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Volkert via Freedos-devel
Hi FreeDOS devs, I understand that the EMM manager that currently ships with FreeDOS, JEMM, has several advantages over Microsoft's EMM386. Apparently it is more efficient in memory use and has some additional features and tweakable settings. And that's of course great. However, there are two thi