Regarding the dll file at http://winmxgroup.com

[Vladd44]

While there is nothing wrong with the patch in itself.

It erases any replacement hosts file with the default, negating the effects of any hosts file updates you may have done to date.

It also blocks specific IP addresses. While I happen to trust the person in charge of doing this, I do not like this feature.

For me this is a classic power struggle, of which I do not care to be a part of.

The new hostfile released by Sabre and co includes KM's peer cache servers, but KM's dll excludes your ability to use Sabres servers. this is something I do not like.

[CoalDust]

Thank you for allowing me to clear up some of the questions your post has posed Vladd .

The hosts file is not so much erased as restored to its normal state.
Obviously if you use the Winmxgroup patch it is no longer necessary to have a modified host file.

As to the block list, I have a personal interest in the blocklist being used as it is my own. I wish to assure you all that no one will be blocked who is not a recording industry flooder.

Also I would like to clear up a minor mistake on what you have said.
The winmxgroup patch does in fact check all the peer cache servers that are currently deployed.
There are 2 good reasons for doing this

1) The primaries are all on the same network and not some smaller mini WPN as could occur.

2) It makes sense to spread the load evenly amongst them.


Aside from the obvious point of if you wish to block the flooders (this is an all in one soloution), it also allows rapid updating of the peer cache addressing and that was one of the primary design features.


For those that are using Windows 9.x series operating systems a problem has been identified and KM is looking into a solution.

A warning notice is posted on the winmxgroup site stating the following

If you have BendMX or RCMS then DO NOT replace BendMX/RCMS with this patch or it will replace BenxMD/RCMS! Instead replace the file named WS2_32o.dll

Users of WinMX 3.53 using the "olepro32.dll" channel list patch, some users have reported conflicts beteen the 2 patches (while a couple have said it works fine). If you do suffer problems then try removing the "olepro32.dll" patch.

There are no other issues that I am aware of, but the situation is that if you are using the host patch and all is fine then continue using it and please try to get the updates with the newer addresses in it when they are availabe.

As many of you are aware KM is doing his best to make things as simple as possible for users by combining all the functions into a simple drop in file, and innovate at the same time, but even he agreed that his purpose behind making this file was to keep the network together and operating well.
There is no malicous intent folks and he has rapidly signed up to operation pie along with many other good people.


Many thanks to Vladd for allowing me to tactfully explain this issue that is causing unecessary friction and alarm. Cheer Vladd

[Vladd44]

Anytime CoalDust,

I never want to control debate, just wanted to keep this area more confined.

And I will have to take careful reconsideration at the issues you addressed.

I think the last thing we need as a community is to be at each others throats.

[Vladd44]

As long as all other peer caches available are used I will retract what I have said.

I still have my concerns about conflicts, and ofc I dont like anyone but my deciding what ips are blocked from my computer. But I do happen to trust the person in charge of doing so.

SO if people want to run this patch, and they get connected with it, it can be a useful way for people to do so. And most likely less intimidating than some of the other options.