HDTenEightyP/NetNews huggingface dataset:
From: faith@bert.cs.unc.edu (Rik Faith)
Newsgroups: comp.os.linux
Subject: Re: compile kernel with gcc2.1
Keywords: linux, kernel , gcc2.1
Date: 12 Apr 92 13:36:14 GMT
Organization: University of North Carolina, Chapel Hill

One simple way to get tools/build.c to compile under gcc 2.1 is just to
edit the Makefile entry for build.c and add the following options to the
command line:

-I/usr/include -I/usr/src/linux/include

This makes gcc search the standard area first and then the kernel
area--only those things which are NOT in the normal area are fetched from
the kernel area.  This is the desired behaviour.  Using the other order
[which is the same as just using -I/usr/src/linux/include] will get the
kernel area to be searched first.

Something similar works fine for ps, also.
From: csn0314@ux.acs.umn.edu (tim)
Newsgroups: comp.os.linux
Subject: Re: kernel building problems
Date: 11 Apr 92 18:43:07 GMT
Article-I.D.: ux.1992Apr11.184307.4633
Organization: University of Minnesota

In article <1992Apr11.095724.8928@klaava.Helsinki.FI> torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds) writes:
>I'm still using 2.0 (and an older version at that) as I've been too busy
>to upgrade.  I doubt the HJ-patch is really needed - I read through it,
>and I'd guess 0.95c+ should compile pretty cleanly without it.  Anybody
>tried it? HJ's patch also assumes you have a 387, and you'll have to
>edit the makefile if you don't. 
>
i compiled 0.95c+ without any changes whatsoever using gcc 2.1. i was,
however, running a 95c kernel which had also been compiled with gcc
2.1 if that makes any difference. i haven't had any problems with
either linux or the compiler that seem to be related to that.

		tim
Xref: sparky comp.os.linux:227 alt.os.linux:2322
From: pgf@cayman.COM (Paul Fox)
Newsgroups: comp.os.linux,alt.os.linux
Subject: Re: vile 3.13 + gcc 2.1 anyone?
Date: 7 Apr 92 18:08:53 GMT
Followup-To: comp.os.linux
Organization: Cayman Systems Inc., Cambridge Ma

hlu@EECS.WSU.EDU (Hongjiu Lu -- Graduate Student) writes:
: How good is vile? 3.13 is out. Is anyone doing the porting? If you are not
: using gcc 2.1, please do.

I'm not doing anything linux-like right now -- but I recommend version 3.14
of vile, due to a (possible) file corruption bug in earlier versions of vile
(3.8 through 3.13).  (It may not show up in linux -- it depends on the
behaviour of realloc(), when asked to shorten a buffer).

paul fox, pgf@cayman.com
(vile is available from ftp.cayman.com, in pub/vile
-- 
		paul fox, pgf@cayman.com, (617)494-1999
		Cayman Systems, 26 Landsdowne St., Cambridge, MA 02139
Newsgroups: comp.os.linux
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: gdb(1) and ptrace(2)
Summary: gdb and ptrace
Organization: University of Colorado at Boulder
Date: Thu, 16 Apr 1992 11:19:55 GMT

1.  gdb does not work with the new .95c+ kernel.  
	Breakpoints end up in wierd places, etc.
	My guess is that internal structures changed
	enough from .95a to .95c to break things 
	(ie task_info, etc)....

	I don't still have my .95a sources to verify this,
	but if it isn't just me someone should recompile 
	gdb with the new kernel header files.  

	(I have 8M free on my disk, and I don't think 
	it's enough.)

2.  ptrace(2) does not support attach/unattach.  Does 
	any one care to rectify this? 

3.  GDB 4.5 has been released.  Is anyone building this?>


 	
Newsgroups: comp.os.linux
From: jplevyak@ncsa.uiuc.edu (John Plevyak)
Subject: Re: GCC2.1 (Wonderful !)
Originator: jplevyak@nvs.ncsa.uiuc.edu
Keywords: gcc, 2.1, 1.40
Organization: Nat'l Ctr for Supercomp App (NCSA) @ University of Illinois
Date: Thu, 16 Apr 1992 23:08:09 GMT


Concerning the various kinds of dynamic linking.

As I remember (from long ago) the Primos (the Prime operating system)
replaced all dynamic calls with calls to illegal addresses.  A table in
the image mapped the index of the illegal address to a filename/symbol
pair.  The filename was found or loaded and the address was patched.  This
has the advantage that you could dynamically replace the library without
relinking (the linker was in the OS).  This could be used on a 386 class
machine.

The disadvantages were:

	1) your program could suddenly fail if the new library (installed by
		someone else) had a bug
	2) you could not page directly off the executable
	3) your operating system was forced to intervene on  the first of
		every dynamic call... thus slowing startup time.

The advantages were:
	1) no need to relink shared library programs
	2) no need to link to libraries that this execution of the program
		did not require... finer grain linking could be a win here.

In general I don't think that you will find an obvious clean and simple winner
in a war of dynamic linking strategies if you ask more that a few people.

The simplest solution is usually the best though, and (not intending to start
a war here) while Primos did dynamic linking which was nice, the lack of
child processes, memory protection of 'shelled' programs, the segmented
architecture, system calls with a mix PL1/G and FORTRAN interfaces and assorted
other goodies made me wish for Unix with or without dynamic linking
(perhaps it has changed, this was 1986).

john (plevyak@uiuc.edu)
	
Newsgroups: comp.os.linux
From: nolan@helios.unl.edu (Michael Nolan)
Subject: 0.95c+ bootimage on tsx-11, will there be a rootimage?
Reply-To: nolan@helios.unl.edu
Organization: University of Nebraska - Lincoln
Date: 11 Apr 92 16:37:20 GMT

I see that a bootimage for 0.95c+ has arrived on tsx-11, will there be a
corresponding rootimage file?  (Linus's message said he would post a new
kernel, but didn't the patches since 0.95a also involve stuff in rootimage?)
---
Michael Nolan
nolan@helios.unl.edu

Newsgroups: comp.os.linux
From: pejn@cc.uow.edu.au (Paul Nulsen)
Subject: Re: HD timeout Errors (with .95a)
Keywords: IDE
Organization: University Of Wollongong
Date: Mon, 6 Apr 92 05:43:04 GMT

torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds) writes:

>In article <1992Apr3.030517.29450@afterlife.ncsc.mil> sdbaker@afterlife.ncsc.mil (Stewart Baker) writes:
>>Is there anyone else having problems with their disk in .95a?
>> [ description deleted ]

>I'm afraid there are people still having problems with the 0.95a
>harddisk drivers: the problems show up in "unexpected HD interrupt" and
>"HD timeout" messages.  These messages sometimes result in read-errors,
>it seems: general protection errors and sometimes even bad filesystems. 

I am one of these people. My system boots smoothly off the 0.95a images, but
after I have installed the binaries onto my hard disk most of them refuse to
function. There are a few corrupt sectors on the disk, but I don't think
there are enough to account for this problem (I have tried installing into
different partitions with the same results).

I might add, fsck detects no problems, and I can cat the files (though they
may be corrupt). The timeouts only occur when I try to run a binary.

My questions:

1. Are these problems basically due to bad hardware? In other words, should
I be demanding that the supplier fix the machine under warranty? I have had
some problems with the disk under DOS, but put them down to a few marginal
sectors.

2. How does linux deal with bad sectors? I am no Unix guru, but I don't see
any attempt to check for bad sectors during the installation.

>I'll make a new alpha-patch available tomorrow, which has some
>corrections to the harddisk driver: they aren't guaranteed to help you,
>but I hope the few persons experiencing these errors will try them out
>and report to me what happened.

While I am about it, can I join the appeal for these patches to be put into
a new set of images. Until I can get a functional system I have no hope of
really looking into the cause of my problems.

