The MicroWeb DOS web browser

[Martin Iturbide]

Hi

I found this file on hobbes: https://hobbes.nmsu.edu/download/pub/os2/dev/info/tcpdos.zip
It has some LIB files, but I'm trying to find the .H files for the mTCP developer to try to make it work on OS/2 DOS VDM.

It is missing is the header files in the TCP/IP for DOS software development kit.

If someone has the those file, please let me know.

Regards

[Martin Iturbide]

Hi

Gotta hint from this file: pgmgc1.zip

The readme says:

Code: [Select]

The latest CSDs for TCP/IP Version 2.0 for OS/2 are shown
  in the following table:

  +----------------------------+---------------------------+
  | KIT NAME                   | PACKAGE NAME              |
  +----------------------------+---------------------------+
  | Applications Kit           | APP20CSD.PKG              |
  +----------------------------+---------------------------+
  | Base Kit                   | TCP20CSD.PKG              |
  +----------------------------+---------------------------+
  | Domain Name Server Kit     | DNS20CSD.PKG              |
  +----------------------------+---------------------------+
  | DOS/Windows Access Kit     | DOS20CSD.PKG              |  <----
  +----------------------------+---------------------------+
  | Extended Networking Kit    | XNT20CSD.PKG              |
  +----------------------------+---------------------------+
  | Network File System Kit    | NFS20CSD.PKG              |
  +----------------------------+---------------------------+
  | OSF/Motif Kit              | MOT20CSD.PKG              |
  +----------------------------+---------------------------+
  | Programmer's Toolkit       | PGM20CSD.PKG              |
  +----------------------------+---------------------------+
  | X Window System Client Kit | XCL20CSD.PKG              |
  +----------------------------+---------------------------+
  | X Window System Server Kit | PMX20CSD.PKG              |
  +----------------------------+---------------------------+

I checked inside this ISO:  OS/2 Master 5/94. It has "DOS20CSD.PKG".

How can I upack it to see if has some .h files for the DOS TCP/IP I'm looking for?

Regards

[Tom]

Hi

Gotta hint from this file: pgmgc1.zip

The readme says:

Code: [Select]

The latest CSDs for TCP/IP Version 2.0 for OS/2 are shown
  in the following table:

  +----------------------------+---------------------------+
  | KIT NAME                   | PACKAGE NAME              |
  +----------------------------+---------------------------+
  | Applications Kit           | APP20CSD.PKG              |
  +----------------------------+---------------------------+
  | Base Kit                   | TCP20CSD.PKG              |
  +----------------------------+---------------------------+
  | Domain Name Server Kit     | DNS20CSD.PKG              |
  +----------------------------+---------------------------+
  | DOS/Windows Access Kit     | DOS20CSD.PKG              |  <----
  +----------------------------+---------------------------+
  | Extended Networking Kit    | XNT20CSD.PKG              |
  +----------------------------+---------------------------+
  | Network File System Kit    | NFS20CSD.PKG              |
  +----------------------------+---------------------------+
  | OSF/Motif Kit              | MOT20CSD.PKG              |
  +----------------------------+---------------------------+
  | Programmer's Toolkit       | PGM20CSD.PKG              |
  +----------------------------+---------------------------+
  | X Window System Client Kit | XCL20CSD.PKG              |
  +----------------------------+---------------------------+
  | X Window System Server Kit | PMX20CSD.PKG              |
  +----------------------------+---------------------------+

I checked inside this ISO:  OS/2 Master 5/94. It has "DOS20CSD.PKG".

How can I upack it to see if has some .h files for the DOS TCP/IP I'm looking for?

Regards

DOS20CSD.PKG is a textfile, with the following contents:

Code: [Select]

**********************  IBM Internal Use Only  *************************
* :nick.DOS20CSD   :sec.IBM Internal Use Only         :disk.OS2CSD
* :title.CSD UN50383, DBOX Kit TCP/IP 2.0 for OS.2
* :version.2.0     :date.94/01/06   :CSD.PTF UN50383  :support.
* :oname.TCP/IP Development         :onode.RALVM12    :ouser.OS2TCPIP
* :aname.John Gunther               :anode.RALVM12    :auser.OS2TCPIP
* :ops.OS/2 2.0+
* :doc.DOSCSD.DOC
* :abs.Fixes for the DBOX Kit for TCP/IP 2.0.  The
* diskette image files are in PKZIP self-extracting format.  The files
* contained in this package can be distributed to IBM customers who
* are licensed owners of TCP/IP 2.0 DBOX Kit.
***********************************************************************+
*
      DBOX20C1  EXEBIN   *
*
*  Download then execute "DBOX20C1 -d" to a diskette.
*  You Must use the -d option when creating the diskette.
*  This will put the following files on the diskette:
*             DOSCSD.DOC
*             DBOXC1.ZIP
*             DBOXXT.EXE
*             TCPINST.EXE
*             TCPINST.HLP
*             TCPINST2.EXE
*             DEFAULT.RSP
*             UNZIP.DLL
*               \lanlk\      (4 files)
*
*  Insert diskette one and enter TCPINST to install the CSD.
***********************************************************************


[Martin Iturbide]

Thanks Tom

I think it was a mislead. Seems that those files (DBOX20C1.EXE and DBOXC1.ZIP) does not has the .h files of the IBM DOS TCP/IP Toolkit I'm looking for.

