Posted by tbone on 05/06/06 19:57

I just had it happen recently.

The resets were due to some crappy trial software I installed
(Save-n-Sync); after deinstalling, system is stable again. However,
after the second BSOD, WinMX's settings file got whacked. I had to
reset many of the core settings, but things like the library and the
list of opennap servers was ok.

I suspect WinMX was writing to some settings file when the system died
and left that file in a bad state. On restart, WinMX couldn't make
sense of the file, so it ignored it and went into "initial setup
wizard" mode.

Hasn't happened since.

HTH
tbone

BTW, I now back up all WinMX settings files in case this happens
again.

On Fri, 5 May 2006 03:22:20 -0400, "No One" <NoOne@123.com> wrote:

>Last week WinMX got terminated -- yes got . . . My system was re-booted and
>all the settings in Win MX were set to some default that wouldn't work.
>Haven't been on in about a week, when I cranked it up tonight is when I
>found that all the settings were changed, fixed it, went to sleep. Woke up,
>checked, same thing. systems was re-booted, all the settings were changed
>so that it wouldn't connect. Any ideas of what is going on???
>
>Primary to secondary
>Incoming TCP to "Unable"
>in/Out UDP Packet to "Unable"
>Search parameters changed to default
>File transfer rates changed to some default
>File transfer incoming folder changed to some default
>Download/Upload amounts changed to some default
>Bandwidth throttle unchecked and numbers set to 15000
>
--
NewsGuy.Com 30Gb $9.95 Carry Forward and On Demand Bandwidth

[Back to original message]