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 [ 06 | May | 2004 ]

>> Next Message >>


Date: Thu, 6 May 2004 01:48:32 PDT7
From: "i-lists" <i-lists@synass.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: netbind

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.
=====================================================

Hi SCOUGians
With replacing a NIC one should NOT REMOVE the previous settings !!!
The connections and crossreferences between NIC, MPTS & TCPcfg are very
complex !!

IMPORTANT:
Changing a NIC should ONLY be done with CHANGING the respective
selection in MPTS !

Procced like following:
1) While the old NIC is still installed and working:
Make sure that the new NIC's drivers are installed !
2) Then, with MPTS, do change from the present NIC's settings to the
future NIC's settings !!

3) Shutdown the system and switch off !

4) Replace the NIC.

5) Reboot your system with the NEW set NIC !
The system should recocnize the new installed NIC !!

I had some different slow NICs in our systems and like this it worked
here without any =

problems when I changed to an identical NIC on all systems !!!

Now the driver maintenance is easy too: All systems do have the same
driver and =

versions: Intel 4.48

ONE EXCEPTION:
The notebook has its own in-built NIC different from the NON notebook
systems =

and is bi-functional: Ethernet & WLAN together with a personal and
mobile AP ;-))

Cheers, svobi =

marka@relaypoint.net on 05/05/2004 21:56:10
Please respond to scoug-help@scoug.com
To: scoug-help@scoug.com
cc: =

Subject: SCOUG-Help: netbind

In , on 05/05/04 =

at 01:20 PM, "Steven Levine" said:

>You should be looking for the reason the driver will not load.

LOL - now I gotta clean off the monitor!

>VECTOR is the internal name for on the interface structures. TCP/IP
>can't bind to a driver that's not loaded.

Are you saying that the driver is not loaded? All the other messages in
Lantran and on bootup indicate everything loaded correctly.

---
>>> Say NO to H T M L in Mail and News <<<
>>> A G A I N S T T E R R O R & W A R <<<=

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

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".

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


>> Next Message >>

Return to [ 06 | May | 2004 ]



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.