Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!panix!MIX!Blackbird From: billy@MIX.COM Newsgroups: comp.sys.mac.system Subject: Re: probing USB Date: Fri, 22 Aug 2014 21:03:44 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 26 Message-ID: References: <53f6958b$0$21337$2c56edd9@usenetrocket.com> NNTP-Posting-Host: panix5.panix.com X-Trace: reader2.panix.com 1408741424 7976 166.84.1.5 (22 Aug 2014 21:03:44 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Fri, 22 Aug 2014 21:03:44 +0000 (UTC) Xref: csiph.com comp.sys.mac.system:63430 John Albert writes: > The problem is that there aren't many USB "diagnostic tools" > that I know of on the Mac (my knowledge may be limited). > > I recall something that was (still is?) part of the Apple > Developer Tools (I think) called "USB Probe". I also don't recall the exact name of this tool, but I do recall it is not very useful in pinning down bus failures (as opposed to just watching traffic on a working bus). Maybe something gets logged (ASL/syslog), though when I was looking at a similar problem (device on the bus going away), nothing was. Most likely there is some seldom occurring conflict between all the USB connected devices. Maybe watching/logging what they're doing would be useful. I'd try not connecting them until they are needed, then disconnecting them when done, or maybe just powering them down. Billy Y.. -- sub #'9+1 ,r0 ; convert ascii byte add #9.+1 ,r0 ; to an integer bcc 20$ ; not a number