Launch file name (Page 1 of 2)

Version 2.34, build 2366 does not have this problem.

Jeff,  not sure what's going on, but now I can't get any version to work, so I'm checking for changes in my program.  So no need to rush for a solution.....
Don

Don,

I'll see if I can replicate the problem.  It should just work on any version of Windows 10.  What exactly are you entering into Launch Options?

You can remove the ".\" from the directory field.  Simply Fortran will default to the project's directory if it's blank.

What exactly did you mean by " does not recognize the input file name given in the Launch Option?"  When you simply print the command line argument corresponding to "Example.WDC," what is printed?

I'll see if I can replicate the problem on a Windows 10 system with the most recent update.

Don,

If you Print *, the command-line argument prior to the OPEN statement, what is the result? 

I'm trying to sort out if it is a problem with the command line handling in the runtime or the Launch Options in Simply Fortran.

Sorry, Don, I think we're having some miscommunication. Could you try, in your code:

       Print *, File_In(1:length)
       Open (UNIT=nRead,FILE=File_In(1:length),ACTION='READ',STATUS='OLD',IOSTAT=IOErr)

I know you're saying that File_In(1:length) is 'Example4.WDC', but I want to confirm that it is.

Don,

You can get a text error message from OPEN as well using the IOMSG argument in the OPEN statement:

Character(256)::ErrMsg

!...

       Print *, File_In(1:length)
       Open (UNIT=nRead,FILE=File_In(1:length),ACTION='READ',STATUS='OLD',IOSTAT=IOErr, IOMSG=ErrMsg)
       If(IOErr .NE. 0) Then
           Print *, IOErr, ErrMsg
       End If

When the file isn't present, IOErr seems to be 2 for me, but it may be runtime-dependent. What is the message you're seeing?

Don,

What unit number are you using?   What's the value of nRead?   Is it possibly 5 or 6?  Or have you used this unit number before in your code?

The error implies you're reusing a unit number without actually closing the unit prior to this OPEN statement.  Units 5 and 6 are especially problematic because they are reserved for standard input and output.  Both 5 and 6 should always be avoided for files for compatibility.  I usually suggest using unit numbers in the hundreds.

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?

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.

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....

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