This contribution consistes of two files: this brief text file and a
short REXX procedure.  The procedure (which I assign to an entry on the
Launch PAd), starts up the File-Cabinet Server and then starts OS2-CIM.

I use this to avoid the "cannot-connect-to-file-cabinet" problem which
remains a source of trouble to many.

Installation:
1)    Unzip the container file and place OS2-CIMA.CMD in the ?:\CSERVE\OS2-CIM 
      directory.  If you set up a remote reference (such as placing OS2-CIM on
      the launch pad) you will want to make ?:\CSERVE\OS2-CIM the working
      directory on the first page of Settings.
2)    Change the second line of OS2-CIMA.CMD to point to the drive on which
      you have installed OS2-CIM.  This is currently coded as "?", which is
      not likely to work.

The procedure is fairly simple: start the File Cabinet Server, wait one
second for it to get established, and then start OS2-CIM.  The only time
I had a problem using this procedure was when I had a full-screen Windows
session active but minimized.  That one time, it took OS2-CIM so long 
to crank up that FCSERVER gave up on waiting for it.

Please use this procedure at your own risk.  It works for me; your mileage
may vary.

Rick Humburg
74653,1725