Prev: range and precision of srk call
Next: Good book on FORTRAN
From: Terence on 9 Apr 2008 05:29
I just tried running a Fortran program compiled (CFV6.6.1) and tested
in september 2004 under Windows.

It calls on about 60 daughter programs, among them MSDOS editors
(which are called and still work with the associated files passed) and
many for-MSDOS compiled (MSv3.31) F77 programs (which in this mode now
do nothing until ctl-C is struck, when they abort; else just sit there
with a pretty screen and no action in response to other keys.

All these called programs still work in DOS, and worked when called
under the parent Windows program in 2004 (because of thorough testing)
and probably 2005 or even 2006 because I suspect I used this mode
myself in those years, and because they were "out there" and worked,
without complaints being sent in.

Now I checked on my own Windows NT 2000 Professional and this was the
result.

Anbody got any quick ideas before I start boring you with details?

My own guess is I have to relink the daughter programs with more stack
(I found this to be necessary with even DIRECT execution of some
existing older programs - suddenly.
From: e p chandler on 9 Apr 2008 10:51
On Apr 9, 5:29 am, Terence <tbwri...(a)cantv.net> wrote:
> I just tried running a Fortran program compiled (CFV6.6.1) and tested
> in september 2004 under Windows.
>
> It calls on about 60 daughter  programs, among them MSDOS editors
> (which are called and still work with the associated files passed) and
> many for-MSDOS compiled (MSv3.31) F77 programs (which in this mode now
> do nothing until ctl-C is struck, when they abort; else just sit there
> with a pretty screen and no action in response to other keys.
>
>  All these called programs still work in DOS, and worked when called
> under the parent Windows program in 2004 (because of thorough testing)
> and probably 2005 or even 2006 because I suspect I used this mode
> myself in those years, and because they were "out there" and worked,
> without complaints being sent in.
>
> Now I checked on my own Windows NT 2000 Professional and this was the
> result.
>
> Anbody got any quick ideas before I start boring you with details?
>
> My own guess is I have to relink the daughter programs with more stack
> (I found this to be necessary with even DIRECT execution of some
> existing older programs - suddenly.

Here are a few other wild guesses.

1. Your early DOS programs lose focus and are lost? Maybe START with
WAIT will help.

2. XP and up do strange things with I/O redirection of MS-DOS
programs.

3. a. XP chokes on DOS extenders where Win9x did not (like MS FPS
1.0).
b. Vista chokes on "OS/2 family apps" (like MSF 4.x and 5.x).
Setting Win9x compatibility for each EXE might help.

HTH

-- e

 | 
Pages: 1
Prev: range and precision of srk call
Next: Good book on FORTRAN