SCOUG-HELP Mailing List Archives

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

Date:	Thu, 5 Jun 2003 00:47:40 PDT7
From:	waynec@linkline.com
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Need Netware requester setup help

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 writes:

>
> If the install diskettes are a problem, dup them and tailor a set for the
> P2. Don't bother trying to make the same set work for both systems.
>

I just finished trying a tailored set (for the AMD, because that's where I
want to build a vanilla Warp maintenance partition). When the attempt to
install is completed (which is after mpts configuration at the end of the
install procedure) it does some loading (with the little slashes that pace
back & forth). Then it says to remove the diskette and the machine will be
restarted automatically. It then does start a bootup, beginning with the
bios boot, then goes to an IBM logo screen (without a fix-level at the
bottom) and just hangs there.

After booting up the Warp install diskettes again, I took a look at the
config.sys file and the os2\boot folder and found there were no entries for
my U160 scsi driver, and several other drivers seemed to be missing. Also
there were some config.sys entries of a type that were unfamiliar to me, and
a lot more networking entries than I'm used to seeing. I tried manually
adding the files I knew should be there to config.sys and the os2\boot
folder, but I keep getting the same logo-screen hang.

Can you think of a reason those files aren't getting into the folder(s) and
config.sys during the install? The files ARE on the install disks 1 & 2.

>
> A couple of comments based on problems I've seen in the past. Some setups
> need to have 803.3 bound before 802.2. It depends on what order you bound
> them on the server. If they need to be swapped, change protocol.ini to
> read:
>
> ETHERNET_802.3 = "yes"
> ETHERNET_802.2 = "yes"

I did try this (I was aware of this issue), and I tried again tonight to be
certain.... sent you (Steven) the current setup and results separately.

>
> also verify that:
>
> NETADDRESS = "0000C05EF08D"
>
> is the correct value for the NIC you have installed.

Golly, I've forgotten how to find the correct address, how can I do that?
I did note a different address was being posted in lantran.log, so I changed
protocol.ini to match that address. I used to have another NIC in the P2, so
that's probably how I got them mixed up, although I thought I heard
somewhere that the protocol.ini address doesn't have to match the actual
card address.

>
> Your net.cfg seems a bit deficient. If always included:
>
> LINK DRIVER ODI2NDI
> FRAME ETHERNET_802.3
> FRAME ETHERNET_802.2
> FRAME ETHERNET_II
>
> when using NDIS drivers.
>

Never had those entries in the past... I tried them tonight, then took them
back out when it still wasn't working. I'll put 'em back in if you really
think they're needed.

Another question... I remember at one time having specified "netbios"
protocol on the NIC, at someone's advice, but I don't remember why.
Although, the only old protocol.ini files I've found on my system are even
smaller than the one I sent you. I do not have a clue as to what netbios is
or why I'd need it, do you?

Wayne

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

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 [ 05 | June | 2003 ]

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.