Thanks
Paul Nulsen
pejn@wampyr.cc.uow.edu.au
From: tsillanp@niksula.hut.fi (Timo Jaakko Sillanp{{)
Newsgroups: comp.os.linux
Subject: HELP! Problems with rootimage.
Date: 7 Apr 92 12:48:47 GMT
Distribution: comp
Organization: Helsinki University of Technology, Finland

I reported this problem two weeks ago but got no help.
So, here it is again.

I got rawrite.exe, bootimage and rootimage (0.95a) from nic.funet.fi.

I booted with bootimage diskette in drive A and Linux told 
me 'Loading....'.Then I selected one of the listed video modes.
Linux told me to insert rootimage diskette in drive A and press
ENTER. I inserted it and pressed enter. Diskette drive light
and motor went on for a second and that was all. Nothing else
happened.

I got a new copy from nic.funet.fi and tried again - still
didn't work. I have tried it on three different machines
but it doesn't work! Unfortunately all of those machines 
are 486/33 with AMI BIOS dated 05/05/91 or 06/06/91, so
I don't know whether it is a BIOS problem. My machine has
OPTI chipset, the other two have some other chipset.

Am I doing something totally wrong? 
I get rootimage.Z from nic.funet.fi (yes, binary mode is on),
uncompress it and write it to a floppy disk (1.44Mb) using
rawrite.exe. 
What should I do? 

Please at least tell me to shut up if I'm wrong. This uncertainty
is killing me.

TS.

tsillanp@niksula.hut.fi
From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson)
Newsgroups: comp.os.linux
Subject: Re: ESDI drives
Date: 16 Apr 92 14:11:56 GMT
Organization: Naval Medical Research & Development Command

In article <1992Apr16.032903.13931@ux1.cso.uiuc.edu> chojnows@osiris (Brian Chojnowski) writes:
>
>	mkfs was able to format the partition that I had prepared, but
>mount gave me an error 2. Does anyone know what this error pertains to?
>I am using an ESDI drive. Other than that, I have followed the installation
>guildlines. They were pretty simple, I prepared the 95a boot and root diskes
>on 1.2M floppies, set a partition with fdisk, that fdisk on linux was able
>to read, then did mkfs -c /dev/hda2 (was second partition). That worked
>fine, but got error 2 for mount /dev/hda2 /user.

This sounds like the mount point doesn't exist.  Did you "mkdir /user"
before you tried to mount?  By default, /user doesn't exist but /usr does.
You may also want to "mkdir /mnt" as a place to mount floppies onto.

Reagrds,

Mike.



-- 
LCDR Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30
AT&T 3B2/600G Sys V R 3.2.3     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
WIN/TCP for 3B2  R3.2           | MCI-Mail: 377-2719 or 0003772719@mcimail.com
From: dennisf@Miles.COM (Dennis Flaherty)
Newsgroups: comp.os.linux
Subject: Patch to preset the SVGA mode
Date: 9 Apr 92 16:49:27 GMT
Organization: Miles, Inc.  Diagnostics Divis.


If you are tired of hitting RETURN and selecting the
same SVGA mode every time you boot Linux, apply this
patch and rebuild the kernel.  It allows you to preset
the mode in the Makefile, so that the setup program
proceeds as if you had hit RETURN and your favorite number.

Dennis


*** Makefile~	Mon Apr  6 15:41:45 1992
--- Makefile	Thu Apr  9 10:39:19 1992
***************
*** 44,49 ****
--- 44,53 ----
  AS86	=as86 -0 -a
  LD86	=ld86 -0
  
+ # If you want to preset the SVGA mode, uncomment the next line
+ # and set SVGA_MODE to whatever number you want.  I use #2.
+ #SVGA_MODE=	-DSVGA_MODE=\#2
+ 
  AS	=as
  LD	=ld
  #LDFLAGS	=-s -x -M
***************
*** 124,130 ****
  	$(LD86) -s -o boot/setup boot/setup.o
  
  boot/setup.s:	boot/setup.S include/linux/config.h
! 	$(CPP) -traditional boot/setup.S -o boot/setup.s
  
  boot/bootsect.s:	boot/bootsect.S include/linux/config.h
  	$(CPP) -traditional boot/bootsect.S -o boot/bootsect.s
--- 128,134 ----
  	$(LD86) -s -o boot/setup boot/setup.o
  
  boot/setup.s:	boot/setup.S include/linux/config.h
! 	$(CPP) -traditional $(SVGA_MODE) boot/setup.S -o boot/setup.s
  
  boot/bootsect.s:	boot/bootsect.S include/linux/config.h
  	$(CPP) -traditional boot/bootsect.S -o boot/bootsect.s
*** boot/setup.S~	Mon Apr  6 13:32:48 1992
--- boot/setup.S	Thu Apr  9 10:36:55 1992
***************
*** 245,250 ****
--- 245,251 ----
  	mov	es,ax
  	lea	si,msg1
  	call	prtstr
+ #ifndef SVGA_MODE
  flush:	in	al,#0x60		! Flush the keyboard buffer
  	cmp	al,#0x82
  	jb	nokey
***************
*** 259,264 ****
--- 260,266 ----
  	mov	ax,#0x5019
  	pop	ds
  	ret
+ #endif
  svga:	cld
  	lea 	si,idati		! Check ATI 'clues'
  	mov	di,#0x31
***************
*** 497,502 ****
--- 499,507 ----
  	call	prtstr
  	pop	si
  	add	cl,#0x80
+ #ifdef SVGA_MODE
+ nonum:	mov	al,SVGA_MODE		! Preset SVGA mode 
+ #else
  nonum:	call	getkey
  	cmp	al,#0x82
  	jb	nonum
***************
*** 508,513 ****
--- 513,519 ----
  zero:	sub	al,#0x0a
  nozero:	sub	al,#0x80
  	dec	al
+ #endif
  	xor	ah,ah
  	add	di,ax
  	inc	di

-- 
Dennis T. Flaherty     dennisf@Miles.com
Miles, Inc.            dflahert@chekov.helios.nd.edu
Diagnostics Division
My doctor says Mylanta, but my boss says Alka-Seltzer!
From: audit036@spacm1.spac.spc.com (David.L.)
Newsgroups: comp.os.linux
Subject: bash ?
Date: 7 Apr 92 11:26:26 PST
Organization: Security Pacific Automation Co., LA, CA

Hi

Where do I get am image or sources for bash ? do I need to get the earlier root
image ? (.12 , .11 ) ? I'm using 0.95a.

--
---->	david@chaos.spc.com	OR	audit036@spacm1.spac.spc.com
David L.
From: juh@qt.IPA.FhG.de (Juergen Henke)
Newsgroups: comp.os.linux
Subject: Re: tar files on floppy.
Date: 13 Apr 92 15:56:36 GMT
Organization: /users/juh/.organization

In article <1992Apr13.132029.8256@colorado.edu> drew@caesar.cs.colorado.edu (Drew Eckhardt) writes:

   When you rawrite to a floppy, you write to the raw device.  The file size,
   etc are lost, and are not encoded in a compressed file as they 
   are with a .tar file.  Solutions to this problem are to  :

[...]

I've done this now several times, with GNU-tar (the normal linux tar) it's no
problem to read a rawritten (:-)) compressed tar from a floppy, just use 
(for example)

		tar xvZf /dev/PS0
                      ^
                      |
           compress/uncompress option

