Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!sm.unisys.com!csun!csuna!abcscnuk
From: abcscnuk@csuna.UUCP (Naoto Kimura)
Newsgroups: comp.lang.pascal
Subject: Re: Int 1CH
Keywords: quest qe ce?
Message-ID: <1635@csuna.UUCP>
Date: 1 Feb 89 19:21:39 GMT
References: <369@lafcol.UUCP>
Reply-To: abcscnuk@csuna.UUCP (Naoto Kimura)
Organization: California State University, Northridge
Lines: 25

In article <369@lafcol.UUCP> pilgrimk@lafcol.UUCP (Guru Jee) writes:
]I'm using INT 1CH to install a clock on my screen. Problem is that
]it works when it wants to. 
]
]The problematic part of the code (at least I think that this might be
]it) is:
]
] ....
] GetIntVec($1C, Int1C);
] SetIntVec($1C, @ClockProcedure); {call ClockProcedure ~ 18 time/sec}
] ....

* I know this is already obvious, but make sure that you used the
  "interrupt" directive on ClockProcedure.  This will assure that
  ClockProcedure will use IRET instead of RET.

* Also make sure that you are not using "write" or "writeln" procedures to
  write to the screen, as they may end up using the DOS routines, which are
  not re-entrant.  I might suggest using the BIOS routines instead.

                //-n-\\				Naoto Kimura
        _____---=======---_____			(csun!csuna!abcscnuk)
    ====____\   /.. ..\   /____====
  //         ---\__O__/---         \\	Enterprise... Surrender or we'll
  \_\                             /_/	send back your *&^$% tribbles !!