Posted by *alan* on 07/15/07 17:24

"b^s" <no@email.ta> wrote in message
news:46995f67$0$16295$88260bb3@free.teranews.com...
>
> "*alan*" <in_flagrante@hotmail.com> wrote in message
> news:TtTli.10652$bz7.8841@newssvr22.news.prodigy.net...
>>
>> "b^s" <no@email.ta> wrote in message
>> news:4697e6d4$0$16402$88260bb3@free.teranews.com...
>> >
>> > "Morton Davis" <antikerry@go.com> wrote in message
>> > news:fKJli.27148$Fc.16575@attbi_s21...
>> >>
>> >> "vince" <vince@gmt.net> wrote in message
>> >> news:Xns996C1950B6DD4ZXMA9@194.177.96.26...
>> >> > http://www.mxpie.info/
>> >> >
>> >> > WINMX IS NOT CLOSING!!!!!
>> >> >
>> >> > July 6, 2007
>> >> >
>> >> > MXPie.info Team has released a special version of the MXPie Patch
>> >> > for
>> >> > WinMX due to the recent closure of WinMXGroup.com.
>> >> >
>> >> > MXPie Special Release Version 3.5 includes:
>> >> >
>> >> > 1. Support for WCS 1.7.4 users to connect to WPN using MXPie Caches.
>> >> >
>> >> > 2. Support for WinMX Group DLL users to connect using MXPie Caches.
>> >> >
>> >> > MXPie Patch Version 3.5 is a special release for users who require a
>> >> > connection method for WCS and the WinMX Group DLL due to the closure
> of
>> >> > WinmxGroup.com (KM). This will allow connection through MXPie
>> >> > servers
>> >> > which are independent from WinMXGroup.
>> >> >
>> >> >
>> >> > The 3.54 patch below is working perfectly for me.
>> >> >
>> >> >
>> >> > http://www.espwinmx.com/
>> >> >
>> >> > http://www.fisioterapiautebo.com/estwinmx/3.0mod2-3.54-Setup.exe
>> >> >
>> >> > http://www.fisioterapiautebo.com/estwinmx/3.0mod3-Multi-Setup.exe
>> >> >
>> >> >
> http://www.fisioterapiautebo.com/estwinmx/3.0mod3-Patch-Only-Setup.exe
>> >> >
>> >> > http://www.fisioterapiautebo.com/estwinmx/ws2_32.dll
>> >> >
>> >> > http://www.espwinmx.com/download/MXPie_Patch_v3.4.exe
>> >> >
>> >> > I'm back up and running.
>> >> >
>> >>
>> >> Many of us never went down.
>> >>
>> >>
>> >
>> > Never stopped for me either, I have stayed with winmx version 3.31 and
> my
>> > own modified hosts file.
>>
>> Would I be correct in assuming that at one (or more) points, your version
>> 3.31 in fact DID stop working until you modified the hosts?
>>
>> Also, on what basis did you modify your hosts? You got a list somewhere?
>> Since you call it your "own" modified hosts file, it sounds like you
> didn't
>> do so from a list, but somehow knew how to compile your own. How does
> one
>> do that?
>> Thanks.
>> --
>> Alan
>>
>
> Alan, you are being pretentious. Obviously I modified my "own" hosts file
> from a list.

Pretentious? Hardly. Just not very computer-savvy (had never even heard of
a "hosts file" until this winmx connectivity issue came up) and perhaps
confused not only by your use of the word "never" but also by your use of
the word "own".
Now that it's clear that you meant "never" in a very relative sense (i.e.
until your hosts file became obsolete and made it unworkable) and that by
"my own modified hosts file" you actually meant "modifications to my own
hosts file" (I thought you were making a distinction between a hosts file
which you yourself had modified, as opposed to the modified host file which
everyone may have been using), I have two questions:
1. Is there any particular advantage to using version 3.31 over using
updated versions (which, I assume, already include an updated hosts file)?
2. In case the hosts file again become unworkable and need to be modified,
what would you recommend as the best source for obtaining a new, workable
hosts file? This newsgroup? WinMXworld?
Thanks in advance for your reply.

[Back to original message]