cassidy@attctc.Dallas.TX.US (Cassidy Lynar) (08/19/89)
I have recently purchased the ISC 386/ix 2.0.2 package, and I find that it is very much broke! Getty will not spawn a process to a modem, uugetty doesn't work either. I am pretty upset to think that close to $4000.00 was spent on an OS that I can not get to work properly. I was running uport's 2.4.0-U for a good while before I bought this 386. Dhrystone benchmarks are close to this NOREG: 6975 REGS: 6975 (running at 25MHz). The system consists of the following: 1 - 25 MHz Computer Research 386 (my company's) 8 - Meg of RAM (zero wait states) 1 - TB2000+ Modem 1 - Hayes 2400b Internal 1 - Paradise 16 bit VGA w/512k RAM 1 - CTX 14" VGA 1 - Adaptec 2372b 16-Bit RLL controller 2 - Maxtor 1140's Ok, The package is the complete (everything they had) system, unlimited users, and no matter what I do, the modems will not answer the phone (once in a blue moon) it will, and then it's only at 1200 baud (another Trailblazer calling). When getty goes to respawn, it finds /dev/tty00 or /dev/tty01 (hayes line) with write permission only. Until I manually chmod the tty's, nothing will happen. Then (heres the bitch) the hayes ends up with '&C0' ?!? What gives? I called ISC many, many times, and they have faxed me many sheets of 'fixes' that contradict themselves on the same page, and sometimes in the same paragraph. If anyone has been able to getty a hayes 2400b and a trailblazer to both call and answer, then PLEASE send me mail describing how you did it in detail. I am very frustrated and have almost shipped the sh*t back to INTERACTIVE, but the only thing stopping me is the excellent SDS package, and the X package. Sorry to flame, but it's hot here in Texas! (I miss the Northern Californian Coast) <grin> or is it <sob?> -cass ..attctc.dallas.tx.us!cassidy or ..attctc.dallas.tx.us!ydisac!cassidy "Once in a while we get shown the light, in the strangest of places if we look at it right!"
jackv@turnkey.gryphon.COM (Jack F. Vogel) (08/21/89)
In article <9046@attctc.Dallas.TX.US> cassidy@attctc.Dallas.TX.US (Cassidy Lynar) writes: >I have recently purchased the ISC 386/ix 2.0.2 package, and I find that it is >very much broke! Getty will not spawn a process to a modem, uugetty doesn't >work either. I am pretty upset to think that close to $4000.00 was spent on >an OS that I can not get to work properly. [ system description deleted ] >Ok, The package is the complete (everything they had) system, unlimited users, >and no matter what I do, the modems will not answer the phone (once in a blue >moon) it will, and then it's only at 1200 baud (another Trailblazer calling). I do not have a Telebit so I cannot be sure, and you do not describe the exact symptoms of your problem, but it sounds like the same thing I saw when first setting things up. What would happen was that every time the phone would ring the modem would cycle DTR and spawn a new getty. Is this what is happening?? At first I got around the problem by running my modems on the BellTech ICC card, but some kind soul (yes, Greg I saw your message, tested it, and it worked!!) told me to RTFM on asy(7) in the operating system guide. It turns out there is a modem control entry point into the asy driver. Of course, ISC does not create a special device file for the entry point, /dev/tty00 is major 3 minor 0. But let us not flame :-}, what you want is a /dev entry with major 3 minor 16 and then run your getty on that, or equivalently for tty01 make it major 3 minor 17. Although I am not using these ( the ICC driver works fine thank you :-}), I did test the COM1 device and low-and-behold :-} it answered the line just as you might expect!! Oh well, half the fun of running ISC is figuring out these little foibles :-}!?! -- Jack F. Vogel jackv@seas.ucla.edu AIX Technical Support - or - Locus Computing Corp. jackv@ifs.umich.edu