FoxPro 2.6 DOS exits silently under NT 4.0

[filibuster]

Hello,

I have a problem running FoxPro 2.6 DOS under Windows NT 4.0. The application is running fine, but all of a sudden the application window is closed.

No error messages are given from FoxPro or Window NT. I assume that FoxPro has created an invalid memory access or so and Windows NT just kicked Fox out.

The problem appears randomly, but mostly when large amounts of data are processed.

Thanks
Holger

 

[rgbean]

Holger,
I seem to remeber a MS Knowledge Base article about something like this, but I can't find it right now. (As I recall, it required a registry fix that affected all DOS sessions.) Is this really FPD 2.6, or 2.6a? Is the application using the Extended or Expanded memory version? Is it an .APP, compact .EXE or standalone .EXE? Are you using a CONFIG.FP? Do you set MEMLIMIT? What are the values? Do you fire up the application with a .BAT file, a .PIF or .LNK?

While I don't have any specific answers, perhaps with the answers to the above, someone may recognize a potential problem.

Rick

 

[filibuster]

Hi,

here is the environment:
(1) FoxPro 2.6a
(2) Don't know about Extended/Expaned version - how can I find out ?
(3) APP file (ca. 6 MB)
(4) config.fp is used
(5) MemLimit = 80, 4096, 8192
(6) batch file (Foxr -t -c\mq\config.fp myApp.app)

Rgds
Holger

 

[rgbean]

Holger,
Unless you display the version used somewhere in the program you may not be able to tell - that's because Foxr.exe is supposed to choose the "right" version dependending on the environment (memory types available and the amounts) and the runtime files available. Unfortunately this was written assuming a "pure" DOS environment and Win NT 4.0 only emulates DOS. Check for Foxd2600.esl, Foxd2600.eso (the Conventional/Expanded memory runtimes) or Foxdx260.esl (the Extended memory runtime).

You can try forcing FOXR.EXE to use one or the other, using the following flags:
+X Load 32-bit Extended version
-X Don't load 32-bit Extended version
-E Don't use Expanded memory (this uses only Conventional memory)

Consider creating a new shortcut (a .LNK file), that just has &quot;<path1>Foxr -t -c<path2>\mq\config.fp myApp.app&quot;. This way, once created, you'll be able to right-click and choose Properties. Here on the Memory tab, make sure they are all set to Auto (not the default).

Does the application use any .PLB's or .BIN routines that directly access the hardware? This of course is a major no-no under NT, and could cause instant termination.

Have you checked the NT System and/or Application Event logs?

Other than finding the previously mentioned KB article, I can't think of anything else to try.

Rick