Xref: news2.mv.net comp.os.msdos.djgpp:7725
From: root AT ursa DOT smsu DOT edu (Tony O'Bryan)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: buffer -> screen transfers
Date: 20 Aug 1996 18:41:05 GMT
Organization: I need to put my ORGANIZATION here.
Lines: 14
Message-ID: <4vd0s1$m76@ursa.smsu.edu>
References: <320647A3 DOT 5827 AT cadvision DOT com> <3209b332 DOT 21898266 AT news DOT wolfe DOT net> <32141C89 DOT 5DB5 AT gbrmpa DOT gov DOT au>
NNTP-Posting-Host: huwawa.smsu.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Leath Muller (leathm AT gbrmpa DOT gov DOT au) wrote:

: If your not in the final development stages of your program, it ends up
: OK to use the farnspoke etc routines because your not too worried about
: speed. What I did, was wait until I knew my routines were debugged fully
: (fully? yeah right... ;) and then used the __crt0_nearptr_enable (or
: similar) flag at the start of my program to disable all memory
: protection.
: This has the advantage of not having to call the enable/disable calls
: all the time, and increases the speed of video intensive subroutines a
: LOT!

Will __crt0_nearptr_enable allow a pointer to linear address 0xa0000 to
directly access the video screen?