|
|
Posted by 1 on 09/18/05 16:59
On Sun, 18 Sep 2005 08:28:34 GMT, "George Hester"
<hesterloli@hotmail.com> wrote:
><1@odds.com> wrote in message
>news:ilopi19n9qnqmrp3f49o3tldkmr5pt5jh5@4ax.com...
>> On Sun, 18 Sep 2005 01:06:31 GMT, "George Hester"
>> <hesterloli@hotmail.com> wrote:
>>
><snip>
>
<snip too>
>
>Really odds these file names were bogus. I asked the trader about them and
>he said he never heard of these groups or songs. I sure as hell didn't
>either. So what Johnny Noname - Singing the Blues in Kansas.mp3 is floating
>around on the Internet and decided we looked like good victims to attach to?
>I've never seen this before. You know if I tried to start one of these
>although it was hooked to a valid partial in my shares it immediately went
>File Unavailable. Most of those it wanted to complete he did have whole.
>But they were just showing white in his shares.
>
>I have looked again in his browse. They seem to be gone. He is no longer
>on line I just keep it up for the hashes. Some are valid but maybe I should
>just close this out? He's got too many mp3s for some one that said he
>wasn't sharing any. I believe this person I've known him quite a while.
The file search and browse results use the UDP protocol, which has no
error correction so is somewhat unreliable. Another computer out
there may have picked up on your search request (as a result of a UDP
error) and responded, or your mystery source may have been connected
as a primary and their computer got out of sync on what it was sending
you, and gave you results of one or more secondary users that were
passing UDP datagrams through the mystery source machine at the same
time. If your mystery machine has a persistant yet non-fatal (at the
moment) memory error, then WinMX could have been mis-directed to the
extent it showed you files from one source that actually exist on
another although it would be difficult to actually connect and
download those files shown in error.
This can also happen if the user has so little memory in their
computer that Windoze is running programs out of the system swap file
and a disk error happens at a vulnerable location. This may not be
such a critical error as to cause a program or system crash, but it
could cause unpredictable behavior in Mx or other applications.
George, my advice is to never walk around barefoot. With your luck,
you would certainly find a nail just under some leaves. ;o(
Navigation:
[Reply to this message]
|