			   WINDOWS 95
                       BETA RELEASE NOTES

TABLE OF CONTENTS
=================
GENERAL
SETUP
PLUG & PLAY
APPLETS
MS-DOS & WINDOWS APPLICATIONS
DISK TOOLS
DISKS & CDs
DISPLAY ADAPTERS & MONITORS
GAMES & NEW PROGRAMS
INBOX & MICROSOFT EXCHANGE
MICROSOFT FAX
MODEMS
MOUSE & KEYBOARD
MSN, THE MICROSOFT NETWORK 
MULTI-LANGUAGE SUPPORT
NETWORKS
PRINTING
WINDOWS 95 PEN SERVICES


GENERAL
=======
Dual booting using F4 is now turned on by default only if you install to 
a clean directory.  If you install to a clean directory, Setup will add 
BootMulti=1 to the [options] section of your MSDOS.SYS file (hidden text 
file in the root of your boot drive).

NOTE: There are known problems if you have configured your system for 
"F4/F8" dual boot between MS-DOS/Win 3.x and Windows 95, and then 
upgrade your Windows 95 directory to a newer version of Windows 95:  
Your Windows 3.x swapfile will show up as corrupted on your next boot 
into Win 3.x, and a number of files in your MS-DOS directory will be 
deleted (see section below on "Previous MS-DOS Files").  You can 
work-around the corrupt swapfile problem by setting up a working 
permanent swapfile in Windows 3.x, and then adding the following lines 
to the [386enh] section of your Windows 95 SYSTEM.INI file:

	PagingFile=<Win_3.x_PagingFile>  
	MinPagingFileSize=<Size_KB> 

Where:
	Win_3.x_PagingFile is usually C:\386SPART.PAR
	Size_KB is the size of Win_3.x_PagingFile divided by 1024
	

SETUP
=====
(Also read SETUP.TXT for additional details about Setup)

Beginning with Build 456, Setup will have a "strict" 
upgrade check.

Since the version of Windows 95 that you are testing is the 
"Upgrade" product, Setup will search the hard disk for existence of 
a qualifying upgrade product:

	Windows 3.0-3.11 
	Windows for Workgroups
	Windows 95
	Windows NT 
	OS/2

If none of these products are found on your hard disk,  Setup will 
prompt the user for the location of their previous OS.  At this 
point, the user can insert Disk 1 from any of these products 
(except Windows 95), and Setup will continue.  Otherwise, Setup will 
refuse to continue.

Note:  Microsoft will also be selling a "Full" Windows 95 
product that will install on machines that no operating system or 
only have MS-DOS.  This will sell in retail stores for a higher price 
than the "Upgrade" product.

Installing Windows 95
---------------------
Setup should be run from Windows 3.x, Windows for Workgroups 3.x, or 
Windows 95 (Beta 2 and higher).  Setup should be run from MS-DOS only 
if there is no working version of Windows on the machine.  

From the CD-ROM, run SETUP.EXE in the "WIN95" directory.

From floppy disks, run SETUP.EXE on disk 1.
Note that Windows 95 uses Microsoft's new Distribution Media Format 
(DMF) which allows more data to be stored on each disk.  Normal 
MS-DOS disk commands (COPY, DISKCOPY, etc.) will not work on 
disks 2 and above.  You can use the EXTRACT utility on disk 1 to 
extract files from DMF Disks, or to copy the .CAB files from the 
disks to your hard disk (type EXTRACT /? for instructions).

Installing Windows 95 over Windows NT 
-------------------------------------
If you are multi-booting MS-DOS and Windows NT, boot to MS-DOS, and
run Setup from either MS-DOS or Windows 3.x.  You will not be able to
install Windows 95 to a directory with a shared Windows 3.x/Windows 
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 your 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).

Installing Windows 95 over OS/2
-------------------------------
Setup will not run on OS/2.  You will need to boot to MS-DOS and run
Setup from the MS-DOS prompt.

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.

Installing Optional Components After Windows 95 is Installed
------------------------------------------------------------
Optional components can now be added/removed after Windows 95 is installed
without re-running Setup.  The "Add/Remove Programs" Control Panel has a
"Windows Setup" tab that will let you add and remove optional components from
inside Windows 95.  

Known Setup Problems
--------------------
- If Setup gets stuck while "Performing a routine check" at the 
  beginning of Setup, you can re-run Setup using with	the command 
  "Setup /is" to disable the system check.  See SETUP.TXT for details.

- Installing Windows 95 on a 4Mb or 386 machine from floppy disks may be very 
  slow, and you may see some screen repaint problems or spurious warnings
  that existing files on your machine are newer than the files in 
  Windows 95.  To avoid or workaround these problems:
     * Run Setup from inside of Windows 3.x or Windows for Workgroups.
       Avoid running Setup from MS-DOS--this will make all problems worse.
     * If you receive warnings about files on your system being newer than
       those on Windows 95, select to *replace* the existing files.
     * If you are running disk compression like DriveSpace or DoubleSpace,
       Setup may be very slow.  You might consider copying the files on the
       floppy disks to a temporary directory on your hard disk, and then
       running Setup from your hard disk.  To copy files from Disks 2-12, 
       you will need to use the EXTRACT command on Disk 1 to copy the 
       WIN95_xx.CAB files to your hard disk, since they are in Microsoft's
       new Distribution Media Format (DMF) and normal MS-DOS commands like 
       COPY and XCOPY won't work on these floppies.  
       To copy a .CAB file from a floppy disk to your hard disk, 
       use the following command:
		       EXTRACT /C A:WIN95_xx.CAB C:\<TempDir>
       where <TempDir> is the location of a temporary directory on your
       hard disk.

Previous MS-DOS Files
---------------------
If you upgrade over a previous version of Windows 3.x, Setup will
delete a number of files from your old MS-DOS directory to free
up disk space and remove utilities that have been replaced by
the Windows 95 versions in the Windows and Windows\Command folders.

The following files will be deleted from the old MS-DOS directory:
ansi.sys
attrib.exe
chkdsk.exe
choice.com
country.sys
debug.exe
defrag.exe
deltree.exe
diskcopy.com
display.sys
doskey.com
drvspace.bin
dblspace.bin
drvspace.exe
dblspace.exe
drvspace.sys
dblspace.sys
edit.com
edit.hlp
ega.cpi
fc.exe
fdisk.exe
find.exe
format.com
keyb.com
keyboard.sys
label.exe
mem.exe
mode.com
more.com
move.exe
mscdex.exe
nlsfunc.exe
scandisk.exe
scandisk.ini
share.exe
sort.exe
start.exe
subst.exe
sys.com
xcopy.exe
emm386.exe
help.com
help.hlp
msd.exe
networks.txt
os2.txt
ramdrive.sys
readme.txt
setver.exe
smartdrv.exe

Note: if you install Windows 95 to a new directory, these files will
not be deleted, so you will still be able to dual boot.  However, in that
case, files pertaining to DblSpace, DrvSpace, Defrag and ScanDisk will be
renamed and replaced with BAT files that tell you to run the Windows 95 version
of these utilities.  You will still be able to dual-boot, but you will
need to run these utilities from within Windows 95 (though you can still
run the Windows 95 version of SCANDISK.EXE from within MS-DOS 5 or higher).

ASSIGN, included with MS-DOS 5.0, functions in Windows 95's real mode but
not in Windows 95's protect mode.  In addition, ASSIGN has the following
anomaly:  ASSIGN A:=C: followed by a DIR A: will do a seek on the floppy
drive, but still display the directory information on drive C:  This is due
to the changes of the DIR command for Windows 95.  The Windows 95 version of
the SUBST command should be used in place of the ASSIGN command whenever
possible.


PLUG & PLAY
===========


3-Com Etherlink III 3C509B
---------------------------
Some 3-Com Etherlink III 3C509B Plug and Play ethernet adapters,
conflict with the port used to enumerate Plug and Play devices.
If you have one of these adapters and experience system hangs you
should change the IO configuration of the "IO read data port for ISA
Plag and Play enumerator" to 274h.
           

IBM Thinkpad models 750 (all 750 series except 750ce)
-----------------------------------------------------
A new BIOS is available from IBM's bulletin board at 919-517-0001, which
solves several problems with power management.


IBM Thinkpad models 755cd,cx,ce,cse,cdv (but not 755c)
------------------------------------------------------
There are several known problems with these machines which we are in the
process of resolving with IBM.
a) Mwave is lost if you have more than 8 megs of memory.
        - IBM is working on updated drivers. The 1.1 revision does not solve
          this problem.
b) Mwave is lost on a clean install of Win95.
        - This is by design, the Win 3.1 drivers are required to run the
          Mwave chip, and these are only preserved on an upgrade of an
          existing Windows directory.
c) Infrared port shows up with problems in Device Manager.
        - IBM is working on an updated Infrared VxD which resolves this
          problem.
d) Docking is not supported
        - IBM is working on fixes to their Plug & Play BIOS which will enable
          full Windows 95 Plug & Play, and Docking, support.
e) Power management problems with suspend/resume
        - If you have a BIOS date from 1994, these problems can usually be
          solved by upgrading to the latest Flash BIOS revision from 1995,
          which can be found on Compuserve, THINKPAD forum, or at the
          BBS number above.


IBM Thinkpad Dock II
--------------------
Users of the IBM Thinkpad Dock II must disable the BIOS for the Adaptec
1530P SCSI controller in the docking station prior to booting while
docked, or you will encounter repetitive hangs.  This controller works
fine in protected mode even without the BIOS enabled, so you should not
lose access to any SCSI devices as a result.

