Message-ID:	<2FFA127C.3248@linetap.com>
From:	nebo <nebo AT linetap DOT com>
Organization:	neboland
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Timer interrupt
References:	<01bda6f1$8ceb4540$LocalHost AT SPOCK> <6nl9r2$fte$1 AT news-hrz DOT uni-duisburg DOT de> <01bda78d$23b78920$433461cb AT spock>
Lines:	32
Date:	Sun, 05 Jul 1998 01:09:12 GMT
NNTP-Posting-Host:	209.205.49.227
NNTP-Posting-Date:	Sat, 04 Jul 1998 21:09:12 EDT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Matt Barker wrote:
> 
> > I don't know the answer to your question, but I have answers to
> > questions you didn't ask:
> >
> > OldTimerHandler() sends an EOI on its own, so you shouldn't do it in
> > your handler when you call OldTimerHandler(). And IIRC you shouldn't
> > call Int 1C manually, because that's done by OldTimerHandler() as well -
> > and I guess you set Factor so that OldTimerHandler() is called just as
> > often as it is normally called.
> 
> Won't OldTimerHandler() end with an iret instruction though, in which case
> it will not return to my handler???  It certainly seemed to work OK.

	It will end with an iret instruction, but...
	IRET only pops IP, CS and the flags, and then returns to the
	interrupted program(your handler).


-- 



        Nb
        nebo AT LTS                MajorNet
        nebo AT linetap DOT com        Internet


        I'll stop drinking when I can't pour,
        I'll stop standing when I fall over,
        I'll stop moving when I pass out,
        I'll stop dreaming when I die.

- Raw text -