Xref: utzoo comp.os.coherent:145 alt.bbs.waffle:1586 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!cs.utexas.edu!helios!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!slxsys!ibmpcug!mantis!mathew From: mathew@mantis.co.uk (mathew) Newsgroups: comp.os.coherent,alt.bbs.waffle Subject: Re: DOS waffle <-> Coherent uucico problems Message-ID: Date: 17 Apr 91 11:17:31 GMT References: Organization: Mantis Consultants, Cambridge. UK. Lines: 36 jep%baugo@nstar.rn.com (Joseph Perry) writes: > I used waffle uucico debug level 5 to try to isolate the problem. My > login proceeds normally. My system responds to 'login:' prompt, the > 'password:' prompt and the secondary 'password:' prompt from Coherent. > I get the waffle debug message 'Awaiting remote identification', I see > the 'Shere=mwcbbs' from Coherent, and get the waffle message 'Talking > to: mwcbbs'. I see that waffle responds with 'Sbbsuser', but then I > see Coherent respond with 'Coherent login: '. Eventually waffle ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is wrong. It looks as though Coherent uucico is falling over and the system is going back to the login prompt. > reports 'TIMEOUT, no ^P' and 'Timed out waiting for authorization'. Yup. After getting "Shere=mwcbbs" and responding with "Sbbsuser", the next thing should be protocol selection (Waffle sends Ug, Coherent sends Pg); presumably Waffle has got past there if it's reporting "Talking to: mwcbbs". The next thing is the first UUCP packet, which begins with DLE = ^P. No extra login: prompt. So it looks to me as though Coherent is broken. > (a) I have no problems with DOS waffle uucico when calling sites > running Unix (osu-cis & nstar, my newsfeed). > > (b) I'm told new Coherent uucico binaries were installed on the MWC > Coherent bbs about the beginning of April. I could successfully > connect to the MWC bbs with DOS waffle until up to about April 1. Supporting evidence for the "Coherent is broken" hypothesis. mathew -- If you're a John Foxx fan, please mail me!