Steps to disable the BIOS:
  a) Boot while docked.
  b) Press Ctrl-A to enter the Adaptec SCSISelect utility.
  c) Choose "Configure/View Host Adapter Settings"
  d) Choose "Advanced Configuration Options"
  e) Set "Host Adapter BIOS" to "Disabled"

Press Esc to back out until asked to exit the utility, at which point
the machine will reboot.

An even superior solution is to disable the BIOS completely, which will
allow the adapter to run completely Plug and Play, which will allow its
resources to be allocated dynamically at Win95 startup.  However, this
requires changing a DIP switch inside the dock unit.  Refer to your Dock II
manual for details on disabling the SCSI adapter BIOS.

Micron M5-PI series
--------------------
BEFORE INSTALLING WINDOWS 95, users of Micron M5-PI series (P-60, P-66) 
need to be sure the BIOS read/write jumper(W22) is set to the read only 
position Setting up with this jumper in the read\write position may cause 
BIOS corruption during the Windows 95 installation. Contact Micron 
Technologies at (208) 465-3434 for more information.

NEC Versa M
AT&T Globalyst
---------------
Users of AT&T Globalyst and NEC Versa M must set the BIOS setting for 
PCMCIA Power to ENABLED before running the PC Card (PCMCIA) wizard to 
enable the Windows 95 PCMCIA support. The default on these notebooks is 
disabled. To set it to enabled, restart your PC and when the cursor changes 
to a rectangle hit the F1 key. When the BIOS configuration program is ready, 
select Power, then change PCMCIA Power from disabled to enabled and save 
these settings.

Winbook XP
-----------
There is a problem on the Winbook XP which could cause the keyboard
not to function properly. The workaround for this problem is to disable
Windows 95's power status polling. This can done be using the following
steps:
Open the System Control Panel and select the device manager tab.
Expand the system class by clicking on the plus sign. Double click on the
Advanced Power Management Support entry. Pick the settings tab and check
the box labeled Disable power status polling. Be sure to close down the
open control panel windows by clicking the OK buttons.

HP OmniBook
-----------
The Omnibook's PCMCIA controller is not supported in this beta. The
Windows 3.1 PCMCIA drivers should work fine with Windows 95.
The OmniBook also requires a special mouse driver for Windows.  Windows 95
Setup will preserve & use this when upgrading over Windows 3.1.  If
you installed Windows 95 into a new directory on an OmniBook, then
you must copy HP's OBMOUSE.DRV file into the Windows \system directory,
and change the following lines in SYSTEM.INI:

	[boot]
	mouse.drv=obmouse.drv

	[386Enh]
	mouse=*vmd

Zeos P-90 & P-100
----------------
The Zeos P-90 and P-100 machines have a bug in the BIOS that was
excerbated by a fix in Win95 for DOS extender support.  A work around
was introduced into Build 445 of Win95.  Builds between 438 and 444
might not boot on Zeos P-90 and P-100 machines.



Acer Acernotes
--------------
If you get a negative (low) tone when the PCMCIA card is inserted after 
activating the 32bit PCMCIA drivers. Remove the EMMExclude line from 
system.ini and the eXclude range from config.sys EMM386 line. If you're still
getting a low tone, open the PCMCIA applet in the control panel, select
global settings, uncheck "Automatic selection" and set the Start to 000D0000 
and the End to 000DFFFF as the valid range.  

Printing from the Device Manager
--------------------------------
When in Device Manager if you choose print "all devices and system summary", 
the device detection code **may** cause problems for DOS programs. The 
symptom is that when you try to run an MS-DOS program, it reports out of 
memory. Most machines do not show this behavior but to ensure you do not 
experience this problem, be sure to close all MS-DOS applications before 
printing this report.
 

BASE
====
- Mitsumi miniport: A new version of the Mitsumi miniport is rolled into
  the build.  If you find any problems with the Mitsumi CD, please report
  a bug with "MITSUMI" in the title.
- The NEC 4X SCSI CD has firmware bugs.  A workaround was put in the Adaptec
  miniport. 
- EZ-Drive, the disk management software, that ships with some of the more
  popular large IDE drives is now supported through the protect mode IDE
  driver.
- Trantor 358 and the 160 miniports were spiffed up for performance.  The
  Trantor 128, 130 and 338 miniports were moved to the WDL (and on default
  will be supported only through the real mode driver).
- The Syquest removable IDE cartridge is supported, if the user adds
  RemovableIDE=1 in SYSTEM.INI.  

APPLETS
=======
Backup and the Quickview files are NOT installed by default.  To
install these, use the Add/Remove Programs utility in the control panel.
Backup is under the Disk Tools heading and Quickview is under the
Accessories heading.

WordPad, Paint, Backup and HyperTerminal have been moved to their new
location under "\Program Files\Accessories" along with some of their
data files.  Start Menu shortcuts have been updated to point to the new
location; Shell/OLE behavior should not be affected.  Note that your
old HyperTerminal connection files have been moved to a folder
called "Old HyperTrm Folder (see release notes)" in your Windows
directory.

Wordpad, Known Problems:
- File/Print Preview may not accurately show the page layout

HyperTerminal, Known Problems:
- does not recognize when a PCMCIA modem is inserted if a session is open
- when receiving a file, does not know if disk is full

Backup, Known Problems:
- The backup applet does not work with all tape drives.  If you load the
  applet and get a message that your tape drive has not been detected, click
  on the help button to see a list of the tape drives which are supported.
- If a backup to tape moves less than 1.5 MB/min, you may have a conflict
  between the tape unit and your video card.  The work around is to start the
  backup operation and then open a full screen MS-DOS box until the operation
  has completed.
- If you turn 32 bit disk access off or boot into Safe Mode, Trakker tape
  drives will not work.  Accessing a CD ROM using a real mode driver turns
  32 bit disk access off.
- Making differential backup's is an advanced feature which we do not expect
  many novice or intermediate users to try.  To do this, please see the
  information in the help file for backup.

WinPopUp, Known Problems:
- You are unable to send messages to workgroups.
- If you are running an old version of WinPopUp with M8 you can generate a
  page fault.


Microsoft MS-DOS Utilities running under Windows 95
-----------------------------------------
The MS-DOS utilities that are installed into the \WINDOWS\COMMAND directory
have been enhanced to work with Windows 95.  If you find any reproducible
problems with these utilities please submit a bug report.

The RESTORE command from MS-DOS version 3.30 will not work with Windows 95.
Later releases of RESTORE will function correctly.



MS-DOS & WINDOWS APPLICATIONS
=============================

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.


MS-DOS Applications
-------------------
Your existing MS-DOS applications should run from inside Windows 95.  If you
experience severe problems with an MS-DOS program you can set it up to run
in an MS-DOS environment.
1) Create a shortcut to the MS-DOS program
2) Right click on the shortcut icon and select Properties.
3) When the property pages come up, go to the Program page.
4) On the Program page choose the Advanced... button.
5) Select the MS-DOS Mode check box.

When you run this application it will force the GUI portion of Windows 95 to
shut down and will run the program in an MS-DOS environment.   Please note
that you will not have access to devices that require protect mode drivers.


Notes on Specific DOS & Windows Applications
--------------------------------------------
Before running Norton Backup for DOS under Windows 95 you need to delete
the existing PIF.   Win95 requires new PIF settings but can only do this
if the old PIF is removed.   Simply delete the file NBACKUP.PIF and then
run Norton Backup.

Quickbooks - there is a problem in this release if you close Quickbooks
while it is minimized and before you have registered the product.   If you
do this it will not run correctly the next time it is started.  Before you
minimize Quickbooks be sure to register the product.  If you encounter this
problem you should delete the QBW.INI file in your Quickbooks directory.
This will allow Quickbooks to start again.

Running Dial-Up networking along with the Microsoft client for Netware
may cause some problems with Pagemaker 5.0.   If you experience problems
you may need to disable Dial-Up networking.

If you are running The 7th Guest with a Pro Audio Spectrum 16 sound card
you will either need to enable and use the Sound Blaster compatibility mode,
or configure your Pro Audio Spectrum card to IRQ 5 and DMA 3.

XtraDrive requires SETVER to be loaded in order to function correctly.  Make
sure that SETVER is loaded before XTRADRV.SYS. 

Microsoft Office setup tries to find a CONFIG.SYS file if none is present.
This will cause additional disk activity, but Office should not affect the
install process.

Paint Shop Pro v2.0 will not be able to draw capture areas inside of 32-bit
applications.   16-bit applications do not see mouse movements over 32-bit
applications.   All other mouse capture methods will still work, and this
will continue to work with 16-bit applications.

PCTOOLS 7-9
Shortcuts will not be created during PCTOOLS installion when the Windows 95
UI is being used.  To create shortcuts after the Installation of PCTOOLS
follow these steps:
1) Choose Run from the Windows 95 Start Menu.
2) Type "CPSDOS.GRP" and press ENTER
This will update the Windows 95's Programs Folder with the information out
of the PCTOOLS group file.  For the created shortcuts to function, the
PCTOOLS installation directory must be on the PATH.

MSBACKUP/Norton Backup for MS-DOS:
There is currently a bug with either of these MS-DOS based backup tools
that causes the user to have to reconfigure their their settings each
time they re-enter Windows 95.  To work around it, you  simply need to
reconfigure and run the backup/restore test.  We will address this
problem for the final release.

