Mail Archives: djgpp/1996/07/16/02:00:14
Date: | Tue, 16 Jul 1996 08:52:21 +0200 (IST)
|
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
|
To: | djgpp AT delorie DOT com
|
Subject: | Re: Locking RAM for hardware interrupts
|
In-Reply-To: | <Pine.SOL.3.91.960715180219.9688B-100000@zveris>
|
Message-Id: | <Pine.SUN.3.91.960716083940.15934F-100000@is>
|
Mime-Version: | 1.0
|
On Mon, 15 Jul 1996, Orbital wrote:
> Now something about the FAQ, so I suppose this goes to Eli:
Thanks for your comments. I will incorporate them into the next FAQ
release.
> Also, the FAQ makes [used to make] the FAT-DS approach
> look kinda scary (at least to me). It is clear, that every single
> Watcom/DOS4GW application uses it (not sure, but I think Borland 4.5+
> 32 bit DOS apps do as well) and nobody seems to care much.
Should I tell you how many times my kids trashed the disk with those
Watcom/DOS4GW apps? IMHO, this should be scary. If the FAQ does sound
that way, then for once I managed to explain myself loud and clear.
> * The FAQ could [does?] have a hint to prevent GNU Make from crashing
> under OS/2 Warp. The hint to set DPMI_DOS_API to ENABLED instead of
> AUTO in DOS Settings for the session. DPMI_MEMORY_LIMIT is also nice
> to experiment with.
I cannot tell anybody anything about OS/2 setup unless somebody reports
it on the news group, and in enough detail so I can at least understand
what am I writing about. If there are important DJGPP-specific system
configuration hints for OS/2, by all means post them, and they will be in
the next release of the FAQ. I don't myself use OS/2 and don't know
anything about it (I only heard about DPMI_DOS_API stuff the other day
when Martynas posted his message).
- Raw text -