Ok so does 1996-2010 Mustang include a 1997 Mustang Cobra 4v? I remember that used to be a different part# in the Predator days...

Is this i2020 a replacement for the U7146 non-can EECV cars?

right click i2000, uninstall and choose check box to remove everything associated with this device, then reboot tool and i2 drive should appear.

Ok - this fix worked- oddly I have to do it anytime I switch between plugging an I1000 and an I2 into my laptop (but not my desktop) for anyone else's ...

I often (like every time often) have the same problem- the I2 shows up in the device manager but no F: or D: or G: drives show up. Is there a way to force the USB driver to install?
And as a tuner who goes back and forth between I2's an I1000's a lot, how can I make this more of an efficient ...

A few questions for you so I can try and help...

What version of Windows are you running?
Windows 10

With the Trinity connected to your PC, go into Device Manager. Under "Ports (COM & LPT)" what COM port is displayed next to "DiabloSport Trinity CDC"? COM1, COM4, COM11...?
Com4

Are there any ...

DSDownloader works fine with it and I found an old DV 3.3 on my laptop and I am using that for now, but I would like to get this solved

I have DV 3.4.1.0 and a Trinity here with r.13 loaded on it and the two just won't talk to each other- see the image below for the Error message in DV

So if anyone cares my feet are getting tired of walking back and forth between computers as I save my tunes to Google Drive and then load them on the the intune at the desktop computer...

I would really like to get to the bottom of this bc it is driving me a bit :normal:

I use multiple intunes from multiple customers, i have one desktop machine that runs W10 and I plug the newly unboxed intunes (v1 or v2) to this machine and they update flawlessly and the drives always show up ...

Thanks to F-ing Microsoft for updating to windows 10 when I tried everything to stop it, CMR did not open this morning when I needed it too NOW- So a little FYI- if your stuck and reading this then you can run the installed CMR software in 'Windows 7 compatibility mode'

Bump for a look- problem still here.

I also tried the old 'disconnect battery and reconnect'. Did not work. Error happens the moment I select one of my Custom tunes, either new ones or the same one that is currently in the vehicle.

XML file:

<?xml version="1.0"?>

-<tool_info>

<main svn="8176" sw_rev="1r04e" full_version="InTune-1r04e 02/12/2015 08:55:43 AM"/>

<registration status="0" sn="IGQM172-2"/>

<cal_id CM1="05035407AE" PCM="05035871AD"/>

<restore bc="4" vin="1C4RJFDJ9FC667800" id="0"/>

<system_db vin="1r01e" dtc ...

2014 Jeep SRT here that I tuned last year, just came back in for a small tweak and I am getting the same error

Nice work- DMR's are finally working every time I connect.