	    * Windows 95 Beta-1.4 Release Notes *

INSTALLATION INSTRUCTIONS
=========================

Setup over previous versions of Windows 95
------------------------------------------   
You can upgrade Windows 95 versions 122 and higher.  To upgrade Build 122 
(M6/Beta 1) or later, you will have to run Setup from real-mode (it will
not run from Windows 95 GUI build 122).

If you are running Windows 95, you can get to real-mode by placing a 
"Pause" statement at the end of your AUTOEXEC.BAT file, and hitting CTRL-C 
when asked to "Press any key to continue . . ."  Or you can Interactive
Boot by hitting F8 when at the "Starting Windows..." message at boot time and
answer NO to WIN at the end of AUTOEXEC.BAT processing.  You should then be 
able to run Setup from the C:\ prompt.

As of build 170, Windows 95 no longer preserves your hardware settings on an 
upgrade. Please note your hardware settings prior to install.  This applies  
to your network settings as well, so you may have to manually configure your 
network settings.  A "Custom" install will show all the wizard pages so the 
settings can be verified.

Location of the Programs Folder
-------------------------------
As of build 189, the Programs folder was moved from the Windows folder to
the Start Menu folder.  Any links that you had in your Old Programs folder will
NOT be automatically moved the new Programs folder in the Start Menu folder.
You will need to manually move any links from the Old Programs folder in the
Windows directory to the new Programs folder in the Start Menu folder.

Setup over Windows NT (including Daytona)
-----------------------------------------
If you are multi-booting MS-DOS and Windows NT, boot to MS-DOS, and
run Setup from either MS-DOS or Win 3.x.  You will not be able to
install Windows 95 to a directory with a shared Win 3.x/Windows NT
configuration, you will need to install Windows 95 to a different
directory.

If you are not multi-booting MS-DOS and Windows NT, you should
configure you machine to multi-boot MS-DOS and Windows NT first, and
then follow the instructions above.

If you boot MS-DOS from a floppy and run Setup, you will no longer be
able to boot Windows NT (however, you can restore Windows NT by
booting from the Windows NT boot/repair disk, and selecting the
"Repair" option).

Setup over OS/2
---------------
If you are using OS/2 Boot Manager to choose operating systems at
startup, Setup will disable Boot Manager to insure that Windows 95 can
reboot the system and complete its installation. Boot Manager can be
reactivated by booting with an OS/2 boot disk and using the OS/2
FDISK utility.

If you are not using Boot Manager, you should configure your machine
to use Boot Manager, and then follow the instructions above.

If you boot MS-DOS from a floppy and run Setup, you will no longer be
able to boot OS/2 after Windows 95 has been installed.  You will need to
delete the AUTOEXEC.BAT and CONFIG.SYS files that OS/2 uses before
running Windows 95 Setup.

Known Setup Problems
--------------------
- Selecting keyboard layouts International English will not work
  correctly.  You must do this from the control panel keyboard
  language applet.

- Some settings in PIF files will be lost on an upgrade
  over build 122.

- Shortcuts to Control Panel Applets will be lost on an 
  upgrade over build 122.

- The WINBOOT directory that was created in build 122 
  is no longer used, you can delete it.

- WINBOOT.SYS is no longer used (and should be deleted by Setup).  
  It has been replaced with IO.SYS.

- WINBOOT.INI is no longer used.  It has been renamed to MSDOS.SYS
  for compatibility reasons.  MSDOS.SYS should NOT be deleted. 

- COMMAND.PIF will be deleted when upgrading over a previous version
  of Windows 95. 

- If you receive the following error message during setup:

    Generic Installer Error
    UpdateInis= processing error
    exiting with error code = 405

  File a bug report, then remove the Device=EMM386.EXE line from 
  CONFIG.SYS and re-run Setup.  Be sure to include the setuplog.txt,
  win.ini and system.ini files in the bug report.


WordPad and these Release Notes
-------------------------------
For those of you using MSVC20 and the integrated development 
environment and/or MFC dll's, you will have to re-install MSVC20 
after you have installed this version of Windows 95.  This is because the 
WordPad applet uses shared MFC DLL's which are not compatible 
with the integrated development environment.  However, before you 
do this, please use WordPad to review these release notes and possibly 
print them as you need to because once you re-install MSVC20, WordPad 
will no longer work.  This version problem will be addressed in a later 
version.

NOTES FOR SETTING UP NETWORKS
==============================

General
-------
If you are setting up Windows 95 for a network, ensure that the network client 
software is correctly installed and is running.  Verify network connectivity 
by connecting to a server before you run Setup.  Also be sure that the 
directory that contains your network software is in the PATH= environment 
variable.

As of build 170, Windows 95 no longer preserves your hardware settings on an 
upgrade. Please note your hardware settings prior to install.  This applies 
to your network settings as well, so you may have to manually configure your 
network settings.  A "Custom" install will show all the wizard pages so the 
settings can be verified.

