Stas says:
> Just to be paranoid, could you please
> verify that it still works on 1.0.2.1?
> You have changed gcc and probably something
> else, so who knows...
OK, here's what I found out:
1.0.2.1 installed from precompiled binaries works under kernel 2.4.20, gcc 3.2.2
The binaries I thought were 1.0.x on my RH system (kernel 2.4.20, gcc 2.96) are
something newer; the announce file says it's 1.1.2 but I can no longer test it
because the binaries crash on my current (kernel 2.4.20, gcc 3.2.2) system. I
also can't get 1.1.2 to compile on my current system.
1.1.5 compiled easily on gcc 3.2.2, but it will not handle the DPMI calls by Clipper
the way the earlier versions did. Also, while writing all this and running tests, I
found the 1.1.5.1 patch and built that, but I got the same results.
I used the free pascal compiler on my NT to create some test programs that
allocate large amounts of DPMI memory, and they work fine with 1.1.5.{0,1} So
it's not ALL uses of DPMI that fail, only the Clipper programs.
> Yes. Please open the bug entry in dosemu's
> BTS on sourceforge and upload your files
> there.
Done. I included the Pascal EXE that requests DPMI successfully and the
boot.log that it generated with +M enabled in debug, and the Clipper EXE and
boot.log that show DPMI crashing.
pbs
--------
Peter B. Steiger
Cheyenne, WY
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
