Getting better with V3.54 & 4th .dll patch. Some tips

[wavoka]

I've been playing with this thing since it came out. I keep task manager open while it's running and monitor CPU usage closely. I've had it running for up to 7 hours without a crash.

What I've found is I HAD a few incomplere files that were at low d/l or 0 d/l that seemed to peg out CPU usage at 100% and hold it there, bouncing between 97% and 100%, at which point 3.54 crashed.

I'm slowly going through files, taking mental notes as to which ones seem to cause spikes. If they cause the program to crash - they're no good to me anyway, so I delete them. They're in my recycle bin if I want to try them again.

If I get a ceash after restoring a file, OUT IT GOES for good.

The good news it that I'm getting some good upload/downloads and all functions seem to be working. It just looks like we're going to have to go at this from both ends.

A tip to the programmers: I don't know if this helps or not. Before the event, if I got a bad incomplete, it'd peg out explorer.exe and freeze Winmx. I could use task manager to kill explorer.exe and then reload it and WinMx would free up and run fine. With ver 3.54 and 4th .dll, it pegs out WinMx and crashes it.

THe trick seems to be to take the time to track down bad incompletes.  Could someone be placing fake files on the network that are designed to peg out the .dlls at 100%?

[NaNashi]

THe trick seems to be to take the time to track down bad incompletes.  Could someone be placing fake files on the network that are designed to peg out the .dlls at 100%?

Maybe yes.  Maybe no.

I have never had problems with fake files and I very, very, very rarely have WinMX crash.

The trick is that all the files I download are Japanese files from Japanese users in Japanese.  Basically no U.S. organisation gives a toss about the files I want.  

If you really want to be sure that the files are bad and will _always_ crash WinMX then you could give them to another WinMX user (with their consent) to see if  they cause problems with _their_ computer.

[Me Here]

Thank you both for your usefull observations..

Wavoka:

I dont think that in this time frame the files could have been widely spread enough to do any damage so I suspect they arent planted no.  However, your concerns and observations are being well noted.. ty

Let me know..

[wavoka]

Thank you both for your usefull observations..

Wavoka:

I dont think that in this time frame the files could have been widely spread enough to do any damage so I suspect they arent planted no. However, your concerns and observations are being well noted.. ty

Let me know..
======================
They're all new files from right before and right after the event.

It could just be that the new .dll reacts differently that the old WinMx did.

[KM]

did you confirm any specific files as problematic? and did you keep any of them so someone else can test and have a look?