Solved

TCPIP Dos/Winos2 Functionality

Posted on 1997-08-22
9
769 Views
Last Modified: 2013-12-27
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?
0
Comment
Question by:harvey0
  • 5
  • 4
9 Comments
 
LVL 1

Accepted Solution

by:
sbufton earned 60 total points
ID: 1806653
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
 

Author Comment

by:harvey0
ID: 1806654
     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
 
LVL 1

Expert Comment

by:sbufton
ID: 1806655
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
 

Author Comment

by:harvey0
ID: 1806656
     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
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 
LVL 1

Expert Comment

by:sbufton
ID: 1806657
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
 

Author Comment

by:harvey0
ID: 1806658
     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
 
LVL 1

Expert Comment

by:sbufton
ID: 1806659
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
 

Author Comment

by:harvey0
ID: 1806660
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
 
LVL 1

Expert Comment

by:sbufton
ID: 1806661
Good! I'm glad I could help.

      Steve
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

I use more than 1 computer in my office for various reasons. Multiple keyboards and mice take up more than just extra space, they make working a little more complicated. Using one mouse and keyboard for all of my computers makes life easier. This co…
The article will include the best Data Recovery Tools along with their Features, Capabilities, and their Download Links. Hope you’ll enjoy it and will choose the one as required by you.
This video shows how use content aware, what it’s used for, and when to use it over other tools.
Using Adobe Premiere Pro, the viewer will learn how to set up a sequence with proper settings, importing pictures, rendering, and exporting the finished product.

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now