Author Topic: New Test Patch from Eagle With UPNP (Read 10866 times)

Mick832 · « **Reply #60 on:** August 27, 2008, 09:40:21 pm »

@Silver Stripes If testing is just done by people like you, rather than idiots like me, then there would be lots of problems undiscovered. An idiot like me can find a whole lot of ways to stuff up a simple patch. And proper testing of any product must cover all who will use it.

PS I might just have to add 56k users to my ignore settings now too.

GhostShip · « **Reply #61 on:** August 27, 2008, 11:16:26 pm »

Cheers for all the helpful feedback folks.

Being one of the those who have tried to steer this patch into development and then onto release I do feel that maybe I may have missed out the info that we are updating from the developers site while testing is going on, this is of course an oversight and no harm was intended or expected.
I have a full list of those allowed access to the site in question ( 2 folks) and made enquiries regarding its security arrangements prior to pointing anyone to the site, and for the public record I have full confidence in Eagle to do whats best for the community of which we are a part.

Eagle has already designed, built and delivered peer caches that have been in use for some time now saving many from leaving the network, he has shared the sources of his work to ensure we can watch development and test for ourselves and has asked nothing in return for his work, he works in my view for the spirit of winmx to survive and wishes to help the community expand by helping in an area we are critically short of talent in.

When we are given an opportunity to re-knit the community and a powerful coding talent to work the knitting needle's I for one am not the man to say not with my wool

I have proposed we make use of a fully working patch and to work together with others to help improve matters for us all, this requires trust and openness, I hope I have demonstrated both in this thread, I have no reason after checking through Eagles sources and speaking to him many times to doubt him or his word, I have absolute trust in him and his continuing desire to develop for the communities benefit, I think that's all need be said from me on this.

White Stripes · « **Reply #62 on:** August 28, 2008, 08:49:29 am »

@mick why do you think many 56k (or other modem speeds) users lie about their connection speed? is it really a cable user with throttle problems or a dialup user... hmmm... apparently you fit into the '99%' of irrisponsible users.... you shouldnt be blocking users of any speed... not everyone is as "fortunate" as you...

btw, if i used moni i would have already found it..

[EDIT -- addon]

for shits and giggles;

installed mxmoni version 1.28Eb on winmx 3.54b4 --- could not replicate the .ini file in the wrong directory bug... this is however with the beta9 patch so perhaps the bug has already been fixed? or perhaps different versions of moni have a different effect? a 3rd party process utility shows winmx is using its own directory as its 'running' directory rather than monis directory... so my previous theory is out... at least for moni 1.28Eb....

any users out there that have the 'wrong directory .ini' try deleting the .ini (if you made changes in it dont forget them!) file and restart MX from moni as usuall to see if the .ini is recreated in the proper place (the main winmx.exe directory)... and plz post the result (whatever it may be) and the versions of MX and moni you are using.....

...mick id like you to try this too regardless of our current.... ....difference of opinion.... consider it for the 'common good'...

Mick832 · « **Reply #63 on:** August 28, 2008, 11:43:16 am »

Deleted as you asked, started MX by moni, In C:\Program Files\MXMoni I have a oledlg.ini again.

Also running 1.28 EB and 3.54b4.

Now that I have actually stayed on topic, I will answer your questions.

I don't think 56k users lie about their speed. In fact I like to upload to them as my Aussie DSL until very recently was only 512/128 anyway, so I am no speed demon.

I don't block users of any speed.

We don't have a difference of opinion. You are just someone who should learn to take a breath before they reply.

Mick832 · « **Reply #64 on:** August 28, 2008, 11:59:07 am »

Deleted it a second time, started MX without moni, put the ini in WinMX folder, shut WinMX, did not delete ini, started it again with moni, now I have an ini file in moni folder too again.

White Stripes · « **Reply #65 on:** August 28, 2008, 12:54:17 pm »

ok this is funky.....

what did you use to install winmx initially? the installers on winmxconex? the original winmx.com installer? other?

winmx itself -is- installed in "C:\Program Files\Winmx" yes? ... if not where?

moni is installed in "C:\Program Files\MXMoni" ?

