Jeff wrote: > Big deal. I have a real beef with screen savers drawing flying Windows, > drawing pipes, or doing other meaningless crud, especially when they are > left turned on overnight. The one that gets me is when you find a *server* running an OpenGL screen saver like the pipes thing. Every time a request comes in for the server, the screen saver will have to be preempted, and the instant that the server is done processing the request, the screen saver will be re-launched and immediately fill up the cpu's cache memory with the screen saver code and the OpenGL library, replacing the server code that is actually doing your work. The next time a request comes in, all of the server code will have to get faulted back into cache again. And people wonder why NT servers are slower than Novell, etc. If your organization uses Windows based file servers, get up right now and go look at their consoles. If you find any animated screen saver running on any of them, either disable it or change it to the simple "blank screen" saver. Instant cpu upgrade. G.