need SETI help

[Baldy18]

Ok I've done this before but I can't remember how. I need to make it so that windows 98/ME doesn't check if any programs are running before it shuts down. I know you have to edit some file and I have done it before but I can't remember which file or how to change it.

I also have one other more difficult problem. I can't put a shortcut to setilog in the startup folder under windows 2000 because it really dogs the computer. I had the same problem with just this one computer under windows me. I have tried just manually starting setilog after startup but I have to start it up and shut it down several times before I get it to run without slowing the computer (and by slowing I mean real slow like it doesn't seem like it is doing anything unless you look at it for one second each week). I would like to be able to just put the shortcut in the startup folder and forget about it. Anyone have any ideas.

 

[ColinP]

I think you do it with conagent.exe

But I don't know the details...


cheers,

Col

 

[Wiz]

Get Default.zip from the seti driver page.
Here is the page that comes from.

Don't know on part 2, sorry.

 

[Smoke]

Sounds like you may be running SetiDriver with the Seti Client Priority set higher than LOW. Make sure it is set to the lowest priority. Are you using SetiDriver?

I noticed my computers seem to slow when I place the priority even in the Normal Mode.

Hope this helps.

 

[Sukhoi]

Yes, just edit the properties for conagent.exe and tell it not to warn if still active...those properties apply to all DOS type programs.

Yeah, it sounds like you're trying to run it higher than low priority.

 

[Baldy18]

Thanks for the help with the win98/me problem that is exactly what I was looking for.

As far as the other problem goes I am just running setilog and connecting to another computer on the network that runs setiq (no setidriver or setispy or anything else). I have the priority for the CLI on the lowest setting and the priority for setilog on the default of normal, although I have tried stepping that down a notch without success.

Is anyone else experiencing this problem?

 

[Sukhoi]

How much RAM does that computer have? Does the DNet client react the same way?

 

[Wiz]

ok, the slowdown may be due to setilog trying to make the network connection. Win98/me boxes can be stupid about this. I've noticed it a lot. NT and 2K are like lightning when connecting to each other but 98/me tend to 'forget' and take 'time outs'.
Hope this helps somehow.

 

[Baldy18]

My computer has 256MB of RAM and it is running Windows 2000, however, the computer that it connects to that is running setiq is running 98SE.

When it locks up and I am finally able to get the task manager up it says that the CLI client is using 99% of system resources. I am thinking that it has something to do with seti starting before the OS loads fully since the problem only occurs at startup and shortly after (although I have never heard of anyone else having this problem.

[EDIT] I haven't tried the DNet client since I don't know how to work it.

 

[Wiz]

I have a similar setup and although making connections between my Win2K machines is pretty much instant on startup doing it from my 2K to my 98SE boxes takes a horribly long time and consumes all resources.
Seti will always sit there saying it has 99% cpu time, that's perfectly normal and is not the cause of your problem.
Your problem is that you are asking it to make this network connection and it has to go through a stupid lame assed MS timeout period for some God forsaken reason.
(I live 19 miles from the Redmond WA campus of MS, I know buttloads of people who work there and have worked there forever, they confirm to me what I said above is true)
(you might notice this kind of lazy MS crap really pisses me off) /rant

Now, what can you do about it?
Get that thing out of your start up folder.
Don't restart your machine so often.
Set up a path to your 98SE box by mapping a network drive to it, then it might remember the path and not give you such a hard time every time you want to re establish it.
Start setilog manually after your machine is started.

As always, I may be full of **it on some of the above, but I have felt this pain and so I might be allowed to be a bit emotional about it. YMMV

 

[Baldy18]

Wiz I think that you are right on this one. Do you think that it would help if I moved setiq to my win2k machine or would my 98 boxes have trouble connecting to it?

 

[Wiz]

My experience is as long as the 98 box has connection rights the flow that direction goes pretty fast. It's connecting to the 98 box from 2K that sucks. Of course not with all machines every time, no it couldn't be consistent.
So, yes that's worth a try.
(do you sense any pent up hostility toward our favorite OS maker here?)