Windows 98/4.10.1525/Release Notes

From BetaArchive Wiki

Microsoft® “Memphis”

Beta 1

Release Notes

June 25, 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.

Contents

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 9

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 17

Expiration of the Software 17

What is Memphis? 18

What’s New in Memphis 19

Application Notes 22

Hardware Support 22

FAT32 22

Multiple Display Support 26

Win32 Driver Model (WDM) 30

PCMCIA 35

Power Management and OnNow.............................................................................................................................................. 36

Device Drivers 39

IrDA Device Drivers and Utilities.......................................................................................................................................... 44

Smart Card Support 45

Under the Hood 46

Internet 47

Internet Explorer Setup 47

Internet Explorer 4.0 Known Issues.................................................................................................................................... 48

Task Scheduler Known Issues.................................................................................................................................................. 50

Microsoft Virtual Machine for Java................................................................................................................................. 50

Microsoft Outlook Express 57

Web-Based Enterprise Management support................................................................................................................. 60

NetMeeting 60

Internet Connection Wizard.................................................................................................................................................... 60

Shell, User and GDI 61

My Documents Folder Enhancements............................................................................................................................... 61

Plus! Features 62

Miscellaneous User/GDI enhancements........................................................................................................................... 62

Image Color Matching 2.0 API................................................................................................................................................... 63

Display Control Panel Improvements............................................................................................................................... 64

Support Tools 65

Windows Tune Up Wizard 65

Memphis HelpDesk 66

Windows Update Manager 66

Web-based Bug Submission 66

Dr. Watson 67

Registry Scan and Backup 67

Microsoft System Information Utility 4.1....................................................................................................................... 68

System File Checker 69

System Troubleshooter 69

Automatic Skip Driver Agent................................................................................................................................................... 71

Communications and Networking................................................................................................................................................... 72

Dial-Up Networking and Dial-Up Scripting.................................................................................................................... 72

Point-to-Point Tunneling Protocol (PPTP).................................................................................................................... 72

TAPI 2.1 75

Unimodem/V 75

ISDN 1.1 Accelerator Pack 76

NDIS 2 77

NDIS 5 78

ATM 78

Memphis TCP-IP 79

Winsock 2 79

Resource ReSerVation Protocol (RSVP)............................................................................................................................ 82

Remote Access Server 84

Microsoft Service for NetWare Directory Service (MS-NDS)............................................................................. 85

Microsoft 32-bit DLC protocol stack................................................................................................................................ 85

3rd Party Networking Release Notes................................................................................................................................. 85

Applets and Utilities 88

MS Paint 88

Backup 88

Compression Agent 89

Disk Defragmenter Optimization Wizard........................................................................................................................ 89

Task Scheduler 91

Calc 92

WordPad 92

MSD 92

HyperTerminal 92

Windows Scripting 93

Imaging by Eastman Kodak 93

Microsoft Fax Installation for Memphis....................................................................................................................... 94

Broadcast Architecture Components.............................................................................................................................. 96

TV Viewer Application 97

The Microsoft Network (MSN).................................................................................................................................................. 99

Online Services 101

America Online (AOL) 101

AT&T WorldNet Service 102

CompuServe 102

MSN 102

Prodigy 103

General & Miscellaneous 103

Version 103

Disk Defragmenter Optimization Wizard...................................................................................................................... 103

Invoking Startup Menu with F8 Key................................................................................................................................... 104

TweakUI 104

OLE/DCOM 105

Multimedia 106

Windows Management Infrastructure........................................................................................................................... 107

Running ScanDisk after bad shutdown.......................................................................................................................... 107

Updated Time Zone, Daylight Savings Time and International Dialing Codes settings............... 107

Service Packs 108

Platform SDK 108

Known Third-Party Application Issues...................................................................................................................................... 108

General Application Notes 108

Specific Application Issues 110

Technical Assistance with Setup........................................................................................................................................ 114

Making an Emergency Boot Disk.......................................................................................................................................... 114

Creating a Bootable Floppy 114

Uninstalling the Memphis environment........................................................................................................................ 115

Installing Windows 95 Memphis onto a newly formatted hard disk......................................................... 115

Installing Windows 95 Memphis onto a blank hard disk (OEM Setup)........................................................ 116


General Information

Welcome to Memphis, the next major release of Windows. This is the Beta 1 release. Memphis has been through three previous Developer Releases, and a number of interim-level releases to a limited number of external sites. This release incorporates most of the key features planned for Memphis, and is now ready for widespread beta feedback.

This document describes setup, new & updated features, and known issues. 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.

Before You Start

First, a word of caution. Although we have put much effort into the verification of this software, it is pre-release software that will be used by every application that you run. Microsoft strongly suggests that you back up any important existing data and programs before you install or run any of this software. Also, whether you intend to use FAT32 or not, be sure to make a new Startup disk when running Setup. Startup disks created with the released version of Windows 95 are not compatible with Memphis.

Setup requires approximately 120 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. Once file copy is complete no other user input is required before the Windows Desktop is presented to run an application.
  • 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.
  • Memphis changes the way Windows handles file version conflicts during setup. Previously, when setup tried to overwrite a file that had a larger version number or different codepage than the one being copied users would be presented with a message box asking them whether they wanted to keep the old file or upgrade to the new one. Memphis now automatically upgrades to the new file and backs up the one that was already on the machine in the C:\Windows\VCM (for "Version Conflict Manager") subdirectory. A list of all the files backed up in this manner along with their destination directories and the dates on which they were backed up is kept in the C:\Windows\VERBACK.LOG text file. If there are no version conflicts during setup the VCM subdirectory and VERBACK.LOG file will not be created. Multiple versions of the same file may be backed up in the VCM directory: Setup will alter the backed up file names as needed and make note of these changes in VERBACK.LOG. This new behavior only occurs during Memphis setup. Version conflicts encountered during software updates after Memphis has been fully installed on the machine will be displayed to the user as before. For beta, the only way to recover a conflicting file is to copy the file back manually. We will be developing UI that will help with this capability.

SETUP Release Notes

  •  Setup hard disk space requirements - The amount of free hard disk space required by the Win 95 to Memphis upgrade is determined by the cluster size of the target partition and the number of components already installed in Windows. Memphis requires at least 90 MB of free hard disk space with the smallest cluster size and minimum installed components to complete. This number can be as large as 243Mb to install to a clean partition with the largest cluster size and all components selected. If Memphis stops the setup due to a lack of available free hard disk space this will be calculated to your specific combination of these variables. You can do the following to free additional hard disk space.

¨ Empty recycle bin

¨ Empty www cache

¨ Delete tmp and bak files

¨ Backup/move off the partition MSDOS programs

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.

  • Low Disk Space Warning - In some circumstances, you can get a low disk space warning that allows the user to continue, only to get another disk space message later on in setup that blocks from continuing. The second dialog is the more important one and hard disk space must be freed up to the amount indicated in the message.
  • My Documents Folder - Previous testers may have a “My Documents” folder on their desktop. The old “My Documents” folder should be renamed to “Obsolete Desktop My Documents Folder” during setup. Likewise, the “Public Documents” folder gets renamed to “Obsolete Public Documents Folder”. A new “My Documents” icon will be added to the desktop. This is not truly a folder, it’s just a shell extension shortcut to the root My Documents directory. All files from the “Obsolete” directories should be moved elsewhere (the new “My Documents” folder perhaps) and the directories should be deleted.

You will need to take special steps to enable this in Beta 1. Please see instructions under the Shell section below.

Winstone97 will not successfully complete with My Documents installed. The most common symptom is that Powerpoint will wait indefinately trying to load a file.

  • Scanning your registry produces a “Registry error (7)” - When installing Memphis on top of any previous version of Windows 95 or Memphis you may receive a registry error 7 during setup. You are given two options. Yes to continue with setup and No to exit setup. Select Yes to continue with setup. This will skip over the registry scan portion of setup. We are currently investigating why the error 7 message is given during setup.
  • If you press CANCEL during setup, you must reboot before trying to run Setup again. This will be fixed in future releases.
  • Xircom 10/100 or Intel 10/100 Cardbus - if you try to logon to the net it fails because the card is rejecting data packets. A new driver is being sought after from the OEM’s.
  • 3COM Etherlink III PCMCIA - Fails to be correctly identified. Find the new drivers/inf files on the 3com web page. Once installed works normally.
  • 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.
  • "Starting Windows 95" dialog may no longer be presented at boot. By default, the 2-second delay for the user to hit F8, F5, or F4 for the different boot options has been eliminated. The user will not have much time to respond with the function keys. To gain access to the menu, hold the CTRL-key down during the Post to display the boot menu.
  • Running Setup from a MSDOS prompt - "Setup cannot find high memory manager" repeats.  When trying to install from real-mode [command line mode, MS-DOS mode] some machines will show the error "Setup cannot find a high memory manager and cannot continue." If this happens, add DEVICE= line to your CONFIG.SYS for HIMEM.SYS.
  • Notebooks that have a shared bay for both CD-ROM and Floppy Disk can not make a boot disk during Setup. Following the prompt to insert a diskette into drive A will require the floppy drive to replace the CD-ROM. Switching devices causes a reboot in most, if not all machines, and the loss of the boot media in the removed CD-ROM driver. When the prompt appears asking for a floppy disk, press cancel to bypass the boot disk creation tool.
  • 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.
  • Sharp Laptops - The SHARP laptops have an APM BIOS which prevents Memphis from running on them. Workaround: Don’t install Memphis Beta1 on SHARP laptops
  • 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.
  • Monitors and mice – can be miss identified. The monitor can be identified as a generic plug and play monitor that can be user selected correctly. The Glidepad pointer found on many portable computers is identified as the generic PS2 mouse and should be reinstalled with OEM drivers. The MS Wheelmouse is identified as a PS2 mouse and should not be reinstalled with original floppy disk drivers. Functionality should be unaffected. Kensington Thinking Mouse is made non-functional. Reinstall with OEM drivers delivered with the mouse. The MS PS2 Mouse can be non-functional when setup is complete. Edit the [386Enh] section of system.ini with

Mouse=*vmouse, msmouse.vxd

  • 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)

Emm386 do not use inclusion range B000-C7FF

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.
  • IBM Aptivas -

On some newer IBM Aptivas with a factory load, you will run into a fatal exception 0D (trap 13) after third boot during the last phase of setup. This is caused by Tela-lit, the driver that enables the animated icons on the desktop. This can be avoided by disabling the “desktop effects” prior to upgrading.

Steps to avoid the trap 13:

Right click on the “Desktop effects” icon in the Systray (next to the clock).

Select “exit”, this will temporarily disable the animated icons on the desktop.

Proceed with the setup normally.

If the effects are listed in “Startup”, they will be enabled by default after setup finishes.

If they are not, enable them by running PROGRAM FILES\IBM\APTDESK\MVSLOADER.EXE after setup finishes.

  • Novell Client32 fix is available through the Novell Company to provide the correct installation parameters.
  • Intel EtherExpress PRO/10+ and Intel 82595 - These Ethernet cards set the default Duplex Setting to "Force Half Duplex", instead of “Auto Negotiate.” On 2nd boot during setup you will be prompted with: “Setup can not access the network to complete the installation”.

Do you want to:

· Reboot (Recommended if you skipped logging on.)

· Change your network settings before continuing?

· Continue without access to the setup files? (Not recommended)

Select the 2nd option, and change the Duplex Setting Property on the net card to "Auto Negotiate" select OK and continue with setup.

  • Setup sometimes creates a C_ directory off of the Start Menu - This is usually seen on clean installs, and will be fixed by the next beta release. You can safely delete this menu item.
  • Startup Disk


  1. 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.
  2. To run setup, copy the OAKCDROM.sys and MSCDEX.EXE to the C: along with the autoexec.bat and config.sys. This will allow you to boot from the c:\ drive and maintain access to the CD-ROM drive through the reboot process.
  • Net Login Message - If you inadvertently type the wrong id/password to log on the network you will not be prompted to change it, even during a restart.

Workaround


  1. Click Start, run, type Regedit.
  2. Click Edit on Menu, select Find, Type autologon (all one word)
  3. Delete the autologon. Value
  4. Reboot AND computer network will appear.
  • If you format your hard disk - you will need a Startup disk (which has a generic CD-ROM driver) or your interface card and manufacturer’s 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.
  • Disk tools can not be set to run in unattended mode via Task Scheduler. Manual execution has not been affected.
  • Performance settings are lost during setup - To change the values after upgrading, do the following:

Workaround


  1. Right-click My Computer
  2. Click the Performance Tab
  3. Click the File System button in the Advanced Settings group.
  4. Change the drop-down list box to the desired value.
  • 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 scenarios 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 incorrectly reporting 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.

Important Issues to Note

MSN Email – If you use MSN for your email provider, after you install Memphis, you will need to reconfigure your system to get your MSN Email. Please see the MSN section below for specific instructions.

MS Money and other Internet Explorer 128-bit users – Installing Memphis will disable your 128 bit encryption. To restore this feature, please do the following:


  1. Copy the two files (rsabase.dll and sigres.exe) from the \betaonly\rsa directory to your \windows\system directory From the Start/Run menu, type “regsvr32 rsabase.dll”. You should see a dialog box indicating that it registered successfully.

Note that this will not enable 128-bit encryption on systems that did not previously have it installed.

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.

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

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. 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. We are introducing the Windows Tune Up Wizard in this beta release which automatically schedules tune up jobs to maintain your computer on regular basis.

Multimedia - DirectShow 2.0 and DirectX 5 - These multimedia enhancements provide improved gaming and multimedia infrastructure.

*Please note that DirectAnimation and some of the other new Multimedia controls are not included in this version of Memphis. They will be available in future builds for download from the winbeta server, and in Beta 2. Once IE4 releases their public beta, some web content may not render properly until you install an updated Memphis release.

Drivers – We have greatly enhanced the networking, display, printing, monitor and modem device driver support among others. 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.

Broadcast Architecture & TV Viewer  - Memphis includes software that broadcast-enables your computer. A broadcast-enabled computer is a versatile next-generation computer that blends television with exciting new forms of information and entertainment. It blurs the line between television, web pages, and computer content. It also enables the reception of broadcast web pages and other live data feeds, such as stock quotes, news feeds and even streaming audio and video.

In addition to viewing television programming from cable, over-the-air, and satellite networks, broadcast reception hardware can also be used as "receive only" network devices. You'll receive true data broadcasts of web pages, multimedia streams, and data packets from television stations and networks that provide this information.

For more information visit http://www.microsoft.com/hwdev/pcfuture/bcast1.htm. For more information on broadcasts of internet-standard information over regular television signals visit http://info.internet.isi.edu/in-drafts/files/draft-panabaker-ip-vbi-00.txt.

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 CVT1.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. However, there are several third-party utility products on the market that do support converting back from FAT32 to FAT16.

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, the answer is 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, the answer is 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 - 8GB4k

8GB - 16GB 8k

16GB - 32GB16k

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

Release notes 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 CVT1.EXE. 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

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

You may notice problems running Quick Time applications with multiple display support enabled. Applications may not run correctly on a secondary display, or crash.

If you have these problems, edit your QTW.INI as follows:

Change the line Optimize=driver (or whatever value) to Optimize=bmp

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 GX
  • S3 764V+ (765) , Trio 64V2
  • S3 ViRGE
  • S3 Aurora (S3M65)
  • Cirrus 5436,7548,5446
  • ET6000
  • ATI Rage 1 & 2 (VT & greater)

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, i.e. 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 DirectShow) will not display across two displays simultaneously at this time. This will be fixed in a future beta.

Toshiba Tecra: It is possible to specify the memory address range of the video ROM on this notebook computer. It must be set to either C000 or E000 in order to work with MDS.

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 Interface Devices (HID)). The new WDM Stream-class support in Memphis provides infrastructure for USB audio and camera devices.

Human Interface Devices (HID)

Keyboards, keypads, mice, pointing devices, and game controllers that are compliant with the USB I/F 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 USB/HID 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 USB/HID 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. USB/HID game controllers, however, are treated as distinct devices just as can be expected so that applications can distinguish which input data 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. For example, HID-compliant virtual reality devices, simulation devices, monitor control devices, power devices, etc, while recognized as HID-compliant devices by the OS, are not automatically supported since these device types require additional, device-specific software (e.g. drivers, special applications or control panel applets, etc.) to be installed on the system. The device-specific software needs to be developed and supplied by device vendors or EOM’s. Software developers should consult the WDM DDK for details about how to develop custom drivers and applications for HID-compliant devices.

This release of Memphis includes an interim release of DirectInput 5.0, which in turn includes a new Control Panel applet for Game Controllers which replaces the Windows 95 Joystick Control Panel applet. While the new Game Controllers applet should work fine with USB/HID game controllers, it is not yet Plug and Play aware, etc. Also, the “Add Other…” button in the Add Game Controller dialog is not functioning properly. Instead, launch the Add New Hardware applet directly instead from the Control Panel. These issues will be addressed in upcoming releases of Memphis.

To get USB/HID game controllers 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. Memphis will first search for new plug and play devices on you system, click “Next”,
  4. select “No” to “Do you want Windows to search for your new hardware?” and click “Next”,
  5. select “Sound, video, and game controllers” as the hardware type, and click “Next”,
  6. 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 core specification as well as the new supplemental HID Usages Table specification v0.9 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.

The released version of Memphis will support DirectSound 5. Beta versions of Memphis will support Direct Sound 5 as it becomes available.

DirectShow is the preferred 32-bit API for audio. DirectShow is supported natively by USB audio. This is the native mode for USB audio support.

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)
  • DirectShow 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 the following: USB conferencing cameras, 1394 DV devices, desktop cameras, TV viewing, multiple video streams support, and VPE capture support. It is based on kernel streaming architecture, and tightly integrated with DirectShow(formerly known as ActiveMovie) 2.0. The following DirectShow 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 DirectShow 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 DirectShow 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.

  • Compaq Trek Laptops with the TI 1131.1 Cardbus controller do not work with Cardbus PCCARDS for Beta 1. You will see Code 10 in device manager under the device class of the Cardbus card. This should be fix in the next release of the beta.
  • Cardbus issue with Xircom 10/100 Ethernet pccards. If you try to logon to the net with a Xircom 10/100 Cardbus card (or Intel 10/100 Cardbus) it fails to allow connectivity to the net. Device Manager will not show an issue and everything appears ok. This is being looked into, and may be Xircom driver related.
  • If a laptop hangs on 2nd boot at the stage of setting up new hardware. Check to see if the driver PCOMM2.386 is in use. This driver file is for the Tranxit Lucent Modem. Clean install is OK, but upgrade to Memphis with this PCOMM2.386 in the SYSTEM.INI [386enh] section, cause the system to hang at setting up hardware stage.

The systems that this behavior has been seen using the driver on; IBM 760 , Toshiba’s 660 Protege, Toshiba TECRA 740cdt and others using this driver for their Lucent built in modem.

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 be 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.

Users of the Matrox Millenium (MGAX64) display adapter may experience resumption failures when they invoke the “suspend” option from their start button or when their system auto-suspends. This issue revolves around the Matrox dirvers’ inability to fully and correctly configure themselves during boot and to then successfully re-configure themselves when the ‘resume’ command is given. Users may want to disable APM functionality in their systems’ BIOS in order to avoid failed resumes when the system auto-suspends. Users may also want to contact their hardware vendor regarding updated software drivers for their device.

When using a portable computer, there should be two columns labeled “Plugged in” and “Running on batteries” under Control Panel\Power Management\Power Schemes.  The ‘running on batteries’ column would dictate how APM should behave while the laptop is not plugged in. This is not the case. For this release the ‘plugged in’ column dictates how APM will operate whether the computer is running on A/C power or running on batteries.  At this time the ‘running on batteries’ column should be ignored. Configure the ‘plugged in ‘ column as though it were the only column on the tab.

Battery Notes:

Do not rely on Low Battery or Critical Alarm function when monitoring your battery life. This function, located in the Power Management Control Panel under the Alarms tab, is unfortunately not yet in operational condition.

On some portables, the Battery Meter will not indicate time remaining. This will be fixed in future releases.

Crystal Audio System CODEC on Toshiba laptops.

When attempting to suspend a Toshiba laptop with the Crystal Audio System CODEC, Memphis will produce a non-recoverable Fatal Exception 0Eh.

The user can work around this problem by either renaming the hidden file Vwstream.vxd in the \Windows\System folder or by disabling the Crystal PnP Audio System CODEC in safe mode. This can be done with the following steps:

  1. Restart the computer and strike the F8 key as soon as the BIOS beep sounds.
  2. That will cause the Memphis startup menu to appear. Choose Safe Mode (option 3).
  3. Upon boot to Safe Mode, click on Start, Settings, then Control Panel.
  4. Double-click on the System icon in Control Panel and click on the Device Manager tab.
  5. Expand the Sound, video and game controllers section by clicking on the “+” next to it, click on “Crystal PnP Audio System CODEC” to highlight it, and click the Properties button.
  6. Under the General tab, click on the checkbox labeled “Disable in this hardware profile.”
  7. Restart the computer as normal.

This will cause lack of sound and inability to play MPEG files, but will prevent the Fatal Exception 0E when attempting to suspend the computer.

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, rendition, s3mm, s3v.

For more technical documentation on Display Drivers - see the DirectX DDK.

Memphis display driver upgrade testing procedure

Microsoft is working to make the Windows 95-to-Memphis upgrade process as smooth as possible. Part of this is insuring that display drivers are upgraded only when appropriate. The drivers included with Memphis are the most solid drivers available for Windows, and provide support for most available video adapters. However, some hardware-dependent third-party software may not run properly on the generic Microsoft-provided drivers. Similarly, some nonstandard third-party Windows 95 drivers may not function properly under Memphis. To provide the Memphis team with the information needed to verify the current setup algorithm, we are asking all beta testers to perform this simple display driver upgrade test.

* Take note of the display you have in your system prior to installing Memphis

  1. Install Memphis
  2. This is the "BEFORE" scenario. Take note of whether your system is running properly. Pay special attention to software that came with system or video card (e.g. custom control panels, taskbar icons, TV tuners, TV-output). Have any applets/control panels disappeared? Do they continue to function properly? Are some controls disabled? Would you accept this behavior in the final release of Memphis?
  3. Run "Internet System Update".
  4. If any display drivers are available for update, choose to install them. Otherwise, skip to step 6.
  5. This is the "AFTER" scenario. Repeat step 2 for this scenario.
  6. Use the Memphis Bug Reporting tool to send this information to Microsoft regardless of whether there are any problems or not. Tell us whether the upgrade went as you expected, and if not, what you think should happen. Include as much information you can about the "BEFORE" and "AFTER" states of your system. Be sure to clearly separate the two scenarios in your report. Be sure to choose "YES, include my computer's configuration files with my report" on the "OK to Include System Information page". Indicate that the bug is on this machine, and "system hangs" for "Problem Severity".

Note: It is important that you run Step 6 exactly as specified. You need to perform these steps even if your machine works perfectly BEFORE & AFTER the upgrade to provide us with the information we need to improve the driver upgrade process.

The default drivers that come with Memphis for the Matrox Millenium can be replaced with the Matrox Millenium drivers available at http://www.compaq.com/support/files/desktops/Windows95/Deskpro6000/5166.htm

These files work for my specific machine configuration and others are available from the Compaq page for other computers.

It is important NOT to keep the newer versions of files when conflict dialogs are displayed. (This way the Memphis files are replaced).

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.

Memphis does not ship with Yamaha OPL sound drivers at this time. However, if you have Yamaha OPL hardware, the drivers can be found in Other\audio\Yamaha OPL4.03 on the Memphis CD-ROM. You can point to this location in the following situations:

  1. While running Memphis setup, if the program cannot find the drivers for the device.
  2. If the device shows “not present, not working properly, or does not have all the drivers loaded” in device manager, you can go to the Driver tab and click on “update driver”, pointing the program to this location.
  3. During hardware detection if you are asked for drivers.

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

599 new printers are supported. This release also includes the 839 printers that shipped with Windows 95 OSR-2. We’ll add some new models in the next beta.

Network Card Drivers

New Support for Network: 170 Adapters

Adapters Affected by Updated Drivers: 198

NDIS 2.0 Functionality

In previous releases of Memphis, NDIS 2.0 support was removed for many network cards. In this release of Memphis, support for NDIS 2.0 drivers is present for many of the network cards supported in Memphis. If your network card is not supported with NDIS2.0, you will need to obtain a driver from the manufacturer that does support NDIS 2.0. These drivers can typically be installed by decompressing the downloaded file, selecting “Have Disk” in the driver selection dialog box, and directing Memphis to the directory where the drivers are located.

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.

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 their PC Manufacturer did not enable it originally.

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.

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)

Monitors

We’ve added approximately 175 new monitors to the built-in supported list.

Human Input (Keyboards, Joysticks, Mice, Game pads)

Look for new drivers built-in for these devices in the next beta release.

Using the MS Sidewinder Pro with Longbow Gold - switching resolutions may cause the joystick to stop responding.

A patch exists for this problem at http://www.ea.com/janes/news.htm

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.
  • Logitech PageScan USB sheet fed scanner. Support includes the TWAIN data source. This scanner also supports push mode scanning. In this release the machine must be rebooted after installation to enable the use of the Logitech USB scanner. This will corrected in the next release.

Memphis support for scanners and cameras includes “push mode” operation. Applications need to be revised to take advantage of this functionality. The Eastman Kodak “Imaging for Windows” application in Memphis now operates in push mode and is associate with the USB Logitech and HP 5 p scanners on installation. To further adjust the association of applications with device events use the “Scanner and Camera” control panel. 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/uncheck the application and it will be launched when the buttons on these devices are pressed. If more than one application is associated with the same device event, a dialog box will appear asking the user to pick one of the choices. If no choice is made within 20 seconds the dialog box will disappear and no application will be launched.

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.

  1. 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.
  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. 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.

  1. 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.
  2. 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”.

Smart Card Support

This beta release is based on the PC/SC Workgroup Interoperability Specification for ICCs and Personal Computer Systems. It provides the necessary files needed to enable smart card-aware Windows application(s) and/or service provider(s) to communicate with a smart card through a reader attached to a Windows PC. The base components included on the distribution media require a device driver from a smart card reader manufacturer in order to be useful. No device drivers are included with this beta release. Likewise, a Smart Card Service Provider (SCSP) dynamic link library is needed to expose the services of a given smart card for use by a Windows application and should be distributed with the smart card by the card issuer. Only generic service providers are included with this release for common, low-level card services.

This release does not include the Smart Card SDK and Smart Card DDK components. These must be obtained separately from Microsoft. In order to develop a device driver or service provider, one must obtain a licensed copy of the Smart Card DDK and Smart Card SDK, respectively.

Installation

To install the Microsoft Smart Card Base Components on a target machine, run SETUP.EXE from the betaonly\scard directory of the distribution media.

There is a known problem with the setup utility when installing the smclib.sys file on Memphis. The setup utility incorrectly installs the smclib.sys file in

%SystemRoot%\system32\iosubsys

instead of

%SystemRoot%\system32\drivers

The workaround for this problem is to move the smclib.sys file from the iosubsys directory to drivers directory.

