SCOUG-HELP Mailing List Archives

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

Date:	Tue, 18 Jan 2005 10:53:21 PST8
From:	"J. R. Fox" <jr_fox@pacbell.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: next step ? (on 1.2 install)

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:

> Installing NIC from the MPTS notebook is drop-dead simple, unless one figures out a
> way to do this this hard way. Click on change and follow the prompts.

Thanks, Steven, and good to hear it. This is very likely something even I can do.
(Getting the Gigabit NIC to work *also* might be another matter, but I never got as far
as trying out that GENMAC driver.

> That said, you don't really know what is causing your install to fail. It could be
> something related to your Peer selections.

I don't recall there being much in the way of choices to make at the Peer portion of
the install, other than selecting NIC(s) and protocols, but . . . .

> It could be something else.

Maybe it has something to do with that "Can't Find Slot" message that comes up when the
Shuttle boots eCS (from the 1.1 partition), switching over to the default slot, where
it does find one of the two built-in NICs ? Could that cause the whole dang install to
bomb out, just because the Peer component gets stymied ? I note that the NDIS info
files says something about determining and explicitly commanding the Slot assignment,
though I don't entirely follow what they're saying.

O.K., but how -- precisely -- does one go about pinpointing the exact cause ? I have
no clue how to go about this.

> If you don't care to have Peer, don't install it.

Well, as I said, there is probably no need for it here, for the indefinite future.
Especially if it has no repercussions for Internet access or any other important areas
of normal computer usage.

> If you want Peer, we need to figure out what you are doing that caused the install to
> fall
> over.

Again, I would need some detailed plan of investigation. With such a plan in hand, one
thing I could do is to partition image the established, working 1.2 with DFSEE. That
way, I could scrub it off for additional Test Install runs, with some good confidence
of being able to get back to where I had gotten, without too much difficulty.

Regards,

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 [ 18 | January | 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.