Mail Archives: djgpp/1996/05/20/21:18:17
Xref: | news2.mv.net comp.os.msdos.djgpp:4059
|
Newsgroups: | comp.os.msdos.djgpp
|
From: | men5cdr AT sun DOT leeds DOT ac DOT uk (C D Radcliffe)
|
Subject: | Help required with DPMI Conflict
|
Message-ID: | <1996May20.195533.28424@leeds.ac.uk>
|
NNTP-Posting-Host: | sunserv2_ie2.leeds.ac.uk
|
Organization: | University of Leeds, England
|
Date: | Mon, 20 May 1996 20:55:33 +0100 (BST)
|
Lines: | 21
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Can anyone help or shed some light on to my problem. I have been using
GNUPLOT compiled under V1.09 for some time now with no problems.
On upgrading to DJGPP V2.0 and recompiling GNUPLOT I find a problem when
I spawn a shell. From within GNUPLOT I would normally spawn a shell and
run ghostscript (V3.1.2 Watcom DOS4/GW compiled version). If I do that
with the V2.0 compiled Gnuplot my machine hangs/crashes.
I assume that there is a conflict between the DPMI of gnuplot and that
of DOS4/GW. I am using the default CWSDMPI driver, which is loaded at
gnuplot run time.
Can anyone offer advice?
Thanks
Chris Radcliffe,
Department of Mechanical Engineering,
University of Leeds, __o
Leeds, LS2 9JT, UK. _ _`\<,_
men5cdr AT sun DOT leeds DOT ac DOT uk (0113 - 2332152) -_ (_)/ (_)
- Raw text -