LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Wine-1.1.32 does not open a .EXE under Fedora 12 64 bit (https://www.linuxquestions.org/questions/linux-software-2/wine-1-1-32-does-not-open-a-exe-under-fedora-12-64-bit-782070/)

lppatmore 01-13-2010 06:50 PM

Wine-1.1.32 does not open a .EXE under Fedora 12 64 bit
 
1 Attachment(s)
Wine version 1.1.32. When I click the icon in the file manager, I get the busy cursor for a few seconds, nothing more. When I use the Wine Add/Remove Programs utility, I get an obscure error message (see the attached screenshot).

The system is Fedora 12 on a Lenovo ThinkPad R61. The program I am trying to install is called MyOrgan, a now unmaintained Windows program that emulates a pipe organ with MIDI. I have used this in Fedora (32 Bit before with no issues. Do the symptoms or GUI message look familiar. I can post any other information that could be useful at a whim.

Any assistance would be appreciated.

Thank you,
Luke P. Patmore

jefro 01-13-2010 09:34 PM

How did you get wine?

DragonSlayer48DX 01-13-2010 10:38 PM

Hmmm... Yeah, that error message is obscure, alright. Tells nobody anything meaningful. :(

On which version of Fedora and Wine did it last work correctly? IIRC, Frank's website states that if a program stops working after upgrading Wine, you may need to revert back to the older version. Just like with Windows, as Wine is upgraded to work with newer software, support for older programs is diminished.

Personally though, I think it may be an issue with trying to run the now-obsolete 32-bit program on a 64-bit system. You may need to find a newer version, or settle for something similar that will work.

GrapefruiTgirl 01-13-2010 10:47 PM

I don't use Wine, but (just an idea) I wonder if, like with a lot of applications on Linux, what if you start Wine from the command line so that you can see the console output as it runs?
This may provide much more (likely obscure) information that could maybe give a clue as to what's going wrong behind the scenes.
Like I said though, this is just an idea -- I have never used Wine nor Win apps for some years now :) but you would probably get *something* more than an empty Error Box.

Sasha

lppatmore 01-15-2010 07:11 PM

Thank you for the suggestion to run it in the terminal, it ran fine there.

This is the terminal output:

Code:

[luke@ainulindale SecureGuard]$ wine MyOrgan_1_0_6.exe
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
fixme:shell:SHAutoComplete SHAutoComplete stub
Unknown media type in type 'unknown/mime-type'

fixme:shell:DllCanUnloadNow stub
fixme:shell:DllCanUnloadNow stub
fixme:shell:DllCanUnloadNow stub
fixme:shell:DllCanUnloadNow stub
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)


GrapefruiTgirl 01-15-2010 07:31 PM

Ok, so I don't really know what I'm looking at there, but I understand the word "FixMe" ;)

Did your organ program work ok? If so, then it looks like a Wine bug(s) you encountered when trying to do what you were doing up there in Post#1 with the GUI.
Or if your program did NOT work, I'd be looking through Wine mailing list or support forum for similar issues and/or for signs of the "FixMe" and other console output you got there.
Finally, if you did not get the organ program to work, follow DragonSlayer's advice up there, and try some different versions of Wine; AFAIK it changes often, so some versions may work and some not.

Sasha

cantab 01-15-2010 09:25 PM

Wine always spits out a LOT of 'fixme', making it hard to know what is actually wrong.


All times are GMT -5. The time now is 06:26 AM.