I got a copy og UPX and unpacked AltBinz 0.31.2 (the expanded executable still started up ok with the -mi flag, so it was a relatively valid unpack). I then used an old copy of 'strings' (from MKS 4.2e), which pulls out all ASCII text 'strings' of 4 or more characters in length. The following group of strings were found in the output:
Exception
Idle
\exceptions.log
XPAT
Alt.Binz
Paused
- Paused
Paused - Alt.Binz
Alt.Binz
XPAT
CONN
Idle
on connectbutton
on updatetree2
on checkthrottling
on abortxp
on calculating download speed
on updatefinlist
on updatexplist
on updatelog
already exists.
Skiping file.
This leads me to believe that AltBinz did create that file and insert the messages. I got another AltBinz lockup today, but there were no new messages in 'exceptions.log'. [I have renamed the old log file now, in case AltBinz won't append to an existing file (although the 4 messages indicate it will)]. About the only thing I find in common with the lockups is I am loading down the machine (Process Explorer v11.33 shows CPU usage over 75%). It can be things like copying large files across the local network (both computers with Gigabit NICs), calculating or correcting downloads with QuickPar v0.9.1, running Xnews v5.04.25 with a large XOVER download and the attendant '(Re)Thread articles'. I try to not do more than one of those operations at the same time since that will saturate the CPU. There is not much I can do about the 'calculating of download speed', <grin>, except replace the slow (power miser) machine with the faster (power hungry) machine; that defeats the whole reason for using a low power 24/7 machine.
Back to the question at hand- what else can I do to track down this lockup problem?
Thanks again.
