Microsoft TCP/IP-32 (Wolverine) FAQ  
(updated 6/11/94)

Q: How can I get support for the Wolverine beta?

A: The official source for Wolverine support is CompuServe, MSNET forum 
section #15. You can post bugs to library #15 of the same forum, or e-mail 
them directly to wolvrine@microsoft.com. More detail can be found in the 
Release Notes, which can be found in the Microsoft TCP/IP-32 program group.

Q: I've sent in bugs, but I don't get back any response!

A: If your bug was not a duplicate, we filed it in Redmond and are looking 
into it. Unfortunately, due to the overwhelming scale of the beta (over 
25,000 users have downloaded it), it is impossible for us to provide personal 
responses to your bugs. If you filed a major bug, it should be resolved in 
the next beta release (consider this your response). If your bug persists 
in beta 3, please repost your bug to CompuServe, or e-mail it to 
wolvrine@microsoft.com as soon as you can. We'll work on fixing it before 
final release. Remember, the better the bug description, the more likely it 
is we'll be able to reproduce and fix it.

Q: How will Wolverine be distributed?

A: The retail packaging plans have not been completely finalized. However, 
we do plan use the Internet and CompuServe to distribute the Microsoft 
TCP/IP-32 product as we have in the past with our TCP/IP products with a 
free license agreement for our Windows for Workgroups 3.11 customers. A 
retail site license package with printed documentation will be made available 
as well.

Q: Where can I get answers to my programming questions?

A: The supported programming API on Wolverine is Windows Sockets 1.1. 
Windows Sockets is an open specification supported by most Windows TCP/IP 
vendors. Unfortunately the CompuServe MSNET forum cannot provide support 
for any elaborate programming questions. There are some resources you can 
use for help. On CompuServe, the specification is available in the MSNET 
forum, library 15, along with some sample code, etc.. to get you started.  

If you have access to the Internet, there are a number of resources for you 
to take advantage of. The specification can be found on 
<ftp://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock>. There is a 
Windows Sockets FAQ available which you can receive by mailing 
lcsinfo@indirect.com with a subject: line reading FAQ (the body of the 
message will be ignored). For example:

	To:  lcsinfo@indirect.unc.edu
	Subject:  FAQ

The official mailing list is winsock@sunsite.unc.edu to subscribe, e-mail 
listserve@sunsite.unc.edu with the Subject: subscribe winsock <email address>.

	To:  listserve@sunsite.unc.edu
	Subject:  subscribe winsock jallard@microsoft.com

The mailing list is also cross-posted to alt.winsock for UseNet users.

Q: My Windows Sockets application used to work on my other TCP/IP stack, but 
it doen't work under Wolverine.

A: Most Windows Sockets applications work fine under the Wolverine 
(Daytona beta) release. We've tried to test with all of the major 
applications, but it's possible that we haven't tested yours. Be sure 
to file a very detailed bug report, including the name and version number 
of your application, along with information on where it can be acquired so 
that we can reproduce the problem and fix it. If it's an application 
that you've written, please include the problematic code fragment so that 
we can diagnose it.

Q: How does Wolverine's performance compare to other stacks?

A: Very well. You should notice the same, or slightly better performance 
relative to other stacks when running natively over enhanced mode NDIS 
drivers. Running over ODI drivers requires a translation layer, or shim 
which will degrade the stack's performance. Run Wolverine over enhanced 
mode drivers whenever possible.

Q: Why doesn't Mosiac work with this beta?

A: The only versions of Mosaic which don't work with Wolverine are 
alpha 3 and greater. Mosaic recently was moved to Win32s, and there 
are some memory locking issues between Mosaic, Win32S and the VxD. 
There is a patch available that includes a temporary fix for windows 
sockets win32s problems with some tcp/ip implementations such as 
microsoft tcp/ip-32. The fix can be applied to Win32s v1.15 (available 
from <ftp://ftp.microsoft.com//developer/DEVTOOLS/WIN32SDK/win32s115.zip>). 
This patch will be rolled into the next release of win32s which will be 
found in the same location. The patch is currently located in PATCH.EXE 
which can be found on 
<ftp://ftp.microsoft.com//peropsys/wfw/tcpip/vxdbeta/patches.exe>

Q: What about server-side applications for Telnet and FTP?

A: This release is focused on providing high-performance VxD transport 
functionality. Since the stack supports the Windows Sockets API, public 
domain and commercial Windows Sockets applications are compatible with 
this product.

Q: What about other utilities like lpr and gopher?

A: Again, Windows Sockets compatible applications are available to meet 
your needs, many in the public domain. The two most popular Internet sites 
with public-domain Windows Sockets applications are:
	<ftp://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps>
	<ftp://ftp.cica.indiana.edu/pub/pc/win3/winsock>

Q: Where is the list of system.ini settings?

A: A complete list of system.ini settings is included in Beta 3's online help. 

Q: Will there be a DOS interface to the stack? 

A: No, the supported interface to the stack is Windows Sockets 1.1. The 
real-mode Microsoft TCP/IP stack supports a DOS interface 
<ftp://ftp.microsoft.com/advsys/msclient/wfw/wfwtcp.exe>.

Q: I need SLIP and PPP to dial in to the Internet!

A: Dialup functionality is not planned for the Wolverine release. We have 
received extensive demand for these features, but do not want to delay the 
release of the LAN product further. Microsoft is committed to providing great 
Internet-ready operating systems - the next release of Windows Chicago and 
Windows NT Daytona will include this dialup functionality. We will investigate 
the possibility of providing this functionality prior to Chicago
with Wolverine.

Q: How do I get NFS support for Wolverine?

A: NFS support is not planned for this product release. A number of third
 parties have expressed interest in developing NFS support for the Microsoft 
TCP/IP-32 stack. It's not possible for us to comment on their intentions or 
schedules, but we hope you'll see third-party NFS functionality delivered 
by year-end '94.

