Hello Arachnoids
About a couple years ago I downloaded Webspyder 2.1b2 and tried to test it
to see how it worked but I couldn't make it dial a number so it stayed
in my HD just occupying space.
Recently I was curious to see how it established a DOS network connection
and noticed that it uses Novell ODI drivers.
Two things called my attention:
1) one of the 4 files loaded LSL.COM has the same name as one used in
the KLOS packet drivers which is sort of an alternative to DOSPPPD.
2) It uses a pkt2odi.exe which is called a shim for transforming
one protocol into another, in this case ODI into packets same as epppd.
So I figured that if I could find a way of finding the the IP number
and stick it into the wattcp.cfg file I could run any DOS wattcp
application including Arachne.
I found a way and it turned out to be much easier than expected.
These Novell Caldera ODI ? drivers are similar to Klos but they are
better in several aspects.
1) they are smaller than Klos. ( it seems that all files loaded take a
little less space than what pppd takes) and also as they are small
files they will be easier to load high when compared to a big chunk
like epppd 70K.
2) They can be scripted (automated). In the case of Klos I always
needed to press keys to get connected (in PPPMENU.EXE) .
Below is a comparison of upper memory usage.
A) DOSPPPD
Modulos usando memoria abaixo de 1 MB:
Nome Total Convencional Memoria Sup.
-------- ---------------- ---------------- ----------------
SYSTEM 18,832 (18K) 9,472 (9K) 9,360 (9K)
HIMEM 1,168 (1K) 1,168 (1K) 0 (0K)
EMM386 4,192 (4K) 4,192 (4K) 0 (0K)
COMMAND 7,632 (7K) 80 (0K) 7,552 (7K)
COMMAND 7,424 (7K) 64 (0K) 7,360 (7K)
COMMAND 8,416 (8K) 1,056 (1K) 7,360 (7K)
MOUSE 18,688 (18K) 0 (0K) 18,688 (18K)
IFSHLP 2,864 (3K) 0 (0K) 2,864 (3K)
SETVER 832 (1K) 0 (0K) 832 (1K)
SMARTDRV 27,520 (27K) 0 (0K) 27,520 (27K)
PPPD 69,008 (67K) 0 (0K) 69,008 (67K) pppd
Livre 679,104 (663K) 638,736 (624K) 40,368 (39K)
Resumo da Memoria:
Tipo de Memoria Total Usado Livre
---------------- ----------- ----------- -----------
Convencional 655,360 16,624 638,736
Superior 190,912 150,544 40,368
Reservado 393,216 393,216 0
Estendida (XMS) 7,149,120 1,279,552 5,869,568
---------------- ----------- ----------- -----------
Total de memoria 8,388,608 1,839,936 6,548,672
Total menor que 846,272 167,168 679,104
Maior programa executavel 638,720 (624K)
Maior bl. memoria superior livre 35,824 (35K)
MS-DOS esta residente na area de memoria alta.
B) Odi drivers
Modulos usando memoria abaixo de 1 MB:
Nome Total Convencional Memoria Sup.
-------- ---------------- ---------------- ----------------
SYSTEM 18,832 (18K) 9,472 (9K) 9,360 (9K)
HIMEM 1,168 (1K) 1,168 (1K) 0 (0K)
EMM386 4,192 (4K) 4,192 (4K) 0 (0K)
COMMAND 7,632 (7K) 80 (0K) 7,552 (7K)
COMMAND 7,440 (7K) 80 (0K) 7,360 (7K)
COMMAND 8,416 (8K) 1,056 (1K) 7,360 (7K)
MOUSE 18,688 (18K) 0 (0K) 18,688 (18K)
PKT2ODI 3,056 (3K) 0 (0K) 3,056 (3K) odi
IFSHLP 2,864 (3K) 0 (0K) 2,864 (3K)
SETVER 832 (1K) 0 (0K) 832 (1K)
SMARTDRV 27,520 (27K) 0 (0K) 27,520 (27K)
LSL 26,784 (26K) 0 (0K) 26,784 (26K) odi
NCOMX 10,576 (10K) 0 (0K) 10,576 (10K) odi
NWREMOTE 22,784 (22K) 0 (0K) 22,784 (22K) odi
Livre free 684,976 (669K) 638,800 (624K) 46,176 (45K)
Resumo da Memoria:
Tipo de Memoria Total Usado Livre
---------------- ----------- ----------- -----------
Convencional 655,360 16,560 638,800
Superior 190,912 144,736 46,176
Reservado 393,216 393,216 0
Estendida (XMS) 7,149,120 1,279,552 5,869,568
---------------- ----------- ----------- -----------
Total de memoria 8,388,608 1,834,064 6,554,544
Total menor que 846,272 161,296 684,976
Maior programa executavel 638,784 (624K)
Maior bl. memoria superior livre 42,160 (41K)
MS-DOS esta residente na area de memoria alta.
As you see I get a decent 624K conventional memory just for Arachne
in both cases but ODI uses 61k in 4 pieces as compared to to pppd 67k
in 1 piece so ODI should be easier to load high for most people.
Note: you can test if your packet loaded high by going
Alt-E
mem /c | more
(see the screen)
exit
when Arachne is running and connected.
Here is an example on how to use ODI driver :
Batch file
@ECHO OFF
LH LSL (Needs file NET.CFG in same directory)
LH NCOMX
LH NWREMOTE
LH PKT2ODI /B:1
DIALER C:\dir\subdir\DIAL.CFG
FIND "My_ip =" C:\dir\subdir\WEB32.CFG | SORT >> C:\ELIANE2\WATTCP.CFG
ARACHNE (Connection READY) {or any other DOS wattcp app.}
@ECHO OFF
PKT2ODI /U
NWREMOTE U
NCOMX U
LSL /U
As you see 3 .cfg files are needed.
NET.CFG
Link driver NCOMX
INT 10
PORT 2E8
Link Support
Buffers 8 1504
MemPool 8192
You can modify it yourself by changing the port and irq or let setup for
Webspyder do this for you.
DIAL.CFG and WEB32.CFG Here is the inconvenient part. You will need to
install Webspyder CORE.EXE to go through the menus and generate the
encrypted password that DIAL.CFG and WEB32.CFG use. But once you generated
your login data you don't need Webspyder CORE.EXE any further.
DIALER.EXE will take care of decrypting the password and doing the PAP
login. If you don't use PAP login then you will need file DIAL.SCP (I haven
't tried it myself) similar to Microsoft Windows DialUp Network scripts.
DIALER.EXE has similar functions as PPPMENU and PPPWAT in Klos and it does
not stay resident.
Make sure the line Update_file = in DIAL.CFG points to the proper address
of WEB32.CFG, otherwise will not work.
DIAL.CFG
[Modem]
Update_file = angel@ts\web32.cfg
PhoneNumber = 50851000
Password = ez +|stlgR+o^+NS+pib SigmaX!{osqrt,D+\u oj?.<=ae C+{xaee ++iyp*
^+stlgK|+A$u={ae?-a~cwM----N|stlgyenee +q\}yen?`+7 |{+8oWBsy+A>>+=wu.25
^nsqrt.sqrt-florinWm.25c] +e7+uOmegaAQ":?d|wC><=c51+| +|-(h?++-
Username = [EMAIL PROTECTED]
Init2=
Init1 = ats95=47
DialTone=ATDT
Scriptfile=dial.scp
LinkProtocol=PAP
DisconnectTime=5
AutoReConnect=Yes
BaudRate=115200
The line FIND.... in batch file
FIND "My_ip =" C:\dir\subdir\WEB32.CFG | SORT >> C:\ELIANE2\WATTCP.CFG
actually finds a line similar to "My_ip = 200.245.253.002" in WEB32.CFG
and adds it to WATTCP.CFG which is all I actually added to make it work.
Also ODI seems to offer support for several models of network cards.
(I haven't tested).
Conclusion:
ODI drivers seem to be a viable alternative to DOSPPPD for running
DOS internet apps. I installed them in a P166 and on a 486 DX2 66 and
both run equally good.
As of now ,I can say ODI and DOSPPPD both run great.
So far ODI never failed on me. (PAP logins only) as opposed to DOSPPPD
which fails to login 10% of the time (non PAP logins).
Also ODI gives you info on DNS servers.
Happy DOS networking !
Regards
Luis Loeff
