CompuServe Messages

I have considered that approach, and have avoided it for the following reasons: 1) Existing BBS software would not be able to run with this arrangement. Custom message/file bases (and probably custom file transfer programs) will have to be written. 2) I'd have to come up with my own algolrythym for full-duplex packet-switching, including windowing (send-ahead) and verification of proper reception by the other end. This is what DNet does so well; I do not want to exert such great effort to re-invent the wheel. Also, it should be understood that DNet in itself is not a network filesystem (which is the impression I think you have, from what I can see from your last message), but simply a packet-switching protocol that can provide many virtual I/O connections over a single hardware I/O connection between two machines. In addition to this, many people use the 'NET' filesystem for DNet written by the Software Distillery to share devices between CPUs; I am, however, only interested in the DNet portion to provide 'packet dispatching' in just the way you described. I have obtained a version of the DNet include library from some Software Distillery source code that compiles relatively easily, so I can access DNet. But now I've got to 'bridge the gap' between DNet and existing BBS software, or something, for even if I were to write my own interactive message base system, programming in 'C' is my idea of hell on earth, and would rather stick to languages like ARexx, Modula, or even BASIC.