However, when I go to set options it acts like it is getting a list of them and then comes back with nothing. This is on a Windows.1 64-bit laptop with a cable bought off Amazon., 10:26 PM Tony Back Junior Member Join Date: Aug 2014 Location: California,.S.A Posts: 19 Thx for so much detail functions Thx for so much detail functions, i have got mine. 6, likes, 05:23 AM alex4wd, oP, junior Member, join Date: Sep 2013, location: Greater Seattle,. Alternatively, you may copy two files from the C:Program Files (x86)XHorse Electronicsmvci Driver for toyota tisprogramFilesFolderToyota DiagnosticsTechstreamEnv" to "C:Program Files (x86)Toyota DiagnosticsTechstreamEnv which seem to do the trick as well.
Now #6, Registry hack. Installed software on my win XP netbook. Ok, I got it so that it connects now fine and I can get real-time and sensor data. The "PassThruSupport.04.04" seems to be the place Techstream looks into for available VIMs (sub-keys appear in the "VIM Select" menu in Techstream). Mine is actually Windows 8 x64, but for Windows 7 the configuration procedure should be identical. I try to install the new driver, but it says the correct driver is already installed. I have a BRZ and the techstream platform is pretty new to most.
Just bought the device. Not a member yet? Do you know if the L line is needed for this function?, 10:02 PM weete Junior Member Join Date: May 2014 Location: LA Posts: 1": I bought one from it, It works. I have only "denso corporation - TIS Techstream VIM" The contents look different: Key Name: pport.04.04denso corporation - TIS Techstream VIM Class Name: Last Write Time: 12/23/2013 - 11:00 AM Value 0 Name: Vendor Type: REG_SZ Data: denso corporation Value 1 Name: Name Type: REG_SZ. Toyota Techstream.00.034.rar - - mvci Driver sunset porsche parts discount code for toyota. The cable is about 4 long, with translucent casing and mini-VCI J2534 Standard obdii Communication Interface sticker: The cable comes with a mini CD with drivers and Toyota Techstream software. Everything works as you described. Both will appear with yellow icon (usually under Other indicating that Windows failed to install drivers for them.
It worked very well, but then I did the upgrade to 147 firmware and now is dead. Took about an hour. Should I wait any longer?, 10:55 PM IBHomer Junior Member Join Date: Dec 2013 Location: Westminster, CA Posts: 1 Alex you rock! As it turned out, with little manual tweaking it is possible, contrary to the popular belief, to get it working under Windows 64-bit.