Michael wrote:
>You can customize how mail reader screen looks by modigying source code of
>Insight.exe (it is GPL-ed, see http://gnu.arachne.cz page).
Michael, you can't assume anyone is able to change the source. (But this
one isn't hard to change if you want one that behaves the other way for
yourself).
>But I don't understand how exactly CWSDPMI works; I know, I should
>tell people to disable DR-DOS built in DPMI status (and I will do, on
>Arachne homepage).
I don't know much about DPMI myself, but I do know that cwsdpmi.exe will
load if it's in the path (and the program is a djgpp program).
>From the docs:
CWSDPMI was written to provide DPMI services for V2 of DJGPP. It currently
does not support 16-bit DPMI applications, or DPMI applications requiring a
built in extender. It does support virtual memory and hardware interrupt
reflection from real mode to protected mode. DJGPP V1.1x and RSX
applications
will also run using this server, which can be used to provide enhanced control
over hardware interrupts. Some DPMI 1.0 extensions (0x506, 0x507, 0x508)
have
been implemented.
(Ok, that wasn't very helpfull <g>)
Additionally what Willy found out (in a private mail to me) is probably of
interest:
>Caldera DR-DOS v7.01, has a very buggy DPMI host. This one
>can better be disabled!!!
>
>BUT.... this is not true with Caldera/Lineo DR-DOS 7.03,
>which has a very good DPMI host (better and faster than
>CWSDPMI). Disabling it, is _not_ recommended!!!
Any info on 7.02?
Perhaps we should contact Matthias Paul (DR-DOS guru and programmer)?
>I think that either loading CWSDPMI in AUTOEXEC.BAT
>would eat DOS memory, or not-loading it slows down DJPEG and JPNG2BMP,
>because they have to re-load it each time they are launched. Is this
>correct ?
Yes that's certainly true, but I wonder how much it actually affects
things. One thing that might help would be if all JPG/PNG conversion could
be done like this:
cwsdpmi.exe -p
djpeg32.exe -bmp whatever.jpg cache\12345678.bmp
djpeg32.exe -bmp whateve1.jpg cache\12345679.bmp
djpeg32.exe -bmp whateve2.jpg cache\12345670.bmp
cwsdpmi.exe -u
And then this BATch file would be run by Arachne.
Still I don't think there's much (if anything) to gain on doing it like that.
The users that know that they can fit cwsdpmi in memmory can do so (cwsdpmi
-p) and if they know that they probably know that they can change mime.cfg
as well (remove all mentions about cwsdpmi).
Others shouldn't need to concern themselves IMHO. (Except to turn buggy
DPMI off).
What happens if DR-DOS DPMI is on and cwsdpmi is executed?
