X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: ahenric AT ccii DOT co DOT za (Arne)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Speeding up timer
Date: 14 Oct 2003 07:31:02 -0700
Organization: http://groups.google.com
Lines: 22
Message-ID: <e74abcbf.0310140631.5440f2ca@posting.google.com>
References: <e74abcbf DOT 0310130606 DOT 19aee3c AT posting DOT google DOT com> <bmeck7$60n$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <e74abcbf DOT 0310132253 DOT 66f171fc AT posting DOT google DOT com> <ur81gkwy6 DOT fsf AT elta DOT co DOT il>
NNTP-Posting-Host: 196.30.62.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1066141862 9481 127.0.0.1 (14 Oct 2003 14:31:02 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: Tue, 14 Oct 2003 14:31:02 +0000 (UTC)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hi,

yes, I have tried PCTIME, but there again it just doesn't change
anything. PCTIME will change the frequency, but the new handler will
still call the original tick handler at the default frequency of
18.2Hz. Thats why I think the signal SIGALRM is called somehow always
from this original handler. Any idea how to generate SIGALRM from my
own handler? Will a signal only be generated when the handler returns?

Eli Zaretskii <eliz AT elta DOT co DOT il> wrote in message news:<ur81gkwy6 DOT fsf AT elta DOT co DOT il>...
> > From: ahenric AT ccii DOT co DOT za (Arne)
> > Newsgroups: comp.os.msdos.djgpp
> > Date: 13 Oct 2003 23:54:00 -0700
> > 
> > I am writing this application for MS-DOS only, and I am using the
> > DJGPP compiler. Why does the timer not speed up when I change it? Does
> > the DPMI server somehow prevent the change to the PIT? And from where
> > is the SIGALRM signal called: from INT 08h or INT 70h?
> 
> The DPMI server does not prevent you from reprogramming the timer.
> In fact, there used to be a PCTIME14.ZIP file on SimTel (RIP) that
> showed a working code that did what you intend.