mwills@x102a.harris-atd.com (wills ms 01309) (03/02/89)
Well, the foregoing dnet discussions almost had me convinced that my dnet woes were 7-bit related. Now I've isolated the problem to the software. At least its not in any of the modems I'm going through nor my preferences, nor my unix stty settings. I found an option in a new version I got from ucbvax about a week ago which does packet level debugging. There are several new options on the amiga dnet command: -8 use 8 bit transfer instead of 7 -d turn on debig mode -p turn on packet debugging. I get the initial FF, 05 sequence ok from the unix side which means SYNC, RESET_DNET (ref: unix/dnet/dnet.h in the distribution). Then the FTERM window pops up, and the amiga begins sending 00, 16 repeatedly. (I'm sure of the 00, but the 16 could be off a bit... this was all late last night.) Seconds later the FTERM window closes and a "can't connect" message appears in the CLI window (stderr), but the amiga dnet process (running in the background) continues to repeat the 00, 16 sequence. All this time, the unix dnet keeps repeating FF, 05. I'm wading through code to determine how close this is to expected handshaking. Can anyone help? Matt? anybody? I just got the latest off ucbvax and will try again tonight. I also noticed a remark about needing WB 1.3 serial.device for reliability. How critical is this? I'm using WB 1.2. -- - Scott Wills mwills@x102a.harris-atd.com uunet!x102a!mwills