Entire Download Que Gets Wiped Out

[No Incomplete Files Here]

How come the entire downloading que other than the files that I am downloading gets wiped out  ( WinMx goes through and timesout every file ) ?
         I am using windows xp, WinMx 3.54 beta, secondary connection   I had the same problem before WinMx had to crash .
                                                                     
                                                                         Thanks

[so_]

This happens to me sometimes also. I can go thru and highlight the ones that timed out, hit retry, and they will all resume their place in queue. But, like yourself, dont understand why it does that to begin with.

[GhostShip]

I havent actually seen this myself so its a puzzle for now, I suspect some outside influence but without it happening at one of the monitoring or moderators machines I cannot help with this one  

In the last few years this was due to secondary disconnection and reconnecting issues, but there is a whole load of new tricks being played that we have to keep our eyes on  
If you have any extra details like client type whether you run Peer Guardian,  XP version etc we would be pleased to hear from you here as we rely on folks like yourselves spotting new Industry/ISP tricks.  

Also if you could PM me with the names of the tracks that you where either uploading and downloading at the time, please do not post this information here as it can be used to monitor them. :twisted:

[nylly444]

Ghost Ship is right, this could be some new trick. However it's always been an issue, it usually happens on secondary connection when you lose connection with "your" primary and get shiftet to another one. You usually can highlight and hit "resume", your queues will then get updated to the new id. You might want to look at the time you're connected (in title bar), if the timeout happens shortly after that it's simply the loss of your id, if it happens "out of the blue" I'd suspect some other reasons too.

[Anonymous]

Ghost Ship is right, this could be some new trick. However it's always been an issue, it usually happens on secondary connection when you lose connection with "your" primary and get shiftet to another one. You usually can highlight and hit "resume", your queues will then get updated to the new id. You might want to look at the time you're connected (in title bar), if the timeout happens shortly after that it's simply the loss of your id, if it happens "out of the blue" I'd suspect some other reasons too.

It's happened to me, running as a primary. My spm went to 203,000 and everything, both downloads and uploads, except the ones actually transferring,  timed out.

I disconnected to jettison all the secondaries, including the bad one, retried every file, and was back more or less where I started.

NYcram