Problems!

[jlangner]

I keep getting Jobpacket1.dat seems to be corrupted errors. Anyone else? It is on all of my pcs.

[em99010pepe]

I think it's a server problem.

[vaughan]

Try this:

http://www.lifemapper.org/clientservercomm/pipelinemonitorclient/pipelinemonitorclient.aspx

[jlangner]

Thanks - working fine now!

[vaughan]

I've had Lifemapper 1.0.3 crash several times today on a WinXP-Pro box.
I also note that the server is very congested with tasks waiting to be assimilated. I might give something else a try.

[em99010pepe]

I've had Lifemapper 1.0.3 crash several times today on a WinXP-Pro box.
I also note that the server is very congested with tasks waiting to be assimilated. I might give something else a try.

I'm running it with no problems in two machines.

I have this in lifemapper shortcut:

Win Me:

D:\****\lifemapper-i386-win-1.0.03\lifemapper_cmd.exe -p 64 -q -f -c 200

Win XP:

D:\****\lifemapper-i386-win-1.0.03\lifemapper_cmd.exe -p 16384 -q -f -c 200

It is important to use -p 16384 in Win XP.

[vaughan]

Thx I'll try that setting in XP.

[mush_mouth]

You've probably posted this elsewhere but what exactly does "-p 16384 " do on XP? I don't usually use switches; does this speed up or slow down the computation? As you can tell I'm new at this game..

[chaz]

-q: quiet mode (does not give you update messages)
-h: displays usage message
-e <email>: log in to server using <email>
-c <jobs>: always try to keep <jobs> cached locally
-x <proxy>: use specified proxy server
proxy format: http://[user[:password]@]http_proxy_address[:port]/
-p <priority>: set process priority


* Valid priorities under Windows systems:
32: Normal priority
64: Low (idle) priority
128: High priority

On XP and Win2K there are additional priorities:
16384: below normal
32768: above normal

Linux priority value range -20 to 20, -20 being highest priority and 20 lowest

Basically if you dont use the -p 16384 switch with 2k and XP the client will run above normal priority and could make your PC hang.

[mush_mouth]

I have noticed more "not responding" errors than normal with the client running.... thanks for the info.

[chaz]

I've read in the forums many people have problems with version 1.0.03 hanging, personally I use 1.0.02 still and no problems.