Once again: win3.11, Novell, ms-tcp/ip, ne2000 difficulties
Marko Niinim{ki
It seems I'm unable to run both Novell Netware (shell 3.32)
and Microsoft's 32 bit tcp/ip in Win 3.11.
simultaneously. Windows locks up on startup and the bootlog.txt file
contains: LoadFail = NETAPI.DLL Failure code is 02
The last line is NCD Done=NCD Done.
win /n works: netware drives can be accessed, but tcp/ip is unavailable.
This is what I've got in ny autoexec.bat:
lh ne2000 -n -w 0x60 5 0x300
ipxp
netx
f:login mtlpc13
\windows\net start
(path settings)
share /l:500 /f:5100
and there is a line
device=ifshlp.sys
in config.sys
I get no errors during boot. Windows network adapter irq setting is 5,
but when I set it, windows claims that it is used by another system
(even though this is not correct).
Should I change the IRQ on the ne2000 or is there something else
I should do?
Yours,
-man
--
Marko Niinimaki, Department Assistant, Dept. of Mathematical Sciences
University of Tampere * m...@sjoki.uta.fi OR Marko.N...@sjoki.uta.fi
C=fi ADMD=Fumail PRMD=inet O=uta S=csmani * http://www.uta.fi/~csmani/
Addr: Satamakatu 5 c 77, 33200 Tampere, Finland * tel +358-31-222 55 48
JJ Keijser
BWA...@INHUF.ANG.AF.MIL (William Walker) wrote:
>You have to use NDIS drivers if you want to access both of these stacks.
>remove the packet driver and let windows install the ndis driver for you. A
>net initialize command will be placed at the start of you autoexec which
>will load the NDIS drivers.
No you don't coz you can't! If somebody can tell how to access a Novell server
using the NDIS3 protocol (no ODI drivers) I'd be very interested.
Novell works best with ODI drivers...
>>This is what I've got in ny autoexec.bat:
>>lh ne2000 -n -w 0x60 5 0x300
>>ipxp
>>netx
>>f:login mtlpc13
>>\windows\net start
>>(path settings)
>>share /l:500 /f:5100
You load a packet driver first and then the Novell driver. Can't do that. Get
the latest Novell drivers from ftp.novell.com:/pub/updates/nwos/vlmkt?.exe.
They contain the latest ODI drivers, which are loaded as follows:
lh lsl
lh ne2000 (the ODI MLID, not the packet driver)
lh ipxodi
lh netx
f:login
And you have to setup WfWg to use ODI/NDIS3 drivers.
I'm using Novell 3.12 + WfWg on a 3Com 3c5x9 adapter and all is working well.
If you're interested I can mail you my configuration files.
HTH,
JJ
----------------------------------------------------------
Jan Just (JJ) Keijser
SMTP: j...@lbvrtda.logica.com
X400: C=GB A=ATTMAIL P=Logica O=LBV OU1=LBVRTDA S=JJK
I prefer clear blue skies over a bunch of clouds any day
My views are my own...
flames > /dev/null 2>&1
----------------------------------------------------------
Markus Gerle
>Novell works best with ODI drivers...
>
>You load a packet driver first and then the Novell driver. Can't do that. Get
>the latest Novell drivers from ftp.novell.com:/pub/updates/nwos/vlmkt?.exe.
>They contain the latest ODI drivers, which are loaded as follows:
>lh lsl
>lh ne2000 (the ODI MLID, not the packet driver)
>lh ipxodi
>lh netx
>f:login
>
>And you have to setup WfWg to use ODI/NDIS3 drivers.
>I'm using Novell 3.12 + WfWg on a 3Com 3c5x9 adapter and all is working well.
>If you're interested I can mail you my configuration files.
>
I am running TCP/IP and IPX with Netware 3.12 and the TCP/IP32 stack too.
After many problems with the Trumpet Winsock I had no problems with the
TCP/IP32 stack together with ODI-drivers (I am using 3Com NIC愀).
But during installation Windows is changing your autoexec.bat. I changed it
back and wrote my own net.bat file. For this it is important to know that you
must call odihlp.exe after net start.
If you are interested in my configuration files you can contact me via privat
e-mail (I have not so much time to look everyday for the news.).
Best regards
Markus (ge...@mzdmza.zdv.uni-mainz.de)