TCPIP Dos/Winos2 Functionality

I have the following lines correctly situated in my config.sys:
      DEVICE=d:\tcpip\bin\vdostcp.vdd
      DEVICE=d:\tcpip\bin\vdostcp.sys
      RUN=d:\tcpip\bin\vdosctl.exe
Also in WINOS2 DOS_DEVICE it says:
      d:\tcpip\bin\vdostcp.sys
PROBLEM: I should be able to use the DIALER in WARP 4 and
then be able to connect to NETSCAPE in WINOS2, but the WIN version of NETSCAPE gives me the following error messages:

      WSO0002:Local Status NCB Failure
      Possible causes
      .Network TeleSystems TCP Stack not loaded
      .Invalid adapter number
      
      Netscape was unable to create a network socket or      connection
      There may be insufficient system resources or the
      network may be down (Reason:Network is down)

      Do you have any idea how to correct this problem?
harvey0Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sbuftonCommented:
It looks to me like you have another
winsock.dll in your DOS PATH before Warp's
winsock.dll. Make sure that the path set
in the AUTOEXEC.BAT includes
C:\TCPIP\DOS\BIN early on (perhaps before
c:\os2\mdos\winos2).

      Steve
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
harvey0Author Commented:
     This above may be one solution to a similar problem, but it is not the solution to my problem.
      When I boot into WINOS2, I do not get the following advisory:
            xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
              Virtual TCP/IP Version 2.1 for DOS
              Copyright (c) IBM Corp. 1992, 1993
            xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
              Version:  2.1.0.3
            xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

This suggests that I have not set up something properly to enable the TCP/IP advisory to show on booting into WINOS2.
I believe that this failure is what is causing the SOCKET problem.
      I'd appreciate knowing "WHAT" I need to do to correct this and "HOW" I would go about making the correction.
      Thank you.
      Harvey Goldenberg

0
sbuftonCommented:
I've taken a look at the settings for
"Windows Ping", in the TCP/IP utilities
folder. Having just tested it, I know that
it works:

The DOS_DEVICE contains
c:\tcpip\bin\vdostcp.sys

The AUTOEXEC.BAT contains:
PATH=C:\OS2;C:\OS2\MDOS;C:\;C:\OS2\MDOS\WI
NOS2;c:\tcpip\dos\bin;
SET ETC=c:\tcpip\dos\etc

Those are the only two TCP/IP-relevant
settings. I also do not see the message
you mention when I open a DOS window.

If you have those settings, I can only
suggest again checking for a winsock.dll
earlier in your DOS PATH than the
tcpip\dos\bin\winsock.dll - remember to
check in the WINOS2\SYSTEM directory, and
the Netscape directory too.

      Steve
0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

harvey0Author Commented:
     I would love for it to work as you say, but it does not.
I obviously do not have something configured properly. I do have the tcpip\bin files correctly listed. The PROBLEM "MUST BE" with
my having failed to INSTALL some part of the TCPIP aparatus or
the MPTS. Wherever my failure is, it still exists and I CANNOT use the dialer connect from the WARP 4 desktop to run NETSCAPE for WIN.
0
sbuftonCommented:
Can you use PING from a DOS prompt? Or the
Windows PING? If those work, then it
points to something (probably a
WINSOCK.DLL) in your Netscape directory.


0
harvey0Author Commented:
     Although I kept getting "timeout" notices in DOS Ping, I was able to WPING in WINOS2. I still do not know HOW to go about to get WINOS2 to use the WARP4 Winsock.dll. Please inform me.
      You've given me hope that this CAN work.
0
sbuftonCommented:
Good news, some progress!

OK, take a look in your Netscape directory. Can you find a
WINSOCK.DLL file there? I suspect that this file is from some
other product (Network TeleSystems), and is getting in the way
of the Warp WINSOCK.DLL. If you can find something like that,
try renaming it to WINSOCK.LLD and then starting Netscape.

      Steve
0
harvey0Author Commented:
Steve. Thank you. You solved my problem. Just as you suggested, I renamed the WINSOCK.DLL WINSOCK.LLD and I was able to use the WARP 4 IBM dial and open a working NETSCAPE in WINOS2.
      Thanks again,
      Harvey Goldenberg
0
sbuftonCommented:
Good! I'm glad I could help.

      Steve
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.