Try the 6.5 to 6.6 upgrade!

Try the 6.5 to 6.6 upgrade!

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

Steve - Intel Developer Support
44 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Good to see that you have the documentation problem that other users are experiencing fixed. I refrained from following up on my particular problem in the interim so as not to confuse the issue for other readers, but getting back to it: I copied *.CHI and *.CHM from CD-ROM to hard disk and now C:Program FilesMicrosoft Visual StudioDF98DOC has 188 files, 149 MB. Subsequently I did the attrib trick you outlined earlier in the thread. But still no joy. Attempting to get to the documentation for LineTo (as in another thread in c.l.f.) still requires me to insert the CD-ROM. Browsing to the above-mentioned directory in the error box that appears when I attempt to access the documentation for LineTo results in the error box reappearing and hitting the &ltENTER&gt key a few more times just results in a "The page cannot be displayed" page. Am I missing something simple or is there another step remaining in my odyssy?

Installed fine for me over 6.5a Pro under WinXP Pro build 2505.

Installation is fine, but I got internal compiler error (C0000005) on CVF 6.6. I upgraded from CVF 6.5A.

The function is like:
function func(ext_fn)
where ext_fn is external function.

What can I do with this bug?

toppo

Notes... 2 minute download (after your server came back up) and 1 minute install ... at least your upgrades are getting quicker for the user to apply. There was a problem with the upgrade from 6.0A to 6.5 IIRC and also with this (6.5A to 6.6 on Win2k Build 2195, SP1) upgrade that some help file (does DFMAIN.CHM ring a bell?) wasn't found on the hard disk and I had to insert my CD-ROM and browse to it to proceed with installation. There was another file the installation program complained about, too, but after I doubleclicked the first file the installation completed normally. The name of the menu item under Start|Programs is still 'Visual Fortran 6.0' -- I wish your installation programs would fix that. Under Help|About Developer Studio one gets the right version, though.

Tried a few benchmarks. Results were mostly a bit faster. In the polyhedron suite, I noticed that you produce a (valid) warning in INDUCT.F90 that either you didn't before or I didn't notice before. What happened in RNFLOW.F90? I see that you got tired of getting clobbered in WH4.FOR. And what about SM4.FOR? Oh, you naughty boys & girls ... John will probably have to uncomment the line

C if ( sum.gt.1E30 ) print *,i,j,k,m,sum

so that your latest upgrade doesn't just throw the whole thing out.

Upgrade from 6.5A was smooth enough for me, it just happened. I have a Win2000 machine.
However, I have noticed a glitch. When trying to open the on-line documentation via
the short cut on the start menu, it pointed to
C:WINNTHH.exe "C:Program FilesMicrosoft Visual StudioDF98DOCdf60.col"
instead of
C:WINNTHH.exe "C:Program FilesMicrosoft Visual StudioDF98DOCdfmain.chm"
after amending that it seams to work.

/Bjrn

toppo - please send a problem report to us at vf-support@compaq.com, and include the problem source. Be sure to mention that you're using 6.6 (from the upgrade I posted on the forum).

James, your observations with the Polyhedron suite are consistent with our own. RNFLOW is still being looked at.

Bjrn, this upgrade doesn't touch the shortcuts (indeed, that's why the name is still wrong). DF60.COL is the correct file for the help shortcut. What happens to you when you try to use DF60.COL?

BTW, the UI and almost all of the logic of these upgrades are written in Fortran.

Steve

Steve - Intel Developer Support

Steve,

I had a similar problem with the help files except the other one that the installaition complained about was mts.chm. I was able to locate the first file in the docs subdirectory, but browsing to it and double clicking on it did nothing. Apparently, it wanted me to find both of the files before allowing me to proceed. Anyway, I cancelled out of it and the installation proceeded without another hitch.

Tom

Yes, the upgrade wants to find a folder that has both dfmain.chm and mts.chm in it. This is if you are referencing the documentation from CD-ROM. I'll take another look at that section and see if I can improve it. If you have all of the documentation installed to hard disk, this isn't an issue.

Steve

Steve - Intel Developer Support

Steve,

After upgrading my CVF 6.5A Standard Edition, the CVF 6.6 help now only contains the Platform SDK help. I remember having similar problems upgrading from 6.0 to 6.1 - the workaround that time was to re-install CVF from scratch.

I'm running Windows 2000 Professional SP1.
Visual C++ 6.0 Enterprise edition SP5 is also installed.

