I have spent days trying to install TIS2000 on a virtual clone of Windows XP so I can flash updates to the modules the Tech2 says are staying awake.

Unless someone here knows how to get VX Manager to run in a 32 bit, Windows XP virtual environment, I’m stuck. The install file (VX Manager 1.8.x) won’t even open, just says it’s not a valid Win32 application.

If no one here knows how to get it to work via internet downloads or DOS Prompt trickery, I’m going to have to break down and buy the 3CD set and the dongle that will let me run TIS2000 from Windows 7, and not a cracked version on a virtual XP machine.

Edit: I have ordered the CD and USB key, but it won’t arrive for two months (by Mar 25) from China, sooo... Still down for any help anyone can give me.

 

What is most current version of VM player can you get loaded on the machine to run a VM shell?

The VM shell I built on XP pro, TIS2000 and VX midi driver was built in Vm workstation 15, but can hardware compatibility it to a older VM version to see if you can get it to run on your machine in Vm player. A quick check and I can hardware compatibility shell all the way back to workstation 5, but may have better luck with a newer version of VM player on your machine to run correctly instead.

 

I have my Windows 7 device.

The latest version of VM Workplace that will run on Windows 7 is 12.5.9, and I am using the free Windows XP Mode option inside the VM Shell.

I was able to power off the VM Shell and change the settings for the virtual computer to include a Parallel port necessary for tricking the TIS2000 crack into thinking there is a dongle present.

So I have a VM copy of Windows XP running, and it has been updated just enough to make it work, I have auto updates turned off.

I used the GM2000NAO zip file to install TIS2000.

I used the crack zip file to install the dongle software. (Follow the instructions!)

So I have a working copy of TIS2000.

The problem is I can’t get Windows XP to find the drivers for the Nano, and I was unable to copy the drivers from the Windows 7 system where it works, to the XP clone. And when I try to install the VX Manager exe file from the CD, or if I save it to the hard disk and try to install there, it tells me that the program is not a valid Win32 application and terminates before the install starts.

 

First off, make sure you have installed a LPT port in the XP shell. Its need for the Nano to show up in the shell as a USB serial adapter.

Next check your PM's, since I sent you a link for VX MDI driver 1.2, which will be installed in the xp 32 bit shell to get the Nano to connect to it in VM manager .



When you open VX MDI Driver (Vx manager) in the VM shell, you will need to click on firmware, to downgrade the Nano firmware to the latest version that it can run first, then license icon, followed by installing the apps-Passthrough-GDS2/T2W.SGM RDS in the diagnostic tabs, automobile in VX Mdi driver in the shell.


Once the above is completed, the follow the instructions to build the needed Nano/VxDiag driver in Tis2000 to get the Nano to connect to it next.

If you are still having problems with the shell you built, then let me know and will just step down my Built shell to run under Vm player 12 that you can use instead.
________________________________________ ________________________________________ ________________________________________ _______
As for once your done with Tis2000 and back in the windows 7 using Tech2win, make sure to open up VX manager, and upgrade the Nano firmware again for VX manager 1.8.

 

That’s the current issue. The license has expired for the VCX MDI Manager, and clicking the “Update License” button returns an error.

 

Gets a little tricky, since you may have to do a frimware update on the Nano in Vx mdi driver 1.2, unplug the nano, plug it back in, then do another firmware update to get the license icon to work. Note, played with VX manager 1.3, and that version is a No go in VP.

But sent you a link on going into the control panel to 16 bit hardware suport capabiliy, and enabling 16 bit driver suport, so you can just install Tis2000 to windows 7 32 bit directly instead. When done this way, you can use the latest VX manager, as well as installing GDS2 to native win 7 as well (hence no reason to run anything in a shell for the Nano when you are running windows 32 bit).


Here is how to enable 16 bit on a win 10 32 bit system.
https://www.groovypost.com/howto/ena...rt-windows-10/

 

The firmware - unplug - firmware pattern causes the VX Manager to crash after the second firmware update, when the license button is supposed to activate. I assume it crashes when it tries to look for the license in both cases.


And this laptop does not have an LPT port, so I have to run TIS crack in the shell where I can emulate an LPT port on the virtual machine. Since it makes changes to the registry, it’s not something I can just copy over to Win 7, I don’t think.

 

LPT is a parallel port, so make sure you have installed one in the VM shell, since the dongle crack is going to need it. Hence when you go to run the DDinst32.exe and get a error message and Express will not install correctly, the problem is due to not installing a Parallel port in the VM machine before hand.

Also, while building up a Win 10 32 bit VM to run TIS2000, kind of ran into a problem after installing the Bosch MDI drivers, then installing the current VX diag, with the GDS2/T2W app not installing in the VX diag. To solve that problem I just installed Tech2win in the shell, which allows Gds2/T2W to install in VX Manger afterwards.

So on that note for the XP shell, install Tech2win in the shell and see if that give you the VX diag in Tis2000. Also don't forget that when you first go into I/O in Tis2000, click on Driver, browse/select J2534.DLL and install the driver for I/O so you do have the J2534 pass through driver in the list to select from when you are building the Tis2000 driver for TIS2000.

As for VX mdi driver, and the apps licenses out of date in XP, still trying to solve that one/why I am building up a 32 bit VM in win 10 since the lastest VX manager works with it no problems, if push comes to shove.




As for this, Its Defender, and you will need to go into its quarantined list, and allow the needed file to run. For some reason in the latest VX manger, Defender is doing a fails flag on one of the VX manager files to cause the problem. If you can not find the file since Defenders erased it, then reinstall VX manager and keep a eye on the defender pop to to catch it in time, and allow the file to run in defender.
Note, while building the Win10 32Bit in VM, Defender did not have a problem loading the lastest VX manger/no fails flaggs isntead.

 

Tech2Win was already installed in the shell. You can see the icon in the lower left of the screen in the pic you referenced.



I went back into I/O as you suggested, and under properties for the Generic Pass Thru device they had me set up following the blog instructions you linked, I was able to find a pull down list with VXDiag name. I selected it and hit the configure button. If I have some free time tomorrow, I will try to hook it up to the car and see if they communicate. I also sent an email to AllScanner to see if their people have a work around for the VXManager license issue. I wonder if the solution might be as easy as just setting the clock on the virtual machine’s XP Demo state back to 2018?

 

TIS2000 now has the driver it needs, so the quick test, open the shell, make sure that you have the Nano connected to the shell, open up TIS2000, click on SPS, and do a dry run with SPS. Hence build the model, hit next, and on the Vin verification screen when you hit next, you don't want the replay that the device was not found, but instead something like ECM is test device instead. This means that TIS2000 is seeing the Nano, but just not the Ecm instead. If you keep going down the same path, will bring you to the modules list so you can take a look at them before you connect to the car.

As for Tis2000 and XP, since the app license problem in VX Mdi driver (since its the only VX manager that will load in XP), I'm just treating the use of building a shell in XP as a death path now. I first built a shell using Win10 32 bit, but was a crash and burn without a ton of work to get it to work, and so built a Win7 32bit shell, that works well for Tis2000, Tis2000, as well as native GDS2V19, to run everything for the nano in the same shell. Granted that TDS will still want to use Win10, For the cracked stuff, Win 7 32Bit is the best option currently.

 

Test run:



XP VM shell is open.

Nano is connected to the shell.

Open TIS2000 and select SPS.

Select Generic Pass Thru Device (the Nano driver I built) and hit Next.

Build the car’s profile and hit Next.

Connect to car, but we are in the kitchen for this dry run, so click Next.

First error message is about Pass Thru license. Clicked OK.

Second error message is the one you said I should see, about the ECM being a service model. Clicked Next

Asks me to verify the VIN, so I canceled at this point. I will go outside and copy down the VIN and try it again.

Update after Vin:



Entered the VIN and clicked Next.

It’s the module selection screen you mentioned.

If I click on a module, I get options. I just chose the default Normal for this test run. Clicked Next.

Error message about Pass Thru license. Clicked OK

Error message about no communication with vehicle. Clicked ok and closed the program.

 

I just PM you on a solution, instead of having to rebuild the shell since Tis2000 is a monster to get all the parts of it uninstalled, to reinstall it again.

But problem is screaming that during TIS2000 install, did not click on the box above the parallel security device so TIS2000 installs the needed driver for the crack, or you did not do the crack correctly instead.

 

Since this was such a nightmare to crack and get up and running, I had ordered the TIS 2000 CD and dongle on EBay for $17 after shipping. It arrived yesterday, 20 days ahead of schedule, and I’m about to try installing it now.

 

If it isn’t one thing, it’s another. When I tried to log into the VMWare virtual machine to try the dongle, it asked me for a password! I did not set up a password for the Virtual OS, does anyone know what the default password is for the virtual machine?

 

VM password for windows/log in name should be what you used when you where building the shell in Workstation.
If no password/user name was used for the VM set up, them should have asked you for a users name and passwork during Windows install the first time you ran the shell.

As for still no joy, then build a bootable USB drive (Rufus and use the iso of what every op system you did build the shell around to set up the usb), and add the windows operating system password recover program at that,making sure to set the shell up as first boot from usb drive on start up..

 

Here for our weekly installment of “How to Setup the Computer”.

I seriously feel sorry for anyone who gets a C6 about two years from now, because the computer hardware and software required is getting so old that it’s hard to find, and even harder to get running once you find it. The laptop is going to have to stay with the car, if you have one and you’re selling it. Don’t leave the next guy in the hook, make sure the dedicated laptop goes with the C6!!!

Right now, I can get VX Manager to operate only in a Windows 7 environment, and the TIS2000 will only work in the XP environment. The VX Manager in the XP environment will no longer update the licenses, so you can’t install any of the Passthru software. It is a nightmare trying to figure out how to make the two connect.

Anyway, here is the list of installation steps I’m following this time around:




And here’s what happened:


Clean installation.

Windows 7 Enterprise in Virtual Machine.

Install VX Manager first.

Installed without any additional licenses.

Had to upgrade C++ Runtime to play the VX Manager file.

Updated firmware and license.

Installed Tech2Win with Nano still connected.

Installed Passthru

Installed GDSS2 and SDS.

Ran the Bosch drivers program.

Installed TIS2000

Ran the crack.

Did not solve the problem.

TIS2000 refuses to recognize J2534.dll as a valid driver file in Windows 7, but works perfectly in XP Pro.

 

No, get window 7 first built in workstation with parallel port added to hardware in workstation, activated windows, and make sure to install VM tools.

Now install 7-Zip in the shell so it has a decompression program in needed.

Install VX manager in the shell, get the nano firmware license updated in VX manager, then Tech2 win install using Autoinstall.exe from the tech2 win folder with VX open and Nano connected, so you can install pass throu, GM gds2/tech2 win, sgm rds VX apps within VX manager only.
Note, we install everything as admin, including the VX manager to start.

Now install Bosch drivers from the link, then NAO Tis2000 disc 1 as VM cd/dvd select from main OS , do the cracks with the Crack folder decompressed in the VM shell (not in the main OS still), go back to VM tools and switch CD/DVD to Tis200 disc 2 to open tis2000 and update it, then same the Tis2000 disc 3 update as well.
Now install the nano driver in NAO Tis2000.

At this point once you have the TIS2000 up and working with the Nano driver (j2534 pass through in device list), you can install the stand alone GDS2V19 software from the GDS folder autoinstall. exe, and then finish updating windows.

So again the problem I am seeing, is that you are trying to install GDSV19 stand alone program fro the GDS folder first since I can see the GDS icon in the desktop, then TIS2000 after that, and what is causing your problem. Truth is, the reason that we install the stand alone GDSV19 at all in the end (over than just having it), it will solve the device number not found pop up on start up of the VM shell from the Bosch drivers in the first place.



Your getting this, since when you built the VM shell, either did not add a parallel port device as hardware in the shell, and/or did not check the parallel security upper box in TIS2000 first set up on disc 1 before you run the Dll crack and install the needed files.

 

If GDS2v19 is the GM MDI Manager, then it is the first thing the Tech2Win autoinstall program sets up, before it installs Tech2Win. If the MDI manager is not GDS2v19, then I did not install it until after Tech2Win was setup, and I only installed what was in the Allscanner VX Manager under the diagnostics tab. I did not install the standalone GDS2 program from the GDS2 folder at all. Didn’t even open the folder.

I only used autoinstall.exe programs to install anything, and I followed the procedure in order when I did it.

Do you want me to use the Tech2Win standalone installer, or the autoinstall?

And I used the parallel port, but I forgot to run the crack as an admin. When I ran it as an admin, it worked perfectly.

 

Start with fresh VM win 7 32bit shell, activate it and make sure to install VM tools, then install Bosch drivers and TIS2000 first (disc one), do the crack, then update Tis2000 with disc 2 then disc 3, then build the Nano driver in Tis2000.

On your machine, Got a feeling that installing VX manger 1.8 before Tis2000 is screwing something up as VX manager changing some of the software around.

This should give you the TIS2000 J2534 pass through in device from the J2534.Dll that is the hang up now, to install the Generic pass thou driver for the Nano and use the J2534 pass through in the driver window of it properties.

Once Tis2000 is golden with Nano driver, Then install VX manager 1.8, T2w with VX open and nano attached, the three VX apps that T2w will allow to happen, then GDSV19, and you can then update windows in the end.

And like always, always install everything as admin.

 

Fresh install.

Copied over KMS, GMNAO2000 and the crack, and the GM MDI Manager setup.

Installed TIS2000, selecting parallel port.

Ran the crack.

TIS 2000 is installed, installing GM MDI Manager.

Manager installing.

Manager still installing.

Manager is finished.

Building the driver in TIS 2000.

Same dead end. TIS 2000 doesn’t recognize the driver.