cambler@polyslo.CalPoly.EDU (Chris Ambler) (07/09/89)
I am nearing completion of my BBS software package, and have recently had a bout of software rot with the medium-level routines for the modem communication. I am using x00.sys, a FOSSIL standard driver, and have created functions like char_ready; getchar; sendchar; sendstring; etc.. etc.. I am having the following problems: every so often, the receive buffer will stop being filled. char_ready reports that there is nothing in the buffer, even though the modem's receive light is flashing. I can output stuff to the modem, and it will act on it (eg. ATDT 555-1212), but it does not echo back. I have tried resetting the echo... this happens at random, and is DEATH to any kind of protocol transfer. every so often, the modem gets REAL confused, and a call to function 0x04 (init) will make the modem autoanswer (pick up phone and give carrier). hanging up by dripping dtr, waiting a second, and raising it again does not work. By every so often, I mean completely at random. I cannot determine what is doing this, although it HAS to be software, as many others use x00 with no problem. I would consider using another comm package, but I need buffers that can be accessed by different programmes (eg. by programme X, which then spawns or execs programme Y) without having to re-initialize (and drop carrier on the caller). If anyone has written a set of routines for talking to a FOSSIL driver (the kind that must be in OPUS, for example), I would GREATLY appreciate some assistance. I can be reached as: cambler@polyslo.calpoly.edu or voice at +1 805 546 0820 (home) Help!!! -- Christopher J. Ambler