Mark.

I wish I could reproduce this problem with the docs here. Mark, did you get any message about locating the documentation files?

I have an idea - go to Tools..Options..Help System and select Compaq Visual Fortran as your preferred help collection.

Steve

Steve - Intel Developer Support

The darned thing about the missing DFMAIN.CHM (or whatever) file is that when I installed 6.0A from the CD-ROM, I thought I was installing everything (by selected custom install and checking all boxes) but you're telling me that I am missing something, either due to failure to scroll down to one of the boxes during my initial installation, or due to a bug in the original installation program itself. CVF documentation seems to work OK, though. What am I missing that I should have on my hard disk? It would be just groovy if the upgrade programs would give me the option to install whatever it is that I seem to be missing rather than just telling me that I'm missing it.

The DVF 6.0 installation did not, by default, copy all of the MS Platform SDK documentation to your hard disk. We changed that in 6.1, or perhaps 6.5. The upgrade is supposed to be able to handle having some of the documentation on the hard disk and the rest referenced from CD - it always does for me - but I have heard from many customers for whom it doesn't. I wish I knew why. The simple solution is to copy all of the .CHI and .CHM files from the INFODFDOC folder of the CD-ROM to the DF98DOC folder of your hard disk and rerun the upgrade.

Steve

Steve - Intel Developer Support

The simple solution would be for the installation program to check to see if the files are there (which it already does, hence the error in finding the files), and, if it can't find the files, install them into the DOCS subdirectory and then go along its merry way.

Tom

As I said, I didn't use the default installation, but rather the custom installation and tried to install everything. Evidently this didn't happen. I looked in C:Program FilesMicrosoft Visual StudioDF98DOC and found DFMAIN.CHI (7/9/01 5:40 A 233 KB) DFMAIN.CHM (7/9/01 5:40 A 3.59 MB) and MTS.CHI (6/12/98 5:24 A 79.9 KB) so I tried simply running the 6.6 upgrade again and once again got the message:

Some of the online documentation is being referenced from CD-ROM. Click OK to browse for the folder containing documentation files DFMAIN.CHM and MTS.CHM, (usually the INFODFDOC folder of your Visual Fortran CD-ROM), or Cancel to omit missing manuals from the collection.

Note the double-backslashes... thought you were writing a C string when you were writing a Fortran string? At this point I inserted the 6.0A CD-ROM and clicked OK and the installation program automatically navigated to the folder mentioned in the message. This time I doubleclicked on MTS.CHM but after completion of the installation, that file still hadn't been copied to my hard disk. Consequently I copied it by hand using Windows Explorer and reran the installation. This time there was no error message. All that work and the installation program didn't even want to update the MTS.CHM file! Your advice to copy *.CHM and *.CHI and rerun the upgrade is rather more cryptic out here in end-user land that you might think. Is there an easy way to do the copy without creating second versions or overwriting existing files? Are we supposed to rerun the 6.5 upgrade, then the 6.6 upgrade, or just the 6.6 upgrade? Life would be easier out here if the installation program gave us the option to copy everything over to the hard disk where it belonged in the first place (I don't know why this didn't happen on the initial custom install) rather leaving us guessing about the next component that might have been omitted in the original installation.

If MTS.CHI was in your DOC folder and not MTS.CHM, that means you did not select to have the Platform SDK manuals installed to your hard disk. (The CHI is the index only, the CHM is the actual manual.)

The upgrade is not attempting to copy the CHM file - it merely wants to know where it is, so it can register it with the documentation collection. If you manually copied MTS.CHM, and reran the upgrade, you will probably find that when you open the VF help collection that there is just one platform SDK manual there instead of the dozens that should be there. If you want everything, copy all the CHM files and run the upgrade again.

The SDK docs are 125MB, so I don't know if people would appreciate having those copied over! But I suppose I can offer it as an option.

Steve

Steve - Intel Developer Support

Steve,

Maybe (probably) I'm missing something in this discussion, but, as I said earlier, it would be simpler to copy the two offending files into the appropriate folder if the installation program cannot find them and then go about its business. The file sizes are < 4 Mb total, so this shouldn't be a major inconvenience once they are compressed. I don't see any need to install all the SDK help files if they weren't originally installed, just the ones that the 6.6 upgrade installation program is looking for.

Again, maybe I'm missing something, but it seems to me that the goal of installation programs is to make the installation seamless. Copying the two files (as opposed to the entire SDK help system) would solve the problem?