Magic Carpet and this release - Currently, there are two known problems
running this game on Windows 95.  First, pressing the ENTER key repeatedly 
causes the game to exit (similar to the  SHIFT+Q command).  Also, on shut-down
the games sometimes faults, requiring the user to "window" the MS-DOS
box (ALT+ENTER), and click on the "X" button on the toolbar in order to
close the MS-DOS box.  Beyond this, have fun!

Because the JOIN command is not supported under Windows you will need to
run the Ultima VI/Wing Commander CD from your hard drive.  The proceedure
for doing this is outlined below and in the documentation for this CD game.
You will need to copy all programs to your hard drive and then run install
to configure the program.  You will need approximately 13 MB of space for
Wing Commander and 5 MB of space for Ultima VI.
** To copy all files for either Wing Commander or Ultima VI use the Windows
   Explorer program:
     1. Click on Start, Programs, Explorer.
     2. Double click on your cd drive and you will see two folders; one for
        Wing Commander, one for Ultima VI.
     3. Click and drag either folder toward the C drive or any other hard
        drive to which you want to copy the program information.  The
        contents of that file including directories and subdirectories will
        be copied to your drive.
     4. You now need to run the install program from your hard drive in order
        to configure the proper video and sound options for the game.

If you see the message "Unable to access network(116)" while running
QuarkXPress v3.3, this usually indicates that you do not have a valid
network installation.  We have seen this internally when just the
DIAL-UP/IPX components are loaded.  When the Win95 network components
are installed this message goes away.

Also, Quark Xpress 3.3 will typically return an out of memory error regardless
of the amount of memory available to a given machine. A patch, to upgrade
Quark Xpress 3.3 to 3.31, can be downloaded from Compuserve or can be provided
by Quark.  Quark Xpress 3.31 functions on Windows 95.  Also, When installing
Quark Xpress on Windows 95, Xpress's install program may stop at 99% complete
on some systems.  Selecting the Continue button finishes the install process.

Microsoft Mail 3.2 and Microsoft Schedule+ - Microsoft Exchange is an upgrade
to Microsoft Mail v3.2 and it replaces many of the older components.  For this
reason Microsoft Mail v3.2 will not function if you have installed Microsoft
Exchange.  Also, the existing version of Microsoft Schedule+ will not be
able to use Exchange to send email.

Any fonts that are not True Type (driver fonts and Adobe ATM fonts)
cannot be printed to printer drivers that are Windows version 1.0.
With a 1.0 printer driver selected only True Type fonts will be
displayed in the font list. WinFax Pro 4.0 is the only known shipping
application with a Windows 1.0 printer driver.

Some existing applications cannot handle the case where a UNC path name is
used to install the application (Lotus Notes is an example).   For these
applications you should use a redirected drive letter instead of a UNC
path.

Windows 3.1 Shell Replacements - Most Windows 3.1 shell replacements
(such as Norton Desktop, PC Tools Desktop, Tabworks, etc.) will still
run on Windows 95 but with many limitations.  You will need to upgrade
to a version that was designed to run on Windows 95.

The setup program for PC Tools for DOS version 7-9 may not create
shortcuts when installed under Windows 95.  Because of changes to the
Windows 95 file system, these disk utilities will not work correctly
with long file names.   You should contact Symantec for information
about purchasing disk utilities that were designed for Windows 95.

Anti-Virus Software - Existing Anti-Virus software should be able
to detect, but not always clean viruses while running on Windows 95.
This depends on where the virus was found and how the program chose to
clean it.  If you run into problems with your Anti-Virus software
you should contact the vendor for information on new releases that
are designed to run on Windows 95.

McAfee - VirusScan does not work properly with Windows 95 for the 
following reasons:
1. The VShield Win16 app cannot "see" the DOS-level TSR, because 
of problems going across the DPMI interface.
2. The TSR interface is not a sufficient protection against viruses under 
Win95. McAfee is working on a VxD implementation compatible with the
Windows 95 architecture.
Please contact McAfee if you need further information about their new
product at the following locations:
McAfee BBS:(408) 988-4004 and McAfee direct line: Call (408) 988-3832

If you try to run Peachtree Accounting version 3.0 under Windows 95 and
see a divide-by-zero error message, you will need to obtain a patched
version from Peachtree Software.

If you run Adobe Photoshop and see an error message saying "Unable to
create font database," or if you see a General Protection Fault error
message, you will need to upgrade to the latest version of Photoshop.
For more information, Contact Adobe at (800) 833-6687.

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

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 if necessary.
Use caution with these commands because these old utilities can cause you
to lose long file names.

Stacker 4.0 - Like older DblSpace & DrvSpace, Stacker 4.0 is not aware of
long file names.  If Stacker 4.0 already exists in the system, then Windows 95
can be installed on top of it without problems.  If Stacker 4.0 is being
installed on top of an existing Windows 95 system, then long file names will
be lost in operations such as compress-in-place.  Hence before installing
Stacker 4.0 on top of Windows 95 and compressing drives, please use some utility
like LFNBK to save the long file names on the media, install Stacker 4.0,
then run the utility again to restore long file names.

Freehand will not function with NetWare on this beta release of Windows 95.
If you try to run Freehand with NetWare you may see a General Protection
Fault.   Windows 95 will work around these problems for the final release.

Blake Stone Aliens of Gold - This game requires COMMAND.COM to be present
while it is running.   You may see errors if you try to launch it directly
from the Windows 95 shell.   Instead, you should start an MS-DOS prompt
and launch the game from there.

Timeline - Running existing macros may not work in this release.  Timeline
tries to use window handles that it has already freed and may cause an
error.  Contact the vendor for information on program updates.

The Print Manager features of Office Accelerator will not load using the
Office Accelerator menus.   Instead, you should configure your printers
using the Start button-> Settings -> Printers.

Borland BC++ 4.5 may experience problems running under Windows 95 if you
do not have an AUTOEXEC.BAT file.   Creating an empty AUTOEXEC.BAT file
should fix this.

Nickelodeon Director's Lab may display some error messages at the end of
its setup program. You will need to close the setup program manually. This
does no harm because it has already finished installing Director's Lab.
After the setup program has added the new shortcuts, you may see a message
that says, "Setup Message: Script or DLL has been corrupted. Unable to load
dialog template: 'mscuistf.dll: 2'." If this message appears, carry out the
following procedure.
 - To close the Nickelodeon Director's Lab setup program
	1) Print or write down these instructions.
	2) Press CTRL+ALT+DEL.
	3) In the Close Program dialog box, click the Director's Lab setup
		program, and then click End Task.
	This closes the setup program and ends the error messages.


Running the Aris MPC Wizard with the Windows 95 display using more than
256 colors may cause a General Protection Fault. If this occurs, you will
need to run this program using 256 colors or less.

Micrologic TrueEffects for Windows does not function correctly under
Windows 95 because it uses Windows 3.1 internal system information. To
resolve this problem, contact Micrologic for an updated version of
TrueEffects.

Wired for Sound version 1.0 does not function correctly with Windows 95.
It was designed to work under Windows 3.1 and is too closely tied to that
operating system to function correctly with Windows 95. For information
about a version of this program that is designed for Windows 95, contact
your software vendor.

The WorldView CD-ROM by Aris Entertainment includes a modified version of
Microsoft Video for Windows (VFW). Because this modified version was not
configured properly, it may erroneously report that a device driver is
corrupted and may advise you to call Product Support Services.  If you are
following the instructions in the READWRLD.TXT file, you may see an error
message indicating that the source file or destination disk may be corrupted.
If you receive such an error message, carry out the following procedure.
If you received a message that says the ICCVID.DRV file is corrupted
	1) Select the following text (from "command" through "/y").
		command /c copy x:\vfwsetup\iccvid.drv %windir%\system /y
	2) Copy the selected text by pressing CTRL+C.
	3) Click the Start button, and then click Run.
	4) Paste the text you selected in step 1 by pressing CTRL+V
	5) Select the "X" in the text you pasted, and then type the letter
		of your CD-ROM drive.
	6) Click OK.
	7) Reinstall Video for Windows by following the instructions in the
		READWRLD.TXT file.

ATM fonts will not show up in the font list when some printer drivers for
fax applications are selected as the default printer. Known examples are
WinFax (all versions), FaxWorks, and older Quick Link 2 versions.  A
substitute TrueType font will be used instead.

Bloodnet will only work when the DMA channel is set to 7 if you are using
the Pro Audio Spectrum sound card.  The game tries to reconfigure the sound
device to DMA 7 automatically.  This will not be tolerated by the VxD.
 - A few solutions:
	1) Use Sound Blaster compatible mode on your PAS.
	2) Reconfigure the PAS device to DMA 7.
	3) Use MS-DOS mode.

Compel from Asymetrix - The setup program for this application may not
create shortcuts correctly in this release.

Lotus Notes Windows Client 3.2 - Configuring Netbios in Notes. If you are
using the netbios interface over ipx and the netbeui protocol stacks then it
is necessary to configure the port of for Netbios using the unit number that
properly corresponds to that protocol. Default number for the first Netbios
protocol is first set to 0, then any additional netbios interface will start
at port 7 through 1. It is likely that netbios will use 7 or 6 if Netbeui is
using 0. Changes must be done in the Lotus Notes Windows Client under the menu Tools-Setup-Ports. 

