Obsolence in software

[HouseCat]

Hey computer wizzes. It has come to my attention that one of my expensive music engineering programs has a ....(bear with me) obsolence exe. type command imbedded in it. What I mean is, once a new version of the program is available for purchase the current version I have starts crashing and giving me errors, forcing me to upgrade, even if I don't want to. This makes me very suspicious and angry that software engineers would sink to this low.

After contacting tech support, their answer was, "if you upgrade to our new 7.0 version, it will fix all of those errors."

I did not fall off the turnip truck yesterday!

This kind of crap is why I won't own a POS American vehicle, as they are guilty of obsolence more than anyone. This BS should be illegal!

So, is there a way to detect built in crash/error commands in the program files? Or, maybe you know of a PC doctor type program that will detect and take this crap out?

[Larry Gude (Premo)]

...I can't help you with the geek side but I can offer a few thoughts on obsolescence.

Is the software you have perfect? Assuming it is, what is the value of that, the price that was paid for it and that's it? Isn't there value in the people that made it making new stuff, staying in business, supporting what they've sold? How do they stay in business if there is no improvement, no upgrade, no service?

Imagine if the model T worked as good today as the day it was built. That's an extreme example, but it illustrates the point. There is a balance between a quality product, getting it to market at an acceptable price and staying in business to make newer and better products.

On the other hand, imagine a model T that only lasted a year. That would be too much in the other direction. No one wants software that has to have an upgrade once a week or once a month or once a year unless the value is there such as anti virus software or perhaps some sort of information type stuff like maps and current data.

So, certainly you are aware of this and maybe you've considered it and don't feel it is fair or reasonable in your case. Fair enough. I don't know your software or your business, so, I just wanted to throw it out there for whatever it's worth for your consideration.

[HouseCat]

Originally Posted by Larry Gude

...I can't help you with the geek side but I can offer a few thoughts on obsolescence.

Is the software you have perfect? Assuming it is, what is the value of that, the price that was paid for it and that's it? Isn't there value in the people that made it making new stuff, staying in business, supporting what they've sold? How do they stay in business if there is no improvement, no upgrade, no service?

Imagine if the model T worked as good today as the day it was built. That's an extreme example, but it illustrates the point. There is a balance between a quality product, getting it to market at an acceptable price and staying in business to make newer and better products.

On the other hand, imagine a model T that only lasted a year. That would be too much in the other direction. No one wants software that has to have an upgrade once a week or once a month or once a year unless the value is there such as anti virus software or perhaps some sort of information type stuff like maps and current data.

So, certainly you are aware of this and maybe you've considered it and don't feel it is fair or reasonable in your case. Fair enough. I don't know your software or your business, so, I just wanted to throw it out there for whatever it's worth for your consideration.

Larry, that's understood, but somewhere the line has to be drawn. I think this was on "Fleecing of America" once. Its not like I'm asking to make it perform better, or do more...I just want what I paid for.

Here's my issue: I paid $400 for this software. (You, being a musician know how expensive recording software is.) The software came out over 3 years ago. I just got around to purchasing it a year ago. Now, that version 7.0 is out..its taking a pre-commanded crash. I do not feel like I got my money's worth out of this product. Were it a matter of operating time, I wouldn't be so pissed, but they've embedded a different "crap.exe" file that crashes when a new version is available.

At least with vehicles, you have an operating time obsolescence rule. Even my beloved Japanese engineered vehicle unfortunately is destined for D-Day. But this is just ridiculous.

I should mention too, that my computer is 3 years old, and it being a Dell...(who is also guilty of this) could also be the culprit. I just wish I could tell which one is causing this and why there isn't a way around it. After all, it is a machine...and like old cars, there should be a way to keep it running that doesn't involve a degree in computer science. look at all the spyware removal programs they have out there. Spyware Doctor, Registry mechanic, AVG, etc...those programs were a god-send when they came out...how about something to stop the crap.exe files?

I don't think that's asking for too much.