During the net part of setup, if you double-click on the client you must 
either disable logon validation or enter a value in the domain field 
(it's blank by default).

Frame Type
----------
The Microsoft IPX/SPX compatible protocol now automatically detects
the Frame Type.  The Frame Type should be set to Auto.

Novell NetWare (VLM)
--------------------
If you are upgrading over a machine running VLM but not running Windows, you
will have to run the Novell VLM install program.  This program adds lines to 
your system.ini that are no longer necessary.  When you install VLM support in
the network control panel, it will remove these lines.  Until you do so, 
you will get error messages about vnetbios not being present when you boot.

Banyan VINES
------------
When you first boot into Windows 95, the Banyan drivers will report that
the VINES version is not the latest.   Follow these steps:

1. Check the "Keep files on network" option.  If you do not have this
option, edit your vines.ini and remove the WindowsVersion line.
2. Click Cancel
3. Windows will restart. When it does, click Install.
4. Windows will restart again.   VINES should now be configured properly.

Net adapter hardware resources page does not save settings
----------------------------------------------------------
The net control panel has problems saving changes to hardware resources.
If you type the new settings in on the keyboard, it will not save the
settings.  Instead, you should change settings with the mouse by using
the spin controls next to each setting.

Cancelling copying files
------------------------
If you go into the net control panel, add something, setup will save the changes 
even if you press cancel while Windows is copying files.  When you reboot, you 
may receive error messages about missing components.   This is a known problem.
To fix the problem, go back to the net control panel and remove the component 
that you had added.

INSTALL NOTES FOR PARTICULAR DEVICES
====================================

Logitech Mouse
--------------
If you have a Logitech mouse and run Setup from MS-DOS, your mouse may
not work during Setup.  This is a known problem and will be fixed in a
future build.

PS/2 Mouse
----------
Anyone installing build 166 over 165 on a machine with a PS/2 mouse should
change the line DOS=LOW,UMB in CONFIG.SYS to DOS=HIGH,UMB before
installing. This will fix the problem of not being able to move the
mouse (and probably use the keyboard) during setup.

Bus Mastering Disk Controller
-----------------------------
"If you have a Bus Mastering disk controller and greater than 16MB of
memory, then you most probably will need a 'SWITCHES=/D' in
CONFIG.SYS.  This will force double buffering to happen and get
around a bug we have in double buffering."

Displays
--------
SYSTEM.INI, [boot] will now always contain "display.drv=display.drv"
if a Windows 95 version display driver is installed.  The actual driver
(e.g. VGA.DRV, S3.DRV, etc.) is loaded from the registry as of this
release.

Computers with a PCI Bus
------------------------
If you have a computer with a PCI bus, you must remove any memory managers 
(such as EMM386, QEMM, etc) before running setup.

IBM Thinkpad 720
----------------
The PCMCIA socket for the IBM Thinkpad 720 is not supported in this release. 
You will not be able to install 32 bit PCMCIA drivers for this computer.

Intel EtherExpress16
--------------------
If you have an Intel EtherExpress16 network adapter, setup may detect that 
it is using IRQ 3.   This setting will conflict with your mouse or serial 
ports.  While setting up, go through Custom setup and verify the net card 
settings.  On the network screen, bring up the properties for the Intel 
EtherExpress16 and go to the Resources page.  Set the IRQ to 5 (or any value 
other than 3 that does not conflict with other devices on your system).

Xircom PE3 Parallel Port Ethernet Adapter
-----------------------------------------
On some machines, the first boot following setup might say your Xircom PE3
adapter is not functioning.  Machines that are affected have lpt ports that
use an Input/Output range other than 378, or an Interrupt of other than 7.
Examples of machines that have this characteristic are IBM Thinkpad laptops
and some Compaq laptops.

If you do not know what value your lpt port uses, look in the System control
panel, Device Manager page, Ports\Printer Port Properties, Resources page.
The Input/Output range should be 378, 3BC, or 278.  Also, if the Printer Port
is LPT2, you will want to use Interrupt 5.

You will want to set your PE3 to use these values.  To do this, look in the
Network Control Panel, Xircom PE3 properties, Advanced Properties page.  Set
I/O Base Address to the value you found in the Input/Output box for your
Printer Port, and set the Interrupt Level to 5 if you are using LPT2.

Reboot your system, and your network should become active.

NETWORKING
==========

Novell NETX with ODI: MAY HANG ON BOOT; there is a workaround
-------------------------------------------------------------
If you run Novell's NETX client with an ODI driver and you have selected no other 
networking client, your computer may hang on boot with a black screen.  This is 
due to a driver that Windows 95 setup places in your AUTOEXEC.BAT file that is 
not needed for the NETX/ODI only configuration.  

In your AUTOEXEC.BAT file, comment out (REM) the line that loads ODIHLP.EXE.  In order 
to do this, you should NOT boot to your previous OS.  

1) When booting into Windows 95, you should see a "Starting Windows..." line at the 
top of your screen.  Immediately press the F8 key when you see this.  
2) From the Windows Start-up Menu, select "2. Command-line Start".  This mode bypasses 
both your CONFIG.SYS and AUTOEXEC.BAT files and does not autostart Windows.  
3) Edit your AUTOEXEC.BAT file, comment out the line containing ODIHLP.EXE, and reboot.

Note that this hang does not happen on all computers.  This is specific to NETX and 
the ODI drivers.  You will not encounter this problem if you have IPX monolithic 
or VLM.