is winmx set to autostart with windows in its preferences? or does it -just- start from moni?

are you running with administrator privalages? (this is in control panel > users just in case)

are you using the same username that you installed winmx with to run winmx?

umm... cant think of anything else right now... lol... lets start with those... cos i never could get eagles patch to write to any directory -but- winmx's no matter -what- i tried... but obviously its possible...

anybody else out there got any ideas? eagle? GS? MH? tiny? anybody??

Lagerlout666 · « **Reply #66 on:** August 28, 2008, 01:07:33 pm »

Router crashed in work, upnp was lost, winmx conencted again but no ports open, not really a issue, just rebooted winmx, but i duno if you can add something that watchs out for that maybe? i know routers can be a pain for alot of people.

MinersLantern · « **Reply #67 on:** August 28, 2008, 06:35:58 pm »

On Beta9 now.
If I set upnp to zero, winmx still partially starts. Winmx window as a big gray area as if the graphics part is boinking out. But update window shows its stuff.
It doesn't connect that way either and winmx wont close by the close button.
That brings up the program not responding, do you want to end the program now window and then it can be terminated by force. Set upnp to one and it works as it should.
Maybe I should open up a range of ports in the 1500s in addition to the TCP/UDP ports it usually uses in the router?

White Stripes · « **Reply #68 on:** August 28, 2008, 10:17:23 pm »

@miners;

the ini is picky....

delete it and restart mx so its recreated....

to disable UPNP make sure that the ini opens in notepad or DOS Edit (blue notepad like editor)
-not- wordpad or anything even remotely wordprocessor/rich text like...

after getting a fresh ini and opening it with -notepad- click just behind the '1' on the upnp line and press backspace just once to delete the 1 and press 0 only once.... press no other keys.... click the 'x' on notepad to close it and when it asks if you want to save click yes...

your problem should be solved and upnp disabled...

@eagle

stronger sanity checking on the .ini is apparently desperately needed.... this is twice now the same problem has cropped up...

@mick

did you disappear on me? that problem is itching my brain like a mosquito bite lol...

Mick832 · « **Reply #69 on:** August 28, 2008, 10:46:11 pm »

@ Silver Stripes, original install, not sure, got a WinMX353.exe and winmx354beta4.zip where u then extract the WinMX.exe. Also got Install-3.1-3.54b4.rar and 3.0mod3-3.54-Setup.exe.

Both installed where you said.

Not autostart, I start moni from a desktop shortcut and have the start WinMX when moni starts option checked.

Administrator, 3 users, me as Computer administrator, the ASP.NET Machine limited account password protected and Guest turned off.

Usually use Mick as username then change to «/¥\íçk»832 (ascii)

I'm Down Under, so I disappear in time zones, plus 12 hour shifts get me too

White Stripes · « **Reply #70 on:** August 28, 2008, 11:14:31 pm »

lol... well.. at least they are in the 'default' directories...

what i ment by login username i ment for the computer itself... like for instance 2 admin accounts one with the name mick1 and another with mick2..... but i take it you dont have it like that...

do the other two users make use of MX? if so what kind of privelages do they have?

Mick832 · « **Reply #71 on:** August 28, 2008, 11:30:28 pm »

There are really no other users on my PC. The ASP.NET user account was put there by a Windows update and the Guest account is never used. So it is just me really, one user with admin.

Mick is not my real name, so my user name on my PC is different but I don't think that would matter, lol.

Me Here · « **Reply #72 on:** August 29, 2008, 03:59:18 pm »

OK folks need to test something for Eagle

Anyone that is using the upnp functions I need you to do some testing for Eagle.

When you next shut down WinMX.
open your Oledlg.ini file in the C:\Program Files\WinMX folder. (as Stripes mentions open this in Notepad only)

In this file you will see this setting:

/enableupnp 1

What some folks are experiencing is when this is set to '0' instead of '1', WinMX start up takes a very long time with grey screen. This also happened to me and upon examination Port 0 had tried to be forwarded via UPnP but was inactive.

