Forum Home
Press F1
 
Thread ID: 17319 2002-04-02 09:55:00 Message for wuppo Guest (0) Press F1
Post ID Timestamp Content User
41449 2002-04-02 09:55:00 wuppo

Sorry about the delay in responding to your post, I've been out of town.

I have the driver disk for the NIC and I found a diagnostic program on it. I ran the utility but all it does is tell me what the settings are for the NIC.

The text up front on the utility implies that the IRQ can be changed, but the program doesn't match the promise!

I now plan to uninstall the NIC and physically unplug it, make IRQ 11 unavailable for PCI Steering via Bios by reserving it for Legacy ISA, reboot to (hopefully) shift PCI Steering elswhere then reinstall the NIC on a clean IRQ11.

Will this work or will the PCI Steering just go back to IRQ 11 as soon as the IRQ is made available for the PCI NIC?

Can't make matter worse. (famous last words)

Thanks

Jim 		Guest (0)
41450 2002-04-02 10:22:00 Jim,
Firstly, did the NIC diagnostic show that IRQ5 could be allocated to the NIC? If so, I'm surprised you couldn't force it from Device Manager. If you sidewise IRQ11 by setting it to Legacy in Bios, you should be able to then allocate it to the NIC under Device Manager. As you surmised; re-enabling IRQ11 in the bios will allow (and usually does cause) the origional configuration to take over. You basically have to leave the IRQ set to legacy if you want any control over it. The other possability is to juggle cards around in different PCI slots - the slots have preferential IRQ allocation orders. 		Guest (0)
41451 2002-04-03 00:33:00 Jim,
Further to above...
The fact that an IRQ has PCI steering associated with it shouldn't give your NIC grief - only perhaps if the IRQ is shared with another device. I suspect your problem will be software related.
Good Luck! 		Guest (0)
41452 2002-04-03 04:25:00 You dashed my hopes there Wuppo but saved me wasting time to no good purpose so thanks for adding the comment.

I have long suspected it was software related because after a lockup (as detected by a failure to send or receive email via Outlook 2000 (not Express) I would normally close Outlook and reboot. However, although Outlook appears to close normally, shutdown hangs and Ctrl/Alt Del brings up 'Outlook not responding'.

This suggests that part of Outlook's programming gets tangled with my network connection. Using 'End Task' allows the shutdown to proceed normally but then I can't tell if that would have restored my connection to life as it is too late, shutdown is in progress.

I have tried checking to see if Outlook has shutdown fully by looking at the Task Manager before trying to reboot but everything looks normal and there are no 'not responding' messages at that time. They don't appear until shutdown hangs.

Is there any program (Dr Watson perhaps) that will log the processes I have running and tell me what files are screwing up the shutdown?

I assume that the problem is a corrupted file but as far as I can tell I can't uninstall Outlook on its own and reinstall. I could try copying known good files such as exe & DLL from my other computer to this one but it would be a bit hit or miss as I don't really know what I am doing and some might be configured for W2K while the other @#$% box is Win 98.

Any suggestions?

Thanks, Jim 		Guest (0)
1