gfxgfx
 
Please login or register.

Login with username, password and session length
 
gfx gfx
gfx
76806 Posts in 13507 Topics by 1653 Members - Latest Member: JDTS April 08, 2025, 05:02:35 am
*
gfx*gfx
gfx
WinMX World :: Forum  |  Third Party Stuff  |  Bots  |  Post reply ( Re: Updates to the Metis Bot )
gfx
gfxgfx
 

Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Bold Italicized Underline Strikethrough | Preformatted Text Left Align Centered Right Align
Insert Image Insert Hyperlink | Glow Shadow Marquee | Superscript Subscript Teletype | Insert Table Insert Code Insert Quote | Insert Unordered List Insert Ordered List Horizontal Rule | Remove Formatting Toggle View
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What program is this site about?:
What year is it next year?:
What's the name of the site this forum belongs to?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Lagerlout666
« on: December 04, 2012, 02:12:32 pm »

Would be nice to enable dns, as a future upgrade rather than see ipv6 long codes after a room name
Posted by: Will
« on: November 28, 2012, 08:06:34 am »

im curious how an ipv4 only user is going to connect to an ipv6 only room or user (or vice versa).... the two versions get along on irc... but on mx? this is gonna get ugly...

The room host or the user could use a tunnel broker, you can find a list of a few here http://en.wikipedia.org/wiki/List_of_IPv6_tunnel_brokers
Posted by: achilles
« on: November 28, 2012, 03:12:41 am »

Microsoft has a utility on this page to check for possible problems in your code when making applications IPV6 compatible, and offers possible solutions. http://msdn.microsoft.com/en-us/library/windows/desktop/ms738649%28v=vs.85%29.aspx
Posted by: achilles
« on: November 28, 2012, 03:08:55 am »

Posted by: White Stripes
« on: November 28, 2012, 01:42:24 am »

im curious how an ipv4 only user is going to connect to an ipv6 only room or user (or vice versa).... the two versions get along on irc... but on mx? this is gonna get ugly...
Posted by: Will
« on: November 27, 2012, 02:53:02 pm »

In theory it's just a case of changing
[ RoomName : S ][ 00 : 1 ][ LineType : 2 ][ PrimaryIP : 4 ][ PrimaryPort : 2 ][ SharedFiles : 4 ][ UserName : S ][ 00 : 1 ]

to

[ RoomName : S ][ 00 : 1 ][ LineType : 2 ][ PrimaryIP : 16 ][ PrimaryPort : 2 ][ SharedFiles : 4 ][ UserName : S ][ 00 : 1 ]
i.e. making the ip field long enough to support the 16 byte ip address needed.

That would only work if your room and the clients are all using IPv6 unless your using dual stack, chat servers would also need to be modded to support IPv6. The problem then is how to display the rooms in the channel list as the protocol atm doesn't support IPv6 or a way to display a IPv6 room hash.
Posted by: GhostShip
« on: November 27, 2012, 12:55:17 pm »

I'm sure its been mentioned a few times already over the years but the limit is not 4GB but 2GB hard coded.

This was done to support win98 users and back in the day they made up  most of the userbase, XP was at that time a spring chicken. At fiirst glance some folks will suggest that FAT32 has a file limit of 4GB which is correct but whats often forgotten is that win98 can also run on a FAT16 partition and there I hope the penny drops.

As RebelMX shows it is a simple matter of sitting down and changing a few fields to adjust the protocol but obviously a new protocol requires a supporting client, fortunately Robomx/Metis src code is available.
Posted by: RebelMX
« on: November 27, 2012, 08:58:47 am »

In theory it's just a case of changing
[ RoomName : S ][ 00 : 1 ][ LineType : 2 ][ PrimaryIP : 4 ][ PrimaryPort : 2 ][ SharedFiles : 4 ][ UserName : S ][ 00 : 1 ]

to

[ RoomName : S ][ 00 : 1 ][ LineType : 2 ][ PrimaryIP : 16 ][ PrimaryPort : 2 ][ SharedFiles : 4 ][ UserName : S ][ 00 : 1 ]
i.e. making the ip field long enough to support the 16 byte ip address needed.

On a slightly different note: what is it that actually stops WinMX sharing files larger than XXX file size?  Does the client itself ignore those files when listing them in the library?  As it appears the protocol in my understanding already supports files up to 4 GB in size.  What sort of limit would you want to set?
Posted by: achilles
« on: November 26, 2012, 11:46:18 pm »

:(  Hopefully the new client will be up to par soon.
Posted by: White Stripes
« on: November 26, 2012, 11:38:53 pm »

robomx like winmx is ipv4 only...
Posted by: achilles
« on: November 26, 2012, 11:37:26 pm »

Oh yeah.. is it possible to use the chat functionality of the network, and RoboMx in general if you are using IPV6? I know the file sharing does not work, but I was hoping the chat functionality would work.
Posted by: achilles
« on: November 26, 2012, 11:34:46 pm »

Is this the most up to date, stable, and functional build of RoboMx for English users? httpss://archive.winmxworld.com/MxControl/RoboMx/RoboMX208_en.exe
Posted by: RebelMX
« on: November 25, 2012, 12:15:18 pm »

I have been looking at a few updates and improvements to RoboMX so it should be pretty easy to modify for the very few packets that may change.  As it is primarily a secondary protocol chat client there are few packets that are likely to change for it.
Posted by: White Stripes
« on: November 25, 2012, 07:08:37 am »

metis is a plugin to robomx... as long as robomx is compatible metis will be...
Posted by: achilles
« on: November 25, 2012, 05:35:11 am »

Sounds like this one can be made compatible with the the upcoming new network with some protocol changes to the code.










































gfxgfx
gfx
©2005-2025 WinMXWorld.com. All Rights Reserved.
SMF 2.0.19 | SMF © 2021, Simple Machines | Terms and Policies
Page created in 0.017 seconds with 17 queries.
Helios Multi © Bloc
gfx
Powered by MySQL Powered by PHP Valid XHTML 1.0! Valid CSS!