Cheyenne ARCSOLO 3.02 - Under Windows 95, ARCSOLO 3.02 cannot connect to the
network network drives mapped through the Client for Netware Networks (NWREDIR.VXD)and Client for Microsoft Networks (VREDIR) either when the drives are already mapped. To workaround this problem, you need to add to
SYSTEM.INI the following line: 

					[boot]
					network.drv=commctrl.dll  

NB: Any DLL will work; this is a Win16 DLL in Win95. Once there, network drives are present and can be used in backups.

XTree gold - Central Point. When copying a file from one directory to
another on a Novell 3.1 server causes the file's attributes to change.
Same behavior going from the NW3.1 server to the local hard drive still
changes the file attribs and date but leaves the size correct. 
Central Point has released a patch for Xtree Gold that fixes the problem.
Please contact your local Central Point office, or get the file from the
Central Point Forum on Compuserve, BBS or WWW.


The game Cyberwar will need to run in MS-DOS mode in this release unless
you are using a MIDI device for sound.   If you are using a MIDI device
then the game should run fine in a DOS VM (DOS Box).


Quick Application status for this release
------------------------------------------------
* If you see a fault in Harpoon II you may need to run it in MS-DOS mode.
* The game Lunicus will not function correctly.
* Microsoft Fortran PowerStation will not run.
* Quicken 8 for DOS may not be able to print to a network printer.
* SmallTalk V may fault if the Class Browser is launched.
* SPSS for Windows v6.1 may hang if launched by clicking on a sample chart.
* Some problems have been reported running Adobe TypeAlign with this release.
* Printed graphics may be distorted in Avery Label Pro.
* CarbonCopy for Windows v1.0 will not run.
* Double Tools should not be installed over Windows 95.
* If you see a fault running Theme Park you need to run it in MS-DOS mode.


Memory Managers
---------------
The following notes are provided as a troubleshooting guide for using
Windows 95 with 3rd party memory managers.  If you are familiar with
IBM compatible PCs you may want to try the following steps before you
call for support.

** 386MAX 7.0 **
Windows 95 removes the following lines from CONFIG.SYS during Setup:

Device=\386MAX\ExtraDOS.max pro=\386MAX\ExtraDOS.PRO
Install=\386MAX\ExtraDOS.max

After Setup, If Windows 95 fails to Start:
1) Refer to the MANUAL/README.TXT (packaged with 386MAX) about Specific
   Software and Hardware incompatibilities with the 386MAX software.
2) Run MAXIMIZE program and follow these steps:
   a) After MAXIMIZE reboots the sytstem for the first time, Press F8
      when you see the "Starting Windows 95" message.  This will bring
      up a boot option menu.
   b) Select "Safe Mode command prompt only" from the menu.  This will
      drop you to the command prompt.
   c) Remove the Following lines from CONFIG.SYS using a text editor such
      as EDIT.COM.
      - Device=\386MAX\ExtraDOS.max pro=\386MAX\ExtraDOS.PRO
      - Install=\386MAX\ExtraDOS.max
   d) Remove the Following lines from the file called 386MAX.PRO which
      will be located in the directory where 386MAX is installed.
      - Line Beginning with "PRGREG" (If it Exists)
      - Line Beginning with "HPDAREG" (If it Exists)
      - Line Beginning with "STACKREG" (If it Exists)
      - Line Beginning with "NOWIN30" (If it Exists)
   e) REBOOT Machine. MAXIMIZE should Continue Setting Up.
   f) Eventually, a dialog saying "ExtraDOS Error" should appear. Choose OK.
      When the MAXIMIZE program finishes, Windows 95 should function
      correctly.
-----------------------------------------------

** BLUEMAX 7.0 **
Currently, Windows 95 removes these lines from CONFIG.SYS during Setup:

Device=\BlueMAX\ExtraDOS.max pro=\BLUEMAX\ExtraDOS.PRO
Install=\BlueMAX\ExtraDOS.max


After Setup, If Windows 95 fails to Start:

1) Refer to the MANUAL/README.TXT (packaged with BLUEMAX) about Specific
   Software and Hardware incompatibilities with the BLUEMAX software.
2) Run MAXIMIZE program. And Follow these steps:
   a) After First Boot of MAXIMIZE, Press F8 When "Starting Windows 95"
      appears.
   b) Select "Safe Mode command prompt only" from Menu.
   c) Remove the Following lines from CONFIG.SYS
      - Device=\BlueMAX\ExtraDOS.max pro=\BLUEMAX\ExtraDOS.PRO
      - Install=\BlueMAX\ExtraDOS.max
   d) Remove the following lines from BlueMAX.PRO located in the directory
      where BlueMAX is installed.
      - Line Beginning with "PRGREG" (If it Exists)
      - Line Beginning with "HPDAREG" (If it Exists)
      - Line Beginning with "STACKREG" (If it Exists)
      - Line Beginning with "NOWIN30" (If it Exists)
   e) REBOOT Machine. MAXIMIZE should Continue Setting Up.
   f) Eventually, a dialog saying "ExtraDOS Error" should appear. Choose OK.
-----------------------------------------------

** NETROOM version 3 **
Before setting up Windows 95, verify that CACHECLK is not being loaded in
AUTOEXEC.BAT.  Currently, Windows 95 Setup will fail with CACHECLK loaded.

After Setup, If Windows 95 fails to Start:
1) Refer to the MANUAL/README.TXT (packaged with Netroom) about Specific
   Software and Hardware incompatibilities with the NETROOM software.
2) Run CUSTOMIZE program.
-----------------------------------------------

** QEMM 7.01 - 7.5 **
Currently, Windows 95 removes these drivers from CONFIG.SYS during Setup:

DOSDATA.SYS
DOS-UP.SYS
ST-DBL.SYS   (7.01-7.04)
ST-DSPC.SYS  (7.5)

After Setup, If Windows 95 fails to Start:

1) Refer to MANUAL/TECHNOTES/README.TXT (packaged with QEMM) about Specific
   Software and Hardware incompatibilities with QEMM software.
2) Check Stealthing Options.  Try changing ST:M to ST:F on QEMM386.SYS
   line in Config.sys and reboot.  If that doesn't work, try removing the
   ST:M or ST:F completely from the QEMM386.SYS line in Config.sys and
   reboot.
3) Run QSETUP and turn off DOS-UP and Stealthing Options (See above).
   QSETUP will recommend running OPTIMIZE.
4) Run OPTIMIZE program.  (Note: If DOS-UP or Stealthing are enabled in
   QSETUP, then OPTIMIZE will add them to CONFIG.SYS.  Currently,
   Windows 95 may fail to start with DOSDATA.SYS  and DOS-UP.SYS installed
   in CONFIG.SYS.)

DOSDATA.SYS, a portion of the DOS-UP features of QEMM, causes Windows 95's
multi-boot feature to attempt to start Windows 95 even after the "Previous
version of DOS" option has been selected.  Pressing F4 during the second
appearance of "Starting Windows 95..." will bybass this situation.  To
correct this problem permentantly, DOSDATA.SYS and DOS-UP.SYS should be
manually removed from CONFIG.DOS.


DISK TOOLS
==========
 - Do not use DriveSpace to compress a Gateway 2000 Colorbook.
 - Do not use Disk Defragmenter on drives compressed with SuperStore 2.0.
 - If you create a Briefcase and then compress a drive that contains files to
   which it refers, the Briefcase's association to the files will be lost.
   The files will still exist, but you will need to reassociate them with the
   Briefcase.
 - If you use INTERLNK, do not use ScanDisk, DriveSpace or the Disk Defrag-
   menter to operate on a drive on a remote machine.


DISKS & CDs
===========
1) The New Media Bus Toaster is not completely compatible with the drivers
from Adaptec.  Hence it will be supported only through real mode drivers in
this release.
2) Older versions of the Bus Logic cards on PCI machines will also be
supported only through real mode drivers in this release.  This applies
to Fab Rev A of the card only.
3) The NEC 260GW ATAPI CD-ROM that shipped with older Gateways is now
supported through protect mode drivers.  All functionality for this drive
is now available.
4) Almost all protect mode support for disk and CD has been tweaked for
performance and/or have taken bug fixes.
   

DISPLAY ADAPTERS & MONITORS
===========================

Monitor type
------------
If Windows 95 does not contain your exact monitor type, select
one of the Standard Types instead.  This will not adversely
affect the performance or quality of Windows 95 display output.

Refresh rates
------------
Selecting your monitor type in the Windows 95 Display control panel 
does not affect the refresh rate used by your display adapter.  
To adjust this, you must specify your monitor type in an adapter
setup program supplied by your display adapter or PC manufacturer. 
Some utilities must be run in AUTOEXEC.BAT. On some PCs, monitor
type is set in BIOS configuration programs.  Examples of utilities 
from adapter manufacturers include:

  ATI                   INSTALL.EXE
  Cirrus Logic          MONTYPE.EXE, CLMODE.EXE, WINMODE.EXE
  Diamond Stealth       STLMODE.EXE
  Diamond Stealth 64    S64MODE.EXE
  Matrox                \MGA\SETUP\SETUP.EXE
  Tseng Labs            VMODE.EXE
  Western Digital       VGAMODE.EXE

Color cursors
-------------
Color cursors require a Windows 95 version display driver
running at 256 or more colors.  They are not supported for
the following display types in this release: ATI Ultra (mach8), 
Chips & Technologies, XGA.

