| ???: |
"Lewis G Rosenthal" <os2-wireless_users@2rosenthals.com> |
?? ????
????????? |
| ??: |
Re: [OS2Wireless] More networking questions |
| ??: |
Mon, 17 Aug 2009 14:06:52 -0400 |
| ??: |
OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com> |
|
|---|
Hi, Mark...
On 08/17/09 07:56 am, Mark Henigan thus wrote :
Hello Lewis:
On the box with one each of a wireless and a
wired NIC, I deinstalled the two NICs in MPTS
but now get the message:
"
Protocol Managaer Not Installed.
NET3406 An error occurred while opening network
device driver NET1=NETBIOS.
Indeed, following onto what Dave has said, you wouldn't see this message if something in CONFIG.SYS wasn't looking for a NIC driver configuration.
NET3406: An error occurred while opening network device driver *** =
***.
Cause: The device driver listed in the error message could not be
installed.
Action: Verify that the listed entry in the [networks] section of
the IBMLAN.INI file is valid. In the CONFIG.SYS file, verify that
the DEVICE entry that loads this device driver has correct entry
parameters. Also verify that the DEVICE entry specifies the correct
path name of the device driver.
SYS1719: The file C:\IBMLAN\NETPROG\NETWKSTA.200
specified in the IFS statement on line 36 of the
config.sys file does not contain a valid device
driver or file system driver.
Line 36 is ignored.
"
Well, it's hard to install NETWKSTA.200 if there's no NIC to bind. :-)
I would prefer not to deinstall and reinstall MPTS
because I've had difficulty with it in the past.
When I deinstalled the two NICs, I of course had
to remove each protocol before removing the NIC.
Is there something in IBMLAN.INI or config.sys
that I should change that would likely fix this?
Dave has mentioned the script, which escapes me...hold on...nope, I don't see it here, now.
I would go through CONFIG.SYS and REM whatever you find located in \MPTN or \IBMCOM or \IBMLAN (et seq), assuming you want to rmeove all networking support for the time being. That said, the above messages are just boot time noise, anyway; networking isn;t going to work with no cards bound, and networking errors won't make much difference.
On a second box I have the NIC loading fine
according to the verbose boot information but then
am stopped by:
"ioctl(SIOCAIFADDR): Invalid argument"
and have to hit ENTER to continue. I recall
searching for SIOCAIFADDR in all of the DLLs and
SYS and other files I could think of since it was
likely present in ASCII text. I found it that way
and was able to solve a similar problem previously
as a result. But, I seem to have saved the
information in that secret place where I "save" so
much valuable material for future reference.
Sounds like we're not able to read the MAC address on the card (likely an Intel model, my gut says) to add it to the internal tables. Try adding a NETADDRESS parameter for the card in PROTOCOL.INI under the appropriate section (you may use MPTS for this).
(FYI:
SIOCSIFADDR sets an interface address.
SIOCAIFADDR adds or changes an interface address.
SIOCDIFADDR deletes an interface address.
SIOCGIFADDR gets an interface address.
(Anyone else have a different take on this?)
Any thoughts? Or, have I provided far too little
background information?
No, I think we've got the info we need, we just need to stew on it a little bit.
--
Lewis
-------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE
Rosenthal & Rosenthal, LLC www.2rosenthals.com
Need a managed Wi-Fi hotspot? www.hautspot.com
Secure, stable, operating system www.ecomstation.com
-------------------------------------------------------------
|