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 [ 30 | August | 2004 ]

>> Next Message >>

Date: Mon, 30 Aug 2004 07:31:28 PDT7
From: sshapiro@ucsd.edu (Sandy Shapiro)
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Lan question

6
=====================================================
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.
=====================================================
This is a MIME encapsulated message.
Content Type: text/plain

Content-Transfer-Encoding: 7bit

In , on 08/29/04
at 10:43 PM, "Steven Levine" said:

>>Lantran.log shows an error message:

>>NETBIOS 4.0 is loaded and operational.
>>IBM LANVDD is loaded and operational.
>>IBM OS/2 LAN Netbind
>>PRO0025: An error occurred when the program tried to bind NETBEUI to
>>GENM32_nif. IBM - OS/2 Socket/MPTS NetBios Service Driver TCPBEUI:
>>Logical adapter 0 is trying to bind to TCP/IP interface lan0. LT00141:
>>Errors occurred while attempting to initialize TCPBEUI.

>It sure sounds like the NIC driver is not loading. If the NIC driver
>does not load, the upper level driver can't bind to it and that is what
>seems to be happening here.

>Check for IRQ conflicts and stuff like that. I suspect the eCS volume is
>loading more drivers than the Warp4 partition.

Hi Steven,

I don't see anything immediately obvious -- that doesn't mean I am looking
in all the right places.

For starters, here are the two config.sys files -- one from OS/2 Warp that
works, and one from eCS (on the same computer) that doesn't work.

If you have any suggestions, they will be very much appreciated.

Sandy

Content Type: application/zip

File attachment: config.zip

>> Next Message >>

Return to [ 30 | August | 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.