I have tried the RC filters suggested and they do not improve the situation=
..

For completeness I  ought to say that the cable from the ICD2 to the target
uses one of those little RJ to single in line adaptors.   There is about
two inches of flat cable from the ICD2 to the adaptor then six inches of
individual wires to the target.     The only opportunity for cross talk is
in that two inches of flat cable.

Wouldn't a corrupt WinUSB.dll cause problems with other USB devices?   And
can I simply replace WinUSB.dll to test this theory.?

<https://www.avast.com/sig-email?utm_medium=3Demail&utm_source=3Dlink&utm_c=
ampaign=3Dsig-email&utm_content=3Dwebmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=3Demail&utm_source=3Dlink&utm_c=
ampaign=3Dsig-email&utm_content=3Dwebmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

__________________________________________
David C Brown
43 Bings Road
Whaley Bridge
High Peak                           Phone: 01663 733236
Derbyshire                eMail: dcb.home@gmail.com
SK23 7ND          web: www.bings-knowle.co.uk/dcb
<http://www.jb.man.ac.uk/~dcb>



*Sent from my etch-a-sketch*

On 1 January 2018 at 21:55, Manu Abraham <abraham.manu@gmail.com> wrote:

> On Tue, Jan 2, 2018 at 3:15 AM, James Cameron <quozl@laptop.org> wrote:
> > On Tue, Jan 02, 2018 at 02:15:10AM +0530, Manu Abraham wrote:
> >> This is what I understand:
> >>
> >> #1. The old machine was slow and the I/O on the cable was okay.
> >>
> >> #2. The faster userspace I/O on the newer system, caused a higher
> >> data rate on the cable, which directly affected crosstalk. This
> >> broke communication.
> >>
> >> #3. Now, the faster machine has a virtual machine, which slows down
> >> all I/O.  App->VM->OS->USB->serial in comparison to
> >> App->OS->USB->serial
> >
> > Yes, that was my theory too; which I expressed far too briefly as
> > a "race condition".
> >
> > There's also a different USB controller in the faster machine.
>
>
> There could be another aspect to the problem, too..
>
> The new machine has a corrupt WinUSB,dll (userspace), the kernel space
> WinUSB.sys is intact.
>
> The Virtual machine doesn't access WinUSB.dll, but does system calls
> directly, for VM optimizations. As a result when the VM is in use,
> WinUSB.dll is not used.
>
> Just another possibility.
>
>
> Cheers,
>
> Manu
> --
> http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.