Microsoft® “Memphis” 
WinHEC Developer Release
Release Notes

April 28, 1997

This guide contains installation instructions, technical application notes and known issues for the new features included in this release. Please read this guide carefully. This guide is not a complete documentation for all product features. This guide will not be available in the final product, but the material will be merged into the standard printed documentation and help files. The purpose of this guide is to enable you to focus on beta testing the new and updated components.

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.

THIS DOCUMENTATION 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	8
Welcome	8
Responsibilities of a Beta Tester	9
Before You Start	10
Read this Guide	10
Installing the Software	11
Changes we have made to the Memphis installation	11
Make an Emergency Boot Disk	13
Expiration of the Software	14
What is Memphis?	15
What’s New in Memphis	16
Beta Preview – Coming soon to a computer near you	18
Application Notes	19
Hardware Support	19
FAT32	19
Multiple Display Support	23
Win32 Driver Model (WDM)	27
PCMCIA	32
Power Management and OnNow	33
Device Drivers	34
IrDA Device Drivers and Utilities	41
Under the Hood	42
Internet	43
Internet Explorer	43
Microsoft Internet Mail and News	44
NetMeeting	44
Internet Connection Wizard	45
Shell, User and GDI	45
Plus! Features	45
Miscellaneous User/GDI enhancements	46
Image Color Matching 2.0 API	47
Display Control Panel Improvements	48
Settings Wizard	49
Communications and Networking	49
Dial Up Networking and Dial Up Scripting	49
Point-to-Point Tunneling Protocol (PPTP)	49
TAPI 2.1	51
Unimodem/V	52
ISDN 1.1 Accelerator Pack	52
NDIS 5	53
ATM	53
Memphis TCP-IP	54
Winsock 2	54
Resource ReSerVation Protocol (RSVP)	57
Remote Access Server	59
Microsoft Service for NetWare Directory Service (MS-NDS)	59
Microsoft 32-bit DLC protocol stack	60
3rd Party Networking  Release Notes	60
Applets and Utilities	62
MS Paint	62
Backup	63
Internet System Update (aka "Code Download Manager")	63
Web-based Bug Submission	64
HelpDesk Icon	64
Dr. Watson	64
System Info Utility	64
Compression Agent	65
Task Scheduler	65
Registry Scan and Backup	65
Calc	65
MSD	65
HyperTerminal	65
Windows Scripting	66
Windows Messaging	67
Imaging by Eastman Kodak	67
Microsoft Fax Installation for Memphis	68
General & Miscellaneous	70
Version	70
OLE/DCOM	70
Multimedia	72
DirectX	72
ActiveMovie	72
Windows Management Infrastructure	73
Running ScanDisk after bad shutdown	73
Updated Time Zone, Daylight Savings Time and International Dialing Codes settings	73
Service Packs	73
Release Notes:  Known Third-Party Application Issues	74
Technical Assistance with Setup	78
Backing up Windows 95	78
Making an Emergency Boot Disk	78
Creating a Bootable Floppy	78
Uninstalling the Memphis environment	79
Installing Windows 95 Memphis onto a newly formatted hard disk	79
Installing Windows 95 Memphis onto a blank hard disk (OEM Setup)	80

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, new & updated features, and known issues. This release represents an interim version of the Memphis base code, new hardware support, and other features described in this document.  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. Please see the Beta Guide for information on the specific bug reporting procedures.

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 downtime, 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.

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.
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.
Setup requires approximately 90 MB hard disk space to complete.  Of this, about 45 MB is temporary space used during setup.
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 the Beta Guide and Release Notes before installing Memphis. These documents contain important beta and product information that you may need.
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
•	Release Notes – Known Third-Party Application Issues
•	Technical Assistance with Setup

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.
•	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.
•	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. 
•	Setup on Toshiba Infinia will disable In Touch module – This is not currently supported by USB but will be fixed in a future release.
•	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. 
•	Novell Client32 fix is available through the Novell Company to provide the correct installation parameters. 
•	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.
•	“Unable to find VREDIR.VXD during Setup” – On certain clean install sceanrios net setup is trying to install the file NETAPI.DLL during first boot.  NETAPI.DLL is not one of the files that we currently copy to the local install directory on first boot, and so setup was unable to install it.  Furthermore because of a subtle bug in SETUPX, it was misreporting the file it was unable to find--saying it was VREDIR.VXD instead of NETAPI.DLL.  This will be fixed in the next release. 
•	Unable to configure some PCI devices behind PCI bridges - In some rare cases of devices behind PCI-PCI bridges Memphis may be configuring devices in conflict with each other.  In some cases Memphis does not even show any problems in Device Manager - no yellow exclamation marks.  In most cases we do show the yellow exclamation mark and indicate a resource conflict.  There is no workaround – you will need to reinstall an older build or wait for an updated build.
Make an Emergency Boot Disk
Better yet, make several!  You can make an EBD during setup when prompted.  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 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.  
Expiration of the Software
This beta release software will expire.  It will first issue a warning each time the system is booted, but normal operation will not be affected until the expiration date.  If you accidentally set your system calendar ahead, and boot your system, it will trigger this event.  To fix it you must:
1.	Reset the system date using the system BIOS or booting from an older operating system floppy disk (MS-DOS 6.x or Windows 95 original edition.)  Do not boot with your new MEMPHIS boot diskette, or it will be rendered invalid also.
2.	Reboot the system with your new Windows 95 boot floppy and SYS your hard disk to restore the original operating systems files.
3.	Reboot from the hard disk.
You will be shipped the next beta release of the software before this expiration date.
System Warning Date:  September 1, 1997
System Expiration Date: November 1, 1997

What is Memphis?
Over the past two years, Windows 95 has had two supplemental releases, called OEM Service Releases (OSR-1 and OSR-2), for PC Manufacturers to support new hardware and provide the latest Internet software. Memphis will be both a retail and PC Manufacturer (OEM) release that incorporates all of the OSR-1, OSR-2 and USB updates combined with new features and functionality, including the next version of Internet Explorer. 
The primary goal of this release is to enable developers working on Memphis technologies and drivers to continue development, as well as general testing and beta feedback on application compatibility and system stability. Key development technology areas include WDM, USB, HID, DVD, Digital Audio, ACPI and other hardware development work.
Memphis is built on the same code base as Windows 95. Our goal is to provide the same level of compatibility as Windows 95, while improving hardware support, system stability and robustness, reducing support and administration costs, and updating Internet applications and other utilities. We have added a limited set of Windows NT Kernel services for WDM, but the same real-mode MS-DOS components, Windows 95 Kernel, User, GDI and VMM are still available for existing application compatibility. Removing or re-architecting these components would introduce significant compatibility and performance problems. By continuing to use these, while adding common services between Windows NT and Windows 95, we are able to support the best of both worlds.  For those users that desire full 32-bit architecture, the Windows NT product provides this functionality.
Memphis has a few API extensions over Windows 95 gold, but most of these are also available as add-on packages for Windows 95 (for example, DirectX, ActiveMovie, Internet Explorer APIs, etc.), or are only relevant to a very few vendors (FAT32 disk structure details). There are a few new Memphis APIs for new features such as Multiple Display Support, which will be documented in a future SDK and are currently documented in the \betaonly directory on your CD.
The official name for Memphis has not yet been decided. Many people in the press have designated it “Windows 97” or “Windows 98”. While these are among several possibilities, neither is the official product name at this time. For convenience, we use the code name Memphis in place of Window 9X terminology. 

What’s New in Memphis
The features highlighted below are features that are new or significantly improved in Memphis since OSR-2.1 (a.k.a. Detroit, a.k.a. the USB supplement). The next section contains the list of most of the key new and updated features since Windows 95, along with short descriptions and release notes.
New Setup – The first thing you will see is that setup has been redesigned and streamlined to improve the experience for existing Windows 95 users upgrading to Memphis. A full hardware detection during the initial setup is no longer necessary. Memphis setup also uses the information on applets and utilities that you have installed already, and updates just those. 
Multiple Display Support – Possibly one of the neatest new features, if you have a PCI machine and can get two PCI display adapters and monitors. Multiple display support enables reading of e-mail and clicking on an HTTP link with the browser popping up on the adjacent monitor. It also enables a game to have left, right and center displays, or a separate instrumentation console. Not to mention the old standby dual-monitor uses – desktop publishing and presentations/notes, or just to get an expanded desktop.
Win32 Driver Model (WDM) – The all-new, unified driver model for Windows 95 and Windows NT. All your existing “legacy” drivers will continue to work just fine. WDM enables new classes of devices and busses to have a single driver for both operating systems. Examples are USB, HID, IEEE 1394, Digital Audio, DVD players, still image and video capture. See below for more information on these device classes in Memphis.
ACPI Power Management – ACPI is a new power control specification that supports new hardware interfaces in future PCs. Many OEMs are developing their ACPI machines. This Memphis test release provides the first operating system support for them to continue their development. We expect that the industry will be able to deliver ACPI-enabled PCs when Memphis ships.
FAT32 in-place converter – This is the feature that many of you tested as part of OSR-2, now becoming available for end-users to upgrade their machines. 
Web-based support tools – A new Internet driver and component update utility will help reduce cost of ownership by providing a simple, controllable update engine. A new web-based bug reporting tool will be used both for beta bugs and, when we’ve shipped, for reporting problems to product support groups along with appropriate configuration information.
Scripting – Memphis includes Windows Scripting Host, a shell that you can use to take advantage of ActiveX scripting (VBS and JS) directly from the shell or the command line, without embedding in HTML.
OLE DCOM- Distributed component object model extensions for existing OLE interfaces.
Dr. Watson 32 – New and improved, when your application generates a GPF, the “details” button now provides a whole host of advanced technical information. This should help technical support desks get their users up and running faster, and help application developers find and fix bugs easier.
Plus! Tab – We’ve built-in the Full Window Drag, Font Smoothing, and other user interface enhancements formerly available as part of the Plus! package, and added the “Plus!” tab to the standard display control panel. This brings Memphis up to par with Windows NT 4.0.
Backup – All-new Backup applet, supports SCSI Tape and a host of other new backup devices.
Windows Sockets 2 – Windows Sockets 2 (WinSock 2) utilizes the sockets paradigm that was first popularized by Berkeley Software Distribution (BSD) UNIX. It was later adapted for Microsoft Windows in the Windows Sockets. Windows Sockets 2 has changed its architecture to provide easier access to multiple transport protocols. Following the Windows Open System Architecture (WOSA) model, Windows Sockets 2 now defines a standard service provider interface (SPI) between the application programming interface (API), with its functions exported from WS2_32.DLL, and the protocol stacks. Consequently, Windows Sockets 2 support is not limited to TCP/IP protocol stacks as is the case for Windows Sockets 1.1
Resource ReSerVation Protocol (RSVP) – RSVP is a protocol for reserving network resources that can be implemented on existing networks. It has been proposed as an Internet standard, and seems likely to receive that designation. Although it is designed to work with any network protocol, it is well matched to TCP/IP. It is also explicitly designed to handle multicast traffic effectively. 
RSVP has the following attributes:
•	RSVP handles reservations for unicast, one-to-many, and many-to-many multicast applications. It can respond dynamically to changing group membership and routes.
•	RSVP is simplex. QOS for each direction of data flow is established separately and need not be the same.
•	RSVP is receiver oriented. The receiver of the data stream is responsible for requesting and maintaining the reservation, not the sender.
•	RSVP reservations are maintained in a “soft state” on participating routers. If the reservation is not periodically updated, it will be canceled.
•	RSVP is not a routing protocol. It utilizes present and future routing protocols to determine the paths by which data will be transmitted.
Performance – We have done a number of things to improve performance, and will continue improvements in this area.  We have improved startup time, application load time, and shutdown time.  
Multimedia - Activemovie 2.0 and DirectX 5 - These multimedia enhancements provide improved gaming and multimedia infrastructure.
Drivers – We have greatly enhanced the networking, display, printing, monitor, modem, and many other device driver support.  Please check for your favorite device, and let us know if it’s not supported.   Hardware vendors, if you haven’t been in touch with WHQL or other program management and you are interested in adding support for your new devices in Memphis, please contact WHQL and they will help you. You can find more information on: 
http:// www.microsoft.com/hwdev
for design information about WDM, busses and classes in Memphis, and 
http:// www.microsoft.com/hwtest 
for WHQL contacts and logo information.

Beta Preview – Coming soon to a computer near you
There are a few features that were not quite ready for this test release, but we are planning to put them in a future beta. We wanted to give you some idea of what is coming. Please remember, however, that as market conditions, development schedules and hardware technologies develop, we may have to change some of these features. This is not a commitment to deliver any of these features, just an indication of current plans. We have also noted in many cases, in the individual feature application notes, what’s coming soon.
Internet Explorer 4 - Most notably absent from this release is the new Internet Explorer 4, with integrated shell browsing and Active Desktop. Various versions of this product have already been in private test releases, demonstrated at developer shows, and reviewed in some publications.  The current versions are not yet ready for full Memphis beta testing, so we have decided to hold off on the integrated version and ship a good test platform for the other advancements we’ve made, to help developers and get some early core beta feedback.  This will be in the Beta 1 release.
Shell and Desktop Improvements - In addition to the IE 4 web shell and active desktop that you may have seen or read about, we have some more user interface and shell improvements that we think you will like. We are making the login, shutdown and control panels more organized, and simplify many of the things you need to do. We’re also fixing a few small things that have shown up after a couple of years using the shell.
Boot – Boot time enhancements and security, including logo.sys validation.

Application Notes
Hardware Support
For more detailed technical information on WDM, ACPI, USB, DVD, and the other new technologies, please refer to the hardware development web site:
http:// www.microsoft.com/hwdev
FAT32
FAT32 is an improved version of the File Allocation Table file system that allows disks over 2GB to be formatted as a single drive, and which uses smaller clusters than on FAT16 drives, resulting in a somewhat more efficient use of space on large disks (over 1 GB). FAT32 originally appeared in OSR-2. 
FAT32 drives have a different on-disk format than FAT12 or FAT16 drives. To date, most disk utilities have already been revised to work on FAT32 volumes, including all the major vendors. You may need to update your disk utilities if you have an older version. The disk utilities included with Windows have already been revised to include FAT32 support, in particular: FDISK, Format, ScanDisk, Defrag and DriveSpace (however, DriveSpace does not - and will not - support compressing FAT32 drives). In addition, support for FAT32 affects many of the internal data structures that the real-mode DOS kernel and the protect mode file system components use. As a result, some device drivers and disk utilities may encounter compatibility problems with Memphis, whether or not FAT32 drives are used. If you encounter such compatibility problems, please submit bug reports on them immediately - even if the problem affects a driver or utility that you or another vendor will be revising. In order to support FAT32, many new low-level disk APIs are provided with Memphis and some old ones will fail or behave differently on FAT32 drives. The new and changed APIs are summarized in the October ’96 Win32 SDK, available via a subscription to MSDN.
Note that most applications are unable to display free or total disk space over 2GB. Memphis includes new DOS and Win32 APIs (GetDiskFreeSpaceEx) that applications can use to obtain the correct amount of space. The Windows Explorer and the MS-DOS command prompt have been modified to use these new APIs so they should display the correct amount of free space. File Manager will not display more than 2GB of free space.

