Tom,
Basically the costs are relevant if the present software can no longer be upgraded to add new features if the older machine won¡¯t fully support migration to a new OS (i.e drivers will no longer work, etc.). Then if that is the case you must move on to a new OS on a new machine to accomplish that task leaving the older machine behind and reinstalling upgraded software from the same manufacturers (if they still exist). Get my ¡°can of worms¡± theory here?
Things are working fine here. I have plenty of resources to accomplish my tasks. The main thrust is to keep dancing around newer software/products so as to minimize time and money wasted (having to do ¡°science experiments¡±) and get on with life. My actual goal is to serve clients who have those legacy systems. It sometimes becomes difficult to deal with older systems that have incurred failures whereby they either lose control of high $$ value systems or cannot interface to them in other ways.
Before this topic grew legs I believe the original interest was why many people are experiencing various anomalies regarding use of the groups.io system after an apparent ¡°upgrade¡± causing more wasted time trying to find approaches around the problems encountered. I have found a simple solution since then without spending a large effort. Groups.io is merely a convenience, not a requirement.
Greg
