Question about SETISpy and Command Line Client

[Fardringle]

I have been using the GUI version 3.0 for a while on one of my machines, and it was set up so that when each WU was completed, the client would automatically dial the Internet (using a modem) and get a new WU, then disconnect the DUN connection after being IDLE. This worked quite well, but after hearing that the Command Line version of the client would be faster, I decided to try using it instead, and have SETISpy monitor the progress for me. I AM getting better times (about 11 hours instead of 12-13) but it looks like I may have to change a setting somewhere, and I'm hoping that you guys can help me find it.

The problem is that when the CL client finishes a Work Unit, it tries to dial the Internet, but it gets a message saying that another application is already using the modem, and that I will have to close this application first. The computer then has to be rebooted to release the modem from whatever is using it before it can be dialed again. Any ideas what could be causing this, and what I can do to fix it? Thanks!

 

[Fardringle]

Bump.

 

[blade47]

What OS are you running? I know in win95 you have to do something to get the cli to work right with the dun.

Sorry I'm not much help.

 

[Fardringle]

Yep, it is Windows95. Any idea what I need to do to make it work?

 

[blade47]

Sorry, I'm not really sure.

If you change the title of your thread maybe someone who knows will drop by and let you know.

I know for certain I read something about it over at Ars awhile back. BTW Poof knows what you need to do.

 

[Assimilator1]

Its the winsock 2 update your thinking of ,but if it worked with v2.xx then that update has already been done.

Do you have a task manager to see what process is holding the modem?

 

[JWMiddleton]

Hi Fardringle,

Have you considered running SetiQ? I run it on Win98SE and it works great! What I really like is that it only dials once each day, rather than every time a WU is completed. You specify the HOUR at which it is to dial, so that it can dial while you are sleeping and not have a problem when you are using you phone. I keep a 4-day cache so that I don't have to worry if I am not able to get into the S@H server.

 

[Fardringle]

Assimilator: The Task Manager doesn't show what process is using the modem, just that Rnaapp (DUN) is active even though there is not an active connection. I may have to try and find that WinSock2 Update for Win95..


Using SetiQ may be an option if I can set it to create a cache, but then have it dial and 'dump' the results of the cache whenever I want it to (when I am actually near the computer..) as well as have the scheduled time. However, would this solve the problem of the DUN conflict I am already having with SETI Spy?

 

[Sukhoi]

<< Using SetiQ may be an option if I can set it to create a cache, but then have it dial and 'dump' the results of the cache whenever I want it to (when I am actually near the computer..) as well as have the scheduled time. However, would this solve the problem of the DUN conflict I am already having with SETI Spy? >>



I don't know about your modem problem, but yes, you can have SETIQ fetch/flush WUs at a scheduled time, and when you're at the computer (by running a special shortcut).

 

[Assimilator1]

Fradingle

Does it auto connect OK if SETI spy is off? (it also connects to the net)

 

[artemedes]

I know this doesn't really answer your ?, but I am with JW on this one. I would try SetiQ, It dials out automatically for me just fine. I also run a 4 day cache, but you don't have to. You could just have it cache 2 work units for you. Nice thing about that is for some reason you can't connect (busy signal) or internet server goes down you machine can still work away.

 

[Fardringle]

After all of your great suggestions, it turns out it was something simple...

I have voice messaging on my phone line, and the modem is set to check for a dial tone before dialing (I use this so I can tell when I have messages) and there happened to be some messages so the client wasn't able to dial the modem, and the &quot;there is no dial tone&quot; message had closed itself, but hadn't released the DUN connection to the modem.

I HATE it when the simple stuff is so hard to find! (I only figured this out when I happened to be sitting next to the computer when it happened again, so I saw what it was trying to do..)

Guess I'll just have to disable that 'wait for dial tone' option.