Xref: utzoo comp.lang.c:11808 comp.sys.att:3965 comp.unix.questions:8735 comp.unix.wizards:10388 Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!killer!vector!rpp386!pigs!haugj From: haugj@pigs.UUCP (Joe Bob Willie) Newsgroups: comp.lang.c,comp.sys.att,comp.unix.questions,comp.unix.wizards Subject: Re: dial() function call Summary: so many requests - i'll post the latest version Real Soon Now(tm) Keywords: ?????? how ???? Message-ID: <210@pigs.UUCP> Date: 8 Aug 88 18:31:46 GMT References: <28@attibr.UUCP> Reply-To: haugj@pigs.UUCP (Joe Bob Willie) Organization: Big "D" Oil and Gas Lines: 28 In article <28@attibr.UUCP> vch@attibr.UUCP (Vincent C. Hatem) writes: >Has anyone out there ever got the dial(3C) function call to work??? > >I've got a 3B2/600 running SysVr3.1.1 here, which comes with HDB uucp. > >This crazy dial() call uses the old style uucp files, which I've re-created. >(Why be consistant???) > >It seems that no matter what I tell it, it returns an error code indicating >that the device I specify is unknown. But - it should be known... > >Can anyone please help???? i've received five or six requests for my modemcap thing, so i will be sharing it up and mailing it off to rich $alz. depending on his current backlog, plus the delay in my getting it out, it should show up in comp.sources.unix in the next few weeks. i'll also go ahead and make a copy available for anonymous uucp, so watch comp.sources.d for that announcement. alas, my code also uses the old style uucp files and has conditional compilation for old style lock files. an improvement since last release is the addition of primitive support for bi-directional modem lines. (it finds the getty, creates the lock, then nukes the getty off ;-) -- jfh@rpp386.uucp (The Beach Bum at The Big "D" Home for Wayward Hackers) "Never attribute to malice what is adequately explained by stupidity" -- Hanlon's Razor