<< Previous Message << >> Next Message >>
Date: | Sun, 23 Jul 2000 16:16:22 PDT |
From: | "Steven Levine" <steve53@earthlink.net > |
Reply-To: | scoug-help@scoug.com |
To: | scoug-help@scoug.com |
Subject: | SCOUG-Help: GTE DSL Challenges Skye To Steel Cage Match |
Content-Transfer-Encoding: 7bit
In <397B6C53.192@peterskye.com>, on 07/23/00
> "No interfaces to trace!"
It probably needs to be:
iptrace lan0
since the interface is not yet set up.
>DEVICE=F:\IBMCOM\MACS\AN16.OS2
My notes say NIC must follow MPTS. Move this after
DEVICE=F:\MPTN\PROTOCOL\IFNDIS.SYS
I've appended some of the network specific parts of a working config.sys,
> DriverName = AN16$
This should be OK. IRQ 10 is usually free.
>option 60 "IBMWARP_V3.1" # Vendor Class
These look OK. You might want to turn on the logging options (i.e.
>LANTRAN.LOG:
>IBM OS/2 LANMSGDD [01/03/00] 5.05 is loaded and operational. IBM OS/2 LAN
This is way too short. It should show the NIC loading and report the MAC
I've attached one from my box.
When you boot, use Alt-F2 and watch for the driver loading message. Also,
You might want to consider adding the NetBIOS protocol, just to make the
If none of this helps, I've got more esoteric stuff we can try.
Steven
--
File attachment:
LANTRAN.LOG
Return to [ 23 |
July |
2000 ]
at 03:06 PM, Peter Skye
so you can get an idea of on ordering that can work.
> interrupt = 10
> iobase = 0x300
>option 77 "IBMWARP_V3.1" # User Class
logitem, logfile).
>Netbind
address. See my suggestion re reordering the load statements.
haul out your trustly hex viewer and see if the driver supports the
VERBOSE keyword. If so, add it to the [an16_nif] section of protocol.ini.
logging more verbose.
----------------------------------------------------------------
"Steven Levine"
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
----------------------------------------------------------------
Content Type: application/octet-stream
<< Previous Message <<
>> Next Message >>