Progress V8.2 Windows Server 2012 Question

[DeadWalker]

Can anyone tell me if you can install progress database version 8.2 on a windows server 2012 operating system?

 

[TomBascom]

You could try it and find out but it is unlikely that it will "just work".

Old versions of Progress have had trouble with new versions of Windows for a long time now. Installs usually hang. One common problem is the "isdel.exe" part of things needing to be killed via taskmgr. Assumptions about how the registry works that were reasonable in 1995 don't work so well in 2015...

You might be able to batter it into submission. For instance, I have a version 6.2 that sort of mostly kind of "works" well enough to extract data from old orphaned databases in an emergency. But you wouldn't want try to run it in real life.

 

[DeadWalker]

You could try it and find out but it is unlikely that it will "just work".

Old versions of Progress have had trouble with new versions of Windows for a long time now. Installs usually hang. One common problem is the "isdel.exe" part of things needing to be killed via taskmgr. Assumptions about how the registry works that were reasonable in 1995 don't work so well in 2015...

You might be able to batter it into submission. For instance, I have a version 6.2 that sort of mostly kind of "works" well enough to extract data from old orphaned databases in an emergency. But you wouldn't want try to run it in real life.

So I would be better of building a WIN XP 2002 Version machine to run it on if I needed for long term use?

 

[DeadWalker]

So I would be better of building a WIN XP 2002 Version machine to run it on if I needed for long term use?

Thanks for the reply btw.

 

[TomBascom]

Win95 would be more appropriate...

 

[Rob Fitzpatrick]

So I would be better of building a WIN XP 2002 Version machine to run it on if I needed for long term use?

What is the nature of your "long-term use"? Is this a production system?

With old software (from any vendor), you are faced with the choice of:

• trying to install and configure on a modern operating system that the vendor never tested with and couldn't have anticipated, and dealing with the various ways that this now-unsupported software may be broken;
• trying to install on an operating system of the same vintage as the software, where you will probably be able to install without issue but in your install of an unsupported OS on modern hardware you may be faced with similar compatibility issues to the choice above;
• upgrading the software so you can run your application on a modern supported platform on a modern supported operating system on modern supported hardware.

If this is an application you keep kicking around so you can reference "how the old system used to do things", you may not be able to justify the expense of an upgrade. But if this a mission-critical application you should try very hard to take the upgrade path unless you can prove to yourself beyond doubt that either you can't afford it (in which case, cover your assets) or it isn't technically possible (in which case, make sure you have very good backups and plan for disaster).