Try the 6.5 to 6.6 upgrade!

[Steven_L_Intel1]

Release Candidate 1 of the CVF 6.5 to 6.6 upgrade is available for folks here to try out. The actual CVF software is final - but I'd like some further testing of the installation process before we start burning this to CDs.

Requirements - you must have currently installed CVF X86 6.5 or 6.5A, either Standard or Pro. No other versions work with this, including beta 6.6 versions. (If you were beta-testing 6.6, uninstall and delete DFOR*.DLL from the Windows System folder. Then reinstall 6.5. Or wait for us to offer an upgrade from the 6.6 "Sanity" kit.)

Installation is like the other CVF upgrades. Download CVF-65-66.exe (44.2MB). Run it and follow the prompts.

If you try it, please reply here and tell me how it went.

Steve

[marklewy]

Steve,

I had several hh.dat files on my c: drive. So, I renamed them all and re-ran the 6.5 to 6.6 upgrade. The help is still not working properly.

BTW, I also have Platform SDK Pre-release (Build 5.0.2128.8) from MSDN installed. I wonder if that is related to this problem?

Another thing I noticed is that I had to re-install Visual Studio SP5 after the CVF 6.0 -> 6.6 install process, because I was getting a link error related to __imp___fpieee_flt.

Mark.

[Steven_L_Intel1]

Mark,

You should NOT have had to reinstall VS6-SP5! I wonder what happened there.

I have no idea if having the MSDN installation should make a difference.

Let's continue this at vf-support@compaq.com - please write there and describe the symptoms.

Steve

[Intel_C_Intel]

My upgrade from 6.5A Professional to 6.6 under Windows 2000 SP1 went through perfectly, without need of my intervening. A number of simple programs compiled and ran without trouble, but then I recompiled Steve Lionel?s Fortran_WinPrint.

As an aside, I find it a splendidly useful module (which I have modified to print out CR & LF characters correctly) that I use principally to print out files without leaving the program.

CVF gave the following error:

Error: This is not a field name that is defined in the encompassing structure [DMORIENTATION]
DEVMODE_struct%dmOrientation = Orientation

Examining old and new versions of DFWINTY shows that dmOrientation has now been moved to field1 of the DEVMODE structure. Changing the line above allows the module to compile and work correctly:

 
DEVMODE_struct%field1%dmOrientation = Orientation 

The point is that CVF6.6 is not fully backwards compatible. Good one, Steve!

Bear of little brain

[Steven_L_Intel1]

Bear,

CVF 6.6 includes completely new retranslations of the Win32 API declarations, based on the current MS definitions. MS changed some fields around, and this is one of the few incompatibilities. This IS called out in the release notes. Please read them!

Steve

[sabalan]

We should talk about the setup procedure only but maybe it is permitted to say this too: I "feel" (since I have not the old version left to compare) that the compilation with the release configuration takes longer time now than 6.5A, and, on the contrary, debug compile time is shorter. Besides, I get now some 7% bigger exe-files for release and some 12% bigger exe-files for debug configurations than with 6.5a. (I have compared console and Qwin applications).

Regards,
Sabalan.

[Steven_L_Intel1]

Napls,

Uninstall everything. Then delete the registry keys HKEY_LOCAL_MACHINESoftwareDigitalEquipmentCorporationVisualFortran and HKEY_LOCAL_MACHINESoftwareCompaqComputerCorporationArrayVisualizer Delete the Program FilesMicrosoft Visual StudioDF98 folder Then reinstall, select Custom and make sure that under the Online documentation component, all subcomponents are selected. Then upgrade. Let me know how it goes.

Windows 2000 seems to be extremely fussy about registering the online documentation. I haven't yet been able to determine what is going wrong here - this is not a new problem. But in the past, copying all of the files from the INFODFDOC folder of the CD-ROM to the DF98DOC folder cured the upgrade problems (after a re-upgrade).

Steve

[Steven_L_Intel1]

The upgrade works from either 6.5 or 6.5A.

For those of you who see just the MS documentation, please select, in Developer Studio, Tools..Options..Help System (rightmost tab) and make sure that the Compaq Visual Fortran collection is selected.

Steve

[Steven_L_Intel1]

The shortcut for documentation is correct. The PDF files are separate.

You have no hh.dat at all? Please search all your drives.

The logic for the doc upgrade hasn't changed since 6.5A, so I am very puzzled indeed. Let me think about this and I may contact you to get more info.

