Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!bak10413
From: bak10413@uxa.cso.uiuc.edu
Newsgroups: comp.sys.ibm.pc
Subject: Re: IBM PC/AT interrupt problems
Message-ID: <46500087@uxa.cso.uiuc.edu>
Date: 9 May 90 15:33:00 GMT
References: <6183@gssc.UUCP>
Lines: 12
Nf-ID: #R:gssc.UUCP:6183:uxa.cso.uiuc.edu:46500087:000:334
Nf-From: uxa.cso.uiuc.edu!bak10413    May  9 10:33:00 1990


Perhaps if you install a hook onto the timer interrupt so when you're
ready to call your interrupt, you can wait until the timer 'ticks' before
you call yours, and then you don't have to worry about the timer interrupting
your code.

- Just a thought...

Brent Knecht
bak10413@uxa.cso.uiuc.edu
University of Illinois
Urbana-Champaign