Some WU stuck on a comp. Will my solution work?

[Dingas]

I have a few work units on a computer on my lan that are completed, and was wondering if I kill seti on my machine and the remote machine, and then copy over the whole setidriver directory, and then start it on this comp, and upload the WU's will it work ok? I just dont wanna take any chances with my WU..
Thanks Folks.

 

[serialb]

It should work if you copy everything, including the 1, 2, 3 etc folders and SETIdriver.cfg, to a new location. By the way, can't you just transmit the WUs from that computer, then kill it?

serialb

 

[Dingas]

that computer cant get onto the internet, however this one i am on is connected to it on my local lan...

 

[IsOs]

I think you can actually run two instances of SETI driver with two separate directories. So if you just share the drive of the computer that does not have internet connection and access the drive from the computer that has internet connection, run SETI driver, you can transmit the workunits.

If your computer that has internet is not powerful enough, you will experience lag and possibly lock up your computer if you run multiple instances of SETI driver. So during the time you merely want to transmit workunits, I suggest you exit the other instance of SETI driver.

 

[ober]

You could also share the SETI Driver folder on the one machine and map a network drive to it from the internet connected machine. Then run SETI Driver across the lan to transmit and process on two machines with a single SETI Driver cache. Note that this configuration isn't as stable as I'd like since I never designed SETI Driver to work this way.

As to your original option, copy the following files:

SETI Driver.*
SETI*.exe
SETI Spy.log if you are using SETISpy to monitor progrss
SETIWatch.csv if you are using SETIWatch to monitor progress

All the Numbered WU folders in their entirity. You can get four WU folders on a 1.44Mb floppy.

Mike.

 

[Dingas]

Oh, yes.. forgot to say this, but it worked fine.. i just copied c:/seti folder.. and transmitted, and now there cruching along again...