Correcting display problems
---------------------------
In general, many display related problems can be corrected using 
the Graphics button on the Performance page of the System control 
panel.  The Advanced Graphics Settings window applies to graphics 
accelerators running with 256 or more colors.  Try changing these 
settings before reverting to 640x480 16 color mode to work around 
a problem.  See below for problems & workarounds for specific 
display types.  If you do not know what display type Windows 95
is using on your computer, open the Display control panel, 
Settings page, and click the Change Display Type button.

Myst & other entertainment programs
-----------------------------------
Moving the mouse may cause movies & graphics to appear in wrong 
places on the screen in programs which use QuickTime.
Possible workarounds:

 1) Change to black & white pointers in the Mouse control panel.
    Also, do not use Mouse Trails.

 2) Add "optimize=driver" to the [Video] section of the QTW.INI
    file in your Windows directory.  This may cause slower performance.

PCI display adapters
--------------------
Screen resolution may revert to 640x480 when Setup starts Windows 95 
for the first time.  Resolution should return to your usual settings 
in subsequent sessions.

Appian Renegade
---------------
Setup will install the VGA driver for these adapters.  Windows 3.1 
Renegade drivers can be used with Windows 95, but the Device Bitmaps
option must be turned off for proper operation.

ATI mach8/32/64
---------------
Your adapter must be configured correctly using the ATI INSTALL.EXE 
program in order for Windows 95 to be able to use high-res modes properly.  
Correct setting of your monitor type is especially important.  Otherwise, 
high-resolution modes may not be available, or your computer may crash
attempting to switch to them.

Chips & Technologies
--------------------
This driver is not installed by default on some laptops, incl. 
Zenith 433. This can be corrected in the Display control panel
"Change Display Type" dialog.

Compaq QVision
--------------
Color cursor fragments may be left on-screen.  If this happens,
select black & white pointers in the Mouse control panel.

Diamond Stealth 32
------------------                                            
On some adapters, 1024x768 with "High Color (16 bit)" palette may not 
work due to a video BIOS problem.  This will be corrected in a driver 
update that you will be able to download from the CompuServe forum, or 
receive by contacting your beta support team or contacting your local 
subsidiary as appropriate.

Diamond Viper
-------------
Windows 95 does not have a built in driver for Diamond Viper.
Setup will preserve and use drivers already installed when
upgrading over Windows 3.1.  If you do not upgrade, Setup
will install the VGA driver.

To install Diamond's Windows 3.1 drivers into Windows 95, run the Viper
setup program to copy driver files into Windows 95, and use 
the Viper control panel icon to select resolution and color 
settings.

Check the \Drivers\Display directory of the Windows 95 CD-ROM and the 
CompuServe forum for Windows 95 Viper driver updates, or contact your beta 
support team or your local subsidiary as appropriate.

IBM ThinkPad
------------
In order to run resolutions above 640x480, you must configure your 
ThinkPad correctly.  Check the ThinkPad utilities supplied by IBM, 
usually located in the Start menu.  Also, some older ThinkPad models 
require that the IBMVESA.COM driver be loaded in AUTOEXEC.BAT in 
order for 256 color modes to work.

Matrox MGA
----------
For proper operation, adapter & monitor settings must be correct in
the Matrox setup utility, usually located on your hard disk under
\MGA\SETUP.  Hanging during start-up may be caused by a conflict 
with a network adapter.  Desktop pattern & non-TrueType fonts may 
appear incorrect in high-resolution 16 and 32-bit modes.

Number Nine GXE (S3 928)
------------------------
If the computer hangs periodically, change the performance level
to "Basic accelerator functions" in the Advanced Graphics settings
dialog of the System control panel.

S3 display adapters
-------------------
S3 adapters conflict with COM4 ports and modems.  If you have modem
problems with this configuration, change your modem to a different 
COM port.  Certain S3 display problems may be corrected by adding
the following lines to the [display] section of the SYSTEM.INI file:
  
  Polygon=0        - For problems w/ line & shape outline appearance
  HighColor=15     - For color problems with "High Color (16 bit)"
  TrueColor=24     - For color problems with "True Color (32 bit)"
  Refresh_Rate=70  - For better refresh rate; can also use 56, 60, or 72

Sigma Designs Legend
--------------------
Full-screen MS-DOS programs may not appear correctly.  Run these 
programs in a window to work around the problem.

Video Logic 928Movie
---------------------
The line "928Movie=1" must be added to the [display] section of
SYSTEM.INI to allow "High Color (16 bit)" color palette.

Western Digital
---------------
On some laptops, the mouse cursor may change to a wide band of colored 
dots when switching from an MS-DOS prompt or application.  To correct
this, switch to & from the DOS program again.

GAMES & NEW PROGRAMS
==========================

Hover!
---------------
CD-ROM releases of Windows 95 now contain  Hover!--Microsoft's futuristic 
hovercraft-based capture the flag action game.  
To run Hover!
   1. Open the My Computer icon
   2. Open the CD-ROM drive icon
   3. Open the Funstuff folder
   4. Open the Hover! folder
   5. Double-click on the Hover! icon

To get started, follow easy-to-use instructions in the Help menu.  
Set your skill level and control support and you are ready to go.  

Your test version includes the wildest mazes on three worlds...Neon, Castle and Sewer. 
The goal is to weave your hovercraft through zany mazes and collect all of  the blue
flags before your computer drone opponents collect your red flags.  
As you progress through the each level of game play you will be rewarded with points.

However, making it to the top of the scoreboard is not as easy as it seems.  
You will discover many obstacles in your path including floor traps that spin, 
change direction and hold on to hovercraft.  
There are also ramming hovercrafts that claim you as the target!

Of course, in Hover! you are not completely defenseless.  You will find a
variety of ingenious items to help you out-run and out-maneuver 
opposing crafts and obstacles:

  --Springs allow you jump over traps or on to high steps, 
  --Walls can be set behind you to block oncoming crafts,
  --Cloaks make you invisible to your opponents.

Microsoft Exposition
---------------
CD-ROM releases of Windows 95 now contain MS Exposition - a fun and
exciting way to find out more about products from Microsoft..

MS Exposition gives you information on product features, system
requirements, and even allows you to see cool demos of the latest
Microsoft products.

To run MS Exposition:
   From the Welcome Screen:
   1. Click the Microsoft Products button
   2. You will be prompted to insert your Windows 95 CD - make sure
      it contains build 440 or higher.
   From the Windows 95 CD:
   1. Insert your Windows 95 CD into your CD-ROM drive
   2. Open My Computer
   3. Open the icon for your CD-ROM drive
   4. Open the "CDExpo" folder
   5. Run the program called "Catalog.exe"

MS Exposition provides you with an easy-to-use electronic catalog.  To
see the products included with this beta version of Exposition, click the
button labeled 'Products'. Then, choose a category and click on the
product you want to see.

NOTES:
1) The current test version of the MS Exposition catalog only has
entries for Microsoft Golf and Microsoft Dangerous Creatures.  Look
for more product previews in future beta CDs.
2) Phone numbers for local retailers are currently unavailable.

INBOX & MICROSOFT EXCHANGE
==========================
The Microsoft Exchange desktop icon has been replaced with an Inbox icon  
that takes you to your Microsoft Exchange Inbox.

SPECIAL BUILD NOTES

None.
 
WHAT IS MICROSOFT EXCHANGE? 
 
Microsoft Exchange enables you to send and receive e-mail, faxes, and documents 
in messages. It also provides rich viewing of the objects you store in it.  Information 
services that can be used with this beta of Windows 95 include Microsoft Mail,  
At Work Fax, CompuServe, and The Microsoft Network.  Note that a Microsoft  
Mail postoffice is included in this version of Windows 95. See "Creating and Using  
a Microsoft Mail Workgroup Postoffice" in EXCHANGE.DOC  
(see "More Information" below). 
 
MINIMUM HARDWARE REQUIREMENTS 
 
Microsoft Exchange runs on the minimum hardware platform for Windows 95. 
However, it is recommended that you have at least 6 megabytes (MB) of RAM for good 
performance in this beta. 
 
In addition, computers using Microsoft Exchange in this beta should have 
at least 7 MB of hard disk space available for the swap file. 
 
USING MICROSOFT EXCHANGE WITH MICROSOFT SCHEDULE+ 1.0 
 
Microsoft Exchange is designed to work with Schedule+ 2.0, which may not be 
available yet.  When Microsoft Exchange is installed, it will partially 
disable Schedule+ 1.0.  You will still be able to use Schedule+ 1.0 in 
standalone mode, but you will not be able to send or receive meeting 
requests.  You will see an error message when starting Schedule+ 1.0 that 
notifies you that the mail spooler cannot be started.  Click Yes to continue,  
and Schedule+ 1.0 will continue to be installed. 
 
Schedule+ is disabled by changing MAILSPL.EXE to MAILSPL.BAK 
and by putting a StartupOffline=1 line into SCHDPLUS.INI. 
 
Note:  There is no message warning users that these changes are made. 
 
USING MICROSOFT EXCHANGE WITH MICROSOFT MAIL 
 
Microsoft Exchange is designed to replace the Microsoft Mail application that 
comes with Windows for Workgroups and Microsoft Mail version 3.x. 
After installing Microsoft Exchange you will no longer be able to run the 
older Microsoft Mail application, but you will be able to use Microsoft 
Exchange to send and receive messages. 
 
UPGRADING FROM WINDOWS 95 M8 OR LATER 

You can install Microsoft Exchange with Windows 95 Final Beta over an 
existing Windows 95 setup.  

Toolbar buttons may be lost when you upgrade.  To restore the default toolbar
settings, select "Customize Toolbar" from the Tools menu, and click "Reset".
 
