Author Topic: winmx not working under wine/opensuse 13.1 (Read 11389 times)

dabud · « **on:** November 26, 2014, 02:20:23 am »

Opensuse 13.1 Wine 1.7.31-388.1-x86_64 Winmx 3.54b4

I have been using opensuse/wine/winmx for a few [8 approx] years now. Occaisionally I have run into trouble but have usually found answers to solve problems. This time however, I am stumped.
Everything was running OK, I had just done opensuse updates thru zypper and was having no problems. I had to reboot and now I cannot get Winmx to start. I kept getting the Winmx has encountered a serious error... window and could get no further. I tried uninstalling winmx and reinstalling, to no avail. I usually go with the latest version of wine and it gets updated thru the wine repos in Zypper. I uninstalled wine completely and turned off the wine repo and went back to the version that opensuse has in their repo [1.7.2.1-x86_64]. Then tried reinstalling winmx, but still got that same error [Winmx has encountered a serious error... ].

All results seem to be the same. It starts the Winmx installer and as soon as it gets to the Winmx License Agreement window, I get the: "This program has encountered a serious error and has to close" window.
I have attached a backtrace from the "details" button of the "Winmx has encountered a serious error" window and a snapshot of all I get when the winmx installer has run.

Can anyone pls advise?
Thank You

White Stripes · « **Reply #1 on:** November 26, 2014, 04:23:20 am »

so im assuming it worked at some point in time on this machine? try reverting to an earlier version of wine maybe?

GhostShip · « **Reply #2 on:** November 26, 2014, 11:37:14 am »

Could be a corrupt WinMX file perhaps ?

nylly444 · « **Reply #3 on:** November 26, 2014, 08:25:49 pm »

Tried with a new .wine folder ?
i.e. rename old .wine and do winecfg to create a new one?

dabud · « **Reply #4 on:** November 27, 2014, 02:05:46 am »

@ White Stripes - yes it worked on this machine and this version of openSuse [13.1] and this version of wine [1.7.31-388.1-x86_64]. I did try to go back to 1.7.2.1-x86_64. It still did not work.

@ GhostShip - I originally used the one I keep on hand, but have since tried 2 different ones from the https://patch.winmxconex.com/, with the same results.

@nylly444 - Are you talking about "reinstall to a clean 32 bit wineprefix"? If so, yes I have tried that. I also posted @ WineHQ forum and have been trying to follow the advice of dimesio.
https://forum.winehq.org/viewtopic.php?f=8&t=23800

NOTE:At the time just before this problem occured, I remember seeing in: Applications>Wine>Uninstall Wine Programs that wine-gecko ver 2.21 and 2.24 were still installed even tho it had upgraded to ver 2.31. I deleted these two older versions. Could that have caused a problem? Meaning that ver 2.31 cannot work on it's own without the prior versions.

nylly444 · « **Reply #5 on:** November 27, 2014, 04:19:08 pm »

Try not using the installer and try starting the .exe directly, download from the archive : httpss://archive.winmxworld.com/WinMX/Beta/3.54%20betas/winmx354beta4.zip

If that works get the oledlg.dll from the patch site or your backed up original .wine folder (prefix) and add it in and set the override as described in our tutorial.

Btw as dimesio already said each .wine folder represents a separate windows installation, so if you use something other than .wine you need to specify it with every installation and launching of a windows app.
The easiest way is to rename your original folder to something like .wine_backup and let wine create a new .wine folder.

dabud · « **Reply #6 on:** November 28, 2014, 01:31:25 am »

@nylly444
Thanks, but I don't seem to be able to get to that archive link. It says "Website is offline" Error 520 Ray ID: 19029b0ef7560540
Web server is returning an unknown error ' '
Is there somewhere else I can get a copy of winmx354beta4.zip? I'd like to try your suggestion.

dabud · « **Reply #7 on:** November 28, 2014, 02:48:31 am »

