SCREEN SAVER
Thom;
…for want of a better place to "hang" this. I know that several have
been discussing the problems with CPU intensive blankers… I sorta solved
that problem for myself. I tried several tricks, none of which would work
and then tried launching the blanker from User-Startup. Used Status to
determine which CLI ended up with the blanker and then went back to
User-Startup and added the lines:
"; WARNIN !!!!!!!!!!!!!!!!!!!!!!!!"
"; The following two lines are sequence sensitive"
"run >nil: sys:tools/commodities/blanker.hi CX_POPUP=NO"
"ChangeTaskPri -1 process 3 ;This may change if other changes are made to"
"; any of the startup files !!!!!!!!!!!!!!"
This seems to work. Normally the StarBlanker runs normally but if there is
some TCP/IP activity (or other activity) running in the background, then
the StarBlanker will be a bit erratic. So far, I have not had anytrouble
with any other programs. This may not be terribly elegant nor the best way
to do it, but at least it seems to work.
An Amiga message processed by Whap!,
bill