| www.delorie.com/archives/browse.cgi | search |
| Xref: | news2.mv.net comp.os.msdos.djgpp:5427 |
| From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: [Q] How does go32 handle the timer tick (interrupt 0x08)? |
| Date: | Wed, 26 Jun 1996 12:08:39 CDT |
| Organization: | Rice University, Houston, Texas |
| Lines: | 13 |
| Message-ID: | <31d16e97.sandmann@clio.rice.edu> |
| References: | <DtLE6z DOT IKn AT world DOT std DOT com> |
| Reply-To: | sandmann AT clio DOT rice DOT edu |
| NNTP-Posting-Host: | clio.rice.edu |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> I have been trying to install a timer interrupt (0x08) handler for a > program under DJGPP/Go32. I've tried a dozen different things and none > worked. No matter what I do, it often crashes, won't deinstall, and > won't co-operate with the keyboard handler. If it's waiting for a > keystroke it loses interrupts. Sure, all known problems with GO32. That's why interrupts were completely re-written in CWSDPMI. You have three options: 1) Quit messing with hardware interrupts; 2) Use a DPMI provider with go32/v1.x (ie windows/cwsdpmi) 3) Upgrade to V2.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |