DG>    They had written a program that merely allocates and deallocates
DG>    a section of memory as a test for me to use. Again, this one
DG>    failed with the same error message the previous version did. Now
DG>    one thing that does concern me as being consistant, is that it
DG>    reports (025) unable to find loader besides the SYS3175 error.

025 is a "failure to initialize" error according to my BP docs, not sure
what that means.

DG>    This seems to me, to point to the loader provided (ie:RTM.EXE
DG>    and DPMI16BI.OVL) rather than their coding implementation.
DG>    However without some conclusive proof, ie: an experianced OS/2
DG>    programmer that is familiar with the Borland products and coding
DG>    for OS/2 or under OS/2 that has run across a simular problem and
DG>    fix, then I will be unable to prove that it is OS/2 that is the
DG>    problem here.... and that I would like to disprove.

Ask the developers if they are using the 7.01 version of BP (or look at
the date on your RTM.EXE and check that the date is 3-09-93 7:01a).
There were problems with DPMI in 7.00 under OS/2, I remember that moving
the mouse in a Turbo Vision app would crash the app.  Here's some other
stuff from the BP 7.01 read.me file:

o CTRL-C IN OS/2 DOS BOX - If you are running under an OS/2 DOS
  box, you will not be able to use Control-C in your DOS
  protected-mode applications. Control-C will cause the DOS
  session to crash. This is a bug in OS/2's DOS protected-mode
  support that will be fixed in a future release.

o OS/2 AND DOS PROTECTED-MODE APPLICATIONS - If you run a DOS
  protected-mode application under OS/2 that starts another DOS
  protected-mode application, both applications MUST use the
  same protected-mode loader.

  There is a known problem in OS/2 which will cause the DOS
  session to crash after the second application terminates if
  it uses a different loader. This will be fixed in a future
  release of OS/2's DOS protected-mode support.

  It is OK to start other DOS protected-mode applications that
  have been built with Borland Pascal with Objects (or BP.EXE
  itself) since they will be loaded by the Borland DOS
  protected-mode loader (RTM.EXE).

  Note that it is not safe to start Paradox 4.0 from a DOS
  protected-mode application written in Borland Pascal with
  Objects.

Also, I just compiled and ran the following program (compiled as a
protected mode DOS app), under OS/2 it runs up until it allocates 2045K
of RAM, then it gives a run time error 203 (heap overflow).  I then
tried it under DOS, it died at about the 1.7M mark.  I have 16M of RAM.

program test;

var p : pointer;
    a : word;
    tot : longint;
begin
writeln('Memory:',memavail);
tot:=0;
for a:=1 to 10000 do begin
     getmem(p,1024);
     tot:=tot+1024;
     writeln('a: ',a,' Memory:',memavail,' total: ',tot);
end;
end.

Your best bet is to get them to lend you a copy of TDX (the DPMI
debugger) and run it with the app under OS/2.

Rob.
___
 X SLMR 2.1a X Windws is ine for bckgroun comunicaions

--- Maximus/2 2.01wb