MS Network & Downloading policies
---------------------------------
If you are running a real mode net (i.e. netx or vines) & MS network is 
your primary network with a domain name filled in, we will try to 
download policies from your domain, which involves doing a
RegLoadKey on a network file.  This has the potential to deadlock your 
machine.  One workaround is to remove the registry entry that controls 
policy downloading, which would disable downloading and avoid the 
RegLoadKey.

Mapping a network drive in the GUI for VLM clients
--------------------------------------------------
With certain versions of the VLM client, you will be unable to map a 
network drive using the GUI.  If you go out to a dos box, you will still be 
able to map the drive.

LOGONOFF.EXE
------------
LOGONOFF.EXE has been removed starting with build 170.  The only way to log 
off in Windows 95 is from the tray, choose Start, Shut Down..., and the third 
radio button (currently worded as "Close all applications and log on as a 
different user").

Using Btrieve (BREQUEST.EXE) with MS Client for NetWare
--------------------------------------------------------
With the MS Client for NetWare, we have seen problems with applications that 
use the Btrieve database. The error: "Btrieve error 20" - unable to initialize record manager

NetWare printing: Getting Properties of NetWare printers hangs
-----------------------------------------------------------------------
If you right-click on a NetWare printer to get its properties, your computer 
may appear to hang for several minutes.

NetWare printing: Printing test page to NetWare printer GPF's 
------------------------------------------------------------------
If you print the test page to a NetWare printer, you computer may page fault.

Printing with Novell NETX client
--------------------------------
In this release, you cannot print to a CAPTURED printer from Windows 
applications when running the Novell NETX client.  You can install the
printer via the Windows 95 printer install, and print that way.

Novell NETX/VLM: Executing login scripts may hang machine
----------------------------------------------------------
To avoid this, add "shell=c:\windows\command.com /p /k /d" in your AUTOEXEC.BAT.

Problem with NETX.VLM dated 12-09-93
------------------------------------
There are known problems running Windows 95 with the Novell VLM component file 
NETX.VLM that is dated 12-09-93.

INFO CENTER
===========

Installing Info Center
----------------------
NOTE: To use the Info Center, you must first have a MS Mail or Workgroup 
Postoffice to connect to.  Please see "Installing a Workgroup Postoffice" 
below.

Info Center is not installed on Windows 95 by default.  To install the Info 
Center, choose the Custom Setup option in Setup.  When you are prompted with 
a list of components, you must select BOTH  "Info Center" and "WMS" 
components.  Setup will install the Info Center icon on your desktop.  The 
first time you launch the Info Center, you will be prompted for additional 
configuration information.

Installing a Workgroup Postoffice
---------------------------------
The Workgroup postoffice installation and administration component is not 
included with this release. To install a Workgroup postoffice, you need 
Windows for Workgroups version 3.11 or Windows NT version 3.1 or 3.5.

From Windows for Workgroups or Windows NT, run the mail program. It asks you 
if you want to (a) connect to an existing postoffice or (b) create a new 
postoffice. Choose the Create A New Postoffice option. Put this new 
postoffice on a network server that Windows 95 machines can access. Next, a 
dialog box appears asking you to identify the administrator's account. Type 
Administrator into the user name field and admin into the mailbox field.

When this has been completed, choose Postoffice Manager from the Tools menu; 
doing so starts the Workgroup postoffice administration component, which 
enables you to add users to and remove them from the postoffice. Users 
connecting to the Workgroup postoffice need the following information: the 
location of the postoffice on the network server, their mailbox name, and 
their password.

More information on creating a Workgroup postoffice is contained in the 
Windows for Workgroups Resource Kit and the Windows NT Resource Kit.

New Features:
-------------
1. Drag and drop now works.
2. Attachments now work.
3. Next/Previous buttons now enabled.
4. Grouping messages now works.

Known Problems:
---------------
1. New Personal Information Store format.  Your old store from the M6 release
is not compatible with the new format.  You must create a new store and
start from scratch.
2. New Personal Address Book format.  Your old PAB from the M6 release is
not compatible with the new format.  You must create a new PAB and start
from scratch.
3. Next/Previous Message On Delete is not enabled.
4. Remote client not working.
5. Personal Information Store doesn't compact.
6. There is no interop between M6 and the M6.2 releases.  You cannot
send/receive messages to/from mismatched Windows 95 releases.  Upgrade all
Info Center users simultaneously.
7. The CompuServe Provider from the M6 release will not work on this version 
of Windows 95.  There will not be a Compuserve Provider available for this
release.
8. Simple MAPI for 16 bit applications  is not yet implemented.  You cannot
use Simple MAPI for 16 bit applications running on Windows 95 (e.g. File.Send
in MS Word running on Windows 95.)
9. Start/Find/Infocenter is not working properly.

MAPI SDK
--------
There is no new MAPI SDK included with this release of Windows 95.
Updated headers and libraries will be posted on Compuserve so that 
developers can update their code to work on this release of Windows 95.

MICROSOFT AT WORK FAX - Known Problems in this Release
======================================================

Adding Microsoft At Work Fax to your Messaging Profile
------------------------------------------------------
Do not select the option to "Use an information service not listed above" in the 
Info Center Configuration Wizard to add Microsoft At Work Fax to your messaging profile.  
Instead, create a profile using the default information services and then use the Info 
Center Icon in Control Panel to edit this profile.  Select your messaging profile and 
press the "Properties" button.  From the properties pane, choose "Add".

Multiple FAX recipients and Automatically attaching cover pages does not work
-----------------------------------------------------------------------------
Attempting to send a single fax to multiple receipents or attempting to send a 
cover page by selecting "Send cover page" in the message property pane of Microsoft 
At Work Fax will cause access violations.

Security and shared fax modem functionality is not enabled
-----------------------------------------------------------
These features will be available in the next release.

Modem dependencies
------------------
Some modems may experiance problems even if they were working in previous betas due 
to TAPI integration issues.  Please include both the make and model of your modem 
when reporting any bugs against this release.

DOUBLESPACE and DRIVESPACE
==========================
M6.4 contains the new DriveSpace disk compression application to 
allow you to compress drives under Windows 95 and to manage existing
DoubleSpace and DriveSpace drives.  You'll find it on the Start menu
in the Programs\Accessories\System Tools folder.  Although DriveSpace
has already been tested extensively, we recommend that you backup your 
system before using it.  Known limitations:
  - Uncompress is not enabled in this release.
  - If you are already running Stacker, do not run the DriveSpace application.

When you install Windows 95, Setup will update your D??SPACE.BIN drivers 
with versions that support both DoubleSpace and DriveSpace drives 
simultaneously.  Setup will also disable the D??SPACE.EXE, SCANDISK.EXE
and DEFRAG.EXE programs in your \DOS directory and install a BAT file
that tells you how to run the Windows 95 equivalent.  The old versions
of these drivers and programs will be deleted if you upgrade a previous 
Windows installation, but if you "clean install" Windows 95 to a different 
directory, Setup will preserve the old versions of these files by 
renaming them.

DEFRAG and SCANDISK
===================
M6.4 now supports defragmenting DblSpace and DrvSpace drives.
However, the option to defragment compressed volume files (this 
only applies when defragmenting host drives) is not enabled.  When Defrag
starts up (or restarts after a disk write), it currently exhibits a lengthy 
pause at 0%, before the gas gauge starts moving.  This will be corrected in
a future release.

The Windows disk checking/repair tool is now called ScanDisk. Windows ScanDisk
can now detect when a long name has been incorrectly associated with a file; 
it repairs it by deleting the long name.

APPLICATION COMPATIBILITY
===============================

Re-installing Applications
--------------------------
If you upgrade your existing Windows 3.1 or Windows for Workgroups 
directory to Windows 95 then you do not need to re-install your applications.   
If you install Windows 95 to a new directory then you must re-install all of your 
Windows-based applications.  Hand copying files from your Windows 3.1 
directory to Windows 95 is not sufficient. 

Right-clicking on DOOM, Flight Sim, or Space Sim in order to view their
properties page may cause the system to freeze.  The work-around is to
change their properties from inside the Application Install Wizard, which
can be found in the control panel.

Some of the versions of LFNBK that were released earlier may not function
correctly with Windows 95 release 6.4.  You should download the current
version from Compuserve for this release.

When opening the help file for some applications you may see an error
telling you that the help file is corrupted.  If you dismiss the dialog
box you should be able to proceed normally.  This is a known bug.

Wordscan Plus 3.0 may not work with this interum release of Windows 95.

SuperStor compression not fully supported in M6.4  You may not be able to get 
SuperStor compression working with Windows 95 M6.4.  If you do decide to
install over SuperStor please report any problems you encounter.

The DOS version of Colorado Backup may not function correctly with this
release.  The Windows version is working so please report any problems you
find.

F4 function with Stacker Ver2.0 & 3.0 and other compression software may not
function in this release.  Use the work-around described in the Beta 1 release
notes to use F4 boot option with these utilities.

If you compress your Windows 95 volume using the Stacker DOS compression
program your desktop shortcuts will need to be manually repaired.  You will
also need to move USER.DAT & USER.DA0 from the host volume to your compressed
volume.

AD-DOS.COM in AUTOEXEC.BAT prevents Windows from loading the After Dark TSR 
because AD-DOS.COM stops Winboot.sys from calling Win.com.  User can 
type Win at the command prompt to continue executing Windows 95.

Quick Time for Windows will cause a general protection fault that will hang
the system.  A work-around is to add the below settings to QTW.INI:
	[video]
	Optimize=RAW

Embedded TrueType Fonts Not Displayed - Microsoft PowerPoint can embed 
TrueType fonts in a saved document so that your presentation can use those
fonts even if they are not installed on the another system. 

PowerPoint 3.0 may GPF if you hit the F1 key without a presentation loaded.

Disk Utilities - Direct disk writes using Int 26h or Int 13h will fail under
Windows 95.  This is necessary in a multi-tasking environment to prevent disk
corruption from multiple utilities running simultaneously.  The LOCK and
UNLOCK commands can be used as work-arounds for DOS utilities.

Adobe Acrobat 1.0 - Acrobat 1.0 is not functioning correctly on this Windows 95
release.  The problems are understood.  You should upgrade to Acrobat 2.0.

Microsoft Visual C++ v1.5 - A duplicate VMCPD entry will be placed in your 
SYSTEM.INI file during installation.  You should remove this entry to avoid 
Windows 95 error messages while booting.

Symantec C++ version 6.1 Profession Will Not Run Under Windows 95.  Symantec
Norton Utilities version 8.0 Will Not Run Under Windows 95.  These applications
will refuse to run under any version of Windows except for 3.1.

Flight Simulator Unable to Lock XMS Memory with SoundBlaster - Microsoft 
Flight Simulator 5.0 crashes with a message "Unable to lock XMS memory-fatal
error" if you try to run it with a SoundBlaster/SoundBlaster Pro card.  To 
work-around, run the Flight Simulator setup program.  On the sound board
settings screen, choose 'NO' for the 'Use XMS Memory' option.

Flight Simulator Hangs when Changing Speaker Settings.  If you change your PC 
speaker settings after you set up Microsoft Flight Simulator 5.0, you will
hang your system.  Select the PC speaker during Flight Simulator setup.

Minimized Clock in Startup Group Runs Maximized - If you had CLOCK.EXE in 
your Windows 3.1 Startup group set to start minimized, Windows 95 will start it 
maximized.  This is a known problem.

Microsoft Publisher - Currently, changes to text in a text frame 
(font, font size, bold, etc) do not occur until the mouse is clicked.  As long
as the mouse click occurs in the 'document design area' (ie. not on a menu or 
button bar), changes will take place.

Cinemania '94 - There are display problems which affects video types such as 
ATI and S3 when using Cinemania '94.  If you experience incorrect colors 
when in 256 color mode,  run in a color mode greater or less than 256 colors.  
Doing so allows Cinemania to run without problems.

cc:Mail installation fails from inside a Windows 95 VM.  cc:Mail should be 
setup using single MS-DOS application mode.

Virus utilities can detect but not clean viruses from Windows 95.  This is
because virus utilities use low-level writes to repair the disk.  MS-DOS
based utilities can still be run using the LOCK command.  Windows virus
utilities can only repair viruses if you setup Windows 95 in Windows 3.1
Compatibility mode (no long file names).

Do not install IronClad on the same machine as Windows 95.  The security 
features of Ironclad create numerous problems for Windows 95.

Dashboard may cause Windows 95 to hang or spontaneously shut down.

Laplink Pro - Running Laplink Pro 4.0a with a communication rate of >9600 
may not recognize other connected machines.  If you have this problem change 
the communication rate to 9600.

Xtree Gold 2.51 for Dos - Xtree Gold cannot PRUNE directories.  The
work-around is to manually delete the directory structure using another VM.
Also, Xtree Gold may see long filename components while running in real mode.

Timeline 1.0 for Windows- The tutorial for Timeline is not functioning with 
this release.

APPLETS
=======
NOTE: all of these problems will be addressed in a future release.

WordPad
------
OLE drag and drop.  WordPad is a full 32 bit app now.  Drag and drop 
works between two 32 bit apps, but it doesn't yet work between WordPad
and a 16 bit OLE server app.

WordPad will not allow you to open a document which is already open 
by another application.

A paste from WinWord 6 shows up as an OLE link.

Wordpad truncates some OLE embeddings.

Wordpad may not read very complex WinWord 6 documents correctly.  If you
have such a document, please submit the document with your bug report so
we can get these problems identified and fixed.

WinPad
------
WINPAD DATA FILES: WINPAD.DAT and WINPAD.IDX are data files that store 
information entered in any of the WinPad applications as well as WinPad's 
online Help. Deleting these files removes all stored information as well 
as online Help. 

REINSTALLING Windows 95: If you need to reinstall this release of the Windows 95 
beta, follow these steps after running Setup in order to restore the existing 
data from your previous WINPAD.DAT file:
1. Copy WINPAD.BAK to WINPAD.DAT
2. Delete WINPAD.IDX

EXITING WINPAD AND Windows 95: Exiting Windows 95 before you exit WinPad can cause 
your system to hang. Therefore, always close WinPad before closing Windows 95. 
This problem will be fixed in later versions of the product.

Keyboard Support has been enhanced, but is not fully implemented in this 
release.

MSPaint
-------
Text Selection.  Selecting text in the text box results in incorrect 
painting of the selection.

Rotating an image either 90 or 270 degrees changes the colors

Drag and drop of a selection into an OLE client doesn't work yet.

Menus not available in print preview.

File Viewers
------------
Several new features have been added to file viewers.  Once a file 
viewer window is open, you can drag and drop files from the cabinet 
onto the viewer window.  The View/Reuse Window command 
controls whether a new window is created.  Also, if a file is not 
recognized, it is displayed as a HEX dump, although this feature 
doesn't always work in this release.

Support for viewing PowerPoint 4, Excel 5 charts, and 1-2-3 for 
Windows charts has been added.  Note this version will not work 
when viewing PowerPoint 3 charts. 

Backup
------
-- Compression is included, to enable look at settings/options/backup
   dialog.

-- this version of backup will NOT work with file sets or backup sets
   created by older versions of backup.  To re-use a tape, erase the tape.

-- the on tape format is subject to change between now and when Windows 95
   is releases so do not store any important information on tapes as it
   may not be readable in a later version of Windows 95.

-- Trying to abort a backup or restore operation before it has completed
   will result in a fault.

-- Once a files are backed up to a floppy disk, it is not possible to
   open the backup set file in the restore or compare tabs.  We are
   looking into this and hope to post a patch on the CS beta forum
   which you can download.

-- restoring a backup set which spans 2 or more floppies or tapes does not
   work with this release.  bug with linking volumns.  Will be fixed in a
   later release.

-- The backup app will not load correctly if a VxD from any other backup
   application is already loaded.  Thus, if you have installed Norton/Symantec
   Backup for DOS or Win or Colorado Memory Systems backup for DOS or Win,
   you will be loading a VxD in your System.ini file automatically.  To
   prevent this file from being loaded, comment out the line in your
   System.ini file.

MS-DOS Editor
-------------
NO Known problems.  If you find one, please report it on the CS beta forum.

HyperTerminal
-------------------
New Features:
+ You can now use HyperTerminal to connect directly to a port.  Try it! When you create a new connection look at the items available in the "Conncet Using" drop down.

Known problems: (all of these problems will be addressed in future releases)
+ If you do not have a modem installed HyperTerminal recognizes this and asks you if you would like to install a modem.  When you have completed the installation and return to HyperTerminal it does not recognize that you have installed a modem and will prompt you to do so again.   The work around is to either install a modem before running HyperTerminal, or if you install a modem when prompted to do so by HyperTerminal then you will need to close and restart HyperTerminal before the modem will be recognized.
+ phone number to be dialed is prefixed with a "T" or a "P" - just ignore this 
+ Capture File function cannot be turned off. Capture menu item should change to a cascade menu with options to stop, pause, etc.
+ Several people have found that sometimes HyperTerminal disconnects or won't connect
+ problems receiving files to D: drive on system with 2 IDE drives
+ On a VGA monitor HyperTerminal may come up underneath the tray
+ sometime auto detection does not work properly.  If you run into this you can manually set your data bits, parity, and stop bits via Configure button on the Phone number tab under File/Properties for your connection. 
+ old Terminal (.TRM) files are displayed in the File/Open dialogue but HyperTerminal can not yet open these files.
+ If you enter an invalid in valid area code, or phone number this is not detected correctly and instead of prompting you to correct the number the mini tapi wizard is run instead.  The fix here is to enter valid numbers!
+ cannot receive file to root directory.  The work around here is to receive files to a folder.
+ Dial Now should not be disabled will a connection is being made
+ An improved error message needs to be in place if the comm port you are trying to use is already in use by another app.
+ keys are sent to host when you use page up and page down to review scroll up and down to review the buffer
+ Hypertrm.exe will be getting a nice long file name"
+ you can not send commands directly to your modem


PRINTING
========

Printing With Image Color Matching
----------------------------------
Printing with image color matching is not functional in this release of
Windows 95.

Printing from WordPerfect for Windows
-------------------------------------
If you are printing from WordPerfect for Windows, and using the
WordPerfect printer drivers, you must have a Windows 95 printer driver
installed to the same port for this to work correctly. This will be
corrected in a future release.

Printing with the Windows Printing System
-----------------------------------------
You must disable sounds from the Windows Printing System in order to
have it work correctly in this release. This will be corrected next release.

DISPLAY
=======

Known Problems
--------------
If Windows 95 reports a problem with your display settings at startup, 
make sure that "Use device" is set in the System control panel, Device 
Manager page, display adapter Properties, General page, Device Usage 
section.

ATI mach64 ISA adapters are not supported by the Win95 mach64 driver.
PCI and VLB adapters should run fine.

Animated cursors are not supported on Western Digital adapters, 
this will be fixed in the next release.

M6 bugs fixed in beta 1.2
-----------------------------
It is now possible to change desktop area to 640x480 without 
restarting (provided color palette and font size stay the same).

Bugs fixed in beta 1.4
----------------------
Cursor problems on Orchid Kelvin adapters are fixed.

Problems running windowed MS-DOS Prompts and applications on 
Compaq AVGA and QVision display adapters are fixed.



MODEM COMMUNICATIONS
====================

New features in M6.2
--------------------
All AT command modems are now detected by the Modems control 
panel.  In this release, most are detected as generic modems, 
(incl. some models that were detected by name in M6).  The 
detection scheme is in the process of being revised.  
Many more models will be detected in future releases.

If your modem is detected as type "Generic", please find the
MODEMLOG.TXT file in your Windows directory, and e-mail this
to modemdet@microsoft.com.  Edit the file to include the *precise* 
make and model name for your modem as it appears on the modem's 
packaging and user manual.  This will help us improve Win95 
modem detection.

Bugs fixed in beta 1.2
----------------------
Performance of background comm applications is improved during 
foreground activity.

Bugs fixed in beta 1.3
----------------------
Sporadic failures of Windows comm apps (e.g. WinCIM) caused by COMENUM.VXD
should be fixed.  If you experience these with this build, please submit a
bug report immediately.

Bugs fixed in beta 1.4
----------------------
Problems with comm programs caused by COMENUM.VXD are fixed.
Note that COMENUM.VXD has been renamed SERENUM.VXD.


MOUSE
=======

Known problems
--------------
Error messages about POINTER.EXE at startup occur if your
mouse is not correctly detected.  To fix this, use the
Mouse control panel to change to the appropriate Microsoft
mouse type, which will enable POINTER.EXE to load and support
Mouse Manager features.

To use Logitech MouseWare, make sure your mouse is set
to one of the Logitech types.  Edit SYSTEM.INI so that
the mouse.drv= line in the [boot] section reads "mouse=lmouse.drv".

Bugs fixed in beta 1.3
----------------------
Speed control is working again in the Mouse control panel.


CORE
====

New core features and bug fixes for this M6.3 release:
------------------------------------------------------
Continued performance enhancements.   This version of Windows 95 should be 
faster than either M6.2 or M6, but it's not yet up to the final release
goals on a 4MB machine.  If you are installing Windows 95 on a 4MB machine 
with a network, setup will install several networking protocols as well 
as the file/print server by default.  The server portion is probably 
something you don't want to run on a 4MB machine and removing it should 
decrease the memory requirements for Windows 95 and make your applications 
run faster.  In future releases, Setup will not (by default) attempt to 
install the server software.  Also, if you have MSCDEX loaded in your
config.sys for a 4MB machine, you should remove that line in order to 
increase performance for this build.

BASE
====

M6 bugs fixed in this release
-----------------------------
1. FLAG_NO_BUFFERING fixed to work as doc-ed in API.
2. IN-2000 adapter related bugs fixed.
3. Sony miniport bug fixes and performance tweaks.
4. Panasonic miniport bug fixes and performance tweaks.
5. Old Future Domain BIOSes (which were buggy) now supported.
6. CD now uses sync data transfer (and async is a user option).

New features in this release
----------------------------
1. PCI IDE supported through protect mode IDE driver.
2. Protect mode driver for Mitsumi miniport.
3. Protect mode driver for Mediavision (with Trantor CD interface).
4. Protect mode driver for DblSpace and DrvSpace drives.
5. UI for manipulating adpater related settings and drive letters.
6. Virtual Memory applet redesigned and bugs fixed.

AMD SCSI
========
If your system has AMD SCSI installed, then you must remove the following
5 lines from SYSTEM.INI to disable AMD SCSI fastdisk. Drives controlled
by this adapter will not be accessible unless these lines are deleted.

 These three lines deal with the FASTDISK driver:
   AMSIWF=TRUE
   device=AMSIWF.386
   device=AMSINT13.386

 These three lines deal with the Windows ASPI stuff:
   AMSIAV=TRUE
   device=AMSIAV.386

You can also disable FASTDISK/WIN ASPI by setting the AMSIWF and AMSIAV
flags to FALSE.


CONTROL PANEL
============
Regional Settings: Selecting a locale has no effect until you reboot 
the system.

PLUG AND PLAY
=============

M6 Bugs fixed in this release:
------------------------------
- Using PCMCIA modems with Win16 applications.
- "New device found" and/or "Device conflict" messages should not appear
  any longer during setup/first boot on PCI or EISA machines. Please file
  detailed bugs if you still see these messages.
- "Safe detection" has been added to the setup process. If certain classes
  of devices such as network or CD-ROM are not detected via safe methods you
  will be prompted to force hardware detection on these classes.
- Better "crash recovery" during detection. Please file detailed bugs if
  you still have multiple hangs during setup.

New features in this release:
-----------------------------
- PCMCIA support will be disabled by default. In order to enable Windows 95's
  32-bit PLug & Play PCMCIA support, do the following steps:
  a) Choose Settings->Control Panel from the Start menu, and start the
     PCMCIA control panel.
  b) Starting the control panel will automatically launch a wizard which
     will walk you through the process of disabling your real-mode
     PCMCIA support and enabling the Plug and Play drivers.
  c) The wizard automatically determines which drivers should be
     commented out of AUTOEXEC.BAT, CONFIG.SYS, and SYSTEM.INI. If makes
     erroneous suggestions or misses a driver which is related to PCMCIA,
     please file a detailed bug report as soon as possible, including the
     names of the drivers in question.
