Mail Archives: opendos/2000/04/04/15:49:04
Posted above the original to please someone but I normally don't do it
this way. :-/
Well, some/most/all of the djgpp-compiled stuff will use either
cwsdpmi (I think that's right) or go32.exe automatically if they're
in the path (probably won't work if not anyway).
For these programs, lynx to name one, they're usually started via a
batch file so I would use the dpmi=off/on anyway and things worked fine.
Non-djgpp programs that require DPMI and don't like DR-DOS's is
something else but I'm not sure if I ever came across any of those.
I'm sure there's gotta be a generic replacement out there that works.
On Mon, Apr 03, 2000 at 08:49:39AM +0500, Mark at Cross+Road's wrote:
>
> Hello All,
> Is there a tested and tried DPMI replacement for the DrDOS #703 version
> or another dpmi product that responded more tolerently to third party
> software? Or is it that the errors which show-up as emm386 "errors", would
> be simular to any dpmi product and are in the third party software and not
> truly the problem of the dpmi?
> The dpmi=off does solve the problem however the loss of memory with this
> solution is quite drastic and may not allow the program which you desired to
> have run at that point due-to a lack of free memory.
<<SNIP>>
> What have others done in this situation with the Dpmi of Drdos?
> Mark
>
--
>>ANIME SENSHI<<
Marc D. Williams
marcdw AT flash DOT net
http://www.oldskool.org/~tvdog/ -- DOS Internet & Tandy 1000
http://www.geocities.com/SiliconValley/Platform/8269/ -- Win3.x Makeover
- Raw text -