After installation of the Microsoft Smart Card Base Components and any smart card reader device driver(s), the machine must be rebooted for the new settings to take effect.

Uninstall

To uninstall the Microsoft Smart Card Base Components go to the Control Panel (under ‘Settings’ on the Start menu) and start the ‘Add/Remove Programs’ applet. Select “Microsoft Smart Card Base Components" from the list of programs displayed in the scroll box and then click the ‘Add/Remove’ button. After uninstall of the Microsoft Smart Card Base Components and any smart card reader device driver(s), the machine must be rebooted.

Notes:

The smclib.sys common library used by the smart card reader driver is not removed during uninstall. This is because device drivers may still be installed in the system and they depend on smclib.sys to start and run. It is not removed during uninstall of the Microsoft Smart Card Base Components to avoid problems.

The smclib.sys file may be safely removed after all smart card reader device drivers have been removed.

The C Runtime and Microsoft Foundation Class files, msvcrt.dll and mfc42.dll, are not removed by the uninstall utility, since they are shared resources.

The install utility may replace your advpack.dll system file. The updated file is not removed by the uninstall utility.

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.

Please note that the NameNumericTail registry workaround detailed in the resource kit is not compatible with any Memphis upgrade scenario, and should not be used.

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 Setup

If Internet Explorer 4.0 appears to stop responding at the end of Setup, you need to restart your computer manually.

About Internet Explorer 4.0 Zones Security

New Security Settings Are Available

The new Internet Explorer 4.0 security options enable you to assign specific Web sites to various zones, depending on how much you trust the content of the specific Web site.

When you install Internet Explorer 4.0, four security zones are set up:

  • An Internet zone that by default contains all Internet sites
  •  A Local Intranet zone for computers connected to a local network
  •  A Trusted Sites zone, to which you can assign sites you trust
  •  A Restricted Sites zone, to which you can assign sites you don't trust

Internet Explorer 4.0 does not try to maintain any existing Internet Explorer 3.0 settings, because the security works differently in this new version. In addition to the new security zones, the meanings of the High, Medium, and Low security settings

have changed. After you install Internet Explorer 4.0, you should review the default security settings and adjust them to your needs as necessary.

You can view and change all the security settings by clicking the Internet icon in Control Panel, and then clicking the Security tab.

Remember, security on the Internet is as good as your settings. Internet Explorer 4.0 provides you with the information you need to make good security decisions, and more flexible tools to implement those decisions.

Setting Up the Internet Zone

By default, the Internet zone is set to the Medium security level. If you are concerned about possible security problems browsing the Internet, you might want to change the setting to High. If you raise the security setting, some pages will not be allowed to perform certain potentially hazardous operations.

If you are an expert user, you might want to choose Custom Settings so that you can control each individual security decision for the zone. To do this, from the Security tab, click Custom, and then click Settings.

Adding Sites to the Trusted and Restricted Zones

There are two zones available to which you can assign Web sites that you specifically trust more or less than the Internet or the local intranet. To add sites to these zones, first choose the zone, and then click Add Sites.

The Trusted Sites zone is assigned a Low security setting by default. If you assign a site to the Trusted Sites zone, the site will be allowed to perform more powerful operations. Also, Internet Explorer will ask you to make fewer security decisions. Add a site to this zone only if you trust all of its content never to do anything potentially harmful to your computer. For the Trusted Sites zone, we strongly recommend use of the HTTPS: protocol so that the site can be connected to securely.

The Restricted Sites zone is assigned a High security setting by default. If you assign a site to the Restricted Sites zone, the site will be allowed to perform only minimal, very safe operations. This zone is for the rare case of a site you don't trust.

Setting Up the Local Intranet Zone (for Network Administrators)

To be secure, it is imperative that the Local Intranet zone be set up in conjunction with the proxy server and firewall. All sites in the zone should be "inside the firewall," and proxy servers should be configured so that they do not allow an external DNS name to be resolved to this zone.

By default, the Local Intranet zone consists of local domain names and those set in proxy override of the Connections tab. The network administrator should confirm that these settings are indeed secure for the installation, or adjust the settings as needed to be secure. You can check that the Local Intranet zone is configured correctly by browsing to various Intranet and Internet pages and confirming that the correct zone is shown in the status bar.

After the Local Intranet zone is confirmed secure, consider changing the zone's security level to Low to enable a wider range of powerful operations to be performed. It is also possible to adjust individual security settings in the Custom Settings dialog box.

If there are parts of the Intranet that are less secure or otherwise not trustworthy, they can be excluded from this zone by assigning them to the Restricted Sites zone.

The Local Intranet zone is intended to be set up via the Internet Explorer Administration Kit, although the options on the Security tab in the Internet Properties dialog box can also be used.

Internet Explorer 4.0 Known Issues

Intermittent hangs loading large files over modems – This may be fixed by replacing \windows\system\mshtml.dll with the version located in \betaonly\ie40.

Microsoft Money: Online Banking Does Not Work

If you install Microsoft Money 97 on a computer running Internet Explorer 4.0, online transactions will not work. This is because Microsoft Money is using an older version of the file Schannel.dll. To work around this problem, open the following Web site:

  http://www.microsoft.com/ie/download

Then install the 128-bit extensions from the Web to enable secure transactions.

Microsoft Access: Database Replication Does Not Work

If you try to replicate an Access database, you will get the following error message: Microsoft Access cannot complete this operation because it can't find or initialize the dynamic-link library Msjtrclr".

Some Encryption Settings Do Not Work in Internet Properties

If you change the ssl or pct settings on the Advanced tab in the Security dialog box, the settings will not be changed in the registry. To work around this problem if you are an expert user, you can change these settings manually in the registry.

Cannot Import Messages from Outlook or Exchange

If you try to import messages from an Outlook or Exchange .pst file, you will get an error message.

You Must Restart for Some ActiveX Controls to Work

If an ActiveX control is installed to your \System directory, a message will appear asking you to restart your computer. After you restart your computer, the control will work properly.

Telcom Fax: Unable to Send Network Faxes

This product currently does not work with Internet Explorer 4.0.

Cannot Add New Instrument in MIDI Properties

If you open MIDI Properties from either the Multimedia dialog box in Control Panel or Media Player, you will not be able to add a new instrument. The Add New Instrument button is not available.

Cannot Turn Off Cookies

You can still specify whether you want to be warned before accepting a cookie. However, there is no setting for turning cookies off completely.

Cannot Print Using Some PCL Drivers

If your printer is using a PCL driver that relies on metafiles, you will not be able to print to it.

Shockwave: Some .dcr Files May Not Run

Certain Macromedia .dcr files may not display in Internet Explorer 4.0 if the file was previously downloaded to the local computer. Downloading the Shockwave Director Active X Control version 6.0 or later from www.macromedia.com may fix this problem.

File Upload Control Does Not Work Properly

The File Upload Control does not work in this release. It will be supported in the next release.

Outlook Express Connection May Be Dropped

When you are using Outlook Express news, it's possible for the server to drop its connection to Outlook Express. This often happens when the client has been sitting idle for a while and the server is trying to conserve resources, or because of network and modem problems. To reconnect, click the View menu, and then click Refresh.

Outlook Express Settings

In OE, if you go to Tools/Options/Security Tab and click on the Settings button you will not be able to exit the resulting dialog box except through Ctrl-Alt-Del, highlighting OE and choosing End Task.

Toolbar Buttons and Icons Might Not Display Properly

If Internet Explorer 4.0 is installed, toolbar buttons and icons for some applications may not display correctly.

Task Scheduler Known Issues

AM/PM Indicators Not Available in Some International Formats

If the AM/PM indicators do not appear in the dialog box where you specify the time you want a task to begin, you can use the 24-hour time format to enter the time. For example, if you want a task to start at 11:15 AM, specify the setting as 11:15. If you want the task to start at 11:15 PM, specify the setting as 23:15. In either case, the time will be displayed as 11:15, but the correct value will be used.

Some Scheduled Tasks Don't Run Properly on Windows NT

If you are running Internet Explorer 4.0 on Windows NT 4.0, and you schedule a task to run when your computers starts or when you log on, the task will not run. This will be fixed in a future release.

Microsoft Virtual Machine for Java

Memphis includes the latest Microsoft virtual machine for Java. This second-generation virtual machine includes the following features:

  • Modular design - the virtual machine can be invoked in the browser or on a standalone basis
  • Performance leadership - the fastest way to execute Java code
  • Compatibility - the most support for JDK 1.1 features of any browser
  • Windows integration - get the productivity benefits of the Java language while exploiting the full power of the Windows operating system.
  • Component support - automatic, bi-directional integration between ActiveX components and Java components
  • Application Foundation Classes - the richest set of foundation classes to help build modern applications more quickly with Java.
  • Capabilities-based security model - granular access outside the Java sandbox to build richer applications
  • Package manager - automatic installation and versioning of classes on the local machine

Developing Java applets/applications using the new Java Virtual Machine

The new Java virtual machine present in Memphis PP2 and used by IE4 uses a different system of organization for packaging classes. Earlier virtual machines would use Java classes packaged in an uncompressed zip archive. Tools and compilers such as Visual J++ 1.1 could also read this zip archive. Since the new virtual machine uses a package manager for organization of class files, this zip archive of classes is not available by default, and no zip files will be present for compilers and other tools to use.

For developers who require a zip archive for their tools to work, the tool clspack is provided.

clspack (available from \betaonly\msjava directory on the Memphis CD) allows you to take packages that are currently installed in the package manager, and write their contents into a ZIP file which tools can use.

Usage

Running clspack -auto will create a single CLASSES.ZIP in the location %WINDIR%\Java\Classes directory that contains all classes stored in the package manager. The Microsoft Java compiler looks in this location by default for classes, so there is no need to set the CLASSPATH environment variable.

For other compilers that do not check this location by default, the CLASSPATH environment variable should be set as follows:

set CLASSPATH=%WINDIR%\Java\Classes\Classes.zip

before running the compiler. For more information on classpath and other development issues, see the Microsoft web site at http://www.microsoft.com/java/. It’s a good idea to place this command in a batch file for easy use.

Security Model

The previous version of the Virtual Machine (shipping in Internet Explorer 3.02) allowed signed code to be treated as trusted. Essentially, classes were placed in a CAB file and signed. When downloaded on to the users machine, the user was presented with a certificate dialog specifying the publisher of the code and other information. If the user granted permission to the trusted code, the code was allowed access to system resources. The capabilities-based security model in IE4 extends this security model by providing a granular approach to allowing applets out of the "sandbox." The Java code may be signed with default capabilities of "High", "Medium" and "Low" safety settings.

The High safety setting is a restrictive set of capabilities that are the equivalent of "sandboxed" Java code. It consists of:


  1. Thread access in the current execution context.
  2. Create a lop-level popup Window with a warning banner.
  3. Access to Reflection API’s for classes from the same loader
  4. Read System Properties.
  5. Open Network Connections to the host machine.

The Medium safety setting consists of the following set of capabilities (in addition to the capabilities in the High setting):

  1. User Directed File I/O
  2. Scratch Space

The Low safety setting consists of all capabilities (in addition to the capabilities in the High and Medium settings):

  1. File I/O
  2. Execute other applications on the clients
  3. User Interface Dialogs
  4. Thread Group access in the current execution context
  5. Open Network Connections to machines other than the host.
  6. Load libraries on the client
  7. Make native method calls
  8. Determines if an applet can make native method calls
  9. Create a top-level popup window without a warning banner
  10. Exit the VM
  11. Registry operations
  12. Printing
  13. Create a ClassLoader
  14. Access to Reflection API's
  15. Read system properties
Signing

Tools for signing code will be available in the Internet Client SDK available for Internet Explorer 4 Beta 2. These tools will provide developers the capability to sign their Java code with the default settings.

Known Issues for the Microsoft Virtual Machine

This release of the VM strictly enforces the following requirement: for a class to access methods of a second class in another package, the second class must be declared public. Previous releases did not enforce this requirement. Hence some applets that worked before may display errors with the new virtual machine. It is advisable to make the packages conform to this Java requirement.

  • For ActiveX-Beans integration, certain functionality (such as persistence and OC96 windowless support) is not yet present. The ActiveX control hosting does not support all ambient properties. Code download will be provided in future betas.
  •  On Windows NT 4.0, the virtual machine install is currently only supported on the default drive. This will be corrected in the next release.
  •  Uninstall of the virtual machine is currently supported. Use Control Panel, add/remove software to uninstall VM.
  •  Raw Native Interface Enhancements: The Raw Native Interface (or RNI) has been extended as a result of feedback and performance enhancements. The enhancements made to RNI are in four primary areas:
  •  Additional API's to enable reflection from native code
  •  Changes to support future garbage collection performance enhancements
  •  RNIGetCompatibleVersion requirement for RNI DLLs
  •  RNI invocation APIs
Class libraries