- The following portables have been tested with the Windows 95 PCMCIA 
  drivers:
  AST Bravo, Austin, Compaq Aero, Compaq Elite, Compaq Concerto,  Compudyne,
  DEC 425SL, Gateway Handbook, Gateway Colorbook, IBM Thinkpad 750, 755, 355,
  360, 500, NEC Versa V, Versa E, UltraLite, Toshiba T4600, T4700, T4800,
  T3400, T3300, TI TravelMate, TI M-Series.
- Hot docking works on Plug and Play portables with docking stations.
  Docking support includes automatic switching of screen resolutions when
  docked and undocked.
- Device Manager now includes a hierarchical "tree view" of your system.
- Device Manager allows printing of system and device properties and
  resources.
- Serial port enumerator enables automatic installation of Plug and Play
  modems and mice.
- Video enumerator enables automatic installation of Plug and Play 
  monitors.

Known issues in this release:
-----------------------------
- Do NOT remove devices from your system using the device manager. Also,
  do not remove modems using the modem control panel.  It is still OK to
  disable devices with the device manager if you wish to not use a device
  that is installed.  This will be cleared up in the next release.
- Hot removal of IDE PCMCIA card may cause a "blue screen". This is  
  harmless, hit enter to recover.
- Installing hardware from the new device control panel may result in an
  installation with no hardware resources. If you install a device in this
  way and you know the resources the device is using you should reserve
  those resources from the device manager under system properties.
