yes admin and yes before evoscan is opened but even if evoscan is on it recognises it. i havent bothered checking if the system see's the cable when plugged into the other usb port, maybe like you were saying com port evoscan is looking for is then changed.

 

Guys, I solved my problem. My gauge was set to P1 because I find it easier to think in lambda. I was thinking on why Evoscan would always show blinking zeroes on WDB field and decided to set the gauge to P0. Guess what? Now it works with all three notebooks I tried and with both Prolific cables I have, each cable with a different driver.

Might be a problem on how Evoscan parses the data it reads from COM port.

 

Yeah that happened to me on my first laptop since it had the USBs in the same position so I would sometimes plug them into diff ports. On the new one the USBs are on different sides so its easy to remember which one to plug it into.

Great glad you got that figured out.