Rick:
I appreciate your passing along the knowledge... however I'm going to politely disagree with you.
As someone that has written a line or two of code for a living I can say that this type of decision tree isn't particularly difficult to code in the software. Assuming that the mothership has figured out how to either code a definitive hardware model and/or a serial number into a location that is programatically addressable it's childs play. We'll assume it's serial number and that serial number X of the product is the first serial of the new hardware type.
Here's what it would look like in pseudocode set version=v1.09
if serial < X set version=v1.08 endif
install version
Want to make it easier for later releases, give them the same base version numbers (such as v1.08) and append an A for baseline hardware and B for second rev of hardware. This becomes extensible through many versions of hardware.
The real world code would be a bit more complex depending on language etc, but not unduly so.
I also respect that the mothership is well within their rights to change their business model. I can't say that I am pleased, but I'm okay with that.
But the ability to programmatically resolve the versioning quandary on the HD621 makes your argument not a particularly robust one.
Surround Music Fan/Computer Geek/Curmudgeon in training. --- 861v4, HD621, Panasonic BD-P55K, Toshiba HD-A35, Oppo HD990, Dish Network 622, Pioneer DV-668AV-S w/ DVD Upgrades mod, EW Fontaine II (x5), Velodyne DD-15 (x2), Seymour AV Ice blocks (x7)
|