Xref: utzoo comp.sys.ibm.pc.programmer:1373 alt.msdos.programmer:1611 Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!ohstpy!miavx1!rjlewis From: rjlewis@miavx1.acs.muohio.edu Newsgroups: comp.sys.ibm.pc.programmer,alt.msdos.programmer Subject: Re: which timer interrupt? Message-ID: <1371.26461650@miavx1.acs.muohio.edu> Date: 8 May 90 05:44:00 GMT References: <484@wjh12.harvard.edu> Distribution: na Lines: 18 In article , mshiels@tmsoft.uucp (Michael A. Shiels) writes: > All of my utilities hook 8 and first call the old 8 then they sit > in a semaphored section donig there stuff. > > This was because way back a lot of TSRs didn't chain to the old int 1C handler > so all of a sudden you lost touch with timer ticks. Everyone passes 8 on > or your machine would lose track of time. I understand why you hook INT 8h, but how do you call the Original Int 8h handler, and have it RETURN to your code? If you call the original int 8h handler, it'll end with a IRET, and won't it bounce back to the currently executing program (and NOT your handler). -- __ Rich Lewis / ) / rjlewis@MIAVX1.acs.muohio.edu / __ __. _ /_ RL83SANU AT MIAMIU.BitNet (__/ / (_(_/\_/_)_/ /_