I recently had to do a reinstall of my Win4Lin image (with
the 3.0.5 base). I specified "v" (for VNET rather than
Winsock) during the setup. Later, when I started running,
I discovered that I could access Network Neighborhood and
any local machine, but no remote machine.
I then tried:
win_network -w (replace VNET by Winsock)
win_network -v (replace Winsock by VNET)
and indeed I could then talk to the rest of the world. In
other words, the bug shows up if you install VNET initially
but not if you install Winsock initially and then replace
Winsock by VNET.
I've reported this one to Netraverse and they've
acknowledged it, but I figured that the rest of the folks on
this list might like to know about it.
Paul
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
