Author Topic: wine on opensus 11.4 (Read 4823 times)

Viper · « **on:** October 10, 2011, 01:26:55 am »

I can;t get winmx to install on opensuse11.4 When I double click on the exe in winefle nothing happens,when i try it in the terminal
nothing happens. I followed your tutorial on these pages. What is wrong?
Thanks

silicon_toad2000 · « **Reply #1 on:** October 10, 2011, 01:34:36 am »

I've found in Debian that sometimes I need to allow the file to be treated as an executable in the properties.
I've always done this via the gui with a right click on the icon.

Viper · « **Reply #2 on:** November 10, 2011, 12:24:18 am »

Hi

I have managed to get wine working on my opensuse computer. I have recently installed
MxMonitor, that works but i can't make the sound work. The test button in winecfg works, howerver
there is no sound when a file download starts or i get a message. Any ideas?

Hans-Linux · « **Reply #3 on:** December 17, 2011, 07:11:25 am »

I am using Wine and WinMx on OpenSuse 11.4 without any problems.

While locked in as a plain user, open YAST, enter the root password, select Software -> Sofware Management. in "Package Listing" type "Wine" .
You will see and select (tick):
Wine
Wine-32bit
Wine-Gecko
Wine-mp3

The then click on the "Apply" button.

When done, you will find your "C" drive under /home/"your username"/.wine/dosdevices/c:
or ~/.wine/drive_c

I never tried sound to work under wine. My PC has no speaker.

Install a Winamp or something like VLC for Windows to test if your sound system is accessible through Wine.

Hans

Lagerlout666 · « **Reply #4 on:** December 18, 2011, 01:44:00 am »

The only way i can think of to test that is to open moni using a terminal window. Write

Code: [Select]

wine /path to/Mxmoni.exe
and hit enter

Dont close the terminal window as the program will close also but keep an eye out of what wine outputs into the terminal. test sounds etc. I know that wine didnt use to play well with pulse audio, and by changing a setting to ALSA fixes sound in some older games. But this was a problem i suffered along time ago on ubuntu. And may or may not be a avenue for you too look down. If the output in the terminal doesn't help you first of course.