The code for differing emissions profiles has a valid reason to be there (different rules for different markets, plus test tunes that stress various components, so there will be many tunes in the codebase).
Logically you are correct -- tunes are made up of a lot of different maps, and each region gets its own set of these maps. These maps are just tables that get interpolated -- e.g. for this RPM and this amount of air, use this much fuel and this timing.
However, each tune only contains a single region. If you look at it economically, there is no reason for them to put all the regions on a single ROM -- this just takes more space. They already need to configure by region, so why not make the entire ROM the configuration and save space?
I can't speak for all car makers, but the ones I'm familiar with do this.
I just had to post something against the classic
you can go look up how
Yes, you can.
Their Win32 API is probably the single largest working example of "backward compatible" you'll find in an API. The thing is for better or worse riddled with deprecated functionality, "Ex" functions to replace it, and structs which need to know their own size. Run an old Win32 app from the Windows 95 days and there's a really good chance it'll still work today. There are very few cases where they've made something specifically not work, and that has sometimes been because people have been using it wrong to the detriment of the user (i.e. retrieving the Windows version).
Their driver side tends to fluctuate a bit more as they make performance or safety enhancements by replacing the various APIs, but there's really no way around that.
Dumping a system that works and does what I want for a system that spies on me and will change at the whim of its maker with but a "swallow bitch" if I complain.
You jest, but Windows is far and above king of backward compatibility as far as APIs are concerned.
One does wonder how efficient it is compared to Linux, though.
Ok, my basic question is...What the hell is an immobilizer chip?
Just about all cars made in the last several years have immobilizer chips in their keys. When you start the car, the chip is read and the car won't start if it is missing or has an unknown identifier. If you've ever had to replace a key, this is why that is so expensive.
It's designed to make cars harder to steal. There is no remote capability.
Both NVIDIA and AMD have methods of capturing directly on the GPU, making for a blissfully lag-free experience compared to, say, FRAPS.
Hopefully Windows has created a standard interface for these, and not just reimplemented FRAPS.
Real Programmers think better when playing Adventure or Rogue.