forums.silverfrost.com

PaulLaidler · Posted: Sat Jun 30, 2018 2:28 pm Post subject: FTN95 beta testing

The latest FTN95 and DLLs are available for beta testing via the following download link. This is for users who have v8.30 and want to test the latest fixes. An archive called demo.zip contains an additional program that illustrates new features in ClearWin+. This archive should be extracted to its own folder.

Please do not post replies on this thread relating to %pl or %fr failures.

Please be careful to create backup versions and make sure that each file is copied to its corresponding installation folder.

https://www.dropbox.com/s/n4xhgkdz71viqrf/Beta279.zip?dl=0

PaulLaidler · Posted: Mon Jul 02, 2018 6:52 am Post subject:

Yes that is correct. That file only needs to change when exports used by clearwin64.dll are added to salflibc64.dll (very rare). It is usually rebuilt for a full release just to make it look right.

mecej4 · Joined: 31 Oct 2006 Posts: 1899

John Silver: I have seen similar problems occur when (by mistake) I used a PATH setting that caused a the FTN95 DLLs were not all from the same release or if some of the DLLs and the compiler (FTN95.EXE) were not from the same release.

Here is what I see from compiling demo.f95 from the 8.30.169 release, using only the .169 release tools, 32-bit mode.

1. The warnings regarding variable I being given a value but never used are appropriate, but the wrong line numbers are shown. The lines containing the assignment to variable 'I' are 261 and 533, whereas the messages give 259 and 526.

2. When there is more than one such assignment to a variable the value of which is never used later, only the first instance is listed. This is appropriate, although "...only the first occurrence is flagged..." would be more helpful in fixing the code to remove those warnings.

3. Linking demo.obj produces the puzzling warning message

PaulLaidler · Posted: Tue Jul 03, 2018 7:27 am Post subject:

Both programs work correctly for me but I tested using Plato under Windows 10 and not Windows 7.

The warning about WINDOW_UPDATE@ can be ignored. This routine is unusual in that it can take arguments of various types. The linker has noted what it thinks might be an inconsistency and issued a warning.

The problem about the missing icon relates to the need to use /r on the SRC command line when compiling the resource script. The linker should then be presented with the resulting .res file. I tested from Plato so I guess that Plato sorts this out automatically.

DanRRight · Posted: Wed Jul 04, 2018 2:23 am Post subject:

Paul, May be good idea to post the full this beta release with the installer on your website. I was unable to run my programs with this beta from start. Sometimes the mix of releases do not work well for testers. Specifically sensitive is Clearwin+ part of the FTN95.

mecej4 · Joined: 31 Oct 2006 Posts: 1899

John Silver:

You do not need a batch file for such a simple job; however, if you use one, don't expect some lines in the batch file to be treated as commands and some lines to be input directives for the linker.

The personal edition produces EXEs that differ from paid-up compiler generated EXEs only in that the former throw up a banner for a few seconds.

If you give the linker a file name with no suffix, it will add ".obj" by default. Therefore, you must explicitly add ".res" to the compiled resource file.

The following commands produced an EXE and ran it for me.

PaulLaidler · Posted: Wed Jul 04, 2018 3:40 pm Post subject:

Resource scripts have the .rc extension and a different form to that shown above.

Why not just run the demo from Plato?

mecej4 · Joined: 31 Oct 2006 Posts: 1899

Remove the first two lines, i.e., the lines starting with "!==" and "RESOURCES", as well as the last line, with "!==", from the input file to SRC.EXE, which should be given the suffix ".RC", as Paul noted.

mecej4 · Joined: 31 Oct 2006 Posts: 1899

You may have a corrupted or otherwise faulty version of the resource compiler. My SRC.EXE is 1,221,632 bytes long, dated 03/13/2018 (mm/dd/yyyy) and has a CRC checksum of 1221632. It prints a version number of 4.07 when run.

P.S. Correction: the checksum is 3295731287 according the the Cygwin cksum utility, and F1BB23AE according to the crc32.exe from http://esrg.sourceforge.net/utils_win_up/md5sum/ . The discrepancy needs to be resolved, but I'll leave that for another time.

mecej4 · Joined: 31 Oct 2006 Posts: 1899

mecej4 · Joined: 31 Oct 2006 Posts: 1899

I run Windows 10-64, but I think that you should not attribute the problems that you ran into to either the version of Windows or the versions of the various components of FTN95.

I can reproduce your second error (Error 343, from FTN95.EXE) by compiling for 32-bit when SRC.EXE is either not found by FTN95.EXE or cannot be run for some reason.

I even ran into the first error (attempt to read from address 1) once, but I do not know how to reproduce it without fail.

When /64 is specified, when FTN95 attempts to run SRC or SLINK64 and those EXEs are not found (or cannot be run), FTN95 fails to produce an output file but gives no hint of having failed. I think that this deficiency must be fixed soon. As it is, one has to list the directory contents to see if an EXE, OBJ or RES file was produced, or look for the signatures of SRC/SLINK to be output when they are run.

PaulLaidler · Posted: Mon Jul 16, 2018 5:23 pm Post subject:

mecej4 · Joined: 31 Oct 2006 Posts: 1899

PaulLaidler · Posted: Wed Jul 18, 2018 7:29 am Post subject:

mecej4

Thank you for pointing out this discrepancy.

mswinmod.f90 is either an old file from an earlier installation or it is included in the current installer by mistake.

window_update@ is located in the clrwin module which is compiled from clrwinmod.f95. It is also in clearwin.ins. In these files it is a subroutine.

johnham · Joined: 19 Jul 2018 Posts: 2 Location: Farmington

See the following test program using Beta279. Generates IOSTAT=202 reading from file. Reads correctly in this instance, but not in others.
PROGRAM FIXFORMNL
C This program test the namelist statement
INTEGER L1,L2,L3,L4,L5,L6,L7,L8
C Define namelist variables
NAMELIST / BINP2 / L1,L2,L3,L4
NAMELIST / BINP3 / L5,L6,L7,L8
C Open & read input file, check IOSTAT
OPEN(UNIT=9,FILE='DataNameList.txt')
READ(9,BINP2,IOSTAT=ICODE2)
READ(9,BINP3,IOSTAT=ICODE3)
PRINT *, 'ICODE2 =', ICODE2
PRINT *, 'ICODE3 =', ICODE3
CLOSE(9)
C Check output
PRINT *, L1,L2,L3,L4
PRINT *, L5,L6,L7,L8
OPEN(UNIT=10,FILE='FFNL.OUT')
WRITE(10,20)L1,L2,L3,L4,L5,L6,L7,L8
WRITE(10,25)ICODE2,ICODE3
CLOSE(10)
20 FORMAT(8I2)
25 FORMAT(2I5)
END

DataNameList.txt
&BINP2 L1=1, L2=2, L3=3, L4=4 &END
&BINP3 L5=5, L6=6, L7=7, L8=8 &END

FFNL.OUT
1 2 3 4 5 6 7 8
202 202

Thank you for all you do.
John