|
3.058 bytes |
Service Hints & Tips |
Document ID: RMIE-3BFEJ9 |
IBM PC330/PC350 - EtherJet shows conflicts using Windows 95
Applicable to: World-Wide
Problem:
Unable to configure adapter in PNP mode without conflicts.
Cause:
Windows 95 registers hardware in device manager that is not active. The secondary hard disk controller and USB ports are both PCI devices. These devices are not active unless something is connected to them. For this reason, the system BIOS does not allocate them as "system resources." Windows 95 does assign them resources in device manager, and therefore can cause resource conflicts.
For Example: Windows 95 will allocate IRQ15 to the secondary hard drive controller in device manager. Since this resource appears as available in the system setup under "ISA Legacy Resources" it is given to the EtherJet adapter during post. Windows 95 will then auto sense the new adapter and ask for the disk, but after rebooting there will be an exclamation point over the EtherJet adapter and it will not work. If there is a device attached to the secondary IDE port there will not be a problem as it will then register with BIOS as a "system resource."
Solution:
There are three different ways to circumvent the problem:
1. In device manager open the EtherJet adapter. Unclick "use automatic settings, and reassign the IRQ to a known free one such as 5"
2. Set IRQ 15 to "not available" in system BIOS
3. Set the adapter to "PNP locked" at known available resources.
This entire tip assumes the adapter begins in PNP mode and BIOS is set to factory defaults.
This could also happen with any PNP card that will accept IRQ15.
|
Search Keywords |
| |
|
Hint Category |
Adapter Cards, Windows 95 | |
|
Date Created |
15-11-96 | |
|
Last Updated |
21-05-98 | |
|
Revision Date |
19-05-99 | |
|
Brand |
IBM PC | |
|
Product Family |
PC 330, PC 350 | |
|
Machine Type |
6577, 6587 | |
|
Model |
All | |
|
TypeModel |
| |
|
Retain Tip (if applicable) |
| |
|
Reverse Doclinks |