Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!pt.cs.cmu.edu!dsl.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: LMI Forth(s)
Message-ID: <1881.UUL1.3#5129@willett.pgh.pa.us>
Date: 21 Oct 90 01:58:26 GMT
Organization: String, Scotch tape, and Paperclips.  (in Pgh, PA)
Lines: 18


   To: ALL                           Refer#: NONE
 From: RAY DUNCAN                      Read: (N/A)
 Subj: 80836 UR/F INTERRUPTS         Status: PUBLIC MESSAGE
 If you are going to service interrupts in a 80386 UR/FORTH application,
 you should LOCK DOWN the pages that contain the handlers in order to
 avoid a page fault at interrupt time.  If you are going to execute HIGH
 LEVEL Forth code during the execution of an interrupt, then you should
 lock down the entire code and data segment up to HERE to eliminate the
 possiblity of a page fault.  Page locking requires a direct call to the
 Phar Lap DOS Extender interface via the INT86 word.  If you need further
 information on the page locking function, we can FAX you the appropriate
 pages from the Phar Lap DOS Extender manual.

 NET/Mail : LMI Forth Board, Los Angeles, CA (213) 306-3530             
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: dwp@willett.pgh.pa.us or uunet!willett!dwp