- Enabling PCMCIA on some portables may cause the system to reboot. If this 
  happens, remove all PCMCIA cards from your machine, restart and disable 
  PCMCIA via the Device Manager tab in the System control panel. Please 
  file a detailed bug report specifying the type of portable, amount of 
  memory, cards installed, etc.

REGISTRY/REGEDIT:
=================
M6 Bugs fixed in this release:
------------------------------
- Automatic recovery when registry gets corrupted
- Several minor cleanups to the Regedit user interface.
- A bug was fixed which would cause Regedit to GP fault at startup on
  certain machines.  If you still encounter GP faults with the new version 
  of Regedit, please be sure to file a WinBug through Compuserve.

New features in this release:
-----------------------------
- Regedit now remembers screen position and window size settings.
- Regedit now includes a search feature, which will allow you to search 
  for text in Key names, Value names, or Value data.  Searching for binary 
  data is not supported.
- Regedit can now be run in real-mode to import or export registry
  information to/from .REG text files. Run REGEDIT /? for syntax details.
  Note that running regedit from a Windows 95 MS-DOS box will still invoke
  the GUI editor, however.

POWER MANAGEMENT:
==================

M6 Bugs fixed in this release:
------------------------------
- A bug causing intermittent hangs in suspend or resume operations has 
  been resolved.
- Machines which used to crash at Windows 95 startup when APM features were
  enabled should work properly now.
- Several fixes to the battery meter to work around buggy status reported
  by various machines have been included.
- Screen saver power management features are no longer visible unless your
  machine has the required hardware and software interfaces.  These
  requirements are: a) An Energy Star (VESA DPMS) monitor, which is settable
  from the Monitor Settings property sheet, and b) a system BIOS supporting
  either APM 1.1 or VESA BIOS Power Management extensions.

Known issues:
-------------
- Some machines may not suspend "automatically" based on inactivity 
  timers. However, user-initiated suspends should still work correctly.
- Resuming from suspend while running in fail-safe mode may cause disk
  access problems on some machines, typically resulting in GP faults which
  require a system reboot.

PEN WINDOWS
===========
1. The pen driver does not work on the Compaq Concerto even though it's
listed as one of the supported hardware configurations.  The Grid 
convertible, however, is now supported.

2. On a system with multiple users, an individual's customized settings
can be saved by turning on "Users can customize desktop settings" in
the Profiles dialog in the Security applet in the Control Panel.  These
settings include options such as ink color, ink width, and other pen
related attributes.  However, there is currently a bug which prevents
an individual's training to be loaded when this setting is turned on.

3. There is currently a bug which prevents the user from writing in the
Edit Text dialog or the Insert Text dialog if they are opened with a
gesture.

