In message <[EMAIL PROTECTED]
m>, Particle Man <[EMAIL PROTECTED]> writes
>> > 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?
>
>
>
>> >And I saw somewhere that it's possible to get a full-screen session?
>
>From Larry Marshall:
>
>> Adjust your max window size by adjusting the screen resolution of your
>> emulation within Windows.
>
>Right, but shat about a full-screen that is not windowed under X?
>
>
>-Particle
>
my recollection ( and I had a hand in writing the first version of
wine's icmp dll) is that ping and M$ icmp call undocumented features of
the M$ winsock in the routine wsControl. It would be easier to rebuild
icmp.dll from scratch (at least that's what we concluded in wine) rather
than try and fathom what Bill's men had carefully hidden...
Bob
--
robert w hall
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
