|
Next Meeting: Sat, TBD
Meeting Directions
|
Navigation:
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
|
|
Pictures from Sept. 1999
|
|
The views expressed in articles on this site are those of their authors.
|
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 [ 23 |
April |
2006 ]
<< Previous Message <<
>> Next Message >>
Content Type: text/plain
Steven Levine wrote:
>In <444B1983.2020509@usa.net>, on 04/22/06
> at 10:07 PM, Sheridan said:
>
>
>
>>There is no startup.cmd but the Startup folder in Local System has
>>TCP/IP Startup in it.
>>
>>
>
>As the list said, provide startup.cmd, if you have you. It's optional and
>if had one, you would know what it is.
>
>
I put the statement about no startup.cmd to let you know I hadn't simply
overlooked that item. Also, the comment about TCP/IP Startup was to let
you know I did see that and I knew it was a different program.
>
>
>>What is it we're looking for?
>>
>>
>
>We are looking for the reason or reasons you can not access your LAN.
>This is your problem. Is it not?
>
>
I should have been a bit more clear. What I was trying to ask was "what
are the catagories of clues are we looking for in those files".
>The first problem you need to fix is the failure reported on line 13 of
>LANTRAN.LOG. Your possible options are shuffle cards or find a better
>driver or get a NIC with decent drivers.
>
>
>
I see this is one the clues - an interrupt conflict. (I hate to admit
it but I missed that one the first time I read the log. Don't hurt
yourself laughting now! ) So the task at hand is to find the
conflict cause.
This MB has a built-in NIC and has been working with the same driver I
used this time ever since I first installed eCS 1.0. Therefore, I know
this NIC and driver work. Digging a little deeper.
I did something that crashed the system (it wouldn't even boot any more)
and decided to install version 1.2R instead of fixing things with my
backup. When I did the 1.0 install I did an advanced install because I
didn't want multimedia. Now that I have a digital camcorder I decided
to do a "default" install of 1.2R so I could have the multimedia stuff.
I suspect that is the first place to look for the conflict. Do you
agree and what tool would be best for that task?
Sheridan
=====================================================
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 [ 23 |
April |
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.
|
|