CompuServe Messages

Dale, Thanks for your insightful reply. I feel I am making progress, as I slowly pick up clues and pointers. Still, I am primarily concerned with a purely Amiga<->Amiga connection, and for almost none of the reasons usually associated with DNet (NET: filesystems, remote CLIs, Unix). Strangely, using DNet for a BBS would benefit far more people than its current uses would. I noticed the support library you uploaded seperately; This should be instrumental in revising and recompiling existing DNet programs via SAS/C. I have actually already compiled my own little DNet server using a mutant dnetlib that I found with the Software Distillery's NETKEYS package; This function library requires no other special files to compile. RE: getting 2.20 protocol to start.. I had found one of the 'incomplete' 2.20 archives on Smorgasboard BBS and set it up on my two Amigas (the same systems I use to test my current DNet project) by dropping the new binaries into the existing setup, and it seems to behave as 2.13 did: Select 'Start Protocol' on one end, and the other end displays a few garbage characters and does nothing. I am using a Radio Shack null modem adaptor and Dataspec full 25-pin serial cable for the connection.. I've tried every relevant parameter in starting DNet I could find including 7-wire, Xon/Xoff, 8-bit path, carrier-detect disable, lowering baud-rates, ad infinitum. I haven't tried the archive you uploaded yet, but will do so shortly. As for experimenting with the dnet.device(s), I have discovered that terminals are much less demanding of the serial.device than BBSs are; The BBS software I presently run, Citadel, opens/closes the device no less than 3 times in rapid succession when it is first executed. Other BBSs I'm trying either don't work at all even with serial.device or won't allow the device/unit# to be changed. I am open to suggestions on good BBS software (esp. w/ a strong/nice message base)! Regards, Chris (who also eagerly awaits his v.32bis modem <g>) [ MORE ]