chris@sloth.bc.ca (Chris Brougham) (06/29/91)
Hello Everyone, I have a few questions concerning modems and the old and new init.c. First of all a couple of days ago I posted a request for information on configuring my modemcap file to allow a high speed modem to connect to my news host. I didn't receive any replies so I'm assumimg either a)it was a stupid question and there should be no problem or b)it can't be done! I'm sure someone can give me an informed answer so I'll post the question again: What changes do I need to make to my modemcap file to allow a T1000 telebit modem to work? Can someone who has done this please post a sample modemcap file. Also, has anyone used a V. 32 or V. 32bis modem with MINIX? How did this work out. And finally, will I need to use a 16550 uart to make these modems work. I noticed in rs232.c there were no provision for this chip, is there an update or can I get *by* woith the older uart chip? BTW I'm using an XT. Concerning init.c and modem.c. I've tried partially successfully to spawn a getty of /dev/tty1 using both the MINIX 1.5 init.c and the new init.c that was posted here in December, 1990. There are a couple of really starnge things that happen though whenever I spawn a getty off /dev/tty1. The first thing that has me perplexed is an electrical noise that I can hear coming from what I guess is my modem speaker (no I'm not crazy :-) ). For the record the modem is a Supra 2400 internal for the PC. The second, and probably more important question, concerns my inability to *consistently* switch the getty states between dialin and dialout. Sometimes it works and sometimes it doesn't. This is the case with both the new and old init.c and modem.c. Should I make sure that a ps alx indicates that a getty process is being spawned before issuing a modem -i or modem -o command? When I do this a login gets spawned (as if the modem ATZ command was trying to login). Please give me any and all advice on these perplexing affairs. For the record here is my inittab and gettydefs files: # # The MINIX 1.5 Init File # # This file contains the actions that INIT nust run for # each possible run-level. Currently, only one level (0) # has been implemented, and it is ignored. # The file has the following layout: # # id:runlevel:mode:command:arg(s)\n # # Here SPAWN means "split off another process" # EXEC means "execute process without fork" # RESPAWN means "do this over and over" # # The first entry should be one with an ID equal to "id"; # INIT uses its runlevel as the default system run-level. # id:2:exec:/bin/sync: dt:S123456:exec:/usr/bin/date: -q rc:S123456:exec:/bin/sh:/etc/rc ud:123456:spawn:/etc/update: #l1:123456:exec:/usr/lib/lpd/lpsched:-p default #l2:123456:exec:/usr/lib/lpd/lpsched:-p matrix #cr:123456:exec:/usr/bin/cron: c1:S123456:respawn:/etc/getty:/dev/tty0 -k CONS1 t1:S123456:respawn:/etc/uugetty:/dev/tty1 -t 2400 #c2:S123456:respawn:/etc/getty:/dev/tty2 -k CONS2 #c3:S123456:respawn:/etc/getty:/dev/tty3 -k CONS3 #t1:123456:respawn:/etc/uugetty:/dev/tty5 -t MODEM #t2:23456:respawn:/etc/uugetty:/dev/tty6 -t 19200 sh:0:exec:/bin/sh: # # MINIX version 1.5 /etc/gettydefs # # Here the entries for the Virtual Consoles. CONS1#SANE B115200 DCD#SANE B115200 DCD#con login: #CONS1 # Finally, the entries for the modem lines. 2400#SANE B2400#SANE B2400#sloth login: #M1200 --- chris brougham chris@sloth.bc.ca