Tech and Talk > Computing Clubs > Team Starfire > Anyone used SETIHide and had problems??

reply to samburgers

Re: Anyone used SETIHide and had problems??

reply to samburgers
Okay thanx a lot everyone....after I finish this WU I'm gonna give this a try...just hope this would work (knock on wood)... But then again, as klambert mentioned, some machines just wouldn't work with SETI Driver....maybe that's me.....BUT, let's just not even think about that...hehe...;)

Thanx to everyone that responded...I'll post later to tell you guys if it worked or not...
--
CPU idling a lot?? Put it to good use! Join SETI@Home!

reply to Doctor Olds
Hey! I think that it actually worked! :) I set it up as you did in your picture and now I think it's working fine! Thanx a LOT!! So now I just leave it and once it's finished a WU it'll automatically send it in and bring back a new WU? And if the Berkeley site is down I can keep on crunching away? After it's back up, does SETI Driver send it back itself?? Again, Thanx very much!
--
CPU idling a lot?? Put it to good use! Join SETI@Home!

Glad to hear that. Yes, it will send all by itself if you have "Auto Transmit" checked in SETI Spy. After sending, it will also download a new WU to replace the finished one.

How many WU's did you cache? I used 9 as an example, but you may need more or less depending on how fast your system crunches. Usually try to keep 7 to 9 day's worth on your system and you will be fine.

Yes, you will cache and crunch while Berkeley is down (hopefully not often . Also, SETI will restart automatically when you reboot as long as you have a ShortCut to SETI Spy (just SETI Spy, nothing else) in the StartUp folder. I'm glad to have been of help to a fellow Teammate!

Keep on Crunching!!!

Doctor Olds
--
Do not remove this disclaimer under penalty of law; Hand wash only, Tumble dry on low heat; Do not bend, fold, mutilate, or spindle; Your mileage may vary; No substitutions allowed.

Yes, as soon as I saw the 9 in the cached field, I figured that your computer must be very fast and can probably crunch 2-3 WUs a day. So I changed that to 5 (I was thinking about 3) because I only crunch on average about WU a day

Thanx a lot again! :)
--
CPU idling a lot?? Put it to good use! Join SETI@Home!

reply to samburgers
I just downloaded setihide for my standalone machine. I used seti driver to download 30 WU's (3 instances x10 wus) and 7 of them were duplicates...Otherwise, I would have hit 250 yesterday. I just let setihide download 100 WU's which I'll occasionally upload on a manual basis.

I ran setihide before now and didn't have a problem with it. I just prefer seti driver...if only it would allow you to batch more than 10 units in a single session.
--
Give a man a fire, and he is warm for a day. Set a man on fire, and he is warm for the rest of his life.

said by seaquake:

---

I used seti driver to download 30 WU's (3 instances x10 wus) and 7 of them were duplicates...Otherwise, I would have hit 250 yesterday.[edit] I just prefer seti driver...if only it would allow you to batch more than 10 units in a single session.

---

OK...this just isn't my night. Was there a time in the not too distant past when there was a limit of 10? Am I living in an alternative universe now or something....UGH!
--
Give a man a fire, and he is warm for a day. Set a man on fire, and he is warm for the rest of his life.

reply to samburgers
Interesting to see that others are having problems with SetiHide too. I posted a couple weeks back that on my first installations the time for the WUs doubled. I posted the same message on the SetiHide forum (that's actually pretty cool, the creator of the program has his own support forum, and responds pretty quickly) but all I was told was that that's impossible, because it doesn't affect the processing in any way. Um, whatever dude ... but yeah, it does!

The double time has backed off some, but there are at least 3 - 5 hours added per WU. Which is extremely annoying, but it is still worth it to me, because I get to run clients I otherwise wouldn't.

Another problem I noticed on later installations, is that it seems to run flawlessly on newer machines, while getting completely mucked up on older ones. It appears to be completely transparent on PIII-type boxes, starting up and shutting down without incident (there may be hanging on windows exit issue, but I haven't confirmed that SetiHide is the cause yet). On older machines it causes errors galore, and made a complete mess of everything -- I had to delete my whole SETI directory and start over from scratch (WITHOUT SetiHide!!) on 3 different machines.

Today I noticed a possible issue where the log info is suddenly all "-----" except for WU ID and 100% completed, so I'm not sure whether the last 3 WUs counted or not (previous WUs show full logging). Anyone else experience that one?
--
Get your daily dose of wonder from the Astronomy Picture of the Day (APOD).