Running Wilbur through Wine on Linux Mint 64bit

[atmycrossroads]

Ive downloaded the 64 bit version of Wilbur from fracterra but Im unable to get it to run on Linux Mint 17.2
When I click the exe the wine program loader appears in my taskbar, sits there for a bit "thinking" and then vanishes.


Is anyone successful at running Wilbur in a similar environment? I read on another thread that it works with wine.

Any help is appreciated.

[ChickPea]

I run Ubuntu but haven't dabbled in Wilbur. I tried to download it quickly there, but my experience was pretty much the same as yours, i.e. nothing happened! I did find this thread, which doesn't sound too optimistic (although it was from 2012, so perhaps things have changed. Or perhaps not.)

http://www.cartographersguild.com/sh...ad.php?t=19651

Maybe Johnvanvliet has better info...?

[johnvanvliet]

it runs in the current development wine 1.7.55

install the 32 bit version of wine !!!
the 64 bit really dose not work well. That and seeing as 99.999% of all windows 64 bit programs ARE the 32 bit code just built on a 64 bit machine

and use the 32 bit wilbur

getting a mixed 64/32 bit dll's set up is rather hard to do easily

but if you already have wine 1.7.55 x86_64 installed
still use the 32 bit wilbur

but

you really SHOULD have a error from the terminal about the missing 64 bit dll's
my 32 bit install

cd  "~/.wine/drive_c/Program Files (x86)/Wilbur1.83"
wine Wilbur1.exe

DO NOT forget the QUOTES!!!! --`Program ( BLANK SPACE ) Files ` has blank spaces in the name




the current mint should have 1.7 in the repos

apt-get update 

apt search wine

1.7 should be called "wine-development" or "wine64-development"

[atmycrossroads]

Hi ChickPea, thanks for the info and the Summoning of the John!

John, Thanks for the info. Im using 32bit Wilbur and here is the output of my cli. It apparently doesnt like my Nv install.

~/.wine/drive_c/Program Files (x86)/Slayton Software/Wilbur 1.83 (32-bit) > err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instea

[johnvanvliet]

Just a very long time user of Linux OS's
and i tossed Microsoft to the trash can in 2005 when i moved to Fedora 4 full time back in `05

is this a laptop by chance ?

wine really NEEDS a 3d card to emulate dirextx using opengl ON the card

what card yo you have and from the error i am assuming you are not using the open Nouveau driver

did you replace that with the nvidia.deb from the mint repos
OR
use the NVIDIA.run ( 352.55 is current for the current cards )

one reason for the error is a minor bug

try this change to Xorg, edit (as root) /etc/X11/xorg.conf and add the following line in the SCREEN - options section

 Option         "metamodes" "1920x1080 +0+0"

copy of mine

Section "Screen"

    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "CRT-0"
    Option         "metamodes" "1920x1080 +0+0; 640x480 +0+0; 640x480 @1919x1080 +0+0"
    Option         "SLI" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

then reboot


also have a look at the script " winetricks "
http://wiki.winehq.org/winetricks
this easily adds needed things simply

[atmycrossroads]

That seemed to make Wilbur a happy camper. Thanks john!

[atmycrossroads]

Well...Wilbur is definitely booting...but Im experiencing constant lock ups when using the paint brushes.
Im still seeing the "Broken NVIDIA RandR detected, Falling back..."
Even after applying your Xorg change, John.

To answer your questions: I used the built in Driver manager of Mint to download the NVIDIA drivers and use that app as well to set them rather than the Nouveau.

Here is the console output after a lockup.

wine /home/mememe/.wine/drive_c/Program\ Files\ \(x86\)/Slayton\ Software/Wilbur\ 1.83\ \(32-bit\)/Wilbur1.exe
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
fixme:thread:GetThreadPreferredUILanguages 52, 0x32fadc, 0x32fc54 0x32fae4
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:shell:SetCurrentProcessExplicitAppUserModelID L"Wilbur.AppID.NoVersion": stub
fixme:thread:GetThreadPreferredUILanguages 52, 0x32f98c, 0x32fb04 0x32f994
fixme:process:RegisterApplicationRestart (L" /RestartByRestartManager:B92EA78C-0480-471c-B4F8-ACB2476ACFEA",0)
fixme:process:RegisterApplicationRecoveryCallback 0x7306a3, (nil), 5000, 0: stub
fixme:win:LockWindowUpdate (0x100be), partial stub!
fixme:win:LockWindowUpdate ((nil)), partial stub!
fixme:uxtheme:BufferedPaintInit Stub ()
fixme:uxtheme:BeginBufferedPaint Stub (0x1004b 0x32d81c 2 (nil) 0x32d728)
wine: Unhandled page fault on write access to 0x00000000 at address 0x340a85 (thread 0009), starting debugger...
err:module:import_dll Library dbghelp.dll (which is needed by L"C:\\windows\\system32\\winedbg.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\windows\\system32\\winedbg.exe" failed, status c0000135

Sorry to be a pest. Wilbur is doing what I need it to do but these constant crashes are annoying to say the least.

[johnvanvliet]

a few "red herrings"

the " xrandr12_init_modes" is really a non issue - the metamode in the xorg.conf takes care of that
all the " fixme " warnings are just that

THIS is however a issue

err:module:import_dll Library dbghelp.dll (which is needed by L"C:\\windows\\system32\\winedbg.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\windows\\system32\\winedbg.exe" failed, status c0000135

this missing file "dbghelp.dll"

that SHOULD have been installed with wine
-- 64 bit
/usr/lib64/wine/dbghelp.dll.so
-- 32 bit
/usr/lib/wine/dbghelp.dll.so

i am guessing you did not do a "apt-file search" for the missing wine file
or synaptic search

my KVM install of Debian 8 has "libwine-development" 1.7.52

and a apt-file search for what package HAS this *.so in it
is "libwine-development"

i use a real root account with a different password for root than the first non root user
-- so i USE " su and " su - " and DO NOT use "sudo"

su -
apt-get update
---
apt-get install apt-file
---
apt-file update 
---
apt-file -s dbghelp.dll.so
---

the search shows "libwine-development"

[atmycrossroads]

Well...dropping to su and running the

apt-file -s

did nothing but bring up a usage sheet.
However, running

apt-file search

produced:

apt-file search dbghelp.dll.so
picasa: /opt/google/picasa/3.0/wine/lib/wine/dbghelp.dll.so
wine1.6-amd64: /usr/lib/x86_64-linux-gnu/wine/dbghelp.dll.so

I dont have a picasa directory in opt. I do have a wine directory in the path specified and there is a dbghelp.dll.so file there.


Im unable to find any apt package named libwine nor libwine-development

[johnvanvliet]

" wine1.6-amd64 "


You need to have installed the CURRENT!!! wine 1.7.5? development version

the OLD 1.5 and 1.6 will not run wilbur well and you will have problems
see that 2012 post in the link in post #2

wine only runs "some" Microsoft programs ( do to patent litigation PROBLEMS caused by Microsoft)