SCOUG-HELP Mailing List Archives

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

Date:	Tue, 18 Jan 2005 17:23:41 PST8
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: next step ? (on 1.2 install)

=====================================================
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 <41ED5AFC.C9A706F6@pacbell.net>, on 01/18/05
at 10:53 AM, "J. R. Fox" said:

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

IIRC, the Peer install can get confused if the NIC selection fails.

>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 ?

This is a definite indicator of NIC issues. It could be driver related or
it could be protocol.ini related. I'm not sure what you mean by "default
slot."

>? Could that cause the whole dang install to bomb out, just because the
>Peer component gets stymied ?

We've discussed this before and the answer is still yes.

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

These are PCI slot numbers, as shown by Veit's pci.exe. If you have
multiple NICs of the same type, you need to identify each by slot number.
Of course, since your NICs differ, you should not even have a SLOT keyword
in protocol.ini.

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

First I would need to see some current data. The last data I have is from
you 1/1/2005 22:51 attempt.

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

You don't need Peer to access the Internet. You need Peer to share files
and printers.

>Test Install runs, with some good confidence of being able to get back to
>where I had gotten, without too much difficulty.

Backups are good. It's up to you. If you don't need Peer, you might as
well install without it and go from there. We can always leave resolving
Peer install failures to someone who wants to use Peer.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.60b #10183 Warp4/FP15/14.100c_W4
www.scoug.com irc.fyrelizard.com #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".

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

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.