Microsoft®
“Memphis”
WinHEC Developer Release

Testing Guide

April 7, 1997

This guide contains installation instructions, bug submission, and newsgroup support options, as well as covering general Q&A.  Please read this guide carefully.  This guide will not be available in the final product, but the appropriate material will be merged into the standard printed documentation and help files.  The purpose of this guide is to provide you with basic beta program infrastructure information.

This document is provided as part of a pre-release product, is subject to change without notice, and may be changed substantially prior to commercial release.
If you received a Memphis WinHEC Developer’s Release CD as part of your WinHEC kit, and are not currently enrolled as a beta tester for Memphis, you will need to enroll in the Beta program before you can access many of the services described in this document.
THIS DOCUMENTATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT FURTHER DISCLAIMS ALL WARRANTIES, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.  THE ENTIRE RISK ARISING OUT OF THE USE OF THIS DOCUMENTATION REMAINS WITH RECIPIENT.

This is a preliminary document provided as part of a pre-release product and may be changed substantially prior to final commercial release.  This document is provided for informational purposes only and Microsoft Corporation makes no warranties, either express or implied, in this document.  The entire risk of the use or the results of the use of this document remains with the user.  Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation.  If however, your only means of access is electronic, permission to print one copy is hereby granted.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.  The furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 1997 Microsoft Corporation.  All rights reserved.
Microsoft, MS-DOS, MS, Windows, Windows NT, Plus!, and other Microsoft product names or titles are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.

This is a legal agreement between you (either an individual or an entity) and Microsoft Corporation (“Microsoft”).  By installing this software, you indicate your acceptance of this Microsoft Corporation License Agreement.  If this software was not provided to you directly by Microsoft or you do not agree to the terms of this License Agreement, Microsoft Corporation is unwilling to license this software to you and you may not use or copy the software.
MICROSOFT CORPORATION LICENSE AGREEMENT
(for Microsoft Pre-Release Product Code-Named “MEMPHIS”)
1.	GRANT OF LICENSE.
	(a)	Microsoft grants you (“Recipient”) a limited, non-exclusive, nontransferable, royalty-free license to make and use up to ten (10) copies of the software accompanying this Agreement (“Product”) on computer systems located on Recipient's premises, solely to test the compatibility of Recipient’s application or other product(s) which operate in conjunction with the Product and to evaluate the Product for the purpose of providing feedback thereon to Microsoft.  All other rights are reserved to Microsoft.  Recipient shall not rent, lease, sell, sublicense, assign, or otherwise transfer the Product, including any accompanying printed materials.  Recipient shall not reverse engineer, decompile or disassemble the Product except to the extent that this restriction is expressly prohibited by applicable law.  Recipient may not disclose the results of any benchmark testing of the Product to any third party without Microsoft’s prior written permission.  Microsoft and its suppliers shall retain title and all ownership rights to the Product.
	(b)	Recipient agrees to provide reasonable feedback to Microsoft, including but not limited to usability, bug reports and test results, with respect to the Product testing.  Recipient will use reasonable efforts to review and comment on all documentation supplied.  All bug reports, test results and other feedback made by Recipient shall be the property of Microsoft and may be used by Microsoft for any purpose.  Due to the nature of the development work, Microsoft is not certain as to when errors or discrepancies in the Product may be corrected.
	(c)	Recipient’s use of the Product is not subject to confidentiality restrictions.  Recipient is free to discuss features of the Product or details with respect to Recipient’s use or intended use of the Product, provided that use of the Product shall take place solely at Recipient's site. Notwithstanding the foregoing, Recipient may not demonstrate or show the Product to third parties without the express written permission of Microsoft.
2.	TERM OF AGREEMENT.  The term of this Agreement shall commence on the Effective Date and shall continue until terminated upon the earlier of (a) Microsoft’ written notice to Recipient, (b) the commercial release of the Product by Microsoft, or (c) one year after receipt of the Product by Recipient.  Upon the termination of this Agreement, Recipient shall cease use of the Product and shall promptly return to Microsoft, or certify destruction of, all full or partial copies of the Product and related materials provided by Microsoft.
3.	COST OF TESTING.  There is no charge to Recipient for testing of the Product.  Microsoft shall bear all transportation expenses relating to the shipment of the Product to Recipient's place of business and Recipient will pay any return transportation expenses.
4.	PRODUCT MAINTENANCE.  Microsoft is not obligated to provide maintenance or updates to Recipient for the Product.  However, any maintenance or updates provided by Microsoft shall be covered by this Agreement.
5.	DISCLAIMER OF WARRANTY.  Product is deemed accepted by Recipient.  The Product constitutes pre-release code and may be changed substantially before commercial release.  The PRODUCT is provided "AS IS" WITHOUT WARRANTY OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT FURTHER DISCLAIMS ALL WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.  THE ENTIRE RISK ARISING OUT OF THE USE OR PERFORMANCE OF THE PRODUCT AND DOCUMENTATION REMAINS WITH RECIPIENT.  TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY CONSEQUENTIAL, INCIDENTAL, DIRECT, INDIRECT, SPECIAL, PUNITIVE, OR OTHER DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT OF THIS AGREEMENT OR THE USE OF OR INABILITY TO USE THE PRODUCT, EVEN IF MICROSOFT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.  BECAUSE SOME STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO RECIPIENT.
6.	GOVERNING LAW; ATTORNEYS FEES.  If you acquired this Product in the United States, this Agreement shall be governed by the laws of the State of Washington.  If you acquired this Product outside the United States, local law may apply.  If either Microsoft or Recipient employs attorneys to enforce any rights arising out of or relating to this Agreement, the prevailing party shall be entitled to recover reasonable attorneys' fees.
7.	U.S. GOVERNMENT RESTRICTED RIGHTS.  The Product is provided with RESTRICTED RIGHTS.  Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause of DFARS 252.227-7013 or subparagraphs (c)(i) and (2) of the Commercial Computer Software -- Restricted Rights at 48 CFR 52.227-19, as applicable.  Manufacturer is Microsoft Corporation, One Microsoft Way, Redmond, WA 98052-6399.
8.	EXPORT RESTRICTIONS.  Recipient agrees that it will not export or re-export Product to any country, person, entity or end user subject to U.S. export restrictions.  Recipient specifically agrees not to export or re-export Product (i) to any country to which the U.S. has embargoed or restricted the export of good or services, which currently include, but are not necessarily limited to Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria, or to any national of any such country, wherever located, who intends to transmit or transport the Product back to such country, (ii) to any end-user who Recipient knows or has reason to know will utilize Product in the design, development or production of nuclear, chemical or biological weapons, or (iii) to any end-user who has been prohibited from participating in U. S. export transactions by any federal agency of the U.S. government.

