New Test Patch from Eagle With UPNP

[MinersLantern]

Beta9b works a charm now. No gray screen after turning off upnp.
@ Silver... Mine starts as usual, not minimized.

[Joshua203]

Since beta9b seems to leave the ini in the right place for Mick using mx moni to start this must be in the way my setup looks

My WinMX is located at D://some folder in my langauge/WinMX/ and MXMoni-folder is located in the WinMX-folder (D://some folder in my langauge/WinMX/MXMoni1.30/)

I handstart WinMX in Moni if i use it (handstart for technical advantages) but i guess if Moni would auto start WinMX it would do exactly the same....

It still leaves the ini in the moni folder

don t change this just for me cause i guess i will be back on my own setup after testing (i never lost 3.54b6 and still like it very much), but i may not be the only one having a setup like this

I hope this helped a bit
Greetings, .. Joshua203

[GhostShip]

The simple cure for all this is to have a fixed INI file and place it in the correct folder with the installer, I,m not certain theres any benefit in asking a patch to start reading the registry to find the location of WinMX on every install.

[Me Here]

The mxmoni should be in its own folder, ie; C\Program Files\MxMonitor.   The fact that it grabs WinMX and starts it was causing the patch file to say  oh im in the Winmx directory so i'll make a ini file as none is present.  Eagle has fixed this having the patch look for winmx.exe and if its not present It knows its in MxMonitor and looks for the C\Program Files\WinMX directory instead. 

To be fair Eagle is not a MxM user and wasnt aware that it could start WinMX for you.

And hes also native italian speaking so Im not entirely sure he will completely understand the comments here about why/how he fixed it.  So in laymens terms there you have it.

Thanks goes to all who are testing this for Eagle 

Im  curious to hear from some of the folks we havnt heard from using this latest version.  I'd like to hear even if its just to say Whoot its great or what not... instead of assuming its all going fine becaue no one else is screaming about anything lol.

[Joshua203]

i did not ask for a fix but i thought this behaviour could be important in this stage of development

btw as stated before also moni has it s own folder ..(just hidden inside mx folder )

edit : reading ghost's solution later again ..... yes that would do the trick

[Me Here]

LOL no i didnt mean you wanted a fix, just givin my 2 cents on that one.

Great anyone else with a report for Eagle on how things are going?

[White Stripes]

The simple cure for all this is to have a fixed INI file and place it in the correct folder with the installer, I,m not certain theres any benefit in asking a patch to start reading the registry to find the location of WinMX on every install.

this i would definitly have to agree with... and in the lack of presence of an .ini file the patch -doesnt- autocreate an .ini but rather uses default -internal- settings....

quite a few DOS and other .ini using programs follow this pattern... default (or none.. depending on the requrements of the program) settings when no .ini (or .cfg but usually they were the same basic structure) is found...

[birdman]

Does this new patch remove the current  KM dll  or PIE patch on install  if not could it do so to avoid any conflicts ?

[White Stripes]

if you have pie installed you'll need to use the installers on  https://patch.winmxconex.com/ (if you already have mx installed use the patch only install to get rid of pie)... then youll have to rename the oledlg.dll (kms patch) in winmx's directory to something like oledlg.off so youll still have it just in case, but it wont run.... then 'install' -this- patch by unzipping it into winmx's directory (it has the same name as KMs patch) start MX and youll be using the new test patch...

...there isnt an installer for this one yet... its 'installed' manually... and its not finished yet so... if you dont feel up to testing an unfinished product that may cause winmx to act odd or not work at all... it may be best to wait....

[Bluehaze]

After some extensive use, I must give beta9 a hearty thumbs up! From the standpoint of a secondary (Celeron 1.13 ghz CPU, 256 mb of RAM, Win. 2000 SP4, WinMX 3.54b), Eagle's patches, beta 8 and beta 9 - have performed admirably! I cannot imagine how they could do any better.

Thanks!

Bluehaze-

[White Stripes]

any news on whats going on behind the scenes? any beta 10 coming down the pipe? a final?
a (tenative?) list of new features or fixes?

cmon guys (and gal) throw us a bone here!

[White Stripes]

hmmmm.... ok... odd... ive rebooted windows a few times since beta9r2 was installed and now winmx doesnt have the 'start minimised' problem anymore.... it may have been fixed after the first reboot i dunno cos i wasnt paying attention (and winmx is set to start hidden in tray with windows anyway...)

but it seems a reboot fixes the odd 'start minimised' problem of b9r2.... i think...?

[GhostShip]

We are now happy that the release is pretty much as good as its going to get, Deux will be looking at the installer intergration next to further cover ourselves with any of the minor issues that have cropped up or expect to crop up we can expect some good news on a final version pretty soon Stripes 

[White Stripes]

cool

will us geeky types be able to keep (with an option in the ini perhaps) the 'FSR' and 'BC' stats? (im curious to see what happenes when ppl start switching over)

[GhostShip]

The Blocking Display option will still appear in the INI file for those that want to be able to view or disable it .

I believe that by not rushing into a fast changeover we have been able to demonstrate publicly the stability of the patch design and hopefully this will ensure we have many confident users when the time comes to take the next step.

That time has now been selected and the clock is ticking down

I would like to take this time to thank all the beta testers for their help and time in ensuring we have something special to offer, also I would like to thank Eagle for his dedication and commitment towards the winmx community as a whole, thanks from us all Eagle 

A new dawn awaits ... 

[nylly444]

Issue about Linux split and moved to "Winmx Without Windows" - nylly