A rich set of class libraries are included included:

  • Most new JDK 1.1 classes - java.net.* enhancements is integrated is this Beta.
  •  AWT: We have completely reimplemented AWT for Win32. During this process we have removed AWT's dependency on MFC, and worked to eliminate overhead, bugs, performance problems and rectified unusual design decisions. ActiveX controls can also now be hosted as Beans.
  •  Application Foundation Classes (AFC) contains
  •  UI: a rich suite of UI controls, written in Java. UI controls will run across virtual machines and across platforms.
  •  Fx: suite of classes for graphics and effects, written in Java. Fx classes will run across virtual machines and across platforms.
  •  Active Accessibility for Java: a compact suite of standard interfaces which give Java developers access to accessibility aids for the disabled (exposed through the five base UI classes and the IUIAccessible interface).
  •  CAB: As part of AFC, we have provided Java APIs for creating and extracting CABinet files on any virtual machine.
  •  JDBC: a set of classes that allows access to any ODBC data source. See the JDBC release notes for more information.
  •  DirectX 3 for Java contains Java classes for the following DirectX multimedia APIs:
  •  DirectDraw(r) - provides 2-D graphics services and bitmap composition.
  •  Direct3D(tm) Retained Mode and Immediate Mode - high and low-level 3D graphics APIs, providing comprehensive 3-D graphics services.
  •  DirectSound(r) - provides sound-mixing and playback services.
  •  DirectPlay(r) - provides multiplayer game connectivity over the Internet.
  •  DirectInput(tm) - provides services for joysticks and other input devices.
  •  Direct Animation: Direct Animation is a new Java API that enables different types of multimedia content to be tightly integrated and deployed, associating the media pieces with a timeline and user events. See the Direct Animation release notes for further information.
  •  Java internationalization support: All UI methods and paths are Unicode enabled. Due to size of the JDK1.1 Unicode code pages (over 4 megabytes), only the Windows local code pages data(classes) have been included for this beta release.
  •  Resource format: AFC includes a set of resource decoder classes, allowing users to load Win32 resources in the same way that images and/or sound files are packaged with apps and applets today. These resources are used to:
  •  Leverage existing Win32 resources in Java in a cross platform manner
  •  Allow easy, safe business application localization
  •  Offer a compact, fast way to pass information across the web.
  •  Support complements our support for JDK 1.1 resource bundles.
  •  Multilingual Input Method APIs: Java IME support has been provided for beta testing only. APIs and sample code have been included in the SDK to allow developers to
  •  Create level 3 pure Java IMEs with self defined UI
  •  Enable Java applet or application to access any system IMEs as stand alone input method on any systems which shares common IMM (i.e. using Japanese IME on Chinese Windows with Java application)

Application Foundation Classes (AFC)

Microsoft's Application Foundation Classes (AFC) are a comprehensive set of Java class libraries providing user interface controls and graphics and effects classes. AFC's UI controls give Java developers a rich set of UI elements from which they can quickly build compelling, flexible and powerful user interfaces for their applications, enhanced by the innovative graphics techniques exposed for the first time by the Fx graphics and effects classes.

Written in Java, AFC ensures that applications built using these classes can be written once to run on any of the popular platforms and browsers that support Java. The AFC UI controls are defaulted to the Windows UI, but are fully customizable to reflect the needs of application and applet designers. AFC supports Active Accessibility for Java, so any application developed using AFC is automatically accessibility-enabled. AFC comprises:

  • UI: a rich suite of UI controls, written in Java. UI controls will run across virtual machines and across platforms, and are automatically accessibility-enabled.
  • Fx: suite of classes for graphics and effects, written in Java. Fx classes will run across virtual machines and across platforms
Known Issues for AFC
  •  Performance: This release contains performance improvement for both AFC and our AWT implementation. However, performance in these areas is still some way short of the level that can be expected in our final release. In particular, we have introduced a new component model that gives us significantly better performance. Please see the accompanying 'AFC: Component and Event Model Update' white paper for implementation details.
  • Platforms: For this beta release, AFC's UI, Fx and CAB classes will only run on virtual machines that support JDK 1.1. However, for future beta releases, AFC will run on virtual machines supporting both JDK 1.0.2 and JDK 1.1. Please note: all virtual machines do not function identically, and while AFC currently runs on JDK 1.1-compatible platforms, we have not tested it on all virtual machines. Any problems you encounter when testing AFC on additional platforms are bugs that we will resolve as part of our testing process, and should be reported as bugs for us to address. If you are using AFC on platforms other than Internet Explorer or the Microsoft virtual machine, please see the Installation Requirements section above for installation details.
  • JDK 1.1 and 1.0.2 compatibility: This beta will only work with JDK 1.1; we will support JDK 1.0.2 in subsequent betas.
  • JDK 1.1 and 1.0.2 event models: This beta now supports both the JDK 1.1 and JDK 1.0.2 event models. Please see the accompanying 'AFC: Component and Event Model Update' white paper for implementation details.
  • Painting: AFC has some painting problems under JDK 1.1 on Solaris. It does not exhibit the same problems on JDK 1.1 under Win32.
  • Popups: Under JDK 1.1 on Win32 popups work; on JDK 1.1 on Solaris they do not. This affects menus and choices.

DirectX 3 for Java

DirectX 3 for Java contains Java classes for the following DirectX multimedia APIs:

  • DirectDraw(r) - provides 2-D graphics services and bitmap composition.
  • Direct3D(tm) Retained Mode and Immediate Mode - high and low-level 3D graphics APIs, providing comprehensive 3-D graphics services.
  • DirectSound(r) - provides sound mixing and playback services.
  • DirectPlay(r) - provides multiplayer game connectivity over the Internet.
  • DirectInput(tm) - provides services for joysticks and other input devices.

For further information about the DirectX 3 multimedia APIs, please see http://www.microsoft.com/directx.

No component of the beta DirectX3J class libraries is redistributable. The final release of the SDK will include a freely redistributable version of DirectX 3 for Java. The license accompanying the final SDK release needs to be accepted to get the right to redistribute parts of the SDK. Vendors can choose to refer their users to http://www.microsoft.com/java for the DirectX 2 Java class library.

Runtime Installation

For this beta release, you will need to install the full DirectX3a runtime, which is available from http://www.microsoft.com/directx. This version of the DirectX runtime contains elements of the Direct X suite of technologies that do not run on Windows NT (see Known Issues below for more details). If you intend running DirectX3 for Java on Windows NT, you should go to http://www.microsoft.com/msdownload for the Windows NT 4.0 Service Pack 3 (SP3), which contains DirectX 3a runtimes for both Windows 95 and Windows NT. You will need to install the DirectX 3a runtime to use DirectX3 for Java class libraries, view the samples, etc.

Known Issues

Windows NT: DirectX 3 for Java depends on the DirectX 3 runtime. Some elements of DirectX 3 (DirectSound) work on Windows NT in emulation only. Direct3D, which will also remain in emulation only until Windows NT v. 5.0, is now available for Windows NT is available with the Windows NT 4.0 Service Pack 3 (SP3), which can be found at http://www.microsoft.com/msdownload.

Samples: We have included samples for Direct3D, DirectDraw, DirectSound and DirectInput. DirectPlay samples will be available in subsequent betas.

APIs: We have implemented DirectX 3 for Java in a Java-centric fashion. Additional changes to the implementation will be made to ensure that the APIs are both cleaner and easier for Java developers to use in subsequent betas. The documentation included with this package and at the DirectX web site can help describe the current APIs.

Palettes: (Only relevant to 8-bit mode) - Palette implementation is still being worked on and will be improved in future versions.

DirectDraw: getClipList does not work in all cases and is currently under investigation.

Microsoft Outlook Express

You will need to reinstall Outlook Express from the \betaonly\imn directory on the Memphis CD.

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.

Outlook Express Known Issues

When receiving a message using a GeoCities mail account, you might be unable to view any of the original message, or you may see only the following information: Postage Paid by [graphic].

You will not be able to see embedded objects or images sent from people using Microsoft Outlook, Microsoft Exchange, or Windows Messaging. File attachments work fine, however.

If you use HTML in your signature, and you send the message before any included images have finished drawing, the text you add to the message may be lost.

Some mail clients send Cyrillic messages with tags indicating that they are in a western European character set. As a result, Outlook Express uses a western-European font to display the message, which then appears garbled. To work around this problem, click the View menu, click Language, and then choose a Russian character set, such as K0I8. The message should display properly using the Russian font.

Inbox rules are not available for IMAP accounts.

If you are using Outlook Express with a SUN Solstice, Netscape, or Innosoft IMAP server, it may cause your server to stop responding. Please contact the third-party provider for an update to the IMAP server software to correct this problem.

Outlook Express S/MIME does not verify the status of digital IDs before sending encrypted or signed messages. This means that a digital ID that is revoked, expired, not trusted or that has an incorrect e-mail address will be used without providing any warning.

In order to send signed messages and receive encrypted messages, you must have a digital ID. Currently, the only way to get a digital ID for use with Outlook Express is to use Internet Explorer 4.0 and go to the VeriSign Web site, http://digitalid.verisign.com.

Sending and receiving signed or encrypted mail to many mail programs that also support secure messaging (other than Outlook Express) does not work in this release. The interoperability issues have been identified and will be corrected in a future release.

While sending and retrieving messages, closing Outlook Express and restarting it will cause Outlook Express to crash. In Outlook Express News, if the option "Get 300 headers at a time" is turned on, the following commands: Get New Headers, Get New Messages, Get All Messages, and Get Marked Messages will retrieve only 300 (or the number that you specify) headers at a time. To prevent this, you should turn off this option.

To cancel a news message, you must be using the same message encoding options as was used for the original message. If no folders are displayed for your IMAP server or if you want to refresh the list of IMAP folders you need to download the folder list from the server. To do this, select the IMAP server. If you connect to the server by using a modem, click the Tools menu, and then select Offline > Dial. If you connect to the IMAP server by using a LAN, you can skip this step. After you have connected to the server, click the File menu, click Folders, and then click Refresh Folder List.

If you need to change any of the following settings for your IMAP account:

  • IMAP server name or port number
  • Account type (POP3 or IMAP)
  • Any logon information

it is recommended that you delete the IMAP account and create a new account with the updated settings.

Outlook Express is designed to work only with IMAP4 compliant servers. IMAP2bis servers are not supported in this release.

If you rename a news server account name and then attempt to perform some action on it, for example copying messages from the server, you may receive an error message. To work around this problem, close OE and restart after the renaming of a server.

If encrypting a message when there is not a certificate for one of the recipients, an error will display stating that there is not a certificate for that recipient as well as the sender.

Certificates are now handled on a per account basis. You must reselect which certs to use for each account. This can be done via the Accounts menu item. Select the account you wish to configure for security features and check the box to use a certificate when sending secure messages. You must also click the Certificate button to select which to use.

If you used Internet News for reading newsgroups, any messages in your "Posted Items" folder will be moved into the "Sent Items folder when you upgrade to Outlook Express.

Troubleshooting

If you run into a problem, try the troubleshooters in online Help or on the Microsoft Web site at http://www.microsoft.com/support/tshooters.htm. To start the online Help troubleshooters, carry out the following steps:

1. In Outlook Express, click the Help menu, and then click Help Topics.

  1. Double-click the "Troubleshooting" topic on the Contents tab.

Check your connection to your Internet service provider.

If you are unable to send or receive mail, check the following:

  • The TCP/IP protocol is installed on your computer.
  • All cables are properly connected to your computer, modem, or LAN.
  • You have a PPP or SLIP account with your Internet service provider.
  • Your Internet service provider or LAN server supports POP3 or IMAP and SMTP
  • Your modem communication parameters (baud rate and type of protocol) are set correctly.

Make sure that you use an account name and password for a news server only if it requires them. If you use an account name and password and they are not required, you will not be able to connect to the news server.

To access the Microsoft peer product support newsgroups, carry out the following steps:

1. Click the Tools menu, and then click Accounts.

  1. Click Add, and then click News on the drop-down menu.
  2. Follow the directions on your screen.
  3. When you are prompted for a server name, type msnews.microsoft.com

If your Internet service provider doesn’t find that name, you can type 131.107.3.27 instead.

You do not need to log on to this news server.

Support for Microsoft Outlook Express

For the latest information about Outlook Express as well as a list of Frequently Asked Questions, see our Web page at http://www.microsoft.com/ie/ie40/collab/imn. You may find that your questions can be answered here.

A newsgroup is dedicated to the discussion of Microsoft Outlook Express and provides peer support:

news://msnews.microsoft.com/microsoft.public.inetexplorer.ie4.OutlookExpress

To read it, follow the procedure outlined in the Troubleshooting section above.

This site is the best place to go if you are experiencing a problem, as someone else who experienced the same problem might already have posted the solution.

Web-Based Enterprise Management support.

The Memphis Beta contains the WBEM infrastructure and a number of data Providers (see the WBEM Development kit on http://wbem.freerange.com/wbempdk for more details). A data Provider that provides data from Talon is also provided as part of the WBEM components. However this Provider, while fully functional, will not provide data from Talon due to a problem with the operation of Talon on Memphis Beta 1.

NetMeeting

This release of Memphis contains the final release of Microsoft NetMeeting™ version 2.0. Microsoft NetMeeting 2.0 is a standards-based audio, video, and multipoint data conferencing product that supports application sharing and real-time voice and video communications over the Internet and corporate intranets. Features of NetMeeting 2.0 include multi-user application sharing, point-to-point video conferencing, point-to-point audio conferencing, whiteboard, file transfer, chat, and shared clipboard

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 2.0 does not work correctly.

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

My Documents Folder Enhancements

Memphis implements several improvements to the My Documents folder from Windows 95 applications. There is a shell extension DLL that will cause My Documents to have special behavior that will make it easier for users to take advantage of a common data storage area.

Installing Memphis will place a shortcut to the My Documents folder on the desktop, and change the behavior of the Common File Dialogs to default to this folder.

Notes:

Memphis Beta 1 does not automatically install the My Documents folder. To use this feature, you need to perform the following steps:


  1. Copy the file mydocs.dll from the \betaonly\mydocs to the \windows\system directory.
  2. From the Start/Run menu, type “regsvr32 mydocs.dll”. You should see a message that indicates that it has registered successfully.

My Documents Folder - Previous testers may have a “My Documents” folder on their desktop. The old “My Documents” folder should be renamed to “Obsolete Desktop My Documents Folder” during setup. Likewise, the “Public Documents” folder gets renamed to “Obsolete Public Documents Folder”. A new “My Documents” icon will be added to the desktop. This is not truly a folder, it’s just a shell extension shortcut to the root My Documents directory. All files from the “Obsolete” directories should be moved elsewhere (the new “My Documents” folder perhaps) and the directories should be deleted.


Winstone97 will not successfully complete with My Documents installed. The most common symptom is that Powerpoint will wait indefinitely trying to load a file.

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.
  • By 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.

Please note that for this release, if you have an IntelliPoint Wheel mouse, Memphis installation may change it to a Standard Serial or PS/2 mouse in Device Manager. This change is only to the description of the mouse in Device Manager, and should not have any effect on the mouse. You should still have full wheel functionality, in fact, with the Memphis mouse drivers, the wheel will work in more applications than the original IntelliPoint drivers. As such, please do not re-install the IntelliPoint software to get the "wheel" back.

Animation - This includes sliding menus and color highlights on menus and controls to track the mouse position. These settings will be able to be controlled using a future version of the TweakUI utility.

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).

