Member Avatar for DAMN FLUSH

i have a 1 ghz AMD duron computer with win xp and i´m trying to run this program named FLUSH that was developed in fortran 77 language, i execute the program in the DOS prompt of xp and it gives me the following error:
Abnormal program termination:stack fault
CS=EIP=000FH=000013EFh

i don´t have a clue of what this means

the program runs well in win 3.x and win 95 but i need it to run in xp
maybe the problem is because of the and files but i´m not sure.

i really appreciate if someone could help me.

  • 3 Contributors
  • 3 Replies
  • 431 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by DAMN FLUSH

Dani AI

Generated

Quick expert note: that "Abnormal program termination: stack fault" with a CS/EIP dump is a DOS‑era crash signature — it usually means the program executed an instruction or accessed memory in a way the NT virtual DOS environment (NTVDM) doesn’t allow. Windows 3.x/95 gave a much closer-to-DOS environment; XP (NT family) does not fully emulate all DOS behaviors or legacy DOS extenders, so a program that ran on 9x can still fail on XP.

Practical, low‑effort ways to get FLUSH running without porting the source:

  • Use DOSBox (recommended). It emulates a real DOS environment and often runs old FORTRAN/DOS executables cleanly. Typical session:

    mount c c:\path\to\flush
c:
flush.exe

    If timing or graphics are odd, tweak cycles (Ctrl+F11/Ctrl+F12) or DOSBox settings.

  • Use a virtual machine with Windows 95/98 (VirtualBox/VMware/Virtual PC). This gives the highest compatibility for DOS/Win9x programs and avoids rewriting code.

Why compatibility mode or recompiling may not help (and what to try next): was right that the Compatibility tab helps Win32/Win16 apps, but it doesn’t fix pure DOS/real‑mode issues. correctly noted recompiling can work, but as experienced, Fortran 77 sources often use fixed‑format, nonstandard extensions, or expect 16‑bit memory models — modern compilers require code changes. If recompiling is attempted, try a maintained compiler (gfortran or a current commercial Fortran), keep sources in fixed‑format (.f), address one compiler error at a time, and link statically or bundle the required runtime.

Quick troubleshooting checklist (without repeating edits already tried): verify whether the .exe is a DOS MZ binary vs a Win32 PE (MZ header / PE pointer), avoid loading TSRs or device drivers via AUTOEXEC.NT/CONFIG.NT, and remember that 64‑bit Windows has no NTVDM — use DOSBox/VM there. The fastest reliable route in most cases is DOSBox or a Win9x VM.

Recommended Answers

All 3 Replies

Member Avatar for qt 3.14159

Rather than running it from the command prompt, you might try right clicking on the file choosing the compatability tab and running it in compatability with win 95. Then just double click the file to run it.

It's worth a shot anyway, eh?

Member Avatar for DMR

You may not be able to run that particular program under XP without recompiling with a newer FORTRAN compiler; "DOS" under XP is not the same as DOS in win 3.x/9.x, and this can break programs compiled with the FORTRAN 77 compiler.

Member Avatar for DAMN FLUSH

i already tried to compile the program with different compilers. The lahey/fujitsu 90-95, the compaq visual fortran and even the g77 fortran compiler from linux and the ones that compile it throw lots of errors and i´m not familiar at all with the fortran language i gess i`ll have to run the program under win 95

thanks anyway

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.