Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!udel!burdvax!sdcrdcf!ism780c!bill
From: bill@ism780c.UUCP
Newsgroups: comp.unix.xenix
Subject: Re: The WHOLE scoop on UNIX 5.3 for the 80386
Message-ID: <7427@ism780c.UUCP>
Date: Thu, 1-Oct-87 21:17:44 EDT
Article-I.D.: ism780c.7427
Posted: Thu Oct  1 21:17:44 1987
Date-Received: Sat, 3-Oct-87 08:32:32 EDT
References: <411@devvax.JPL.NASA.GOV> <845@vsedev.VSE.COM> <7375@ism780c.UUCP> <1395@van-bc.UUCP>
Organization: Interactive Systems Corp., Santa Monica CA
Lines: 29
Keywords: UNIX,5.3,INTERACTIVE,386/ix,80386,386,VP/ix
Summary: Configuration problem


> All *I* want to know is who is responsible for the async and parallel port
> drivers in Bell Tech's release. I wouldn't want to flame the wrong party.
> 
> I've had the 386 box for a couple of weeks. Basically after much frustration
> I have given up on the parallel port driver. I must admit it *does*
> function. However printing one line every 5 to 10 seconds does not impress
> me *to* much.
> 
> And as bad as the lp driver is, it's at least consistent. The serial drivers
> on the other hand.... Can you say *schizophrenic*...  (let alone spell it).
> 

Your parallel printer port problem is a configuration problem. Check your
config file. The reason your printer runs so slowly is that you've configured
it to run off the clock interrupt, rather than the printer port interrupt.
So you are sending a character to the printer every clock tick.

The ICC driver was developed by BTI. You may also have a configuration
problem there as well. You might check with them to find out if you have
the latest version of the driver.

The base drivers (display, keyboard, parallel, async (COM1 & COM2), CMOS,
hd, and fd) were certified by AT&T and were also extensively tested by
Intel's beta sites (more than 60 beta customers). They work if configured
properly. Note that the standard V.3/386 release does not support more
than a single device per interrupt vector. If you have 2 devices on a single
interrupt vector, one of them will be serviced when interrupts occur and
the other will likely be serviced by clock ticks.