Support Tools

Windows Tune Up Wizard

The Windows Tune Up Wizard is one of our many steps to make the PC self-maintainable. The Wizard schedules tune up jobs to be run automatically on a regular basis. You can launch the Wizard from the Start menu, off the Programs, Accessories, and System Tools.

Following is a list of known issues:

  1. Task Scheduler does not restart automatically when the computer is restarted. After Windows Tune Up sets up the default tasks, it activates the Task Scheduler and the SAGE icon will appear in the System Tray. But if you restart the computer, Task Scheduler will no longer be active (no SAGE icon in the System Tray). The workaround is to manually run the Task Schedule (Programs\Accessories\System Tools) before running Tune Up. You should select the Advanced menu in Task Scheduler and select “Start Using Task Scheduler.”
  2. Disk Cleanup defaults to delete no files from the hard drive. When Windows Tune Up schedules Cleanup to run, by default, no files will be deleted from the local hard drive. To activate Disk Cleanup, go to Start menu and select Run, type in “cleanmgr”.
  3. Scandisk is set up to run and show the summary for each drive scanned, by default. After Windows Tune Up is run, Scandisk will run as scheduled, but leave a summary dialog box on screen after each drive is scanned. To have Scandisk run and only prompt you when an error is found, change the Display Summary option. Open Scandisk (Start\Run . . .\SCANDSKW.EXE), hit the “Advanced. . .” button, and select the option “Only if errors found” under Display Summary. This will allow Scandisk to run without user intervention during the scheduled times, but will stay open and prompt you, if any errors are found.

Memphis HelpDesk

Launching Memphis HelpDesk is the first step in resolving a technical support issue. It links you to local and Internet resources, including Online Help, Troubleshooting Wizards, the Microsoft Knowledge Base, the MTS Windows Support Home Page, Windows Update Manager, and the Memphis Web-based Bug Reporting Tool. You can launch the Memphis HelpDesk from the Start menu.

Windows Update Manager

The Windows Update Manager 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 will be listed with descriptions to aid you in determining whether or not to install them. Any updates installed with this service can be uninstalled.

To run the Windows Update Manager, click its shortcut on the Start menu, in the Programs->Accessories->System Tools folder.

Note:  The Windows Update Manager is implemented as an ActiveX control, requiring the use of a browser, such as Internet Explorer version 3.0 or higher, that supports ActiveX controls.

Web-based Bug Submission

A Web-based bug reporting form is available for your use during the Memphis beta. This form includes an ActiveX control that scans your system to generate a profile of your hardware and then uploads this information, in addition to key system configuration files, when the bug report is submitted.

To submit a bug for Memphis, click the HelpDesk shortcut on the Start menu, and click the "Contact a Support Engineer" link.

To submit a bug for Memphis, click the shortcut on the Start menu, in the Programs->Accessories->System Tools folder.

Note:  The Web-based Bug Reporting Tool is implemented as an ActiveX control, requiring the use of a browser, such as Internet Explorer version 3.0 or higher, that supports ActiveX controls.

Dr. Watson

Dr. Watson collects detailed information about the state of your system at the time of a fault. Dr. Watson intercepts the software faults, identifying the software that faulted and offering a detailed description of the cause. When enabled, this tool logs this information to disk (*.wlg), and can be used to display it on screen (click Details on the dialog box that is displayed when a fault occurs). This information can be used to assist product support personnel in determining the cause of the fault.

The snapshot generated by Dr. Watson presents a comprehensive picture of the software environment in its Advanced view. If it is capable, Dr. Watson will diagnose the issue and offer a suggested course of action. Additional tabs list software loading in real-mode, software loading at startup, 16-bit modules, 32-bit modules, User and Kernel drivers, running tasks, as well as detail the system itself.

Note:  If you discover a reproducible error, please use Dr. Watson to record the state of your system. Comment the system snapshot with the steps to reproduce the error and save the log file with a descriptive name by choosing “Save As” from the File menu. Watson logs (*.wlg) are not uploaded with your bug report by default; manually attach the file to the report to aid our diagnosis of the issue.

Dr. Watson is not loaded by default. To launch Dr. Watson automatically, create a shortcut in your Startup group to \Windows\DrWatson.exe.

Registry Scan and Backup

Memphis automatically scans the system registry for corruption when booting, creating a backup of system files once daily. If registry corruption is detected, the utility will automatically restore a previous day’s backup (SCANREG /RESTORE). If no backup is available, the utility will attempt to repair it (SCANREG /FIX).

ScanRegW.exe is a protected-mode version of this utility that can both create a backup of the system files and scan the registry for corruption. If corruption is detected, it will refer to the real-mode utility, Scanreg.exe, for a resolution.

Memphis’ Setup invokes Scanreg.exe to verify the integrity of the existing registry before upgrading an installation. If registry corruption is detected it will attempt to fix it automatically. Failing that, it will halt the upgrade. If you experience this, please save the corrupt System.dat and User.dat to a different file extension (*.old) and attach them to a bug report detailing your experience. In this event, your only recourse is to either install Memphis to a clean directory from the command prompt, or to manually remove the corrupted files before launching setup.

The Registry Scan and Backup tool can be configured with the Scanreg.ini file. Configurable settings include enabling/disabling the utility, the number of backups maintained, the location of the backup directory, as well as settings to add files to the backup set.

Known Issues:

If your registry contains an entry referencing a file, such as a VxD, that no longer exists, it will not be ‘fixed’ by ScanReg. Such errors are not damaging; manually removing the entry will alleviate the symptoms.

The amount of conventional memory required by ScanReg is determined by the size of your registry. Upwards of 580k of free conventional memory may be required to complete the repair process. If you encounter an "out of memory" error message, optimize your memory by commenting out TSRs and loading device drivers into the upper memory area (UMA). For more information concerning the optimization of your real-mode configuration, see Microsoft Knowledgebase Article Q134399, “How to Increase Conventional Memory for MS-DOS-Based Programs” (http://www.microsoft.com/kb/articles/q134/3/99.htm)

Microsoft System Information Utility 4.1

Memphis now contains a centralized system information utility that gathers system configuration information for technical support. This tool is comprised of a collection of ActiveX controls, each responsible for collecting and displaying a certain category of system information in the right frame of MSInfo. A Support Engineer can guide the user experiencing an issue to MSInfo to facilitate the information gathering process. MSInfo includes viewers for the following file formats:

  • MSInfo files (*.nfo)

The information collected by MSInfo can be saved to file (*.nfo) and viewed using another machine.

  • Cabinet files (*.cab)

Cabinet files uploaded by the Web-based Bug Reporting tool can be opened to access the files therein.

  • HWInfo files (hwinfo.dat)

HWInfo files detail device configuration information, including resources.

  • Dr. Watson logs (*.wlg)

Dr. Watson is invoked by MSInfo to view Watson logs.

  • Text files (*.txt)

The hierarchy displayed in the left pane of the MSInfo container is dependent upon the controls that are installed on the system and registered with MSInfo. This hierarchy may change based on the means used to launch the utility; applications that call it may optimize the layout for support issues concerning it. Memphis support tools are made available from the Tools menu.

Known Issues:

This version of MSInfo does not open cabinet files (*.cab) created by the Memphis Bug Reporting Tool or the Registry Scan and Backup Utility.

System File Checker

System File Checker (SFC) verifies the integrity of your operating system files and offers to restore missing, corrupted, or replaced files. SFC can be configured to backup/not backup the existing file before restoring the original. A log file (SFCLog.txt) is generated by default. Additional options include the ability to customize search criteria based on folder and/or file extension, choose a different verification data file, create a new verification file, or restore the default verification data file (DEFAULT.SFC).

Known Issues:

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 Troubleshooter

System Troubleshooter (Tshoot.exe) automates the routine troubleshooting steps used by Microsoft Technical Support Engineers when diagnosing issues with the Windows configuration.

Modifying system configuration files has been an inherently dangerous task, as the only tools available were basic text editors such as Notepad and System Configuration Editor (SysEdit.exe). Tshoot permits the user to modify the system configuration with checkboxes, disabling/enabling items without a risk of spelling errors. This tool significantly reduces the reliance on a user's technical knowledge to troubleshoot issues with the system. Resolving issues with the Windows configuration has largely been reduced to a process of elimination using checkboxes.

Usage

System Troubleshooter can help you resolve issues that occur when you start Windows 9x normally. These issues include (but are not limited to):

  • Symptoms are not reproducible when launching in Safe mode
  • Error messages
  • Hanging
  • Loss of functionality

Note:  The goal of the Beta process is to eliminate errors that would lead someone to use this tool. Please submit a bug report detailing any issue you encounter testing Memphis, regardless of your ability to resolve it using System Troubleshooter.

Troubleshooting

To launch System Troubleshooter, click the Start button, choose Run, type "tshoot" (without quotation marks) in the Open box, and then click OK.

Before the troubleshooting session begins, backup your current system configuration files with Tshoot. To do so, click the Backup button located on the General tab. Establishing a baseline configuration ensures the modifications made during this session are reversible.

1. Disable Normal startup to create a clean software environment

The following steps create a clean environment for troubleshooting. This action determines if the issue can be isolated using Tshoot.

Note:  Disabling Normal startup with the current build of Tshoot renames the Config.sys file. Ensure your system does not require software loading in the Config.sys before choosing this option. Successfully launching Windows 9x in Safe mode indicates it is safe to disable Normal startup.

  1. Disable the Normal startup option, "Load all device drivers and software", click OK, and restart the computer as prompted.
  2. Determine if the symptoms are reproducible in this environment.

If the symptoms are alleviated, isolate the source of the issue using the selective startup options.

If the symptoms are reproducible with the Normal startup disabled, investigate the following:

  • Advanced troubleshooting options (detailed in the following section)
  • Protected-mode device driver configuration

For information detailing the troubleshooting steps, refer to the “Protected-Mode Device Drivers” section in article Q156126, “Troubleshooting Windows 95 Using Safe Mode.

  • A file is missing, corrupt, or has been replaced (refer to the System File Checker)
  • Registry corruption (refer to the Registry Scan and Backup Utility)
  • Virus
  • Faulty hardware/Hardware settings (CMOS)
  • Unsuccessful upgrade of previous Windows configuration
2. Isolate the issue using the Selective startup options

Enable the Normal startup option to access the Selective startup options. Using a process of elimination, strategically enable options until the symptoms are reproducible. Once the problem reappears, isolate the issue by narrowing the suspect options down to one source.

To determine the source of the problem:

  1. Identify issues with the real-mode configuration by disabling all but the Config.sys and Autoexec.bat files and restarting.
  2. Enable the System.ini and Win.ini and restart as prompted to determine if the problem lies in the Windows configuration files.
  3. Test the software loading at startup by enabling the Winstart.bat and Startup options and restarting the system.
3. Identify the problem using the appropriate tab(s)

The CONFIG.SYS and AUTOEXEC.BAT tabs intelligently identifies settings and minimizes the risks inherent in editing configuration files using the following conventions:

  • Disabled checkboxes indicate lines commented out by the tool
  • Settings used when the file’s Selective startup option is disabled are identified with a Windows logo
  • Previously commented lines are listed without a checkbox
  • Lines edited from within the tool are identified by a yellow pencil

The System.ini and Win.ini tabs follow the aforementioned conventions as well as identify sections with a yellow folder. Entire sections can by commented out by disabling the checkbox for the section.

The Startup Tab lists items loading at startup from the Startup group, Win.ini load= and run=, and the Registry.

Advanced Options

The Advanced Options tab may be used to further narrow the scope of an issue with Windows 95. The options invoke many of the diagnostic switches for Windows (equivalent to WIN.COM /D:<switch>). Options include the ability to disable 32-bit disk access and force the display to VGA. In addition, use the advanced options to limit the memory used by Windows (commonly used to identify issues with physical memory), enable the Startup menu, disable ScanDisk after bad shutdowns, and enable/disable SCSI double-buffering (this option is grayed out if the system requires Dblbuff.sys to access the drive).

Automatic Skip Driver Agent

Automatic Skip Driver Agent (ASD.exe) will identify potentially dangerous failures that are known to have hung Windows 95 systems and mark them to be bypassed on subsequent boots. ASD performs as follows:


  1. Identifies specific device(s) that fail to enumerate as expected
  2. Reports that it has detected a failure that may cause a system hang
  3. Offers to bypass this action on subsequent boots

If an error to this effect is ever displayed, the Hardware Troubleshooting Agent can be invoked by running ASD.EXE. All devices that have failed enumeration are listed by the HTA. The user can enable any device previously disabled by ASD and Windows will attempt to enumerate it on the next boot. Choosing Details identifies the failing device as well as suggests a course of action.

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. Access 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 that 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

Setup Safety Net Dialog

When installing Memphis over a network Memphis requires access to the install server during the second reboot of the setup process. Therefore, setup verifies that the files are accessible before continuing. If the files are not accessible the following dialog box is displayed:

  • Setup can not access the network to complete the installation. Do you want to:
  1. Reboot (Recommended if you skipped logging on.)
  2. Change your network settings before continuing?
  3. Continue without access to the setup files? (Not recommended)
  • This dialog is to help resolve the issue so setup can continue. Some of the reasons network access may not be available are:
  1. You didn’t log on, or you logged on using a user name that doesn’t have access to the necessary files.
  2. The server or network is down.
  3. The net card or net card driver is not working.
  4. The network settings are wrong.

The first item simply reboots. Trying this option first is a good idea. If given a chance to log on be sure to log on as user name that provides read access to the Memphis release server you installed from. If you were not given a chance to log on the net card or driver may not be working properly.

The second item displays the Network Control Panel where you can verify or change your network properties as necessary. Setup will force the system to reboot when you’re done.

The third item allows you to continue without network access. This is not recommended, since the only option from that point on is to skip the files the system needed to complete setup. If you do use this setting it is HIGHLY recommended you immediately reinstall since many of the files necessary will either be missing or out of date. To reinstall if these problems persist you can copy all the files on the Memphis release server to your local hard disk, then install from the local 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

Windows Modems

Many modems now split their functions between the modem hardware and a Windows 95 VXD driver. The generic name is "Windows Modem". These modems are usually bundled with the PC, rather than sold retail.

The more common type is "controller-less", with a hardware DSP. Examples: US Robotics WinModem, Lucent modems sold through HP, IBM, Compaq, etc, IBM MWAVE, etc. There are now some modems called "software modems", which implement the DSP in the main CPU (e.g. Pentium MMX) as well.

We expect that Windows 95 compatible VXD Windows Modem drivers should also work in Memphis, but problems have been found. As noted elsewhere, it would be prudent for these drivers to be unloaded during setup - don't run the modem. If possible, the modem driver files should be identified and backed up in case they are needed for reinstallation after the installation of Memphis.

Microsoft needs the help of beta users to identify which Windows modem drivers need reinstallation after Memphis upgrade. This would focus our efforts to get upgrade drivers from the modem vendors for inclusion in the final version of Memphis.

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 2

Support for previously supported cards

Many NDIS 2 drivers shipped in Win95 are not currently shipping in Memphis. If your card is one of the affected, the symptoms will be an inability to add ODI or NDIS 2 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 Win95 will also ship in Memphis, they will re-appear in a future Beta.

Possible workaround:

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 wehre your most recent updated drivers are. If the manufacturer still supports NDIS 2, you will be able to install support in this way.

NDIS 2 and ODI support will re-appear in future beta releases of Memphis.

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).

