home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!math.fu-berlin.de!news.netmbx.de!Germany.EU.net!mcsun!sunic!seunet!kullmar!henryg
- From: henryg@kullmar.se (Henry Gessau)
- Subject: Virtual timer ticks into TSR loaded before Windows
- Message-ID: <1992Jul31.092732.9971@kullmar.se>
- Summary: Some versions of Windows 3.0 have a timer bug!
- Keywords: TSR Windows enhanced timer virtual
- Organization: Firma Bo Kullmar Datakonsult
- Date: Fri, 31 Jul 1992 09:27:32 GMT
- Lines: 30
-
-
-
-
- I have a TSR that hooks to the timer interrupt (INT 08, IRQ 0), among
- others. It uses this interrupt for various timings.
-
- I usually load my TSR and then start Windows, which runs in enhanced
- mode on my machine. This means that my TSR exists in every DOS window
- that I open. It works fine on all computers that I have tested,
- except one. All the ones where it worked OK ran either Windows 3.1
- (English or Swedish versions) or a Swedish version of Windows 3.0.
-
- However, when I ran it under an English (USA) version of Windows 3.0,
- something went wrong. It turned out that this particular version
- simulates one timer interrupt into my TSR for every virtual machine
- that exists. Surely this is a bug (why don't later versions have this
- behaviour)?
-
- If I know that some particular version of Windows has this horrible
- symptom then I can fix it by checking the ID of the current VM for
- every tick (yuk, I know).
-
- BUT, how do I know whether the version of Windows that is running has
- this bug?
- Has anyone else had a problem with this?
-
- --
- Henry Gessau henryg@kullmar.se
- --
- Henry Gessau henryg@kullmar.se
-