Post by Edward RawdePost by Don YPost by Don YPost by Edward RawdeIt's been a long time since the average software update switched from
actually fixing anything to forcing the latest version into use.
Unfortunately, you may not realize that this has been imposed on you
until it is too late to "go back".
I preserve copies of old files in their original forms (and file formats)
to safeguard against this biting me -- again! This lets me decide if I
want to abandon the "more recent" version of the file in favor of returning
to an earlier version (with known performance characteristics in the earlier
application version)
Of course, maintaining old versions is a piece of cake with VMs
(and folks who haven't adopted SOME form of that technology are
needlessly hindering their own productivity!)
I frequently find a need to use an older program on Windows XP, including posting here.
It's all in a VM now, accessed by remote desktop, so I can be XP one second and Win10 the next.
Also useful when playing with cpu intensive software such as AI.
Leave it running on another computer then get the result by remote desktop.
I build VMs of each project's development system and archive them on one
of my ESXi servers. So, when I need to revisit a project, I am not
constrained by <whatever> the current hardware/software environment
"du jour" happens to be.
[You can access a VM via a web service through ESXi; so just open a browser
from ANY host]
Prior to this, I would take an image of the system and store it offline.
In hindsight, I probably would have built smaller VMs for each individual
application (plus a small set of common utilities) and shuffled files
between VMs. Multi-terabyte images eat through disk space pretty quickly
(OTOH, disk space is cheap). As I can have multiple VMs running at any
given time, it's a simple matter to move between them, based on the task
at hand.