Subject: Re: using CLI minimized
From: "Michael D. Ober" <obermd-.@.-alum-mit-edu-nospam>
Date: 15/04/2004, 21:53
Newsgroups: alt.sci.seti

"f/f george" <george@yourplace.com> wrote in message
news:0mqt70dbdrleemhcm8k867rdj7t1vphd97@4ax.com...
On Thu, 15 Apr 2004 16:47:34 GMT, Joe K <"Joe K"@myhome.computer>
wrote:

  How do I get the the CLI to work minimized at all times.Now I have it
working on a Win XP Pro.In a limited account it works fine.
 SetiSpy turns on in Max position,then seti driver comes on in
minimized position.When it transmits the command prompt window opens in
max position.
 I want SetiSpy and transmit window to open minimized at all times.
 I have setidriver icon hidden at all times.
 Because other people use the computer they have turned off the command
prompt window not knowing what it is.
The way I do it is to minimize it to the tray and then do a right
click and left click "save configuration". That way it comes up
minimized every time.
Also if you uncheck the "display transmit" box in SetiDriver you will
only know it is doing something because the icon changes color. Blue
is normal processing, green is getting a new unit and black is stopped
and waiting for the timeout to try again. The timeout time is set at 6
hours, I think< because Berkeley doesn't want people banging the door
down trying to get in. But I do wish it was adjustable since people
like me use a cache and when the connection is down the timeout to
retry is still 6 hours! Sometimes I manually reset my cable modem and
of course that is when one of machines, I have 14, tries to connect to
the cache.


The icons for SETI Driver are as follows:

Blue Parked (Upright) Telescope - cache full
Yellow Parked Telescope - cache needs transmitting
Green non-parked Telescope - cache transmitting
Red Upside Down Parked Telescope - Out of WUs.

You can see these icons at
http://www.wakeassoc.com/setidriver/gui_interface.htm

The 6 hour timeout was inserted at the request of Berkeley
(http://setiathome.ssl.berkeley.edu/unix.html) as you suspected.  The actual
processing of transmits is as follows
On any of the following events, start the transmit process:
    6 hour timer expires
    A WU completes and "Auto Transmit" is checked
    The user requests a Transmit

Scan the cache from top to bottom transmitting as needed
If there are any errors during transmit, set a 6 hour timer

Also, have you looked at the SETISpy FAQ
(http://cox-internet.com/setispy/faq.htm#2.13).  Instructions for using SETI
Driver as the "client" for SETISpy are here.

Mike Ober.