Approximatrix Forums — Launch file name

Re: Launch file name

null@example.com (jeff) — Mon, 17 Jul 2017 11:29:44 +0000

Don,

I'm glad you figured out the cause of the issue. However, I would suggest running some sort of virus scanner. I usually just use Microsoft's own under Windows 10, but that's merely a suggestion on my part. I don't endorse it or anything.

Re: Launch file name

null@example.com (Don Hazlewood) — Fri, 14 Jul 2017 16:16:35 +0000

Hi Jeff,

That's the output I'm expecting.

I'm running Windows 10 version 1703, build 15063.483 and I have COMODO a/v installed.

I'll try disabling COMODO and recompiling and running.

Thanks!!!
Don

Well, killing COMODO didn't do it. Still doesn't work for me. Do you think it's the Windows version?
Don

At 12:12 pm CDT: It WAS comodo. After I completely uninstalled it and reran my program, it worked perfectly. I get bit more by Virus Scanners than I do by Viruses...

Again, thanks for letting me take up too much of your valuable time.
Don

Re: Launch file name

null@example.com (jeff) — Fri, 14 Jul 2017 13:44:43 +0000

Don,

I just loaded, built, and ran your project on Windows 10 using Simply Fortran 2.38, and I had no issues. After the run, I had a new file, Example4.OUT in the project directory, and I had a few minor messages about temporary arrays in the Console tab. Your problem sounds like it might be system-dependent.

What version of Windows 10 are you using? You can check the specifics by running winver from the "Search Windows" box on the task bar (or the Run dialog). Specifically, I'm interested in the Version and OS Build numbers.

Also, do you have a virus scanner installed? Virus scanners that aren't Microsoft's own regularly interfere with Simply Fortran as most are quite aggressive towards compilers and their outputted executables.

Re: Launch file name

null@example.com (Don Hazlewood) — Fri, 14 Jul 2017 13:27:55 +0000

Just sent it to you.
Don

Re: Launch file name

null@example.com (jeff) — Fri, 14 Jul 2017 11:46:17 +0000

Don,

Just zip up the source code and project file (with the .prj extension), and email the zip file to support@approximatrix.com. Do not include the compiled executable in the zip file, though, because email server will block the entire message in that case.

Re: Launch file name

null@example.com (Don Hazlewood) — Thu, 13 Jul 2017 20:42:35 +0000

Send me instructions on how to do it and I'll gladly turn it over to you.

Re: Launch file name

null@example.com (jeff) — Thu, 13 Jul 2017 18:26:02 +0000

Well, IOErr being zero means the file was successfully opened, and ErrMsg would be left unmodified in that case. I'm not sure, though, why you can't find the output file, though. Would you be open to sending the project and source code along to support at approximatrix.com?

The file should be opened in the same directory as the project file (ending in .prj) based on the information you've given so far.

A friend, who is a Professor of Computer Science at Kansas State University, has compiled this code and it runs successfully. He uses gfortran.

Simply Fortran is using gfortran as well, but it is probably a different version.

Re: Launch file name

null@example.com (Don Hazlewood) — Thu, 13 Jul 2017 14:20:13 +0000

IOErr is zero and MsgErr is a bunch of hex data (MsgErr is defined as Character(256). So, to me, it doesn't look like it really helps any. A friend, who is a Professor of Computer Science at Kansas State University, has compiled this code and it runs successfully. He uses gfortran. If you have any questions for him, I'll be glad to pass them along.
Don

Re: Launch file name

null@example.com (jeff) — Thu, 13 Jul 2017 11:12:54 +0000

Don,

Can you add the status indicators to this OPEN statement as well? Perhaps it will yield more info:

       Open (Unit=nPrnt,File=File_Out,Action='Write',Status='Unknown',IOSTAT=IOErr, IOMSG=ErrMsg)
       If(IOErr .NE. 0) Then
           Print *, IOErr, ErrMsg
       End If

Re: Launch file name

null@example.com (Don Hazlewood) — Wed, 12 Jul 2017 20:27:43 +0000

Thanks, I'll give it a try.

Nope, didn't create the output file. No error or anything. I'm probably filling up the "cloud" with all my output....

Re: Launch file name

null@example.com (baf1) — Wed, 12 Jul 2017 20:19:54 +0000

Try

Open (Unit=nPrnt,File="abc",Action='Write',Status='Unknown')

as a test. I suspect that variable File_Out is somehow not defined properly.

Re: Launch file name

null@example.com (Don Hazlewood) — Wed, 12 Jul 2017 14:28:32 +0000

It's opened explicitly as:

Open (Unit=nPrnt,File=File_Out,Action='Write',Status='Unknown')

where 'nPrnt' is now 106.

I also tried changing nRead back to 5 and nPrnt to 6 and putting Close statements for both when the file_open program is entered. It did not give the error 9, but I still can't find the output and I can't get anything to write to the console.

11:00 CDT - I just updated to 2.38 and still get the same results.

Re: Launch file name

null@example.com (jeff) — Wed, 12 Jul 2017 11:15:58 +0000

I would guess that using 5 or 6 may be at issue on current versions of Windows 10, causing the error in the OPEN statement. I might work better, actually, if run in an external console.

Is the output file OPENed explicitly, or are you just writing to a unit number?

Re: Launch file name

null@example.com (Don Hazlewood) — Tue, 11 Jul 2017 20:44:23 +0000

Jeff, that seems to have been the problem. Thanks, I would NEVER have thought of that!

However, I cannot find the output file anywhere, not in the project directory, not on C:. Can you help with that?

Re: Launch file name

null@example.com (Don Hazlewood) — Tue, 11 Jul 2017 20:27:28 +0000

I think I am using 5 as input and 6 as output. I'll change them and let you know how it works.