Author Topic: Update of OurMX (Read 15734 times)

rhd2330 · « **on:** January 20, 2014, 05:10:36 am »

Where do I get the update of OurMX?

silicon_toad2000 · « **Reply #1 on:** January 20, 2014, 05:15:09 am »

https://forum.winmxworld.com/index.php?topic=12702.0.html

rhd2330 · « **Reply #2 on:** January 20, 2014, 05:48:07 am »

That gives me a lot of popups when I try to search on the Secondary, and on the Primary the doesn't work right and I get this error ever time I try and download something, and nothing will go into the download. Nothing there!

silicon_toad2000 · « **Reply #3 on:** January 20, 2014, 06:29:22 am »

its a preview, it has a lot of bugs being worked on

you'll the bug reports on the ourmxworld forum, your account there should be active shortly.
If you find a new bug that hasn't been reported in the bug reports or closed bug report sections add it with as much information as you can.

rhd2330 · « **Reply #4 on:** January 20, 2014, 06:33:01 am »

Please help, I can't download anything.

GhostShip · « **Reply #5 on:** January 20, 2014, 09:03:01 am »

For now can I suggest you continue using WinMx to do your downloading with Rhd, Ourmx is a beta client that means its still in testbed stage and not yet fully operational, you can get a copy of WinMx from here

https://patch.winmxconex.com//

For those of you who want to know what has been updated already heres a partial list of fixes that will appear in the ourmx beta 2 thats not yet ready for release.

https://www.winmxworld.com/tutorials/ourmx_client_updates.html

RebelMX · « **Reply #6 on:** January 20, 2014, 07:05:17 pm »

Update 1 *almost* sounds like a developer test bed, and forgetting to remove it... just like a program had in the not too distant past and got blasted for it... mistakes do happen, just a pity people believe the worst. Looks like the client is coming on well, and I'm glad the regionalisation has been built in even if not to split the network but to offer nodes that best fit that particular region as priority

What about the "do not browse" packet i proposed a while, that would add security for individuals and be easy enough to implement?

GhostShip · « **Reply #7 on:** January 20, 2014, 07:17:29 pm »

The do not browse mechanism is already in place in the beta 1 release RebelMx, as for forgetting to remove something what is it you refer to that may have been missed ?

RebelMX · « **Reply #8 on:** January 20, 2014, 07:48:18 pm »

The update 1, the message boxes of packet info.

I must have overlooked the do not browse, i now see it included many thanks for pointing out. I'm interested in how a primary (presumably OurMX) knows which of the tick boxes are in use?

GhostShip · « **Reply #9 on:** January 21, 2014, 12:35:38 am »

Its all done by magic mate

wonderer · « **Reply #10 on:** January 21, 2014, 01:51:59 am »

Darn
and I was presuming is has been GS behind the ticket boxes

RebelMX · « **Reply #11 on:** January 21, 2014, 06:59:33 am »

Quote from: GhostShip on January 21, 2014, 12:35:38 am

Its all done by magic mate

Very good. Perhaps at some point one of the developers (whilst they are awaiting the lead developer) could update the core thread where it was suggested with any additional data types that are no doubt required. Trivial as it seems it makes sense to try and document the changed packets. Also i presume that OurMX will still accept the "basic" packet and thus prevent all browsing?