SCOUG-HELP Mailing List Archives

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

Date:	Tue, 18 Jan 2005 17:55:00 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.
=====================================================

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

Steven Levine wrote:

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

I'm not sure either. I may well be misquoting that boot-time message, which does go by
fairly quickly. The gist, it seemed to me, was that no (appropriate) NIC was found in
whatever slot was being looked at, so it went for the NIC in the other slot . . . which
must have been applicable, because it worked. This whole slot business seems kind of
arbitrary to me, since we're not talking about *real, tangible* slots (PCI), but the way
built-in chips happen to be wired on the motherboard. Alas, eCS won't take it so
casually.

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

But it seems to matter for boot-up purposes, or for the installer.

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

I'd be happy to send you the readout from PCI.Exe. The data from the 2nd. install attempt
probably won't differ enough from the first, but I expect the logs from the 3rd. (which
worked, except for Peer / TCPIP) likely would. I'd be glad to send this to you, as well
as any logs from further attempts.

> You don't need Peer to access the Internet. You need Peer to share files and printers.
>
> 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.

I'd still be curious to see a blueprint on how one goes about installing it a la carte,
after the fact. Might be a good Mr. KIA column in that.

At this point, I'm tempted to get the internet access going there and just declare
victory. If it is something to do with the dual NICs, that would be a semi-unique
circumstance, since not too many computers come this way. Therefore, of limited benefit
to others. It does leave open the question of what will happen when I get around to
trying a migration install over the *other* eCS boot partition. And dontcha think it is
kind of curious that we did not run into anything like this at the time you guided the 1.1
installs, on the same hardware ?

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.