<< Previous Message << >> Next Message >>
Date: | Mon, 7 Aug 2000 15:05:04 PDT |
From: | Peter Skye <pskye@peterskye.com > |
Reply-To: | scoug-help@scoug.com |
To: | scoug-help@scoug.com |
Subject: | SCOUG-Help: DSL Duck Does DHCP (was: D-Link Challenges ...) |
Content Type: text/plain
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
Mark Abramowitz wrote:
>
> So, it was a BIOS/interrupt problem, and not an OS/2 one.
Pretty much. Regarding OS/2, one of the D-Link driver files was bad
(Steven fixed it for me) and, to be honest, OS/2's RMVIEW isn't very
helpful since it doesn't report all IRQs. (ScanPCI only reports PCI
interrupts. When RMVIEW reports the _same_ interrupt number for an ISA
card and _doesn't_ report the PCI owner of that interrupt, it's not
obvious until you compare the two different lists.)
But the major problem was the bug in the Award BIOS (it's not that old,
Nov97) which caused the interrupt assignment errors. The D-Link driver
file error was a problem too but something I could have quickly worked
around by using a different NIC.
As for the TidalWave 128 sound card, I tend to think it too was a victim
of the Award BIOS bug.
- Peter
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
Return to [ 07 | August | 2000 ]