ATM with LANE Emulation Support

Memphis beta1 has support for LAN Emulation (LANE) over ATM (asynchronous transfer mode).

Supported ATM network card miniport drivers will be automatically added through Windows PnP. After the miniport driver software installation is complete, you will be prompted to select a Protocol. Select Microsoft, then select ATM Call Manager. Click Okay. Supported ATM adapters are Adaptec, Digital Equipment Corp., Madge, Fore, Olicom.

Unsupported ATM Network cards will be detected by PnP at system startup and a Start the Search dialog box will be displayed. Insert the manufacturer's software diskette in your diskette drive and select the Brand and Model. After the ATM adapter is installed, select the ATM Call Manager as above. It is necessary to add three components through the Networking applet of the Control Panel as follows:

  1. Go to Control Panel, Select Networking
  2. At Configuration, Select Add Protocol
  3. Select Microsoft ATM LAN Emulation 1.0 Client Miniport
  4. Select Microsoft ATM LAN Emulation 1.0 Client Protocol
  5. Select Microsoft ATM LAN Emulation 1.0 Client Protocol, Advanced and type in the ELAN Name if provided by your Network Administrator. If no entry is made, the LANE Client will join the default ELAN.
  6. Select Microsoft TCP/IP, IPX, or NetBEUI Protocols
  7. Reboot the system when requested

NOTE: Selection of the ATM ELAN is limited to either the default ELAN of the ATM ELAN Host Switch utilizing the Well Known Address or to a specific ELAN Name at this time. IP PING sizes above 1908 bytes are not supported at this time.

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 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 WINS 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. For example, Netbt tries to establish a session using the IP address that it gets from its favorite WINS first and if this 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 on 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 extend 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 include 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 might 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 Internet Engineering Task Force (IETF) is developing the RSVP specification. 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

FTP Software’s OnNet32 TCP/IP Stack

The only way that the OnNet32 IP Stack can be installed on Memphis is by upgrade from previous install or follow the instructions under the Winsock 2.0 section to return to Winsock 1.1 before installing OnNet32. When upgrading the system, it may hang on first boot. If this occurs, shutdown the machine and restart. The software will also ask you to “install protocol that matches your hardware” select “cancel” to continue.

When using the OnNet32’s IP Stack with Client for Microsoft Networks, there may be some difficulty in transferring files with other Windows 9x or NT machines.

Novell Release Notes

Client 32 and InterNetware Client

Note: Please update to Novell’s Beta Client32 2.20a later before upgrading to Memphis. Releases of Client32 before 2.20a will not install properly on Memphis.

If Client32 functionality is lost during the upgrade, the following steps MAY restore functionality:


  1. Ensure you have a locally accessible copy of the installation media for all installed clients.
  2. Write down your current network configuration, including client, protocol, and NIC settings.
  3. Switch the primary network logon to a setting that is neither the current setting nor Client32. If you are asked for client files, direct Memphis to the installation media.
  4. If step 3 works, you may be able to return the primary network logon to its original setting and still have Client32 functionality.
Novell 32-bit ODI NIC drivers

If you upgrade over a Novell provided 32-bit ODI driver and you receive the Hardware Troubleshooting Agent (asd.exe) for your network card every other boot, please switch to NDIS drivers. Microsoft is investigating this issue.

VLM Client

VLM Client Kit 1.21 not compatible with Memphis

Do not install VLM Client Kit 1.21 over Memphis, or install Memphis over Client Kit 1.21. The system will not boot to normal mode with Netware.drv 3.10.96.201 installed. VLM Client Kit 1.21 is available for download from Novell and is also the version of VLM shipped with NetWare 4.11 and IntraNetware.

Netware.drv version 3.03.94.280, included with the version of the VLM shell shipped with NetWare 4.10, is compatible with Memphis.

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 upgrading from Gold or OSR2 and setup is ran from a DOS prompt, 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.

Unable to map NT drive in GUI when the Banyan 16 bit client and Client for Microsoft Networks is loaded without Microsoft’s Client for NetWare Networks.

If the Banyan Vines 16 bit client and Client for Microsoft Networks is installed, a general network error occurs when trying to map a local drive to an NT server. The workaround is to install the Microsoft Client for NetWare in addition to the Banyan 16-bit client and the Client for Microsoft Networks then the mapping will be successful.

Uninstall fails when the Banyan 16bit RM client is installed

If you have the Banyan vines 16-bit client installed in Win95 and you have upgraded to Memphis you will not be able to Uninstall Memphis back to Win95. Currently there is no workaround.

Opening and closing Network control panel when Banyan Vines 16 bit client is installed

If you access the Network Control panel ANYTIME when you have the Banyan Vines 16 bit client installed you will be prompted to reboot your computer and the Vines drivers will need to be reinstalled. This will happen even if you access Network control panel and then select cancel. You can reinstall the drivers by rebooting the computer then logging into the Vines network, you will be prompted to install the drivers from the Vines server.

Windows does not display the correct properties for Banyan Vines mapped drives.

When you right click on a mapped Banyan Vines drive the properties such as drive size, capacity, and name will show up incorrectly. Currently there is no workaround.

Black screen upon Windows initialization with Banyan Vines 16 bit client.

If Banyan Vines 16 bit client is installed, Windows will hit a black screen upon initialization. If Microsoft’s client for NetWare is installed in conjunction with Banyan then the fault does not occur.

Extended characters with Banyan Vines 16 or 32 bit client

If you are using Banyan Vines in conjunction with Client for Microsoft Networks, and your computer name has an extended character in it then your computer name will not be recognized properly over an NT domain. The current workaround is to not use extended characters.

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

Artisoft LANtastic Release Notes

LANtastic 16-bit server does not function

Currently 16-bit versions of LANtastic’s Server (versions 5.x and 6.x) software do not function while Memphis is loaded. It is possible to boot the system to command prompt only in order to start the server software and access the system. Starting windows will stop the server service however and restarting in MS-DOS mode will not restore functionality. If operated from command prompt only, the server will not be able to function to full capacity. Support for real-mode share has been dropped and the server used this to provide greater functionality. The 16-bit LANtastic client software still functions under Memphis.

Installing Memphis disables LANtastic Internet Gateway Client

Installing Memphis on top of any previous version of Win95 running LANtastic7 will disable the LANtastic Internet Gateway Client.

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

Real-Mode LANtastic 6.x Server doesn't function under Memphis

The real-mode LANtastic 6.x Server requires that the DOS SHARE.EXE utility be installed before it will function as a server. The LANtastic 6.x real-mode client still functions in Memphis. It is just the server portion that is non-functional.  The Server software uses its own version of real-mode DOS sharing to get maximum functionality for Server services. Support for the DOS real-mode SHARE.EXE utility was dropped in OSR2 because sharing is accomplished entirely in protected mode and is not an option that can be added or removed via the SHARE.EXE utility. Users should contact LANtastic for a version of the LANtastic client/server that does not depend on the presence of real-mode DOS SHARE.EXE and utilizes the built-in file sharing support in Memphis.

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, & 3), 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 backups to local, removable, and network drives.

Backup Known Issues:

The tape formats have changed since earlier pre-beta releases.

You may not be able to restore or append to backups created in previous pre-beta releases of Memphis because the tape formats have changed to accommodate more features.

Seagate Backup v2.0 will not work with Backup installed.

Seagate Backup v2.0 and Memphis Backup will not coexist. You will have to remove one and reinstall the other if you have both installed.

Some tape devices such as parallel drives may not show up in the Device Manager.

To fix this, run C:\Program Files\Accessories\Backup\System\PNPWTape.EXE and reboot your computer. If the drive is installed correctly, it should be added to the Device Manager after rebooting.

Can not emergency restore backups made with Windows 95 Backup.

Any backups made with the Windows 95 Backup applet can only be restored in Windows.

Can not emergency restore backups made to non-tape media.

Any backups made to removable media or to a hard drive can not be restored with real-mode emergency restore.

Can not restore multiple tape backups made with Windows 95 Backup.

Currently only one tape Windows 95 backups can be fully restored. Only the first tape of multiple tape backups made in with Windows 95 will be restored.

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.

Disk Defragmenter Optimization Wizard

Disk Defragmenter has been enhanced to make your programs start faster. The new Disk Defragmenter Optimization wizard allows you to pick the programs you use most often and steps you through creating a program log. Disk Defragmenter uses the log to arrange program files in the order they are accessed when the program starts. This allows the program to start more quickly.

To run Disk Defragmenter Optimization Wizard:

  1. Click Start, point to Programs, Accessories, System Tools, and then click Disk Defragmenter. Note: If the Disk Defragmenter Select Drive dialog appears, click "Settings" and then click "Create Program Log".
  2. On the Disk Defragmenter Optimization Wizard window, click "Create a log now to optimize my disk(s)" and click Next.
  3. Follow the instructions to complete the wizard.
Answers to Commonly Asked Questions about Disk Defragmenter Optimization Wizard

Q: Some of my programs do not appear in the list of programs provided by the Disk Defragmenter Optimization Wizard. Why?

A: The programs shown in the list are programs that have a link in the Start menu or on the Desktop and a program file size of 800 KB or larger. You may add other programs by clicking the "Other" button in the wizard.

Q: When I start Defrag the Disk Defragmenter Optimization Wizard does not appear. How do I start the wizard?

A: On the Defrag Select Drive dialog, click "Settings" and then click "Create Program Log".

Q: Do I have to run the Disk Defragmenter Optimization Wizard and create a program log each time I want to defragment my hard disk?

A: No, once you have completed the Disk Defragmenter Optimization Wizard the log information is stored on the hard disk and is used each time you defragment the drive. Typically you only need to run the wizard again if you want to add or remove a program or if you have upgraded one of your programs.

Q: How do I add a new program to the program log or remove one of the programs that I logged previously?

A: To add or remove a program, run the Disk Defragmenter Optimization Wizard and create an entirely new log by selecting all of the programs you want to optimize.

Q: Defrag keeps restarting and has been running for a long time without making much progress. Why is it restarting?

A: Defrag must keep track of where files are stored and where free space is located; therefore, Defrag must reread the disk information anytime a program writes to the hard disk. If Defrag is restarting often you may be running another program that is making frequent writes to the disk. Try quitting other programs while Defrag is running. If you are running the Microsoft Office Find Fast utility, you may need to pause Find Fast while Defrag runs. To pause Find Fast, click Start, point to Settings, and click Control Panel. Double-click the Find Fast icon and then click "Pause Indexing" in the Find Fast Index menu.

Task Scheduler

Microsoft Task Scheduler helps you automate routine tasks for your computer.

The new Task Scheduler replaces System Agent on Windows 95 computers, which was included in Microsoft Plus!, and the Windows NT AT service. If you have Microsoft Plus! installed, your existing tasks will be upgraded to the new format. Existing AT tasks on Windows NT will also be upgraded.

If you have scheduled tasks to run:

1. Open the Scheduled Tasks folder.

  1. Click the Add Scheduled Task Icon.

Remotely Managing Tasks on Windows NT from a Windows 95 Computer:

If you want to use Task Scheduler to manage scheduled tasks on Windows NT from a Windows 95 client computer, you must install some additional networking components on your Windows 95 computer. These components allow Windows 95-to-Windows NT registry access. For more information, see the section on networking and the registry in the Windows 95 setup documentation.

Executing Tasks When the Computer Is Idle

If you used a computer running Windows 95 to schedule a task, and you set the start time to run when the computer has been idle for a specified period, computers running Windows NT ignore the setting. However, the setting is preserved if the task is again run on a computer running Windows 95. This will be fixed in a future release.

Differences Between Windows 95 and Windows NT

Because these operating systems are different, you will see the following differences in functionality:

Windows 95 supports:

  • Power management

Windows NT supports:

  • Task security via the NTFS file system

Some Scheduled Tasks Don't Run Properly on Windows NT

If you are running Internet Explorer 4.0 on Windows NT 4.0, and you schedule a task to run when your computers starts or when you log on, the task will not run. This will be fixed in a future release.

AM/PM Indicators Not Available in Some International Formats

If the AM/PM indicators do not appear in the dialog box where you specify the time you want a task to begin, you can use the 24-hour time format to enter the time. For example, if you want a task to start at 11:15 AM, specify the setting as 11:15. If you want the task to start at 11:15 PM, specify the setting as 23:15. In either case, the time will be displayed as 11:15, but the correct value will be used.

More Information

The Task Scheduler Help files are integrated with the system Help files. If you want to display only Task Scheduler Help, carry out the following steps:

1. On the Start menu, click Run.

  1. Type the path to the Task Scheduler Help file, Mstask.hlp. For example, you might type C:\Windows\Help\Mstask.hlp

If you don't know the path to the Mstask.hlp file, you can use the Find command on the Start menu to locate it.

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 of your favorite Calc bugs, and let us know if you find any new ones or if any old ones still exist.

Using -1 in non-decimal modes does not work

As a shortcut for entering large numbers in non-decimal modes you can enter an equivalent negative number. For example, in hex mode entering -2 will result in FFFFFFFE being displayed. This shortcut does not work with -1.

WordPad

