Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!van-bc!sl
From: sl@van-bc.wimsey.bc.ca (Stuart Lynne)
Newsgroups: comp.unix.xenix.sco
Subject: Re: Using COM3 under SCO XENIX
Message-ID: <2078@van-bc.wimsey.bc.ca>
Date: 23 Sep 90 08:18:14 GMT
References: <3446@dftsrv.gsfc.nasa.gov> <402@tygra.UUCP> <1947@sixhub.UUCP>
Organization: USENET Public Access, Vancouver, B.C., Canada
Lines: 17

In article <1947@sixhub.UUCP> davidsen@sixhub.UUCP (bill davidsen) writes:
>In article <402@tygra.UUCP> cat@tygra.UUCP (CAT-TALK Maint. Account) writes:
>
>| XENIX wont be able to see the ports if they're not listed in the CMOS
>| config. 
>
>  Hogwash. Xenix looks in the config files in /usr/sys for this,
>sio-something and master as I recall.

Machine specific. The TI 1300 for example has a built in serial and parellel
ports, which can be turned on or off via CMOS configuration utility. The
idea being that if you don't want or need them, but want the interrupt, or
the io address you can disable them. 

-- 
Stuart Lynne	Unifax Communications Inc.
		...!van-bc!sl 604-937-7532(voice)     	sl@wimsey.bc.ca