[Larry Gude (Premo)]

Originally Posted by HouseCat

I don't think that's asking for too much.

...well, that's your call. Quickbooks does the same crap, but, for $2-300 a year, I stay current and it's easy to use even though the first version I got way back in the paleolithic era was just fine.

[clevalley (Premo)]

Originally Posted by HouseCat

Hey computer wizzes. It has come to my attention that one of my expensive music engineering programs has a ....(bear with me) obsolence exe. type command imbedded in it. What I mean is, once a new version of the program is available for purchase the current version I have starts crashing and giving me errors, forcing me to upgrade, even if I don't want to. This makes me very suspicious and angry that software engineers would sink to this low.

After contacting tech support, their answer was, "if you upgrade to our new 7.0 version, it will fix all of those errors."

I did not fall off the turnip truck yesterday!

This kind of crap is why I won't own a POS American vehicle, as they are guilty of obsolence more than anyone. This BS should be illegal!

So, is there a way to detect built in crash/error commands in the program files? Or, maybe you know of a PC doctor type program that will detect and take this crap out?

Is this software package been on the same computer, with the same O/S and the O/S has not changed? If so, they are feeding you BS.

Now, if the O/S has been updated via service packs, it is quite possible the O/S Kernel or supporting modules (for lack of a better term) has changed enough where the application has gone out of revision. It does happen and normally the vendor should have a patch to fix whatever update the O/S vendor has changed.

If you have changed O/S's - all bets are off.

Most of the times, designing software will have a way of running the app in debug mode where it logs error information, but you will have to dig into developer documentation or some type of support forum for this information...

Originally Posted by Larry Gude

...I can't help you with the geek side but I can offer a few thoughts on obsolescence.

I digress .... I own and Drive the following (not all @ once )

1967 Jeepster Commando
1969 VW ( Baja Mod )
1983 Jeep Wagoneer
1995 Saturn (daily driver)

Wife has a 1994 Ford Explorer

and we share a 1996 Ford Bronco ....

all bought and paid for, only thing needed is spare parts, GAS and OIL

I am still using Windows XP and have a Win 98SE Box for older games that require a Monster II 3D graphics card

The House I live in was built in the 1950s ....

should I dump it all to keep some one in the business of making new widgets

[Jeff]

Originally Posted by HouseCat

Hey computer wizzes. It has come to my attention that one of my expensive music engineering programs has a ....(bear with me) obsolence exe. type command imbedded in it. What I mean is, once a new version of the program is available for purchase the current version I have starts crashing and giving me errors, forcing me to upgrade, even if I don't want to. This makes me very suspicious and angry that software engineers would sink to this low.

After contacting tech support, their answer was, "if you upgrade to our new 7.0 version, it will fix all of those errors."

I did not fall off the turnip truck yesterday!

This kind of crap is why I won't own a POS American vehicle, as they are guilty of obsolence more than anyone. This BS should be illegal!

So, is there a way to detect built in crash/error commands in the program files? Or, maybe you know of a PC doctor type program that will detect and take this crap out?

"Format C:"

[Larry Gude (Premo)]

Originally Posted by RadioPatrol

I digress .... I own and Drive the following (not all @ once )

1967 Jeepster Commando
1969 VW ( Baja Mod )
1983 Jeep Wagoneer
1995 Saturn (daily driver)

Wife has a 1994 Ford Explorer

and we share a 1996 Ford Bronco ....

all bought and paid for, only thing needed is spare parts, GAS and OIL

I am still using Windows XP and have a Win 98SE Box for older games that require a Monster II 3D graphics card

The House I live in was built in the 1950s ....

should I dump it all to keep some one in the business of making new widgets

...I'm sorry, but I did I miss the Model T? I don't seem to see it anywhere on there?

Originally Posted by Larry Gude

...I'm sorry, but I did I miss the Model T? I don't seem to see it anywhere on there?

If I owned one ..... like the 1960's cars aren't old enough ...