Hi, Lee.

LL>      Depending on how you program there could still be some conversion
LL>necessary.  I have OPro, APro, and TTT and will have to do considerable
LL>modifications to be able to use them with BPOS2.  If you use any interrupt
LL>calls (Intr or MSDos) you will either have to change them or do extensive wo
LL>on the RTL to patch them into API calls.

I am not familar with OPRO, APRO, TTT OR RTL.  What are they?

Is BPOS2 what this German co. calls there product now?

LL>      So far I have managed to get some of TTT ported, still need to fix
LL>the mouse support, but haven't even started on APro/OPro.  I also haven't
LL>managed to compile any program that wasn't written with OS/2 in mind.

In the past year I have been hearing varying opinion on converting DOS
apps to this 16-bit OS/2 apps via Pascal.  Recently one person told me
he took a 30K plus lines of 16-bit DOS - Pascal and converted it to
32-bit C++ in a week for OS/2.

Astonding rate of conversion, IMHO.  His apps sounded like they were
compute bound apps vs text processing apps and maybe this accounts for
this rate of conversion.  They may have been text vs PM conversions.

I am not sure what the scope of the conversion might be (in
many-months) for beyond a re-compilation of a 16-bit Pascal to 32-bit
Pascal to add PM - but it deeply concerns me for my own app which is
over 64K Pascal lines (DOS) - and growing.

My apps is DB based and I wondering how to get the DB core of this
converted from 16-bit Pascal to 32-bit C++ for flat DB files and
relational DB file structures. I use an un-supported DB toolbox right
now.  Got any ideas?  Thanks.

Regards, -= Lou =-





--- WM v3.10/91-0154