First let me say that as many here know this isn't my first patch rodeo so to speak. We have been through a few of these and never in our history has a release been so problem free as this. Its refreshing and well, at first was a bit scary, but now just a wonderful thing to see so few problems.
Now of course there have been some reports of some minor issues and I'd like to cover those here and the respective cures we've found.1)
The first is an actual bug that was discovered with users on RCMS. Symptom:
Users with RCMS installed were seeing multiple listings in the chat user list of the same user. Everytime a user left and re entered the lists contained both user names.Cause:
The WinMX Community Patch has code in it, to handle a bug known in WinMX, where by a redirect in a certain condition could cause WinMX to crash. RCMS was unable to handle the style in which the Community Patch handed the data to it, there for caused the information to be lost that a user was to be removed from the user list.Cure:
Eagle made a special version of the dll for RCMS users where by the protective code has been disabled. Because he reason for the code to be in place is for protection of a known issue, he decided a general disabling would be determental, so for RCMS users experiencing this issue there is a special download available from all download mirror sites.
The rest of this list is problems that users noticed after updating to the WinMX Community Patch.2)
Problems with ports.A--
UPnP auto forwarding, caused conflict with manually opened port rules.Symptom:
Although most routers that have uPnP ability, can have ports set both ways, some do not allow the identical port numbers to be used for both, thus causing a conflict between rules in the router.Cure:
Use one or the other method. If you previously had ports set up in your Modem/Routers, then disable the uPnP in the patch, go to your Program Files\WinMX folder. Locate the file named 'oledlg.ini' and open this with notepad. Find the line that says '/enableupnp 1
' change this '1' to '0
' to disable upnp, save the file and close. Recheck your manual rules are still in place, and restart WinMX.B--
UPnP not working.Symptom:
Even though some routers have an option for uPnP in the configuration interface, some ISP issued Modem/Routers have this feature disabled. We found a small amount of users were simply unable to use this feature regardless of enabling it or not, due to the ISP disabling it in the firmware.Cure:
Manually forward your ports instead or use Passive Secondary mode in WinMX.C--
Ports not working, or settings changed in WinMX due to non default installation of WinMX previously.Symptom:
Having to run through the set up wizard, even though you already had WiNMX installed. Loosing settings like favorites, port settings, and rebuilding of library, among other settings. More then one 'shortcut' for WinMX on desktop or start menu.Cure:
Do a Search for your previous WinMX installation, by searching the machine for say 'winmx.exe
' files or 'settings.dat
' files. Find the location of the previous install, copy your settings.dat & lib4.dat or library.dat files into the proper new installation folder, remove the old files/folder and shortcut. This should reset your ports and library to what it was previously.D--
Set up Wizard runs, or reinstall of MX when starting.Symptom:
The WinMX set up wizard runs through the installation process with you, when you restart your WinMX. This is actually not an uncommon thing if you have a computer crash or sudden shut down of WinMX, however this cure is for users with MXMonitor running on a different drive then WinMX is located. The WinMX Community Patch looks for winmx.exe when it starts and if it doesn't find this file, it assumes that you have used MXMonitor to start MX. If the two are on different drives like say C:\Program Files\WinMX
It confuses the the patch file, and has caused at least one person to go through the set up wizard on start up of MX via MxMonitor.Cure:
Close both WinMX and MxMonitor down, Move the entire MxMonitor folder and its contents to the same Drive and Folder as WinMX is located (default is C:\Program Files ).
You may also need to re make your desktop short cuts as the path for MxMoni will have changed, once the MxMonitor folder is moved, Go to the desk top and delete the current shortcut for MxMonitor. Open the MxMonitor folder you moved, Right click on the mxmonitor.exe file and choose 'Send to...' then choose Desktop Create Shortcut.3)
Problems with Connection.A--
No Network connection after update, flashing yellow.Symptom:
Updated WinMX or the patch and no longer can connect, getting flashing yellow.Cure:
Quite often this is because a firewall program installed has blocked the connection, they are designed to protect against changes made within a program so that it can not be hijacked as a trojan. Go to the firewall settings, remove WinMX, close WinMX, and restart. When the firewall asks say Yes to allow it full access.B--
Using the 'patch only' download and dropping it into your existing WinMX folder.Symptom:
Various things from old patches still in place to old registry entries in place.
We as regular MX users are well trained in the art of updating MX, and in the past this site has always carried a 'patch only' with installer, this is no longer the case and we are seeing lots of users with various issues because they grabbed the 'dll only' file available for linux users. Cure:
Please if you have done this and are having 'ANY
' issues with your WinMX, go back to the download site http://patch.winmxconex.com
and get one of the installers for your WinMX Version. I can not stress enough how important it is to let the installer do what it is designed to do for you, that is remove old patches, remove/fix old registry entries, check your WinMX install locations, check for things like Peerguardian or PGLite, remove hosts file entries from all groups and will not alter your WinMX in any way if you have it installed already. The installers are
the patch only solution for you.4)
Problem with Installer.Symptom:
Installer fails or stops and doesnt finish installation.Cure:
Download the installer of the WinMX Version you use now, and 'save
' it to your machine, in a location you can find. Do NOT
run the installer from the download dialoge box, this causes it to need to run from the 'Temp' folder which is not ideal.
There has been one report of increased CPU and a que clearing issue that turned out to be a MxMonitor setting, and a issue with room droppage since the update by one user, however, that has always been a problem for hosts and most report less droppage with this WinMX Community Patch, so that doesn't warrant making it to this list.
As you can see from my list really very minor issues if any and those that are having issues, the root cause is usually down to something on the system that needs adjustments. There are well over 100,000+ users now on this new patch, and most are finding the update pain free and problem free. A note for those that haven't updated yet.
Please if you have been waiting to update to let others make sure its ok first, take this as a sign its ok. Remember the patch update is important because it fixes some major issues of connecting for secondary users and for third party software like bots or servers, that affect the entire network. As long as you or others keep using older patches this problem will persist for users of that software, even if your not one of them you could still be causing problems.
If any one has any questions about this post or the information contained in it please just ask.