| delorie.com/archives/browse.cgi | search |
| Date: | Wed, 25 Jul 2001 11:49:46 +0300 (IDT) |
| From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
| X-Sender: | eliz AT is |
| To: | "Dykstra, Sean" <Sean_Dykstra AT maxtor DOT com> |
| cc: | "'djgpp AT delorie DOT com'" <djgpp AT delorie DOT com> |
| Subject: | Re: Pharlap 286 |
| In-Reply-To: | <68C4CF842BD2D411AC1600902740B6DA02CDC45D@mcoexc02.mlm.maxtor.com> |
| Message-ID: | <Pine.SUN.3.91.1010725114927.14848H-100000@is> |
| MIME-Version: | 1.0 |
| Reply-To: | djgpp AT delorie DOT com |
| Errors-To: | nobody AT delorie DOT com |
| X-Mailing-List: | djgpp AT delorie DOT com |
| X-Unsubscribes-To: | listserv AT delorie DOT com |
On Tue, 24 Jul 2001, Dykstra, Sean wrote: > Does anyone have any experience spawning a Pharlap286 application from > within a DJGPP app? > > The only way I can get it to work is to load the following statement in the > config.sys: > > Device=c:\emm386.exe RAM NOEMS Charles explained why, but please note that the reason is spelled out in section 15.8 of the DJGPP FAQ list.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |