![top](top.jpg)
![<-](prev.jpg) A.2. What's this about a Win95NetBugs email list?
Date: Wed, 27 Dec 95 14:44:00 -0800
From: Rich Graves <win95netbugs-owner@lists.stanford.edu>
win95netbugs@lists.stanford.edu is an unmoderated
electronic mail discussion list for the purpose of sharing information
and, hopefully, solutions to the networking bugs and "missing features"
in Microsoft Windows 4.x.
It is intended as a relatively low-traffic list for
network managers who know from whence they speak. I don't want any basic
setup questions. We are cooperatively maintaing this FAQ.
If you don't need any more mail littering your inbox,
perhaps we could interest you in the archive of all messages posted to
win95netbugs on gopher://quixote.stanford.edu.
Currently the path is 1m/win95netbugs,
but this is likely to change to separate directories for each month Real
Soon Now.
Currently, there is no digest option, but this is
expected to become available "soon." See above for a suggested
workaround.
The list is managed automatically by a majordomo
list server. To subscribe to the list, send the command "subscribe
win95netbugs" in the body of an electronic mail message
to majordomo@lists.stanford.edu.
Do not include your real name or email in the body of the message; it will
be extracted from the From: header. This is important because
if the From: header of subsequent messages don't match, they will
be bounced to the list moderator.
For more information, email win95netbugs-request@lists.stanford.edu.
Please read the preceding four paragraphs again before
inquiring about or asking to join the list.
Messages sent to the list by non-subscribers will
be discarded.
All messages to the list are archived, redistributed
on a gopher server, and physically become the property of Stanford University
and other recipients, though you retain other rights associated with copyright.
Subscriptions from anonymous remailers are very welcome.
The majordomo we're using does not honor the "who" command. Subscriptions
from local mailing lists are not welcome, because of the feedback
errors this can generate.
![top](top.jpg)
![<-](prev.jpg) A.3. What related resources are available?
Date: Mon, 22 Jan 96 20:00:00 -0800
From: Rich Graves <win95netbugs-owner@lists.stanford.edu>
The "official" Microsoft Windows FAQ suite
is maintained by tomh@metrics.com (Tom Haapanen). Information on getting
the various Windows FAQs is posted to comp.os.ms-windows.announce on a
weekly basis. The offical FTP archives for the Windows FAQs are:
ftp://ftp.nimh.nih.gov/pub/win3/FAQ/
ftp://wuarchive.wustl.edu/usenet/comp.binaries.ms-windows/faqs/
ftp://ftp.metrics.com/faq/
More pertinent, up-to-date, and useful resources
are also available on the Net. There's far too many to list. Just see Yahoo's
Windows Page. Of special interest might be the official www.windows.microsoft.com.
Unfortunately, at this writing, all of the Win95
networking resources listed in Yahoo, with the exception of this one :-),
are SLIP/PPP guides written by nontechnical people. If you have a good
guide, please list it in Yahoo and
other directories and send
me a note.
For technical information on PC TCP/IP networking,
notably some free/shareware SLIP/PPP servers and IP gateways, see Bernard
Aboba's excellent FAQ for the comp.protocols.tcp-ip
newsgroup, which you can get from:
ftp://ftp.netcom.com/pub/ma/mailcom/IBMTCP/ibmtcp.zip
http://www.zilker.net/users/internaut/update.html
Another useful page from the loyal opposition (David
really likes Win95) is Windows95
Annoyances, http://www.creativelement.com/win95ann/.
Microsoft publishes selected known problems and workarounds
in the Microsoft Knowledge Base,
http://www.microsoft.com/kb/. The keywords "kbnetwork," "3rdPartyNet,"
and "win95" are useful to know. Another useful search is "network
not kbnetwork," which returns several interesting files. Shows attention
to detail in indexing.
There are some other
random, unindexed files in this directory. Especially get the new.txt
spool of stuff that should probably be added to the FAQ, but which
I haven't had time for. Write up an appropriate FAQ question and answer,
and see your name here.
Finally, those with a technical bent should take
a look at Kent Daniel Bentkowski's Registry FAQ, so that you can help him
fix it up and find a real (non-AOL) home for it. This potentially useful
document is, unfortunatey, homeless at this time, but anyone with sufficient
interest should have no trouble finding it.
| |