USING MICROSOFT EXCHANGE WITH WINDOWS 95 M8 MICROSOFT EXCHANGE 
 
There is NO interoperability between M8 and the 456 releases.  You cannot 
send or receive messages to or from mismatched Windows 95 releases.  Upgrade all M8 
Microsoft Exchange users simultaneously to Microsoft Exchange 456. 
 
INSTALLATION 
 
Microsoft Exchange is not installed on Windows 95 by default.  To install 
Microsoft Exchange, choose the Custom Setup option when running Setup.  When 
you are prompted with a list of components, you must select Microsoft 
Exchange from the list. 
 
You can also install Microsoft Exchange after you have completed installation 
of Windows 95 by using the Add/Remove Programs control panel. You must 
shut down and restart Windows 95 after doing this. 
 
When you install Windows 95 or use Microsoft Exchange for the first time, the  
Microsoft Exchange Setup Wizard will be run. The Wizard is also run each  
time you add a new profile in the Microsoft Exchange Profiles control panel. 

MORE INFORMATION 
 
For more information, see EXCHANGE.TXT in the DOCS directory of the 
CD-ROM. It is also found in the DOCS directory of floppy disk #1. 


MICROSOFT FAX
=============

1.  For the Network Fax support to operate properly, all clients and servers
must be running the same pre-release version of Windows 95 and must be running 
build 447 or greater.

2. While fax is in automatic answer mode, no 16-bit application will be able 
to use the modem.  To let a 16-bit application use the modem, click on the 
telephone icon near the clock in the Taskbar, choose Modem Properties from the 
Options menu, and put fax in Don't Answer mode.

3.  CAS modems are not supported.

4.  Do not manually change any of the printer spool settings on the
properties sheet or the Microsoft Fax printer.  

5.  Microsoft Fax is recommended only for machines with more than 8Mb of
memory in this release.   

6.  Running the Fax Cover Page Editor or the New Fax Wizard on a Server
Based Setup installation will not work.  To work around this problem, change
the path on of the shortcut or menu item to a fully qualified path, including
the drive letter, to the location of the shared installation and copy the
cover page templates (*.CPE files) to your local Windows directory.


MODEMS
======

Modems Control Panel
--------------------
In order to use your modem with built-in communications features of
Windows 95, including HyperTerminal, Microsoft Network, and Dial-Up
Networking, your modem must be configured in the Modems control panel.

Settings made in the Modems control panel do not affect modem operation
in programs designed for MS-DOS or Windows 3.1.

Modem Detection
---------------
If the Modems control panel detects your modem as "Standard modem",
or incorrectly detects its make and model, you may use the "Change" button
in the Install New Modem wizard to make a different selection.  Use
care, however, since manually selecting an incorrect type may cause
your modem not to work with Windows 95 communications features.
If this happens, remove the modem in the control panel, and add it
back as one of the Standard modem types.

When configured for "Standard Modem", Windows 95 will use your modem
with its factory default settings.  The modem will make optimal 
high-speed connections with Windows 95 communications features. 
However, you will not be able to adjust some of the modem's
settings, such as speaker volume, cellular protocols, etc.

Racal modems
------------
Do not use detection in the Install New Modem wizard if you have
a Racal modem.  Select "Don't detect my modem", and pick one of
the Standard modem types.  If you have already run detection and
your modem is not responding, turn it off and then on again.

Minitel (France)
----------------
Some modems may not be able to connect to French Minitel in
HyperTerminal using the Windows 95 default settings.  To correct 
this, an extra command may be needed in the "Extra Settings" field
of the Advanced Settings dialog of the modem's property sheet.
Check your modem manual for the command that will enable your
modem to connect in V.23 modulation to Minitel, and add this to
the Extra Settings field.


MOUSE & KEYBOARD
================

Microsoft Mouse & BallPoint:  GROWSTUB errors
---------------------------------------------
If you were using the Microsoft Mouse Manager with Windows 3.1,
Windows 95 Setup will update the POINTER.EXE and POINTER.DLL files
in the Mouse directory of your hard disk.  If these files are not
updated correctly, then you may experience errors in module GROWSTUB.
If this happens, make sure that the POINTER files were copied properly
by Setup.  They may have been copied to the Windows 95 directory
instead of your Mouse directory.

Logitech Mouse
--------------
The Windows 95 Logitech driver supports Logitech MouseWare features.
Do not install Logitech drivers for Windows 3.1 into Windows 95.
If this happens, use the Mouse control panel to change back to
the Windows 95 Logitech drivers.

Mouse Systems / Genius
----------------------
Windows 95 does not have built in drivers for Mouse Systems or
Genius 3-button mice.  The "Standard mouse" type will work with
these devices in their 2-button mode.  Driver updates are available
in the \Drivers\Mouse directory of the Windows 95 CD-ROM, or on
the CompuServe forum, or contact your beta support team or your 
local subsidiary as appropriate.

Microsoft Natural Keyboards
---------------------------
Windows 95 has built -in support for your Microsoft Natural Keyboard.
You will find your Windows logo keys will have added functionality
under the new operating system (including launching of the Start
Menu when pressing either Windows logo keys).

IntelliType 1.00 will not install under Windows 95 and have
limited functionality if you upgrade to Windows 95 over a
previously installed Windows 3.1 configuration.

If you are upgrading your Windows 3.1x system and the IntelliType 1.00
software we recommend that you delete the following line from your
SYSTEM.INI file:

taskman.exe=TASKSW16.EXE

This will deactivate the Windows 3.1 IntelliType Task Manager and
ensure full support of the Windows logo keys under Windows 95.

Microsoft IntelliPoint 1.00
---------------------------
Windows 95 has built -in support for your Microsoft Mouse.

IntelliPoint 1.00 will not install under Windows 95 and have
limited functionality if you upgrade to Windows 95 over a
previously installed Windows 3.1 configuration.


MSN, THE MICROSOFT NETWORK 
===========================

Access to The Microsoft Network
-------------------------------
The Microsoft Network is not installed on Windows 95 by default. To  
install The Microsoft Network, when running Setup, check the box for
The Microsoft Network on the Get Connected screen.

You can also install The Microsoft Network after you have installed  
Windows 95. Double-click the Set Up The Microsoft Network icon on your
desktop.

To sign up, double-click The Microsoft Network icon on your desktop.
Even if you were a member of MSN during a previous Beta, you must sign 
up again.

Billing
-------
Currently all access to The Microsoft Network is free. Information on 
pricing and policies will be sent to you before we begin actual billing.
At that time, you will be able to select a subscription and payment plan. 
If you do not select a subscription and payment plan, your MSN account 
will be terminated.

During the free period, billing information will be collected to ensure 
that billing will work correctly when the product is released. You will 
need a valid credit card number to use MSN, but no charges will be billed 
to your account. Your online statement will show your account activity, 
but the charges will always be $0.00. You may see a message about the 
cost of a file you are about to copy (download) to your computer, but
that charge will not be billed to your account.

