On Thu, 06 Aug 2015 15:09:40 -0700, Jim Thompson wrote:

On Thu, 06 Aug 2015 15:02:05 -0400, Spehro Pefhany
wrote:

On Thu, 06 Aug 2015 11:28:03 -0700, Jim Thompson
wrote:



I'm getting the general impression that I should avoid 64-bit to make
sure that my legacy programs will still work. Is that correct?

...Jim Thompson
--

No, you should make the jump and adapt (with VMware or some other
method) or dump the really old 16 bit programs. Most 32 bit stuff will
still run. It's time, and it will be the last major change for a very
long time.


--sp

Is there any way to tell what type a specific program is? I haven't
updated my PSpice since 2003 when OrCAD Crapture and Cadence stopped
improving PSpice (simulator) and tried to force everyone onto Crapture
:-(

...Jim Thompson

I don't know of any method that is certain. I'd say its even worse.
One of the 'features' of Windows is that it may work today - but with
a 'security update' it may stop working. With diligence you can
usually back out of a specific update, but that can become problematic
with more and more updates. You may be able to isolate your computer
from the web-slime as one alternative.

We run some legacy Windows apps that require 32-bit Windows though the
machines are 64 bitters. There's one app with a key dialog window that
- if you have to use it - causes its calling window to go blank.
Backing up several steps then forward one or two solves this (for now).

I agree with those who have suggested using virtualization software so
you can run particular software packages in cloistered environments,
though there can be consequences (e.g. with CPU speed, the display in
some circumstances, and possible hardware device interactions).