SatSYNC.exe fails to work

[NickF]

Hi All
I'm a totally new user to Wine, so please forgive what may be a relatively naïve question!
I'd be really grateful if someone can point me in the right direcvtion, because I've little idea how to proceed.
I've been trying to use SatSYNC.exe - a Windows program for loading my GPS made by SatMap systems ltd. - on Linux Peppermint 4 (Ubuntu derivative).
Please note that I HAVE already loaded the full MONO package - but it still suggests I need Mono. Why?
Here is the error log when I run in the terminal:

$ wine "C:\Program Files\Satmap Systems Ltd\SatSYNC\SAtSYNC.exe"
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"configSections" in state 1
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"sectionGroup" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"section" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"userSettings" in state 1
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"Satmap.SatSYNC.UI.Properties.Settings" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 3
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 3
wine: Install Mono for Windows to run .NET 2.0 applications.

Advice gratefully received. Thanks.

[dimesio]

Please note that I HAVE already loaded the full MONO package - but it still suggests I need Mono. Why?

What exactly do you mean by "the full MONO package"? If you mean Linux Mono, that won't work with Wine. You have to install wine-mono; Ubuntu does package it.

[NickF]

I installed the 'Mono-complete' package using the Peppermint/Ubuntu Software Manager.
It makes no mention of Wine - so I would think you are right, it is probably Linux mono.
But, there is also an 'Ubuntu-mono' package - which I haven't loaded.

Search in the software manager as I will, I can't find any mention of wine-mono.
I think PM4 is based on the latest Mint, so maybe not quite the same as Ubuntu itself - I'm unsure.

Can I get wine-mono somehow else (from a ppa ?)

Thanks

[NickF]

did my reply go missing?

[dimesio]

New forum members' first three posts have to go through moderation. It's the only effective way to keep spammers out.

Ubuntu packages wine-mono. https://launchpad.net/~ubuntu-wine/+archive/ppa

If the Ubuntu wine-mono package doesn't work on your system, you can install wine-mono manually. http://wiki.winehq.org/Mono

[NickF]

As it happens, I have just added the Ubuntu-wine repository using sudo ... in the terminal, because I was getting a notice about unverified (or something like that) sources when I added the ppa manually to the software updater. That now works and has updated (to 1.6, I think).

I'm unclear if wine-mono is included in that automatically - or do I have to add it somehow?

Thanks

[NickF]

I'm assuming that my actions to add Ubuntu-wine is what you suggest is necessary (and I don't have to add wine-mono separately).
I have just tried again to run SatSync.exe from the terminal, result:
1. Exactly (I think) the same set of Fixme: lines as reported above, BUT without the request to install MONO.
2. A long set of Fixme:wincodecs: errors, the last few lines posted now:
fixme:wincodecs:PngDecoder_Block_GetCount 0x188df60,0x32f5e8: stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x188df60,0x32f5e8: stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x188df60,0x32f5e8: stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x188df60,0x32f5e8: stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x188df60,0x32f5e8: stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x188df60,0x32f5e8: stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x188df60,0x32f5e8: stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x188df60,0x32f5e8: stub
err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded
fixme:wincodecs:PngDecoder_Block_GetCount 0x157e9e0,0xa25e4a8: stub
(Obviously I could provide the whole output)

The other change is that the Satsync initial 'logo' page appears on screen = a small step forward!

Please - can you advise how I move forward from here.

many thanks

[dimesio]

Try winetricks windowscodecs.

[NickF]

It would help if you could spare me a few more words - I feel like I'm sinking under layers of stuff and need some guidance!
However, from the WineTricks page on WineHQ:

Ubuntu Users
If you have followed the instructions at http://www.winehq.org/download/deb to install the latest Wine, then you should already have winetricks installed as its own package.
Using winetricks
Once you've obtained winetricks you can run it simply by typing sh winetricks at the console.

but I just get 'can't open winetricks'
Presently I have little idea what 'winetricks' is, no idea how to get 'windowscodecs' and now can't be sure whether 'winetricks' is loaded or not!

[NickF]

Despite the failure of "sh winetricks" I have now spotted 'Winetricks' on the menu - so it is loaded.
Working my way rather blindly forward, I have found the opportunity to load DLLs - and in particular, Windowscodecs.
Unfortunately I simply get another problem:

sha1sum mismatch! Rename /home/fane/.cache/winetricks/windowscodecs/wic_x86_enu.exe and try again.

Did as it requests - but just got the same error again. Nothing is simple!
What now??????

[oiaohm]

NickF somethings ubuntu people really should not package. At least the way they do.

http://wiki.winehq.org/winetricks use the getting winetricks and use the newest version.

If you have a old version of winetricks and a .exe or something has been updated winetricks will call it defective over and over again.

Basicically the sh winetricks instruction was intentional. The winetricks include with ubuntu is horiblely out of date.

Winetricks itself is a single script file.

[dimesio]

Try updating winetricks; the version that ships with your distro may not be the latest. You can get it from http://winetricks.googlecode.com/svn/tr ... winetricks.

[NickF]

Many thanks for the help - I've update Winetricks and think I loaded windowscodec OK - that error has vanished, so I'm hopeful.

I now get a long list of errors - which I have piped to a file (can I upload that anyhow?)
To summarise, I get the same 'L' value and settings errors as before, followed by:

fixme:wer:WerRegisterMemoryBlock (0x530aa498 6144) stub
fixme:wer:WerRegisterMemoryBlock (0x530a4000 4) stub
err:menubuilder:convert_to_native_icon error 0x88982F81 initializing encoder
err:menubuilder:convert_to_native_icon error 0x88982F81 initializing encoder
err:menubuilder:convert_to_native_icon error 0x88982F81 initializing encoder
err:menubuilder:convert_to_native_icon error 0x88982F81 initializing encoder
err:menubuilder:convert_to_native_icon error

and a lot more like the last few lines, then a very long, but similar set ending:

fixme:rpc:NdrStubCall2 new correlation description not implemented
fixme:ole:NdrCorrelationFree (0xa27e20c): stub
fixme:ole:NdrCorrelationInitialize (0xa27e20c, 0xa27de0c, 1024, 0x0): stub
fixme:rpc:NdrStubCall2 new correlation description not implemented
fixme:ole:NdrCorrelationFree (0xa27e20c): stub

How might I proceed now?
Again, help and suggestions much appreciated - as a 'newcomer' this isn't an easy road.

[NickF]

It would be great if someone could spare a few minutes to attempt an answer.
At present the previous help is simply wasted because I'm unable to make any progress without some guidance.

[dimesio]

There's nothing obvious from the last output you posted. Try the latest development release.