MJ>                    I just downloaded a program called RAMFS (a RAM
 MJ> Drive IFS)  from os2bbs. The author says he compiled it with Borland
 MJ> C++ 3.1. It is  a 16 bit program. 

As it would be, with BC++DOS 3.1.  (-:

 MJ>                                    He says that you need the OS/2
 MJ> header files (and  presumable the libs) but it runs okay here.
 MJ> Presumably these would be  availabe in an old (16bit) version of the
 MJ> OS/2 Developers Toolkit.  He  also said it did link with TLINK.  No
 MJ> F?API or other things mentioned  here. 

That's because it is an installable filesystem driver.  IFSes don't need
the 16-bit OS/2 1.x API, not even the Family API subset of it, because they
*aren't user-level code*.  IFSes run in ring 0.

The headers for use in building an IFS are *not* part of the 16-bit OS/2
1.x Developers' Toolkit.  The Developers' Toolkit is for building
*applications*, not device or filesystem drivers.  To build device drivers,
one needs the Device Driver Kit (DDK).  To build installable filesystems
one needs the IFS Kit.  For building 16-bit OS/2 1.x *applications*,
however, all of the headers and import libraries for the system API are
included in the 1.x Developers' Toolkit.

 ¯ JdeBP ®

--- FleetStreet 1.19 NR