Browse Prior Art Database

Avoiding Slow Print Screen in a Multitasking Environment

IP.com Disclosure Number: IPCOM000038854D
Original Publication Date: 1987-Mar-01
Included in the Prior Art Database: 2005-Feb-01
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Nyfeler, JA: AUTHOR [+2]

Abstract

A method is described for avoiding the slow printing of a screen in a multitasking environment. Personal computer users are accustomed to creating a copy of the screen quickly by pressing the "Prtsc" key. This consistently happens when there is a single application active. However, in a multitasking environment, many applications may be executing at the same time. Because the print screen function runs at a very low priority, other applications will take precedence over this function and cause it to take a long time to execute. This time delay is unappealing to users. Since in a multitasking environment, the "user" process is running at a higher priority than the print screen process, the user process can run any desired program.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 69% of the total text.

Page 1 of 1

Avoiding Slow Print Screen in a Multitasking Environment

A method is described for avoiding the slow printing of a screen in a multitasking environment. Personal computer users are accustomed to creating a copy of the screen quickly by pressing the "Prtsc" key. This consistently happens when there is a single application active. However, in a multitasking environment, many applications may be executing at the same time. Because the print screen function runs at a very low priority, other applications will take precedence over this function and cause it to take a long time to execute. This time delay is unappealing to users. Since in a multitasking environment, the "user" process is running at a higher priority than the print screen process, the user process can run any desired program. With this being the case, there is a need to answer the question as to whether the user process is running (busy). There are methods that are used to determine if the user process is busy. This is done to allow other processes to run if the user process is not busy, and to improve the overall performance of the system. For example, if the user process issues a request to wait for a keystroke, the user process is suspended until a keystroke is available. If, instead of issuing a wait for a keystroke, the user process polls the keyboard buffer, the user process appears to be very busy. Each time a poll is done by the user process, a LOCK is issued on the DOS Function Call. If this lo...