SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 13 | March | 2006 ]

<< Previous Message << >> Next Message >>


Date: Mon, 13 Mar 2006 22:47:20 PST8
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Network Not Working

In <20060312143741.94489.qmail@web81609.mail.mud.yahoo.com>, on 03/12/06
at 06:37 AM, Harry Motin said:

> 3. According to my system information the VIA adapter, the video AGP
>adapter and the Adaptec SCSI adapter were all sharing interrupt A (hex).
>I was able to remove the video AGP adapter from this interrupt level by
>altering a BIOS setting, but that was all. I could not effect either the
>VIA adaptetr or the Adaptec adapter in the BIOS.

You might want to see it Veit's spciirq can do the job.

The VIA NIC drivers are notoriously bad. The Intel drivers are usually
better. That said, I think you might be able to find an alternative
driver for the VIA. How does pci.exe describe the NIC chips?

> 2. Can anyone explain the message about binding "VECTOR to FETND_NIF"?

Sure.

>What is VECTOR? I know that FETND_NIF is the driver for the VIA NIC.

The terms refer to the internals of the NDIS protocol. Basically the
message means the upper level of the stack could not bind to a NIC driver.
In your case this occured because the NIC driver did not load.

> I really do not know how to start troubleshooting this problem. Any
>help on this is greatly appreciated. Thanks in advance.

If you review your message archive, you will see I typically ask to see

\config.sys
\startup.cmd (if you have one)
\ibmcom\lantran.log
\ibmcom\protocol.ini
\ibmcom\macs\yournic.nif (yournic is the name of your nic's nif)
\ibmlan\ibmlan.ini (if you have LAN networking installed)
\mptn\bin\setup.cmd
\mptn\etc\dhcpcd.cfg
\mptn\etc\resolv*

Given your additional issues, I'd need to see the output of pci.exe. Run
it twice. Once as pci -S. The second time as pci -P -B -D -R.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 Warp/eCS/DIY/14.103a_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------

=====================================================

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
"postmaster@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 13 | March | 2006 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.