SCOUG-HELP Mailing List Archives

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

Date:	Sun, 13 Feb 2005 16:22:57 PST8
From:	"J. R. Fox" <jr_fox@pacbell.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: Help Desk 06 Feb. | 1.2 install residue

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

Steven Levine wrote:

> I draw pictures when it gets too complex since it's all relative when devices are daisy
> chained. When is a WAN interface when views from your LAN because a LAN interface to the
> next device in the chain.

Hi Steven,

Yes, diagrams or maps can really come in handy. Especially for the technically challenged,
like myself.

> >Well, ideally, I would like to get to a situation where I could connect the ethernet
> cable to *either* port at will (the Gigabit *or* the plain
> >ol' 100 NIC), and have it work.
>
> That will happen if you configure both interfaces. TCP/IP is smart enough to know which
> can see the outside world at a given point in time.

Hmmm, thought I had done that, esp. now that the NICs have individual addresses . . . .
What else needs to be done ?

> >In order to accomplish this, I'm guessing there would need to be some sort of specific
> Slot assignment (?)
>
> This is unlikely.

Then I should disregard that stuff in the drivers' .INF file about identifying or
designating the Slot Assignment ?

> All you need to to is have a driver loaded that works with the chipset.

E1000 was *supposed* to be it, but evidently that is not the case. Other than the GenMac,
I'm not sure what else to try. btw, REMing out the E1000 driver line in Config.Sys proved
to be a bad idea. That caused there to be *no* NIC functionality at all.

> >to be functioning normally . . . except for the fact that the eCenter bar at the bottom
> won't appear unless explicity invoked.
>
> That a eCenter properties settings option.

I didn't know it had one, but I'll check on that. What I did do was change SET
RESTARTOBJECTS=NO to SET RESTARTOBJECTS=STARTUPFOLDERSONLY,REBOOTONLY (I _think_
that's how it goes . . . anyway, it was cribbed from my working Config.Sys for eCS 1.1),
and *that* seems to have resurrected the eCenter at bootup. {Comparatively speaking, I
still miss some of what the WarpCentre gave us, and even have a lingering fondness for the
LaunchPad, althought it did take up too much space.}

Still looking for anomalies that might be related to the less-than-perfect install of 1.2
Have noted a few, but I'm not sure they will turn out to be repeatable. One that looks
persistent is a phantom 2nd. CD-Rom drive that shows up in Drives, etc.

Is IBMCDROM the successor to OS2CDROM ?

Jordan

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

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

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

Return to [ 13 | February | 2005 ]

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.