Contents
General Information	6
Welcome!	6
Responsibilities of a Beta Tester	6
WinHEC Attendee – Enrolling as a Beta Site	7
Before You Start	8
Read this Guide	8
Installing the Software	9
Changes we have made to the Memphis installation	9
SETUP Release Notes	9
Technical Support - Internet Newsgroups	11
Using News Reader Programs	11
Newsgroup Frequently Asked Questions and Answers	11
Configuring Microsoft Internet News and Outlook Express	12
Memphis Web Site	14
Connecting to the Web site	14
Feedback	14
Administrative	14
Cannot Access the Memphis Web Site	14
Reporting Problems via MSReport	18
Set up MSREPORT	18
Write good MSREPORTs	19
Submit problem report files using FTP	19
Providing additional hardware information	21
Compatibility Issues with other Beta Products	21
Questions and Answers	22
Technical Assistance with Setup	24
Backing up Windows 95	24
Make an Emergency Boot Disk	24
Creating a Bootable Floppy	24
Uninstalling the Memphis environment	24
Installing Windows 95 Memphis onto a newly formatted hard disk	25
Installing Windows 95 Memphis onto a blank hard disk (OEM Setup)	25

General Information
Welcome!
Welcome to Memphis, the next major release of Windows. This is the WinHEC Developer’s Release.  This is the second Developer’s Release of Memphis, provided for distribution at the Windows Hardware Engineering Conference, 1997.  This document describes setup, bug submission, and newsgroup support options, as well as covering general Q&A. This release represents a developer’s release of the Memphis base code, new hardware support, and other features described in this document but not a beta of the complete Memphis product. We believe that this is a solid release and a good platform for testing hardware and application compatibility.
YOUR participation and YOUR timely feedback are critical to the success of this product!  Please install this product on as many different hardware configurations as possible, and report both your successes and your problems as soon as possible.  Successes should be reported using our web-based survey tools, while bugs should be reported using the web-based bug report tools or MSReport.  
NOTE:  If you received a Memphis WinHEC Developer’s Release CD as part of your WinHEC kit, and are not currently enrolled as a beta tester for Memphis, you will need to enroll in the Beta program before you can access many of the services described in this document.
Responsibilities of a Beta Tester
1.	Install and use the software promptly.  
2.	Test the product for application and hardware compatibility, and report problems and suggestions promptly. 
3.	Ensure that the pre-release software is used only by the beta test participants at your site in accordance with the Microsoft Corporation License Agreement included in this document.
4.	Understand that the increased level of contact (such as phone calls from Microsoft to you) is for the beta test period only.  At the conclusion of the beta test program, normal product support will be available.
5.	Allow Microsoft access to the designated beta test equipment if necessary.
6.	Understand that a pre-release product may contain problems that could affect normal office productivity.  You should expect some down time, and you might encounter loss of data.  You should back up your system before installing the pre-release software, and often during the beta test program.  Microsoft is not responsible for any problems resulting from the use of this pre-release software.
7.	Upon notice of completion of the beta test, destroy all of the pre-release software and beta program documentation.
8.	If you manufacture products that are designed to be compatible with Windows 95, you may be asked to provide loaner copies of your products for our test labs.  This includes new PCs, adapter cards, disk drives, software, etc.  If you want to loan your latest products to ensure that your products are adequately covered, contact your Microsoft Account Manager or send email to IHV@microsoft.com.  PC Manufacturers should ensure that the new Windows 95 Hardware and Integration Labs have final production copies of all of your machines to ensure broad test coverage, and enable our engineers to rapidly diagnose reproducible problems in our labs.

WinHEC Attendee – Enrolling as a Beta Site
If you received this kit as part of your WinHEC kit, you will need enroll as a beta participant in order to access the discussion newsgroups, bug reporting web site, and to receive updated versions of this test product.  
If you are already a Memphis beta site, you do not need to enroll again.
To enroll, please send this information via Email to memreq@microsoft.com. To ensure enrollment as a WinHEC attendee, please indicate “WinHEC Attendee” as the subject of the message.

BetaID (if you have one from a previous Microsoft Beta): ________________

Name: ________________

Title: _________________

Company: ______________________

Address (no PO boxes): ___________________

City: _______________________    State/Province: ______________________    

Country: __________________    Zip/Postal Code: _________________

Phone: _________________          Fax: _______________________

Internet Address (email):  _________________

Company Type (Check all that apply):
( ) Press
( ) PC Manufacturer (OEM)
( ) Hardware/Peripheral Manufacturer (IHV)
( ) Software Developer (ISV)
( ) Corporate/Business
( ) Individual End User

Before You Start
First, a word of caution.  Although we have put much effort into the verification of this software, it is pre-release software that will be used by every application that you run.  Microsoft strongly suggests that you back up any important existing data and programs before you install or run any of this software.  Also, whether you intend to use FAT32 or not, be sure to make a new Startup disk when running Setup.  Startup disks created with the released version of Windows 95 are not compatible with Memphis
Setup requires approximately 90 MB hard disk space to complete. 
If you are running an earlier build of Memphis with IE4 integrated, or have IE4 running on your system already, please switch to the old shell before installing this version of Memphis.
Sites using this software may encounter minor problems, and in rare cases, it is possible that some sites may encounter loss or destruction of data. Microsoft is not responsible for any problems resulting from the use of this beta software.
Read this Guide
Please read both of these documents before installing Memphis. These documents contain important beta and product information that you may need.
The documents are organized as follows:
Beta Guide
•	General Information
•	Installing the Software
•	Technical Support – Internet Newsgroups, Web site
•	Administrative Issues – change of address, etc.
•	Reporting Bugs
•	General Q&A
Release Notes
•	General Information
•	Installing the Software
•	What’s New in Memphis – Highlights
•	Application Notes – Feature Descriptions and Known Issues

Installing the Software
Run SETUP.EXE from the \Memphis directory of your CD and follow any prompts that are presented.  \Memphis\Setup.exe
Changes we have made to the Memphis installation
We have made several changes to Memphis installation that makes the process easier and more reliable.
	When upgrading over Windows 95, Memphis uses the same settings as the current installation, and so is able to proceed through the setup process more quickly with less user interaction.
	Legacy hardware detection now takes place during Memphis’s first boot, after all plug and play devices have been set up, enabling detection to run more quickly and reliably.
	You have the option of backing up system files on your hard disk so that you can uninstall Memphis and return to your previous Windows 95 installation.
	The Emergency Boot Disk (EBD) now contains a generic real mode ATAPI CD-ROM driver, making compatible CD-ROM devices available when running from the EBD. This driver is not guaranteed to work with all CD-ROM devices but is offered as a possible replacement if the real-mode drivers that came with your machine are unavailable. See “Create a Bootable Floppy” in the Technical Assistance section at the end of this guide for more details.
SETUP Release Notes
	If you are using a build of Memphis greater than 1397 (or otherwise using Internet Explorer 4), you MUST do the following:   Change the Shell to “Windows Classic Shell” on the appearances tab of the desktop control panel (or if using IE4, go to add/remove programs control panel and remove web view integration) BEFORE installing Memphis WinHEC Developer Release.  If you do not do this, you will not have a working Internet Explorer Browser after the upgrade.  See the Internet Explorer section on how to re-enable your browser.
	Setup requires approximately 90 MB of hard disk space to complete. This will be reduced for the next beta. A significant portion of this is temporary work space will be removed at the completion of setup. Note: This does not include the optional Win95 uninstall file (winundo.dat) which can be up to 50 Mb depending on your system.  This file can be located, at user discretion during setup, on a separate drive/partition if available.
	If you CANCEL during setup, you must reboot before trying to run Setup again. This will be fixed in future releases.
	Policy Editor and Default User-Disable system policies restricting the Default User before installing Memphis.  Windows is launched during setup without prompting for a login to reduce required input and improve performance.  A policy restricting the Default User will be invoked without a Windows login, potentially preventing setup from finishing.
	Setup on Toshiba Infinia will disable In Touch module – This is not currently supported by USB but will be fixed in a future release.
	Number Nine Imagine 128 Display Adapters, with the original display driver, may have to either set up from MS-DOS or change your display driver to VGA to prevent setup from hanging. There is a new I128 driver in Memphis. After you install Memphis, you will not have to do this for future upgrades during the beta program. 
	Diamond – InControl Applet, Must not be running during Memphis Setup.  Edit the Win.ini and remove the executable from the load or run lines.
	Aztech Systems – PnPchk Applet, Must not be running during Memphis Setup.  Edit the Win.ini and remove the executable from the load or run lines.
	USR Winmodem, Must not be running during Memphis Setup.  Edit the Win.ini and remove the executable from the load or run lines.
	APM, Does not recognize file copying as activity and powers down the system during setup.  If the sourcepath is on the local disk, there is no harm done, and moving the mouse kicks setup back in motion.  You may experience this issue when installing over the network - this terminates the connection.  In the Control Panel-turn off APM for network Memphis setup.
	Memory Managers, In order for detection to run properly, users need to remove conflicting managers from the config.sys, otherwise a dialog on 1st boot will ask to remove it.
emm386 (only if they use the highscan option)
qemm
386max
	Compaq LTE 5xxx portables -  Setup or Installing New Hardware may hang during Hardware Detection when the machine is docked. If this happens, just restart the machine and let the Setup Safe Recovery continue. It will skip over the detection code that hangs, and complete setup normally. 
	Online Services folder shows up as “Online~1” - If you have user profiles enabled when you install Memphis, the Online Services folder will appear in the individual user’s desktops as “Online~1”. This is because during the first boot the short file name is converted to the long file name in the default user name desktop, not the individual desktops. 
	Startup Disk Recommended. Due to changes in the real-mode and protect mode kernels to support FAT32, original Windows 95 Startup disks are not compatible with Memphis Startup disks. When setting up Memphis for the first time you will be prompted to make a new Startup disk.
	If you format your hard disk, you will need a Startup disk (which has a generic CD-ROM driver) or your interface card and drive manufacturers real-mode CD-ROM driver. These drivers are customized for each device. If you do not have these drivers you should contact your vendor. If this is not possible please read “Creating a Bootable Floppy” in the Technical Assistance section. 
	You should back up your core configuration files and Registry using the ERU and CFGBACK utilities on the CD ROM before installing. These can be found in the \other\misc\eru and \other\misc\cfgback directory. Just run eru.exe and cfgback.exe and follow the instructions. 
	If you receive any version conflict dialog boxes during Setup, you should answer “No to All” to ensure that the Memphis version of all files is installed.
	Setting up English Memphis over localized or Pan-Euro Windows 95 is not supported. You cannot update a non-English version of Windows 95 to English Memphis. Instead, you must do a clean install of Memphis. This is the same as Windows 95 - you can convert from English to other Pan-Euro versions of Windows 95, but you cannot convert Pan-Euro versions to English.

Technical Support - Internet Newsgroups
Microsoft uses Internet Newsgroups for beta support.  If you are new to Internet newsgroups, you will find that they operate similarly to CompuServe forums.  Private newsgroups are accessed from a dedicated news server.  Name and password authentication is required for access to newsgroups.  Memphis contains a built-in news reader, or you may use third-party news readers.

NOTE:  You must be enrolled as a valid beta site to access the Memphis newsgroups.
Using News Reader Programs
•	The News Server for this beta program is:  betanews.microsoft.com
•	Your “User Account” is: your Beta ID
•	Your password will be sent to you by e-mail or by letter.  If you have not received your password within 5 business days of receiving your beta kit, please e-mail us at memreq@microsoft.com.  The people who monitor this e-mail alias can only help you with administrative issues.  This alias does not answer technical support questions.
•	All support for this beta will take place in the newsgroups beginning with:		microsoft.beta.memphis.
•	PLEASE configure your regular “friendly” name, e-mail address, and organization for your chosen News Reader program.  Microsoft support personnel will not respond to postings that use alternative names.
•	You may need to log onto your Internet Service Provider prior to starting your News Reader.  You can use MSN with the Internet access by opening your Dial Up Networking folder and double-clicking on the MSN connection, or by having Auto-Dial selected in the Control Panel - Internet.
•	Most News Readers include the ability to “Subscribe” to specific newsgroups.  This is just a data file located on your local computer that provides a way to “group” the newsgroups into two categories - subscribed and unsubscribed.  Subscribing to newsgroups makes it easier to follow topics you find interesting.  No information on subscribed vs. unsubscribed newsgroups is stored on the server, sent to Microsoft, or available to any other users on the Internet.
•	Once you are connected, you may have to Download Newsgroup Headers.  You will also have to “Refresh”  Newsgroup Headers in order to see newer postings, including your own postings.  
•	Please read the Readme files and use the Help information provided with the news reader program to learn more about subscribing, downloading, reading and posting.
•	These newsgroups are provided for the purpose of beta test feedback and support for Microsoft products.  We expect all beta testers as well as Microsoft engineers to keep all postings relevant to the purpose of the newsgroup, and to maintain polite and professional postings at all times. 
•	There is a technical Hotline for emergency problems when you can not access the newsgroups.  This hotline goes to a voicemail system that is checked periodically.  Please use this only for no-boot or cannot-access-newsgroup problems.  For other problems, the newsgroups will have a better response time.  The hotline number is 206-703-1904.  
Newsgroup Frequently Asked Questions and Answers
I have not received my account and password information.  When should I expect to receive it?
Your account and password should have been sent to you by e-mail at about the time your beta kit was mailed.  However, if we did not have an e-mail address on file for you, we have mailed the information to you by US Mail.  Please allow five business days after you receive your kit for the information to arrive.  If you have not received the account and password by then, please feel free to contact us at memreq@microsoft.com.
If you are a WinHEC Attendee, you will need to enroll in the beta program.
Will I receive one account/password for all the Microsoft betas that I am participating in?
For any beta that you are registered for with the same Beta ID number, you should receive one account and password.  However, we may find it necessary to periodically change this account.  In this case, we will resend the account information before changing over to the new account.
For previous betas, Microsoft paid for my time on CompuServe.  Will Microsoft pay for my time on the newsgroups?
Due to the way Internet access works, we cannot monitor which Internet sites are being accessed to suspend charges during the specific time you're online, even if you are using MSN.  You are responsible for any charges that you incur while on the Microsoft newsgroups.  Many ISPs, including MSN, offer unlimited access times for a low monthly fee.  You may want to investigate these pricing policies.
I have tried to use my News Reader to see the Microsoft newsgroups, but I am having problems.  Where can I get help?
This document gives you a lot of information for accessing newsgroups.  Anything beyond what is provided here is probably specific to your individual network connection. It is also possible that your proxy server does not pass NNTP requests. You will need to talk with your network manager to find out if there is a way to do this on your network.  It may require accessing a specific server.
I was able to connect to the Microsoft newsgroup server before, but now I cannot.  What has changed?
If you were able to connect to the newsgroups before, chances are the problem is on our end.  You should wait for few hours and try again.  We will also try to post newsgroup status on the web site, so you might check there.  We update our access list daily so it is possible that the update had some problem with your account.  If you cannot access the newsgroups for more than two days, please feel free to ask us to check your account by sending e-mail to memreq@microsoft.com.
My company has a firewall that is preventing me from accessing the Microsoft newsgroups.  Can Microsoft help?
If your ISP or proxy server has a firewall that prevents your connecting to the betanews server, you will have to coordinate with your provider concerning methods for gaining access. You may have to use a dial-up Internet provider such as MSN, or an alternative independent Internet service provider, to gain access.
Configuring Microsoft Internet News and Outlook Express
Microsoft Internet News is a “News Reader” that lets you read bulletin board discussion groups, such as the USENET, using NNTP-based news servers. If you install Internet Explorer 4, Microsoft Internet News has been updated to Outlook Express.
Getting Set Up
The first time you run Microsoft Internet News, you will be asked for the following information:
•	The name of your news server (betanews.microsoft.com).
•	Your account name and password on this server.  You will need to use your Beta ID as your account name, and the password that was sent to you separately by e-mail or letter.
•	Your full e-mail address. For example, “PatSmith@acme.com”  This is the address that people should use when responding to a message that you post into a discussion group.
•	Please use a valid email name in case Microsoft support engineers need to contact you via email to help understand or resolve a problem.
•	Please set your friendly name to your real name when using Microsoft support forums.  Microsoft engineers will not respond to or support aliases or pseudonyms.
If you do not know all of these items, or are unsure, then your service provider or mail administrator should be able to provide it to you.  You can add or change any of this information at a later time using the appropriate news reader menus. 
If you have problems…
•	Check your connection to your Internet service provider.
•	Try subscribing to a group before reading it.
•	At this time, you must either establish the connection to your Internet provider manually before reading news, or else use Autodial (in the Internet control panel)

Memphis Web Site
Connecting to the Web site
The web server can be accessed at: http://winbeta.microsoft.com/Memphis
You might want to add a link to your Favorites so you don't have to remember this.  You will now be connected to the WINBETA Web Site for Memphis.  If you are unable to access the Web site, see the following section, “Cannot Access the Memphis Web Site.”
Feedback
Installation Survey
Your continued participation in the Memphis Beta Project requires the completion of an Installation Survey subsequent to each Beta release. Data collected through this survey will improve our ability to measure the Beta's coverage of third party products. Please take the time to complete this survey today.
Submitting Bug Reports via Web
The Memphis Beta Project will serve as a testing vehicle for many new support tools, including a Web-based Bug Reporting tool. Development continues on this tool, guided by your feedback.
Application Compatibility Survey
The Memphis Team would like to ensure that all applications run as well, if not better, on Memphis than they run on Windows 95. Your feedback will help us achieve this goal. Please complete the Application Compatibility Survey for each application you test on Memphis.
Administrative
Address Change
You will now be able to submit address change via the Web.  Please follow the links to the address change page and submit all your new information.  Your address will be updated in our main database within 48 hrs.
Nominate a friend as a beta site
The Memphis Beta Team is looking for a few good testers... who could better recommend people with what it takes to Beta test operating systems than you? All we ask is that you take two minutes to fill out the Nominate a Beta Tester survey.
Cannot Access the Memphis Web Site
We are aware that difficulties accessing winbeta.microsoft.com have plagued a number of Beta sites.  We are investigating these issues and we will post information to the Memphis newsgroups as it becomes available.  An overwhelming majority of access issues are a direct result of the security on the site.  The confidential information on this server requires secured access.   Memphis Web site security cannot be relaxed.
The size of this project has grown significantly over the past several months and it will continue to grow exponentially.  Please take this into consideration, and only request assistance if you suspect your user account on the server has not been established.  
**Note** You are strongly discouraged from the use of workarounds that might compromise security.  You are responsible for your Beta ID and password -  sending them across the Internet in clear text compromises security.
Following is a list of troubleshooting steps and additional information concerning security on the Internet.

Troubleshooting Suggestions

If you are unable to access the Memphis Web site, you may be experiencing one of the following: 
- You are attempting to access the site with a clean installation of Memphis build 1415.  Upgrading previous IE 3.x installations will workaround the authentication issue.  This is under investigation - information will be posted to the Memphis newsgroups as it becomes available.
- Access to the Internet is through a firewall that does not pass the NT Challenge and Response protocol (NTLM). 
- Access to the Internet depends on a proxy server that does not pass NTLM
	**Note** Internet Service Providers may use proxy servers.
- Your Memphis Beta account has not been processed - please allow seven business days before inquiring. If, after seven business have passed, you still have not received a Beta ID and password, please notify the Microsoft Beta Group. 
- Access control privileges are not set correctly on the server. If you suspect the issue is with your user account, request its verification.  If the account is found to be valid, the issue you are experiencing is detailed on this posting.
- You are using MSN to access the Internet.  This issue is currently under investigation - information will be posted to the newsgroups as it becomes available.
- The browsers’ configuration may be at fault - see the following:
1  The MS Client for MS Networks is required to access the site.
To add the MS Network Client:
		1. go to Control Panel
		2. click Network
		3. Add "Client" for Microsoft Network
		4. click Ok 
		5. restart system 

2)  You must use a browser that supports the NT Challenge and Response Protocol.  At this time, Internet Explorer is the only browser that supports NTLM - Netscape does not understand the request for NTLM authentication.
3)  Try connecting directly to your Internet Service Provider.  Accessing the site through a proxy server may not work, as the proxy server must be configured to allow NTLM transient access to port 80.  A majority of companies use firewalls for security on their Internet connection.  Firewalls by definition are not going to pass NTLM.
4)  It may prompt you for the password twice.  This is expected behavior.  By default, a null password is offered by the browser on the first attempt.  Enter your Beta ID and password when prompted the second time.
5)  Use the same 14 character password you use for the newsgroups.
6)  Check the registry.  If you have an extra entry for the service provider, you must manually remove it.  In Regedit, view: 
HKEY_LOCAL_Machine\system\currentcontrolset\control\securityproviders
Its value should be “msnsspc.dll” without the quotes.
7)  Do not log into Windows before dialing into your ISP.  Your Windows login is offered by the browser to any request for NTLM authentication.
8)  If you can access from home but not work, and you can access other HTTP sites, there may be an issue with a router between you and winbeta.microsoft.com.  Try the following from a command prompt within Windows:
TRACERT WINBETA.MICROSOFT.COM  
This will display the IP address of each router that directs your packet until it hits its destination (winbeta.microsoft.com).  If it does not reach its destination, your issue is not with the Web server.
9)  You may be experiencing a friendly name resolution issue.  To test your DNS settings, try using the IP address for the site: "http://198.105.232.67" without the quotes.  If this works, your issue is with your DNS server.  A workaround is to add this address and a friendly name to the HOSTS.SAM file in your Windows directory, and then rename the file, removing the extension, so that it is just HOSTS.

More Information

Following is additional information concerning the security options we considered for the Memphis Web site, as well as an explanation as to why we chose to implement NTLM.

Proxy Servers and Firewalls
Firewall
A system or combination of systems that enforces a boundary between networks to prevent unauthorized access of private networks. Firewalls prevent the passage of packets between separate networks.
An Internet firewall system permits one to take advantage of many of the services offered on the Internet, while limiting exposure to attack.  Firewalls may consist of a collection of hardware and software components that collectively provide a protected channel between networks with differing security.  Potential paths to the private network are limited by configuring the firewall to only accept packets from IP addresses and/or ports of the TCP/IP protocol that have been designated by the system administrator.  
Proxy Server
A program that deals with external servers on behalf of internal clients.  Proxy clients talk to proxy servers, which relay approved requests to real servers, then relay the server's response to back to the clients.
Proxy servers make a firewall safely permeable to users behind the secured entrance, while closing entry ways in the private network to potential attacks.  The proxy server must act as both a server and client.  It serves proxy clients when accepting approved requests for external servers, and requests services from those servers on behalf of its clients.  Proxy servers are commonly used for corporate networks that are connected to the Internet - Internet Service Providers may use them as well.
Access to the secured Memphis Web site requires firewalls/proxies be configured to permit passage of NT Challenge and Response (NTLM). Modifications to your company's firewall may not be acceptable given your company's security requirements. The security requirements for the Memphis Web site demand the implementation of a user-level access control scheme. NTLM satisfies our security requirements without affecting server performance.

Internet Information Server Security Options 
Basic
Basic authentication sends Windows NT usernames and passwords across the network without encryption. 
The relative ease with which a Beta ID and password could be acquired by even the most novice of hackers makes basic authentication an unacceptable solution for the Memphis Web site.
SSL
SSL (Secured Sockets Layer) supports data encryption and server authentication. All data sent to or from the client using SSL is encrypted. Accessing a Web site secured with SSL requires the user to notify the browser by typing "HTTPS://" when entering the address. If basic authentication is used in conjunction with SSL, the username and password are transmitted after being encrypted by the client's SSL support. 
SSL was implemented on the Detroit (OSR 2.1) Beta project Web site. It proved impractical for the site, as the server suffered severe performance degradation when encrypting each packet transmitted over the Internet. Browsers timed out, content was delivered at rates so slow as to be intolerable.  In short - its value as a resource suffered. Additional issues that weighed negatively in our consideration of SSL include the potential for confusion with the use of a different addressing scheme (HTTPS://) to access the site, as well as the requirement that firewalls be configured to accept the SSL protocol. 
NTLM
Windows NT Challenge/Response requests clients to send user account information using the Windows NT Challenge/Response (NTLM) protocol. Encryption is used for the secure transmission of usernames and passwords. Currently, NTLM authentication is only supported by Microsoft Internet Explorer. 
NT Challenge Response offered the most viable security solution for the Memphis Web site. Passwords are protected with encryption, while content is delivered using HTTP. Implementing NTLM offers user-level access control without an impact on the server's performance. We regret that the implementation of NTLM may make the site inaccessible to you; an evaluation of all the security configurations available resulted in its selection.

Reporting Problems via MSReport
Set up MSREPORT
If you were unable to send us a bug via the web, you can still use MSReport as a backup.  To use MSReport, please follow these steps:
1.	Set up MSReport.  To set up MSReport, go to the \betaonly\msreport directory and run Setup.  
2.	Read the MSReport Help file, it contains many valuable tips about using the new program.
3.	Fill in the User and Machine information sections before reporting your first problem.
4.	IMPORTANT:  Report all Beta bugs in the “Memphis” folder.  You must explicitly select the “Product” folder before entering a new bug.  This allows a single tool to be used for different products.  Please DO NOT submit Memphis bugs in the MSReport folder(s) (those are for bugs against the MSReport tool), or in any other folder (if you have previously been aa beta tester).  As those programs may not be active anymore, or may be part of another group, using those folders will cause your bug report to not be processed correctly.  You may want to delete the corresponding directories from your hard disk to avoid using them by mistake.
5.	Internet Explorer, Mail, News, Java and NetMeeting all have custom Web pages and do not use MSReport.  To report specific bugs in these applications, please see the Internet location in the Release Notes document.
Bug report confirmation for all bugs submitted should be received in less than two business days via Internet email. Possible reasons why you may not have received confirmation mail for each bug report are:
•	Our system may be experiencing delays in sending confirmation mail due to heavy load and increased processing times.
•	Your bug report could not be entered into our database due to corruption of the file. The most common cause of this is sending the file in ASCII mode when using FTP. Please make sure to submit MSReport files in binary mode, as ASCII mode will render the file unprocessable. Consult the beta support notes, or any documentation you have for your FTP or terminal program for information on setting the binary mode for file transfers. 
•	Your MSReport files contain an invalid Internet address. Examples include using a comma instead of a period, or incorrectly placing space characters in the email address. Note: placing two or more valid email address causes an invalid email address in our processing system. Please use only one Internet address in MSReport.
•	You created a subdirectory under the bupload directory.  Please do not use subdirectories as our automated bug processing system will not process your bug reports.

If you have not received confirmation mail within two business days for all bugs submitted, please resend you report. If you do not receive confirmation mail after resubmitting your reports, please post a message with the name(s) of the file(s) you uploaded and we will assign an engineer to investigate the situation.
NOTE:  You should not use MSReport with Large Fonts enabled - many of the dialog boxes will not display properly.
NOTE:  If you are using a previous version of MSReport, this beta comes with version 1.1.  Please install the new version and use it.
Write good MSREPORTs
Please include all relevant information when you report a problem.  Clear, thorough bug reports are necessary for us to track down, reproduce and debug problems.  Problem reports should:
•	Include all necessary or relevant files
•	Include an accurate description of the hardware and software configuration, including networking.
•	Have a good description of the problem.
•	List steps to reproduce if possible.
•	Indicate whether the problem occurs on the released version of Windows 95 (build 950) or OSR-2.
•	Have a good description of what happens when you hit the problem, including the exact text of any error messages you encounter.
•	Make sure you Create the Bug Report in the correct folder in the left-hand pane of the MSReport tool.
Submit problem report files using FTP
The preferred method for submitting bug reports is to use the new Web page forms.  If you are unable to use those, the second best solution is to use the MSReport utility and upload using FTP.  If you are unable to access the FTP site, alternative solutions are listed later in this document. 
FTP Clients
If you do not have an FTP client, you can use the command line FTP client that ships with Windows 95.  For detailed information on using the Windows 95 command line FTP client, please refer to the Windows 95 Resource Kit (included on your CD in help-file format in the directory \ADMIN\RESKIT\HELPFILE\WIN95RK.HLP).
Many corporations have an internal FTP client that they recommend that you use.  Contact your MIS department to find out if your company has a recommended FTP client.  
There are also many good Windows 95-based FTP clients available on the Internet.  One that many people use is WS_FTP32, available from :
http://www.csra.net/junodj/ws_ftp32.htm.  
Another place to look for FTP clients is:
http://www.windows95.com/apps/ftp.html.  
If you use these clients available from the Internet, you are responsible for ensuring your compliance with any applicable license agreements.
Uploading Bug Reports
You should upload your bug reports to the FTP site: “transfer.microsoft.com”.  Please upload all bugs to the /Bupload/Memphis directory.  Note that /Bupload is a hidden directory!  Just go ahead and “CD /Bupload/Memphis” and it will work.
In order to FTP, be sure you are “winsock-enabled.”  Typically you will be winsock-enabled if you are already accessing the internet. 
Using Windows 95 FTP Client from MS-DOS Prompt
1.	Log onto your Internet Service Provider.  You can also use MSN with the internet access as an Internet Service Provider by opening the Dial Up Networking connections in My Computer and connecting directly to MSN.  
2.	Start an MS-DOS box.  
3.	Type: "ftp transfer.microsoft.com" at the C:\ prompt.
4.	The system will respond with:
Connected to transfer.microsoft.com.
ftp Microsoft FTP Service (Version 1.0)
5.	You will be prompted for a user name. Type in "anonymous"
User (transfer.microsoft.com:(none)): anonymous
6.	You will be prompted for a password.  Type in your email address.
Anonymous access allowed, send identity (e-mail name) as password.
Password: (nothing will show up here when you type in your email address)
7.	Type in "binary" and "prompt" in order to set the file transfer type to binary, and to turn off interactive mode.
ftp> binary
Type set to I.
ftp> prompt
Interactive mode Off.
8.	CD to the /Bupload/Memphis directory.
9.	CD /Bupload/Memphis
10.	Type in "mput <drive:\folder\filename> on your computer.  The example below assumes you are "FTP-ing" the file "report1.bug" from the "c:\bugs" folder on your hard drive.
ftp> mput c:\bugs\report1.bug
That will commence the upload.
Using WS_FTP32
The following instructions are provided for the convenience of our customers using the popular WS_FTP32 client software.  
If you are using WS_FTP32 on your machine, you can configure the following fields:

1.	Profile Name: this is what you would call this particular connection.  For our bug upload server it might be something like "Bug Upload Profile."
2.	Host name: This would be transfer.microsoft.com. 
3.	User Name: Fill in this field with “ANONYMOUS”.
4.	Password: Fill this in with your email name. 
5.	Remote Host: Fill this in with /bupload/memphis 
6.	Local PC: This is the folder (ex: c:\bugs) where you have your bug reports stored on your local machine.  
7.	Press the save button and you’re ready to connect.  

To connect and upload a bug report using WS_FTP32:
1.	Hit the Connect button in WS_FTP32.  You should see the status bar flash, then a directory listing on the server should appear.  
2.	Using the controls on the right side (the host), navigate to the upload directory, \Bupload\Memphis, you need.  If you are going to send a bug to the upload directory, you will only have write access without read access.  This means that you won’t be able to see your files once you’ve uploaded them. 
3.	Send your bug files. 

Providing additional hardware information

If you are using the new Web Bug Report page, hardware information is automatically collected.
If you are using MSReport, you can use the following procedure to upload more accurate hardware information than the manual fields in the MSReport hardware description.
Here's how to generate a simple hardware log file:
1.	Install a Generic/ text only printer via control panel/ Printers
2.	Goto Control Panel/ System/ Device manager.
3.	Hit print.
4.	Choose All devices and system summary
5.	Choose Print to file.
6.	If needed, hit setup to change the printer to a non-fax printer.
7.	Let it print, name it Devman.txt
8.	Include the resulting text file devman.txt with the bug report.
This file includes: Bios/ CPU info, IRQ status, I/O Status, Memory Status, DMA Status, Drive Info, Device and driver info.
Compatibility Issues with other Beta Products
Please indicate in your bug reports WHENEVER you are using other Microsoft Beta software, whether as part of a direct beta program or from our Internet Web site. It is important that we understand the beta program interactions.  
If you are using third party beta software, and can indicate so in your bug report without violating your NDA terms, please do so.

Questions and Answers
Can I install this product over existing Windows 95 installation?
Yes. This release will upgrade Windows 95 PCs, and be preinstalled on new PCs by PC Manufacturers.  We encourage you to upgrade over existing Windows 95 PCs (including the original release, as well as over OSR-1, OSR-2 and Detroit updates), and report any upgrade or software compatibility problems ASAP.
Can I install this product over existing Windows 3.x or Windows NT machines?
No, this is designed as a Windows 95 upgrade.  It will not upgrade over Windows 3.x.  Downgrading over Windows NT would be a very complex task that will not be supported.  We are working on a 3.1 upgrade version, but it is not supported in this code.
Can I set up my PC to Dual Boot different Operating Systems?
Dual boot will NOT work with FAT32 hard drives at this time.  This is simply because at this time, other operating systems, including the original release of Windows 95 and all versions of Windows NT to date, as well as earlier versions of Windows and MS-DOS, do not recognize the FAT32 partition, and do not have the code necessary to understand it.
If you are not using FAT32, then you can set up a system for dual-boot with Windows NT using the exact same procedures used for Windows 95 (see the Windows 95 Resource Kit for details). You can also dual-boot with older versions of MS-DOS and Windows 3.x and this release of Windows, using the F4 boot-to-old-MS-DOS feature.  You can NOT, however, set up a single PC to dual-boot the original Windows 95 release and this update.  This replaces Windows 95 with updated files and features.
I installed the software on a new PC that came preinstalled with Windows 95 from a PC Manufacturer.  My display driver, or other preinstalled software doesn’t work the way it used to.
There are three possibilities here.  One, of course, is that you’ve found a bug in either Windows 95 or the preinstalled software on the PC.  
The second is that the PC Manufacturer has enhanced capabilities drivers (such as display drivers), customized for their specific hardware.  Windows 95 attempts to provide a very robust set of drivers that offer the best performance possible for the widest range of customers.  However, many hardware vendors offer new, improved, or enhanced versions to the PC Manufacturers for new PCs as a value-added extra.  It is not always possible for Windows 95 to support these enhanced features in the base product.  If you suspect that you may need to reinstall an enhanced driver, check to see if the PC Manufacturer supplied you with a drivers diskette, or a tool on the hard disk to create such a diskette.  (TIP:  You might also look in the \windows\options\cabs directory if it exists on your PC. Many manufacturers use this standard directory for enhanced drivers and INF files).  Note that using third-party display drivers with Memphis will disable the multiple display support feature, as the third-party drivers do not yet support this new feature.
The third case is if the image is no longer centered on your monitor.  It may be that the optimal refresh rate chosen by setup for your monitor is different than you were previously using.  Simply use your monitor controls to adjust the position on the monitor, and you should not have any more problems.
In either of the first two cases, please report the issue to Microsoft.  If it’s a bug, we’ll try to fix it.  If it’s an enhanced driver we don’t support, we will try to leave it in place, or explore alternate solutions to provide the best possible customer experience.  
If I beta test this product, how will I get the final version for my PC?
We will provide a courtesy final CD to all of our active beta testers.  Active means uploading bug reports, participating in online discussion forums, and participating in beta surveys.  
What do I need to do if I’ve successfully installed the product, and don’t see any glaring hardware-related bugs right away?
Please complete the Upgrade Survey Form located on our web site.
How can I get other people at my company or other companies included in this beta?
You can send us the following information via the Memphis Web Site.  Also you can email "MEMREQ@microsoft.com".   This will be processed by an automated processing system, so please fill in all of the information. 
BetaID: (if you have one from a previous Microsoft Beta)
Name:
Title:
Company:
Address (no PO boxes):
City, State/Province, Zip/Postal code:
Phone:
Fax:
Internet Address (email):
Company Type (Indicate all that apply):
( ) Press
( ) PC Manufacturer (OEM)
( ) Hardware/Peripheral Manufacturer (IHV)
( ) Software Developer (ISV)
( ) Corporate/Business
( ) Individual End User
How do I notify the beta program of new contact information such as a new mailing address or new email address?
You can change you address via the Memphis Web site.  If you can not connect to the web site, please submit your address change request to MEMREQ@microsoft.com with your beta ID.

Technical Assistance with Setup
Backing up Windows 95 
You should back up your core configuration files and registry using the ERU and CFGBACK utilities on the CD ROM before installing.  These can be found in the \other\misc\eru and \other\misc\cfgback directory.  Just run eru.exe and cfgback.exe and follow the instructions. 
Note on Backup:  Memphis includes a new backup utility.  If you currently have the Windows 95 Backup on your system.  This new backup will be able to restore from Win95 backups in the next beta, but right now, the format is not supported.  
Sites using this software may encounter minor problems, and in rare cases, it is possible that some sites may encounter loss or destruction of data. Microsoft is not responsible for any problems resulting from the use of this beta software.
There are two possible installation paths for Memphis.  You may reformat your hard drive and install Memphis to a clean hard drive. OR Unlike OSR2, you can upgrade your current version of Windows 95.  We recommend you upgrade your current version of Windows 95.  
Make an Emergency Boot Disk
Better yet, make several!  You can make an EBD during setup when prompted during the setup process.  You can also make a Startup Disk afterwards using the “Add/Remove Programs” Control Panel, Startup Disk tab, which is the same as an EBD.  You can also SYS a floppy disk after installing Memphis.  Your existing boot floppies (of any version of a MS operating system) will not be able to recognize a FAT32 disk partition.  Moreover, you will not be able to start the Memphis version of Windows if you boot your system with a build 950 startup disk.  You MUST use a new boot floppy disk made with this new release of Windows 95 if you want to be able to get to your data when booting from floppy disk.  It is therefore a good idea to have several spare bootable floppy disks with the new, FAT32-aware system files on them.  
Creating a Bootable Floppy
Use a text editor to create an AUTOEXEC.BAT file on the root of the Emergency Boot Disk that contains the following line:
MSCDEX.EXE /D:mscd0001 /V /M:12
Then add the following line to the CONFIG.SYS file already present on the root of the Emergency Boot Disk after “DEVICE=HIMEM.SYS”:
Device=ATAPI2CD.SYS /D:mscd0001 /i:0
Reboot the machine with the Emergency Boot Disk in the 
Uninstalling the Memphis environment
An option to backup your current Win95 operating files is offered during the normal Memphis setup procedures.  This recovery capability is only successful if you do not compress your primary partition after you have upgraded to or clean installed Memphis.  If for any reason you would like to return to your original Win95 configuration and have not compressed the primary partition since installing Memphis you can execute the program UNINSTAL.EXE located in the \windows\command subdirectory.  The program will copy your original Win 95 environment back to your windows directories.  The backup files can only be executed one time and is not perserved to run twice.  The only way to obtain a Memphis uninstall capability is to recreate the backup file set by installing Memphis a subsequent time.
Be advised that the backup file set of Win95 has no long file name support.  The only way to reinstate long file name support is after Win95 has been reinstalled, run the program :\>SULFNBK /r.  The program is on your Startup disk and on the CD.
Installing Windows 95 Memphis onto a newly formatted hard disk
If you intend to start with a freshly formatted hard disk, you will need to either SYS your hard disk after formatting it and then install real-mode CD-ROM drivers, or create a boot floppy that contains both the real-mode drivers for your CD-ROM and the MSCDEX driver.  Your PC System Vendor or SCSI Adapter Card Vendor should have provided appropriate drivers and/or documentation with the hardware.  If you have a new PC preinstalled with Windows 95, it may be set up to allow you to create a CD-aware boot floppy using the “Microsoft Create System Diskettes” utility (mscsd.exe).  This is an optional utility and some PC manufacturers provide this tool for your convenience.  If your manufacturer did not provide this on your hard disk, you will have to make the boot disk manually.
CAUTION:  Each of the following procedures involves reformatting your hard disk, which destroys all of the data on it.  If you intend to use one of the following procedures for installing Memphis and your hard disk contains data you wish to save, back up the data to a second medium before proceeding and restore the data after the Memphis installation is complete.
The best way to prepare a clean hard disk for setup is to:
1.	FDISK your hard disk.  Note that if you want to format the hard drive using FAT32, boot from a Memphis Startup disk (for instructions on how to create a Memphis Startup disk prior to installing Memphis see step 1 of the following section.  After booting from the Startup disk, run FDISK.EXE on the Memphis CD and answer Yes when prompted to enable large disk support.  To delete all existing partitions, create a new primary DOS partition and make sure it is marked as “Active
You can also create a Startup disk (bootable floppy) 
•	During Memphis Setup.     Or
•	Using the Add/Remove Programs option in the Control Panel
2.	Install your real-mode CD-ROM IDE or SCSI drivers, either using the manufacturer’s installation disk or by manually copying from your original Windows 95 files before formatting your hard disk.  This real mode configuration is first tested on a boot floppy and then transferred to the hard disk after it has been formated.  It’s a good idea to test this procedure on a boot floppy before formatting your hard disk.  
3.	Re-boot the system using the boot floppy, and format the disk with FORMAT.COM, with the /s switch, of the Memphis CD.
4.	Run Setup from the \memphis directory of the CD ROM.
Installing Windows 95 Memphis onto a blank hard disk (OEM Setup)
1.	Copy the contents of the bootflop directory (in the \BetaOnly directory on your beta CD-ROM) to a freshly formatted diskette.  The diskette can be formatted with Windows 95, but you must copy the IO.SYS and COMMAND.COM files from the bootflop directory on your beta CD in order for it to become an MS-DOS 7.1 boot disk (7.1 is the version of MS-DOS included with Memphis).
2.	If necessary, use the ATTRIB command to remove the read-only attribute from the following files:
ATTRIB -R A:\AUTOEXEC.CD
ATTRIB -R A:\CONFIG.CD 
ATTRIB -R A:\DRVCOPY.INF
3.	Rename the Autoexec and Config files on the boot floppy as follows:
REN A:\AUTOEXEC.CD  AUTOEXEC.BAT
REN A:\CONFIG.CD  CONFIG.SYS
4.	Copy your hardware vendor-supplied DOS CD-ROM drivers to the floppy disk.
5.	Modify the AUTOEXEC.BAT, CONFIG.SYS and DRVCOPY.INF files as needed for your CD-ROM and, if necessary, SCSI adapter card. This is a complex process and varies depending on your hardware, so we cannot provide direct support for individual cards.  Follow the comments in the files to determine what changes need to be made. 
The DRVCOPY.INF file is essential for setup from a boot floppy.  It will copy your real-mode CD ROM drivers to the hard disk during installation and update the config.sys and autoexec.bat on the hard disk so that the CD ROM is accessible during the restart at the end of setup.
6.	Boot from your boot floppy diskette and it will automatically run OEMSETUP.EXE from your beta CD-ROM.  If your disk is unpartitioned (e.g. if it is a brand new disk that has never been FDISK’d, or if you have used FDISK to delete all its partitions), then as part of the Setup process, the disk will be partitioned (followed by a reboot) and formatted.  If the disk is larger than 512MB, it will be partitioned and formatted using the FAT32 file system.
7.	Once OEMSETUP.EXE has begun copying files, remove the boot diskette from drive A: so that it will boot from the hard disk at the conclusion of OEMSETUP.  Note that on an unpartitioned disk, OEMSETUP will reboot the system after partitioning it.  It must reboot off the floppy during this second boot.  Then it will format the drive and begin copying files; you should remove the floppy before it reboots again after the file copy is complete.