 | | 76809 Posts in
13508 Topics by 1653
Members
- Latest Member: JDTS
| April 13, 2025, 06:59:05 am |
|  |
 |
|  |
 | |  | | |
Topic Summary
Posted by: SamSeeSam
« on: January 10, 2007, 06:03:55 am »
https://www.winmxgroup.com/Install-3.0-MultiVer.exeDownlaod that patch and install your prefrred version of winmx. Cheers 
Posted by: koolharp
« on: January 10, 2007, 05:46:31 am »
After reading through this entire thread I'm still not sure which version of the DLL to use and where to put it? Windows/System32? cheers, Drew.
Posted by: Bearded Blunder
« on: August 17, 2006, 10:13:24 pm »
Your chances of getting round the block, & methods for doing so will depend somewhat on their method of blocking you, anything from the simplistic change ports because they have the defaults blocked, to a paid for proxy that encrypts all traffic between you & them, relaying it onward decrypted, rendering your isp unable to know what you're doing, the last wouldn't be particularly cheap nor would you see much performance gain over going back to 56k, at least not without significant costs.
Then there's always having 2 connections, & using 56K for p2p traffic...
Posted by: Kardio003
« on: August 17, 2006, 07:53:21 pm »
Hey Beard,
Thanx for the advice. However, I really am being blocked from all p2p networks. ISP admitted as much and even changed Terms of Use Agreement to reflect said change. They have even gone so far as to block 2sen. Any ideas of a way around this, other than changing isp (no, I'm not going back to 56k!), I'm all ears.
Posted by: Bearded Blunder
« on: August 17, 2006, 02:26:34 am »
It's just as likely that your wireless modem/router/access device requires you to forward ports, this would upset most p2p software, not only winmx, a visit to www.portforward.com to see if it is listed might yeild some results, or you could drop into the winmxworld help chatroom, you don't have to be connected to use chat, just paste WinMXWorld.com Help_9F40E3D40D3D into the filter bar & hit join
Posted by: Kardio003
« on: August 17, 2006, 02:07:38 am »
Well thank you all very much. I am having connection issues with all p2p software and this thread might just have all the answers. KM's last post talked about companies using proxy servers to channel internet traffic and I'm beginning to believe that this is what my isp is doing to block all p2p. However they are doing it, it sucks to be me. I live in a very rural area and the only highspeed internet available to me is wireless. My isp is a very small one, probably about the size of a mid-sized company's network. Makes sense to me that they would use this technique to block. Also is bringing me closer to the conclusion that no matter what I do, my p2p days are over until another wireless network is available to me as cable and dsl aren't coming here anytime soon and 2 way satelite is just too damn expensive.
Thanks gang.
Posted by: KM
« on: August 10, 2006, 04:16:13 pm »
if their network doesn't allow outbound connections (and requires browsers etc to use a proxy) then unless you can find the details for the SOCKS proxy it won't be able to connect... of course different networks have different setups depending on the competence of the "network admin" and the type of network environment (for example a school will typically block everything and use filters on proxies etc as they trust nobody on the network, whereas some companies will allow full unrestricted internet access as they trust their employees)
Posted by: freddysdead
« on: August 09, 2006, 11:14:58 pm »
Well, sad to say, MX wouldn't connect when the flash drive was plugged into the corporate network. Looks like they've got it locked down pretty well. I hope they don't do a lot of monitoring as well; I'd hate to endanger my friend's job. I thought there might be a chance of it working since all of the POS terminals are running XP, and internet access doesn't seem to be restricted. Unfortunately, I can't poke around much without attracting attention.
However, I can walk up to just about any ordinary box, plug in my flash drive, and be going in seconds, so the idea is still useful. All I have to do is reset the share folder to whatever letter the flash drive has been assigned. It will be interesting to see what longevity implications there might be for the drive; they're rated for between 100k and 1 million write/erase cycles.
Anyhow, thanks heaps guys, for the patch info; now I can almost create the impression that I know what I'm doing.
Posted by: KM
« on: August 05, 2006, 11:22:55 am »
the file ws2_32.dll is used by older patch versions so if it's that then it's safe to delete, however it is also used by the 3.53/3.54 bendmx versions and also RCMS so if you are using either of those then the file will be one of those (then you'd have to check ws2_32o.dll and ws2_32r.dll to make sure they are original winsock versions and not the patch)
Posted by: freddysdead
« on: August 05, 2006, 10:03:15 am »
Wow, this is fuckin beautiful. For the first time, I am beginning to understand how all this works! I have got MX all working on the flash drive, plugged into a machine that never had anything to do with MX before, and it connects and downloads ok, apparently. But this is a cloned copy of what was runnning on the other box and has been patched I don't know how many times. The directory has both the oledlg.dll and the ws2_32.dll. I don't know if they both should be there or not.
The hosts file was being rewritten at every program initiation and restored at exit, until I grabbed the 3.1 patch and copied it to the flash drive. Now it leaves the hosts file alone. This is just too beautiful for words. Methinks I can dump the ws2_32.
I am going to try this on the corporate network tomorrow. I will let you know what happens. Many thanks to Valor for starting this thread. And thanks to KM for explaining it so even I can understand it.
-freddy
Posted by: nylly444
« on: August 05, 2006, 05:24:02 am »
Hehe, I was only posting this because people get confused by the mentioning of ws2_32.dll From what I've seen the Pie "Helpers" are still telling people to delete that one from their winmx folders, seems they still haven't realised it has changed 
Posted by: KM
« on: August 04, 2006, 10:22:30 am »
just to confuse ppl regarding nylly's post it's only accurate if you ran windows xp or 2000, for windows 95, 98, & ME it used to be olepro32.dll
for those very few running NT4 they had to choose the 98/ME install despite the choice stating "NT based systems"
3.x versions of the patch use oledlg.dll regardless of operating system
that's why i just said it uses a dll file, because that is true of all versions and much simpler - for example you also forgot to mention the IE7 situation with those ones as well 
Posted by: SamSeeSam
« on: August 04, 2006, 05:11:21 am »
I have been perplexed by repeated mention of "the DLL" without finding any other reference to this dll. Then I found the "WS2_32.DLL" which is presumably patched Winsock file, but not much help as to what to do with it. I put it in the a WinMX directory, that being the most logical place for it, but I don't see by what mechanism it works. Nobody talks about it.
The dll refers to the dll that KM has made so that winmx tries to connect to his caches instead of frontcode's . The dll is needed as nobody has winmx's source code so that it can be modified from within. Hence we need to do it externally. The patch: Blocks flooders from connecting to the primaries. Also, it filters the searches from fake files. The patch also has other features like km has mentioned. The exact working of the patch is not revealed for obvious reasons, as flooders may then be able to bypass it. If revealed, then you would get many people who will claim that 'they' made the patch. When it is Km's hard work that has made winmx alive. The patch is in the winmx directory as windows tries to first see if the dll needed is in the directory and if not there, it uses the one from system 32. The patch does not mess with system files. So that's a big plus too. Especially if somebody does something wrong, then it can mess up this a lot. The more one researches this subject, the more one becomes suspicious of hidden agendas in all directions. Fingers are being pointed regarding various entities attempting to hijack the whole network.
Who is doing what can be seen in the posts of the forums. Other people's opinions count as well. But it also depends if they answer your questions. If they do and give a good reason, then some credibility can be given I believe. You can read more of the patch in these thread: https://forum.winmxworld.com/index.php?topic=2932.0.htmlInformation of the other patches will be in that section only. I'm too lazy to search for them Sorry lol Cheers
Posted by: Bearded Blunder
« on: August 04, 2006, 05:01:59 am »
just to confuse ppl regarding nylly's post it's only accurate if you ran windows xp or 2000, for windows 95, 98, & ME it used to be olepro32.dll
for those very few running NT4 they had to choose the 98/ME install despite the choice stating "NT based systems"
3.x versions of the patch use oledlg.dll regardless of operating system
Posted by: nylly444
« on: August 04, 2006, 04:54:24 am »
Just to clear up things even more:
The .dll used to hook into winmx has been WS2_32.DLL with versions 1.9 and 2.2 and
has been replaced by OLEDLG.DLL since Version 3.0.
|
| |  | |  |
 |
|  |
|
