Wouter van Ooijen wrote:

>>I will report the details of my Windows 2000 setup when I get 
>>back to my Embed office this afternoon.
>>    
>>
>
>That won't help me (I have no win2k around), but maybe others.
>
>  
>
>>The specifics of my XP setup will have to wait until I get 
>>home sometime much later tonight.
>>    
>>
>
>That could be usefull.
>
>USB specialists around: what *is* important here?
>- OS
>- driver
>- usb/serial hardware
>
>anything else?
>  
>
probably ...
We solved our USB problem for 80%.
The frequency of the crashes on the "bad PC" is reduced from 5 minutes
to 24 hours.
What we did: disabled a small analog part that wasn't in use and doing
almost nothing ?????????
There could be a problem on the PCB, but we see no way how it can
interfere with
either the RS232-part, nor the USB-part of the FTDI device.
In the next weeks (when I hope to have some more time) I'm still going
to try the FTDI suggestions.

Another way I was thinking of, are software USB-sniffers.
Has anyone experience with these ??
Are they usefull for logging normal running USB communication ??





Stef

>  
>



-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist