Another big one goes down...

[Baldy18]

Poof- Thats exactly what I'm saying.

 

[ShotgunSteven]

<<

<< What is it with ignorant people in high places smacking down SETI left and right, these days? Bandai, IndyJaws, blcjr.... >>

bandwidth costs money, revolt agenst the telco's! >>



They need to pay flat rate for their bandwidth, not have it based on usage. :| That is the reason I took the somewhat slower DSL up here instead of cable, there are no bandwidth caps.

 

[PieDerro]

It appears as though we have several major problems that must be solved before transporting WUs from a home Q to an offsite Q becomes possible with a CD-ROM or ZIP disks.

Also, thanks Ray for the SETIDriver idea, but the time needed to do that for 50 or more PCs would be just too much (or i might just be a bit too lazy for that )

I think the major problems that have been outlined here, and that I can think of are:

1. Finding the NAMES and LOCATIONS of files that need to be taken from the home SETIQ to the offsite SETIQ.
2. Finding some way of getting a home SETIQ to download the 3000+ (in my case, or much more in the cases of Baz and Indy) WUs to keep a large network fed for a period of a few weeks to a month. There must be some config file SOMEWHERE in the SETIQ directory which would let you make this change.
3. Just thinking, but even a 700MB or 800MB CD would not store that many WUs. Probably in the vicinity of 2800 to 3500. Unless, of course, they can be compressed. (does anyone know if you can zip WU's and how much they zip by?). That COULD be a problem for people having to take 2 CDs worth of WUs with them. (Of course, this would create a massive problem of having to rename ALL the files on the 2nd CD so that they are not the same as the ones on the first CD, based on the fact that they are created with an alpha-numeric order to them by SETIQ)

I just had another random thought. I don't have SETIQ installed on this PC at the moment (i can't get SETIDriver on this PC to connect to it when I don't have a local area network happening). But there is an option in the web-based Tools of SETIQ which allows you to import and export WUs between Q's right? Is there some way that this feature could be used to solve the problems stated in either 1, 2 or 3?

-PieDerro

 

[Jay]

Try This

This is a prog that I think supports not-networked PC's. Just a thought.

 

[Assimilator1]

What about using the old SETIQ to transport WU's? ,moving results & WU's in & out of the old Q is easy ,no renaming needed.
Its easy to get the new Q to grab WU's from the old Q too if needed.
Old Q has to grab directly from SETI though

And yes the old Q does still work ,though it needs the 'host' file fix to get it to connect to the SETI servers

Btw yes WU's & results will compress by a fair amount.

If anyone wants it I still have the old SETIQ available (0.78)

Baz
Hope you can get it sorted

 

[Sukhoi]

Assim, I thought the old SETIQ could use a proxy by putting a line in one of the config files?

 

[Fardringle]

Regardless of the method you use to have the two Queues connect to each other (a laptop that downloads WU's and uploads results at home is an excellent idea) just have the Queue at work act as server for the systems at work, then whenever you have the laptop or other queue at work, just have the permanent work queue fetch and flush to the mobile one. If you don't have a laptop you can use, just put the mobile queue on a hard drive. A 1 or 2 GB hard drive would work for even really big networks. Plug that hard drive into your home computer and run SetiQueue from the drive to fetch and flush what you need from Berkeley (or OK's), take the drive to work and plug it into an available computer and run SetiQueue again there, then have the permanant queue fetch and flush work from the mobile one. Take it home and fetch/flush again, etc.

 

[IndyJaws]

Baz,

I feel your pain.

Indy

 

[zeruty]

if you dont have a laptop bazilla, I wonder if anyone here has an old one they can donate to the cause?

 

[paf077]

WTF IS GOING ON!!!

This is getting really bad :|

First INDY , then Migroo wants to quit and now Baz!

Has someone cursed us in the last 3 days??? :Q

 

[Jeff7]

Winzip reported 24% when I compressed a work unit; went from 348KB to about 260KB.

 

[Assimilator1]

Sukhoi
I'm not sure ,but I think one of the limitations of the old Q was that it could only connect to Berkley servers (whatever their IP is).
I could be wrong but I never heard of anyone getting around it

 

[Sukhoi]

Oh. You should be able to get around that anyway by messing with the HOSTS file if needed.

 

[Assimilator1]

hmm ,maybe ,but I seem to have a vague recollection that the old Q actually 'looked' for Berkely *shrug*

 

[KifArU]

If nothing works out for seti, maybe you can install another program, like Eccp-109.
This uses almost no bandwidth. Just a few kb upload for a completed workunit and no download.

 

[Assimilator1]

Should that ever happen I'd rather go for F@H or G@H

 

[IsOs]

I assumed that they are all networked. Is it possible to add a modem to one of the computer? If so, you can setup a Q in that computer for the rest to fetch workunits from. This Q can be program to dial up at night when no one is using the phoneline.

Unfortunately, at this time, the problem is that connecting to Berkeley is next to impossible.

 

[Assimilator1]

My main Q seems to be able to get WU's & send results ok ,though it took 3.5 hrs this morning (7-10.30 am GMT) to send them all ,multiple retries.
That was only with about 20-25 results though