Further to cannot get to archives.
I have another machine that I dual boot with Win 7 and openSuse 13.1. I went to openSuse and tried to get to the Winmxworld Archive page and I got there. WTH?
I downloaded the Winmx 3.54b4.zip .
While I was on this other openSuse machine I tried to install Winmx. It did install, with no problems. It is using an older wine version [1.7.11-316.1-x86_64] and an older gecko version [2.24].

I am about to try "starting the .exe directly" as Nylly444 suggested.

And unfortunately it didn't work.

Any ideas where I might get a copy of Wine 1.7.11-316.1-x86_64? All I can get from source_forge is 1.62

White Stripes · « **Reply #8 on:** November 28, 2014, 05:52:21 am »

http://download.opensuse.org/repositories/devel:/cloverleaf/openSUSE_13.1/x86_64/wine-1.7.15-345.2.x86_64.rpm --- closest version to your target i could find... note that this is considered an 'unstable' build....

dabud · « **Reply #9 on:** November 28, 2014, 04:15:58 pm »

Thanks White Stripes

nylly444 · « **Reply #10 on:** November 29, 2014, 07:16:45 pm »

Quote from: dabud on November 28, 2014, 02:48:31 am

Further to cannot get to archives.
I have another machine that I dual boot with Win 7 and openSuse 13.1. I went to openSuse and tried to get to the Winmxworld Archive page and I got there. WTH?

Check your browser preferences - if it's not sending referrers (safe browsing/do not track etc) then it will be blocked.
It checks that it's being access from some winmxworld domain due to lots of japanese sites linking to our downloads from their own sites.
We didn't want them using our bw to provide winmx downloads via their own sites.

White Stripes · « **Reply #11 on:** November 30, 2014, 12:04:20 am »

im guessing that version of wine worked? we need to jot this down for other wine users....

dabud · « **Reply #12 on:** November 30, 2014, 02:30:35 am »

@ White Stripes - Sry have not tried it yet, but I am planning to and will post results.

@Nylly444 - I was able to get to the archives and tried your suggestion,but it did not work.

dabud · « **Reply #13 on:** December 02, 2014, 08:00:41 pm »

@ White Stripes - OK found some time to install earlier version that you linked me to - same results

Quote

getting the Winmx has encountered a serious error... window and could get no further

- I also tried a 1.6 version with no luck there either.
Both times I completely uninstalled Wine64, Wine32, winegecko and wine mono and reinstallled the appropriate packages to go with the version I tried.

White Stripes · « **Reply #14 on:** December 02, 2014, 08:50:00 pm »

...and deleted .wine and any other configuration files?

another option.. https://www.virtualbox.org/ ... do you still have a copy of windows (2k or newer) laying around? ...i know this is a stretch for one application but.... it would work....

White Stripes · « **Reply #15 on:** December 02, 2014, 09:25:45 pm »

i tried it under 1.6 and it worked... until i tried to do the override for the patch in which it faceplanted...

White Stripes · « **Reply #16 on:** December 02, 2014, 10:17:52 pm »

ok... this is interesting ... if i 'browse the c drive' and click winmx.exe directly it runs... if i click any of the shortcuts it made it crashes...

one big difference here... im using 32bit linux/wine (on linux mint) not 64bit.... i cant try 64bit cos i dont have the cpu needed for full virtualization.... i honestly dont know whats going on... other than problems with 64bit or a broken configuration file still hiding somewhere...

White Stripes · « **Reply #17 on:** December 03, 2014, 10:02:34 pm »

@dabud ... did you ever find a way to fix your problem?

dabud · « **Reply #18 on:** December 04, 2014, 01:06:14 am »

@ White Stripes - not yet still working on it. I may just upgrade to openSuse 13.2

Hans-Linux · « **Reply #19 on:** January 11, 2015, 06:46:40 am »

Hi,

I upgraded t from OpenSuse 13.1 to 13.2. Spend 5 days over Xmas / New Year trying to get it to work on my system and setup. To many problems. Audio, printing, and many more.

Then wiped everything, reformatted all disks and did a new install of OS 13.1. did the update. installed wine from Yast and WinMx 35.4 beta 4, opened TCP port 6699 and UDP port 6257. All works fine as before.

Hans