harrison@ucsfcgl.UUCP (Peter Harrison%MIS) (10/12/84)
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? Peter Harrison (415)921-5060 ARPA: ucsfcgl!harrison@berkeley.arpa UUCP: ucbvax!ucsfmis!harrison
jsoc@lasspvax.UUCP (John Socha) (11/27/84)
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.