Streets and Trips broken by Anniversary "Upgrade"

Admittedly, my copy of Streets & Trips is aged at v2009. But it ran last month!

My fears about W10 included the fact that MS would eventually start obsoleting older software. I used MS S&T for quick evaluation of routes for trip planning, and also as a "just-in-case" to my GPS when traveling since I had the version with the (now useless) GPS receiver.


"Been there, done that!" The screen-shot is after I had already received the warning and gone through the Repair/Reinstall procedures using the original installation media.

They are not far from making enough of my software obsolete that Linux becomes a viable alternative. If my older, 3-license version of Office goes, I'm gone. Only the many Access reports I have developed over the years keeps me from doing that. I consider "End of Support" to mean no new patches, no developer support, and no user support. I have never considered "End of Support", which has been announced, to mean "Will no longer run". How about you?

Any suggestions other than to not expect old software not to run? Over the years I saw MSDOS applications drop off the cliff, then many of my early Windows applications. Now stuff that ran under W10 as recently as the end of July doesn't work.

Did you try to r-click Setup_ST.exe from your mounted install disc and click 'Troubleshoot compatibility' ? This will install it with compatibility for even as far back as XP. The software obsolescence tales are over blown. I am running Office 2010 Pro on every Windows OS incl 10. I also have old programs from 1999 that still work too. You just have to test compatibility and re-install if a major Windows upgrade uninstalls your program, which has never happened to me (knock on wood).

I have Streets and Trips 2013 (last version) and it works OK with the AU. I had an older version but it wouldn't install on Win 8 so I upgraded to the 2013 version (even using compatibility mode). However, some older software will install and work. I'm still using Office 2003.

mrgeek said:

Did you try to r-click Setup_ST.exe from your mounted install disc and click 'Troubleshoot compatibility' ? This will install it with compatibility for even as far back as XP. The software obsolescence tales are over blown. I am running Office 2010 Pro on every Windows OS incl 10. I also have old programs from 1999 that still work too. You just have to test compatibility and re-install if a major Windows upgrade uninstalls your program, which has never happened to me (knock on wood).

Thanks for the suggestion, but no joy! First, I tried running the W10 installation using Vista compatibility mode as Troubleshoot Compatibility suggested. Would not run. Next, I tried installing it as Vista compatibility, as suggested by default by Troubleshoot Compatibility. Would not run. I tried executing that version as Vista, as suggested by default using Troubleshoot Compatibility at the program menu level. Would not run. I repeated both of those steps forcing W7 compatibility for install, and for W7 execution, in the same fashion. All 5 attempts resulted in the same error that the Registry is kaput.

What did MS remove, forget to include, or screw up in the Anniversary "Upgrade"? Remember, it ran until then, from Day 1 of W10.

As far as software obsolescence I could probably come up with at least a dozen applications I have lost over the years, or had to upgrade, not for more capability, but because system "upgrades" made them obsolete. Some were rather costly and still-worthwhile products. I can maybe see some MSDOS items going away (which would not even run in compatibility modes), but have problems with Windows applications, even as "recent" as this, not running. But, obviously, even with compatibility modes, Windows isn't Windows.

Service calls are frequently removed or changed so they don't work with older software. Could those not have been retained and new service calls created to support previous software? In one case, they either changed the default font used by an application which had no provision to change fonts or deleted it completely from the Font Library. Totally destroyed that products functionality. And I can find no equivalent software, anyplace. Bits and pieces of the capability here and there, but never the total. Of course, it is of benefit to the entire industry to have obsolescence. Always touted as "New and Improved", of course. Not just as "Gotcha!". Then again, maybe that software company folded because they could not afford to market a product which required research and rewrite with each Windows release. Maybe a software version of the "Broken window theory".

