The traffic on comp.os.ms-windows.win95.misc is ridiculous. Other
   Win95 FAQs I read were too sparse, too technical, too anti-Microsoft,
   or otherwise too un-useful for the common folk. Also, Microsoft's FAQ,
   which shipped with the CD-ROM version, was pathetic. But ultimately, I
   wrote it for the experience, so I can say, "Hey, I made a Web page!" I
   hope this page is useful to you out there.
   
   This FAQ tries to get the big questions answered while going into some
   technical detail for those who want to learn more. Where content goes
   beyond the scope of this FAQ, I link you to appropriate sites.
   
     * 1.3.1. Why did you cross-post this FAQ to all the .win95
       newsgroups? 
       
   Because I was asked to. One of the initial letters I received in
   response to the FAQ was to have me post it in the FAQ archives for
   news.answers, so non-WWW people could use it. And not everyone has FTP
   either; people using the Vancouver CommunityNet have no FTP access
   at all! To get in the archives I had to actually post it to, not only
   news.answers and comp.answers, but the groups directly concerned with
   the questions in the FAQ. I wouldn't have received approval from
   rtfm.mit.edu to cross-post if I wasn't supposed to.
   
   Cross-posting also takes less disk space on news servers than
   multi-posting. In a cross-posted article you have only one message ID
   (and only one file). Cross-posting the FAQ to the groups in question,
   as well to news.answers, takes the same bandwidth as a single posting
   to news.answers would.
   
     * 1.3.2. Why did you include all the .win95 groups in the
       Followup-to header? 
       
   Originally, the .answers moderators' FAQ checker would reject the FAQ
   if it didn't include a followup-to line containing all the groups in
   question. I've started using only the .win95.misc group as it seems a
   better place for folow-ups to the FAQ itself. Yes, I've started
   reading .win95.misc to look for FAQ followups.