It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Matruchus: Can anybody help me out with a mono problem. Since I deinstalled Winetricks and reinstalled Wine and Banished I can't get the dxsdk_june2010 package installed which means there is no sound in Banished. Basically its says that there is no mono installed and that the 64 bit version of os is not supported. As much as I understand mono usually fixes that issue.

These are the steps I took:
- deinstall Winetricks,
- deinstall Wine
- physically erase Wine folder,
- sudo apt-get --purge autoremove
- sudo apt-get autoclean
- sudo apt-get clean.

After that reinstalled.
For winetricks you might want to manually update it to the latest version if you don't already have it.

Could you run "winetricks --version" for me and see what you get?
avatar
JudasIscariot: For winetricks you might want to manually update it to the latest version if you don't already have it.

Could you run "winetricks --version" for me and see what you get?
20160425 - after I reinstalled Mint and installed Wine from PPA it still shows that I have a 64 bit version of Wineprefix. It seems all wine versions automatically install a 64 bit wineprefix on Mint.
avatar
JudasIscariot: For winetricks you might want to manually update it to the latest version if you don't already have it.

Could you run "winetricks --version" for me and see what you get?
avatar
Matruchus: 20160425 - after I reinstalled Mint and installed Wine from PPA it still shows that I have a 64 bit version of Wineprefix. It seems all wine versions automatically install a 64 bit wineprefix on Mint.
OK, so you have an older version of Winetricks...I suggest getting the latest version here: https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks (cool thing about this version is that winetricks now comes with its own update function :D)

As for the 64-bit prefix thing have you tried :

WINEPREFIX=$HOME/.wine32 WINEARCH=win32 winecfg wineboot

in terminal?
avatar
Matruchus: 20160425 - after I reinstalled Mint and installed Wine from PPA it still shows that I have a 64 bit version of Wineprefix. It seems all wine versions automatically install a 64 bit wineprefix on Mint.
avatar
JudasIscariot: OK, so you have an older version of Winetricks...I suggest getting the latest version here: https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks (cool thing about this version is that winetricks now comes with its own update function :D)

As for the 64-bit prefix thing have you tried :

WINEPREFIX=$HOME/.wine32 WINEARCH=win32 winecfg wineboot

in terminal?
You pointed me to the same version of Winetricks I already have.

Otherwise this is what I get in terminal for 64 bit prefix
WINEPREFIX=$HOME/.wine32 WINEARCH=win32 winecfg wineboot fixme:winediag:start_process Wine Staging 1.9.9 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory

Edit: According to this page here:https://appdb.winehq.org/objectManager.php?sClass=version&iId=3754&iTestingId=18546
If I get an error that says this: This product is not supported on a 64-bit operating system. Setup will now exit. - It means that I have WoW64 Wine installed?
Post edited May 13, 2016 by Matruchus
avatar
JudasIscariot: OK, so you have an older version of Winetricks...I suggest getting the latest version here: https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks (cool thing about this version is that winetricks now comes with its own update function :D)

As for the 64-bit prefix thing have you tried :

WINEPREFIX=$HOME/.wine32 WINEARCH=win32 winecfg wineboot

in terminal?
avatar
Matruchus: You pointed me to the same version of Winetricks I already have.

Otherwise this is what I get in terminal for 64 bit prefix
WINEPREFIX=$HOME/.wine32 WINEARCH=win32 winecfg wineboot fixme:winediag:start_process Wine Staging 1.9.9 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory

Edit: According to this page here:https://appdb.winehq.org/objectManager.php?sClass=version&iId=3754&iTestingId=18546
If I get an error that says this: This product is not supported on a 64-bit operating system. Setup will now exit. - It means that I have WoW64 Wine installed?
If you had a WoW64 version of Wine then you would not have seen the message "This product is not supported on a 64-bit operating system" since a WoW64 build of Wine lets you run 32-bit and 64-bit applications in one prefix.

As for winetricks, can you check if this works for you?

winetricks --self-update
OK I managed to figure out the problem with Skyshine's BEDLAM and its Options menu not closing.

Game: Skyshine's BEDLAM Redux
Installer MD5: 9FA7FDB957941EB0B9E6B53F6A9EA4A3 setup_skyshines_bedlam_redux_2.0.0.2.exe
30CDB581D87CC26574C5BBB935E897FA setup_skyshines_bedlam_redux_2.0.0.2-1.bin

WineHQ AppDB link:https://appdb.winehq.org/objectManager.php?sClass=application&iId=17120

Distro: Antergos 64-bit
Kernel version: 4.5.4-1
Graphics card: Nvidia GeForce GTX 560Ti
Graphics driver & version: Proprietary 364.19
Wine version(s) tested: Wine 1.9.9

Install notes: Install and disable ALL xinput DLLs in winecfg for the game.
How well does it run: Almost perfect. You may experience the sound just cutting out completely until you exit the game and start it up again
Details: I played as the Mutants and as Humans before dying twice to some random thing or another. I fought at least 10-15 battles and everything worked.

For those of you who see the Options menu right when you start the game via Wine, open up winecfg, add the Skyline's Bedlam executable, and set all 4 xinput DLL files to "disabled" in order to get rid of the issue where the Options menu will not go away.

I had the sound drop put on me once just after the intro where some guy was sending out my character to go out into the wasteland towards Aztec City. I did skip the intro entirely in another playthrough and the music seemed to work fine throughout my time with the game.
Post edited May 13, 2016 by JudasIscariot
avatar
Matruchus: Otherwise this is what I get in terminal for 64 bit prefix
WINEPREFIX=$HOME/.wine32 WINEARCH=win32 winecfg wineboot fixme:winediag:start_process Wine Staging 1.9.9 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
well, that's at least a very clear error message :)

