The University of Queensland Homepage
UQ VisLab UQ VisLab

 Contents
This document describes the steps to install and run the ClearOne echo canceller setup tool G-Ware under Linux using Wine. It was prepared by Chris Willing (c.willing (at) uq.edu.au) based on the work of visiting student, Cihan Altinay.
  1. Prerequisites
  2. Optionally building from source code
  3. Configuring Wine
  4. Running GWare
  5. Troubleshooting

1. Prerequisites

You need the following:
  • A modified version of Wine
  • The most recent versions of Wine don't work as needed for this project (there are problems dealing with serial port). We therefore provide binary packages of Wine for a number of Linux distributions with the required modifications already built in. Alternatively, the patch required for correct operation is available for those wishing to build from the source code.

    Binary packages and instructions currently available are for


  • If building from source code, this patch is needed for G-Ware to run correctly under wine. This patch was originally made against wine-0.9.44 but will apply to other recent versions (at least up to 0.9.59). It is not needed if installing one of the binary packages listed above.
  • G-Ware installation files
  • At the time of writing the latest version is 5.0.6 and can be obtained here.
  • DCOM98
  • Get the Distributed Component Object Model from Microsoft (or search for dcom98).


  • Fonts

  • The following truetype fonts are essential for a proper display:
      arial.ttf
      arialbi.ttf.

    To remove some minor visual glitches these are also helpful:
      coure.fon
      serife.fon
      smalle.fon
      sserife.fon


    Some Linux distributions supply packages for these fonts e.g. the msttcorefonts package for Debian & Ubuntu.

    If you don't have the truetype fonts (eg. in the X11 fonts folder) those from an existing Windows installation could be used. Alternatively, some appropriate exe files (arial32.exe and courie32.exe) can be downloaded from here. Don't worry about packages or cabextract because wine itself can be used to install the files. A google search should lead to pages with the *.fon files (eg. distributed in a RPM package) but don't worry if you can't find them.

2. Building from source code

Skip this section if one of the binary packages has been installed. Otherwise see how to build agwine.

3. Configuration

Either in a shell, run:
winecfg
or if your installation has a Wine entry in the Applications menu, select Configure Wine

This creates a .wine directory structure in the user's home directory as well as providing a gui to enable changing of some important settings. Using the gui that appears:
  • set the Windows version to 'Windows 98'
  • under Libraries enter ole32 and press Add. Repeat this step with oleaut32 and rpcrt4. Now select each entry and click on Edit to change the load order to 'Native (Windows)'. The list should now contain:
ole32       (native)
oleaut32  (native)
rpcrt4      (native)
Apply the settings and press OK to close the window.


Three files must now be erased from the user's new .wine directory structure which has just been created (new versions of these files are created in the following step when DCOM is installed). In a shell, run:
rm -f ~/.wine/drive_c/windows/system32/ole32.dll
rm -f ~/.wine/drive_c/windows/system32/oleaut32.dll
rm -f ~/.wine/drive_c/windows/system32/rpcrt4.dll


This enables DCOM to be installed. Change into the directory where the DCOM98.EXE file was saved and run:
wine DCOM98.EXE
The GWare software is now ready to be installed. First unzip the G-Ware archive, then change into the folder that was created and run the installer e.g.
unzip G-Ware5.0.6.zip
cd 5.0.6 (Build 7)
wine setup.exe
As the installer runs, it is probably a good idea to confirm that a desktop shortcut should be created. Read ahead in the Running GWare section below about alternative or additional methods of launching the GWare application.

You can safely confirm the dialog about 'Restarting your computer' as it will only simulate a Windows reboot (running wineboot).


4. Running GWare

