Launch2Net no longer starts after Restart after Installation of Parallels 3.0

Discussion in 'Parallels Desktop for Mac' started by stroll, Jun 8, 2007.

  1. stroll

    stroll Bit poster

    Messages:
    2
    After upgrading and restarting the new Parallels Version, launch2net will not work any longer. After starting the program it asks for the password (normally just after the installation and configuration). After entering password launch2net closes again.
    After deinstalling Parallels 3.0 launch2net is working again.
    No problems with 2.5.3188 I downgraded to.
    So I have to stay on 2.5 version until provides a fix.
    Pity....

    P.S. I already informed novamedia (manufacture of launch2net). They told me to test this today.

    Greetings
     
  2. Dan Ingold

    Dan Ingold Bit poster

    Messages:
    4
    Works after fiddling...

    Well, you can make it work, but it takes a while. I experienced the same problem as "stroll" -- launch2net wouldn't run after installing Parallels 3.0. I first tried installing the latest version of launch2net (1.6.8.7658), but same problem. Then I un-installed Parallels, but that didn't fix the problem. Several iterations of un-installing/re-installing launch2net (latest version) led nowhere.

    What finally worked: With Parallels UN-installed, installed an older version of launch2net (unknown version, but less than 1 month old). Launch2net worked. I then upgraded to 1.6.8.7658. Still worked. I then re-installed Parallels 3.0, and it works, too. Everything now works, and life is wonderful.

    The main difference I can think of from earlier failures is this time I quit launch2net and removed my ExpressCard modem before I installed Parallels. I'm sure I didn't do this the first (failed) time. Perhaps somebody else can experiment further and find the minimal incantation. Good luck!

    --Dan
     
  3. Dan Ingold

    Dan Ingold Bit poster

    Messages:
    4
    Not quite...

    Reports of success were premature :(. Launch2net worked until the first time I ran Parallels 3.0. Then, the same old behavior. Uninstalling Parallels wasn't enough to fix it. I also had to uninstall, then reinstall launch2net. Didn't have to fool around with the old launch2net version, though. A clean install of the new version works fine.

    --Dan
     
  4. Dan Ingold

    Dan Ingold Bit poster

    Messages:
    4
    Update from Nova Media

    With a little help from Nova Media (who were very prompt in responding), I managed to get launch2net and Parallels 3.0 to play nice together. Here are the instructions as received from Nova Media:

    We have discovered that problems with the upgrade from 2.2 to 3.0 in
    Parallels can leave something behind that produces incompatibility not
    only with Launch2Net but with VMWare and Cisco. The new version does not
    uninstall or trash any unneeded file from previous version.

    The solution is to uninstall Parallels completely (following the
    instructions in http://forum.parallels.com/thread11880.html), launch
    Launch2Net and configure it, save the configuration and connect to
    introduce the software activation code. Thereafter, Parallels 3.0 can be
    installed anew and keeps the activated status and the last loaded VM.
    Now, both return to cohabitate peacefully.

    Let me emphasize (since I overlooked it myself) that you MUST actually CONFIGURE and ACTIVATE launch2net BEFORE installing Parallels 3.0. If you just install launch2net without configuring it, then install Parallels, launch2net will fail to launch the next time.

    --Dan
     
  5. stroll

    stroll Bit poster

    Messages:
    2
    Still working after restart of machine

    Hi.
    I also get the information, and worked on it.
    But there is still the same problem. Everything is working fine until I restart the machine, after that launch2net starts asks me for password, after entering the password launch2net quits.

    They ask me to install Mac OS X newly (and archive settings) but i havent found the time for this.

    I am working now with the Mac OS dialup and there is no problem.

    Greetings
    Sascha
     

Share This Page