Juergen


--
_________________________________________________________________________
Juergen Henke, e-mail juh@IPA.FhG.de, PSI-mail PSI%4505016002::JUH_IPA
Fraunhofer-Institut f. Produktionstechnik u. Automatisierung
Nobelstrasse 12, D-7000 Stuttgart 80
From: alsaggaf@ERL.MIT.EDU (M. Saggaf)
Newsgroups: comp.os.linux
Subject: Re: Linux SCSI support
Keywords: scsi, future domain, linux
Date: 10 Apr 92 22:33:01 GMT
Organization: Massachvsetts Institvte of Technology

Is there any way Linux can work with a SCSI Future Domain 1670 host
adapter? I'm a new user of Linux. Version .95a could not recognize my
hard drive. I also have an RLL drive connected to an Adaptec 8-bit
(XT) controller (in my 386 computer). Version .95a failed to recognize
that one as well. Is there any way I can get Linux to work with any of
these? Thanks.

-- M. Saggaf (alsaggaf@erl.mit.edu)
Xref: sparky comp.os.linux:237 alt.os.linux:2341
From: sweh@spuddy.uucp (Stephen Harris)
Newsgroups: comp.os.linux,alt.os.linux
Subject: Large disk partition
Date: 7 Apr 92 20:22:08 GMT
Organization: Spuddy's Public Usenet Domain

Is it possible for Linux to use a disk partition greater than 64Mb ?
I have a 650Mb disk at 1283x16x63.  DOS takes up the first 1023 clinders
(the most it can have), leaving me 128Mb as a second partition.  But when I
try mkfs it moans for greater than 64Mb :-(

So I now have 64Mb of unused disk (and unusable!  Stupid idea of BIOS boot to
have each partition starting before cylinder 1024.  means my last partition
MUST be at least 128Mb).

Alternatively, could I make this into an extended partiton, with 2x64Mb
in that, or even 1x10Mb (root+tmp), 1x12Mb(swap=3xRAM),1x64 (/usr), 1x42 (think
of something!).

If so, how?  I've read the begineers guide, and the FAQ (Mar 29th) mentions
hda5 as extended partition with a warning, but I couldn't find any info
on how to create this extended partition (NOTE: Dos fdisk won't do it because
it is above the 1024 cylinder limit), nor how to make this as root partition.

Help please!  I am on 0.95c (yippeee! I successfully managed to get Linus's
patches to work! Well the kernel boots :-) ).

