× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Hooking display file I/O
  • From: "Leif Svalgaard" <leif@xxxxxxxx>
  • Date: Sun, 5 Aug 2001 11:43:17 -0500


----- Original Message -----
From: Joe Pluta <joepluta@PlutaBrothers.com>
To: <MI400@midrange.com>
Sent: Sunday, August 05, 2001 10:57 AM
Subject: Hooking display file I/O


> One of my CFT (Copious Free Time) projects is going to be looking into
> hooking the SEPT for display file I/O.  Has anybody done something like
> this?  Please recognize that I'm an asbolute neophyte, and haven't a clue.
> Is this project bigger than a breadbox?
>
> Joe
>


The way to do this is to monkey with a local copy of SEPT, instead of with
the global system-wide SEPT. The PCO (Process communication obj)
contains a pointer to the SEPT to be used by this process. Changing
that pointer to point to your own copy (which you make with a single
CPYBWP-instruction) requires you to set the tag bit for the pointer.
SST can do that (the "T" flag). If the above is Greek to you, better not mess
with it. BTW, a coming chapter (42?) of my ebook explores this in some
detail.

Leif



+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.