google says you are missing some packages.

sudo apt-get install p11-kit-modules:i386 libp11-kit-gnome-keyring:i386

then try again
Post edited May 13, 2016 by immi101
avatar
Matruchus: Edit: According to this page here:https://appdb.winehq.org/objectManager.php?sClass=version&iId=3754&iTestingId=18546
If I get an error that says this: This product is not supported on a 64-bit operating system. Setup will now exit. - It means that I have WoW64 Wine installed?
avatar
JudasIscariot: If you had a WoW64 version of Wine then you would not have seen the message "This product is not supported on a 64-bit operating system" since a WoW64 build of Wine lets you run 32-bit and 64-bit applications in one prefix.
hmm unless the error isn't coming from wine, but from the installer. Wine happily starts the 32bit installer, but the installer checks for a 64bit windows and throws the error.. WoW64 or not doesn't matter.
that would be my guess from what's written on that appdb page.
avatar
JudasIscariot: If you had a WoW64 version of Wine then you would not have seen the message "This product is not supported on a 64-bit operating system" since a WoW64 build of Wine lets you run 32-bit and 64-bit applications in one prefix.
avatar
immi101: hmm unless the error isn't coming from wine, but from the installer. Wine happily starts the 32bit installer, but the installer checks for a 64bit windows and throws the error.. WoW64 or not doesn't matter.
that would be my guess from what's written on that appdb page.
Maybe? I am not sure as I have not seen too many 32-bit versions of installers from winetricks fail in a strictly 32-bit prefix.

If the prefix is strictly a 32-bit one and a 32-bit installer fails on it then it sounds like a potential Wine bug and should be reported accordingly to their BugZilla...
Post edited May 13, 2016 by JudasIscariot
avatar
JudasIscariot: Trust me, if I can compile Wine from source on Mint you can do it too :)
That's what post #1 is mostly about (compiling Wine on Mint, not you :p).

avatar
Matruchus: Otherwise this is what I get in terminal for 64 bit prefix
WINEPREFIX=$HOME/.wine32 WINEARCH=win32 winecfg wineboot fixme:winediag:start_process Wine Staging 1.9.9 is a testing version containing experimental patches.
What Windows version do you have set in the Banished prefix? Set it to XP if it's different. Have you tried stock Wine 1.9.9? If not try it with a new prefix:
WINEPREFIX=$HOME/.prefixBanished WINEARCH=win32 wine cmd
Post edited May 14, 2016 by Gydion
avatar
immi101: hmm unless the error isn't coming from wine, but from the installer. Wine happily starts the 32bit installer, but the installer checks for a 64bit windows and throws the error.. WoW64 or not doesn't matter.
that would be my guess from what's written on that appdb page.
avatar
JudasIscariot: Maybe? I am not sure as I have not seen too many 32-bit versions of installers from winetricks fail in a strictly 32-bit prefix.

If the prefix is strictly a 32-bit one and a 32-bit installer fails on it then it sounds like a potential Wine bug and should be reported accordingly to their BugZilla...
wait ...
i feel we're somehow talking past each other. Or I just haven't had enough coffee this morning :p
wasn't the problem that the installer failed in a 64bit prefix?

Which could either mean that the installed wine has no 32bit support (no WoW64). Solved by installing the 32bit wine as well or compiling 32bit wine yourself as you said.
- or -
The installed wine has WoW64 support, but the installer has a stupid check that blocks installing in a 64bit prefix. A WoW64 build of wine will still create a 64bit prefix by default and is recognized as a 64bit windows, despite being able to execute 32bit binaries. This can be solved by creating a 32bit prefix via WINEARCH=win32. (and fixing the errors that pop up there)
Game: Turok (aka Turok EX, Turok: Dinosaur Hunter - Steam HD Edition)
Installer MD5s: setup_turok_2.2.0.7.exe = e3a51ba0889a2f26c29403aa90893be6
WineHQ AppDB link: n/a (WineHQ AppDB Entry is for the original PC port, not the EX/Steam HD remastered edition)
CodeWeavers link: n/a
Distro: Mac OS X El Capitain 10.11.4
Kernel version: Darwin 15.4.0 (Build 15E65)
Graphics card: nVidia GeForce 320m / Intel HD 5000 Graphics
Graphics driver & version: OS Default
Wine version(s) tested: WINE 1.9.9 via Wineskin
Install notes: Used the latest version as of May 15, 2016 (1.4.7 / GOG-7)
How well does it run: Almost perfectly (So far)
Details: Tested in fullscreen 1366 x 768, with Mac driver enabled. The game works almost flawlessly, with the exception of some occaisional lagginess on some levels. No extra configuration or installations were necessary.
Post edited May 15, 2016 by rampancy
avatar
rampancy: Here's my current progress on Shadows of the Empire...

Game: Star Wars: Shadows of the Empire
How is this coming along? If Gall Spaceport plays normally for you I would say it's a success under OS X at least.
avatar
rampancy: Here's my current progress on Shadows of the Empire...

Game: Star Wars: Shadows of the Empire
avatar
Gydion: How is this coming along? If Gall Spaceport plays normally for you I would say it's a success under OS X at least.
...because I suck at this game I'm still plodding along in the starting phase of the Ord Mantell junkyard level. Is there a specific bug/glitch I need to look out for?
avatar
rampancy: Is there a specific bug/glitch I need to look out for?
Borked physics. Sliding all over the place when going downhill.