• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New Version of SETIQ ,v2.0 out

Assimilator1

Elite Member
Just went browsing to the SETIQ site & spotted yet another new version of SETIQ 🙂 ,at least 1 of the major 3rd party SETI addons hasn't quitt!😛

Here's the revision notes

2.0 Hang up on client when passthrough operation connection fails (before the connection would just sit until the client hung it up).
2.0 Handle "lookup user" requests locally if possible (without performing a passthrough)
2.0 Changed client obsolete code to check last connection time in addition to checks currently performed.
2.0 Remove AR from batch delete tool (people where abusing it)
2.0 Added LoopBackIp to setiq.ini for those whom don't want to use 127.0.0.1
2.0 Hangup on certain mal-formed client requests instead of treating them as passthroughs.
2.0 Added user-priority setting. New users default to low-priority. New global "low priority max queue size" setting. See: Which Queue for more information on queue priorities.
2.0 Change 'x' close window to minimize (you now need to select exit of the right-click popup menu to exit the app)
2.0 Fixed right-click popup menu options to be more sensible
2.0 Fixed Shc to let go of last queue before waiting
2.0 Fixed empty queue waiting bug (where waiting client would not be given a WU after it was downloaded)
2.0 Added remove client admin tool
2.0 Improved logging. Better viewing options, miscellaneous small changes to recorded information, added client/server/and queue log page viewing options.


Download SETIQ v2.0 here
 
Thanks for the heads up! 🙂

It looks like it might have fixed some problems at OK's proxy... All the result flushed last night! 🙂
 
The only thing I don't like about this update is that there is now a "_" button and a "x" button and they both do the same thing.
rolleye.gif
 


<< The only thing I don't like about this update is that there is now a "_" button and a "x" button and they both do the same thing.
rolleye.gif
>>



I actually like programs like SetiQ to do that, cos it means that i don't close it by accident! 🙂

Thanks for the heads up Assim 🙂

Will i have to reinstall it as a service, or will it detect it from before....me goes to see 🙂

ConfusedBW
 
2.0 Remove AR from batch delete tool (people where abusing it)

You know, what's interesting is that I never even knew this ability was there! :Q I have linux clients where VLAR WUs are routed to and the rest of my machines run what they get 'cause there's no way I can monitor 15 machines with only 2 monitors and a 4-port KVM (so most of the machines run headless)... 😛 But I didn't know you could delete batches of a specific AR range. :Q

Thanks for the heads up Assimilator1! 🙂
 


<<

<< The only thing I don't like about this update is that there is now a "_" button and a "x" button and they both do the same thing.
rolleye.gif
>>



I actually like programs like SetiQ to do that, cos it means that i don't close it by accident! 🙂

Thanks for the heads up Assim 🙂

Will i have to reinstall it as a service, or will it detect it from before....me goes to see 🙂

ConfusedBW
>>

All I had to do was stop setiqueue service, install new version, and start setiqueue service again. 😉
 
Poof
I guess you could use an old version of SETIQ to retain the AR specfic delete ,though I don't agree it should of ever been there in the 1st place!.
Like you do ,the best way to deal with them is to route them to a non Win9x OS.🙂
I'm gonna have Win2k soon ,can I route WU's to that?
 
I guess you could use an old version of SETIQ to retain the AR specfic delete ,though I don't agree it should of ever been there in the 1st place!

As I said, I didn't even know it was there! :Q I know that Setiqueue is very very configurable, but I just haven't had chance to even bother with all that. My heart is still with the original text version of Setiqueue! 😀

Like you do ,the best way to deal with them is to route them to a non Win9x OS.
I'm gonna have Win2k soon ,can I route WU's to that?


I believe it does do that as part of the routing of VLARs - ie., it'll shunt these to NT/2K (which comes up as "NT4" or "NT5" in a results file). It even does this when I run the CLI in WINE since I run it with the "-nt40" parameter. Thus it moves those away from the 98SE machine that I have running the CLI, and to the linux machine running WINE + CLI.
 
I'd like to upgrade, but since things seem to be going so well here, I'm hesitant to try. Is it really just as easy to stop SetiQ, install the new version and restart it? It will keep all the old settings for me?

Funny thing is, I'd feel more comfortable upgrading an OS before upgrading SetiQ! 😉:Q
 
Yes if you enable VLAR routing it will send all VLARs to Windows NT/2K/XP and Linux boxes if any clients are of that type. I have 3 2K/XP boxes and my 98 boxes haven't seen a VLAR since I enabled routing.

I tried to delete WUs by date and by AR before but it never worked for me. I guess I'm just too stupid to figure it out. I also agree that deleting by AR should have never been an option.
 
IndyJaws,

To avoid complications, make sure you terminate SETIQueue program/service before you replace your SETIQueue executables.

Assim1,

Nice to see you posting around here again, but.... don't you have a queen to serve? 😛
 
serialb
yeah ,but I'm on holiday so I can do both 😉
At the end of March I'll have 2weeks holiday so I'll be around more then too🙂

OK
Maybe but I posted 1st about it 😛😉

Steell
Dunno ,but maybe Poof has?

Poof
Re old text SETIQ ,I know what you mean ,I still prefer the result log it did in many ways.Btw I still have the old Q running on my little bros PC! ,replaced mine & my friends last summer but havent got around to changing his ,still works fine🙂
 
Back
Top