delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:175 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!europa.chnt.gtegsc.com!cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!newsfeed.rice.edu!rice!news!sandmann |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: [HELP] New int handler messes up fprintf |
Date: | Tue, 06 Jun 1995 14:47:59 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 7 |
References: | <gantose DOT 22 DOT 000B7026 AT lerc DOT nasa DOT gov> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
Nntp-Posting-Host: | clio.rice.edu |
To: | djgpp AT sun DOT soe DOT clarkson DOT edu |
Dj-Gateway: | from newsgroup comp.os.msdos.djgpp |
> In my program, I install a new interrupt handler for the system timer (int 8) > so that I can get 64 ticks per second. After a while, I put the old interrupt > handler back. Later in the program, when I try to fprintf some values, the If you do this you must run under DPMI. GO32 does not support restoring the original timer, keyboard or mouse interrupt handlers. A known bug, but GO32 is going away with V2.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |