Running Delphi 1.x on OS/2 Warp
3/1/96

Hi there.  Let me start with the disclaimer:  I am not associated with 
either Borland or IBM.  I just use their products.

I began using Delphi under Warp (for Windows) when it came out and did
not have any significant problems.  In preparation for a new project, 
however, I upgraded my environment to Warp Connect (no fix packs) and 
the updated Delphi. (My original setup used the shipping Delphi CD, and 
then later added Delphi patch 1.  My updated Delphi is a CD containing 
DELPHI.EXE dated 8-24-95 that I mail-ordered from Borland.) With this new 
setup my PC would lock up every time I hit the Delphi IDE "GO" button on 
the tool bar.

It took me several days to figure out the problem, so I am posting it
here in the hope that it will save you some time. According to Borland's
TI2816, the Delphi IDE tries to intercept system calls in order to provide
"Integrated Debugging" when you run a program from within Delphi.  In order
to run programs from within Delphi, I had to to disable the integrated
debugger by un-selecting Options|Enviroment|Integrated Debugging.
This works for me; obviously, your mileage may vary.

You can identify this problem by compiling a Delphi program and running it
from the File Manager instead of from Delphi.  If the app runs from the
File Manager but not from inside Delphi, you probably need this fix.

Above all, please note that this problem stems from a Delphi feature. The
fact that it can make Warp lock up should in no way reflect badly
on OS/2.  OS/2 is definitely the best platform for developing database
front ends with Delphi.  The Delphi designers apparently took advantage of 
some weedy unauthorized features of Windows 3.x and didn't notice the side 
effects until after releasing the update CD.  

-David Peterson
CIS 75030,1300