The main new features since Win95 are support for Unicode text files, Word97 files, and richedit2.

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

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.

  1. Double click on the “Add / Remove Programs” icon.
  2. Click on the “Windows Setup” tab, and install all the options concerning the “accessories”, “communications”, “disk tools”, and “Microsoft Fax” components.
  3. Click “OK” to any message boxes that appear.
  4. When the “Inbox Setup Wizard” dialog asks, “Have you used Windows Messaging before?” click on “NO” and then “Next”.
  5. When asked, “Select the information service(s) that you want to use with Windows Messaging” – make sure that the Microsoft Fax option is checked.
  6. Next, at the prompt for “Location Information” enter your telephone area code and optionally, fill in the other fields. Click “Close” when done.
  7. The “Dialing Properties” dialog appears with a “My Location” tab. Fill in the appropriate fields then click “OK”.
  8. 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.
  9. 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”.
  10. Verify that modem has been correctly detected. Click “Next”, then “Finish”
  11. The “Inbox Setup Wizard” appears without the detected modem in the list. Click “Next”.
  12. 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”.
  13. 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”.
  14. An error message box may appear describing an error in MLSET32 (i.e.: 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.
  15. At this step, the Microsoft Fax feature is installed. To finish, right-click (right mouse button) on the Inbox icon located on the desktop.
  16. Click on Microsoft Fax in the “Services” box.
  17. Click on “Properties” button.
  18. Click on the “Modem” tab
  19. Click on “Set as Active Fax Modem”
  20. Click on “OK”
  21. Click on “OK”

Microsoft Fax should now be operational now.

NB: Another method of getting Microsoft Fax operational, is to do a hardware detection on modem first (via control panel / hardware detect), reboot, and then add on Microsoft Fax (via control panel / “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

Broadcast Architecture Components

This Beta release of Memphis includes components which enables you to

  • Download TV listings from the web or over-the-air
  • Watch TV from analog (over-the-air or cable) television networks
  • Receive broadcast web pages over multicast-enabled IP networks (which includes some cable television and satellite television networks)

Future releases will enable

  • Watching TV on your computer from satellite digital television networks, with an all-digital path, at resolutions unobtainable with current television receivers.
  • Receiving gigabytes of information per day along with digital television networks, so popular content will be instantly available on your computer, without direct connections to the Internet.
  • Reception and display of enhanced television shows -- shows that combine broadcast video with interactivity provided by your computer.

TV Viewer Application

Memphis includes a TV Viewer application (installable as an optional component) that works in conjunction with video capture cards/drivers that are compatible with DirectShow 2.0 and WDM. With TV Viewer, program listings can be viewed and searched through an Electronic Program Guide. With appropriate hardware, you can select and tune among hundreds of analog or digital (satellite) television programs, and navigate to web channels and other information broadcast through these networks. Check the broadcast architecture portion of the Windows Beta web site (http://winbeta.microsoft.com/bpc) for more information on supported hardware.

If your computer doesn't have broadcast reception hardware

You'll still be able to download program listings for your TV viewing area (cable or broadcast) from the web, and use the Electronic Program Guide feature. You can even set reminders to watch your favorite shows!

Notes for the TV Viewing application

  •  Only hardware for which WDM Video Capture drivers are available will work with the television viewing application.
  • In addition to the keyboard equivalents of remote control keys (see discussion below on remote controls), function key F1 will access help, F6 toggles full screen/windowed viewing, F10 toggles the channel bar.
  • Program guide information for your zipcode area is available through channel "TV C" (channel 1).
  • When using the TV Viewer application to view web pages containing edit fields expecting numeric input (for example, the zipcode information for electronic program guide data), you must use the number keys on the keypad to enter the numeric information. Otherwise, the TV Viewing application will interpret the number key entries as channel numbers.
  • Channel 720 in the TV Viewer is not yet functional

Remote Controls

The TV Viewer application is designed to work with remote controls available (or to-be-available) from your computer manufacturer. For this beta release of the Memphis software, the following may be used with the TV Viewer application:

1. Gateway Destination Remote control

When you install Memphis and BPC software, the registry settings in \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TV Services\Explorer\RemoteKeys are already installed. You can start using the Gateway Destination remote control immediately. The Recall button on the Gateway remote control has no function with the TV Viewer application.

2. Logitech (IBM) Remote control

Please visit the broadcast architecture web site to obtain a file that enables the use of this remote control.

Using other remote controls with Beta1

The use of arbitrary HID devices to control the TV Viewer application will be available in a later beta release. 

The following keystrokes are expected (via the default values in the registry) to produce the associated actions: (Win = Windows Key)

Keystroke Action
Win Bring up Start Menu
Win+Ctrl+Shift+z Bring up Program Guide
F10 Bring up Menu
Win+Ctrl+z Bring up TV Viewer if not yet started, otherwise toggle between desktop and full screen
Win+Ctrl+v Volume Up (on Master Mixer)
Win+Shift+v Volume Down (on Master Mixer)
Win+v Toggle Mute (on Master Mixer)
Win+Ctrl+Alt+z Channel Up
Win+Ctrl+Alt+Shift+z Channel Down
Win+Ctrl+Alt+Shift+f Arrow Left (some apps may interpret as REWIND)
Win+Ctrl+Alt+Shift+p Arrow Up (some apps may interpret as PLAY)
Win+Ctrl+Alt+f Arrow Right (some apps may interpret as FORWARD)
Win+Ctrl+Alt+Shift+g Recall (some apps may interpret as EJECT)
Win+Ctrl+Alt+p Arrow Down (some apps may interpret as STOP)
Win+Ctrl+Alt+g PAUSE
0-9 0-9
Enter Enter


To remap any of the keystrokes (i.e. because your remote control won't map to these keystrokes), you can change registry values as follows:

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TV Services\Explorer\RemoteKeys has the following values you can change: CHANNELDOWN, CHANNELUP, DOWN, LEFT, MENU, RECALL, RIGHT, UP.

Do not modify ctrlkeys.

For example:

CHANNELDOWN = 5a 80 80 80 80 00 00 00 00

In this example, 5a = "z". The next 4 bytes represent Win, Ctrl, Menu, Shift, where 80 indicates pressed and 00 indicates not pressed. So CHANNELDOWN = Win+Ctrl+Alt+Shift+z.

Note that MENU = 5a 80 00 80 00 00 00 00 00, which indicates Win+Alt+z. F10 will also work.

  1. \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TV Services\Explorer\RemoteKeys\WakeupKeys has the following values you can change: GUIDE, MUTE, TV, VolumeUp, VolumeDown.

For example:

TV = 5a 10 10 00

The 5a = z. The next 4 nibbles represent Ctrl,Shift,Win,Alt, where a nibble of 1 indicates pressed and 0 indicates not pressed. This means TV = Win+Ctrl+z.

  1. \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TV Services\Explorer\RemoteKeys\CommandLines has no values you can change. Note, however, that Guide and TV strings must contain the correct path to where tvx.exe (TV Viewer) is run.

The Microsoft Network (MSN)

Memphis allows the user to install the latest beta version of MSN, version 2.5. Note that this version of the Microsoft Network is also a beta; thus there are some interaction problems running MSN 2.5 beta 2 on Memphis and on the beta version of Internet Explorer 4.0 that ships with Memphis.

The previously shipping version of MSN on Windows 95 (msn13.exe) is available on the Memphis CD if the user wishes to install that version instead.

The most recently shipped version of the Microsoft Network, MSN 2.0, is not supported on Memphis.

Known Incompatibilities with MSN 1.3

Undeliverable Mail – You may not be able to receive or send mail using the Exchange mail client after upgrading to Memphis. This appears to be a compatibility problem when you upgrade to Memphis/Windows Messaging. Reinstalling MSN 1.3 from the Memphis CD (\Memphis\OLS\MSN\MSNSetup\Compnts\msn13.exe) will re-enable MSN 1.3 mail.

Known Memphis Incompatibilities with MSN 2.0

Memphis does not support MSN 2.0.

Known Memphis Incompatibilities with MSN 2.5 beta 2

Undeliverable Mail – You may not be able to receive or send mail using the Exchange mail client after upgrading to Memphis. You will however be able to access your new Internet Mail account (see “Outlook Express Mail & News using MSN 2.5” section below). Additionally, running the MSN13.EXE file from the Memphis CD (\Memphis\OLS\MSN\MSNSetup\Compnts\msn13.exe)will re-enable you MSN Classic e-mail account on your machine. Please also note that this will not affect MSN 2.5 functionality.

Known Internet Explorer 4.0 incompatibilities with MSN 2.5 beta 2

As both IE 4.0 and MSN 2.5 beta 2 are in Beta testing there is some interaction problems between the two products. Specifically,

  • Multiple Log-in screens once you’ve connected– You may see multiple login screens once you’ve connected to MSN; approximately one per page frame. If you click the “Connect” button every time you see this screen, you will eventually see the page you’re going to.
  • VB Script Errors --You may see VB script Error messages particularly in the Find and Member Services areas of MSN. Our content is in the process of being upgraded to Internet Explorer 4.0 standards.
  • General Protection Fault (GPF) Errors—You may encounter a GPF on the Find site. If you close the Program Viewer while in the middle of a navigation to another Web site, this can cause a General Protection Fault error in the Program Viewer.
  • Display differences between Internet Explorer 3.0 and Internet Explorer 4.0- You may also notice that some of the pages you view on MSN will look or behave differently with IE 4.0.

Outlook Express Mail & News using MSN 2.5 beta 2

As part of the MSN Beta Setup program, MSN will install and configure Microsoft Outlook Express for IE 4.0. Your e-mail address when using these programs will be:

       Your_MSN_Login_ID@email.msn.com

So, if your MSN Login ID is Bob, then your new Internet mail account address will be Bob@email.msn.com.

This will be a separate Internet Mail account, which will not affect your Original (MSN Classic), mail account (Your_MSN_Login_ID@msn.com).

Messages sent to your Original (MSN Classic) Mail account will have to be retrieved in the same way as you do today (with Microsoft Exchange/Windows Messaging or Microsoft Outlook).

In order to receive messages via the Microsoft Outlook Express Mail, they’ll have to be explicitly addressed to your new Internet Mail account: Your_MSN_Login_ID@email.msn.com (the full address).

During this Beta Phase, you should think of these e-mail addresses as completely separate mail accounts. In fact, that's exactly what they are.

Once the MSN Beta Phase is complete, we'll provide a mechanism for you to combine these two accounts into one, so you won't have to check for messages on two separate accounts anymore. In the meantime, however, this will be necessary and we'll provide you with means (a button on the Communicate Home Page and a link on the Beta FAQ) to switch back and forth between these two mail accounts.

You'll find lots of good information on the MSN Beta Internet Mail FAQ, which is available from:

      http://msnbeta.msn.com/limbeta/faq/mail/

These pages are also available from the Communicate Site "Frequently Asked Questions" link (under "Setting up E-mail").

Online Services

America Online (AOL)

In order to setup America Online in this Beta release you will need to perform the following steps:

  1. Copy AOL30US.exe (and/or AOL30UK.exe or AOL30CA.exe) from the CD "\Memphis\OLS\AOL" directory to the "\Program Files\Online Services\AOL" directory on your local hard drive.
  2. Open the "Online Services" folder on the desktop and click the "AOL" shortcut to launch AOLsetup.exe, or open the Start Menu and choose "\Programs\Online Services\AOL". You can also launch AOLsetup.exe directly via Explorer from the "\Program Files\Online Services\AOL" directory.

Known issues:

  1. AOL Setup doesn't find some installed modems and reports TCP/IP as the only identifiable communication device.
  2. AOL Setup as TCP/IP fails to find DNS due to failure to setup a proxy server or other valid Internet connection.

Workaround:

Choose No to bypass the recommended TCP/IP LAN setup, manually select a modem from the list, and complete AOL Setup using settings for a dial-up connection.

AT&T WorldNet Service

Known issues:

1.   AT&T Setup doesn't reset the "Connect to the Internet using a modem" property if a LAN or proxy server were previously selected.

  1.   AT&T Setup automatically configures mail client for receiving email successfully, but not for sending email.

CompuServe

In order to setup CompuServe in this Beta release you will need to perform the following steps:

  1. Copy CSSETUP.exe from the CD "\betaonly\cs30" directory to the "\Program Files\Online Services\CompuServe" directory on your local hard drive, and replace the existing file.
  2. Open the "Online Services" folder on the desktop and click the "CompuServe" shortcut to launch CSSETUP.exe, or open the Start Menu and choose "\Programs\Online Services\CompuServe". You can also launch CSSETUP.exe directly via Explorer from the "\Program Files\Online Services\CompuServe" directory

OR

1.   When prompted by the old CSSETUP to find CS3Kit.exe, browse to the "\Memphis\OLS\CIS" directory on the CD.

Known issues:

  1. The following error message pops up when initializing the first page for CompuServe.

"CompuServe - HTTP error
 Error: 400 Bad Request
 Server is unable to make sense of the request."

Workaround:

Since this is not the main browser window, user can simply minimize or close this window, click on <Internet> <Enter the Internet> , and successfully connect to "http://member.compuserve.com" and other www pages besides "http://new.compuserve.com".

MSN

Please see the section in this document titled The Microsoft Network (MSN).

NOTE: If you are an existing MSN 1.3 user, you will need to run msn13.exe found on the CD, to be able to successfully send and receive mail via Windows Messaging with your old <username>@msn.com. This will not be necessary if you choose to upgrade to MSN 2.5 Metro and send and receive mail with the new Outlook Express mail client at <newaddress>@email.msn.com. (Details can be found in the MSN section of this document).

Prodigy

This is a new service for Windows.

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.

Disk Defragmenter Optimization Wizard

This wizard enables your programs to run faster.

To run Disk Defragmenter Optimization Wizard:

1. Click here: file:defrag.exe

  -- OR --

Click Start, point to Programs, Accessories, System Tools,and then click on Disk Defragmenter. If the Disk Defragmenter Select Drive dialog appears, click "Settings" and then click "Create Program Log".

  1. On the Disk Defragmenter Optimization Wizard window, click "Create a log now to optimize my disk(s)" and click Next.
  2. Follow the instructions to complete the wizard.

How it works:

Disk Defragmenter Optimization Wizard lets you pick the programs you use most often. It then runs each program and monitors disk access as the program starts. This information is stored in a program log file. After the programs have been logged, Disk Defragmenter runs and arranges the program files in the order they are accessed when the program starts. Arranging the files in this manner reduces the number of seeks that the hard drive

performs when the program starts. This allows the programto start more quickly.

Q&A:

Q: Some of my programs do not appear in the list of programs provided by the Disk Defragmenter Optimization Wizard. Why?

A: The programs shown in the list are programs that have a link in the Start menu or on the Desktop and a program file size of 800 KB or larger. You may add other programs by clicking on the "Other" button in the wizard.

Q: When I start Defrag I do not get the Defrag Optimization Wizard. How do I start the wizard?

A: On the Defrag Select Drive dialog, click "Settings" and then click "Create Program Log".

Q: Do I have to run the Disk Defragmenter Optimization Wizard and create a program log each time I want to defragment my hard disk?

A: No, once you have completed the Disk Defragmenter

Optimization Wizard the log information is stored on the

hard disk and is used each time you defragment the disk.

Typically you only need to run the wizard again if you want to add or remove a program or if you have upgraded one of your programs.

Q: How do I add a new program to the program log or remove one of the programs that I logged previously?

A: To add or remove a program run the Disk Defragmenter

Optimization Wizard and create an entirely new log by

selecting all of the programs you want to optimize.

Q: Defrag keeps restarting and has been running for a long time without making much progress. Why is it restarting?

A: Defrag needs to keep track of where files are stored and where the free space is located. Each time a program writes to the hard disk Defrag must restart. If Defrag is restarting often you may be running another program that is making frequent writes to the disk. Try quitting other programs while Defrag is running. If you are running the Microsoft Office FindFast utility, you may need to pause FindFast while Defrag runs. To pause FindFast, click Start, point to Settings, and click Control Panel. Double-click on the Find Fast icon and then click "Pause Indexing" in the Find Fast Index menu.

Invoking Startup Menu with F8 Key

The "Starting Windows" message and the two-second boot delay (provided in Windows 95 for invoking the Startup menu with the F8 key) have been removed to reduce Memphis' boot time. As a result, using the F8 key to invoke the Startup menu may be difficult. The Startup menu can now invoked by depressing the CTRL key throughout the boot process. The CTRL key will not overload the keyboard's buffer, so it can be held down for the duration of the boot. If holding down the CTRL key during startup invokes anything but the Memphis Startup menu, please submit a report detailing your experience.

TweakUI

A test version of TweakUI for Memphis is located in the \betaonly\tweakui directory. You can control issues such as menu and window animation with this version. Right Click on the INF file and select Install to install this version.

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 applications 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.

DirectShow

DirectShow 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. DirectShow’s playback capability makes use of video and audio hardware cards that support the Microsoft DirectX ™ set of API’s. DirectShow 2.0 also plays movie files in .avi or Apple® QuickTime® .mov format. Please test DirectShow 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.

You can set the default behavior that Scandisk uses to respond to specific error conditions by editing the SCANDISK.INI file in the \windows\command directory.

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.

Platform SDK

The Microsoft Platform Software Development Kit (SDK) is the successor of the Win32 and BackOffice SDKs and provides a single, integrated SDK that developers can use to obtain documentation, samples, and a common build environment for Microsoft platforms. The web-based version at http://www.microsoft.com/msdn/sdk provides the most current documentation drops, an up-to-date build environment, and the most recent versions of Platform SDK component technologies. As it becomes available, developer information on new technologies shipping in Memphis can be found on the Platform SDK web site.

Known Third-Party Application Issues

The following applications may not install or function properly with this beta version of Memphis. Please promptly submit bug reports via the on-line bug reporting tool at http://winbeta.microsoft.com/memphis or MSREPORT if you discover any additional application incompatibilities introduced by the Memphis Beta.

Additionally, because we are interested in knowing about the performance of all applications, not just those which have resulted in problems, please take a moment to complete the Applications Compatibility Survey, located at the above web site, for each application you are running on Memphis.  Thank you.

General Application Notes

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.

DOS based applications & PnP Sound Cards

Use of DOS based applications in combination with PnP sound cards may result in application malfunction. To correct this problem, the user will need to rerun the sound setup utility in order for the sound to properly work. Applications known to exhibit this type of problem include:

  • Aces of the Deep ver 1.0
  • Spell-It

There is a problem with old DOS based applications and PnP sound cards where the user will need to rerun the sound setup utility to in order for the sound to properly work. Reason...When the user upgrades and Memphis is detecting the sound card it often changes the address/irq/interupts etc. of the

sound card so when the game attempts to access the old sound card values it can no longer find them. We need to have some rel-notes informing the user that they may need to reconfigure their games for the sound to play correctly.

Internet Explorer 3.02 and earlier

Please do not install any application that installs Internet Explorer 3.02 or earlier versions. The active desktop in Memphis will be disabled if versions older than IE 4.0 are installed.

Multi Monitor

DOS and Windows applications were not developed with Multi Monitor in mind. As a result, some applications may display some abnormal behavior while operating with more than one monitor. Adobe Type Manager (ATM) 2.0 and 3.0 are know to have Multi Monitor incompatibility issues.

Network Games from 3D Realms

Duke Nukem 3D, Shadow Warrior and other games from 3D Realms may not work on a network. To work around this situation, remove the IPX protocol form your network properties and rename nwlink.vxd in your windows\system directory. This will be fixed in a future version of the operating system.

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.

SHARE.EXE

Memphis no longer supports real-mode MD-DOS Share. However, some applications check for the existence of a file named share.exe. To work around this issue, create a file named share.exe in the \windows\command directory. The following applications require this work around:

Do It Yourself Lawyer by Expert Software

Resume Write by Expert Software

Great Gourmet by Expert Software

WINSOCK

The following applications will not run after uninstalling Memphis:

  • Internet Explorer 3.0
  • Eudora
  • Netscape
  • CoolTalk

To re-enable functionality, reinstall the application. This is a winsock.dll issue and will be fixed in a future version of the operating system.

Microsoft Handheld PC Explorer

There is a known problem when using the H/PC Explorer with Memphis, which will be fixed in a future release. Follow these steps to restore functionality:

  1. Copy DIRECTCC.EXE from \BETAONLY\HPC into the \WINDOWS directory.
  2. Copy RASAPI32.DLL and RNASERV.DLL from \BETAONLY\HPC into the \WINDOWS\SYSTEM directory.
  3. Reboot the system.

Specific Application Issues

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  

This application fails to start after installation. The vendor is working on a resolution.

Ascend 97 Franklin Day Planner

To allow this application to properly install, rename MFC42.dll in the system directory. Ascend 97 will now use its own MFC42.DLL and complete the installation process.

Chessmaster 4000

In order to run the Book Editor on Chessmaster 4000 without experiencing video problems while dragging a window, complete the following steps:

  • Go to Start, settings, control panel
  • Double click on Display and select the Plus! tab
  • Uncheck the “Show window contents while dragging” option, then click Apply

Cheyenne Backup 2.0

This application does not correctly complete the backup operation. Please contact the vendor for their Service Pack to correct this problem.

Doom 95

This game is known to malfunction with the S3 968 video card.

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.

Longbow AH-64D

Using the MS Sidewinder Pro and switching resolution from 640x480 to 320x240 will cause the joystick to stop responding. Hitting one of the arrow keys will restore joystick input. A patch to correct this problem exists at http://www.ea.com/janes/news.htm

Macromedia Director 4.04

This application will not start on a system with more the 2GB of free drive space. The work around is to run this program on a hard drive with less than 2 GB of free disk space.

MagnaRAM 97 version 3.0 by Quarterdeck

If you are running MagnaRAM 97 version 3.0, add this line to the [386Enh] section of the SYSTEM.INI file in your Windows directory before upgrading.

ConservativeSwapFileUsage=1

This will be fixed in a future version of the operating system.

MechWarrior 2 DOS 1.1

This game does not function properly on Memphis. To correct this problem, download the Mech2v11.exe patch provided by Activision on their web site at http:\\www.Activision.com.

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.

Microsoft Plus! for Windows 95

Once Memphis has been installed on your PC, DO NOT install Plus! for Windows 95. Memphis comes equip with a number of the Plus! performance features. In addition, if Plus! For Windows 95 was installed on your PC prior to your Memphis upgrade, DO NOT remove Plus! Performing either of these two actions will disable portions of Memphis.  These issues will be resolved in a future release of the operating system.

Microsoft Money 97

The Online Services portion of Money is temporarily non-functional. This will be fixed in a future release of Memphis.

Microsoft Office 4.0

This version of Office will not install on Memphis because share.exe is missing. Creating a dummy version of share.exe will not correct this problem. We are looking into correcting this in a future release.

MSVC++ 4.2

File versions conflicts will occur when installing this version of VC++ on Memphis. When prompted, do not permit fOLDER versions of files to be copied over the newer versions. Installing older versions will disable the Memphis active desktop.

MS Word 97

This application has been reported to randomly hang. This issue will be fixed in a future release.

MS Office 97 “FindFast”

This application is loaded by default in the Start/Programs/Startup folder. It has been reported to randomly hang. This issue will be fixed in a future release. Remove FindFast from the startup group to eliminate this problem.

Netroom 3.04

Netroom’s Customize has been reported to hang the system. Before setting up, verify that Cacheclk is not being loaded in the autoexec.bat file, the boot process of Memphis is interrupted as a result. Memphis will boot normally if cacheclk.exe, Netroom\Stacks.exe and Netroom\Setcfg.exe are disabled.

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 in the “FAT32” section of the Application Notes.

PC-cillin version 2.0

PC-cillin will not uninstall correctly after loading. Additionally, WordPad and MS Paint become disabled after PC-cillin is installed. Reinstalling both applications, WordPad and MS Paint, corrects the problem.

PhotoShop 4.0

When using the pull down menu Select, Color Range, a page fault results. Adobe has a patch on their web site (PhotoShop V 4.01) which corrects this problem.

Savage: The Ultimate Quest for Survival

This game has been known to hang during set up, occasionally display a double cursor and malfunction with the use of a S3 Trio64+ video card. To overcome these problems, reboot your PC. If the problems persist, the vendor recommends installing the 16-bit version of this game.

Where In The USA Is Carmen Sandiego

Unable to initialize graphics when running on Memphis. This will be fixed in a future version.

Zip-It 95

This application will not install on Memphis. It mistakenly believes Memphis is NT.

ZipFolders

Some Beta sites have reported that while attempting to convert a Zip file to a self-extracting archive, a general protection fault occurs. All other functions of this program work fine. This will be fixed in a future release 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 inaccessible while the driver is loaded and running. I.e. /D:test -then any file named test, regardless 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 have 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
  1. 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.
  2. Re-boot the system using the boot floppy, and format the disk with FORMAT.COM (found on the Memphis CD), with the /s switch.
  3. 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

  1. Rename the Autoexec and Config files on the boot floppy as follows:

REN A:\AUTOEXEC.CD AUTOEXEC.BAT

REN A:\CONFIG.CD CONFIG.SYS

  1. Copy your hardware vendor-supplied MS-DOS CD-ROM drivers to the floppy disk.
  2. 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.

  1. 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.
  2. 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.