I'm using the SETI CLI 3.03/Driver/Spy combo on all my computers & SETI Gate for a WU cache for all systems.
I use the v3.08 client on my Win XP computer to process VLAR WU's, anything less than 0.100 AR. So since i've only been recieving them occasonally, when one comes along i grab it with Driver out of my SETI Gate cache of WU's. Then i let it process till it's done. Usually there isn't another VLAR one to process, so i set the cache size in Driver to '0' & upload it to SETI Gate. Problem is that it won't get logged into the SETI Spy log.
Does anyone know, when in the process the WU info gets logged into the Spy log?
As far as i can tell, the only way to get the WU info to log in Spy is to keep the finished WU in Driver(i/e- my SETI v3.08 folder) till another VLAR WU is available to process.
This isn't a huge deal, it's just nice to keep the log info.
I use the v3.08 client on my Win XP computer to process VLAR WU's, anything less than 0.100 AR. So since i've only been recieving them occasonally, when one comes along i grab it with Driver out of my SETI Gate cache of WU's. Then i let it process till it's done. Usually there isn't another VLAR one to process, so i set the cache size in Driver to '0' & upload it to SETI Gate. Problem is that it won't get logged into the SETI Spy log.
Does anyone know, when in the process the WU info gets logged into the Spy log?
As far as i can tell, the only way to get the WU info to log in Spy is to keep the finished WU in Driver(i/e- my SETI v3.08 folder) till another VLAR WU is available to process.
This isn't a huge deal, it's just nice to keep the log info.
Facebook
Twitter