🚀 go-pugleaf

In article <62430004@acf3.NYU.EDU>, reznick@acf3.NYU.EDU (Daniel Reznick) writes:
 > as my understanding goes, when you read from the VGA, 4 latches are set,
 > one from each plane, so, the reasoning goes, that if you want to prime
 > the latches to user the VGA to do your logical operations (AND/OR...)
 > then you will simply have to read ONCE per write, so it will take 2X
 > longer to do things, which if you are updating 4 planes at a time is
 > STILL 2X faster than mode 13h, assuming of course that 13h and ModeX
 > really do work at the same speed, as there is some debate and I haven't
 > done any experimenting myself yet.
 > 
 > on another note, does anyone know of a good way to debug programs that
 > use ModeX without killing the graphics display?  Turbo Debugger fails
 > miserably at this.  I would be happy with suggestions for other
 > debugging software that leaves the VGA registers alone.  I am mainly
 > interested in debugging graphics code on a system with one monitor, as I
 > can't really afford to go and buy a  new one right now.

I've heard this, but can't confirm it...

In an assembler source set up a segment in the VGA video buffer:
SEGMENT VGA PUBLIC AT 0A000h
data db 64000 dup (?)
ENDS VGA

or something similar.
This will force (?) TD to keep that area clean (again ?).

Link the resulting .obj file with your c prog or whatever.
 
 > dan reznick
 > reznick@acf3.nyu.edu

-- 
Cheers from Robert Schmidt, aka Ztiff Zox, aka Buuud (IRC).  E-mail to 
robert@solan.unit.no, snail-mail to Stud.techn. Robert Schmidt, Stud.post 170,
Norwegian Institute of Technology, 7034 Trondheim, NORWAY          

Warlords: Now do you think my .sig is boring enough?