The new VNET gives you complete Windows IP based networking.
So Windows network printers just work. As does browsing
shares in you network neighborhood.
Your windows session needs it's own IP address for this, but
if your network uses DHCP it will use that. It is so easy.
You can also specify all the IP settings yourself if you
don't have DHCP.
You can also choose to use just the Winsock networking
as Win4Lin currently has and you don't have to worry
about IP issues, but it still has the same limitations.
-David
Slurp is not in 3.0. Serial support is the same as in 2.0.
James Bearden wrote:
>
> Folks,
>
> I'm just glad I will be able to run Win4Lin on a 2.4 kernel, and have real
> TCP/IP support to boot! I've also been with Win4Lin since 1.0, and I'm glad
> Netraverse has decided to concentrate their efforts on a few key features. I
> for one am happy to pay for a copy of Win4Lin 3.0 in order to help support
> their efforts. Am I telling you all this because I'm brown nosing in hopes on
> getting on the 3.0 beta team? Hell yes! But I also happen to think that way
> anyway.
>
> When a better feature list comes out, hopefully it will also include:
> * slurp support
> * better serial support (I never did get my PDA to sync with 2.0. And yes, I
> tried the damn baud rate thing.)
>
> I also have a question: Will I be able to use my Windows network printer
> (actually Samba/CUPS, but whatever) to print from Win4Lin 3.0?
>
> Later!
> --
> James D. Bearden
> [EMAIL PROTECTED]
> http://james.bearden.com/
> The impossible is relatively easy.
> The unfeasible is a sticky wicket.
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