I need to keep looking for those.

Regards

[Martin Iturbide]

Hi

I wanted to give it one more try to see if I can find some things the author of mTCP asked me, so it can turn mTCP also DOS VDM compatible.

I sent him the "TCP/IP ver 2.1 for OS/2's DOS BOX: Programmer's Reference (1998-06-03)" that we found on hobbes and he answer me:

He asked me last time:

The short story is that it looks like almost everything that somebody needs to write a TCP/IP porgram in DOS that runs under OS/2 is there:

    Documentation
    Static libraries to link against for small, medium and large memory models

What is missing is the header files in the TCP/IP for DOS software development kit. If you find that piece of software, the rest is fairly easy.  (A quick search shows that it's not going to be obvious, but maybe somebody squirreled it away?)

Any help on finding the header files for TCP/IP for DOS SDK will be awesome.

Regards

[Dave Yeo]

Wonder about the 1.x versions of TCPIP, https://winworldpc.com/product/ibm-tcp-ip-for-os-2/1x, I'm not set up for the disk images.

[Martin Iturbide]

Hi Dave.

Thanks for the pointer. I wonder if there is a way to know the names of the .h files that I'm looking for.

I got "IBM TCP-IP 1.2.1 for OS2 (3.5)" and it has some .h files on disk #3. It has db.h, font.h, kbd.h, msgs.h, nameser.h, ns.h, nstat.h and tmp.h. But I'm not sure if those are for DOS or just for OS/2. Also, I guess the installer does something to those files, since are not txt files.

Regards

[Martin Iturbide]

Hi

I also found this documentation on the internet.

IBM's TCP/IP stack For DOS can be found in the QIWSTOOLS folder on the
AS/400. What's actually there are diskette images. You need to use the
LOADDSKF.EXE program on these files: S1.DSK, D1.DSK and D2.DSK to load the
images onto diskette, then run the INSTALL program from the S1 disk.

Here's the TCPIP.DOC file from the QIWSTOOLS folder:

The QIWSTOOL folder contains the install diskettes for the
IBM TCP/IP Version 2.1.1 for DOS

Maybe if I can find some old AS/400 client access tool. Not sure yet.

Regards

[Martin Iturbide]

Hi

I think I found something at:
http://greyghost.mooo.com/pccBBS/tcpip/tcpv21cp.exe

tcpv21cp.exe TCP/IP v 2.1 Programmer's toolkit CSD
    (1054355 bytes, 10-21-93)

I'm checking how to unscrable the .H_# files. Suggestions?

- Source
- Files

Regards

[Alfredo Fernández Díaz]

[...]tcpv21cp.exe TCP/IP v 2.1 Programmer's toolkit CSD
    (1054355 bytes, 10-21-93)

I'm checking how to unscrable the .H_# files. Suggestions?

Having a look at the TCPCSD.BAT inside tcpv21cp.exe, you'll find that it wants to process them using something called "decomp.exe", located in %ETC%\..\BIN (?:\TCPIP\BIN, one would guess). That is not present on MCP2/AOS systems, so I would guess it is yet another relic, er... custom [un]packer from the TCPIP 2.1 days, presumably to be found on ancient enough systems.

[Martin Iturbide]

Hi

I found decomp.exe 3.0 on a PCOM package, but it gives me some issues trying to decomp the files.

[C:\pcomos2]decomp c:\desktop\1\types.h_# c:\desktop\1\types.h
Message file not found.
Message file not found.
Message file not found.
Message file not found.
Message file not found.
Message file not found.
Message file not found.
Message file not found.

At the end types.h turns out as an empty text file.

Regards

[Dave Yeo]

I found the same, it is the wrong decomp.exe. Since it is a bat file that calls it, it must be a DOS program.

[Martin Iturbide]

No luck yet with this ones.

[Dave Yeo]

Yea, I hunted around a bit, seems to be a few decomp.exe programs out there but none the correct one. Even Googling the file signature came up empty. File just says data and it is pretty good at figuring out file types.
It seems the correct decomp.exe came with the original DOS tcpip package and the one we're looking at is a fixpak.

[SoundChaser]

I' ve been hunting this SDK for a while and I'm happy to report that I've managed to install the long-forgotten TCPDOS 2.1.2 + Base CSP + Prog CSP. Oh yes indeed.

Installing the Prog CSP required some tinkering with the provided batch file - as elaborated this thing is, it failed to install the Prog CSP when I tried it. And kept failing for sufficiently iterations that I got annoyed and debugged the damn file.

The recipe:

1. On the installation media of IBM OS/2 LAN Server 4.0 Advanced from 1994, look for a TCPDOS folder. There's a BASE folder from where you can do a network install (faster than the tedious floppy image fun). Install the thing to a TCPDOS folder. Lo' and behol' - decomp.exe in under \bin.

2. Download the CSP files and install Base 1 and 2, then.... toy around with the prog csd. I _think_ the failing part was the few lines where it tries to create the folders. Somehow they were not created and decomp failed to extract.

I've attached the extracted files from the prog CSD and the precious decomp.exe for your pleasure.

I'm really looking forward to see if he (mTCP author) can make his sockets library talk to VDOSTCP through those libraries! I'll gladly assist!