Blinker 1302: DPMI function call nnnnh failed with error code nnh

I have a Clipper application that calls a batch file. The batch file
executes a WS_FTP Pro script which does FTP communications with a
remote host. This is a POS application and the call to the batch file
occurs with each sale. The user reports that they are getting a
"1302: DPMI function call nnnnh failed with error code nnh" error
after 'X' number of sales.... they estimate it to be around 25 or so.
I'm not sure if it's the same number each time or not.

The program is using the 'swpruncmd' command to execute the batch
file. I tried substituting a simple 'run' command and got the same
error message after what seemed to be the same number of attempts
(according to the user).

I'm assuming this is some sort of out of memory issue. Can anyone
provide any insight as to the best way to avoid this error?

Clipper version 5.3
Blinker version 7.0

Link script:

BLINKER EXECUTABLE CLIPPER F:127 E:1024
BLINKER EXTMEM BLOCK 512
BLINKER INCREMENTAL OFF
BLINKER EXECUTABLE EXTENDED 2048
BLINKER PROCEDURE DEPTH 75
BLINKER EXECUTABLE NODELETE
BLINKER LOWMEM RESERVE 64
SEARCH BLXCLP53
LIB NANFOR
LIB DBFNDX
LIB CPMI

Dear Scott Coffey:

On Aug 28, 1:58*pm, Scott Coffey <n...@noemail.com> wrote:
> I have a Clipper application that calls a
> batch file.
....
>*The user reports that they are getting a
> "1302: DPMI function call nnnnh failed
> with error code nnh" error

What are the numeric values?

> I'm assuming this is some sort of out of
> memory issue.

After each sale, what does WinDoze Task Manager say? (<Alt>+<Ctrl>
+<Del> and click on the Processes tab)

> Can anyone provide any insight as to
> the best way to avoid this error?

Convert to (x)Harbour or other current variant of the langauge. Find
out if each invocation of WS_FTP is staying in memory, or at least
leaves memory trapped.

David A. Smith

On Thu, 28 Aug 2008 16:58:02 -0400, Scott Coffey <none@noemail.com>
wrote:


Thanks for the reply David.

Weird situation. After doing some local testing I found that the
application would fail on the 20th call to the batch file. This
happened without fail and it was always exactly on the 20th call.

Without any real facts to back it up, I felt like the problem was the
repetitive calling of a batch file which then called a 32 bit program
(FTP Pro). I decided to move the functionality of the batch file to a
Clipper program and doing this appears to have solved the problem. I
was able to do over 50 iterations of executing FTP Pro without
failure. So, the problem appears to be solved.