Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!news.nd.edu!shillelagh.cse.nd.edu!flynn
From: flynn@shillelagh.cse.nd.edu (Patrick J. Flynn)
Newsgroups: comp.sys.next
Subject: Those offscreen pixels (Was Horz scan rates)
Message-ID: <1991Apr12.185441.20166@news.nd.edu>
Date: 12 Apr 91 18:54:41 GMT
References: <492@rosie.NeXT.COM>
Sender: news@news.nd.edu (USENET News System)
Reply-To: flynn@cse.nd.edu
Distribution: usa
Organization: Amrcn. Abbrvtn. Soc'ty.
Lines: 22

In article <492@rosie.NeXT.COM>, jgraves@next.com (John Graves) writes:
>
>The file /usr/include/nextdev/video.h defines the number of visible pixels in a 
> horizontal line and the size of a horizontal line in VRAM (1120 and 1152,
> respectively). 
> Similarly, there are 832 visible vertical lines, but physically 910 fit into VRAM.

Hmm.

Script started on Fri Apr 12 14:01:08 1991
1csh>dc
10 k
1120 1152 / 832 910 / * p q
.8888888887
3csh>^D
script done on Fri Apr 12 14:01:53 1991

So what does NextStep do (if anything) with the 1/9 of VRAM that won't fit
on the screen?  I hate to see memory go to waste ;-)

-- 
Patrick J. Flynn, CompSci&Engg, UnivNotreDame, flynn@cse.nd.edu  ('til 7/1)