I have successfully been using NevoStudio Pro on my Mac (via Parallel Desktop) for a couple hours while the Nevo Q50 was charging but when I connected the Q50 to the USB port all hell broke lose and the Mac crashed (Kernel Panic).

Just a warning to all the people out there using Macs, the Nevo Q50 will cause a Kernel Panic, there is no way to connect/update a Q50 on a Mac it seems.

I was able to reproduce the error many times, just plug in the Q50 in your USB port before turning on the Mac and... well, it won't even turn on.

So the Mac seems to be hating the Nevo (unless it's the contrary).

Hi, I haven't been able to get my Q50 to work w/ parallels or Fusion, but I've never gotten a kernel panic plugging it in.

I *suspect* you have an over-current which I've seen manifest itself exactly as you describe. Too many devices trying to charge their batteries off your mac.

Try a powered hub, I can recommend one if you'd like.

I am not sure what the problem is. I plugged the Q50 in a Macbook with Windows running with Parallels and got the Kernel Panic. Then just to be sure I tried pluging the Q50 in another Macbook that had all apps closed and nothing else plugged in and got the same results = total failure and must hard reboot.
Both Macbooks are running OSX Leopard and are up-to-date.

Plugged the same Q50 this morning on my work PC laptop which already has 4 devices plugged in via a USB hub and everything went smoothly.

Are you using leopard or tiger? It occurs to me Ive only tried on tiger.

I just tried it on leopard, and Ill be damned you're right it panic's the machine! The remote didnt work for me on tiger, but didnt panic the machine. I am quite certain of this because I spent a couple weeks trying to get it working.

Just for the "programmer" inclined people here is the error result you get when connecting a Q50 to a Mac Leopard:

Mon Dec 31 20:35:15 2007
panic(cpu 1 caller 0x001A7BED): Kernel trap at 0x00420c82, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x00d4c000, CR4: 0x00000660
EAX: 0x00000000, EBX: 0x05bbbc00, ECX: 0x00420c58, EDX: 0x05bbbc00
CR2: 0x00000000, EBP: 0x5413bce8, ESI: 0x00000000, EDI: 0x00000000
EFL: 0x00010206, EIP: 0x00420c82, CS: 0x00000008, DS: 0x03a70010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x5413bac8 : 0x12b0e1 (0x455670 0x5413bafc 0x133238 0x0)
0x5413bb18 : 0x1a7bed (0x45ea20 0x420c82 0xe 0x45e1d4)
0x5413bbf8 : 0x19e517 (0x5413bc10 0x3a743dc 0x5413bce8 0x420c82)
0x5413bc08 : 0x420c82 (0xe 0x3b60048 0x54130010 0x410010)
0x5413bce8 : 0x3e809c (0x5bbbc00 0x0 0x1 0x0)
0x5413bd08 : 0x3e8169 (0x5bbbc00 0x0 0x3a3d664 0xce)
0x5413bd28 : 0x420950 (0x5bbbc00 0x1 0x0 0x1)
0x5413bd58 : 0x421150 (0x39c6e18 0x1 0x0 0x1)
0x5413bd78 : 0x345ff5e9 (0x0 0x1 0x0 0x4)
0x5413bdc8 : 0x3517775e (0x494a700 0x0 0x39c3e00 0x428fec0)
0x5413be18 : 0x351773f5 (0x5bbb700 0x346180b8 0x39c3e00 0x10001)
0x5413be48 : 0x40d650 (0x5bbb700 0x494a700 0x1 0x3e8070)
0x5413bea8 : 0x40f4e5 (0x494a700 0x5bbb700 0x4975480 0x49f05a0)
0x5413bf28 : 0x40ed49 (0x494a700 0x42a7a80 0x0 0xffffffff)
0x5413bf78 : 0x40d9c5 (0x494a700 0x0 0x5413bfac 0x1)
0x5413bfc8 : 0x19e2ec (0x497f940 0x0 0x1a10b5 0x39d8128)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBComposite(3.0.0)@0x35176000->0x35179fff
dependency: com.apple.iokit.IOUSBFamily(3.0.5)@0x345f1000
com.apple.iokit.IOUSBFamily(3.0.5)@0x345f1000->0x34618fff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9B18

Kernel version:
Darwin Kernel Version 9.1.0: Wed Oct 31 17:46:22 PDT 2007; root:xnu-1228.0.2~1/RELEASE_I386
System model name: MacBook2,1 (Mac-F4208CAA)

I too own a Mac, and was going to attempt to use the latest version of Parallels with my Mac Mini (running latest version of Leopard).

I saw your post, as well as another post mentioning your Q50 needing to be exchanged, and decided I'd better install Windows through Bootcamp.

I appreciate your posts warning of potential problems, you may have saved me from possible problems.

While I doubt your original Q50 problem was because of Parallels, I thought it would be best to not attempt to mess with Parallels. However, I wish I could muster up the testosterone and give it a try, but I'm to afraid.

I hope in the future Parallels will work for us, as I have no interest or need to run Windows through bootcamp on a permanent basis, makes me feel to vulnerable since I am not running, nor wanting to spend money on virus protection to run on bootcamp.

Mark

Ditto, many thanks for your posts! You've saved me a great deal of time and aggravation and I'm now considering other options like the Beo5 or the Phillips TSU9400. I've come close to purchasing a Nevo product twice in the last few years, but for whatever reason, their incompatibility with software like Windows Vista last year and now Parallels or Mac OS, has convinced me that I can no longer wait for them to provide basic software support for the machines that our household runs.

I'm certain there are several remote manufacturers interested in supporting the millions of Apple users around the world today. Maybe there are other Apple folks that could recommend a device and software that runs smoothly on Mac?

You'll actually find out that most "professional" remotes are not supported (Officially) with Mac, that includes Pronto, RTI, Nevo... However the Pronto software and remote work with Parallels for example.

The problem with Nevo only concerns the remote. The Nevo Studio Pro works fine under Parallels it's the remote that causes the problem. I can only assume that becasue Nevo is running Windows OS this is where the problem lies.

Let me preface this by saying: I'm a mac fanboy. I have 3 macs, iphone, ipods, apple tv... And now for the rant:

Mac's are a pleasure to use and a bitch to program. Objective-C sucks (Apples language), Apple has consistently pissed on the Java community by not supporting Java on OS X, and the open source .NET frameworks are crap. To write a portable app between Windows and OS X you pretty much have to use C++ which is frankly primitive.

Juxtapose that with MS who spends billions developing SW tools and on software engineering R&D that make SW engineering easier.

This is just how it is. If you want to see more mac products, pressure Apple to get their act together.