License Number?

[Geoffrey_P_]

I have Compac Visual Fortran Professional Edition for Win32x86 Systems version 6.6A that I haven't been using lately, and I have a new computer and harddrive and am currently running 32 bit Windows 7. When I try a fresh installation, the serial number that is printed on both the CD sleeve and on the original packing envelope don't work - i.e., setup keeps telling me the number (which of course I have checked multiple times) is invalid. How do I fix this?

[mecej4]

I cannot give you specific advice about installing CVF6.6A on W7-32, but here is something that often works and is worth trying. 

From Windows Explorer, locate the installer (setup.exe, install.exe, etc., depending on the package). Right click on it, and select Troubleshoot Compatibility. Wait until Windows checks the program and offers you a choice between "try recommended settings" and "troubleshoot program". Choose the latter and select "This program worked in earlier versions of Windows...". Depending on the software that you are attempting to install, choose "the program requires additional permissions". Click "Next", and select Windows XP SP2 or whatever worked previously for the software.

Note that there is no official support here or anywhere for installing an old package such as CVF.  The last update released by Compaq/HP was CVF6.6C, without which CVF6.6 may not be fully functional on Windows 7.

[Kevin_D_Intel]

As mecej4 noted, unfortunately this is not something within our ability to help. There were other recent comments about problems installing CVF on Win7/8 here (https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/559840). It is unclear how successful this might be.

[TimP]

I ran CVF successfully under XPM on Win7.  This requires a platform with a BIOS where XPM can be installed,  It doesn't perform as well as CVF would under an older Windows version.

You may have better luck with install if you browse down on the install CD to the actual 32-bit setup.exe, as the auto-launcher is a 16-bit script.

[mecej4]

Tim Prince wrote:

I ran CVF successfully under XPM on Win7.  This requires a platform with a BIOS where XPM can be installed,  It doesn't perform as well as CVF would under an older Windows version.

I have CVF running fine on Windows 10 X64. It actually runs better on Win 10 than it did on Win 8.1 X64, and Win 8 does not provide XPM. On the latter, if I ran MSDEV or DFDEV from the CVF command prompt to start a debugging session, those programs would crash, so I had to run DFDEV from a different command window or from the Start Menu, but then there were problems with PATH not being suitable for the EXE being debugged. Those problems disappeared after upgrading to Windows 10.

I have found it more convenient to keep an Zip archive of the CVF directory tree from an older XP machine on a thumb drive for installation on newer versions of Windows, than to attempt to install CVF from the CD and then try to obtain the 6.6C update from HP.