OK while I do _not_ pretend to have material that's awesome enough to make an OS/2 Museum article, or the talent of Michal to do spelunking within the darkness of days gone by, this is getting pretty interesting nevertheless.
My system boots. I suspect ae (e replacement, I hate it) to have garbled my config.sys the first time, which - *if* its indeed the case, led to the infamous country.sys trap error. Maybe it was an operator error as well. Anyway, I've had many problems with editing simple text files from the prompt using ae, so I decided to stick with tedit and epm and forget about e until I recover IBM's original one from my Warp 4 Advanced Server CDROM.
Enough ramblings. the findings:
First, PC/TCP 1.3.1 modifies the config.sys with new entries very early in the file.
I decided to move them closer to other IBMCOM and MPTN (MPTS, whatever) :
...snipped...
REM *** this next line was added to the config.sys in the original install.
SET HOSTNAME=ARCAOS
REM *** the line below was added by PC/FTP and I commented it out as it uses the old MS Protocol Manager.
REM DEVICE=d:\pctcp\drv\PROTMAN.OS2 /I:d:\pctcp\drv
REM *** I replaced it with IBM's PROTMAN. I do not know whether they can co-exist.
REM *** BTW, interestingly enough, protman was not in the config.sys already, perhaps because
REM *** I opted out from NetBIOS/NetBEUI?
DEVICE=D:\IBMCOM\PROTMAN.OS2 /I:D:\IBMCOM
REM *** This line corresponds to PC/TCP socket driver.
DEVICE=d:\pctcp\drv\SOCKET.OS2
REM *** This comment was added by PC/TCP installer. I moved it right before my
REM *** NIC driver to document the original message and what's my NDIS driver.
REM *** You must find what is your NIC corresponding NDIS device driver for your setup.
REM *** PUT THE NDIS DEVICE= STATEMENT HERE ***
DEVICE=D:\IBMCOM\MACS\E1000B.OS2
REM *** This is where the fun starts. This is the int 61h driver.
REM *** I'll post another message with additional findings
DEVICE=d:\pctcp\drv\INT61VDD.SYS
REM *** ... and it darkness, bind them :-)
REM *** At this point, everything else correspond to my original config.sys
CALL=D:\IBMCOM\PROTOCOL\NETBIND.EXE
<...snipped...>
Then the installer also add a script to the startup folder, the script invokes the following from pc/tcp folder.
netbind
tcpmgr start
There another script, called pctcp.cmd which starts, minimized the VDD_D daemon:
rem pctcp.cmd - starts up pctcp services
ifconfig lo0 localhost
hostname arcaos.local
minstart VDD_D
Finally, the default autoexec.bat receives the following new entry:
D:\PCTCP\BIN\INST61
And _that_ is what loads the int 61h handler in every VDM instance.
-=-=-=-=-=-=-=-=-=
The install process also tell about modifying the protocol.ini file.... yay..... Since I'm using IBM's protocol manager, I left PCTCP protocol.ini untouched and updated \IBMCOM\protocol.ini instead. I copied the snipped to be filled from PCTCP's protocol.ini, though.
[PROT_MAN]
DRIVERNAME = PROTMAN$
[IBMLXCFG]
TCPIP_NIF = TCPIP.NIF
E1000B_NIF = E1000B.NIF
[TCPIP_NIF]
DriverName = TCPIP$
Bindings = E1000B_NIF
[E1000B_NIF]
DriverName = E1000B$
;FTP Software --- PCTCP Section -------
[SOCKET]
drivername = $SOCKET
; The next line was unfilled, I've manually added E1000B$ to bind $SOCKET with E1000B$
bindings= E1000B$
;----------------------------------
Does it work? Hell no :-) Even PCTCP software doesn't work _but_ it could be a configuration thing. I went fast in itsinstall process. The IBM TCP stack still works, I'm typing this from Firefox under ArcaOS 5.1
Oh, and I get a trap error on shutdown in the int61vdd ever since. Very annoying.
Next post will cover my findings wrt int 61h.