Content
-------
The Microsoft Network is a big place, with many forums to visit and 
bulletin boards to browse. While some of them will have forum managers 
and content (you'll see bulletin board messages and chat discussions), 
not every area will be populated on the first day. Please don't let 
this stop you from posting a message or arranging to meet someone in 
a chat room. If you don't find something you want, keep checking; 
we keep growing and adding content all the time.

Tell us what you think!
-----------------------
We'd love to hear what you think of The Microsoft Network. Click Member
Assistance, double-click the Suggestion Box and let us know what you like, 
what you want to see added, and what you couldn't live without in an 
online service.

E-mail
------
You use Microsoft Exchange to send and receive MSN e-mail. 
For Beta information on Microsoft Exchange, see EXCHANGE.DOC in the DOCS 
directory of the CD-ROM or in the DOCS directory of floppy disk #1.

If you used e-mail on a previous Beta of Windows 95, and want to upgrade
your files containing messages, follow the directions in EXCHANGE.DOC
titled "Personal Information Store: Upgrading old PSTs from previous 
Betas of Windows 95." 

Beta support
------------
Support for The Microsoft Network is available online. You can get help 
from our Beta support staff in several ways. Click Member Assistance,
and then double-click the MSN Beta Support folder for your area. You'll 
find Beta Support bulletin boards with messages about every area of MSN. 
Take a look at the questions that other members have already asked. 
If you don't see the answer you need, you can post a message, and our 
Customer Support staff will answer your question.

Having trouble connecting or getting to online support?
-------------------------------------------------------
First, try using the Signup and Access Troubleshooter that is part of 
MSN Help. Click Start on the taskbar, click Find, and then type MSN.HLP. 
Once the filename is found, double-click it. In the Help Contents, 
double-click Troubleshooting.

There are a few other reasons you may not be able to connect:

1. If you can dial in, but can't connect, we may be performing periodic 
maintenance or automated testing. Although we will not take The Microsoft 
Network offline every day, we will occasionally schedule work between 
11:00 P.M. and 2:00 A.M., PST (7:00 A.M.-10:00 A.M., GMT). In addition,
automated tests will be run every Tuesday and Thursday.
At other times, we may be experiencing unanticipated outages of service. 
Please try connecting at a few different times before contacting our 
customer support numbers. 

2. If you have trouble connecting while trying to sign up for a 
member ID, you may be in an area that is not supported by our 
toll-free signup number. If this happens, you will hear your modem 
try to connect several times without success. The Connection Settings
dialog box will then appear. Click Access Numbers, and then for both the 
primary and backup phone numbers, click Change, and choose a number
in your calling area. Click Try Again in the Connection Settings 
dialog box, and you should be able to connect. 

If you are still unable to connect, contact Customer Service
at the phone numbers listed in the MSN Help file. If you can't reach 
Customer Service using the number listed for your country, try the 
number listed in "Other countries" in your region.

Reporting Bugs
--------------
To submit a bug, use the Bug Report form in Member Assistance. Fill in the 
necessary information. Please be specific on your modem settings, TAPI 
configuration, the time the problem occurred (including time zone), and 
steps to reproduce the problem.  

Known Problems
--------------
For more information on known problems and workarounds, click Member 
Assistance and look in the MSN Questions and Answers folder.

* When you use the Find command to find services, if you type a query with 
  all three boxes checked (Name; Topics, Place and People; and Description), 
  and then click Find Now, you will get a "Syntax not valid" error message. 
  To work around this, check only one or two boxes at a time.

* For MSN users in Australia: Dialup access numbers are available for most 
  STD codes in Australia. Choose the correct access number for your area. 
  If you choose the number for a different STD code, MSN will fail to 
  connect. If for some reason you cannot choose the number for your STD 
  code, you will have to type the number in the phone number box rather 
  than choosing from a list. The number to enter is 
	131400:.MSFTG000

  Enter  0,131400:.MSFTG000 if you need to dial 0 to dial out of your 
  PBX system. The extension ":.MSFTG000" will be hidden after it is accepted, 
  but you must enter it in order to connect successfully.

  Also, note that when you are asked to type your area code (STD code), you
  should type it without the leading zero used for dialing in Australia. 
  For example, the area code for Sydney is 2, and for Melbourne is 3.



NETWORKS
========

Client for NetWare: Opening files on NetWare 3.11 servers
------------------------------------------------------------------
Using certain applications, you may encounter problems opening files on 
NetWare 3.11 servers (3.11 only). Possible error messages could be:
- file not found error on a file you know exists
- sharing violation or lock violation error
- unable to open file error
- file in use error
This may happen with applications that open a very large number of files 
in a consecutive fashion. This can also happen when opening a file in a 
directory for which you do not have file scan rights(ex. MS Mail shared post 
office). This only happens on NetWare 3.11 servers; please file a bug if you 
have problems opening files on other versions.

If you encounter this problem, there are two different ways to get around it.
One is to obtain a patch (for 3.11 servers) from Novell which fixes this 
problem. It is available via ftp from ftp.novell.com; go to 
/pub/netware/nwos/nw311/osnlm and run 311ptd.exe. This exe will extract the
file os2opnfx.nlm. Then, load this nlm on the 3.11 server. 
("load os2opnfx.nlm")

Alternatively, you can disable long file name support in the Client for NetWare.
This means that you will not be able to use long file names on any NetWare 
servers from Windows 95. There are two ways to disable long file name support:
(1)In your system.ini file, paste in the following two lines:
[NWRedir]
supportLFN=0
(2)Alternatively, run REGEDIT, navigate to 
HKEY_Local_Machine\System\CurrentControlSet\Services\VxD\NWRedir
Create a new binary value whose name is supportLFN and whose value is 0.


ARCNET and Windows 95
---------------------
You cannot use the IPX/SPX compatible protocol over an arcnet real
mode (16 bit) NDIS2 driver.  When connecting to Windows NT server or 
Windows for Workgroups using arcnet, make sure you have another 
protocol in common such as NetBEUI.

For NetWare connectivity using arcnet, you must install support for
one of Novell's real mode Network Clients.  It is not possible
to use the Client for Microsoft Networks if you use an arcnet ODI
driver, or IPX monolithic.

Plug And Play Network Cards and 16-bit Real Mode Drivers
--------------------------------------------------------
When you need to run the 16-bit real mode driver for
your NIC (which is common if you use DLC or another real mode
protocol), sometimes your PnP card may appear not to function.
The reason for this is that on most computers, your PnP card remains
inactive until Windows 95 turns on the card.  16-bit NIC drivers, load 
before Windows 95 has a chance to turn on PnP cards.  Some 16-bit 
NIC drivers know nothing about PnP cards (most NE2000 PnP clones fall 
into this category), and this is where you would see a problem.

In order to use your PnP card with a 16-bit NIC driver:
1) Run the softset utility that comes with your PnP card, and set the
card to non-PnP mode.  
2) Remove the net card from the network control panel
3) Read the card using the Add New Hardware Control Panel applet.

When you move to a 32-bit protect mode NIC driver in the future, you
may rerun softset to turn on PnP mode for your card.

Intel EtherExpress 16 NICs and PCI machines
-------------------------------------------
You may experience system hangs or initialization problems if you are
using an Intel EtherExpress 16 NIC in a PCI machine with some Diamond
Speed Star PCI video cards.  The following are excerpts from Intel's
Customer Support Database.  These problems are not related to Windows
95, and happen on a variety of operating system platforms.  In
general, if you experience other problems with your EtherExpress 16
in a PCI machine, please attempt to replace the card before reporting
the problem to Microsoft.

If you have one of these video cards, contact your vendor about 
getting a new video BIOS update.

* Diamond Speed Star PCI video card with BIOS version 1.01
* Diamond Viper PCI VGA Video Adapter
* Diamond Stealth video card, BIOS v1.03

Windows for Workgroup shares
----------------------------
When you upgrade from Windows for Workgroups, it will not upgrade the
folders/directories that you have shared.  You will have to recreate them.

Drive connections to other servers will be migrated to Windows 95.

Running Windows 95 off a server
-------------------------------
M8 allows you to run Windows over the network.  The beta Windows 95 Resource 
Kit contains complete instructions in for installing Windows in this 
environment (see chapter 4, "Server Based Setup for Windows 95").  

There are a few limitations in this release:

 The following configurations are supported:
   Booting from hard disk using:
    Client for Microsoft Networks
    Client for NetWare Networks
    Novell Workstation Shell 3.x (NETX)
    Novell Workstation Shell 4.x (VLM)
   Booting from a floppy disk using:
    Client for Microsoft Networks
    Client for NetWare Networks
   Booting from a remote boot server using:
    Client for NetWare Networks

 To use one of the Microsoft clients, your network card must have an
 NDIS2 (16 bit) *AND* and NDIS3 (32 bit) driver.

Known bugs:

 Shutdown does not get all the way to the final shutdown screen that says
 you can press CTRL+ALT+DEL to reboot.  This makes it appear that the 
 machine is hung.  When shutting down these machines, wait for a few 
 moments after disk activity has stopped, and then you may reboot or turn 
 off the machine.

 To boot from a remote boot server using the client for NetWare Networks, 
 there are a few extra steps to follow:

 1) Before running setup, edit the msbatch.inf on the server and add 
    the following line to the [Network] section:

    SaveSUBoot=1

 2) Run setup as usual.
 3) After running setup, go to the SUBOOT subdirectory of the home 
    directory.  
 4) Edit the win.bat and switch the "nwrpltrm" and "set comspec" lines.
    (The "set comspec" line should be first)
 5) Make a new boot image by going back to the home directory and running:

	  RPLIMAGE SUBOOT

    (The RPLIMAGE can be found in the same directory as the NETSETUP 
    program)
 6) Copy the new NET$DOS.SYS file to your \LOGIN directory.

 Near the end of setup, you will be prompted saying that setup cannot write
 to mapisvc.inf.  This is just a harmless error.   Just click Continue and 
 let setup finish. 

 Exchange clients (MSN, Exchange mail, Route 66, FAX, etc) do not work 
 on machines that boot over the net in this beta.

 If you encounter problems during first boot of an EISA machine, try renaming
 EISA.VXD on the server to some other name (like EISA.BAK).  

 Always run SETUP from the root of the directory that NETSETUP creates.  Do 
 not run the SETUP program in the SUWIN directory.

TCP/IP & System Pauses
----------------------
If you are using TCP/IP for WAN connections but it is bound to both LAN and PPP
adapter but no DHCP server is present on the LAN, your system may pause for a
couple of seconds every once in a while. To avoid this, unbind TCP/IP from your
LAN adapter by bringing up properties of LAN adapter in the Net control panel
and unchecking TCP/IP in the bindings property sheet.

FTP Software's Windows 95 NFS client
------------------------------------
FTP Software, Inc. has prepared a Windows 95 specific .INF for installing
their fully integrated 32-bit NFS client for Windows 95, which can work
simultaneously with other Windows 95 32-bit networking components.

This file can be obtained directly from FTP Software (see below).
To install FTP NFS support:

1. Get the FTP NFS Windows 95 client software from FTP software.
2. Copy the file NETFTP.INF to the \windows\inf directory of your Windows 95
installation.
3.  From the start menu, choose Settings, Control Panel, Network.
4.  Press the Add button in the Network control panel, and add the
    FTP Software NFS Client for Windows 95.

To request a beta test application form for FTP Software's 32-bit Windows 95 NFS
Client, send an Electronic Mail message to:
   nfs95beta@ftp.com

Third Party Networks
--------------------
Windows 95 detects certain real-mode networks at installation time and installs
over them, leaving them running.  You must be running your real-mode network
when you run setup.  Windows 95 does not support installation of a real-mode 
network after setup, unless you have a Windows 95 specific .INF file from your 
network vendor.  Windows 95 does not include network component files for networks 
other than Microsoft networks.  You must already have the files for the network.  