Windows is so horribly large now, that a full rewrite would do it some good, but "ain't never gonna happen". For one thing, no one, or no group, at MS knows what is really in there. That is apparent in all the major and minor problems with the International W10 Beta Test of the past year, now supposedly completed, and the product perfect. If I look at my previous posts on here, the thingsI really care about are still broken. After over a year. File Explorer, which goes back to the first Windows versions is a mess. It can't handle things W7 handled with no problem, and keeps adding the strangest directories to my directory tree. (I tossed the atrocious Start Menu completely and stuck with Firefox since Edge's Favorites list is so obnoxious.)

On one of our 3 computers it turns off the mouse and/or the wireless adapter at random, and the only recovery is to "get out and get under", unplug the device, and reconnect it. Obviously some minor driver support problem.

I was a software engineer and applications programmer in aerospace for 26 years. The most dreadful thing any software guys have to admit is that it is "those stinkin' EEs" who have saved our bacon. Without faster, larger capacity devices, we would still be running MSDOS. Spacelab, for instance, had 4k machines, as I recall. "Bloatware" is the norm now, not restricted as in the first 2k computers I worked on where the fastest instruction (Branch if Bit Equal) took 1/10 of a second! Windows is now what, 15gB or so? I admit it does a lot more, and most of it works. But like I said, no one knows what is in there.

Buy more wood!

fireberd said:

I have Streets and Trips 2013 (last version) and it works OK with the AU. I had an older version but it wouldn't install on Win 8 so I upgraded to the 2013 version (even using compatibility mode). However, some older software will install and work. I'm still using Office 2003.

You will see from a post just above, that no matter what I try with the 2009 version, it fails.

I am using Office 2003 Professional, a 3-license version. It does all, and more, than I need in an Office product. The loss of it would be quite expensive. And now that MS has become a "Rent, Don't Buy!" firm, I am not sure how long before they find something in there to obsolete it. One good bit of supposition. I suspect many commercial firms might go for the jugular on that, who have no real interest in complaining about Streets & Trips going away.

I was a software engineer and applications programmer in aerospace for 26 years

I worked as a PCM Telemetry processor (decommutator) programmer at Goddard Space Flight Center on the Apollo project (a "few" years ago too).

fireberd said:

I worked as a PCM Telemetry processor (decommutator) programmer at Goddard Space Flight Center on the Apollo project (a "few" years ago too).

I started on 1401s at GM in 1964. Moved to Huntsville in 1968 and worked various aerospace and private SCADA systems, primarily in system architecture and software. Came in on the very end of Apollo, worked Site Defense, Boeing Brave 200/Pave Tiger (cancelled due to costs),

Boeing CQM-121 Pave Tiger - Wikipedia, the free encyclopedia

Spacelab, Orbital Maneuvering Vehicle (I was system architect and telemetry guy on the ground software for that, cancelled due to performance capabilities),

1984-7 - Orbital Maneuvering Vehicle (OMV) + Kits - NASA (American) - cyberneticzoo.com

SDI/"Star Wars", and other defense and NASA projects of one sort or another. Wrote on hardware ranging from 8086 microprocessors for oil platforms to Convex Super Computers. Assembly to Ada (ugh!). Great work, horrible conditions under which to do it. Pressures, lies, good employees doing the work of themselves and the slackers who were needed to keep the WBN (Warm Body Number) up to get enough billable hours to bilk the taxpayer. But I bet you saw a bit of that, too. No need to comment, no need for both of us to wind up in Leavenworth.

I spent 26 years at that, never had a day off that I didn't choose myself while working for 4 companies (one of them twice). Got out on the very first day I could retire and never once, in the 22 years since then have even thought "Gee, I wish I were back in the office today."

To keep from hijacking the thread..... I really am disappointed, almost disgusted, with W10.

I have no problems with Win 10. I have a recording studio and my recording program (Sonar Platinum) and associated software and hardware are all Win 10 compatible. I'm a retired LAN/WAN Network Manager (retired in 96) and still do some computer support for the local retirees.