From: jlemon@netcom.com (Jonathan Lemon)
Newsgroups: comp.sys.next.bugs
Subject: Re: Known Mux (Serial) Driver Bugs and Problems
Message-ID: <jlemonCJwxpn.Dsp@netcom.com>
Date: 20 Jan 94 05:24:58 GMT
References: <CJv5uH.9HL@ve6mgs.ampr.ab.ca>
Organization: Netcom - Online Communication Services (408 241-9760 guest)
In article <CJv5uH.9HL@ve6mgs.ampr.ab.ca> mark@ve6mgs.ampr.ab.ca (Mark Gregory Salyzyn) writes:
>The following problems have come to my attention for the updated Serial Driver:
> 1) The serial Bus Mouse Configuration program will not recognise
> that the Mux driver can replace the SerialPorts driver and will
> complain (or crash Configure.app). Since I do not have a serial
> mouse on my system, I will need to regroup to figure out how to
> test this and a workaround. (Suggestions, reduce the number of
> supported ports in SerialPorts to 1, and use the "Path #"
> Configuration parameters in the Instance?.table files under Mux to
> start placing ports at ttyb and so on. This requires *good*
> understanding of the Instance?.tables and editing, not for the
> weak or the Weary!). If anyone has dealt with this issue, please
> send me a note of their configuration as some people are interested.
I'm currently running NS/I 3.2 with a serial mouse, driven by the
SerialMouse + SerialPorts driver, and Mux on my modem line. Here's how:
1) copy the COM1,COM2 configuration files into Mux's top-level
default configuration directory before building Mux.
2) build and install Mux
3) change the Default.table for the SerialPorts driver so that the
'Port Count' is '1' instead of '2'. (for good measure, I also
edited down the 'IRQ Levels' to only show the IRQ that my
mouse actually uses, although I don't think this is necessary)
< Mark Salyzyn Note: Leave BOTH port addresses in place in the >
< Instance0.table, set the second to a non-existing port on the>
< machine (I use 0x100-0x107) >
3) Remove the 'Path:' lines from the SerialPorts Default.table for
the port your mouse is not on. (IE: assuming your mouse is on
/dev/ttya, remove the 'Path:' lines for /dev/ttyb). You may want
to paste these lines into Mux's Default.table, see step 5).
4) the 'I/O Ports' line in the Mux Default.table is missing a
trailing semicolon. Add it. There are also two 'Instance'
lines. Remove one for good measure.
< Long since Fixed ... >
5) By default, Mux will start assigning lines from /dev/ttya. If,
like me, your mouse is on that particular line, you will have to
tell it to start with /dev/ttyb. The easiest way to do this is
simply to copy all the 'Path' lines for /dev/ttyb from the
SerialPorts Default.table, and then change them to reflect the
correct PortCount. (IE: change "Path 1 ..." into "Path 0 ...")
6) fire up Configure, and add in the Mux driver. You should see
the SerialPorts driver only taking up one IRQ level.
7) reboot, and keep your fingers crossed. If you've hosed your
mouse, you can reboot with "config=Default", to hopefully get
a workable configuration back.
When I originally did this, I thought it would be possible to have Mux
replace the SerialPorts driver, since they are both of 'Family = "Serial"'.
No such luck. Configure complained that the SerialMouse driver needed
SerialPorts. And it didn't work when I tried it anyway.
Examining the Default.table, for the SerialMouse driver, I found the
"Driver Dependencies" line and set it to "Mux". No go again. Configure
still complains that it needs SerialPorts. (and it still doesn't work)
Hmm. A quick check with check with 'strings' shows that the SerialMouse
dependency on SerialPorts is hard-coded into Configure, of all places.
(now, who's bright idea was this?)
IMHO, more time should be spent getting Configure to work properly in cases
like this, and less time putting in ridiculous 'Infomation' easter eggs into
the app. H*ll, enough time may be saved to write a _REAL_ 1742 driver!
I'm mostly happy with the driver at this point; I can at least drive the
serial port (16550AFN) reliably at 19.2K on a V.32b/V.42b link without
losing data.
I haven't been able to get a squeak out of my terminal server when I set the
line speed at 57600, although my computer will happily talk to my ZyXEL.
Yesterday I didn't have any problems at 38400, but today I get the same
results as 38400, so there's still some room for improvement.
< Hopefully this is a moot point now on V1.4 ...>
The Default.tables from my system for SerialPorts and Mux are included below.
I have a serial mouse at 0x3F8, IRQ 4, /dev/ttya, and a modem at 0x2F8, IRQ 3,
/dev/ttyb.
Hope this helps someone!
--
Jonathan
Path: adec23!ersys!pagesat.net!decwrl!decwrl!spool.mu.edu!howland.reston.ans.net!EU.net!Germany.EU.net!ping.de!gurke!tini From: tini@gurke.ping.de (Constantin) Newsgroups: comp.sys.next.software Subject: Re: SLIP and hardware configs Message-ID: <Cy5Dvp.DK@gurke.ping.de> Date: Sun, 23 Oct 1994 22:45:24 GMT Organization: Legalize THC Lines: 22 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Mime-Version: 1.0 >Can you use the MUX driver if you have a serial mouse? Yes. The problem is that Config.app needs the old serial driver as well!! That means that you have to change the Default.table of SerialPorts.config, because SerialPorts always wants TWO serial ports. Do the following thing: 1) MAKE A SAVETY COPY of the old SerialPorts.config 2) Change Default.table to the version supplied with the Mux packet. 3) Remove instance0.table 4) Start Config.app and add the SerialPort again! (Now it should be only ONE serial port) Greetings, Constantin -- <--------------------------------------------------------------> | Constantin Szallies ||| tini@gurke.ping.de | | Emil Figge 7 44227 Dortmund (o o) Tel: 0231/7519681 | <------------------------------oOo--(_)--oOo------------------->
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.