FWIW: Do you have the latest version of the FTDI OSX driver? I've had cases where the entire Mac would luck up under certain conditions (mostly related to the USB device itself). The older versions of the OSX drivers definately had some problems vs the Windows drivers. I've yet to have a lockup with the latest driver, however.

That said, from your description sure sounds like something in RB is getting locked into a loop, waiting for something to happen with the USB driver. (which could be a pure RB issue, or could be an RB issue triggered by the driver)
--

---
Chris Smolinski
Black Cat Systems
http://www.blackcatsystems.com
____________________________________


Well... I'm one version back. I'm using driver version 2.01. They have just released a newer one on February 1st - version 2.10. I've put in a request for a custom version of the driver that has my VID and PID numbers in it. Until I get that, I really can't make use of their new driver. Unless I can find a way to hack them in there ;-) ...or pull my eprom out... hey, not a bad idea!

I've read the release notes, and it looks like the only (documented) change that they have made was something to with supporting aliased baud rates. I don't know what that's about, but it doesn't sound like my problem. But there could be undocumented changes. In their older driver I had a lot of problems with the OS being able to find the device after it was disconnected and reconnected again. Never had any lockup problems until now.

Which driver version are you referring to as being the stable one? The one that was release a week or so ago?


Oh... and by the way... opening and closing the port immediately before and after every data send did not solve things either...


Thanks,

Ron Benditt
Alien Apparatus Company, Inc.
http://www.alienapparatus.com

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to