PC-NFS
------
Windows 95 supports Versions 5.0 or greater of Sun PC-NFS.  If Sun PC-NFS
is installed using an NDIS 2 network adapter card or an ODI driver, then
Sun PC-NFS can be installed as an additional 16-bit network client along 
side 32-bit protected mode clients.  If you are using a Sun PC-NFS Lan Driver, 
Windows 95 can support PC-NFS as the primary network only.  Additional 
32-bit network providers are not possible in this case.

Banyan VINES 
------------
If Banyan drivers report that the VINES version is not the latest, edit the 
VINES.INI in the Windows directory so it contains the following lines:
[NEWREV]
dontcopy=1
vines.version=5.5x (x) USA      ; where x=your version
windows.version=3.95

DEC PATHWORKS
-------------
DEC PATHWORKS support involves running the Microsoft client over the
DECNet protocol.  To support this, Windows 95 requires some additional 
files and templates from DEC.  These files are shipped as the 
PATHWORKS for WFW 3.11 patch disk.  If you are running PATHWORKS and have 
not run the PATHWORKS for WFW 3.11 patch disk, you must first do so 
before installing Windows 95.  

If you use DLLNDIS.EXE, you must use a version dated 10/06/93 or later to
work with Windows 95.

Artisoft Lantastic
------------------
The Lantastic server cannot be run when Windows 95 is setting up.

There are known problems running MSCDEX and Lantastic.  If you experience
hanging problems or protection faults, remove MSCDEX.

Artisoft Lantastic, Beame and Whiteside BW-NFS 3.0
--------------------------------------------------
You cannot run any of these two networks along with a second network.  With
other supported third-party networks, you can run any
Windows 95 32-bit networking components at the same time.

Printing to network printer
---------------------------
Setting up for a printer that is shared via a 3rd party server may fail.
The workaround is to redirect lpt1: through a MS-DOS window (command prompt)
to the 3rd party share, then use printer setup for lpt1.  For example, if
a network printer is connected to "lpt1:" type:
"net use lpt1: \\servername\sharename" at a DOS command prompt (this command
depends on the network you are using; please consult the product documentation
to find out how to redirect a LPT port).  Then use printer setup in the Control 
Panel.  Alternatively, you can try selecting the printer from the printer folder,
choose "Map Printer Port" from the "File" menu, and select the redirection
for the dialog that is displayed.


Issues and Installation of MSDLC with Windows 95
------------------------------------------------
MS-DLC does not currently ship with Windows 95.  It is available to
customers via MSDL Microsoft Download Service, CompuServe and other
distribution methods as it was for WFW3.11.

Setup Issues:
To install the Real Mode MS-DLC stack, you need to have a copy of MSDLC.EXE
and NETDLC.INF.  These are the only files necessary and both can be found 
on CompuServe, or contact your beta support team or your local subsidiary 
as appropriate.
To install:
	a. After installing Windows 95, copy NETDLC.INF into the \WINDOWS\INF
	directory and copy MSDLC.EXE into the Windows directory.
	b. In the configuration tab of the net control panel click 
	Add/Protocol/Microsoft/Microsoft DLC then click OK.
	c. Restart machine and MS-DLC should now be installed
A minimum example of the AUTOEXEC.BAT with MS-DLC looks like this:
c:\windows\net initialize
c:\windows\msdlc.exe
c:\windows\net start

The net initialize command must come before the MSDLC.EXE line, which
must come before the net start command.

Upgrades:
* If after upgrading a machine that had MS-DLC installed, you encounter
problems, remove any NET INIT AND MSDLC.EXE commands from AUTOEXEC.BAT.  
Then repeat the install procedure above.

* If you install MS-DLC after installation of Windows 95, check to make sure
there is only one NET START command in AUTOEXEC.BAT before installing
MS-DLC.  
 
Install issue:
The default parameter settings for MS-DLC under the advanced properties
are configured for Token Ring connectivity.  You may have to modify the 
'swap' and 'usedix' parameters for use for ethernet networks. 
Consult the prior protocol.ini ms-dlc section for similar settings or 
consult the DXME0MOD.SYS line in CONFIG.SYS for the corresponding 
parameter settings.

If you receive the error message, "Protocol.ini. Keyword is not recognized"
when msdlc.exe executes, edit the PROTOCOL.INI and remove the lanabase 
entry under the [msdlc] section.

IBM's Lan Support Program:
IBM's real mode DLC protocol is called the IBM Lan Support Program.  It
uses drivers that load in CONFIG.SYS typically as follows:
	c:\lsp\DXMA0MOD.SYS
	c:\lsp\DXMC0MOD.SYS
(A token ring setup)

Windows 95 must be configured with NetWare ODI to use the LAN Support Program

If used with NetWare, the CONFIG.SYS is the same as above, but the AUTOEXEC.BAT
looks like the following:
	lsl
	lansup
	ipxodi
	netx (or vlm)

If you do not have this configuration in place, but are running DLC on token
ring, we recommend using the MS 32 bit client components of Windows 95 and replacing 
ipxodi and netx(or vlm).  Windows 95 will replace the two files with odihlp.exe.  
Example AUTOEXEC.BAT below:

lsl
lansup
odihlp.exe

If the IBM Lan Support Program is using the DXME0MOD.SYS driver in CONFIG.SYS,
it is then configured for its NDIS implementation.  See example below:
Sample CONFIG.SYS:
C:\LSP\PROTMAN.DOS /I:C:\LSP\
C:\LSP\ELNKII.DOS
C:\LSP\DXMA0MOD.SYS
C:\LSP\DXME0MOD.SYS

In this configuration, it is best to remove the drivers from the CONFIG.SYS
and configure Windows 95 to use the Microsoft DLC stack instead.

Novell NetWare Login Scripts
----------------------------
The Login Script Processor for the Microsoft Client for NetWare should 
correctly process all commands in your login scripts, except that you cannot 
load TSRs in these scripts. If you find that any line(s) in your login scripts 
are not being executed correctly, make sure to file a bug report, and include 
your login scripts in the report.

Microsoft TCP/IP Protocol
-------------------------
If Microsoft's TCP/IP is the only protocol you have loaded on your system, the
IP Address will not be added during Setup. If you have a DHCP server, just
open the Net Control Panel Applet and then close it; this will update the IP
Address.  Otherwise, open the Net Control Panel Applet, bring up properties
on TCP/IP and manually enter your IP Address.

On a clean install, to use DNS or LMHOSTS name resolution, make sure you have
DNS enabled in the network control panel.  Earlier Windows 95 versions (pre 337)
stored DNS information in the SYSTEM.INI file.  This version stores the info
in the registry.  When doing DNS lookups, the subsytem will check both the
registry and SYSTEM.INI for DNS information. A side effect of this is that
DNS lookups will be enabled even if the TCP/IP setup UI does not show any
DNS hosts or DNS disabled.  To fix this, delete the DNS section in your
SYSTEM.INI after copying the relevant info to the TCP/IP setup UI.

When upgrading a Windows For Workgroups PC with the Microsoft TCP/IP protocol, 
Windows 95 detects the TCP/IP stack and installs the Windows 95 version, but it 
will not preserve your WFW settings.  To restore the settings, open the TCP/IP 
property sheet from the Network Control panel.

Dial-Up Networking
------------------

Connecting to the Internet with Dial-Up Networking?  Then be sure to download
latest Inet.zip from your CompuServe forum, or contact your beta support 
team or your local subsidiary as appropriate.  It contains all
the latest instructions for smooth connections to Internet/PPP servers.

We have some reports of interoperability problems when connecting with
PPP accounts Internet Service Providers. These problems can be overcome
if you turn off IP header compression.  To do so, open the Dial-Up adapter
property sheet (from Network Control Panel) to the Advanced TAB, and set the
"Use IP Header Compression"  value to no.

User Profiles Over the Network
------------------------------
If you are using user profiles over a Windows NT or Novell NetWare network, 
and you choose to include Start Menu/Programs, Network Neighborhood, and/or 
Desktop Icons in your profile, then you must have Long File Name support on 
the server in order for these parts of the user profile to follow you around 
the network. 

Arcada Backup Exec network backup agent
---------------------------------------
In order to use the Arcada Backup Exec network backup agent included in 
Windows 95, you must have Arcada Backup Exec version 5.X.

Cheyenne ARCserve network backup agent
--------------------------------------
In order to use the Cheyenne ARCserve network backup agent included in 
Windows 95, you must have Cheyenne ARCserve version 5.01F. You may also use 
earlier versions of 5.01 if you obtain updated NLM's from Cheyenne Software.

Troubleshooting Networks
------------------------
Netcard Driver Problems
  Change the driver type of the card in control panel networks from
  enhanced mode(32bit and 16bit) NDIS to real mode 16bit NDIS driver. 
  If this fixes the problem please file a bug report indicating the
  model of the netcard and it's settings(irq, io, ram, eisa, pci,
  etc...) Also include what driver is showing up in netsetup exactly.

Browsing problems
  If you suspect browsing problems make sure that MS File and Print
  Sharing is installed in control panel, networks.  This is not
  installed by default, only on a upgrade that has it already
  installed.


PRINTING
========

Network Printing
----------------
Printing over the network between a computer running this release (M8 or
later) to, or from, a computer running the previous release (M7) is not
supported.


WINDOWS 95 PEN SERVICES
=======================

The Win95 beta SDK disk has a \PEN directory that contains the current
beta version of Pen Services for Windows 95.

Please refer to the penbeta.txt file in the PEN directory for installation
instructions.

