Particle Man wrote:
> > > Running a command such as ping or tracert returns "Cannot load ICMP.dll"
> > > whether or not I'm online with DUN.
> > >
> >
> > Hi! Since ping isn't a Winsock 1-1 compliant program, it's not installed
> > when Windows installs under Win4Lin. Both ping and traceroute work
> > marvelously
> > under Linux - we suggest using those utilities there instead.
>
> Actually, ping is installed.
>
> # ll win/windows/ping.exe
> -rw-r--r-- 1 particle wheel 28672 May 11 1998 win/windows/ping.exe
>
> # ll win/windows/tracert.exe
> -rw-r--r-- 1 particle wheel 20480 May 11 1998 win/windows/tracert.exe
>
> I understand the superiority of Linux, however, this "undocumented feature"
> of ICMP.dll not loading seems to relate to DNS queries failing.
> Thus, when DUP connects successfully, network apps do not work.
>
> Is it possible to direct networking through ipchains--when Win4Lin doesn't
> detect or install a NIC device?
>
Networking should be transparent, and not needing any set-up. Win4Lin supports
Winsock 1-1 compliant net applications. Thus, if Linux is connected to the
internet, things like web browsers, ftp and telnet should work without further
networking configuration under Windows. Windows doesn't have direct hardware access
to any of the networking hardware, thus it will never see the NIC or the modem.
There may be
ways other users have found to gain modem support under Win4Lin, but we do not
install any of the Dial-Up Networking applications because we do not support modem
access under Win4Lin. Networking should be handled by the Linux layer. So long as
the application is Winsock-compliant, it should work.
Regards,
Amanda Owens
Support Engineer
NeTraverse, Inc.
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
