Uwe@Ross-Tech

No, it's not their development. It's a blatantly stolen version of our product, simply translated into Russian without our authorization, and with our copyright notice hacked out. It is your problem as well because you will not get any help from us, and I really doubt you will get help from anyone who has a legitimate version of our product. -Uwe-

Announcing on a public form that you're going to use an illegal, pirated version of our product? Brilliant. -Uwe-

I think this thread is mis-titled. VCDS did not kill this module. It's possible the module in question had some sort of fault to begin with, which wasn't evident until that feature was activated; or perhaps the module has some sort bug in its firmware; or that particular variant of this module was never intended to have that feature activated but they forgot to lock out the relevant bit to prevent activation, which could be considered a firmware bug in the module. In any case, we can't address it in more detail without specifics: The exact part number of the module and exactly what was done to it. The CodingLog.txt file in the VCDS folder should have some of that info. A current scan of the module (or even the whole car) showing what (if) any fault codes exist would be good too. -Uwe-

There are a few ECUs which are just plain buggy when you try to read more than one measuring block group at a time. There's nothing we can do about it when the ECU doesn't answer valid requests properly. -Uwe-

Post the complete part number from your Convenience Module please. VAG-COM shows it as "VAG Number" when you access the module. -Uwe-

Right, that's be behaviour we have seen here. We think we've found a solution, but have some more testing to do. -Uwe-

Baaahhh! This is a Ewe: My name starts with a 'U'. -Uwe-

OK, we've figured out that the problem is User Account Control. Automatic Updates work on systems with UAC off, but fail on system with it turned on. Although I run my home system with that nagging b*tch turned off, I would not recommend this to everyone, so we are looking for a solution. Please be aware that even if we find a solution tomorrow, it may take an additional update cycle for it to become effective. In other words the next update may not work automatically even if we've found a fix, because the code on your PC which is actually performing the update doesn't have the fix yet. -Uwe-

If we give a discount to members of one forum, soon the members of every forum will be clamoring for the same discount, and then we'll be giving everybody a discount. Think about it this way: With the dollar being so weak now, you're already getting a good discount (compared to people who bought in the past). -Uwe-

Auto-Update works fine on my home machine which runs Vista Business (32-bit), but we did find a machine at the office this evening on which it doesn't work, so we'll be trying to figure out why. Work-arounds: If it leaves a file called VCUPG.EXE in the folder where you've got the software installed, you can just run that. If that doesn't work, head for the Beta Page and download and install manually. Sorry for the inconvenience. -Uwe-

Occasionally. -Uwe-

That's fine. Since it worked in your brother's Ibiza, the logical deduction is that there's something awry with your Octy. First, check that the cable is fully seating in the socket. -Uwe-

What year car? What Engine? VAG-COM would show you something like this: 17588 Linear O2 Sensor; Pump Current: Short to Plus P1180 35-00 Sounds like you need to check your Lambda sensor and the connections to it. -Uwe-

Might be easier for somebody to help if you posted: - The part number of the control module that you tried to change the coding on. - The original coding and what you changed it to. - The exact fault code you're now getting. -Uwe-

Puts some perspective on the price of VAG-COM doesn't it? -Uwe-