How to enable FAT32
There are 3 ways to enable FAT32:
•	Convert an existing FAT16 drive in place using the FAT32 Converter in Start > Programs > Accessories > System Tools > FAT32 Converter.  The actual converter is CVT32.EXE, installed in your Windows directory. This is the preferred method for converting to FAT32 for this release, to get additional testing on the FAT32 Converter. This program has already received extensive testing during the OSR-2 test program, and there are no known problems or data loss issues at this time.
•	Set up Memphis on an empty, unpartitioned disk, using a boot floppy and running OEMSETUP.EXE (not Setup.exe)
•	Run FDISK on a drive over 512MB. It will prompt you whether to enable “large disk support”. If you answer Yes, any partitions you create that are over 512MB in size will be marked as FAT32 partitions and will be formatted as such. (Note that there is no benefit to installing FAT32 on a disk smaller than 512 MB.) 
Converting a drive in place is a safe, fast operation (it typically only takes a few minutes, except for the defrag operation, which may take several hours). However, Memphis does not include a utility for converting a drive back to FAT16 once you’ve converted it to FAT32. There are several third-party utility products on the market now that do support converting back from FAT32 to FAT16, however.
IMPORTANT notes about testing FAT32:
•	Make a Windows Startup disk using Memphis before enabling FAT32.
•	Back up any data on your drive before converting it in place. If you like, you can use the RAWREAD utility in the \BetaOnly directory on your beta CD to copy an exact image of your drive into a single large image file on another drive. If necessary, the RAWWRITE utility can be used to restore the contents of your drive from the image file that the RAWREAD utility creates.
•	Do not use FAT32 on any drives that you need to access from other operating systems, including the gold version of Windows 95, all versions of Windows NT, and earlier versions of Windows or MS-DOS. Note that if you need to dual boot another operating system, you cannot convert drive C: to FAT32, even if the other operating system is installed on a different drive. However, systems running Memphis can share FAT32 drives across a network, and they will be accessible by MS-DOS, Windows 3.x, “gold” Windows 95 and Windows NT clients, just like any other FAT drive. Also note that MS-DOS 7.1 (the version included with Memphis) fully supports FAT32, so you can run most MS-DOS mode games and applications from FAT32 drives.
•	IMPORTANT NOTE if you use anti-virus software: Converting your drive requires updating your partition table and boot record. If you have anti-virus software enabled, it may intercept the request to update the partition table and/or the boot record and ask you whether to allow them to be updated. If this occurs, you must instruct the anti-virus software to enable these structures to be updated. Also, when rebooting your system after converting the drive, your anti-virus software may detect that the partition table and/or boot record has changed and offer to "repair" it for you. Do NOT allow the anti-virus software to restore the boot record or partition table, or your drive and all the data on it will become inaccessible.
FAT32 Question and Answer
Will FAT32 be faster than FAT16?
In general, no. FAT32 performance will usually be about the same as FAT16, but in some cases, it may be a bit slower. Typically, there is no noticeable performance difference. The major benefits of FAT32 are that it's more efficient than FAT16 on larger disks (sometimes by as much as 20-30%), and that it can support drives larger than 2 GB without having to use multiple partitions.
Note that in real-mode MS-DOS or when running Windows 95 in Safe Mode, FAT32 will be considerably slower than FAT16. If you need to run applications in MS-DOS mode, loading SmartDrv.EXE in Autoexec.bat will be beneficial.
What should I test?
The best way to help us test FAT32 is to enable it using one of the methods described above and verify that all of your applications set up and run properly from a FAT32 drive. We’d also like you to focus on verifying that your Backup, Anti-Virus and MS-DOS mode games and applications continue to function as they did under “gold” Windows 95. If not, please submit bugs.
Can I dual boot Windows NT if I use FAT32?
In general, no. Windows NT (including version 4.0) cannot access or boot from a FAT32 drive, so if you need to dual boot Windows NT, you should not use FAT32 except on a non-boot drive that you don't need to access from Windows NT.
Will Windows NT ever support FAT32?
We are unable to comment at this time about the features of future versions of Windows NT. We recognize that this will prevent some of you from testing FAT32, and we're sorry that we can't provide FAT32 support in Windows NT at this time. Please understand that the issue is not whether we think customers want FAT32 support under Windows NT, but is strictly a matter of development and test resources and our existing release commitments. We're actively working on plans for converging file system support between Windows 95 and Windows NT (including ensuring that Win9x customers with FAT32 drives will have an upgrade path to Windows NT), but we can't make any specific commitments at this time.
Why didn't Microsoft just add NTFS to Windows 95, rather than introduce another file system?
Supporting NTFS under DOS would have taken a significant amount of very limited DOS memory and thus would have impaired the ability of Windows to continue to support games and DOS applications. Implementing NTFS without DOS support would have meant that two disk partitions would have been required: a FAT partition to boot from, plus the main NTFS partition.. To complete and test an NTFS implementation, given the sophistication and complexity of NTFS, would have taken until well after this problem had become acute. Finally, because NTFS has such a different on-disk format than FAT, FAT32 was much less likely to introduce application compatibility problems.
Is the FAT16->FAT32 converter part of Memphis?
Yes. The conversion tool will be a part of the final release version of Memphis.
How can I tell if my drive is FAT32?
In My Computer, right click the drive and select properties. The “Type” field should indicate whether a drive is FAT or FAT32.
What cluster size is used on FAT32 drives?
As with all FAT drives, the cluster size used on FAT32 drives depends on the size of the drive. The defaults are:
Drive size		Cluster size
< 260MB		512 bytes
260MB - 8GB		4k
8GB - 16GB		8k
16GB - 32GB		16k
> 32GB  		32k
These are the defaults you will get if you FDISK and format a drive using FAT32 or if you convert an existing FAT drive in place using the FAT32 Converter tool. NOTE: FDISK will only offer to enable FAT32 support on drives over 512MB.
Can I use disk compression on FAT32 drives?
No. The DriveSpace included with Memphis has been modified to recognize FAT32 drives, but it will not compress them. We do not plan to make further modifications to DriveSpace at this time. 
Can I use FAT32 on drives that are NOT visible in real-mode MS-DOS?
Yes, the FAT32 Converter utility can convert "protect mode only drives" while Windows is running. 
Relnotes for FAT32
Dual Boot and FAT32
You cannot use FAT32 on a machine that you need to dual-boot to another operating system, including the original release of Windows 95, Windows NT and Windows 3.1 or MS-DOS 6.x. Other operating systems are unable to access a FAT32 partition. This is simply because these older operating systems do not recognize the new data structures. You CAN dual boot to another operating system if drive C: is FAT16, but if you have other partitions that are FAT32, they will not be visible to other operating systems. Memphis also supports dual-booting between Memphis and older MS-DOS operating systems (e.g. MS-DOS 6.22) using the same “F4” dual-boot that Windows 95 supports, provided you are using FAT16. You cannot at this time, however, multi-boot between Windows 95 and Memphis as Memphis replaces Windows 95.
FAT32 and Disk Free Space
Some applications will be unable to display free or total disk space over 2GB, even on larger FAT32 drives. These applications show the correct free space up to 2GB, but at that point they will max out and only show 2GB. This is typically due to limitations in those applications that were written when free space could never exceed 2GB because of the previous FAT16 limitations. Memphis provides new DOS and Win32 APIs that applications can utilize to determine free or total disk space over 2GB. 
FAT32 Converter
You can convert a hard drive from FAT16 to FAT32 by running CVT32.EXE x: (where x: represents the drive letter you want to convert). After running the FAT32 converter, Defrag will run on that drive during your next boot. Defragmenting your drive after it has been converted may take several hours. You can stop the defragmenter and run it at another time, but your system performance may be degraded until you allow the defragmenter to complete on this drive.
InterLnk from MS-DOS 6
The InterLnk networking product contained in MS-DOS 6.x will not function properly in MS-DOS mode if you are using FAT32.
Ontrack Systems Disk Manager
If you use Ontrack Systems’ Disk Manager product on a system that is booting from a FAT32 drive, it may result in a long pause at boot time and/or the drive will be set to run in compatibility mode. With version 7.0x, you can use the /L=0 option with Disk Manager to avoid this pause. If you are running an earlier version of Disk Manager, you should update to at least version 7.04 and use the /L=0 switch if you use FAT32.
Syquest SQATDRV.SYS and SQDRIVER.SYS Drivers
The SQATDRV.SYS driver may cause systems containing FAT32 drives to hang during boot. Remove this driver from the CONFIG.SYS file if you are using FAT32 drives on a system with this device driver. Versions of these drivers that are compatible with FAT32 boot drives will be added to the Windows Driver Library (on the Windows CD and downloadable from the Internet) shortly.
Multiple Display Support
New for Memphis
You can use Multiple Display Support to use multiple monitors and/or multiple graphics adapters on a single PC. If you have the opportunity to install multiple PCI adapters and monitors on a single PC, you should try this feature. We think that it will greatly expand the horizons for Windows. Typical. Potential uses for Multiple Display Support are:
•	Desktop Publishing
•	Presentation Graphics (projection and presenter’s notes simultaneously)
•	Games – multiple views (simulator with simultaneous front, left and right views), or front view and status information on different displays.
•	Business – reading email, clicking on a link with the browser on the adjacent screen. 
•	Monitor walls – the feature currently supports up to 4 simultaneous displays, we may be able to expand this to 9 for a 3x3 rectangle.
People who have been using internal test versions of Multiple Display Support for the past few months love it – and say that it would be hard to go back to a single display. 
Changes for Multiple Display Support
The user interface has been modified to recognize a desktop that spans multiple monitors, with no restrictions on size or position. For monitors attached to the same system but showing different images simultaneously, the different displays might have differing X,Y resolution and refresh rates as well as differing display capabilities.
To support this capability, APIs have been added to the Win32 API set to allow any application to take advantage of multiple monitors. Applications do not need to be modified to work on a PC with multiple monitors, but some application developers may want to take special advantage of this feature by calling the new APIs. See the \BETAONLY\MDS folder for an overview of Multiple Display Support, and documentation of the Win32 API changes.
Enabling Multiple Display Support:
Enabling this feature is fairly straightforward. The primary requirement is that both of the display adapters must be PCI devices. The setup instructions vary according to the following two scenarios:
Your computer has PCI display on the motherboard and you have a second PCI display adapter to plug in.
If your computer has a built in PCI display chipset on the motherboard, follow these steps exactly when setting up Memphis:
1.	First, run Memphis Setup with only the motherboard video in the computer. 
2.	After Setup has completed successfully, shut down and add additional display adapters.
3.	Boot the computer, and restart when prompted.
4.	In control panel, display, you should notice a “Monitors” tab replacing the “Settings” tab. If you do not see this tab, see the “Troubleshooting Multiple Display Support” section.
5.	Select the secondary display/monitor combination, and select “Use this device as part of the desktop”.
Notice you can independently set the resolution and color depth for each display by selecting the settings button when the desired monitor/adapter pair is selected. Other notes with regard to systems with built in motherboard display adapters are:
•	The built in display will usually become your secondary display (or tertiary, etc., depending on the number of graphics boards you have in the system). The system will disable the onboard video at boot time, and the add-in card will become your primary display. This is a function of the BIOS and is not under our control.
•	It is important you set up Memphis for the first time with only your onboard video in the system. If another adapter is present before you start Memphis for the first time, it is likely that Setup will not be able to initialize your onboard video properly.
•	If you follow the instructions, and your onboard video does not function correctly as the secondary display, it probably never will. It’s likely that Setup is unable to find and read the complete ROM of the adapter in order to initialize it properly. You will have to use two add-in adapters for multiple monitor support.
You have two separate plug-in PCI display adapters.
If your computer’s display adapter is an add-in card (i.e., none of the display adapters in the system are on the motherboard or built-in), you have the option of installing the additional graphics cards before setting up Memphis. The instructions in the preceding section will also work.
Secondary graphics drivers that support Multiple Display Support
Virtually any graphics adapter can function as a primary display. Any PCI graphics adapter with a Windows 95 or later driver (with the noted exception of motherboard, or onboard video) can be a primary display. In order to function as a secondary display however, the display adapter must be a PCI device supported by Memphis as an additional display adapter. The following display adapter chipsets are supported as additional displays in this release:
•	ATI Mach64
•	S3 764V+(765)
•	S3 ViRGE
•	S3 Aurora (new)
•	Cirrus 5436,7548,5446
•	Imagine 128 I and II
•	ET6000
•	Matrox Millenium and Mystique (new)

These drivers have DirectDraw support
•		ATI Mach64
•		S3 ViRGE

These drivers have Direct3D support
•		S3 ViRGE

Unsupported Hardware (These chips were supported in the Developer release but have been dropped because the VGA can’t fully be disabled)
•		Any S3 < 765, ie 968, most Diamond cards
•		Cirrus 5430

