Console app needs Windows User to be Administrator

[brent_griffith]

hello,

I am having a strange problem with an executable that fails with exit status 128 on selected windows boxes. Application is Fortran Console Ap. I am wondering if there are compiler settings in CVF that can affect the permissions required to run a program. I am running the executable in the CONDOR distributed computing environment where execute machines have a special user. Never seen this problem before, but it goes away if I make the CONDOR user a member of administrator group. Exit status 128 is said to be missing DLLs but the user permission thing is the only thing I have found to solver the problem. (It is too insecure to leave CONDOR users as Administrators)

[Steven_L_Intel1]

There's no setting. What operation is failing?

Steve

[brent_griffith]

Well it is difficult to tell what exactly is failing. The executable doesn't seem to start at all. Nothing is sent to stdour or stderr. I have tried a different, simpler fortran program and don't get the problem. The problem program is pretty large (compiles at 9.5Megs) and comprised of over a hundred modules. It reads and writes text files in only its own directory. I need to figure out what dlls or resources this program is attempting to use that may be restricted by user permissions...

[Jugoslav_Dujic]

Can you start the debugger on it? You don't even have to have the source -- if you open "yourapp.exe" in VS and hit F5, you should get "Loaded xxxxx.dll, no symbolic information found" messages -- that may give you a clue.

Depends.exe (Dependency Walker) from CVF program group gives you the dependency tree for given module.

Jugoslav

[brent_griffith]

Thanks,

I have been going down the missing DLL road for some time and nothing has solved the problem. I have been doing some testing and running FileMon (www.sysinternals.com) and it looks like the console application is trying to access c:winntwin.ini which can't unless it has admin rights. There is nothing in my fortran code that directly works with win.ini. So I think it must be something that the compiler is making it do... Any ideas?

Brent

[Steven_L_Intel1]

It's not the compiler - the compiler hasn't a clue what win.ini is. Something to do with the Windows "console" application type, I would guess. I have never heard of this symptom before.

Can you open a command window and run the program from it?

Steve