So set yours to 0 making sure there are no spaces after this, and save this file. Then restart Your WinMX and see if you get the same sluggish result. Also if you do happen to have a router that lists the UPnP ports forwarded for you maybe you can check this for any thing on port 0 if you get this same delay in start up. And post back results.

NOT to be confused with the '/upnpreopen 44000' Leave this set to defaults.

Me Here · « **Reply #73 on:** August 29, 2008, 05:10:11 pm »

Sorry for the double post folks but I had some feed back on this from some others that are indeed experiencing this issue and after a few test runs with Eagle he was able to resolve that issue, we hope.

Change:
Fixed UPnP set to 0 errors and lag.
Fixed oledlg.ini file placement in MxMonitor folder when MXMonitor starts WinMX.

No need to delete your oledlg.ini file for this just repace this with the oledlg.dll and test this with the /enableupnp 0

Please anyone that was having this issue try this and post back results.

[Edit: File removed as update pending - Ghostship]

EDIT*******
I literally just posted so sorry folks, Im going to upload the version with the fix for MXMonitor users who start WinMX with MXMonitor here also as its working perfectly here and I was able to make the older one have the same problem Mick describes so ... this will always place the oledlg.ini file inside the WinMX folder with the winmx.exe file.

White Stripes · « **Reply #74 on:** August 29, 2008, 07:16:00 pm »

how did you fix the .ini in moni folder bug??

what was causing it?? (i gotta know)

EaglE123 · « **Reply #75 on:** August 29, 2008, 07:28:09 pm »

if mxmoni loads winmx, probably the "current" folder is the mxmoni folder, probably mxmoni changes directory to winmx after the load of the patch and before winmx reads his config
i corrected with something like that:

if ( winmx.exe is NOT in the current folder )
change dir to "../winmx/"

White Stripes · « **Reply #76 on:** August 29, 2008, 07:59:55 pm »

still seems odd that if moni started as the working directory that the patch could even load at all... cos if moni was the working directory after winmx started but before the patch loaded then winmx would load the default oledlg.dll that comes with windows wouldnt it? (arent the various .dll patches not taking advantage of the 'dll hell' glitch of windows?)

oh.. one more tidbit... i never deleted the .ini file after beta8 created it (and i turned upnp off... with no troubles...) but when updating to beta9 the ''/upnpreopen' line wasnt added to the old .ini

if this variable is a nessesary one a fix for 'update old ini that doesnt have new feature or obsolete lines in it' function is needed... if not... it would be nice if there were so us tweaker types can see what new options we can change without deleting the old ini...

comment lines would be a good idea to add to the ini as well so folks dont get creeped out at lines that they dont understand... and/or for general info...

and perhaps a changelog.txt that gets autocreated/changed in the winmx directory to give infos and even infos about you... ya gotta at least sign your art

just some random thoughts... guess it was more than a tidbit tho

White Stripes · « **Reply #77 on:** August 29, 2008, 08:57:26 pm »

oddity/bug found in beta9r2 ... on startup winmx -insists- on starting minimised to tray... regardless of settings to the contrary... otherwise has no problems connecting... havent had a download start yet so dunno about that but i think that part will be fine too...

EDIT -- transfers work fine...

thunderwinds · « **Reply #78 on:** August 30, 2008, 01:05:30 am »

lets start with the Linux comp,openSUSE 10.3 wine 1.1.3 athlon64 3500+ 1 gig ram, i also have wcs and moni running. no major issues with the beta 9 patch, it seems to have solved the excessive cpu usage.also the ini file is now in the folder with mx, originally it had been placed in the home folder. just a minor nuisance when i'm on primary a room hosted on one of the other comps will not show in the list and if it's hosted on the same comp i'm checking the channel list then the loopback addie is what shows in the list. this happens to all three comps.

the win 98 comp seems to be doing quite well with the beta9 patch. there is only the one minor nuisance noted above.

the xp comp no issues with the beta 8 patch, i haven't switched it to the beta9 patch yet. there is only the minor nuisance.

it's looking prety good

Mick832 · « **Reply #79 on:** August 30, 2008, 12:46:39 pm »

Deleted the ini in both the winmx and moni folders, installed beta9, started with moni, now it only creates a new ini in the winmx folder.

Everything else fine.