From:	chepelov AT rip DOT ens-cachan DOT fr ("Cyrille Chepelov")
Subject:	Re: screen saver
18 Oct 1996 18:06:16 -0700 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199610182221.AAA07586.cygnus.gnu-win32@nemo.rip.ens-cachan.fr>
Reply-To:	<chepelov AT rip DOT ens-cachan DOT fr>
Mime-Version:	1.0
Original-To:	"Oliver Korfmacher" <okorf AT netcs DOT com>, <gnu-win32 AT cygnus DOT com>
X-MSMail-Priority:	Normal
X-Priority:	3
X-Mailer:	Microsoft Internet Mail 4.70.1155
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

hi,

> anybody wrote a screen saver application using cygnus?
> Is it true that such an application (with this screen saver bit
> set) never puts any load on the machine which may affect its
> operation as a server?

Last time I checked, a screen saver was only a standard .exe renamed to
..scr, which creates a full-screen toplevel window, puts itself at priority
class "Idle" and starts playing with graphics. 
There is no "screen saver bit" to be set in the executable. 
Yes, a thread at priority class "idle" will rarely take precedence over a
thread at a higher level (it should in fact never, but murphy's law always
replaces ohm's). However, just put an OpenGL screen saver and benchmark
again your server... you'll be seriously disapointed (perhaps the OpenGL
screen savers <I>don't </I> put themselves at class "idle", or perhaps
something nasty in the GL subsystem hogs the CPU... I don't know... but it
still eats too many cycles for a server).

My preferred screen saver, however, eats 220V AC / 50Hz only when it is
*not* functioning...

good luck


-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -