What I mean by "does not work" is that ''output_val'' is empty (zero by zero). That means that the system ('test.exe') is not working. The same code was working when the fortran code was compiled on a 32 bit machine and its exe is called on 32 bit matlab installed on that machine.
"Steven_Lord" <email@example.com> wrote in message <firstname.lastname@example.org>... > > > "E U" <email@example.com> wrote in message > news:firstname.lastname@example.org... > > I have similar problem. I have a simple fortran code (test.exe) which > > takes exponential of a number. I want to run this code several times from > > matlab as follows: open an input.dat file, write a number into it, call > > test.exe and then write the output to output.dat file. > > > > The associated matlab code is as follows: > > *snip* > > > When I compile the fortran code on a 32 bit machine and then run the above > > matlab code on 32 bit matlab installed on 32 bit machine it works. > > However, if I compile the fortran code on a 64 bit machine and then run > > the above matlab code on 64 bit matlab installed on 64 bit machine it does > > not work! What can be the reason? > > Define "does not work" -- does it throw an error? Does it issue a warning? > Does it give you a different answer than you expect? Does it crash MATLAB or > your machine? > > Post that information to the group and someone may be able to offer a > suggestion; determining the cause of this problem may require posting a > SMALL section of your Fortran code as well, but let's start with the answer > to the question above. > > -- > Steve Lord > email@example.com > To contact Technical Support use the Contact Us link on > http://www.mathworks.com