jsmith@earth.tmc.edu (Jeff Smith) (03/16/90)
I have been trying for a while now to get dnet running on our Sun. I'm reasonably sure that I have cleared an 8-bit path, and run dnet -m0 from the Amiga. Then I run dnet -m0 on UNIX and an fterm opens up. Since fterm opens up, I *MUST* have all the necessary assigns/setenv's pointing to the correct places, right? But as soon as I hit the return key, fterm goes catatonic. I can't even close it. I ran statdnet and found Bytes Packets Errors OUT: 4 7 n IN: 4 2 0 Garbage IN: 0 where n continues to increase (I stopped checking after it reached 4 or 5 hundred. I tried again, setting the -p switch from Amy for packet debugging. Once I initiate the <CR> in fterm, I get an endlessly repeating cycle of packets: . . . SEND 62 3 Bytes -- RECV 64 0 Bytes \ this pattern repeats seemingly forever. SEND 71 12 Bytes / RECV ff 0 Bytes -- SEND 62 3 Bytes RECV 64 0 Bytes SEND 71 12 Bytes RECV ff 0 Bytes SEND 62 3 Bytes RECV 64 0 Bytes SEND 71 12 Bytes RECV ff 0 Bytes . . . I know very little about Matt's sliding window protocol and the intimacies of the packets. Does anybody have any idea why I can't run? I should mention (as I've seen recent posting related to this) that I am trying to run on a Telebit modem. Recent net traffic indicates that I should be expecting a low throughput, but frankly I'd be happy with 2400 when that is compared with my current zero. I'd also like to know if there are any man pages for the dnet stuff. I find the docs that came with my stuff sadly lacking in concise info about command line options etc. Mine don't even mention the -m switch, but I picked that up from net chatter. I would love to get dnet up and running (limping?) so that I can work effectively from home. Any and all help would be appreciated. --------- Smithicus Alias Research, Inc., Toronto ON Canada jsmith%alias@csri.utoronto.ca "I gave you 7 children woman, now you say you want to give 'em back!" -BB King