1. The stack is always there, but it gets bypassed if your CommDb is
specified to use the winsock driver. Any of the other main transports will
use the tcpip stack - ie ethernet/NTRAS etc.
2. You say
"Whoever decided to put the WSOCK.PRT into SDK for emulator should have
at least put a BIG WARNING SIGN on the SDK readme/release notes, and
also provided clear instructions to re-enable the real stack."
Couldn't agree more - I have already raise this with Nokia to no avail.
Please complain to Forum Nokia - its their SDK. I believe this decision was
ill-considered. Currently they do not intend to do anything about this, but
the intention is that they will update to Symbian's WinTap solution in a
release or two.
3. The beta SDK is gone from Forum Nokia.
I don't know how to configure the current SDK to use a valid transport. My
suggestion would be to use WinTap (because its less problematic than
ethernet). I have not tried this personally.
"Markku Savela" <firstname.lastname@example.org> wrote in message
> Marko Saukko <email@example.com> writes:
> > I dont really know how to check if I'm linking to replacement library
> > not. Anyway this is what I found out with those filenames you gave
> > wsock.ptr and tcpip6.ptr are in here Epoc32\release\winscw\udeb\
> > ip.tcpip.esk in Epoc32\winscw\c\private\101f7989\esock points to
> > wsock.prt and ip.tcpip.esk in Epoc32\Data\z\private\101f7989\esock
> > points to tcpip6.prt.
> > I tried to replace ip.tcpip.esk in c with one in z (this is in the
> > phones ROM so it is the orginal version?) but that didn't help.
> That should have worked, assuming you removed totally the ESK file
> referring to the WSOCK.PRT (or just rename the extension to something
> else than ESK).
> > So how can I get real stack reinstalled?
> Stack is apparently installed, its just not activated due to different
> ESK file configurations.
> Whoever decided to put the WSOCK.PRT into SDK for emulator should have
> at least put a BIG WARNING SIGN on the SDK readme/release notes, and
> also provided clear instructions to re-enable the real stack.
> This WSOCK.PRT apparently only support very minimal subset of the internet
> socket api of the real stack (support only IPv4 TCP! No UDP! ...)