LE>>  * An OS/2 HDD device driver
MB> somewhat complicated, since different controllers are supported by their 
MB> appropriate Adapter Device Driver (ADD) and all hard disk drives are 
Sorry, yes, I meant the ADD. Long week.

MB> (OS2DASD.DMD).  An example of an ADD is the IBM1S506.ADD source provided 
Yes, but I can't afford DevCon and I can't persuade my employer to
subscribe to it, which is why I was hoping for something available freely.

#define PET_GRIPE
OS/2 development tools are just too expensive. Microslut give away bundles
of CD-ROMs at the drop of a phone call. There are lots of applications
which simply can't be developed without the DDK. IBM needs a cheap and
simple developer level, which just entitles the recipient to the occasional
CD, and no incident support.
#undef PET_GRIPE

LE>>  * An OS/2 printer device driver (laser)
LE>>  * An OS/2 IFS
MB> Unfortunately, I don't have any good IFS source I can disclose to you other 
MB> than a very simple skeleton:
That's enough.

MB> Perhaps if you explained what you are trying to do, I could help you.
Okay, well there are two projects in those three files. The printer driver
source is strictly for myself. I want to write some decent drivers for a
couple of printers I have here. It took me about two days to write Win-OS/2
drivers (based on sample source in the 3.1 DDK)... how much more complex
can PM be ?

The IFS and the ADD are for something quite different. There is a product
which I co-develop which secures a workstation by encrypting the root dir
and FAT and it has a dynamic decryptor module which hooks int 13h at boot
(it's in the boot sector). I want to be able to install OS/2 over the top
of this. The IFS part is because I would also like to implement some of the
file-level protection provided by the product.

-- Lewin A.R.W. Edwards [Team OS/2]  Tel 0419320415 * 0412809805 * 0414927056
@EOT:

--- MsgedSQ/2 3.35