odious winmx nutsackery

[asoneuponarock]

greetin's, cretins. having downloaded winmx 3.31 (3.31 on account of my tres moderne OS Win 95. yeah, you're jealous.) and satisfactorily configured it, what's next but to connect to the WPN - alas, dammit, it don't. the yellow flashes endlessly, and i weep. oh how i weep. please, boys and girls, end my suffering.

[Siskabush]

Get the new WinMX 3.53

[notbob]

Get the new WinMX 3.53

does it work with windows 95?


(also, other than fixing the chat, which is completely unimportant, 3.53 adds few (if any) fixes that relate to this guy)

use a secondary connection

[asoneuponarock]

no, 3.53 ain't compatible with 95; moreover, ah IS using a secondary connection. i'm near suicide here, folks.

[shawners]

an endless delusional ray of imperfection.. whats your ip?? I may want to run my old nuke program to cause the blue screen of death =) MUAAAHHHhhh .

[Gnidrologist]

greetin's, cretins.

:bk
So that is how we show our appreciation to each other now days. I guess I'm missing a lot. Need to get out and learn more :playboy

[MushroomheadXIII]

I reccomend you use any progg other than winmx(opennap).

[PirateCy]

Buy an other computer.

[Mels_Smileys45]

I recommend you use any progg other than winmx(open nap).

Thats not answering the question. Maybe he knows how good winmx is and chooses to stick with it. Also Winmx is not open nap. Although people would be wise (if you like movies) to use the open nap function.

[Crazy Horse]

Try adding the number 1 at the beginning of your incoming TCP connections & your in/out UDP packets. I had the same problem when I had a modem, that fixed it ....then (many,many moons ago)

[asoneuponarock]

so i'd be adding "1" to the fixed port numbers; i.e. the default TCP of 6699'd become 16699 & the UDP would from 6257 become 16257-- or replace port numbers alltogether with 1?

[asoneuponarock]

regardless, it's ineffectual either way. at present settings are as follows:
OUTGOING TCP: i ain't usin a proxy
INCOMING TCP: "unable to accept incoming TCP connections" is selected (in accordance w/ the findings of the initial winmx-run test; the alternate setting results in total inability of winmx to detect 'net connection).
IN/OUT UDP: "unable to send or receive UDP datagrams on any port" is selected.

that'd be that - and yet still no succesful connection.

[Crazy Horse]

so i'd be adding "1" to the fixed port numbers; i.e. the default TCP of 6699'd become 16699 & the UDP would from 6257 become 16257?

This is what I was referring to but it didn't seem to help you. My only other suggestion is to go to the link here http://homepage.ntlworld.com/j.buchanan/index.html. Hopefully there is a solution there. Good luck.