Page 1 of 1

No joy with wine on Mepis 6.5 RC2

PostPosted: Sun Mar 18, 2007 9:49 am
by Cyber-Wizard
I've been running NewsBin Pro V4.22 Build 4495 on Suse 10.1 for a while now and I've been very happy, I don't recall the wine version that I was running. Yesterday I decided to reload my PC with Mepis V6.5 to reclaim some of the speed that Suse/KDE were sucking out of it.

To get things back in business I installed wine via apt-get (it claims to be wine V0.9.9 although WineHQ claims the latest release is V0.9.33). I decide to move up in the world at the same time and install NewsBin V5.33. I left my .wine directory as it was in /home so all of my dll's etc would stay in place. The install seems to have gone smoothly enough although it winds up in Program Files/Newsbin as opposed to Program Files/nbpro where V4.22 was installed, no big deal. Now when I try to launch nbpro I get some error messages involving dll's

wine: Call from 0x4017cf to unimplemented function MFC42.DLL.6491, aborting
wine: Unimplemented function MFC42.DLL.6491 called at address 0x4017cf (thread 0009), starting debugger...
WineDbg starting on pid 0x8
Unhandled exception: unimplemented function MFC42.DLL.6491 called in 32-bit code (0x7ff9c137).


Clearly there is much more to the debug output, but this is the part that I've started dealing with. I recopied all of my .dll's via 'Net downloads to both windows/system and windows/system32 but I'm still not having any luck. Has anyone got any suggestions where I go from here?

More Info

PostPosted: Sun Mar 18, 2007 10:36 am
by Cyber-Wizard
As an added little tidbit...

Given that I had left my /home directory untouched, I tried firing up the existing 4.22 installation that was sitting in my Program Files/nbpro directory and it worked like a charm.

PostPosted: Sun Mar 18, 2007 12:26 pm
by DThor
As a test, rename your .wine directory and reinstall, remembering to copy the correct dll's over. I wouldn't assume the SUSE-approved wine distribution is precisely the same as another distro's.

[EDIT] oh, nm, I see it's not a distro, it's a desktop. Then sorry, I dunno what the problem is. It's probably a wine + mephis issue.

DT

Re: No joy with wine on Mepis 6.5 RC2

PostPosted: Mon Mar 19, 2007 5:28 am
by rein
Cyber-Wizard wrote:wine: Call from 0x4017cf to unimplemented function MFC42.DLL.6491, aborting
wine: Unimplemented function MFC42.DLL.6491 called at address 0x4017cf (thread 0009), starting debugger...
WineDbg starting on pid 0x8
Unhandled exception: unimplemented function MFC42.DLL.6491 called in 32-bit code (0x7ff9c137).
[/i]


Wine has loaded a native MFC42.DLL, but this dll is missing a function needed by newsbin.
Use a more recent version, one from Win2k or XP will do fine.

PostPosted: Mon Mar 19, 2007 6:10 am
by wiredog
or a older one, when I used the file from a vista install I got the same errors. Using one from XP works fine

Fresh DLL's

PostPosted: Mon Mar 19, 2007 9:19 pm
by Cyber-Wizard
I replaced all of the .dll's with ones that I downloaded from the 'Net as soon as I completed the installation. The ones that were already in my nbpro directory had been the ones that were downloaded previously so I copied them over to my Newsbin directory. Does this newer version of wine or Newsbin require a newer .dll? Does anyone have a version number of the one that is required? I don't have an XP installation in the house to compare versions against. I believe that I'm running 4.21.71 without any luck.

Re: Fresh DLL's

PostPosted: Tue Mar 20, 2007 1:26 am
by rein
Cyber-Wizard wrote: The ones that were already in my nbpro directory had been the ones that were downloaded previously so I copied them over to my Newsbin directory. Does this newer version of wine or Newsbin require a newer .dll?


It is newsbin that calls the missing function.

Run like
WINEDEBUG=+loaddll wine nbpro.exe

to see which dll from which location is actually used.

