A work project I'm one entails migrating old applications to new servers. Our base server install these days is Windows 2008 R2. For those not in the know, this is a 64-bit OS only. You can run 32-bit applications, but the OS itself installs as 64-bit mode, and 32-bit support (especially for older applications) can be spotty.
To help mitigate some of the 32-bit issues, you can specify that certain applications run in compatibility mode. The system includes a number of predefined compatibility levels, from Windows XP SP3 all the way back to Windows 95.
One application that we're migrating is getting rather long in the tooth, but it still does the job. As such, there is just no impetus to actually upgrade. Instead, we're trying to just make it work in the new server environment. In order to get the application installed, I had to run the installer itself in Windows XP SP3 compatibility mode.
Everything seemed to install without a problem, but when I tried to launch the app, it kept crashing out. I realized I forgot to set the compatibility mode, so I went into the properties and set it to Windows XP SP3.
No joy.
Windows XP SP2.
No joy.
Windows 2000.
No joy.
At this point, I'm really starting to get frustrated.
Windows NT 4.
No joy.
Guess what ladies and gentlemen?
I had to dial the application compatibility all the way back to Windows 95 in order to get this thing to work.
Remind me again what century I'm in?
I have an app running on a couple of my servers that was written when I was in high school. In one of the folders on my desk is a letter from the vendor stating that the app had been superseded and that they would not be making it Y2K compliant.
ReplyDeleteStay strong, brother.