Results 1 to 6 of 6

Thread: wine 1.7 vs EchoLink vs 13.1

  1. #1

    Default wine 1.7 vs EchoLink vs 13.1

    I have a fresh 13.1 install with the current wine version installed. I have installed EchoLink. The installer works OK. When the program runs this error is generated:

    Code:
    ~/.wine/drive_c/Program Files/K1RFD/EchoLink$ wine EchoLink.exe
    fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}
    err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded
    Does anyone have any info on how to fix this, or point me to a reference?

    The current version of EchoLink works fine under 12.2 and Wine 1.5.6-2.

    Any and all help appreciated.
    Rick71

  2. #2

    Default Re: wine 1.7 vs EchoLink vs 13.1

    The fresh install I mentioned above was using an existing /home. I reinstalled 13.1, with a fresh installed /home and Echolink appeared to work. At least it will now allow me to log in and listen. I haven't tried transmitting yet.

    I also had problems with fldig crashing on startup. It also seems me to start it up, configure it and attempt to listen. Unfortunately, I don't have a radio connected to that box.

    Hopefully, I'll be able to install both by removing the .wine and .fldigi directories before installing both programs.
    Rick71

  3. #3
    Join Date
    Jun 2008
    Location
    Sogndal, Noreg
    Posts
    1,103

    Default Re: wine 1.7 vs EchoLink vs 13.1

    Hello.

    If you encounter further problems you might find some additional information here; not any too recent tests though but you might ask someone supplying any error message output, it might apply to WINE more in general.
    http://appdb.winehq.org/objectManage...cation&iId=994
    OpenSuSE 13.1, KDE 4.11.5, 64bit
    Gigabyte 990FXA-UD3, AMD FX8350, MSI GeForce GTX 760, RME HDSP9632, 16GB HyperX Kingston DDR3, Samsung 840-Pro SSD 128GB, WD Desktop Black 1TB, Hitachi Deskstar 7K1000 750GB

  4. #4
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: wine 1.7 vs EchoLink vs 13.1

    On 2014-02-26 15:36, rick71 wrote:
    >
    > The fresh install I mentioned above was using an existing /home. I
    > reinstalled 13.1, with a fresh installed /home and Echolink appeared to
    > work. At least it will now allow me to log in and listen. I haven't
    > tried transmitting yet.


    Wine (windows) programs are installed on your home. So you can try
    instead with a new user.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)

  5. #5

    Default Re: wine 1.7 vs EchoLink vs 13.1

    Quote Originally Posted by F_Sauce View Post
    Hello.

    If you encounter further problems you might find some additional information here; not any too recent tests though but you might ask someone supplying any error message output, it might apply to WINE more in general.
    http://appdb.winehq.org/objectManage...cation&iId=994
    I had already looked there. But it's all working for now.

    Thanks for the info.
    Rick71

  6. #6

    Default Re: wine 1.7 vs EchoLink vs 13.1

    Quote Originally Posted by robin_listas View Post
    On 2014-02-26 15:36, rick71 wrote:
    >
    > The fresh install I mentioned above was using an existing /home. I
    > reinstalled 13.1, with a fresh installed /home and Echolink appeared to
    > work. At least it will now allow me to log in and listen. I haven't
    > tried transmitting yet.


    Wine (windows) programs are installed on your home. So you can try
    instead with a new user.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)
    That would have saved a lot of distro install if I had thought of it :-)

    Thanks for the suggestion, I'll give it a try next time something like this happens
    Rick71

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •