I use VMWare Player and WinXP SP3 and it works just fine on my Windows7 64bit laptop.

 

You don't have to have Windows Pro. On one of my computers I have installed Windows VM tool (Windows 7 X64, Home). There are ways around it.

Did you install the cable drivers and also manually enable the VM to see the cable? You have to enable the cable everytime you plug it into your computer.

 

So I brought my home PC down to the garage which is running Vista which is 32 bit. Now I am getting this error when trying to run the tool set up.

This setup can not be installed on this operating system version. Only Windows NT 4.0 and Windows XP Professional are supported.

What next?

 

Set Compatibility Mode for Windows XP SP2.

 

I tried to right click to get the option to and it was not there?

 

Under properties it does not give me the option.

 

When is it giving you this message? What file are you trying to launch?

Are you using the latest version of the installer?

 

The setup file in the Mini Cooper Tool Setup 2.10.0 folder.

 

Got installed. Had to go about comparability mode differently than the directions stated.

Thank you for your help!!

 

Glad you got it going!!

 

Any idea why I am getting this error?

VIN is faulty
COAPI-2020: no answer from ECU
IFH-009: ECU not connected or doesn't answer

 

Have the pin properly shorted / unshorted?

 

One of the pins is loose so I am guessing it it not connecting property.

What a PITA this has been. Now I have to wait another week or so to have a cable sent.

 

Damn! Sorry to hear that. Some of these cables have been pretty crappy for the amount of money they cost!

It sounds like the universe is against you right now with this. I (and all of us here) assure you that it will be worth your time and trouble!

 

Want to borrow mine in the meantime?

Michael

 

That would be great. I will send you a pm with my number.

 

Ok so I was able to borrow a cable and get started. Everything is going smoothly but when I hit execute job after changing the codes, I don't hear my car clicking at all and the code does not stay? I did it two times and when I re-read the ECU the code is back to original?

Any ideas?

 

Sure. We've all run into that at one time or another.

Make sure you're coding CAS, though I actually code both out of habit. I'm talking about choosing one or the other after loading and hitting ZCS.

Sorry if that's vague. I haven't coded in a while so I'm a bit rusty.

 

WZA,

I wish I remember more of what I did to code mine, but it was 100 degrees and I would literally read the MAN file step by step and pray I did get heat stroke. Try mentioning this in the 2nd gen coding area. It gets a lot more traffic. I never could get VIM to work, Thear helped me at Minis in the Mountains.

PS: Did the puppies come say hi when you picked up the cable?

Michael

 

And I remember, it is definitely CAS.

Michael

 

Thanks, edited that. Thought I was right, but it had been a while.

 

Are there any coders in the Dulles area of Northern VA? I have been reading this thread, and would love to do some of these mods, but it seems to me to be a bit dangerous and would feel more comfortable if I had a mentor. Maybe even someone that would be willing to do it with/for me the first time. All standard bribes apply of course. .

 

SO… Here is my latest issue. For some reason, last night every time I changed the code in the FSW_PSW.TRC file of the CAS Module, saved it as the FSW_PSW.MAN everything was fine. The issue I was having was that once I tried to Execute the Job, the new code was never written to the ECU. After trying this a few times, I figured I would give up and wait until some others chimed in.

Here is where things got hairy. I figured I would give it one last try (never a good thing). I read the FSW_PSW.TRC file from the ECU, opened it up and it appeared to have a lot more code than I previously remembered. Thinking this was odd; I figured I would try to read it again, same issues. ( I did not delete the previous TRC file in the Work folder) Good thing is I was never able to Execute the Job, so the longer code was just in the FSW_PSW.TRC file. So I figured hey, let me try and copy over my original FSW_PSW.TRC file and try to write that over to the ECU. It would have helped if I copied, and not moved the original file to the Work folder. Yes, that’s right I wrote over my original FSW_PSW.TRC file with this longer file? Remember earlier when I said giving it one last try was not a great idea? This is why. Luckily I was never able to Execute the Job and actually change the code. Everything is working fine but I cannot figure out why when I read the code from the CAS Module I am getting this larger file. Is it just due to the fact that I did not delete the previous TRC file in the Work folder? You would think that since I never really changed the code, I would pull the same code from my original file that is currently written to the CAS module. Has anyone ever seen this before? I am thinking never go near the CAS module again??? I am guessing I read a file when I still had a TRC file in the work folder? Also am I correct that each module will have its own original TRC file?

 

All is good!! Everything coded. Thank you for your help!!

 

Can anyone confirm the welcome lighting coding working on US models?