Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site lasspvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!houxm!vax135!cornell!lasspvax!jsoc
From: jsoc@lasspvax.UUCP (John Socha)
Newsgroups: net.micro.pc
Subject: Re: What bytes control the length of time for scrnsave to blank screen.
Message-ID: <131@lasspvax.UUCP>
Date: Tue, 27-Nov-84 12:36:13 EST
Article-I.D.: lasspvax.131
Posted: Tue Nov 27 12:36:13 1984
Date-Received: Thu, 29-Nov-84 03:25:15 EST
References: <>
Reply-To: jsoc@lasspvax.UUCP (John Socha)
Distribution: net
Organization: Theory Center (Cornell University)
Lines: 23
Summary: 

In article <486> harrison@ucsfcgl.UUCP (Peter Harrison%MIS) writes:

>The distributed version blanks after 3 minutes.  It is not likely that
>burnin will occur in less than hours.  How do I change the time that
>scrnsave will wait before blanking the screen?  

The word that contains the number of clock ticks is at 11FH.

Scrnsave stores a blank-time as a word starting at location 10FH.
For a three minute delay, the old value, you'll see the two bytes
CC 0C.  These are in memory with the lower-order byte first, and
they're clock-ticks.  Since one word can't hold a number larger than
65535, that means you can't program a delay larger than 65535/18.2
seconds, or about 1 hour.

If you know assembly language, you can find the full listing and
a short description of scrnsave.com in my original article, on
page 81 of the December 1983 issue of Softalk for the IBM PC.

	John Socha
	Author of
		Assembly Language Safari for the IBM PC:
		First Explorations -- a new book from Brady.