DIS v57 running on Windows 10 and VMware

[4.8isX5]

I get the same message on mine that it cant auto detect or something. I use it with manual detection, select the car model, rest of software works as it should.

[1iwilly]

i tried that but then i get this code error= 200.28
which has to do with the cable is not set to Latency1 but it is so i'm still dumb found about it

Originally Posted by 4.8isX5

I get the same message on mine that it cant auto detect or something. I use it with manual detection, select the car model, rest of software works as it should.

[1iwilly]

ok so when the batt icon on top bar is fully shade means you are connected beside the 2 color radio signal bar mines start off fully shaded then goes clear
also still getting the diagnosis bus error 200.28 but my com 1 is set correctly latency 1

[rogerkiu]

There is some problem for running VM on windows 10 that is upgraded from windows 8 or 7. I have to clean install windows 10 to make DIS work in VM environment. When I was running windows 8, DIS worked fine in VM but it did not work after I upgraded my system to windows 10, there was some problem saying cannot connect to the DIS in VM.

[X5only]

Originally Posted by rogerkiu

There is some problem for running VM on windows 10 that is upgraded from windows 8 or 7. I have to clean install windows 10 to make DIS work in VM environment. When I was running windows 8, DIS worked fine in VM but it did not work after I upgraded my system to windows 10, there was some problem saying cannot connect to the DIS in VM.

I had a somewhat similar experience, but I didn't have to clean install Win10. After the upgrade from Win8, I added vmware virtual ethernet adapter for vmnet1 since it was missing. The upgrade process had nuked it. Bad user experience. The upgrade process should not have to require a reinstall of any Win10 supported app.

[1iwilly]

thanks would you mind if you have the time the steps you had to take to make work.??

Originally Posted by X5only

I had a somewhat similar experience, but I didn't have to clean install Win10. After the upgrade from Win8, I added vmware virtual ethernet adapter for vmnet1 since it was missing. The upgrade process had nuked it. Bad user experience. The upgrade process should not have to require a reinstall of any Win10 supported app.

[1iwilly]

ok double check again this time the usb driver was updated here are pics of it running but still get the error no voltage at terminal 15 and bus error-200.28
vmware shows connected i just can't put my finger on it.thanks
the only one not highlighted is the head icon

[X5only]

When I get home will post pic of the settings on my win10 notebook. It also works on my win10 surface-pro3 tablet but I prefer the laptop for doing diagnostics.

[1iwilly]

thanks alot looking forward to good news.my ABS module will be here tomorrow sent it out for repairs want to use dis for testing system out

Originally Posted by X5only

When I get home will post pic of the settings on my win10 notebook. It also works on my win10 surface-pro3 tablet but I prefer the laptop for doing diagnostics.

[X5only]

Originally Posted by 1iwilly

thanks alot looking forward to good news.my ABS module will be here tomorrow sent it out for repairs want to use dis for testing system out

My settings are exactly like yours. I suspect you're missing the vmware virtual Ethernet adapter for vmnet1. Check your windows device manager for it. If the adapter is missing, it can be re-added by running network editor in vmware workstation selecting host and configured (in windows control panel network settings) as shown in the picture.

Have you also verified that the APITest is successful? APITEST is in Easy DIS configuration menu.