Troubleshooting Multiple Display Support:
Under some circumstances you may find that you either cannot see the new “Monitors” tab in control panel, display, or you otherwise cannot use the additional display(s) as part of your desktop. Here are a few known scenarios to be aware of:
Motherboard, or onboard video
Certain problems can occur using onboard PCI video with additional displays:
•	PCI motherboard video is hidden from enumerator and may be identified incorrectly.
•	Some systems vendors hide the motherboard video from PCI when another video card is detected in the system. If plug and play can’t find the device, Setup cannot start it. If you have this particular problem, there is nothing you can do. If you look in control panel, system, device manager, and only your add-in card is present and working, this could likely be your problem.
•	Memphis cannot read the ROM from a motherboard video device. We may be able to overcome this problem for now, provided you set up Memphis without any other display adapters in the system. See the preceding section for Setup instructions.
The primary display is using the VGA driver, or a Windows 3.x driver
Again, virtually any PCI graphics adapter can be used as the primary display. However, if the driver used for the device is an old Windows 3.x driver, or the standard VGA driver, any secondary displays will not start. The standard VGA driver is used whenever the desktop resolution is 640x480 and the color depth is 16 colors.
Unsupported secondary display
Secondary displays must be PCI devices that meet certain criterion. One of these is the capability of running in “GUI” mode, or running without using VGA resources. They must also have a Memphis driver that enables them to be the secondary display. If any of these conditions is not met for any additional graphics adapters in the system, they will not work as secondary displays. See the list of supported chipsets in the section Secondary graphics drivers that support Multiple Display Support: 
Shell Support: The current shell does not fully support multiple display monitors. You can only position the taskbar and desktop icons on the primary monitor. This support will be in the new shell that will be enabled in the next beta release. You will then be able to dock the taskbar on any monitor border, and place desktop icons on any surface.
Application Compatibility: Please file bug reports on any applications that do not behave properly when using multiple display surfaces.
Adobe Type Manager: Adobe Type Manager (ATM) is not compatible with multiple display support.  When ATM is installed, multiple display support is disabled.
Full Screen MS-DOS boxes: These will only display on the primary display (the “VGA” display.
DirectX Applications: Full screen DirectX applications will run normally. Windowed DirectX applications (such as Activemovie) will not display across two displays simultaneously at this time. This will be fixed in a future beta.
Win32 Driver Model (WDM)
The all-new, unified driver model for Windows 95 and Windows NT. WDM enables new classes of devices and busses to have a single driver for both operating systems, by adding selected Windows NT Kernel services in a new NTKern.VXD, while maintaining full legacy device driver support for existing device drivers in existing code.
USB Support
Includes support for USB hubs, Universal and Open host controller interfaces, and HID compliant USB devices (see Human Input Devices (HID)). The new WDM Stream-class support in Memphis provides infrastructure for USB audio and camera devices.
Human Input Devices (HID)
Keyboards, keypads, mice, pointing devices, joysticks and game pads that are compliant with the Human Interface Devices (HID) Firmware Specification Version 1.0 are automatically supported by Memphis when connected via the Universal Serial Bus (USB). Input data from these devices is routed to applications through the legacy input driver architecture in a totally transparent way. Multiple keyboards can be connected and used simultaneously, but the multiple input streams are merged and passed to the single active application window in focus. Similarly, multiple mice and pointing devices can be connected and used simultaneously, but the input streams are merged to control the movement of the single pointer on the screen. Joysticks and game pads, however, are treated as distinct devices just as can be expected so that applications can distinguish which input comes from which device, or user, and react appropriately.
Memphis does not automatically support devices that implement HID functionality that goes beyond the capabilities of the input device types listed above (e.g. virtual reality devices, simulation devices, monitors, power devices, etc.). These device types require additional vendor-supplied and device-specific software (e.g. drivers, special applications, etc.) to be installed on the system. Device vendors and developers should consult the WDM DDK for details.
To get USB game devices to work on a machine that’s NOT equipped with a legacy game port or sound card, the following steps must be followed – after you have installed this release of Memphis - to ensure that all required files get installed properly:
1.	open the Control Panel (Start/Settings/Control Panel),
2.	double-click on the Add New Hardware icon to launch the Add New Hardware Wizard, then click on the “Next” button,
3.	select “No” to “Do you want Windows to search for your new hardware?” and click “Next”,
4.	select “Sound, video, and game controllers” as the hardware type, and click “Next”,
5.	select “Microsoft” as the manufacturer, and then select “Non-Gameport joystick” as the model, click “ Next”, and then click “Finish” to complete the installation of the Microsoft Non-Gameport joystick.  

This release of Memphis supports devices that are compliant with the final HID 1.0 Specification (Version 1.0 Draft #4), as well as earlier 1.0 drafts (#2 and #3) for backwards compatibility reasons. The final HID 1.0 specification is available on the USB Implementers Forum Web site at http://www.usb.org.
IEEE 1394
Support for the IEEE 1394 bus includes the 1394-bus class driver, and mini-drivers for both the Texas Instruments PCI-LYNX, and the Adaptec 8940 200Mbps host controllers. A Stream-class driver for the Sony desktop camera (CCM-DS250) is also provided.
The following contact information is provided for those interested in testing Memphis 1394 support:
Adaptec contact information:
1394@corp.adaptec.com, http:// www.adaptec.com, (800) 442-7274
Texas Instruments contact information:
MikeField@tx.slr.com. http:// www.ti.com/sc/1394, (800) 317-8354
IEEE 1394 networking
A driver is provided for running IEEE 1394 networking. You can run the Microsoft networking stack when you connect two PCs with IEEE 1394. The driver can be found in the directory drivers\netlan\ndis1394. There are some limitations to this version of the driver.
•	This is a beta only driver and may not be included in the final version of Memphis.
•	It currently only works for the case of connecting two PCs together with IEEE 1394. It does not support more than two PCs connected.
•	It currently does not work with two PCs of which the two IEEE 1394 host controllers in the PCs are different.
•	It does not currently support hot plug and play.
WDM Digital Audio
This version of Memphis contains support for audio over USB speakers. During the test period from now to release, speakers will be available to Memphis beta testers from Altec Lansing Multimedia and Philips Semiconductors. Specific details on how to order these speakers can be found in the \betaonly\usbspeak directory on this CD. The altec directory contains the file Altec.doc. To see the offer from Philips, point your web browser at philips.htm in the philips directory.
If you are not planning on testing USB speakers, this note should not be of use to you. Conventional sound cards that operated prior to Memphis should continue to operate exactly as they did before Memphis. The bugs and features listed below should be of no relevance to systems with conventional audio systems installed. 
The code is under intense development at Microsoft and will be evolving in future releases. Many features are not yet implemented and the only USB audio devices supported are those made available with this release.
As of this release audio is output only. No record capability has been implemented.
WDM audio includes a software emulator for DOS games running under Memphis that provides an interface that emulates the Sound Blaster 2.1 hardware. There will be no support for real-mode DOS Sound Blaster register sets for USB audio. DOS games will run in ‘DOS Boxes’ (DOS virtual machines that run under Memphis). Some games will not run in DOS emulation mode. At this time we do not have a list of which games will and will not run in DOS emulation mode.
The current emulation only supports monaural 8-bit audio. Future versions of Memphis will emulate the Sound Blaster Pro interfaces. This is also known as Sound Blaster 3.2 and features stereo audio.
OPL-2 and OPL-3 music synthesis is not emulated. These are the FM synthesis chips manufactured by Yamaha. The OPL-2 was used in the Adlib and Sound Blaster boards. The OPL-3 is used in Sound Blaster Pro and Sound Blaster 16 hardware. Emulation of these music synthesis chips is not now and will not in the future be supported by USB audio.
The MPU-401 is a music synthesis hardware interface defined by Roland. Most recent DOS computer games support this register interface for generating music. The MIDI emulation today supports General MIDI wavetable music synthesis.
Normally RedBook or CD audio is supported by sending a command to the CD drive that causes the CD to play audio with an onboard DAC. This DAC is connected to the system sound card that controls volume levels. This is impractical for USB audio so Memphis reads bits off the CD over the computer interface (SCSI or ATAPI) and sends them out to the USB speakers.
Few CD drives are supported today. More drives will be supported in the future. Today we do not identify which drives work and which do not. This will be fixed in future versions of Memphis.
Normally CD-audio will play out headphone jacks on the front of the CD drive. Usually there is a volume control near the headphone jack. Playing audio through this headphone jack is not supported in this version of Memphis.
Most Windows applications use 16-bit APIs to play audio. These APIs will be supported exactly as they have been in earlier versions. Today only audio playback is supported.
The mixer is used to set volume controls. This API is not supported in this release of Memphis; however, the mixer is implemented. For example, CD-Audio, wavetable music synthesis, and 16-bit Windows applications can all play through a USB speaker simultaneously.
DirectSound is not supported for USB audio in this version of Memphis. The released version of Memphis will support DirectSound 5. Beta versions of Memphis will support Direct Sound 5 as it becomes available.
ActiveMovie is the preferred 32-bit API for audio. ActiveMovie is supported natively by USB audio. This is the native mode for USB audio support.
DirectMusic will be the preferred music interface to Windows. Future versions of DirectMusic will support downloadable samples. As beta versions of DirectMusic are released, USB audio will support them. Today MIDI under Windows is supported by USB audio in the form of the 16-bit MIDI APIs.
MIDI in is not supported in this beta version; only MIDI out is supported. Patch caching is not supported, but it will become an important memory optimization feature of future releases of Memphis.
Wavetable music synthesis is supported with kernel resident software. The quality is better than earlier FM synthesis hardware. System latency will be improved in future releases.
DVD Storage and UDF File System
DVD-ROM drives as a storage media are being supported for the first time in Memphis. In order to be able to use a DVD-ROM drive, you must have a drive that is compliant to the Mt. Fuji specification (also called SFF8090). The CD-ROM class driver that existed in Windows95 has been updated to support DVD-ROM drives as well.
We also have a new file system, called UDF (Universal Disk Filesystem). It is currently a read-only file system; you can not write UDF to a disk. This is implemented because DVD movies will always have a UDF file system on them, while they may or may not have an ISO9660 file system on them. You can tell if you have UDF support installed on your system if you have the binary udf.vxd somewhere on your system.
All DVD-ROM drives are required to support DMA. You will have to enable this on your own for now. To enable support for DMA, please go to Device Manager, select properties of the drive, check the DMA box presented, and reboot to run on DMA.
DVD Movie Playback
DVD movie playback requires the following components:
Hardware:
•	DVD-ROM drive
•	DVD movie media
•	DVD (MPEG/AC-3) decoder
Software:
•	DVD storage support
•	WDM Stream class driver
•	Stream minidriver specific to your decoder hardware (not written by Microsoft)
•	ActiveMovie filtergraph specific to your decoder
•	DVD Movie playback application
The above list will allow DVD movie playback on a NTSC or PAL display, if the decoder card has such an output. If output on a VGA is desired, then there should be a physical connection between the decoder card and the graphics adapter, and a DirectDraw HAL with VPE support should be written for the graphics adapter.
There is the possibility for the decoders to be in software rather than hardware on faster processors. If you are interested in help on your stream class minidriver, please talk to your Microsoft contact about visiting the WDM porting lab to further your efforts.
On the WDM DDK Preview, there is a test application for DVD movie playback in the \betaonly\dvd directory. This can be used to try movie playback on your PC. Microsoft is not yet providing DVD movie content. 
WDM Still Image Capture
Memphis contains support for scanners and digital still cameras. This support includes kernel components for SCSI, USB, and serial devices. There is a new control panel for integration and configuration of scanners and cameras. Support for “push mode” image acquisition has been added. This allows devices with buttons or paper detect switches to launch an application and start the process of getting an image from the device. The control panel allows the user to configure which applications respond to the devices events.
WDM Video Capture
WDM video capture provides backward compatibility for VFW applications without the shortcomings of VFW. The goal of WDM video capture is to provide support for: USB conferencing cameras, 1394 DV devices, and desktop cameras, TV viewing, multiple video streams support, and VPE capture support. It is based on kernel streaming architecture, and tightly integrated with Active Movie 2.0. The following Active Movie Filters are provided in the DDK for WDM capture: 
•	KsCap.AX: the main capture filter. This is the main proxy filter between the stream class drivers and Active Movie filters. It provides a standardized connection and streaming in the kernel, standardized property sets, standard way of controlling stream flow ( start, stop, run), and a standard way of exposing data formats.
•	KsTVTune.ax: TV Tuner interfaces. It handles channel to frequency mapping, worldwide frequency tables, multi-standard tuners, support for fine tuning methods using: PLL, signal strength, or Driver specific methods.
•	KsXBar.ax: A/V crossbar. This is a general signal router for: analog or digital (VPE input) video or audio. It provides a MxN general switching matrix, and allows any output to be connected to any input.

These filters can be used with Active Movie Graphedt.exe application (provided in the DDK). Also, included is a test application (captest.exe) that build a customized filter graph which utilize these filters, and connects to a WDM video capture mini driver. 
PCMCIA
PCCard16 now supports 3.3volt & multi-function (i.e. net/modem) cards.
PCCard32 (CardBus) now supported.
Power management for PCCard Modems is now supported. These devices are put in a low power state when software is not actively using the modem. See the power management section for more information.
Cardbus Release Note:
If you are using Cardbus support, the SubVendorMaskID is not being processed correctly.  This will only affect users who plug in cardbus cards that are from different vendors, but use the same core chipset.  For example, if a Cardbus user first inserts a DEC 21143 chipset Ethernet Cardbus card (SMC, Xircom, TDK, Toshiba ) into a laptop it will work fine.  If, however, you insert a second DEC 21143 based device from another vendor, it will have problems being identified and correctly functioning because Memphis will not load the correct driver.  Results vary depending on the controller, but the user could see Code 10 in device manager, or the driver loads with the wrong name of the card (the last card, or closest registry entry left over name will show). 
The workaround is to remove the 1st cardbus card from device manager or remove the entry from HKeyLocalMach. \Enum\PCI ( the card(s) left over) and then the next cardbus card will work without a problem.

Power Management and OnNow
New Power Control Panel Schemes
The new control panel features power schemes, which are groups of power settings optimized according to computer use.
ACPI
Memphis contains basic ACPI support, to enable PC Manufacturers to begin testing their prototype ACPI systems.
Supported ACPI features
The ACPI driver now supports the following:
•	Legacy ACPI select
•	PM timer
•	System states S1-S3, and S5
•	CPU states C1-C3
•	Thermal Model (active & passive cooling)
•	Configuration of devices (_PRS, _SRS, _CRS)
•	Device power management of the USB host controller
ACPI Questions & Answers
Answers to frequently asked questions about how Microsoft operating systems interact with ACPI as well as ACPI development tools and tests can be found at:
http://www.microsoft.com/hwdev/onnow.htm
Questions regarding ACPI on Memphis or Windows NT should posted to the memphis.DDK.ACPI beta newsgroup.
Suspend button & the Start Menu
Memphis seeks to encourage people to put the computer to sleep instead of shutting the computer off. One of the ways it does this is by moving Suspend from the Start menu to the Shutdown dialog box. 
However, there’s a bug currently that prevents the sleep option from being shown on the Shutdown dialog box. We are working on this bug and hope to have a fix shortly.
(Note: this requires the new IE4 shell, so it is not visible in the current build).
APM 1.2 Extensions
•	New APM 1.2 services
•	New Power Management control panel user interface (including IDE drive spindown user interface)
•	New battery meter
Disk Spindown
Reduces power consumption, drive wear and low noise. This may cause a slight delay in system response when the disk needs to spin back up. You can control the power down delay as well as disable disk spindown in the Power Management control panel. Typical settings for desktop machines are 30 to 60 minutes.
Release Note: Some older systems may hang when the disk is spun down or back up. You should disable disk spindown on these systems. 
PCMCIA Modem Power Down & Resume on Ring
Power management for PCCard Modems is now supported. These devices are put in a low power state when software is not actively using the modem. Look in the Power management control panel to control this feature. 
Modem Power-Up Delay
If you get a message Modem Not Found or Not Ready, you may need to increase the modem power up delay. The default delay is 2 seconds. 
Some PC Card modems require an extra delay when PC Card Power Management is enabled, before they are ready. You may be experiencing this if the modem doesn’t respond on the initial try, yet works if you immediately try again.
If you encounter this with your PC Card modem, increase the delay. To do this, you can either Disable PC Card Power Management in the Power management control panel, or you can add a Registry key using Regedit:
	1.	Navigate to the key:
\HKey_Local_Machine\System\CurrentControlSet\Services\Class\Modem
	2.	Go to the key for the modem that you are trying to use, and add a key in the root of the modem key.
	3.	Edit / New, create a DWord named ConfigDelay 
This value is in milliseconds. Set the value equal to "3000" for a 3 second delay. Experiment to get enough delay.
Please submit a bug with the delay necessary for your modem, and your computer manufacturer and model information, and we will add this to our list.
Device Drivers
Display
These are DirectX 3 and/or DirectX 5 drivers, with multiple display support enabled.
New for Memphis: Tseng ET6000, 3Dfx VooDoo, 3Dlabs Permedia, Chips 6555x
Updated for Memphis: ati3d, chips, cirrus, cirruslg, cirrusmm, i128, mach64, mgamm, rendition, s3mm, s3v.
For more technical documentation on Display Drivers - see the DirectX DDK.

Display Driver Release Notes:
The ATI Rage/Rage II driver has been removed from the build. We are working with ATI to get a stable driver to release Memphis. Users may go to ATI's web site to download their latest drivers.
The following list of issues have been observed in the current driver set.
3Dfx VooDoo Graphics
====================
3Dfx:   Sporadic hang in 3Dfx running Monster Truck Madness
Blt from system memory to video memory on 3Dfx is broken
3Dfx Locks in 3D Tunnel (infinite loop)
DX5 build084 - Cannot decrease video modes in Rockem with 3DFX card
3Dfx: Implement DriverGetAvailMemory callback
3DFX: Out of Vid Memory in Rockem destabilizes system: Crash in Twist
BLT from secondary to primary surface is incorrect on 3Dfx device

3DLabs Permedia
===============
3d Labs Permedia white bar flashes at top of screen in Hellbender
3D Labs Permedia - D3D Tunnel gets corrupted after task switching
3D Labs Permedia - DCT reports that modes are failed by the driver
3Dlabs Permedia - menu shows through Hellbender in low-res modes.
Permedia - Textures are lost when pixel format is changed.

ATI Mach64 / Rage
=================
ATI Rage II: 'Optimal' & 'Adapter Default': no difference in refresh rate
ATI (mach64) Hi-Res Setting Results In Static Screen
ATI Rage II does not work with TV tuner with our drivers
rockem fails to attach z-buffer to back surface with RAGE-II drivers installed
RageII drivers do not export dwZBufferBitDepth
ATI Rage 2 - Globe causes trap 14 in ATI_D3D.DLL
ATI Rage 2 + driver fails rate test
ATI Rage 1 - Culling order is broken in 3D Twist
Changing color depth from 16 bit to 256 still crashes Windows
MM_DXAPP: Regress Installing Road Rash reports display driver no hardware support ati rage 3d
ATI Rage 1 has no textures in hal mode with 3d tunnel and 3d flip cube in 640x400x32
ATI Rage2: Toggling to/from full-screen in Dos box causes debugger to break in Win95 debug:
ATI Rage II - 3D Globe puts static on the desktop when running in HAL.
ATI Rage 2 + does not display 3d flip cube on screen correctly at 1024x768x16
ATIM64: Black printed as red to clipboard by disptst
ATI Rage 1 has broken mode with tunnel

Chips 65548, 6555x
==================
Chips 65554 driver validates invalid mode 1280x1024x24
Chips Tecra F65550 has broken foxbear modes when desktop is 800x600x24

Cirrus
======
Nec: Ne2 & Nd 24bpp True Color is black
Advanced Display Properties error may occur with Cirrus Logic 5434 PCI video card.
Cannot set correct refresh rate on Cirrus Logic GD5434
Cirrus: Lines & dots on display
Cirrus Logic 5440 is not able to obtain 1024x768x16

Cirrus Laguna (cirruslg)
=============
CL5464(LG):  mov has distortion when moved in window
CL- 5464- Lor switches display to 512x384x24bpp and scrambles display.
CL laguna fails case 26 of (Tddraw) test
Cirrus LG 5464 - Ratetest reports 7 failures.
Cirrus Laguna 5464 - Colors are very wrong in 8 bit RGB emulation.
Cirruslg, 5464, Fail BLT shrink(1/2) Vmem to Primary, 16bpp
CL laguna fails case 19 of (Tddraw) test
2DFlipCube, Cirrus 5464, Right Half of Screen Not Being Refreshed at 512x384x32
Cirrus 5464, Foxbear, Jittery Screen after Alt-Esc
CirrusLG, 5464, MOV, Right Click Popup Menu Offset with Green Line
CirrusLG, 5464, MOV, Trashed MOV Following Alt_Tab From DosBox

Cirrus Memory-mapped (cirrusmm)
====================
System page-faults when trying to set settings for 2nd display/monitor.
Cirrus 5434, 3DTunnel Locks, 320x200x8
Cirrus 5434, Links386, Duke3D, Will Not Return From Windowed(Alt-Enter) Test
CirrusMM 5446 has corrupted desktop problems with driver in build
Movie flickers when playing in ActiveMovie 1.0
Cirrus 5434 2M PCI has display problems on desktop at 32bpp
Cirrus 5446, Foxbear, 800x600x8/16, Incorrect Paint Along Bottom Edge
DISPLAY: Cirrus Logic 5446 PCI using Direct Draw 1.00 having problems
CIRRUS 5446: 512x384x[16 | 24] modes do not sync to PnP monitor (Sony 100sx)
CirrusMM Logic 5434 PCI fails ratetest
Cirrus mm and nec power vr trap 14 when running 3d flipcube
Casino CD: changing resolution causes lines accross the desktop and the casino screen

Tseng ET6000
============
Tunnel in RGB with Textures is Corrupted in all modes
fails many areas of RateTest
fails two areas of Tddraw and distorts desktop
GPF@vdd:_LGROUP:VDD_Int_Set_CanRestore + 117
Vertical Blank status fails and then faults
Links and Duke 3D loose sync when windowed - fullscreen
Mode switch to 1600x1200x8 fails
Running Charmode leaves driver spinning in an infinite loop.
Problems with default refresh rate at 640x480 on STB LightSpeed 128.
wrong colors with overfly test with 32bit and desktop mode 640x480x8

Number Nine Imagine 128
=======================
movies play with distortion and behave strange @ 32bpp
Low power hangs machine
Rotating SETUP.BMP by 270 results in black picture
DispTest causes blue-screen warning from Windows
Mouse pointer changes color after suspend/resume

NeoMagic
========
NeoMagic128zv hangs when dragging dos box windowed in vmode 12

Rendition Verite
================
V1000-E - Mouse pointer does not work correctly in 2D Flipcube.
V1000-E - Ratetest locks at 640x480x32bpp @ 120hz.
Hellbender, 320x400, Locks at Full Screen
V1000-E plays and loads Hellbender in upper-left corner
Win95 hangs at boot if Rendition changed to custom refresh rate.
V-1000E - Driver in build 1421 not certified!
Ignores color key on DirectDraw destination color key blts.
Rendition: Problems with combined Stretch/Source color key blts in 32bpp modes.
LoadTexture on Rendition cause windows to stop painting
Vertie 1000 creative labs has IMMORTAL kLOWNS  has pallete problems

S3 (s3mm)
==
S3 765 (on board) has distortion when running @ 1024x768x8
S3 765 on board IBM 350-P90 locks windowing dos box during directory scroll in vmode 12
S3 765 on board IBM 350-P90 locks during character mode test (DCT)
S3MM fault while testing background wallpaper during Lor run
S3 968 has bltting problem in Doom95
Video Driver: S3 Trio64V2(DX/GX) coming up code 24 in devman
964 After install some systems lock up that a NMI board can't break into rterm
Visual failure in DCT Transparent Blt test
964 trap 14 when running DCT character mode test
S3765/MultiMon: machine locks when switching to full-screen playing an AVI

S3 ViRGE
========
S3 VIRGE:  APP:  Asymetrix 3D FX locks machine when rendering scene
Multi-mon - dragging boxes diagonally across screens distorts them.
DirectDrawCreate on the S3 Virge when in 1024x768x8 causes weird screen effects
VX STB has broken modes in 2D flipcube 320x200x16 800x600x24 1024x768x16 1600x1200x8
Overfly pallete is distorted in 24bpp RGB surface type.
Visual failure in DCT Transparent Blt test
Ratetest fails 2 tests.
Running BOIDS, parts of the BOID disappear sometimes (wings) while it is flying
TRI5.EXE caused a hang in S3V.DLL + 1acd6
3D Flipcube caused trap 14 in S3V.DLL + ADC6
Has various problems with lines
Incorrectly rendering triangles with non-flat Z values
320x200x8, 320x240x [ 8 | 16 ] modes corrupt
Releasing overlay surface results in system hang
Tddraw&Ratetest hit INT01 in VMM(08) + 426
Does not set the BLENDENABLE or ALPHABLENDENABLE renderstates

Trident
=======
FE-N: Display incorrect on "R2".
TGUI9682 has Active Movie problems when changing from full screen to windowed
T9680&T9440 bllting problem in Doom95
T9685 dos box will not toggle to/from window with foxbear running in background
Trident on board Aptiva will not go above 640x480
9440 - Trap 13 on boot DISPLAY:_TEXT:_GetRefreshRateSupport + 165
9680 & 9685:  validate invalid mode in rate test
9320 has problems with 3d flipcube in modes 800x600x8 640x480x8
9680 - Fails BltFast SRCKEY, From/to same surface
9680 has broken modes in 3d flipcube 320x200x8 320x240x8 640x400x8 640x480x8 800x600x8 1024x768x8 1280x1024x8 320x200x16 320x240x16 1024x768x16
T9385,T9440,&T9685 playing multiple movie clips causes remnants to appear at top of screen
9320 in IBM Laptop, Trashed Full Screen DosBox With Windowed Foxbear, AVI, MPG or MOV
Audio
Updated Audio drivers from DirectX 3, and an updated Windows Sound System driver from DirectX 5. Full DirectX 5 support will be in the next release.
Modems
Approximately 300 new modems are supported, to bring Memphis up to compatibility with Windows NT 4.0. We’re now starting to add the current crop of new Modem drivers, which will be available in the next beta.
Printers
Look for new updated driver support in the next beta. This release includes the drivers that shipped with Windows 95 OSR-2.
Network Card Drivers
New Support for Network: 170 Adapters
Adapters Affected by Updated Drivers: 198

NDIS 2.0 Functionality...
As a result of upgrading the netcard driver support for 'Memphis,' some drivers such as the Intel EtherExpress 16 and Intel EtherExpress PRO/10 are available only as NDIS 3.x 32-bit protected-mode drivers.  In those cases, NDIS 2 real mode drivers can usually be found on the netcard manufacturer's Web site.  They can be installed by downloading, uncompressing to an empty directory, selecting "Have Disk" and pointing to that directory.

Diamond Multimedia ISDN Adapter
It is strongly recommended not to install the Diamond Multimedia's ISDN adapter drivers into Memphis. During installation Diamond's setup will prompt for the location of Microsoft's ISDN Accelerator Pack 1.1.  Installing ISDN 1.1 on top of Memphis will break all of Memphis's networking components.  This issue will be fixed for Beta 2.  If you need this adapter to work under Memphis please contact Diamond Multimedia's Support Center.
Disk Drives
Floppy Disk Driver
Memphis includes an all-new “HSFLOP.PDR” floppy disk driver. This new driver offers significantly enhanced performance on many machines. It should also work on some portable machines that required custom HSFLOP.PDR files in the past. This new driver should work on 100% of all known hardware. If you encounter problems with this new code, please report as soon as possible. 
Relnote: The current version will hit the floppy disk on boot; this diagnostic test will be removed for the next beta.
LS 120 Support
The real mode MS-DOS kernel, protect mode file system components, and the various formatting utilities have been updated to support the LS-120 (120MB) floppies built in to some newer PCs.
IDE Disk Driver
This is an updated IDE hard disk driver that includes support for: 
•	Bus Mastering chipsets such as Intel Triton and Opti Viper M
•	SMART (Self-Monitoring Analysis and Reporting Technology), a hard-drive fault prediction system developed by Compaq and several hard drive vendors
•	IDE Tape backup units
•	ATAPI-CD-Changers (with up to 7 CD slots), including the Sanyo/Torisan 3CD changer
Bus Mastering
Caution: Some hard drives which were originally designed to support this DMA functionality were found during joint Intel and Microsoft testing to contain firmware bugs which can cause data corruption. Only OEMs should enable the DMA feature when they ship compatible hard disk drives. End Users should not enable the DMA feature on their PCs if it was not enabled originally by their PC Manufacturer.
Notes
•	Bus Mastering should only be enabled for specific hard drive models that are certified by their manufacturer to work properly with a Windows bus master driver. 
•	The drives in question must indicate that they support DMA in the drive ID data (both ATA and ATAPI drives).
Go to the System Control Panel, Device Manager, select the individual Disk Drive (not drive controller), and select Properties. If a checkbox for DMA shows up under the Int13, then you can try the Bus Master DMA transfers. If no checkbox appears, then your motherboard chipset does not support a compatible bus master interface. If the checkbox is not checked after your system reboots, then your hard drive probably does not support bus mastering, and it has been automatically disabled again.
CD-ROM-Changers
CD ROM Changer support is now available for ATAPI-CD-Changer compliant CD ROM drives with up to 7 CD slots. CD ROM devices with more than 7 slots are generally considered “CD Jukeboxes” and are not supported with these drivers. This driver set also includes support for the Sanyo/Torisan 3CD changer.
Note: There is one known issue regarding the new CD+ format. CD+ at present only works properly on the first assigned drive letter. CD+ audio will not be recognized on CD+ discs in slots not assigned to the first drive letter (for example, on a system that has letters assigned to D:, E:, F:, and G:, CD+ audio will only play on drive D:). This does not affect standard Audio CDs.
CD Disk Driver
CDFS.VXD and CDVSD.VXD have been updated as follows:
•	ISO-9660 format CDs greater than 4GB in size are now supported
•	CDFS Read ahead behavior is now more intelligent, to better support slower hardware and applications that access the CD randomly
•	CDI disks are now supported (with appropriate application software)
Known Disk Driver Issues:
There is a problem with the Future Domain 18xx SCSI controller using the FD16_700.MPD driver in Memphis build 1423.  User must go back to older version to work.
Monitors
We’ve added approximately 175 new monitors to the built-in list. 
Human Input (Keyboards, Joysticks, Mice, Game pads)
Look for new drivers built-in for these devices in the next beta release.
Scanners and Cameras
Memphis includes support for the following scanners and digital still cameras.
•	Hewlett Packard SCSI SCL flatbed scanners including the 3c, 4c, 4p, and 5p. The 5p includes support for push mode scanning. The TWAIN data source and PictureScan or DeskScan software required to use the scanners via a TWAIN application are not included in this release. If these components are already installed before an upgrade to Memphis, they will be used. Otherwise the HP software will have to be installed.
•	Kodak DC-25 digital still camera. The TWAIN data source is included in this release. To add a Kodak camera, you need to use "Add New Hardware" in the control panel. Do not do the hardware detection and select the cameras and scanners category. Then select the Kodak DC-25. In this release the machine must be rebooted to enable the use of the DC25. 
•	Logitech PageScan USB sheet fed scanner. Support includes the TWAIN data source. This scanner also supports push mode scanning.
Memphis support for scanners and cameras includes “push mode” operation. Applications needs to be revised to take advantage of this functionality. The Eastman Kodak “Imaging for Windows” application in Memphis now operates in push mode. To enable this for a device the application must be run at least once. For the Memphis HP 5p or Logitech PageScan USB scanners, use the “Scanner and Camera” control panel to associate the Imaging application with these devices’ push mode events. The property page for these scanners contains an “Events” tab. Once an application has registered itself as “push mode ready” it will appear in the application list in this property page. Simply check the Imaging application and it will be launched when the buttons on these devices are pressed. In this release only one application can be selected in this application list.
Video Capture
Look for new drivers built in for these devices in the next beta release.
IrDA Device Drivers and Utilities
Support for Fast Infrared (FIR) and Serial Infrared (SIR) devices, easy file transferring over Infrared and LAN connectivity. This beta release includes infrared support up to 4Mbps. It includes the Microsoft Infrared Transfer applet that makes file transferring over infrared as simple as click and send. To enable infrared support, perform the following setup steps:
	1.	Go to Control Panel
	2.	Start Add New Hardware
	3.	Select “No” when the Add New Hardware wizard prompts you to have the system automatically detect any new hardware, and click Next.
	4.	Select “Infrared” device and click Next.
	5.	When the wizard prompts you to choose a manufacturer’s name for your IR device, choose “Microsoft (Standard Infrared Serial Port)” if you have a computer with a SIR infrared device, or choose the name of the manufacturer and the model of the computer if you have an FIR device.
For SIR device:
	1.	If you have a SIR device, choose “Generic Infrared Port” for built-in infrared port; or choose the name of the manufacturer and the model of the adapter if you have an external Infrared adapter connected to your computer.
	2.	When the wizard prompts you to choose the communications port that the IR device is physically connected to, click the port from the list. If you are not certain which physical communications port the IR device is using, make your best guess. 
	3.	When you are done with the wizard, click the Finish button to complete the IR device installation. The wizard should have briefly displayed New Hardware Found messages. If the wizard did not display these messages, then restart the computer.
	4.	Activate the IR device by clicking the Start button, pointing to Settings, and then clicking Control Panel. Double-click the Infrared icon. If you chose the correct port in Step 2, the Infrared Monitor interface screen appears. If you did not choose the correct port, a message appears telling you that the port you have chosen is being used by another program. Click OK. Right click the Network Neighborhood icon on desktop and choose Properties. Select “Standard Infrared Serial (COM) port” and click Properties. Click the “Advanced” tab, and select “Serial Port” to change the COM port settings. Repeat this step until you have chosen the correct port.
For FIR device:
	1.	If you have a FIR device, contact your hardware manufacture to get the driver for that model of the computer. Click “Have Disk” to install the FIR driver, supplied on a floppy disk by the manufacturer. 
	2.	When you are done with the wizard, click the Finish button to complete the IR device installation. The wizard should have briefly displayed New Hardware Found messages. If the wizard did not display these messages, then restart the computer.
	3.	Activate the IR device by clicking the Start button, pointing to Settings, and then clicking Control Panel. Double-click the Infrared icon.
Microsoft Infrared Transfer
To use the Microsoft Infrared Transfer, simply right-click the file you want to transfer and select “Send to->Infrared Recipient”. 

Under the Hood
The following are some ongoing changes “under the hood” that you can’t really experience. 
Registry Improvements
We’ve rewritten the Registry handling code to be faster and improve robustness. The in-memory data structures are more optimized. You won’t see any changes in the Registry structure as exposed through the APIs or Regedit. But how it’s handled in code has been significantly improved.
Power Management 
Power management improvements throughout the system in User, device drivers, network stacks, and many other places should improve the power performance, and enable the ACPI machines to work even better.
Internet
Internet Explorer
Memphis will include Internet Explorer 4. However, we have not yet integrated the new Internet components into the product. In the meantime, we are including the same Internet Explorer 3.02, the latest version with the security updates. IE 3 advanced the state of the art for web browser technology with support for Frames, ActiveX components, Visual Basic Script, Java, JavaScript, Netscape Plug-ins, HTML 3.2, Cascading Style Sheets and many more features.
For more information about Internet Explorer 3 please visit the web site at:
http:// www.microsoft.com/ie
Note: For your convenience, we have included an IE 3.02 self-installing EXE in the \betaonly directory on the CD. 
This release of Memphis contains the current release of Internet Mail and Internet News, build 1161.  However, you will have to manually install it from \betaonly\imn. For more information about Internet Mail and Internet News, including FAQs, links to newsgroups, bug reporting, and other information, please visit our web site at:
http://www.microsoft.com/ie/imn/default.htm 
Notes on IE 3 in Memphis when installed over IE4:
If you have a build of Memphis with IE4 installed, such as any build 14xx build, then you MUST switch to the “classic” shell prior to installing Memphis.  If you do not, then you must follow these steps to restore your IE 3.02 browser:
1.	Exit to MS-DOS
2.	Delete \windows\system\wininet.dll and \windows\system\urlmon.dll
3.	Restart Windows, and double-click on “msie302.exe” in the \memphis directory of your CD.  Allow IE 3.02 to reinstall and then reboot.
If you are running IE4, and install Memphis, you can recover your favorites by doing the following:
1.	Boot into Safe Mode
2.	Open an MS-DOS prompt
3.	Go to Favorites in the Windows directory
4.	xcopy *.* /e /s /c <to somewhere> (save your existing favorites)
5.	Then Deltree Favorites (eliminate the old directory)
6.	MD Favorites (create it fresh)
7.	Re-xcopy everything back using the same command
8.	Shutdown & re-start - they should be up & functional
Microsoft Internet Mail and News
You will need to reinstall Internet Mail and News from the \betaonly\imn directory with this version of Memphis.
Note:
If you were running Outlook Express (IMN 2.0), you will still have some dead shortcuts in your start menu after installing Memphis.  These are harmless.
If you were running Outlook Express, you may need to manually set the message store location to point to \Program Files\Outlook Express\Your Name to access your Outlook Express mail.  You may get a “Store Corrupt” message, and the folder names and hierarchy may be gone, but you should be able to access your messages.
NetMeeting
This release of Memphis contains the final release of Microsoft NetMeeting™ version 1.0. Microsoft NetMeeting conferencing software is a standards-based, multipoint data conferencing product that supports application sharing and real-time voice communications over the Internet and corporate intranets. Features of NetMeeting 1.0 include multi-user application sharing, whiteboard, file transfer, chat, shared clipboard, and point-to-point audio conferencing. 
The \Betaonly\Nm20 directory of this Memphis CD contains the final release of NetMeeting 2.0, which adds standards-based audio and video conferencing and other enhancements, such as user interface improvements.
For more information about NetMeeting, including FAQs, links to newsgroups, bug reporting, and other information, please visit our web site at:
http:// www.microsoft.com/netmeeting
For direct newsgroup access,  you can find NetMeeting discussions on:
	Server: msnews.microsoft.com
	Newsgroup: microsoft.public.internet.netmeeting 
Please report NetMeeting bugs directly to the NetMeeting team using the web site:
http://www.microsoft.com/ie/support/msnetmtg.htm
Note on Application Sharing: In this release of Memphis, the application sharing feature in NetMeeting 1.0 does not work. Application sharing will work with NetMeeting 2.0.
Internet Connection Wizard
The Internet Connection Wizard (ICW) provides Windows users with all the functionality necessary to get their desktop connected to the Internet. With ICW installed, a user can easily configure their machine for Internet communication, sign up for an account with any participating Internet Service Provider of their choice, and setup any custom software required by that provider.
If you do not currently have an Internet account, the first setup option is a good way to choose an Internet Service Provider that offers a flat monthly rate, which you may find useful while participating in the Memphis beta program.
The ICW is automatically run when launching Internet Explorer or The Microsoft Network icons the first time a new PC is booted or the first time following an upgrade.
The Wizard consists of the following three options:
•	I want to choose an Internet service provider and set up a new Internet account will configure your machine for dial-up access to the Internet and enables you to sign-up for Internet access via an ISP account using the Microsoft Referral Server program.  If you sign up for an account using the ICW and Referral server, you will be liable for the charges imposed by the Service Provider.
•	I want to set up a new connection to my existing Internet account using my phone line or local area network (LAN) allows you to hand-configure your Internet settings for use with an existing ISP or local area network.
I already have a connection to the Internet and I do not want to change it will reset the Internet Explorer icon on the desktop, and allow you to manually configure your Internet Control Panel settings.
Shell, User and GDI
Plus! Features
We’ve incorporated the basic display enhancements included on the “Plus!” tab in the display control panel such as Full Window Drag and Font Smoothing. We’ve continued to call the tab “Plus!” so that current users don’t get confused and existing documentation doesn’t change. This is identical to Windows NT 4.0.
•	Full Window Drag
•	Font Smoothing
•	Wallpaper stretching
•	Large Icons
•	Hi-color icons
•	Desktop Icon Changer
•	Sliding Hiding Taskbar
Miscellaneous User/GDI enhancements
The following are some miscellaneous enhancements that don’t really fall well into any other category, but improve the overall product usability.
Accessibility – New Accessibility API support in GDI and User to enable support helper applications for disabled computer users. This includes support for screen readers, larger, high contrast font displays, and more. For more information about Microsoft Accessibility support, and for API information, please see: 
http://www.microsoft.com/windows/enable
Wheel Mouse Support – for the new Microsoft Intellimouse with the wheel on top, this builds in support for applications that can take advantage of it.
•	Just rotating the wheel causes text to scroll several lines (default 3) per wheel detent.
•	In Office97, rotating the wheel while holding down the Ctrl key will zoom in or out (cause the document to be displayed larger or smaller).
•	The wheel itself acts as a middle mouse button if pressed.
•	y pressing the wheel button in a wheel-aware app (Office97/IE3), you are then in "panning mode". This is indicated by the mouse cursor changing to a special panning cursor. While panning mode is active, just dragging the mouse forward or backward will cause the document to auto-scroll. The speed at which the document scrolls is determined by how far the mouse is dragged away from the position where panning mode was enabled. To exit panning mode, just press any mouse button.
•	Not all software that has a scroll bar will work with the wheel. In order for the wheel to work in an application, one of two things must be true:
•	The application must be revised to handle the new WM_MOUSEWHEEL message. Office97/IE3 are two examples of this.
•	The application must use one of USER's built-in controls. The wheel will work with Notepad because Notepad uses USER's edit control.
Animation - This includes sliding menus and color highlights on menus and controls to track the mouse position. For performance concerns, it has been turned off as default..
To enable the animated menus feature, perform the following steps:
•	Insert your Memphis CD into your CD-ROM drive.
•	With Memphis CD window displayed, choose the "Browse this CD" option
•	Open the "betaonly\menuani" folder
•	Double-click on the file called "Animate.reg"
•	Shutdown, then restart Memphis
•	Animated menus are now enabled
You can disable this featureby double-clicking the file "Noanimat.reg" instead of "Animate.reg" in the above steps.
Image Color Matching 2.0 API
Microsoft's first implementation of color management support was released in the Microsoft® Windows® 95 operating system as ICM 1.0. This version of ICM was designed for applications that do not work in colors outside of RGB (such as CMYK) and that want color management to work fairly transparently for the end-user. ICM 1.0 requires ICC profiles to be installed for all of the color devices on the user's system, and it requires the application that wants to accurately portray colors to the user to support the ICM 1.0 APIs. 
After meetings with multiple industry leaders in the color field, Microsoft has designed ICM 2.0. The new APIs are a complete superset of the ICM 1.0 APIs and add a new range of capabilities: 
•	ICM 1.0 compatible 
•	ICC compliant 
•	Scalable: Simple APIs for applications such as Microsoft Office, complete control for applications such as Adobe PhotoShop 
•	Same APIs for Windows 95 and Windows NT operating systems 
•	Support for Profile management at API and user interface level 
•	Bitmap v5 header support 
•	Standard Color Space support: sRGB 
•	Broader color space support: RGB, CMYK, LAB, and others 
•	Broader support for bitmap formats 
•	Improved palette handling 
•	Device driver participation on the Windows 95 and Windows NT operating systems 
•	Support for multiple Color Management Modules (CMM) 
•	Faster default CMM that supports all ICC-compliant profiles 
•	Easier installation of profiles 
This new version of ICM will be integrated in Memphis and Windows NT 5.0. For more information on ICM 2.0, please see the document in the \betaonly\icm20 directory. 
A beta version of the ICM 2.0 SDK is located on:
http:/www.microsoft.com/msdn/sdk/icm20.htm
Display Control Panel Improvements
The Display Control Panel has been enhanced to support new display driver technology. It contains the following new features:
•	QuickRes, the quick resolution switching utility, has been incorporated into the standard control panel. There is a checkbox that will turn on the taskbar notification icon for quick resolution and color depth switching.
•	DynaColor, the ability to switch display color depths, is now included in the display control panel. (You still need a reboot if you change “font size”.) Many applications and display drivers will work with this automatically, but some may need to be updated. Please send us a bug if you find an application that does not update properly. This feature is useful for game developers who wish to use a specific color depth. 
•	Refresh Rate Support is now available from the Change Display Adapter button. This support was built into the Windows 95 Registry, but only a few display adapter drivers support the refresh rate setting. Contact your Display Adapter vendor to get a refresh-rate enabled display driver. Refresh rates are stored in a per-resolution setting.
•	Display Adapter Performance Slider is now accessible from the Display Control Panel, instead of having to go to the System Properties. This slider is used to diagnose and solve display driver incompatibilities.
•	Hardware Panning is now enabled on lower-resolution displays such as VGA-only monitors or laptop LCD panels where the chipset supports it. If your chipset supports this, and you have a monitor selected in the Monitor settings that does not support greater than 800x600 resolution, hardware panning will be enabled. Hardware panning is disabled on monitors capable of 1024x768 resolution as it is not normally needed. If hardware panning is enabled, and the display device is capable of 800x600, there are two graphics sliders - one for the screen resolution and one for the virtual desktop resolution. The screen slider is not shown for 640x480-only displays as it would be fixed at one setting only.
•	Multiple Display Support – if multiple displays are enabled, the Settings tab is replaced with a Monitors tab. You can use this Monitors tab to control relative screen placement by dragging, and to set individual adapter settings as described above by selecting the appropriate adapter.
Release Notes for Display CPL: 
On some chipsets (older S3 chipsets such as 801 and Cirrus Laguna), lower resolution modes may cause some older monitors to lose sync. This is because the lower resolution modes are driving the pixel clock too high. It might help to reset your display settings to VGA settings (640 x 480 x 16 color).
Settings Wizard 
Settings Wizards showcases a number of wizards that help accomplish frequent tasks.  To get to Settings Wizards, click Start, Settings, Settings Wizards.  Point at a wizard to see a graphical preview and text description.  Click on a wizard name to launch.  You can use User Policy to remove Settings
Wizards from the Settings menu, if you wish.
Known issues: 
- Window might flash briefly while in 256 color video mode; switch to greater than 256 colors to avoid this
- Not all items are wizards yet, and the list of wizards is not final.  
Communications and Networking
Dial Up Networking and Dial Up Scripting
Dial Up Networking now includes built-in Dial Up scripting. This is a property sheet for each individual connection icon. Connection Icons also include a separate tab for Server Type.
The beta version of  Dial-Up Networking provides support for a single client PPTP connection, support for internal ISDN adapters, connection time scripting to automate non-standard logins, and several bug fixes. All prior fixes included in the OSR2 release of Windows95 and the ISDN1.2 Accelerator Pack have been included in this release.
Certain network limitations involving will occur, as described in Known Bugs and Limitations, below.
Point-to-Point Tunneling Protocol (PPTP)
Tunneling is a networking term describing the encapsulation of one protocol within another protocol. Tunneling is typically done to join two networks using an intermediate network that is running an incompatible protocol or is under the administrative control of a third party.
PPTP is a tunneling protocol defined by the PPTP Forum that allows PPP packets to be encapsulated within Internet Protocol (IP) packets and forwarded over any IP network, including the Internet itself.
PPTP is used to enhance the networking services provided by the WindowsNT Remote Access Server (RAS) and Memphis Dial-Up Networking clients. 
Windows Dial-Up Networking allows a computer to join and leave a network of computers over a dial-up connection. While connected to the network, the Windows client behaves exactly as if it had a local network connection. Except for speed differences over slow links, network applications are unaware that a Dial-Up Networking connection is in use.
Memphis Dial-Up Networking uses the Internet standard Point-to-Point Protocol (PPP) family to provide a secure, optimized multiple-protocol network connection over dialed telephone lines. 
PPTP extends the service provided by Windows Dial-Up Networking. PPTP adds the ability to treat the Internet as point-to-point Dial-Up Networking connection. All data sent over this connection can be encrypted and compressed, and multiple network level protocols (TCP/IP, NetBEUI, IPX) can be run concurrently.  WindowsNT Domain Login level security is preserved even across the Internet.  PPTP can be used to connect to an Intranet that is otherwise isolated from the Internet, and may even have Internet address space conflicts. 
PPTP appears as new modem type (Virtual Private Networking Adapter) that can be selected when setting up a connection in the Dial-Up Networking folder. The PPTP modem type does not appear elsewhere in the system.
When initiating a PPTP connection, use the DNS hostname of the destination computer or its IP address in dotted format (x.x.x.x) as the phone number. Area Code is not used for PPTP connections.
This release provides support for two concurrent outbound Dial-Up Networking connections. This support exists to allow a Dial-Up Networking PPTP connection to be established over a modem based Dial-Up Networking connection to the Internet.
It is not necessary to have a Dial-Up Networking connection to the Internet to support PPTP. Reachability to the PPTP server over any IP network is the only requirement for a PPTP connection.
PPTP Limitations
Can’t ping PPTP Server from the Internet
This is by design.  When enabled, PPTP filtering on the server allows only PPTP packets to pass. The ICMP Echo packets used by ping will not pass through this firewall.
Cannot access network shares across private networks
This can occur when a tunnel is established between the two networks which are under domain login security but in different, non-trusted domains.  The Memphis client logs into the first domain and cannot log in to a second domain.
The workaround is to skip the initial domain login (Cancel) and log into the second network when the PPTP connection is established.
From a PPTP connection, can’t see computers on a private network when a netcard is installed.
This occurs only when the private network is running TCP/IP.   The problem occurs when a computer that has been connected to the private network is disconnected and then attempts a dial-up or PPTP connection.  (This can happen, for example, when a laptop user disconnects an Ethernet connection from the corporate network and then tries to dial in from home.)   If the network card is still installed, TCP/IP thinks that the computers that could be reached through the netcard are still reachable through the netcard. Even after a modem Dial-Up Networking connection or a PPTP connection is established back to the same network, TCP/IP will continue to send all traffic for computers on the local network out the netcard.
The workaround, if the computer originally booted from DHCP, is to run the winipcfg utility and select the Release option. If this does not fix the problem, the netcard has been manually configured through the control panel, and will have to be removed (in the PCMCIA case) or disabled through the control panel.
Can’t see computers on the Internet after establishing a PPTP connection to a private network.
This is by design, and only occurs only when the private network to which you have tunneled is running TCP/IP.  When a tunnel is established, a new default route is created which directs most IP traffic through the tunnel rather than the Internet.  When the tunnel is disconnected, this default route is removed.  The PC will revert to its previous behavior for forwarding IP packets.
This problem can also occur in more complex network environments.   If your PC is LAN-attached, and you establish a PPTP tunnel over that LAN to a foreign network, a default route will be created directing remote traffic to the foreign network.  You will continue to see TCP/IP hosts and servers that are on your immediate LAN segment, but computers that are not on your local network LAN segment will no longer be visible.
Note that a DNS or WINS server that may be one of the computers that is hidden.
The workaround to these problems is to add one or more route entries by using the route command from a DOS prompt. For matching traffic, TCP/IP will use this route rather than the default gateway.
Very Large File Copies over PPTP Tunnel Sometimes Fail
This is a known bug.  There is no workaround.  It is rarely encountered in normal remote access activities such as email and web browsing.
NWLink over PPTP Tunnels
Once connected via PPTP, only the target network will be visible with IPX at that time. This is unchanged from the way Window95 works today for dial-up (PPP) connections.  Currently, when IPX is selected in a phonebook entry and IPX is active on a NIC, a dialog is presented to the user (at dial time) informing them that NetWare servers on the local LAN will no longer be visible once a connection is established to the remote LAN. Users will see this same dialog when establishing a PPTP connection.  
TAPI 2.1
Memphis contains TAPI 2.1, based on TAPI 2.0 support as shipped in Windows NT 4.0. If you have any TAPI-aware applications, please test them against the new TAPI 2.1, and let us know if you encounter problems.
Relnote: There are known problems with several third-party TAPI Service Providers (TSPs). If you encounter these, please file a bug report so that we can work with the vendor.
Unimodem/V
Unimodem was updated in OSR-1 to support VoiceView modems. Memphis will add support for:
•	Sierra modems (e.g. Prometheus, Motorola, VoiceSrfr, and some PC systems).
•	Spartacom modem pooling
•	Denmark support
•	Intel H.324 support
•	Lucent controller-less modems
ISDN 1.1 Accelerator Pack
ISDN is a service of your telephone company that can provide up to 128 kbps access to the Internet and other networks. To learn about ISDN and to determine if ISDN service is available in your area, please visit the “Get ISDN” web page at:
http:// www.microsoft.com/windows/getisdn
The ISDN Accelerator Pack adds multlink,, which allows you to bond two B channels together for 128k performance. The ISDN Accelerator Pack is required to configure your system to use an internal ISDN adapter card. External adapters don't require any additional software. 
Relnote: To use ISDN 1.1 Accelerator Pack you must have ISDN 1.1 compatible driver software provided by your ISDN adapter manufacturer. Certified Windows 95 compatible ISDN 1.1 adapter drivers are available for download from the Hardware Compatibility List. The ISDN 1.1 Accelerator Pack will not work correctly with 1.0-compatible drivers. To check on driver availability, check the ISDN Accelerator Pack web page at: 
http:// www.microsoft.com/windows/common/aa2720.htm
If a driver for your ISDN adapter is not listed, please contact your ISDN adapter manufacturer or check the Hardware Compatibility List at a later date. New ISDN driver software will be added to the list when the drivers pass WHQL certification. 
Warning: USR ISDN Drivers – At the time this Developer Release shipped, USR was still working on their ISDN 1.1 drivers. Installing Memphis will disable your USR ISDN adapter. There is no easy workaround at this point, until USR makes drivers available.
To enable ISDN 1.1 support, perform the following setup steps:
	1.	Go to Control Panel
	2.	Start Add New Hardware
	3.	Select "No" when the Add New Hardware wizard prompts whether you want the system to automatically detect any new hardware, and click Next.
	4.	Select "Network Adapter" device and click Next.
	5.	Click the "Have Disk" button and insert the manufacturer’s driver disk and click OK.
	6.	Install as per your ISDN manufacturer's instructions
7.	ISDN configuration Wizard will guide you from there.
ISDN Limitations
No support for ISDN1.0 Accelerator Pack drivers
This release of Dial Up Networking now supports ISDN NDISWAN drivers.  These are binary compatible with drivers for WindowsNT.   ISDN Accelerator Pack 1.0 drivers will no longer work.   ISDN Accelerator Pack 1.1 drivers are fully supported.   See http://www.microsoft.com for a list of known vendor drivers.   Note that the U.S. Robotics Sportster 128 ISDN card may need a 1.0 to 1.1 driver upgrade.
Install from ISDN vendor doesn’t work
Many vendors bundle the ISDN1.1 (or 1.0) Accelerator Pack with drivers on diskette. This package was designed for installation on the original Windows95 system, rather than a Memphis system.  If a vendor install procedure is run on a Memphis beta system, the install procedure may overwrite some of the system files and leave the system unusable.   Contact the vendor’s support organization before beginning an install.
Multilink assumes identical connection types
Multilink was originally implemented for ISDN lines, in order to allow the user to consolidate two 64Kb links into a single 128Kb link.  Multilink will also operate with other link types, including simple dial-up analog phone lines.   However, performance will degrade markedly unless both links operate at the same speed.
NDIS 5
Memphis adds support for NDIS 5. The primary change between NDIS 4.0 and NDIS 5 is native support for ATM (asynchronous transfer mode) network cards. The standard NIC interfaces have not been modified.
We encourage network card vendors to thoroughly test their existing cards and drivers with the new NDIS 5 interface in a variety of networking scenarios, and report any problems to Microsoft using the Memphis bug reporting procedures.
ATM
Memphis and Windows NT are adding native support for ATM (asynchronous transfer mode) network cards. The NDIS 5 DDK Alpha release for development and testing of NDIS 5 ATM miniport drivers is currently available. ATM network card vendors can request the NDIS 5 DDK Alpha release by sending mail to: Atmfb@microsoft.com
For more information, please see http:// www.microsoft.com/hwdev (for development issues) and http:// www.microsoft.com/hwtest (for test issues). 
Memphis TCP-IP
The stack supports RAW sockets under Winsock 2. Stack support for IP multicast has been significantly improved under Winsock 2.  There is support for IGMP version 2 (Internet Draft, http://www.ietf.org). There is support for ICMP Router Discovery (RFC 1256).  Memphis’s TCP supports Fast Retransmit and Fast Recovery for better performance over lossy networks.  DHCP support has been improved in the areas of address assignment conflict detection and longer timeout intervals.  The IP stack has support for automatic address assignment in the absence of a DHCP server.  The stack will determine a network 10.x.x.x address and use this address until the stack detects the presence of a DHCP server.  The PC will be able to communicate with any other net 10 addressed machines on the same subnetwork.
WINS Persistent connection attempts
It has been observed that due to replication delays between WINSs on the network, it is possible for WINS servers to return stale IP addresses when they are queried. Netbt has been changed to work around this problem by being more persistent about connect attempts, i.e. Netbt tries to establish a session using the IP address that it gets from its favourite WINS first; and if that fails, it tries to get another IP address from the next WINs server (or Broadcast as necessary), remembering that the first one had failed.  This process continues until either the Query path is exhausted or we are able to successfully establish a connection to the destination machine.
In order to enable this functionality, the following (String) registry key must be set:
HKLM\System\CurrentControlSet\Services\Vxd\MSTCP\TryAllNameServers="1"
Winsock 2
Windows Sockets 2 (WinSock 2) utilizes the sockets paradigm that was first popularized by Berkeley Software Distribution (BSD) UNIX. It was later adapted for Microsoft Windows in the Windows Sockets 1.1. 
One of the primary goals of Windows Sockets 2 has been to provide a protocol-independent interface fully capable of supporting the emerging networking capabilities, such as real-time multimedia communications. 
Windows Sockets 2 is an interface, not a protocol. As an interface, it is used to discover and utilize the communications capabilities of any number of underlying transport protocols. Because it is not a protocol, it does not in any way affect the “bits on the wire”, and does not need to be utilized on both ends of a communications link.
Windows Sockets programming previously centered around TCP/IP. Some of the programming practices that worked with TCP/IP do not work with every protocol. As a result, the Windows Sockets 2 API added new functions where necessary. 
Windows Sockets 2 has changed its architecture to provide easier access to multiple transport protocols. Following the Windows Open System Architecture (WOSA) model, Windows Sockets 2 now defines a standard service provider interface (SPI) between the application programming interface (API), with its functions exported from WS2_32.DLL, and the protocol stacks. Consequently, Windows Sockets 2 support is not limited to TCP/IP protocol stacks as is the case for Windows Sockets 1.1. 
There are new challenges in developing Windows Sockets 2 applications. When sockets only supported TCP/IP, a developer could create an application that supported only two socket types: connectionless and connection-oriented. Connectionless protocols used SOCK_DGRAM sockets and connection-oriented protocols used SOCK_STREAM sockets. Now, these are just two of the many new socket types. 
Additionally, developers can no longer rely on socket type to describe all the essential attributes of a transport protocol.  The new Windows Sockets 2 extends functionality in a number of areas. 
Windows Sockets 2 Features
Access to protocols other than TCP/IP	Windows Sockets 2 allows an application to use the familiar socket interface to achieve simultaneous access to a number of installed transport protocols.	
Overlapped I/O with scatter/gather	Windows Sockets 2 incorporates the overlapped paradigm for socket I/O and incorporates scatter/gather capabilities as well, following the model established in Win32 environments.	
Protocol-independent name resolution facilities: 	Windows Sockets 2 includes a standardized set of functions for querying and working with the myriad of name resolution domains that exist today (for example DNS, SAP, and X.500).	
Protocol-independent multicast and multipoint:	Windows Sockets 2 applications discover what type of multipoint or multicast capabilities a transport provides and use these facilities in a generic manner.	
Quality of service	Window Sockets 2 establishes conventions applications use to negotiate required service levels for parameters such as bandwidth and latency. Other QOS-related enhancements include socket grouping and prioritization, and mechanisms for network-specific QOS extensions.	
Other frequently requested extensions	Windows Sockets 2 incorporates shared sockets and conditional acceptance; exchange of user data at connection setup/teardown time; and protocol-specific extension mechanisms. 	

For more information on programming to the WinSock 2 API or SPI specification, see the Microsoft Developer Network (MSDN) or the official WinSock working group’s specification.
Known Problems
•	WinSock 2 installation breaks applications and network stacks that replace the Microsoft Windows 95 version of WINSOCK.DLL or WSOCK32.DLL.  
In an effort to minimize the impact of this issue, Microsoft has identified the following popular products and, as a workaround, WinSock 2 will not be installed as part of Memphis installation if any of the following are detected:
•	Cisco/TGV -TCP/IP Suite 100
•	Novell -NetWare Gateway
•	WRQ -Reflections 
•	NetManage -Chameleon  5.01 and 6.01
•	Microsoft Proxy -WinSock Proxy Client
•	FTP Software -All Win95 TCP/IP related products
Microsoft is working with all of these vendors to ensure that all of these applications will work with WinSock 2 in the near future. Please do not file bugs against the applications mentioned above in this round of beta testing.
If you experience difficulty using an application or stack that is not in this list, please file a bug report, as each non-functional application/stack will be treated as an individual bug by the WinSock team. If the problem you encountered was with an application, as opposed to a network stack, you may be able to work around the problem by reinstalling the application.
•	16-bit WinSock 1.1 applications that share socket handles do not work.  (This includes Microsoft Proxy’s 16 bit WinSock Proxy Client)
•	Microsoft specific WinSock 1.1 extensions only work with Microsoft TCP/IP and IPX. 
Uninstalling Winsock 2 and reinstalling Winsock 1.1
During Memphis installation, all WinSock 1.1 components are backed up. In the unlikely event that you experience interoperability problems with WinSock 2, and are unable to workaround the problem, after reporting the bug, you can uninstall WinSock 2 which restores your pre-existing WinSock 1.1 configuration. Uninstall is performed by opening the Add/Remove Programs applet in the Control Panel and selecting "Restore Winsock 1.X Configuration”, then clicking “Yes” when prompted.
Please note the following about WinSock 2 uninstall routine:
•	The user’s WinSock 1.1 environment is only backed up the first time the PC is upgraded from Windows 95 to Memphis.  Subsequent reinstallation of Memphis onto Memphis will not back up the WinSock environment.  
•	After uninstalling WinSock 2, the only way to put it back on the PC is to reinstall Memphis.
•	When WinSock 2 is uninstalled, only the WinSock 2 related files are removed. The Memphis version of the Microsoft TCP/IP and IPX/SPX stacks stay installed, and will run with WinSock 1.1.
We have also included documentation on the new Winsock 2.0 APIs. For more information, and to install the drivers, please see the \betaonly\winsock2 directory, for the full Winsock 2.0 SDK.
Resource ReSerVation Protocol (RSVP)
A primary concern of network technology is how best to deliver information from a sender to a receiver. At present, most networks only promise to make their best effort to deliver packets to their destination. There is no guarantee that the packets will arrive. For example, when a router is overloaded, packets may have to be dropped. When packets are sent over the Internet, they may travel by different paths and arrive out of order.
Since missing or out-of-order packets may make mincemeat of the original message, protocols such as TCP/IP were developed to make best-effort service reliable. By ensuring retransmission of lost packets, they guarantee that all packets eventually arrive. By keeping track of the order of transmission, the message can be reassembled, regardless of the order in which the packets are received.
Until relatively recently, a reliability guarantee (all the packets that make up a message will eventually arrive intact at their destination) has been sufficient for most applications (e-mail, for instance).
However, networks are increasingly being used to transport a much wider variety of information. For some of them, real-time audio and video for example, guaranteeing that packets will arrive sometime in no particular order is not enough. Delayed or out of order packets may degrade the quality of a video to the point that it is unacceptable, or require large and expensive buffering capacity. On the other hand, while missing packet is serious matter for e-mail, it may not pose a problem for real-time speech transmission, as long as most of the packets get to their destination at the right time.
Rather than thinking about networks simply in terms of reliability, the computer industry is increasingly shifting to the broader concept of Quality of Service (QOS). QOS encompasses the much larger range of transport-related issues that are raised by the rapidly changing role of networks. 
Optimal use of limited network resources demands that QOS be tailored to the particular requirements of an application. At the same time, conventional best-effort network applications must be able to operate normally. The most common approach to providing QOS is to allow applications to reserve the particular network resources they need prior to initiating a transmission.
If the desired QOS is unavailable, the reservation process allows applications to attempt to reserve a lesser but still acceptable level. They may also be able to use control messages to determine what service level is available, prior to making a reservation request.
RSVP is a protocol for reserving network resources that can be implemented on existing networks. It has been proposed as an Internet standard, and seems likely to receive that designation. Although it is designed to work with any network protocol, it is well matched to TCP/IP. It is also explicitly designed to handle multicast traffic effectively. RSVP has the following attributes:
•	RSVP handles reservations for unicast, one-to-many, and many-to-many multicast applications. It can respond dynamically to changing group membership and routes.
•	RSVP is simplex. QOS for each direction of data flow is established separately and need not be the same.
•	RSVP is receiver oriented. The receiver of the data stream is responsible for requesting and maintaining the reservation, not the sender.
•	RSVP reservations are maintained in a “soft state” on participating routers. If the reservation is not periodically updated, it will be canceled.
•	RSVP is not a routing protocol. It utilizes present and future routing protocols to determine the paths by which data will be transmitted.
•	RSVP provides opaque transport for policy and traffic control messages. These protocols are independent of RSVP.
•	RSVP provides several reservation styles, to accommodate a variety of applications.
•	RSVP functions transparently through routers that do not support it (although the specified QOS is longer guaranteed).
The RSVP specification is being developed by the Internet Engineering Task Force (IETF). The complete specification is available from several ftp sites including: ds.internic.net (US East Coast), ftp.isi.edu (US West Coast), nic.nordu.net (Europe), and munnari.oz.au (Pacific Rim). It can also be found via the World Wide Web, for example, at www.isi.com or www.internic.com.
How to Use RSVP
RSVP is installed during Memphis installation of WinSock 2 and is available to WinSock application programmers through the Generic Quality of Service (GQoS) API’s in WinSock 2. RSVP functionality is only available programmatically and does not affect any application that does not explicitly request its services. To use GQoS via RSVP, the sockets programmer simply enumerates the available protocols using the WSAEnumProtocols API to look for one that supports QOS (via a service flag ) and passes the protocol info structure in on the call to  WSASocket().
For more GQoS programming details, please download the document entitled “WinSock Generic QoS Mapping” available at ftp://microsoft.com/bussys/winsock/winsock2. GQoS header files are also available from this ftp site.
Known Issues with RSVP and GQoS
•	QoS support is only available for UDP sockets.  QoS support for TCP socket is not yet implemented.
•	This implementation of RSVP supports the USE-0 wire format of the RSVP protocol.  Subsequent betas and the final release will support USE-1. (and USE-1 will not be backward compatible with USE-0).
•	This implementation of RSVP supports the value “0” ( zero ) to indicate “use  default”. Subsequent betas and the final release will support the value “-1” to  mean use the default value.  This applies to the ReceivingFlowspec in the LPQOS  structure.  The application can request default values for all parameters in this  structure except the ServiceType parameter.   Defaults are not support for SendingFlowspec parameters in this Beta.
•	Traffic Control is not yet implemented.
•	Joining multiple multicast groups with WSAJoinLeaf on the same socket is not yet  implemented
•	SIO_SET_QOS IOCtl is not yet implemented as it pertains to GQoS
•	WSAAsyncSelect() does not report QoS related events
•	The ProviderSpecific buffer of the QOS structure is not interpreted in any way.
•	LOCAL_INTERFACE_QUERY IOCtl is not yet implemented.
Remote Access Server
Memphis Dial Up Networking includes the file rnaserv.dll, previously included with Plus!, which enables remote network access using NETBEUI or IPX protocols. You can enable the remote dial-up access from the Dial Up Networking – Settings menu. Removing this DLL completely removes this capability from a PC if necessary.
Microsoft Service for NetWare Directory Service (MS-NDS)
Microsoft Service for NetWare Directory Services (NDS) provides all the functionality that Information Systems Professionals need to connect to NDS servers and run many important utilities. Service for NDS provides the following networking features to support computers running on NetWare 4.x networks: 
•	Integrated log-in to NetWare 4.x servers 
•	Full support of NetWare 4.x login scripts 
•	The ability to use Network Neighborhood to browse the directory tree 
•	Full support for 16-bit NDS-aware programs written for MS-DOS or Windows using documented calls from the NetWare Client SDK
When the service is installed, it can be activated in the network control panel by selecting Add>Service and choosing the Microsoft Service for NetWare Directory Service. This is a supplement to the standard Windows 95 NetWare client software.
Relnote: Some problems have been reported when upgrading over Novell Client 32. We are currently investigating these issues. You may need to remove the Novell Client32 software, and reinstall the Memphis Service for NDS, then reinstall the Novell Client 32 software.
Microsoft 32-bit DLC protocol stack
The Microsoft 32-bit DLC protocol stack upgrades the DLC protocol stack that shipped in the original Windows 95 disks with a protect mode implementation of the DLC protocol. This can be used to provide enhanced connectivity and performance on Windows 95 systems.
3rd Party Networking  Release Notes 
Novell Client32 
NOTE: Please do not install Novell’s Client32 on this build of Memphis. Installing Novell’s Client32 on Memphis is not supported at this time.  Microsoft is working with Novell to obtain resolution to current conflicts.
If the user upgrades over a Gold or OSR2 machine running Novell’s Client32, functionality MAY be restored by attempting the following:
If your other network clients are working, work around this 
problem by the following method:
1.	Ensure you have a locally accessible copy of the Client32 installation media. Write down the current settings of the currently installed Client 32.
2.	Open Network Properties and remove both "Novell Netware Client 32" and "IPX 32-bit Protocol for Novell Netware Client 32". Click OK on network properties, and reboot when prompted.
3.	Once the system has rebooted, open network properties, Click on the Add button, select "Client" from the list of installable network components, Click the "Add" button. In the "Select Network Client" window, click the "Have Disk" window.
4.	Type in the correct path to the Client32 installation files. Click OK.
5.	Click the OK button on the screen prompting to install Novell Netware Client 32.
6.	In the Network properties window, bring up the properties of Client32.
7.	Fill in the blanks using the settings you wrote down in step 1. Click the OK button.
8.	Click the OK button of the network properties window. Click "Yes" when prompted to restart the computer.

If none of your network clients are functioning, work around the problem by the following method:
1.	If your network card uses drivers from the manufacturer, make sure you   have the disk available.
2.	Open Network Properties.
3.	Click the Add button. Select "adapter" from the list of installable network components. Click Add.
4.	Select "Microsoft" from the list of manufacturers. Select "Dial-Up Adapter" from the list of adapters. Click OK.
5.	In the network properties window, highlight your network adapter, and click remove.
6.	Click the OK button on the network properties window. When prompted to restart the computer, do so.
7.	When the system reboots, if Windows does not detect your network card you will need to run Add New Hardware from the Control Panel.
8.	If prompted to restart, do so.
At the current time, Novell’s Client32 Uninstall program is NOT supported in Memphis.

NDIS2 Support for previously supported cards
Many NDIS2 drivers shipped in Win95 are not currently shipping in Memphis.  If you card is one of the affected, the symptoms will be an inability to add ODI or NDIS2 support to the card in Network Control Panel and an inability to access the network from DOS.  The real-mode networking drivers that originally shipped in Windows 95 will also ship in Memphis, they will re-appear in a future Beta.
Possible workarounds:
Rename c:\windows\protocol.ini and copy c:\windows\protocol.--- to protocol.ini.  This replaces the new Memphis protocol.ini with one backed up before upgrading.
Obtain the most recent drivers for your Net card from the manufacturer.  Remove the Net card from Network Properties and subsequently choose Add / Adapter / Have disk and browse to where your most recent updated drivers are.  If the manufacturer still supports NDIS2, you will be able to install support that way.
NDIS2 and ODI support should be back in Memphis soon.
Banyan Vines Release Notes
Cannot upgrade Banyan Vines client using NEWREV
If you are using the Banyan Vines client for 95 you will not be able to upgrade your existing client by using NEWREV.  This only applies if you have an older version then what is on the Banyan server you are connecting to.  This may happen if your administrator has upgraded the server to the latest edition and it is newer then your existing client.  Please contact your LAN administrator or Banyan Vines to get the latest upgrade.  
Upgrading from Gold/OSR2 to Memphis with the Banyan Vines 32 bit client.If an upgrade setup is run from DOS , the error  "Failed to load resource DLL (VNSDIR)DLL will occur and cause the existing 32bit Banyan client to be removed from Network setup.  After setup is complete you can proceed to re-install the Banyan 32 bit client.
Banyan Vines 32 bit client and client for Netware;  Accessing Network Control panel.
If the Banyan vines 32bit client and the Client for Netware are installed at the same time and the network control panel is accessed more than twice without rebooting then all protocols will unbind from the network interface card, the Banyan 95 client will be removed from network setup, and garbage will be placed in the Client for Netware properties.  This problem can be recovered from by CANCELing out of network properties and rebooting.
Other Banyan Problems
A number of Vines issues can be corrected by downloading the latest version of Banyan’s 32-bit Vines client from www.Banyan.com
Artisoft Release Notes
Installing Memphis kills LANtastic ModemSharing and LANtastic Internet Gateway Client.
Installing Memphis on top of any previous version of Windows95 running LANtastic7 will disable the LANtastic Internet Gateway Client.  LANtastic's ModemSharing com ports in device manager will also no longer function.  
Currently the only way to fix this problem is to run LANtastic's setup utility and remove your current LANtastic install.  After it is uninstalled then run the setup utility again to reinstall LANtastic.  When done this way LANtastic will save your user and resource settings for use in the reinstall.  
DO NOT use Add/Remove Programs remove utility to uninstall the application.  This will completely remove LANtastic and cause you to lose your user and resource settings. 
For more help, information and the latest patches for LANtastic 7.0 contact Artisoft.  Their website is HTTP://www.artisoft.com.
Applets and Utilities
MS Paint
MS Paint now supports loading and saving GIF and JPEG images if the appropriate Office97 Graphics Import Filters are installed. If the filters are installed, the Open and Save As dialogs will include GIF and JPG extensions.
Also, Beta 1 may ship with these bugs: Tooltips don't appear for drawing tools, and Stretch/Skew dialog doesn't allow vertical stretching/skewing.
Backup
The new Memphis Backup applet adds support for parallel, IDE/ATAPI, and SCSI devices. Devices supported include: QIC-80, QIC-80 Wide, QIC-3010, QIC-3010 Wide, QIC-3020, QIC-3020 Wide, TR1, TR2, TR3, TR4, DAT (DDS1&2), DC 6000, 8mm, and DLT. This includes drives branded by Conner, Exabyte, HP/Colorado, Iomega, Micro Solutions, Seagate, Tandberg, WangDAT, and Wangtek. In addition, the Memphis Backup applet supports backup to floppy-based and network drives.
Known Problems:
Backup App for Memphis doesn't show Removable drives as an option to backup from.
Removable drives do not show up in the drop down list as a device to backup to like the tape drives, but you can backup to them by selecting ‘File’ and choosing the removable drive letter as the place to backup to.  If the disk fills up, it will prompt you for another disk.
Backup always gets errors on a restore of the Windows drive.
Backup does not restore open files.  If restoring the Windows drive, suggest using Disaster Recovery (if it gets fixed).
After identify on a tape is done Device View indicates that the tape is blank when it contains a full backup set.
Choosing Tools / Media / Identify on a tape causes backup to think that there are no backup sets on that tape (wither there is or isn’t) until backup is restarted.
Internet System Update (aka "Code Download Manager")
Internet System Update is a web-based service that scans your system to determine what hardware and system software you have installed, and compares it to a back end database to determine whether there are updated drivers or system files available that you may wish to install. Any applicable updates it finds will be listed and described so that you can decide whether you want to install them. Any updates you install with this service can be removed later.
To run the Internet System Update, click its shortcut on the Start menu, in the Programs->Accessories->System Tools folder.
Notes:  
Internet System Update is implemented as an ActiveX control, so in order to use it, you must be using a browser such as Internet Explorer version 3.0 or higher that supports ActiveX controls.
Web-based Bug Submission
We will be using a web-based bug reporting form during the Memphis beta. The form includes an ActiveX control that scans your system to obtain a complete profile of your hardware, and uploads that information, along with key system files such as your Registry and Dr. Watson logs, with your bug report. 
To submit a bug for Memphis, click its shortcut on the Start menu, in the Programs->Accessories->System Tools folder.
Because the bug reporting form utilizes an ActiveX control, we strongly recommend using a browser such as Internet Explorer version 3.0 or higher that supports ActiveX controls.
HelpDesk Icon  
There is now a Help Desk Icon on the desktop.  This icon is only temporary for this WinHEC update release.  In addition, the three-button application that it runs is also temporary.  We will be migrating this to an improved design (the leading candidate is a cascade off of the Help menu on the Start menu) for Beta 1, but for this release we wanted to enable the basic functionality and expose it for internal testing.  You are welcome to try this out, but please realize this is not a final implementation by a long shot.  No bugs should be submitted agains the Help Desk Icon or any related functionality for this release.
Dr. Watson
Dr. Watson is an enhanced version of the Windows 95 fault dialog box. With Dr. Watson enabled, when a software fault occurs, Dr. Watson will intercept it and indicate what software faulted and why. In addition, Dr. Watson collects detailed information about the state of your system at the time the fault occurred. It logs this information to disk, and can display it on screen (click Details on the dialog box that is displayed when a fault occurs), to assist product support personnel in determining the cause of the fault.
System File Checker
System File Checker (SFC) verifies the integrity of your operating system files and offers to restore missing or corrupted files.  When running System File Checker for the first time it may report that a number of files have changed.  This is because the default file checksums are not up-to-date for the current build of Memphis.  If System File Checker reports that a file has changed, select "Update verification information for all changed files", and click OK.
System Info Utility
Memphis now contains a centralized System Info utility, which provides core file information for product support groups.
Compression Agent
Memphis includes the Compression Agent utility from MS-Plus! that enables scheduled high-compression to happen when you are not using your machine.
Task Scheduler
Memphis contains Microsoft Task Scheduler, an improved version of the System Agent that was included with Microsoft Plus!.  The new task scheduler is a special folder, or shell extension.
Registry Scan and Backup
Memphis automatically scans and backs up the system registry when booting.  This provides increased robustness for registry corruption problems.
Known Issues:
If after installing build 1423 you are getting the "One or more system files corrupt." error every time while booting, reboot your machine and choose command prompt only.  Run checkreg.exe and confirm that your system files are ok or corrupt.  If checkreg.exe reports "No errors", then increase the amount of conventional memory by loading devices high and adding emm386.exe to your config.sys.
Earlier Memphis builds created a Scanreg directory in your \Windows directory and created a new backup registry each day.  You should delete this directory and it’s contents.
Calc
Memphis now contains an updated, high precision calculator.  The math engine in the calculator has been updated to fix the nagging problems due to binary to decimal math conversion errors.  Please test this version of Calc with all your favorite Calc bugs, and let us know if you find any new ones or if any old ones still exist.
MSD
The old MS-DOS “MSD” utility on the CD has been updated.  The older version would sometimes indicate an incorrect CPU model on non-Intel CPUs.  Memphis System Control Panel displays the correct CPU, so the CPU display has been eliminated from MSD to avoid confusion and incorrect information.  In addition, Dr. Watson and System Info both provide CPU identifier information.  There are no other changes to MSD.
HyperTerminal
HyperTerminal: Will not save newly created connection sessions.
Currently it is not possible to save newly created sessions (.ht files) within HyperTerminal.  You can save changes to existing sessions.  
If you wish to create a new session, copy an existing session and rename it to the name of the new session you want to create.  Open this session and change the phone number and other data to what you need for the new session and then save the changes on this new session.  
TAPI: Getting "No dial tone" connection causes GPF in TAPISRV when exiting HyperTerminal
Make sure that the phone line is properly connected and that you can get a proper dial tone on the phone line before using HyperTerminal.  If for some reason you get a "No Dial Tone" message when dialing out, do not immediately shutdown HyperTerminal.  Exiting HyperTerminal after getting this message will cause a general protection fault in the TAPISVR component.  It is suggested that you save any information in any open applications before exiting HyperTerminal.  It is also suggested that you reboot the machine before using HyperTerminal again should you get this problem.
HyperTerminal adds empty folders to root directory when executed.
Any time HyperTerminal is executed a folder titled "Start Menu" will be created in the root of the drive where HyperTerminal is executed.  This folder and its subfolders can be deleted without causing any problems.
Windows Scripting
Windows gets Scripting built-in. With the Memphis and NT 5 releases, we will be supporting direct script execution from the shell or the command line. We include direct support for Visual Basic Scripting (VBScript) and JavaScript. The scripting host, however, is extensible to additional language by third parties.
Internet Explorer 3 installs an ActiveX control that interprets VBS and JavaScript. Memphis will include the “Windows Scripting Host” which is just a simple executable that provides a direct interface into the scripting ActiveX controls. 
Windows Scripting Host: A Shell-based Host for Integrated Scripting in Windows
The Windows Scripting Host (WSH) is a language-independent scripting host for 32-bit Windows platforms. Microsoft provides both Visual Basic Scripting Language® and JScript scripting engines with WSH.  Microsoft anticipates that other software companies will provide ActiveX™ scripting engines for other languages such as Perl, TCL, REXX, and Python.
WSH can be run from either the Windows-based host (WSCRIPT.EXE), or the command shell-based host (CSCRIPT.EXE). When you double click a .VBS or .JS file in the shell, WSCRIPT is used. When you do a Start XXX.VBS from the command line, Wscript is also used. To execute in command line mode, you must explicitly start the command shell host using the syntax “cscript xxxx.vbs”.
For more information on the Windows Scripting Host, please review the documentation in the \betaonly\wsh directory on the CD.
Visual Basic Documentation and Examples
The authoritative information source for VBScript is:
http:// www.microsoft.com/vbscript
This web site contains tutorials, beginner and expert information, samples, and anything else you wanted to know about VBScript. It is, however, slanted toward using VBScript within a browser and HTML pages, so you will have to do some filtering to apply the information to the direct VBScript implementation in WSH.
We have included some WSH sample scripts, however, many of them are for the Windows NT Server DFS administration examples and are not useful on standalone machines. Look in \betaonly\wsh\samples.
We have also included the VBScript Tutorial and Language Reference hypertext files. You can set these up using the \betaonly\wsh\vbscript\vbsdoc.exe file. This executable will install VBScript HTM files. There are several ways you can view the VBScript documentation. You can double-click the icon that Setup creates. You can also start your browser, click Open on the File menu and type the file name, VBSTOC.HTM, into the dialog box.
VBSDOC.exe contains language and run time reference, using VBScript in HTML
Windows Messaging
The Windows Messaging Inbox Client software in Memphis is a new, updated version. This is the same version that ships with Windows NT 4.0, and is available to current Windows 95 users through online download.
Changes:
•	MAPI 1.0b 
•	The wording has been changed throughout the Windows Client version of the product from "Microsoft Exchange" to "Windows Messaging" to reduce confusion between the Windows standalone client and the Exchange Server enabled client.
•	A simple, fast send note has been added that allows the File->Send operation to be significantly faster on highly memory constrained machines. This only affects the File->Send operations.
•	OLE messaging has been enhanced to contain support for VB script.
Imaging by Eastman Kodak
Imaging is a new FAX viewer utility that has replaced FAXVIEW. It offers improved functionality for viewing faxes, as well as improved performance under some circumstances. It also includes TWAIN32 support, which works with many scanner devices. This application now supports the push mode of scanning .This allows the application to be launched by events from a scanner or camera. The HP 5p and the Logitech USB scanner included in this release each support buttons that trigger this behavior. See the above section on WDM drivers for scanners and cameras for more information.
Microsoft Fax Installation for Memphis
If you have difficulties using Microsoft Fax on Memphis, the problem may be due to installation and configuration. If you have problems using Microsoft Fax, follow these detailed step-by-step installation instructions before reporting bugs in Microsoft Fax.
Step-By-Step Installation Instructions for Microsoft Fax
After a successful upgrade or installation of Memphis, open the “Control Panel” by clicking on the Start button, then the Settings menu option and then the Control Panel option.
Double click on the “Add / Remove Programs” icon.
Click on the “Windows Setup” tab, and install all the options concerning the “accessories”, “communications”, “disk tools”, and “Microsoft Fax” components.
Click “OK” to any message boxes that appear.
When the “Inbox Setup Wizard” dialog asks “Have you used Windows Messaging before?”, click on “NO” and then “Next”.
When asked, “Select the information service(s) that you want to use with Windows Messaging” – make sure that the Microsoft Fax option is checked.
Next, at the prompt for  “Location Information” enter your telephone area code and optionally, fill in the other fields. Click “Close” when done.
The “Dialing Properties” dialog appears with a “My Location” tab. Fill in the appropriate fields then click “OK”.
The “Inbox Setup Wizard” window will then ask “What do you want to use to send and receive faxes?” Choose “Modem connected to my computer” and click the “Next” button.
The “Install New Modem” dialog appears. Allow the system to automatically detect your modem; do not check on the “Don’t detect my modem; I will select from list” feature. Click on “Next”.
Verify that modem has been correctly detected. Click “Next”, then “Finish”
The “Inbox Setup Wizard” appears without the detected modem in the list. Click “Next”.
The Setup Wizard will display “You have not selected a fax modem. That’s OK, but you will only be able to work offline. Do you want to select a fax modem?” Select “No”.
The “Inbox Setup Wizard” will ask you to enter a name and fax number. Fill in the fields and then click on “Next” and “Finish”.
An error message box may appear describing an error in MLSET32 (ie: MLSET32 caused an invalid page fault in module KERNEL32.DLL at 0157:bff7a020). If this occurs, click on the “Close” button and proceed to the next step.
At this step, the Microsoft Fax feature is installed. To finish, right-click (right mouse button) on the Inbox icon located on the desktop.
Click on Microsoft Fax in the “Services” box.
Click on “Properties” button.
Click on the “Modem” tab
Click on “Set as Active Fax Modem”
Click on “OK”
Click on “OK”
Microsoft Fax should now be operational now.
Another method of getting Microsoft Fax operational, is to do a hardware detection on modem first (control panel / hardware detect), reboot, and then add on Microsoft Fax (via “Add Remove Programs” icon).
Updated awfxcg32.dll
With Microsoft fax installed as a mapi service provider, you may encounter a page fault on exiting a mapi client such as exchange or outlook.  This has been corrected with a new version of the awfxcg32.dll binary.  You can copy this file from betaonly\fax\awfxcg32.dll to your windows\system directory, copying over the old awfxcg32.dll file.
Microsoft Fax and Exchange 5.0
There are problems with the installation order of Microsoft Fax and Exchange 5.0. We recommend installing Microsoft Fax before upgrading to Exchange 5.0. However, if Exchange 5.0 is installed prior to Microsoft Fax, you will need to edit the c:\windows\system\mapisvc.inf file.
In the mapisvc.inf, file, add the following line to the sections indicated:
[Services]
AWFAX=Microsoft Fax

[Default Services]
AWFAX=Microsoft Fax
Then, add the following statements: 
[AWFAX]
PR_DISPLAY_NAME=Microsoft Fax Messaging Service
PR_SERVICE_DLL_NAME=awfaxp.dll
PR_SERVICE_ENTRY_NAME=ServiceEntry
WIZARD_ENTRY_NAME=WizardInformation
Providers=AWFAX_AB, AWFAX_XP
PR_RESOURCE_FLAGS=SERVICE_SINGLE_COPY|SERVICE_NO_PRIMARY_IDENTITY
PR_SERVICE_SUPPORT_FILES=awfaxp,awfxab,awcl1_,awdevl,awrndr,awfxcg

[AWFAX_AB]
PR_PROVIDER_DISPLAY=Microsoft Fax Address Book
PR_DISPLAY_NAME=Microsoft Fax Address Book
PR_PROVIDER_DLL_NAME=awfxab.dll
PR_RESOURCE_TYPE=MAPI_AB_PROVIDER
PR_RESOURCE_FLAGS=00000000

[AWFAX_XP]
PR_PROVIDER_DISPLAY=Microsoft Fax Transport
PR_PROVIDER_DLL_NAME=awfaxp.dll
PR_RESOURCE_TYPE=MAPI_TRANSPORT_PROVIDER
PR_RESOURCE_FLAGS=00000000
General & Miscellaneous
Version
The final version number for the Memphis release of Windows has not yet been determined. The current beta test version will report 4.10.xxxx (where xxxx is the build number). The released version will be at least this version or higher.
OLE/DCOM
Distributed COM (DCOM) extends the Component Object Model (COM) infrastructure which underlies ActiveX™, transparently and naturally adding support for reliable, secure, and efficient communication between ActiveX Controls, scripts, and Java applets residing on different machines in a LAN, a WAN, or on the Internet. With DCOM, your application can be distributed across locations that make the most sense to your customer and to the application.
Because DCOM is a seamless evolution of COM, the world's leading component technology, you can leverage your existing investment in all ActiveX applications, components, tools, and knowledge to move into the world of standards-based distributed computing. As you do so, DCOM handles the low-level details of network protocols so you can focus on your real business: quickly providing great ActiveX solutions to your customers.
You can configure your components for DCOM using the DCOM Configuration tool. To start DCOM Configuration, select Run from the start menu, then enter "dcomcnfg" at the prompt.
For more information about Distributed COM, please visit http://www.microsoft.com/oledev/olemkt/oledcom/. 
Known Issues:
DCOMCNFG does not have an option to set EnableRemoteConnection
To use a Memphis machine as a remote object server, you need to set  the HKLM\Software\Microsoft\OLE\EnableRemoteConnection registry key to "Y". To set this value, you will need to use OLEView or RegEdit. Valid values for this key are "Y" and "N".
RPCSS Not Started in Some Situations
RPCSS is not launched reliably when a manually-started single-threaded apartment (STA) server is the first caller of CoRegisterClassObject and EnableRemoteConnection is set to Y. When RPCSS is not launched properly, you may observe that remote connection attempts to the server machine fail with error RPC_SERVER_UNAVAILABLE. 
You can determine whether an observed failure is caused by failure to launch RPCSS by either checking whether the RPCSS process is running or manually starting RPCSS before launching the server process. You can work around this problem by pre-launching RPCSS.EXE before any class objects are registered. A convenient place to do this is in the registry at HKLM\Software\Microsoft\Windows\CurrentVersion\Run, which launches when the shell loads, or \RunServices, which launches immediately upon machine boot (i.e., before login). Add a named value (any name) and a value of "RPCSS.EXE". 
Security Information is not Synchronized in Some Situations
If client "A" initializes COM, then client "B" starts and makes a remote COM call, an attempt by Client "A" to make a secure remote COM call fails with error RPC_E_NO_GOOD_SECURITY_PACKAGES. 
You can work around this problem by pre-launching RPCSS.EXE before launching the client process. A convenient place to do this is in the registry at HKLM\Software\Microsoft\Windows\CurrentVersion\Run, which launches when the shell loads, or \RunServices, which launches immediately upon machine boot (i.e., before login). Add a named value (any name) and a value of "RPCSS.EXE".
Multimedia
DirectX
This release of Memphis contains a beta version of DirectX 5, including drivers and new API support.  For this release, DirectX 5 features:
•	AGP Support
•	MMX support in both Direct3D and DirectDraw
•	Support for DirectX applicatons on multiple monitors
•	Support for force feedback and USB input devices
•	3D audio hardware support
•	Enhanced performance and robustness
Testing DirectX 5
Most of DirectX 5's new features for this Memphis beta are designed to enable new hardware functionality, while still preserving compatibility with older versions of DirectX and Windows.  To test DirectX, please run your existing DirectX games and other applications on Memphis, and report any problems or compatibility problems you find through normal Memphis bug reporting channels.
Known Issues
Users running DirectDraw applications on secondary displays on multiple monitor systems may experience the following problems:
•	Secondary monitors may not repaint properly when exiting DirectX applications.
•	If the primary and secondary monitors are running at different bit depths, DirectX applications running on secondary displays may display with an incorrect palette.
•	This version of DirectX will issue a warning starting May 5, but it can be ignored.  The next release will have a later warning date.
ActiveMovie
ActiveMovie 2.0 is an architecture that controls and processes streams of multimedia data; it is also a run time that uses this architecture to allow users to play digital movies and sound encoded in various formats, including MPEG 1.  The runtime is what is shipping with Memphis.  ActiveMovie’s playback capability makes use of video and audio hardware cards that support the Microsoft DirectX ™ set of API’s.  ActiveMovie 2.0 also plays movie files in .avi or Apple® QuickTime® .mov format. Please test ActiveMovie runtime functionality and provide feedback you may have.
Windows Management Infrastructure
The Windows Management Infrastructure collects information about configuration of devices and the system as a whole. This information is stored in the Registry, and made available through extensions to the Registry API. This software is the foundation of Microsoft’s support for DMI. The package can be installed through “Add/Remove Programs” in the control panel. The package is selected from the list under “Windows Setup”. When Windows Management Infrastructure is installed, a new key is created in the Registry, HKLM\DesktopManagement. There will be many entries under this key, and instrumentation code (which “mines” device information) will be installed.
Running ScanDisk after bad shutdown
If you don’t shut your system down cleanly, or if your disk suffers a hard error, ScanDisk will be run automatically when your system restarts. By default, a message will be displayed before ScanDisk is started. You can override this behavior by setting the AutoScan variable in the [options] section of your MSDOS.SYS file:  
•	AutoScan=0 will disable this feature entirely.
•	AutoScan=1 is the default; the system will stop and prompt you before running ScanDisk. After one minute, ScanDisk will run automatically.
•	AutoScan=2 will launch ScanDisk (if required) automatically, without stopping and prompting first.
Updated Time Zone, Daylight Savings Time and International Dialing Codes settings
Since Windows 95 originally released, a number of changes have occurred in the time zones, daylight savings time start/stop dates, and local participation in daylight savings time. In addition, a number of telephone systems worldwide have changed their international dialing codes. Please verify the cities & their time zones, check the daylight savings times switchover dates and check the international dialing codes for various countries.
Service Packs
Memphis contains the complete set of fixes that were made available in Service Pack 1 for Windows 95:  For a complete list of SP1 changes see http://www.microsoft.com.
There is no need to install SP1 on top of Memphis. If you inadvertently install SP1 on Memphis, however, no harm will be done. All of the Memphis files have a newer version, so SP1 files will ignore them automatically.

Release Notes:  Known Third-Party Application Issues
The following applications may not install or function properly with Memphis. Please promptly submit bug reports via MSREPORT if you discover any additional application incompatibilities introduced by Memphis.
General note on SHARE.EXE
Memphis no longer supports real-mode MS-DOS Share.  The functionality is available from an MS-DOS box while Windows is running.  However, some applications check for the existence of a file named share.exe.  You can create this file in \windows\command with any file, and these applications will work. Memphis will provide a dummy version of share.exe for these apps.
General note on SETVER
SETVER has been removed from the default environment to save memory and increase performance.  If you need to have the version set for MS-DOS apps, you can load setver in the config.sys file by adding the appropriate line.
Adobe Premiere 4.2
During installation Adobe Premiere 4.2 incorrectly detects Memphis as a 16-bit version of Windows. Currently, the only way to avoid this problem is to install Adobe Premiere prior to upgrading to Memphis. This problem will be fixed in a future release of the operating system.
Agent 95 by Connectix 
This memory management software fails to start after installation.  This will be fixed in a future version.  
Delrina WinFax Pro 7.0
If Memphis is installed over Delrina WinFax Pro 7.0, communication problems prevent the fax from functioning properly. This will be fixed in a future version of the operating system.
Do it Yourself Lawyer by Expert Software 
Do it Yourself Lawyer does not install without Share.exe (which has been disabled to support FAT32).   To work around this issue, create a dos directory and create a bogus share.exe file.  Continue to install software.  This will be fixed in a future version of the operating system.
Expert Forms  
An error message "Illegal Operation" will result by choosing "print control" from the "layout" menu bar in Form Design.  This will be fixed in a future update.
Great Gourmet 1.0 by Expert Software 
Great Gourmet does not install without Share.exe (which has been disabled to support FAT32).   To work around this issue, create a dos directory and create a bogus share.exe file.  Continue to install software.  This will be fixed in a future version of the operating system.
LapLink 6.0
LapLink version 6.0 a and b will not operate when installed on Memphis using 16-bit color. An immediate work-around involves the following steps: change the system color to less than 16-bit, reboot, install LapLink 6.0, change the color back to 16-bit (if desired) and LapLink will run. Please note that this problem does not exist with LapLink versions 7.0 or later.
Remove-IT 95
The Remove-IT 95 applets (two) located on the Start-Up menu will not function properly if you try to execute them while logged on to a Windows NT domain server. A work-around is to remove both applets from the Start-Up menu, reboot, wait a minute or two then launch the applets. This will be fixed in a future release of the operating system.
Resume Writer 1.0 by Expert Software
Resume Writer does not install without Share.exe (which has been disabled to support FAT32).   To work around this issue, create a dos directory and create a bogus share.exe file.  Continue to install software. This will be fixed in a future version of the operating system.
SPQR 
Color degradation will result if attempts are made to run this game in a window.
Using COMSPEC variables pointing to Network comand.com files
If you are on a network and are currently mapping your comspec to remote network file servers, you may get “incorrect DOS version” errors (and an explanation of the version shipping with Memphis being an updated ver 7.1 etc.). You need to map the comspec to the local copy or to a compatible version on the network.
Error using data access from Microsoft Office Standard for Windows 95 version 7.0
If you install Microsoft Office Standard for Windows 95 version 7.0 on a machine running Memphis, and you perform certain ODBC operations, you will receive an error “Failure to load expression service” when using the Access ODBC driver from Office apps such as Excel or Word. To correct this problem you need to obtain the Microsoft Office for Windows 95 version 7.0b release from Microsoft Product Support. You can obtain a copy of Microsoft Office for Windows 95 version 7.0b by calling the Microsoft Order Desk at (800) 360-7561. If you are outside of the United States, contact the Microsoft Subsidiary in your area. To locate your subsidiary call the Microsoft International Sales Information Center at 206-936-8661. This problem does not affect any versions of Microsoft Office Pro. Also, if you do not use these ODBC functions, you do not need the updated versions.
Office 95 and 97 Find Fast Utility
Beta sites have reported that if the Find Fast utility is in the startup group, the system may experience random hangs, and that removing this utility from the Programs Startup folder eliminates the problem.
Installing Win32 SDK Debug Components from MSDN CD
The MSDN components are from Build 950 and will not work properly with some of the Memphis components. Installing the SDK or DDK debug components will render your system unusable and you will have to reinstall Memphis. We will be releasing the Memphis debug components in the next release.
Disk Utilities
In general, older disk utilities that perform low-level disk functions, such as defragmenters, disk repair tools and disk compression utilities, will not function properly on FAT32 drives. In most cases, the vendors have updated their utilities to be FAT32 aware. The older versions of these utilities should continue to work properly on Memphis on FAT16 drives. The disk utilities included with Windows 95 (ScanDisk and Disk Defragmenter) have already been modified and fully support FAT32. A version of DriveSpace 3 is included with Memphis that handles drives up to 2 GB, but it will not compress on a FAT32 volume. 
Norton Utilities/Anti-Virus/Navigator for Windows 95
Many of the utilities contained in the original release of these products will not function properly on FAT32 drives. In some cases, (e.g. Norton Disk Doctor), they will not function properly on FAT16 drives under Memphis. The 2.x versions of these utilities support FAT32 completely. If you use the older versions of these products on Memphis, in many cases warning dialog boxes will be displayed indicating that you should obtain an updated version of the program from Symantec. Please submit bugs if you find cases where these dialog boxes are being displayed when they shouldn’t be, or if you encounter problems for which no warning dialog box is displayed.
If you are using Norton Anti-Virus 2.x and plan to convert your boot drive to FAT32, be sure to adhere to the release note above, in the “FAT32” section of the Application Notes. 
Microsoft Plus! for Windows 95
Memphis includes an updated DriveSpace that is compatible with Plus!. When you install Microsoft Plus! on Memphis, it will not actually install any DriveSpace 3 files. However, the DriveSpace 3 advanced features, including Compression Agent, will be enabled when you install Plus!. 
IMPORTANT NOTE: If you compressed your hard disk with Microsoft Plus! and then upgraded to Memphis, if you need to re-install Microsoft Plus!, do not use the "Re-Install All" option in Microsoft Plus! Setup. If you need to re-install Microsoft Plus! and your disk is compressed, you must delete your Setup.STF file (which should be in your \Program Files\Plus!\Setup folder) and then re-run Plus! Setup.
SHARE.EXE no longer works in MS-DOS mode
In order to support FAT32, SHARE support has been disabled in the real-mode MS-DOS kernel (sharing support is still provided under Windows 95 however), regardless of whether you have any FAT32 drives. If you use applications that require SHARE support in MS-DOS mode, please submit bug reports about them.
Adobe Photoshop 3.0.4
If you have more than 2GB of free space on your boot drive, Photoshop may be unable to run. You may be able to work around this by setting a large maximum size for your swap file.
Dunce 2.02
The shareware Dial Up Networking utility Dunce 2.02 will not work correctly with Memphis. Version 2.03 is now available which will work with Memphis.
Arcada Backup
You may need to remove the Arcada Backup VXDs from your \windows\system\iosubsys directory if you use this application. This can prevent your system from booting.
WinZip 6.1 32-bit
When attempting to unzip a file you may receive an error message "Cannot Access this folder. Path is too long." You may be able to continue successfully at this point, or you may not. You may need to use another unzip utility for this release. This will be fixed in a future version of the operating system.

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, the new backup utility will be installed. This new backup will be able to restore from Windows 95 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 OSR-2, you can upgrade your current version of Windows 95. We recommend you upgrade your current version of Windows 95. 
Making an Emergency Boot Disk
You can make several Emergency Boot Disks (EBDs). 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 Microsoft 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
Note:  If you load a real mode driver with the Config.sys line switch /D: with any field name that could reflect an actual file name, that file will be unaccessable while the driver is loaded and running.  i.e. /D:test  -then any file named test, reqardless of extension, will not be available to open.
Reboot the machine with the Emergency Boot Disk.
Uninstalling the Memphis environment
An option to back up your current Windows 95 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 cleanly installed Memphis. If for any reason you would like to return to your original Windows 95 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 Windows 95 environment back to your windows directories. The backup files can only be executed one time and are not preserved 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 Windows 95 has no long file name support. The only way to reinstate long file name support is after Windows 95 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 formatted. 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 (found on the Memphis CD), with the /s switch.
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 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 MS-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, for your 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.