Thanks in advance.
-- 
                               Stephen Harris
               sweh@spuddy.uucp    ...!uknet!axion!spuddy!sweh

 * Meeeeow ! Call Spud the Cat on > +44 203 638780 < for free Usenet access *
Xref: sparky comp.os.linux:332 alt.os.linux:2419
From: shem@phoenix.oulu.fi (Janne Himanka)
Newsgroups: comp.os.linux,alt.os.linux
Subject: Which graphics card for a new Linux machine?
Date: 11 Apr 92 13:53:18 GMT
Reply-To: shem@phoenix.oulu.fi
Organization: Tilde's home bakery

I'm about to buy a new machine, in which I will run mainly Linux. I
have an attractive offer of a 486 machine that has Microgram
motherboard with local bus (directly on the motherboard) SVGA card
with a S3 chip. That is supposed to be a very fast configuration, and
popular with (blech) MS-Windows. But I'm not sure if I should buy this
card, since it's new and I anticipate it won't be among the first cards
that the Linux (or BSD) X servers will have drivers to. So, should I
buy a tried and true ET4000 card instead?

I would appreciate a general comment on graphics cards from the
people who are working on Linux's graphics, since it might shed light
for others also. 

-Janne

"What did you do with the Pharaoh + shem@phoenix.oulu.fi
 Great Outhouse 8?"               + shem@nic.funet.fi
"We ate him. He was unspeakably   + TKOP-HJH@FINOU
 toothsome."                      + Oulu Univ., Dept. of Libr. & Inf. Sc.
From: zlsiial@uts.mcc.ac.uk (A. V. Le Blanc)
Newsgroups: comp.os.linux
Subject: include/linux and include/asm (was Re: kernel building problems)
Date: 14 Apr 92 14:58:22 GMT
Organization: Computing Centre, University of Manchester

In article <LILJEBER.92Apr11131400@kruuna.Helsinki.FI> liljeber@kruuna.Helsinki.FI (Mika Pekka Liljeberg) writes:
>
>I compiled .95c first without and the with the HJ patch. There were no
>problems either way. Then I moved the kernel includes under /usr/include/linux
>with HJ's conv script. I hope this will become "official" practise, since
>it makes everything ever so much simpler. How about it, Linus? :)

The include files distributed with the kernel should not be part of
normal C programs, and are closely linked with the kernel.  For the
purpose of compiling fundamental utilities, they are often useful, and
for this reason I have usually put at least those in linux/include/linux
and those in linux/include/asm into /usr/include/linux and /usr/include/asm
respectively.

I hope this will NOT become the official practice, in that I do NOT want
to see these files 'distributed' with the compiler; this would cause too
many problems coordinating versions.  The include files used to compile
Linux MUST be able to be changed as Linux changes, and so are distinct
from the include files used by the C compiler.  In any case, the only
compilation about which I have heard that these include files caused a
difficulty was the compilation of tools/build, which is, of course, not
part of the kernel, but a tool used to put the kernel together.

     -- Owen
     LeBlanc@mcc.ac.uk
Organization: Sophomore, Physics, Carnegie Mellon, Pittsburgh, PA
Newsgroups: comp.os.linux
Date: Thu, 16 Apr 1992 19:03:30 -0400 
From: "Demian A. Johnston" <dj1l+@andrew.cmu.edu>
Subject: Re: ESDI drives

Excerpts from netnews.comp.os.linux: 16-Apr-92 Re: ESDI drives by Brian
Chojnowski@osiris 
>        mkfs was able to format the partition that I had prepared, but
>mount gave me an error 2. Does anyone know what this error pertains to?
>I am using an ESDI drive. Other than that, I have followed the installation
>guildlines. They were pretty simple, I prepared the 95a boot and root diskes
>on 1.2M floppies, set a partition with fdisk, that fdisk on linux was able
>to read, then did mkfs -c /dev/hda2 (was second partition). That worked
>fine, but got error 2 for mount /dev/hda2 /user.


