NOTE: As of Wine 1.7, there still was not USB support for ANY devices without some substantial hacking work. This process is just to test Spectravue processing recorded data files. Note the comment from Andy- G3TDY that starts siqs-ftdi then connects SpectraVue to that server–thanks Andy!
SpectraVue 3.30 and newer changed to using Visual Studio 2010. As a result, you will need to install:
then you will be able to run SpectraVue 3.30 and newer under WINE on Ubuntu and other Linux. (Tested with WINE 1.6.2).
Error messages (before this fix):
err:module:import_dll Library mfc100.dll (which is needed by L"C:\\SpectraVue\\IOModule.dll") not found
err:module:import_dll Library IOModule.dll (which is needed by L"C:\\SpectraVue\\SpectraVue.exe") not found
err:module:import_dll Library mfc100.dll (which is needed by L"C:\\SpectraVue\\SpectraVue.exe") not found
So far, the webcam doesn’t work, but the send/receive audio does work on a test call. I didn’t test receiving video.
NOTE: in an actual conference, I wasn’t able to get sound, and so had to use a telephone. I have also seen problems with this for people using Windows and Mac at a large conference–leading the remote speaker to call in.
I personally avoid using GoToMeeting and would recommend using Google Hangouts or Skype instead of GoToMeeting for desktop sharing, video and audio between Mac/Linux/Windows/Android/iOS.
I tested this on Ubuntu 14.04 with wine 1.7.18. Again, this ultimately failed in a real conference. I don’t recommend GoToMeeting at this time for Linux or any operating system where you have a lot of people counting on it actually working..
1) Get the latest MSI file for GoToMeeting — I used V6.2.1 build 1350 from
2) in Terminal, type
wine msiexec /i ~/Downloads/G2MSetup6.2.1350_IT.msi
3) You may not have sound by default. To fix this, start GoToMeeting, right-click the flower toolbar icon, select Preferences, Audio, and select the Pulseaudio device for each.
Uncheck the “Automatically adjust my system mixer settings” and “Use automatic volume and noise processing” boxes.
Migrating to a new PC or new install of Linux can be accomplished by first copying your entire home directory to an external HDD, then copying back to your new (install) PC with a tool like grsync. (I don’t necessarily recommend this method, but it can work).
This can cause two issues for WINE.
- if your username changed, you have to update the “exec” lines of the .desktop files that reside in ~/.local/share/applications/wine/Programs/ (or create softlinks–maybe someone knows a more efficient way to do this?)
- Sometimes the softlinks in ~/.wine/dosdevices don’t survive the copying process (e.g. if your external HDD is NTFS formatted), because some filesystems (NTFS) don’t like filenames like “c:”. So at a minimum if your WINE programs don’t run, and there’s no “c:” in ~/.wine/dosdevices, you need to type:
ln -s ~/.wine/drive_c ~/.wine/dosdevices/c:
It can be crucial to reliable performance while running Windows applications under Linux using Wine to use separate wineprefixes for potentially difficult programs you’re using–the more complex the software, the more you need to make a separate wineprefix for it.
The method for creating a new wineprefix has change with newer versions of Wine–here we describe the method for Wine 1.7. The example Windows software we’ll install to run under Linux is the popular free program Irfanview.
- Make the new wineprefix (this is equivalent to making a totally separate install of Windows, except that it’s really fast and takes about 355MB)
Type in Terminal:
env WINEPREFIX=~/.wine_irfanview winecfg
- Install your program (in this case, Irfanview) by typing in Terminal:
env WINEPREFIX=~/.wine_irfanview wine iview_setup.exe
One possible fix to this error, including where the Windows program gives an Error 481 is to execute the following command at the Linux terminal: