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 [ 22 | November | 2002 ]

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


Date: Fri, 22 Nov 2002 18:55:19 PST7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: PCMCIA Lan Card

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

In <0H6000KD6BYE2A@mta7.pltn13.pbi.net>, on 11/22/02
at 06:23 PM, sshapiro@ucsd.edu (Sandy Shapiro) said:

>I then replaced Protocol.ini from the Linksys driver with Protocol.ini
>from the 3Com driver. ELPC3OS2.NIF was already there.

Oops.

>Now I get numerous errors during boot, the first one is that it is unable
>to load \IBMCOM\PROTMAN.OS2.

That's expected when you edit things without knowing what does what.

>important lines. Could I try replacing the 3Com Protocol.ini with the one
>from Linksys, and just change the reference to the driver?

That's what whould have happened if you used MPTS to do the switch. Try
this:

- leave the 3com card installed
- restore the orginal Linksys protocol.ini
- reboot
- ignore the error messages
- run MPTS
- select the Linksys driver in the lower listbox window
- click the change button
- find the 3com card in the list
- select it
- click OK
- follow the prompts
- reboot

If you added the /IG switch to the Socket Services driver, you will need
to edit config.sys and remove it.

Steven

--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.35 #10183 Warp4/FP15/14.085_W4
www.scoug.com irc.webbnet.org #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
"rollin@scoug.com".

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


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

Return to [ 22 | November | 2002 ]



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.