Author |
Topic |
|
kareemix
Germany
2 Posts |
Posted - 03/01/2016 : 09:11:59
|
Hi there,
I want to install my GMC 320+ v4 in operating Ubuntu 14.04 (LTS).
WINE says installation sucsessful. The installed "GQ GMC Data Viewer" appears in the menu of Ubuntu, but after clicking and a few seconds with a sandglass nothing happens.
I don't think the problem is a driver because the program doesnt start....
Pleas help me :)
Cheers, Max |
|
Reply #1
ZLM
1261 Posts |
Posted - 03/01/2016 : 21:28:58
|
can you try the Data Logger PRO? |
|
|
Reply #2
kareemix
Germany
2 Posts |
Posted - 03/02/2016 : 14:16:58
|
Yes. Same problem. |
|
|
Reply #3
ZLM
1261 Posts |
Posted - 03/02/2016 : 19:43:09
|
Those software works with all true Windows and without problem. The software is 32bit application.
|
|
|
Reply #4
zArcher
1 Posts |
Posted - 05/14/2016 : 12:57:57
|
I got my GMC 320+ v4 running using WINE on Ubuntu 14.04 just fine (including submission of data to gmcmap.com).
To make it work, you need to do two things:
1. Fix the missing mfc42 dependency issue (this is needed but doesn't come with the default install of WINE).
2. Get the USB to serial adapter to work in WINE.
The good news is that both are easy to do and the whole setup will take you about 5 minutes.
To fix the mfc42 dependency, you can run these commands: sudo add-apt-repository ppa:ubuntu-wine/ppa winetricks mfc42
To make the USB to serial adapter work, it is no different than doing so for any other USB to serial device using WINE. A good set of instructions can be seen here: https://onetransistor.blogspot.com/2015/12/wine-serial-port-linux.html
Also, just to make life easier when using WINE, I thought I would share this: When you try to run a program in WINE and it doesn't work, you can often learn what is wrong if you look at the error message that it displays in the terminal. So, instead of opening the program using the GUI, pull up a terminal, browse to the directory where the .EXE is located, and run "wine nameOfProgram.exe" and look at the error message that is displayed. That is how I found the mfc42 dependency issue here. |
|
|
|
Topic |
|
|
|