Aussie wrote: > The problem for mine was that the BIOS was assigning IRQ 9 for the NIC, > but Windows was assigning IRQ 10. Have a very close look at the IRQ's > for the card, both in the bios startup screen (after the memory check) > and in Windows and make sure the same IRQ is listed in both places. I > manually set the IRQ's to the same and the network has worked ever > since. Well, I'm pretty sure both cards were set with IRQ 10 when they came to me (as in that's what they were set to on their own hardware). At the moment, the Win95 machine is using IRQ 10 for the NIC, the Linux box IRQ 3, which I reset using the 'Atlantic' program, which gives the results: atlantic.c:v1.00 1/30/98 Donald Becker ([EMAIL PROTECTED]) Reading the configuration from the AT/LANTIC at 0x300... The current configuration is Register A 0x00: I/O base @ 0x300, IRQ 3, NE2000 mode, normal ISA read. Register B 0x00: Interface 10baseT. Boot PROM writes are disabled, CHRDY after IORD/IOWR. Which all looks right to me. I'll check the Win95 box next time I boot it though, not 'til tomorrow sometime - thanks for that idea. Something I've just discovered though, looking at the routing tables for both machines: On the Win95 box I've got a metric of 1, while in the Linux box I've got a metric of 0. I don't really know what this means, but I wonder if this could be causing problems? Thanks. -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
