Please try the CVF 6.6C update

[larsm]

Steve

I got the same error as a couple of other users, viz.

Error: This module file was generated for a different platform or by an incompatible compiler or compiler release. It cannot be read. [F2KCLI]

when trying to USE the F2KCLI (Fortran 2003 standardized program arguments) interface from Winteracter.

It worked very well in 6.6B.

I will submit the files to vf-support@compaq.com.

I rewrote the stuff using the DFLIB procedures GETARG and
NARGS so it was no big deal, really, but I expected it to work as it was.

LarsM

[Steven_L_Intel1]

I can reproduce the module problem - not sure what happened here.It seems to relate to modules built with CVF 6.1A. We'll investigate.

I've pulled the 6.6C update for now until we get this settled.

[Steven_L_Intel1]

I see what changed to cause this to happen. I've asked the developer in charge of this area to fix it, and I should have a program that "fixes" the bad modules for you tomorrow.

[Steven_L_Intel1]

Attached is a tool that will "fix" the .mod files so that they are acceptable to 6.6C. There's a field in the module header that was apparently left uninitialized by 6.1A. Just run the program and select the .mod files to fix. Let me know how this works.

[durisinm]

This tool is something people should run only if they encounter this problem with modules, correct?

Mike D.

[Steven_L_Intel1]

Correct, though it should be harmless otherwise. You should use this only if you get an error from CVF that a .mod file generated by an earlier CVF is incompatible with the compiler version, hardware or operating system.

[gfthomas8]

If a CVF module is bandjaxed for whatever reason will recompiling it (with CVF of course) fix it and if not why not?

Thanks,

Gerry T.:smileyhappy:

[Steven_L_Intel1]

Yes, a recompile will also solve the problem. This tool is mainly for use with .mods you get from external vendors for which you don't have the source.

[Steven_L_Intel1]

It's been bought to my attention that .mod files from earlier DVF versions also have this problem, and the tool currently ignores those.