I think  I might no your problem..  I had problems when I made a very
large partition..  You might want to try and smaller partition size.  I
think Linux has a 64Mb limit...  My  partitions are on the order of
40,000 blocks...

                                                  Demian 
                                              --->  daj+@cmu.edu
                                              --->  dj1l@andrew.cmu.edu
                                              --->  demianjn@ids.jvnc.net
From: david@maxwell.ucsc.edu (David Darknell)
Newsgroups: comp.os.linux
Subject: X-Windows status?
Date: 14 Apr 92 19:14:41 GMT


Whats the current status of X?  Is there something available
to play with?  

David

Newsgroups: comp.os.linux
From: abc@banjo.concert.net (Alan B Clegg)
Subject: Unfortunate, but true....
Organization: Concert Network -- Internet Operations Group
Date: Wed, 8 Apr 1992 18:04:09 GMT

I will *NOT* be producing the "ABC Release of Linux .95a" before I go on
vacation.  I am currently over-whelmed by work, and won't have free-time
before leaving on Saturday morning.

In the off-chance that I do get some time, it will be devoted to getting
my scsi disk back working again, as that is where the sources that I have
so-far compiled are living... 8-(

-abc
-- 
abc@concert.net				Alan Clegg - Network Programmer
KD4JML (just my luck!)			MCNC -- Center for Communications
Newsgroups: comp.os.linux
From: hlu@yoda.eecs.wsu.edu (Hongjiu Lu -- Graduate Student)
Subject: Re: GCC2.1 (Wonderful !)
Keywords: gcc, 2.1, 1.40
Organization: Washington State University
Date: Tue, 14 Apr 92 06:50:32 GMT

In article <20176@castle.ed.ac.uk> pthoms@castle.ed.ac.uk (P Thomson) writes:
>
>
>There seem to be some band width about problems with gcc2.1, I would
>like to say that after installing it and getting the swap space 
>sorted out I've had no problems. In fact running it on 2M bytes memory
>4M swap space I managed to compile the best part of 1M byte of source
>code this evening (in about 30 minutes) the amount of disk traffic
>was not nearly as bad as I thought it might be. The source code was
>
>

It seems that gcc 2.1 can run with 2MB RAM. I think it's the time we
retire gcc 1.40. Lots of problems about kernel and gcc 2.1 are related
to the old gcc 1.40. With gcc 2.1, we can use the shared libs as the
standard. So we can squeeze more stuffs into rootimage. I really miss
bash. I had to copy it from 0.12 rootimage.

What do you guys think?


H.J.
From: jnelson@plains.NoDak.edu (Jim Nelson)
Newsgroups: comp.os.linux
Subject: Re: Problems with serial port drivers??
Date: 13 Apr 92 15:27:45 GMT
Article-I.D.: plains.16739
Organization: Chaos Central, Fargo ND

In article <54335@hydra.gatech.EDU> gt0178a@prism.gatech.EDU (Jim Burns) writes:
>in article <LILJEBER.92Apr11124027@kruuna.Helsinki.FI>, liljeber@kruuna.Helsinki.FI (Mika Pekka Liljeberg) says:
>> using the same IRQ line simultaneously. Isn't it possible to poll all the
>> UARTS on the IRQ line in the interrupt handler? Ie. you'd need a slightly
>
>You're not *supposed* to be able to do this. The ISA interrupts are level
>triggered, which I believe means that after the ICU latches the first
>interrupt, a 2nd one won't still be active after the first one is serviced.
>You might try polling all devices on any interrupt, not just poll for the
>*first* device that needs service. Don't know how successful that would be.
>The MCA interrupts are level triggered, so this is not supposed to be a
>problem there.


Dunno about MCA.  Never had the pleasure.  I do know that *sometimes* you
can move a comx to another IRQ.  If you have an internal modem, then you can
change it's irq if you like voiding any warranties you might have on your
hardware.  One of the pins on the modems bus fingers is the apropriate IRQ
line.  A little soldering can re-arrange these.  A friend of mine is using
this techniqu with great success.  He has his modem on com3 and a mouse on
com1, and they both work simultaneously.

I have the doc for it at home, I think.  Email me and I'll try to find it
and mail it back to you.

Dependng on your hardware, the above may or may not work for you.

-- 
Jim, in the Land of the Lost.            |Disclaimer:  These are probably 
ObQuote: Do Not Meddle in the Affairs of |   opinions.  I'm probably not
          Wizards, For You are Crunchy,  |   supposed to have any.
          and Good with Ketchup.         |