ston
June 15th, 2002, 11:51 PM
I have discovered that WinMX version 3.2 has many serious problems that were not in 3.1. (or even in 3.0Beta)
Most of the problems relate to poor connectivity. I use a secondary connection. (Win98)
3.2 takes a lot longer to connect.
3.1 used to connect right away. 3.2 seems to get stuck on "Finding network connections"
3.2 has a lot more upload and download connections timing out. Even those that do successfully connect seem to take a lot longer.
Whois and Browse do not work much of the time in 3.2
In 3.2, many messages I send do not get received.
Many users are queued twice in 3.2. I tried to message these double queued users to ask if they had a problem connecting, but all messages were bounced back undelivered.
I get often zero search results for words that were previously returning hundreds of results
I have tried rebooting, reinstalling, increasing timeout limits, none has helped.
There are some additional annoyances with 3.2, like features that were removed or altered, but that I can live with as this was a decision on the part of Frontcode.
Since I have only been using this new version for 2 days, perhaps it is just bad luck. I have got every function to work sometimes, but these problems occur a large portion of the time, perhaps several times as often as in v.3.1
Frontcode has stated that the main changes in v.3.2 were in improving the network connections of the primary nodes. Apparently these changes have come at the expense of the secondary connections.
Most of the problems relate to poor connectivity. I use a secondary connection. (Win98)
3.2 takes a lot longer to connect.
3.1 used to connect right away. 3.2 seems to get stuck on "Finding network connections"
3.2 has a lot more upload and download connections timing out. Even those that do successfully connect seem to take a lot longer.
Whois and Browse do not work much of the time in 3.2
In 3.2, many messages I send do not get received.
Many users are queued twice in 3.2. I tried to message these double queued users to ask if they had a problem connecting, but all messages were bounced back undelivered.
I get often zero search results for words that were previously returning hundreds of results
I have tried rebooting, reinstalling, increasing timeout limits, none has helped.
There are some additional annoyances with 3.2, like features that were removed or altered, but that I can live with as this was a decision on the part of Frontcode.
Since I have only been using this new version for 2 days, perhaps it is just bad luck. I have got every function to work sometimes, but these problems occur a large portion of the time, perhaps several times as often as in v.3.1
Frontcode has stated that the main changes in v.3.2 were in improving the network connections of the primary nodes. Apparently these changes have come at the expense of the secondary connections.