Tom

Steve,

My current help collection was Fortran, so no joy there, I'm afraid. The upgrade program did ask me to locate dfmain.chm, so I used the one on the 6.x to 6.5 upgrade CD.

I decided to reinstall CVF from scratch. So, I uninstalled CVF, and re-installed it
from the 6.0CD, the 6.x to 6.5 Upgrade CD, and CVF-65-66.exe. I did a complete custom install from the 6.0 CD so all the documentation is on the hard drive.

Unfortunately, the help is still not working properly. The root for my help is titled "Compaq Visual Fortran 6.6". The only book beneath it is "Platform SDK", and the default page is "Built-in ASP Objects Reference". This applies whether the help is invoked from Developer Studio or from the Online Documentation start menu entry.

Help was working OK in 6.5 before I did the upgrade.

Mark.

I have W2K Pro and had CVF 6.5a Pro. The installation was smooth and painless. No problems with help files etc. discussed here. A minor observation: Tools | Options? | Help System is still showing "Compaq Visual Fortran 6.5 (7/11/2000)" while the HTML help itself shows "Compaq Visual Fortran 6.6" in the Contents window.

Coming to Array Viewer, "The "black border problem" due to a bug in Microsoft's OpenGL implementation for Windows 2000" is fixed as promised (see here)
BUT, is it possible to fix a bug without creating some other(s)? Apparently not! Try to view an ARRAY(3,600) while debugging. In the array viewer click on the button for "Vector Graph": the graph is going to disappear and the graph window is going to hang! You can not go back to "Plane Graph" either! You are saved only if you try to change the size of the array viewer window. Only then you can see your "Vector Graph" and can carry on.

Another thing that I have noticed, both in 6.5a and 6.6, is that if you view an array while debugging, stop debugging, run the program again to the break point and view the array, stop debugging, and repeat this a few times (varying between 2 and 7 times for me), then the Developer Studio is going to hang (Program not responding). Some memory leakage due to Array Visualizer?

Regards,
Sabalan

Tom,

Let me try again. The upgrade is looking for DFMAIN.CHM and MTS.CHM as "markers" that help it identify a place where all of the online documentation can be found. It does not want to copy these files, it simply wants to know where to find a folder containing both of them. In an installation where the SDK documentation is referenced from CD-ROM, the VF documentation will be on your local disk and the SDK documentation on CD. The help collection is created with each manual recorded as being wherever it is, hard disk or CD. The upgrade, not having a copy of all of the documentation, needs to be able to find the right folder.

If you simply copy MTS.CHM into your DOC folder, you fool the upgrade into thinking that all of the manuals are there. The result is that when it goes to try to create the collection, it won't find the rest of the SDK manuals and will omit them from the collection.

If you want everything on your hard disk, copy all of the CHM files to your DOC folder and run the upgrade, so it can register them.

Mark - try this. Search your hard disk for a file called hh.dat Rename it to hh.old or something like that. Now reapply the 6.6 upgrade.

Sabalan - please report the Array Visualizer problem to vf-support@compaq.com Thanks for picking up on the collection name - I'll fix that.

Steve

Steve - Intel Developer Support

Steve,
I have sent the problem report and the source code, and support reference ID is #CVF15186.

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.

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

Steve - Intel Developer Support

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

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

Steve - Intel Developer Support

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.

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

Steve - Intel Developer Support

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

Steve - Intel Developer Support

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

Steve - Intel Developer Support

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?

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

Steve - Intel Developer Support

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

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

Steve - Intel Developer Support

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

Steve - Intel Developer Support

Steve,

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

Tom

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

Steve - Intel Developer Support

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

Steve - Intel Developer Support

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

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

Regards,
toppo

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

Steve - Intel Developer Support

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.

Yes, the samples changed - but not extensively so.

Steve

Steve - Intel Developer Support

Steve, I have tested CVF 6.6 for a compiler bug that I got in version 6.5A, it's OK. But I got another bug in 6.6 and did not occur in 6.5A (I have submitted to vf-support@, but they were unable to find workaround).

Do you plan to fix a compiler bug on a final version 6.6?

toppo

toppo,

There will be no changes to 6.6 - a fix for your bug, when found, would go into the next update after that. Once we understand what the problem is, we can probably get you some sort of solution soon afterwards.

Steve

Steve - Intel Developer Support

Leave a Comment

Please sign in to add a comment. Not a member? Join today