Rick beat me to the punch.
This is far and away the most frequent question I get from my page. So much so that the very first paragraph of the Introduction has a big 'NOTA BENE' in the fond, though futile, hope that people will read the solutions given there.
I have to answer this question so frequently that I wrote a form letter with which to reply...
This is a form letter reply to your email because I'm really, really tired of continually having to answer the same question again and again.
The problem you're having is not due to a fault in my software. Rather, it's a result of the fact that you don't understand how your operating system works.
If you had read the very first paragraph in the Introduction section at the top of my webpage, you would have seen that it says:
*** NOTA BENE ***: If you're too lazy to read this introduction, at least read the last four paragraphs so I don't have to waste my time answering questions already answered here.
And the last four paragraphs say:
A number of DOS-challenged users of my programs have written to complain that when the program terminates, Windoze, in another one of its mis-guided attempts to think for the user, closes the window before they can inspect the answers generated by the program. Dave Wood has spent some time working out how to keep Micro$oft's abortion from trying to outthink the user. He writes:
In Explorer, right-click on the .exe program name. Select "Properties". Select the "Program" tab. At the bottom of this dialog is a single check-box "Close on exit". Un-check this box. At the bottom of the dialog click on "Apply," then "OK".
His remarks are specific to XP but I expect they are applicable to other flavors of MS so-called operating systems.
Also, Anthony Nagy writes, "I discovered that if you create and use a shortcut to run the program it will run under Windows and not terminate. I run Windows 2000. This may also work with your other programs and other versions of Windows."
??? I don't get an answer. ???
