Post reply

Topic Summary

Posted by: KM

« on: August 03, 2006, 01:47:40 am »

Insert Quote

yep, or do that and let the patch take care of redirecting to working caches instead of robomx... lol

Posted by: Lagerlout666

« on: August 03, 2006, 01:16:44 am »

Insert Quote

Doesnt work or didnt for me, the way i got round this was i found the bot ws2.dll looks for any old peer cache ips tryin to go out an i assume it takes over somehow, So what i did was put an old ip

67.18.233.36

into the edit peer cache servers box, shut it down restarted an it connected before i could see it turn yellow, channel list frozze a few secs but think that was shock that it was brought bk to life

Just some of the other crap advised did nothing for me , may have worked for u but this worked for me, hope this helps anyone stuck

Posted by: KM

« on: August 01, 2006, 04:26:22 pm »

Insert Quote

or better yet, stop using IP Addresses that keep changing and use hostnames that will always be correct?

cache?.winmxgroup.com (? is 1-9)
cache?.winmxgroup.net (? is 1-19)

put a few random ones in, currently every hostname points to every cache, but that can change so multiple hostnames is a good idea (plus i believe robox will only try the first if you only put 1 hostname in, multiple hostnames will make it try multiple times)

Posted by: Me Here

« on: August 01, 2006, 12:14:37 pm »

Insert Quote

New peer cache ips to add to this to make it connect.

209.67.209.54
217.160.28.101
80.175.31.63
82.195.155.6
207.210.117.53

Alternatively you can always have a peek here for current working Cache IPs to add to this..

http://www.winmxgroup.com/check2.php

Posted by: nylly444

« on: June 04, 2006, 06:03:59 am »

Insert Quote

Another way to get it to connect is to take the dll (ws2_32.dll) from the winmxgroup patch and drop it into your robomx folder

At least that works for me, hehe

Posted by: GhostShip

« on: June 04, 2006, 12:58:21 am »

Insert Quote

Hmm sorry to hear that ZîldjîåñÐ®µmmè®G®l , Bender did mention that the modification involved adding the peer cache numbers to RoboMx but on the MxControl site front page, so many folks may have missed what to do.

List of peercache servers that are available for use
205.238.40.2
209.67.209.50
212.227.64.159
82.195.155.5
82.43.224.20

As this is really the only change on 2.07 I would suggest sticking to your current patched 2.06 if its working, future versions will I hope provide an internal list and hopefully more features.

Posted by: ZildjianDrummerGrl

« on: June 03, 2006, 09:33:40 pm »

Insert Quote

Just a heads up though, when I downloaded this newer version I could not connect to the WPN at all. I had to switch back to 2.06 just to connect. From what I heard you don't need a patch for this version but again it didn't work for me.

Posted by: GhostShip

« on: May 05, 2006, 10:54:37 pm »

Insert Quote

Cheers Nylly, I just spotted it myself after a nap, its a very welcome release from Bender

Posted by: nylly444

« on: May 05, 2006, 05:30:23 pm »

Insert Quote

Bender just released a new RoboMx version:

Quote

I released RoboMX 2.07. This release contains a fix for the new peercache servers. You can add/edit peercache servers under Settings->Network->Edit peercache servers (Make sure, Show advanced options is checked...) RoboMX 2.07 comes - as the previous versions - in three flavors and 2 languages. 1) With sound effects 2) Without sound effects 3) Without the MFC runtime and soundeffects (update version) A) English B) German You can find it in the download section (where else...) Cheers, Bender. (List of peercache servers: 205.238.40.2 209.67.209.50 212.227.64.159 82.195.155.5 82.43.224.20 )

Glad to see him back