• Date
    ldsfx
  • Date
  • Replies 14 replies
  • Subscribers 185 subscribers
  • Views 15640 views
  • Users 0 members are here

Ion Client in Parallels

I have heard that this is a viable option for running an Ion client on a mac. Currently, when I plug in my dongle, I get the message :

"The USB device you are trying to connect to the virtual machine is being used by another application. Close that application or unplug the device and plug it again. Then try to connect the device again."

 

I don't have any other applications running, so I am confused by the message. Anyone have a similar issue?  

 

Thanks!

 

-Nick 


 

Parents Reply
  • in reply to ldsfx
    LOL I missed that in the title. So are you Parallels 3.0 or something older? Also are you rebooting into windows or are you running windows and OS X at the same time? If you are not rebooting into windows, then I think that the issue is that you are just running windows as a shell or application in Mac OS X. So therefore windows does not have control of your USB controllers.
Children
  • in reply to usesafesets

    I am running Parallels 3.0, and I am pretty sure that I have setup the USB busses to be controlled via the virtual machine; the dongle however, is registering as being already used....but I don't understand what process or application this could be. Should I somehow disable the USB device in my Mac OS so that the virtual machine is the exclusive controller?

     Thanks! 

  • in reply to ldsfx
    Again I would recommend rebooting your machine directly into Windows. The issue, could be, that we are not talking about a normal USB device but a HASP software key. Can you get a flash drive or other USB device to work in your virtual machine?
  • in reply to usesafesets

    The more I have looked into this issue, it seems to not be an ETC issue, but more of a Parallels/USB issue. I have tried many of the options suggested on other forums, including installing the HAS PL driver in both my Mac OS and the Virtual Machine, but still nothing. Unfortunately with Parallels, I cannot "boot directly" into Windows as the program, by definition, runs as an application within the Mac OS. My only thought now is that I somehow need to have my Mac OS "ignore" the dongle so that it may be only used by the virtual machine.

    Does anyone have experience running the Eos/Ion client in Parallels? Or even in native Windows? How does the application perform differently with the dongle inserted? 

  • in reply to ldsfx
    I am using Boot Camp to run Windows on my MacBook Pro and have not had any issues with the client. Well that is now that I have all the drivers installed  . . . thanks again David. The client looks and feels just like the offline, which you do not need a dongle to run. The only difference is that when you have a client dongle and run the software in client mode you can actually work as a "user" on an Eos/Ion network. So you can control the rig via your laptop. If you are logged into the network with the same user ID as a console, then you can view the screens for that console; making the client able to function as an RVI type device.
  • in reply to usesafesets
    Does the "network" tab appear on the displays menu? I only ask because I have been trying this entire process at home, without actually being on our network. If there is no visible change in the app, then its possible my dongle is working, I just haven't noticed any visible difference...
  • in reply to ldsfx

    I've done it. You simply have to grab control of the USB dongle from the Windows side. There is a menu at the top of Parallels called Devices (or something like that, sorry, am not on a Mac). This is the same way you relenquish control of a CDROM, floppy, etcetera. If you have the Mac dongle driver installed, the dongle LED will probably already be red. Once you've taken control of the dongle, you need to install the HASP driver in Windows as normal. You should see it in the Windows device manager as well.

    You also need to run in Bridged mode - this makes the Windows machine and Mac machine appear as two different computers on the network (and therefore the Windows machine is visable for Eos). This is changed in the main setup screen for the VM (before you launch the OS).

    Hope that helps!
    -luke- 

  • in reply to luke.delwiche

    Unforutantely, I have done all of those things, but I still get the error message:

    The USB device you are trying to connect to the virtual machine is being used by another application. Close that application or unplug the device and plug it again. Then try to connect the device again. 

     I have been reading around on the Parallels support boards and it seems this is a pretty common issue with no definite solution. I will try and contact Parallels directly about the issue. 

  • in reply to ldsfx
    I would try removing the OSX HASP driver. I'm not sure where that is, sorry!
  • in reply to luke.delwiche

    Ah ha!

     Finally it worked. Removing the OSX HASP driver did it. Thanks everyone!

     

    -Nick 

  • in reply to ldsfx

    I'm trying to use parallels to run an Ion client as well, and parallels recognizes my dongle just fine, my problem seems to be a network (perhaps IP address) issue. 

    What did your settings end up being?

    I recall using xConnect on a Strand through parallels, where the IP address had to be the same in the network settings on my mac os (on all 3 Ethernet tabs) and in my windows virtual machine. So naturally I tried the same here. But my client in windows just hangs on "Waiting for master".

    any help would be appreciated.

  • in reply to ldsfx
    Just as a Note. It is possible to KEEP the OSX HASP driver. Because I have several different HASP keys, I need to have the driver on the mac side.

    To make windows accept a hasp key and to 'release' it from the Mac control you need to access the virtual machine setup in Parallels and under the USB Controller setting before Windows boots.

    Set the drop down to "Connect to Guest OS", hit OK and then Start Windows. You cannot just change it in the Devices/USB menu after you have already booted windows.

Related

www.etcconnect.com