Assimilated a PIII 800 24/7 for S@H ,but no net connection,need advice

[Assimilator1]

I've finally managed to assimlate the Workshops office PC a PIII 800 which runs 24/7 (was refused permission 2yrs ago,is cool now).

Only trouble is its not connected to the internet ,though he does have a dialup connection to some company internal network which belongs to Lex,I think.
Anyway I decieded I had to bring the WU's,SETIdriver etc on a CD RW ,which I did today so its crunching now.And I plan to bring back the results once a week via some floppies (what a pain!).I have a few questions though.

I remembered that after copying the SETIDriver directory to the HDD to alter the folder atributes & turn off 'read only' ,do I have to do this to every single file? ,alternatively is there a way to stop the file being altered to 'read only' in the 1st place?

Another thing ,I have a copy of the SETIDriver folder on my machine so that I can download the WU's here & upload the results ,do I just need the result.sah files from the works PC when there done?.
On my PC ,is there a way I can deleted the WU's already transferred without it ask me for the email address each time?

Any help would be appreicated! ( & soon it only has 2days worth of WU's atm!)

[update]
Just thought there's probably aload of people who don't know what 'Snekker netting' means

 

[Smoke]

Ass1,

Check out this thread

A pretty good discussion on various ways to handle this.

 

[Confused]

Assmutilator1 (hehe, sorry, couldn't resist it Mark )

To prevent all the file attributes being changed to Read Only, zip them up then unzip onto work's computer. This will mean you won't have to change all the files

As for uploading/downloading new results, i would try to see EXACTLY how many it'll do in a week (and try to make it about the same time each week), copy the results files onto floppy for each one, and delete and replace whole directory with new one on a CD?

This would keep results small enough to transfer to a floppy, but still allow you to keep it going.

That's all i can suggest at the moment mate, without having a good think about it (which is always difficult )

Garry

 

[Assimilator1]

Thanks guys

Re Winzip, I don't know if the work PC has it installed.
That thread has the ticket ,for now I'll do what the Spacehead posted :-

Getting started:
1. On the connected PC, create a SETI folder just for the non-connected PC.
2. Start up SETIDRIVER in that folder, configure the # of WUs to cache, turn off auto-transmit, save config, then initiate transmit, let it download WUs.
3. Shutdown SETIDRIVER, copy all of SETI folder and subfolders to zip or CD-ROM,
4. take ZIP or CD-ROM to non-connected PC.
5. Copy the SETI folder and subfolders to the hard drive.
6. right click on the folder and change attributes
7. Start SETIDRIVER. Turn off auto-transmit. Save configuration.

Once WUs are completed on non-connected PC:
1. On non-connected PC, stop SETIDRIVER, move SETI subfolders (1,2,3,4,etc..) to ZIP drive or CD-RW
2. Take to connected PC, copy/move SETIsubfolders to the SETI folder on the hard drive.
3. right click on the folder and change attributes
4. Startup SETIDRIVER, transmit completed WUs.
5. Once WUs transmitted, and new WUs filled, move/copy SETI subfolders to ZIP or CD-RW
6. Take to non-connected PC, copy/move subfolders to the SETI folder on hard drive. Start SETIDRIVER.
7. repeat steps 1 through 5.


NOTE: If using CD-RW, be sure to change the properties of the folders/files from READ ONLY after copying them to the hard drive from the CD

However I'll have to use floppies to return the results.Hmm gonna need a few I think!
Btw what about all the .sah files outside of the subfolder ,I assume they belong to the WU in progress?How do I know which subfolder that is?
Also it seems by whats been said that changing the properties on the folder will also change the properties of all files inside ,that's much less hassle.

However I much prefer Mofunks idea ,I didn't realise that SETIHide had an export option ,once I've learnt that proggie I shall switch to that
His post :-
I have been doing something similar to this on my home computers. But I use SetiHide. It has an option to import and export WU's so I dont ever have to get confused with seperate folders. I download a bunch of WU's from my connected computer, then I export say 40 wu's to a folder. I then make 2 zip files with 20 WU's in each (that way I dont have to mess with the file attributes changing) and take them to the non connected PC's. On each PC I unzip them to a folder and then use SetiHide to import the WU's and then I am done! One they are crunched I export, zip, import and flush.

 

[Spacehead]

Read thru the thread Smokeball linked to. Very helpful

If both your home & work computer have CD-RW's then you won't have to worry about the file attributes changing, at least they haven't been for me.
If you only have a CD-ROM on the work computer, well then the attributes will get changed. That's been my experience in this ordeal.

I gathered all the info from that thread & made this instruction set. Works for me!

Getting started:
1. On the connected PC, create a SETI folder just for the non-connected PC. We'll call this SETI #1 for this example. Place a copy of the CLI.exe & SETI Driver in this folder.
2. Turn off the SETI client running on your connected PC. Start up SETIDRIVER in the SETI #1 folder, configure the # of WUs to cache, turn off auto-transmit, save config, then initiate transmit, let it download WUs.
3. Shutdown SETIDRIVER, cut/paste all of SETI #1 folder to zip or CD-RW.
4. Take ZIP or CD-ROM to non-connected PC.
5. Cut/paste the SETI #1 folder to the hard drive.
6. Right click on the folder and change attributes(if needed).
7. Start SETIDRIVER. Turn off auto-transmit. Save configuration.

Once WUs are completed on non-connected PC:
1. On non-connected PC, stop SETIDRIVER, cut/paste the entire SETI #1 folder to ZIP drive or CD-RW.
2. Take to connected PC, cut/paste the entire SETI #1 folder to the hard drive.
3. Right click on the folder and change attributes(if needed).
4. Turn off the SETI client running on your connected PC. Startup SETIDRIVER from SETI #1 folder, transmit completed WUs.
5. Once WUs transmitted, and new WUs filled, cut/paste SETI #1 to ZIP or CD-RW.
6. Take to non-connected PC, cut/paste SETI #1 folder on hard drive. Start SETIDRIVER.
7. repeat steps 1 through 5.


NOTE: If using CD-RW, be sure to change the properties of the folders/files from READ ONLY after copying them to the hard drive from the CD.

 

[Assimilator1]

That's all very well but the work PC has no Zip drive or CDR.I can only use floppy there so I can't take the entire directory

There's another problem I thought of,I don't want to let the client run out of WU's so I'll have to move WU's/results before they are all finshed,would I then have to go through every directory to see which ones are completed? (I assume completed folders will have no WU & will have a result.sah?)

Also how do I know which WU SETIDriver is currently working on?

Thanks so far anyway
Btw I'm just checking out SETIHide atm & its looking good

 

[Smoke]

Also how do I know which WU SETIDriver is currently working on?

Uncheck: HIDE PROCESSING

 

[Ken g6]

If you really want to make an investment in these WUs, you could get a small USB drive.

Edit: Now I see the "work pc" is the PIII. So, yes, the results can fit on a floppy. The results directories have no result_header.sah or work_unit.sah, and do have result.sah.

Also, if you want to get more WUs on a CDR or avoid the read-only bug, you can Winzip them and convert the file to an executable.

 

[Assimilator1]

Smokeball
Doh! ,of course!

Pressumable SETIDriver works on the WU's in sequence? ,so that if SDrv is on WU 10 out of 20 then 1-9 have been completed & 11-20 are yet to be done?

Ken g6
In installing Task info 2000 on it today I discovered that it does indeed have Winzip installed ,so I will be zipping up WU's.

I put taskinfo on there(with permission of course) to see why the heck a PIII 800 was taking 24-30hrs/WU!:Q ,strange thing is taskinfo was showing 97-98% CPU time for SETI despite all the programs running OSR................ I've just thought,I wonder if the HDD's are spinning down overnight?.
The other odd thing is that SETISpy predicts a WU time of around 9hrs with 33% of the WU complete which is a little closer to what it should be,this was at the end of the day when I was checking taskinfo.

Once I have crunched all the WU's I currently have under SETIDriver I will be switching to SETIHide ,makes moving WU's & results much easier

Works PC spec

PIII 800
128Mb RAM
Intel 810 chipset
On board VGA
Win 98SE
CDROM
FDD
NIC
Modem (yeah I could connect to the net using my dialup account ,but I'd be doing that on the companies phone bill!,so best I avoid that route!)

Thanks guys

 

[Confused]

If i remember correctly, SetiDriver will start at 20 and work down to 1.

So if it's on 10, it would have done 11-20 already

99% sure of it

 

[Spacehead]

Assimilator1 wrote:
"I put taskinfo on there(with permission of course) to see why the heck a PIII 800 was taking 24-30hrs/WU! ,strange thing is taskinfo was showing 97-98% CPU time for SETI despite all the programs running OSR................ I've just thought,I wonder if the HDD's are spinning down overnight?."


Is the computer set for power savings overnight?
On my other computer the HD was set to turn off after 1 hour. Just to see, i set it to never turn off & i didn't notice any difference in WU times.

 

[Assimilator1]

I've always thought that as long as their is some program/disk activity that at least the system drive wouldn't spin down.But I have heard otherwise
I have HDD's power down in Win98SE & the system drive never powers down,just set it in Win2k so I'll see what happens to SETI tomorrow

Confused
Wierd!thanks Garry