Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!comp.vuw.ac.nz!csc.canterbury.ac.nz!phys169
From: phys169@csc.canterbury.ac.nz
Newsgroups: comp.lang.pascal
Subject: Re: INT 019h question
Message-ID: <1990Dec7.170745.10136@csc.canterbury.ac.nz>
Date: 7 Dec 90 04:21:25 GMT
References: <25207@adm.brl.mil>
Organization: University of Canterbury, Christchurch, New Zealand
Lines: 16

In article <25207@adm.brl.mil>, C0361@univscvm.csd.scarolina.edu ( Thomas Jenkins) writes:
> ...  All my references say 19h has no
> arguments and if a certain memory location contains 1234h, no memory check
> is done, else a memory check will occur.
>   Now I tried it.  No luck...

Ralf Brown's interrupt list mentions the problem of interrupt vectors being
changed spoiling the reboot. interrupts up to 1C should be returned to
reasonable values (ie. into ROM), esp int 08.

I haven't had much to do with int 19h, but if you're still stuck I can get help
from a friend for you who knows about such things. I also have a list of what
the interrupts should be pointing to on an original IBM, but you probably need
to see what your particulr machine does with them before TSR's take them over. 

Mark Aitchison.


Brought to you by Super Global Mega Corp .com