-------------------------------------------------------
 Generating a Complete Problem Report Using WINBUG.EXE
-------------------------------------------------------

WINBUG.EXE is an application that was developed to help beta sites
report bugs to Microsoft.  Using this tool you will record information  
about your system and the problem you encountered.  This information 
and any additional files needed by the beta team are compressed in a 
file you can upload to CompuServe or copy to a floppy disk and mail to 
the MSDN beta team.

I. Using WINBUG.EXE

A copy of WINBUG.EXE has been included with your beta kit.  You can run 
WINBUG.EXE from the floppy or copy all files on the disk to a new directory 
on your hard drive and run the program from there.  Please keep any other
versions of Winbug (from other Microsoft beta programs) you may have 
in separate directories since each version of the program generates files 
that are specially marked with the ID of the beta program it came with. 

Follow the instructions in WINBUG.EXE to create your bug report (you can 
reach on-line help by selecting Index from the Help menu).  When saving, 
you will have the option of attaching files to the report. If you have 
additional files that would be helpful to the beta team in debugging 
your problem please include them with your report by adding them to 
the list in the "Select files to include with your report" dialog 
that is displayed when you choose to save a report.

II. Submitting Problem Reports to Microsoft

   A. Reporting Problems Using CompuServe

   	Uploading complete problem reports into Library 1, "Bug Reports"
	in the MSDN Beta forum on CompuServe (GO MSDNBETA) is the preferred 
	method of reporting problems for this beta.  Please create a problem 
	report using WINBUG.EXE and upload it to library 1 in the MSDN Beta forum.

      WinCIM Users

	There are two known problems when using CompuServe Information 
	Manager for Windows (WinCIM). 

	1. There is a problem with WinCIM, DOS CIM, and Mac CIM that 
	can cause some of your bug report(s) to be lost when you upload 
	multiple reports.  Unlike DOS file naming conventions, CompuServe 
	limits file names to 6.3 characters.  CIM will truncate whatever 
	filename you choose to 6.3 (i.e., 12345678.TXT - > 123456.TXT). CIM 
	will not warn you that you are overwriting a file that you
	previously uploaded (i.e., if you upload BUGREP1.CIS, BUGREP2.CIS,
	etc., they all get truncated to BUGREP.CIS and each one will 
	overwrite the last). Until these problems are fixed in future 
	versions of the CompuServe Information Manager software, PLEASE 
	BE SURE TO USE UNIQUE 6.3 NAMES for your bug reports to make sure 
	we receive them all.  If you do not receive a receipt from the beta
	group via CompuServe mail within two working days letting you know 
	we received each of your reports please upload the file(s) again.

	2. WinCIM users who have accessed a forum previously may not see new 
	private sections in that forum to which they have been granted access.
	This is because WinCIM doesn't automatically update the user's Forum 
	Database. The solution is to go (while off-line) to WinCIM's 
	Special:Forum Database menu and delete the entry for the forum where 
	you cannot see some sections.  When the forum is next accessed, the 
	additional section(s) should be available.