home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!news.mentorg.com!caeco!picard!gillmore
- From: gillmore@picard.slc.mentorg.com (Mike Gillmore (Consultant))
- Subject: Re: Can TSR slow down system too much?
- Message-ID: <1992Aug17.202850.12580@caeco.mentorg.com>
- Sender: gillmore@picard (Mike Gillmore (Consultant))
- Reply-To: mike_gillmore@mentorg.com
- Organization: Mentor Graphics Corp., Murray, Utah
- References: <15775@star.cs.vu.nl>
- Date: Mon, 17 Aug 1992 20:28:50 GMT
- Lines: 31
-
- In article <15775@star.cs.vu.nl>, estel@cs.vu.nl (Stel E) writes:
- >
- > Hai programmers,
- >
- > I've made a simple Screen Saver. I'd like the program to work
- > with both DOS and Windows programs. So I hooked it to the
- > timer interrupt (0x1c). Every time this interrupt is generated
- > (18.2 times a sec.) it checks the SHIFT status (scancode).
- > If both SHIFT keys are pressed, the screen blanks, if some
- > other key (SHIFT/ALT/CTRL) is pressed the screen unblankes.
- >
- > The program has to check some things every time it's called.
- > Can this slow down my machine too much? Can my clock start
- > to run too slow (clock = DOS clock)? It's not so easy to
- > test (my machine is quite fast). I couldn't notice any
- > difference, not even when blanking/unblanking very fast and
- > frequent.
- >
- > I don't think it's a problem, but I wanna be sure.
- >
- >
- > Thanks in advance, Erik Stel (estel@cs.vu.nl)
-
- Rather than checking at every clock tick, why not check with
- each key press (Int 9). This is much more efficient (at least
- in my experience), and seems to make more sense.
-
-
- --
- Mike "Okie" Gillmore
- no .sig, no glory
-