forums.silverfrost.com

With the version of FTN95 that I have (my subscription expired late last year, so it is is fairly recent), doing what you suggested does not generate an X86 application with PE = PE32 and 32Bit = 1.

With the version of FTN95 that I have (my subscription expired late last year, so it is is fairly recent), doing what you suggested does not generate an X86 application with PE = PE32 and 32Bit = 1.

I looked for where to make this change in Project Properties and Build Configuration in VS and could not find where I could set Windows Application to "no".

Andrew,

It was not clear to me from your reply whether there is a way to compile and produce the correct corflags tags for an x86 application or whether I have to, for now, use corflags to fix it. ...

I have two questions, Andrew.

1) I have been suing FTN95 with VS 2008. Will integration with 2010 come in the near future?

2) I need to run an exe process compiled with VS 2008/FTN95 from withi ...

I got it to run, but without doing corflags /32bit+ to tag it as a 32-bit process, I first get messages that the process stopped, etc., then, after closing all of these messages, I do get the results ...

I'm trying to start an exe process from within my C# application. This worked before in VS 2008 and 32-bit computer, but now with VS 2010 and 64-bit windows (7), it is now working. I tried to change ...

Found the four files that need to go with it. It would be awful nice if they could be bundled with the exe.

I've had a problem with a code working fine on the computer in which I have built the exe as .Net build but not on other computers.

Note however that this is not integrated with C#. I run it using ...

Ian,

Thanks for the post.

I get

68: Field width exceeds direct access record size

when using integer*4 or simply integer, although the number saved to the file is the standard int (32-bit ...

I create the binary file from C#:

BinaryWriter bw = new BinaryWriter(fs);

where fs is a file stream.

I write an integer to it:

bw.Write(securitycode2);

Then, within FTN95, I would like ...

Neither 'formatted' nor 'unformatted' work to read a binary file. If there is no other way to do it in FTN95, it would be an interesting feature to add. If there is a way, I would appreciate it if s ...

BUFFER is defined as character*150. The argument does not get read into buffer.

I will research the other option that was mentioned (GET_COMMAND_ARGUMENT).

I will try 'formatted'. From the manual, it doesn't seem to mean the same as binary. It seems to indicate that it is a text file. At any rate, will post here the results.

As to STATUS = 'UNKNOWN ...

This statement

CALL GETARG(1,BUFFER)

doesn't seem to be capturing the argument that I am passing to the executable. There are no errors or warnings. Should this not work with FTN95?

Thanks