Steve

[pcurtis]

Me too. I had all the doc files on hd with 6.5, but now with 6.6 the system only wants to got to the CDROM. The previous posts/responses in this thread do not shed any light on this issue. Simple question... What is the procedure to move the doc files onto the HD, and correctly establish the HD as the default search path?

[Steven_L_Intel1]

The method is to copy all of the files in the INFODFDOC folder (but not any of its subfolders) to the DF98DOC folder on your hard disk, and rerun the upgrade.

I'd be interested in the following experiment. Install 6.5/6.5A and verify that the manuals are working as expected. Using an UNZIP tool, unzip the 6.6 upgrade to an empty folder. Rename VFD6566.RTP to be something else (.OLD or whatever). Run SETUP.EXE in the folder. You will get a message that the documentation update could not be found - click OK to let the upgrade continue.

When you are done, you won't have the 6.6 documentation added, but see if the 6.5 documentation still works. I wonder if the update of the HTML Help support breaks anything. (Seems unlikely to me, though.)

Steve

[davidgraham]

I have just updated to v6.6.
It took 'forever' to download (to the UK), the upgrade was simple, except for the question 'Some of the online documentation is being referenced from the CD - DFMAIN.CHM & MTS.CHM', but inserting the CD solved that.
I recompiled a program and got errors on type (T_MEMUITEMINFOA) as Compaq have now given it the correct name - type (T_MENUITEMINFO).
David

[Steven_L_Intel1]

napls, I did say this was a test of the installation process. If you were not comfortable with testing, you should not have installed it.

I can now reproduce the documentation problem on one of my own systems and have removed the upgrade from the FTP server until I get it fixed.

zhang, you reported the linking problem to vf-support, and we'll respond from there.

Steve

[Steven_L_Intel1]

I think I figured out the documentation problem. Try this...

Open a command prompt window (you can use Fortran Command Prompt for this if you want). CD to your ..DF98 folder. Type the command:

attrib -R /S

Close the command prompt window.

Now can you see all the documentation?

Steve

[Intel_C_Intel]

Steve,

Bingo!!! You're a magician. Thanks,

Tom

[Steven_L_Intel1]

I have put what I hope is the final version of the 6.5-6.6 upgrade here. If you installed the test version, and have issued the attrib command I described above, you don't need to download this again. Note - some users found that their antivirus program prevented the attrib from working, so disable it while you execute the attrib command. I do recommend that everyone who ran the RC1 version do the attrib thing, even if your documentation works. Also, NT/2000 users should be sure to run this from an account with Administrator privileges.

This upgrade will also be available on CD-ROM at a nominal charge ($19.95 in the US) from participating resellers worldwide - watch our web site for the announcement and details. (The CD won't be available until sometime in September.)

Please report any installation or operation errors to vf-support@compaq.com

Steve

[Steven_L_Intel1]

James,

I'm not sure what causes the problem you're seeing, but try this. Search your system for files named hh.dat and hhcolreg.dat. There may be more than one of each of these. Delete them. Now reapply the upgrade.

Last, go into Developer Studio, Tools..Options..Help System and make sure that the Default collection or the CVF 6.6 collection is selected.

These documentation errors are probably the most frustrating things to get right - HTML Help is so fragile, and it has information scattered throughout the system.

Steve

[Intel_C_Intel]

Kaplah! Renaming C:WINNTHelphhcolreg.dat to hhcolreg.old and rerunning the 6.6 upgrade did the trick. Thanks for your solution, Steve.

[Intel_C_Intel]

Steve,
Have this version of CVF 6.6 fixed the internal compiler error that I got in previous version of it?

Regards,
toppo

[Steven_L_Intel1]

James,

Glad that you got it going.

toppo,

The only change I made in this new version of the 6.6 upgrade was to fix the documentation installation issue - the installed software is identical.

Steve

[Intel_C_Intel]

I upgraded to CVF 6.6 on WinNT4 without any problems and without having to
run attrib -R /S on the Doc folder.
As i didn't have the samples installed, I copied the folder from the 6.5 CD to the hd, ran attrib -R /S, and reran the 6.6 upgrade. Now I have a silly question: were there any changes to the samples between 6.5A and 6.6? I'm interested in changes that accrue from dfwinty changes.

Thanks,
Gerry T.

[Steven_L_Intel1]

Yes, the samples changed - but not extensively so.

Steve