At this point G-Ware should be ready to run. It may be launched in a number of ways:
  1. If you chose to create a Desktop icon during the GWare installation, double click on the ClearOne G-Ware icon
  2. A new 'Wine' entry should have been created in the Applications menu of the Gnome desktop when GWare was installed. Click on the new Wine entry and then follow the cascading Programs->ClearOne GWare entries to find and select G-Ware - Main Program
  3. A menu entry for G-Ware can quite easily be added to main Access Grid menu of the Gnome desktop. Edit the file:
    ~/.local/share/desktop-directories/wine-Programs-ClearOne\ G-Ware.directory
    and at the very end, add the line:
    Categories=X-Access-Grid3-Configure;
    A launcher will now be found in the Applications->Access Grid 3->Configure menu folder
  4. G-Ware may also be launched from the command line with the following command:
    wine C:\\G-Ware\\GWare.exe
    or
    wine ~/.wine/drive_c/G-Ware/GWare.exe
    (change the path if you installed it into a different directory).


5. Troubleshooting

  • Why do I get a message 'Html Help is not installed' when starting G-Ware?
  • The G-Ware help file is in Html Help format which needs extra libraries that are installed with Internet Explorer.
    If the message really annoys you, you could install IE6 to get rid of it but note that at this stage of development the online help won't work even then.
  • I can't find the 'Wine' entry in the Gnome main Applications menu. Where is it?
  • Try these commands from a shell:
    cd ~/.config/menus
    ln -s applications-merged gnome-applications-merged
  • The interface looks wrong - the font size is too small/large or button text is not aligned correctly. Why is that?
  • Wine uses replacement fonts if it cannot find the fonts that are requested by the application. This either means you are missing some of the fonts mentioned above or you didn't copy them into the right folder.
    Check the ~/.wine/drive_c/windows/fonts folder for the fonts mentioned above and add the missing ones.
  • When I start GWare from the console I get a lot of errors similar to
    fixme:comm:COMM_WaitCommEvent
    EV_RXFLAG not handled
    or
    fixme:commdlg:GetFileName95
    Flags 0x00800000 not yet implemented
    What's wrong?
  • These are not errors but notes that something is not (yet) implemented in wine which may cause different behaviour compared to Windows. In the case of G-Ware these can be safely ignored or even disabled by setting an environment variable:
    $ export WINEDEBUG=-all

  • The G-Ware interface comes up, but I can't connect to the hardware
This is likely to be a permissions setting on the serial port preventing you from reading or writing to the port. If you list the serial ports with:
$ ls -l /dev/ttyS{0,1}
you'll see a response something like:
crw-rw----  1 root uucp 4, 64 1994-07-18 09:48 /dev/ttyS0
crw-rw----  1 root uucp 4, 65 1994-07-18 09:48 /dev/ttyS1
which shows that only root or members of the uucp group can read/write the serial ports. You could make everyone able to read/write the port with:
$ chmod a+rw /dev/ttyS0
or you make yourself a member of the uucp group (method varies according to Linux distribution; with Slackware, man usermod)

Note that in newer systems using UDEV (just about any system using 2.6 kernel), /dev/ttyS0 is a link to /dev/tts/0 whose group is tty. The user's groups should include the tty group rather than uucp.
  • I followed all the steps and when I try to run G-Ware nothing happens or it crashes immediately with a page fault/exception/error. What can I do?
  • Most likely this is an OLE issue. Double-check that the Windows version is set to Windows 98. Also confirm that all three libraries (ole32, oleaut32, rpcrt4) are set to native and you didn't make any spelling mistakes. This behaviour was also experienced when trying to run G-Ware in a Xen system. The reason for that being that the TLS libraries were not in place. If you are in this situation you can run G-Ware as follows:
    $ LD_LIBRARY_PATH=/lib/tls.disabled wine GWare.exe
    Another thing to try is to do the following (with appropriate paths):
    $ wine PSRServe.exe &
    $ wine GWare.exe
    If it still doesn't work properly please send an e-mail to the address in the header.


Last modified: 30/1/2009 by Chris WIlling (c.willing (at) uq.edu.au)