4. When running the debug version the Windows 95 pen extensions, do not
plug your mouse into the Com 1 port. Doing so can cause unpredictable
mouse and pen events.

5. Pressure pens do not work with the WACOM HD-648A.  If you turn off
this option in the registry, your pen should work fine.

ACCESSIBILITY
=============
The following notes describe features designed for users with disabilities.

New features in this release:
-----------------------------
1. Accessibility features can now be adjusted using the Accessibility icon
in Control Panel, which has on-line help.
2. A new accessibility status indicator can be displayed on the task bar or 
as a floating window.
3. The SerialKeys feature now functions to allow alternative input devices
to simulate keyboard and mouse input.
4. The High Contrast feature now allows you to switch between normal and 
high contrast color schemes.

New bugs since M6
-----------------
1. SerialKeys will cause a system errors when turned off, and you can't 
change settings once the feature is turned on.
2. Appearance schemes chosen using the High Contrast feature are not always
reflected in the Display property sheet, the Accessibility Status 
indicator, and the system Start button.

SDK/DDK
======
Win32 tools
-----------
The Release of MSVC++ 2.0 that shipped with Beta 1.3 can be use with this
build of Windows 95.  One file will need to be replaced.  The file be found
on the CD in the \SDK\VCPATCH directory.  This replacement file will also be
necessary with the final version of MSVC++ 2.0.

Win16 tools
-----------
If you are using MSVC 1.5 for your 16bit development tools on Chicago you
will need to update the linker.  The linker can be found in the \SDK\VCPATCH
directory on this CD.


New Printer Commdlgs
--------------------
Note there are new printer commdlgs in the SDK.  These include an 
updated File/Print and File/Page Setup dialogs.

WinHelp
=======
Known Problems:
+ Bubble help popup does not come up in the correct location.
+ fails to display Windows 95 SDK help from Dolphin
+ ALink macro duplicates topic titles
+ If a .CNT file containing a :Base command is :included in another .CNT file, 
  then none of the jumps that don't specify a filename will work
+ WinHelp: on-top status doesn't stick accross window jumps
+ Under a low memory condition, the 'What's this?' option comes up, but 
  clicking on it just makes it go away instead of bringing up popup, a 
  message indicating why the help can't come up needs to be added.
+ Context sensitive help for printer prop "Not Selected" is incomplete
+ Incorrect popup help message on printer property "printer memory tracking"
  item
+ Using context sensitive help in the 'Advanced Options' window of Control
  Panel 'System' applet will hang your system; do not use any context
  sensitive help in this window.
