MO> Quickly reading the readme.os2 within it, I notice the
 MO> following:

 MO>       modification of res_init.c to read %ETC%\resolv instead of the
 MO>     UNIX default /etc/resolv.conf.

 MO> I have no "resolv" files except in \TCPIP\DOS\ETC - all in
 MO> the %etc% path [\mptn\etc] are "resolv2.*"
 MO> Does that make any difference or is the documentation way out
 MO> of date.

i just participated in a discussion on resolv and resolv2 in another area
within the last few weeks... the concensus seemed to be to copy resolv2 to
resolv and to either adjust your DOS VDM etc variable to point to the same
place as the OS/2 config.sys setting or to copy the files from the OS/2 etc
location to the DOS VDM etc location... this would be done in a script
after the connection is made...

no one could come up with a valid explanation as to why IBM decided to go
with resolv2 for OS/2 native TCP/IP apps when the rest of the world was
using resolv... additionally, no one could come up with a valid explanation
as to why IBM decided to keep the DOS etc variable pointing somewhere else
instead of to the "main" etc area...

)\/(ark