From: "ChaoTix" <ChaoTix AT c-a-t DOT nl>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Terminate and Stay resident in CWSDPMI
Date: Tue, 15 Oct 2002 13:35:16 +0200
Organization: XS4ALL Internet BV
Lines: 49
Message-ID: <aogul8$p30$1@news1.xs4all.nl>
References: <aofchh$kar$1 AT news1 DOT xs4all DOT nl> <3dab979d DOT sandmann AT clio DOT rice DOT edu> <aogspp$kf3$1 AT news1 DOT xs4all DOT nl>
NNTP-Posting-Host: 213-84-241-227.adsl.xs4all.nl
X-Trace: news1.xs4all.nl 1034681832 25696 213.84.241.227 (15 Oct 2002 11:37:12 GMT)
X-Complaints-To: abuse AT xs4all DOT nl
NNTP-Posting-Date: 15 Oct 2002 11:37:12 GMT
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hey, thats strange. It seems to work under full dos mode, but not in windows
98/95 dos. But we can still work with it. Thanx.

Greetz,

ChaoTix


"ChaoTix" <ChaoTix AT c-a-t DOT nl> wrote in message
news:aogspp$kf3$1 AT news1 DOT xs4all DOT nl...
> Can't start COMMAND.COM
>
> Thats the error I am getting when try to call interrupt 21 which includes
in
> the djgpptsr.zip.I am just using Windows 98 and not NT windows like. Does
> nobody have some source code of 5 lines to keep a program in memmory??? It
> cant be that hard, because Watcom seems to have a simple function called
> keep.
>
> Greetz,
>
> ChaoTix
>
> "Charles Sandmann" <sandmann AT clio DOT rice DOT edu> wrote in message
> news:3dab979d DOT sandmann AT clio DOT rice DOT edu...
> > > It seems that the standard __dpmi_terminate_and_stay_resident(x,x);
does
> not
> > > works in windows and CWSDPMI (wich is used by djgpp). Does anybody has
> still
> > > a way to simple terminates the programs, and stays in memmory.
> (Example?)
> >
> > This is a DPMI 1.0 function, and probably nothing implements it.
> >
> > Did you try v2tk/djgpptsr.zip?  Comment the section on space saving and
> > uncomment the line about resetting exceptions, and it will at least
build.
> >
> > It seems to work fine on Windows 95 & 98; it was tested on DOS some time
> back.
> > It even ran under Windows 2000, but I never saw the cursor change (so
> > interrupts aren't getting there?)
> >
> > DOS sessions which are not active may not recieve interrupts on Windows.
>
>