Or try the latest beta, I am running 5.34B7 without problems. This one uses a MFC80.DLL that gets actually installed by the installer in the newsbin directory. No other native dll's seem to be used.

PostPosted: Tue Mar 20, 2007 11:05 am
by DThor
Just to clarify, as mentioned in the sticky in the forum, those dll's *have* to come from a valid XP install. In my experience the "freely available" ones that come from linux wine sites don't work. According to other users vista dll's don't work either.

DT

Now it's clear

PostPosted: Fri Mar 23, 2007 8:07 pm
by Cyber-Wizard
Now I'm getting the gist of it. I was missing the "HAVE to come from XP" part. I'll try to get my hands on one as soon as possible and report back.

Still no luck

PostPosted: Sun May 13, 2007 9:39 am
by Cyber-Wizard
It's taken me some time as I had some minor disagreements with Mepis. I wound up rebuilding again with SUSE 10.1. As before, my 4.22 installation just works, but my new installation is still giving me the same error as seen above.

I copied my msvcp60.dll and mfc42.dll from an XP Pro SP2 installation(my work laptop), but nothing seems to have changed.

It's not a critical issue for me as my 4.22 installation seems to be working just fine, but now that I've had a taste of the 5.33 version with it running in an XP Pro VM on my work laptop, I'd love to start using it full time at home.

If anyone has any other suggestions I'll try to tackle them quicker this time.

Got it

PostPosted: Sun May 13, 2007 9:45 am
by Cyber-Wizard
I just reinstalled 5.33 via Wine and for some reason it worked this time. I don't believe that I did anything different, but it just works.

Thanks to everyone who helped get me on the right path!!

Spoke too soon

PostPosted: Sun May 13, 2007 10:02 am
by Cyber-Wizard
I was able to get it running as root but not a user.

It turned out that it was a permissions issue on msvcp60.dll.

Just for the sake of anyone who runs across the same issue..

I had copied the files to my machine remotely via my Linux Laptop as root. With the msvcp60.dll being owned by root, I couldn't utilze the file as a user. From the command line I ran an ls -l on the .wine/drive_c/Program Files/windows/system/ directory and found the following:

-rw-r--r-- 1 [Username] users 1028096 2007-05-13 08:42 mfc42.dll
-rw------- 1 root root 413696 2007-05-13 08:42 msvcp60.dll


To correct this, the msvcp60.dll line should look much like the mfc42.dll line above it.

While there are easy ways to fix this with a single command, I'll provide the step by step for clarity.

To fix the ownership and group of the msvcp60.dll file I ran (as root):
chown [Username] msvcp60.dll
chgrp users msvcp60.dll


To make sure that the file is readable by the correct users and group run (as root):
chmod 644 msvcp60.dll

This is probably pretty basic stuff for most of the users here, but I have a pet peeve about finding a forum post that outlines the same problem I'm having with no one ever having posted the solution. Hope this helps somebody else out!

PostPosted: Sun May 13, 2007 11:34 am
by DThor
Just a heads up - most SUSE users nowadays would be installing 10.2 - I recently did a brand new install, and apart from a couple of minor drawing issues you don't even need to fiddle with dlls anymore. Just run the installer through wine, making sure you're not reusing an old .wine directory, making a new one, and it installs fairly decent new dlls that seem to do the trick. Redraws and other speed issues seem to be reduced, too.

DT

PostPosted: Mon May 14, 2007 3:32 am
by rein
DThor wrote:Just a heads up - most SUSE users nowadays would be installing 10.2 - I recently did a brand new install, and apart from a couple of minor drawing issues you don't even need to fiddle with dlls anymore.

DT


That is true for 5.34. But Cyber-Wizard uses 5.33 that still needs the MFC42 dll.

PostPosted: Mon May 14, 2007 9:55 am
by DThor
The I'd say it's upgrade time. :)

DT

PostPosted: Fri May 18, 2007 7:26 am
by Cyber-Wizard
Agreed!!