Sieve client?!?!

[em99010pepe]

Hi to all,

A week ago I left the sieve client running all night and when I woke up the client was not running giving the usual windows error. Mean temperature of my room is and has been about 15-16 ºC. Until today never had a problem with all DC projects. The computer is 2 months old.
Thursday I restarted with sieving and today, a few minutes ago, the client stopped by itself. I run Norton and Ad-Ware and nothing was detected.
The range did not finish, the current one is 55% completed, and I use the flags -d and -w on the sieve shortcut.

The computer is the server on a LAN.
I have 25 processes running under Windows XP, I checked them all and no one is a virus. I went to registry by using the regedit command and everything is clean.
I will be off all afternoon and I don't know if I should keep the client running so I ask for help.

Thanks in advance,

Carlos

[Mystwalker]

Maybe you could first open a DOS shell and inside that start up proth_sieve. This way, you still have the error message (if there is any) when proth_sieve should quit again. This doesn't happen very often, though. I haven't experienced it so far, using it basically since it was released.

[Citrix]

Carlos,

Your computer might have rebooted turning proth_sieve off and then when it restarted proth_sieve did not start.

Try running proth_sieve again from the point where you think it stopped, by double clicking the program and see if it runs properly or not, if it doesn't then there is a bug with the program, else there might be a problem with the machine itself.

Citrix

[em99010pepe]

Originally Posted by Citrix

Carlos,

Your computer might have rebooted turning proth_sieve off and then when it restarted proth_sieve did not start.

Try running proth_sieve again from the point where you think it stopped, by double clicking the program and see if it runs properly or not, if it doesn't then there is a bug with the program, else there might be a problem with the machine itself.

Citrix

The computer did not reboot by itself. As I said the client just stopped, the DOS window wasn't there! I was studying not in the internet at that moment.

Now the sieve client is running, I restarted it.

I was near the computer when that happened, I was lucky, suppose this happens at night? Let's see tonight.

I really want to get 4th place at sieve but with this problem.....I don't know.
PRP3 is running well on my friend P4 3.0Ghz. 26 numbers tested. No one is prime.

Carlos

[Mystwalker]

Originally Posted by em99010pepe

As I said the client just stopped, the DOS window wasn't there!

That's always the case when you open a command line application by a double-click on its icon and the application eventually quits.
Try it with "cmd" and then starting proth_sieve within this command shell - then you can see error messages.

[VJS]

Does the entire dos box close or does the client simply freeze but the window remains open???

It will stop if you clicked within the window.

I use to leave proth sieve open on my screen. During the night or ??? it was stopping. Turns out my cat was actually laying by the computer on the mouse etc. He would click the mouse within the window.

Sounds weird but it happened more than once.

Guess my cat has something against DC.

[japelprime]

Try to close down some of the 25 processes (applications ) you are running. this could be simble sufficient memory problem. Not enough memory available for sieving.

japelprime.

[em99010pepe]

Guys, I had that problem almost two years ago! Carlos

[ltd]

Originally Posted by VJS

Does the entire dos box close or does the client simply freeze but the window remains open???

It will stop if you clicked within the window.

I use to leave proth sieve open on my screen. During the night or ??? it was stopping. Turns out my cat was actually laying by the computer on the mouse etc. He would click the mouse within the window.

Sounds weird but it happened more than once.

Guess my cat has something against DC.

CMD boxes stopping to work if you click into them has something to do with some windows settings. If you open the properties for a cmd box you will find a tab called options.

There you find under edit options the point:
"Quick edit mode".

If this is enabled a click into the cmd box will freeze the process to enable marking contend of the box for cut and paste by using the mouse.
I have disabled that behaviour for all my cmd boxes as i did stop applications more then onces. If you right click into the window it continues to work

[axn]

Originally Posted by ltd

If this is enabled a click into the cmd box will freeze the process to enable marking contend of the box for cut and paste by using the mouse.
I have disabled that behaviour for all my cmd boxes as i did stop applications more then onces. If you right click into the window it continues to work

The freezing actually happens as soon as the program tries to output something new to the screen (which could be quite a while for the sieve client, so you might not be there to notice it when it happens).

I actually use it to "pause" running programs