Strange SETI Driver problem...

[movinslow]

Hi,

I'm using SETI Driver 1.6.4.0 with cmd_line 3.08 under WinXP. Just recently, I cannot transmit WU's. I try, the transmit window comes up, and then disappears a few seconds later without sending or receiving WU's.

Any ideas?
Thanks

 

[PraetorianGuards]

I can't remember exactly movinslow but I think that's happened to me before. Try exiting SETI Driver and terminating the cmd line process and then launch Driver again. If that doesn't work, exit everything then reboot.

XP did that when I hit the power switch and SETI was forced to quit all of a sudden. Rebooting seemed to fix the problem though.

 

[Assimilator1]

I seem to vaguley remember that happening to me too ,I think ,is there a file called something like 'loopdetect.txt' in the SETIDriver folder?

 

[movinslow]

Originally posted by: Assimilator1
I seem to vaguley remember that happening to me too ,I think ,is there a file called something like 'loopdetect.txt' in the SETIDriver folder?

yes, there is, in both of my WU folders. I have the cache currently set at 2.
edit: the filename is "SetiDriverTransmitLoopDetector.txt"

I've tried quitting/rebooting but that didn't help...

 

[Freewolf]

i would delete the seti install and start over with a new install

 

[Coolkid]

Originally posted by: Freewolf
i would delete the seti install and start over with a new install

Probably the best idea 🙂

 

[Soggysocks]

And use the 3.03 cli😉

 

[Soggysocks]

And use the 3.03 cli😉

 

[JBT]

that happend to me the other day when I Was setting up my parents old machine hehe. I was getting p1ssed so I just set up the GUI. I'm using it now again though so maybe I'll try again.

 

[Spacehead]

Sometimes i get those '.txt' files when i change the cache size in SETI Driver. Did you by chance change the cache size?
You can safely delete the '.txt' files. If they reappear, reduce the cache size to "1", let it process a couple of WU's(this kinda clears things out) then adjust the cache to what you want.

Or if you want, just do as others have said & reinstall.

And, yes, the v3.03 client is faster & since you're running XP the fix to the security issue is easily fixed. Read Ken_g6 & OD's posts in this thread.
Link to v3.03 from Berkeley's site: ftp://alien.ssl.berkeley.edu/pub/setiathome-3.03.i386-winnt-cmdline.exe

It's up to you if you want to make the switch.

 

[panhead49]

i have one machine that does the same thing.......running winxp ........no matter what i do ......sometimes i exit seti.....open again......transmit ...no go.....just sits there like yours......i have done everything....delete/ reloaded program.....but to no good......the machine crunchs w/u's good ...just wont transmit.......i gave up and now just floppy them to a diffrent machine to upload results.........if you find a cure ...let me know......😕

 

[BadThad]

It seems sometime the driver.exe gets corrupted or something. I've had it hose up on many machines over the past years. Try downloading new copy's of driver and the CLI, seems to always fix probs for me.

 

[panhead49]

i have tryed new downloads a couple of times ......no go......it seems like seti dosent like that machine.....

 

[movinslow]

Thanks for all the replies. I didn't realize that 3.03 is faster.

I moved the non-function WU folders(3) out of the directory, then was able to receive a new one (cache set to 1). I tried moving the folders back, but they still would not trasmit their results...so, I guess I'll lose the work of three WU's, no big deal I suppose.

I use dialup, and for the non-functioning WU, the connection icon shows activity, but nothing is displayed on the dos window. then the window just closes.

 

[Freewolf]

You could check and see if they have been changed to read only

 

[JBT]

on my Parents XP machine it still just opens then closes in a 2nd it does seems that they are read only for somereason but even changeding them still doesn't do anything grrr. NExt time I go there I will just bring the seti driver from MY machine to see if it is jus ta corrupted file Im dling.

 

[movinslow]

Originally posted by: Freewolf
You could check and see if they have been changed to read only

Interesting. When I select the properties of the WU folders, there is a faint check on 'Read Only.'
However, this is true for both the working and nonworking WUs.

When I unchecked Read Only on the nonworking ones and tried to send them, same thing. No send. 🙁

edit: If I try to uncheck it, it is checked again after I 'Ok' it and look at the properties again. None of the individual files are set to Read Only. Maybe that is the reason for the faint check. The check mark can be faint, bold, or not there.