Mail Archives: djgpp/1997/10/28/15:31:23

From: Mark Slagell <bald_soprano AT nospam DOT usa DOT net>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: PCTIME13
Date: Mon, 27 Oct 1997 06:58:39 -0600
Organization: Lunar Hostility Studies
Lines: 26
Message-ID: <>
References: <3453BC56 DOT 55A6 AT nospam DOT usa DOT net> <3455600a DOT 1637974 AT news DOT uni-duisburg DOT de>
Mime-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Michael Mauch wrote:
> > What I'm trying to get, ultimately, is a reliable 200hz interrupt.
> On plain DOS you can use the libc function uclock(), on Windows/Win95
> you can use the puclock() function that is in the DJGPP mail archives
> at (search for puclock()).

That would provide a high-resolution timer, but not an interrupt per se,
or would it?

I can get PCTIME running at the right speed by removing this line from

So it would seem that under Windows, both the protected mode and real
mode handlers get called with every timer tick, and under DOS only the
real mode handler gets called.  I don't understand this, and would
rather not blindly hack at the code without knowing why a modification
seems to work...



Remove the "nospam." to reply by email.

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019