outSPOKEN for Windows Demonstration Disk
Version 1.1
8/7/95
 
This demonstration version of outSPOKEN for Windows contains a fully
functional version of the product as well as electronic documentation. The
documentation is contained in a self-extracting archive called
MANFILES.EXE. To extract the documentation from this archive, type the
command MANFILES from the outSPOKEN directory after installing the demo.
This command will place a number of text files in the outSPOKEN directory.
The file CONTENTS.TXT contains a list of the text files and explains what
each one is.
 
Previous demos of outSPOKEN for Windows had the restriction that you could
not exit Windows without rebooting your computer. The outSPOKEN demo no
longer has this restriction. This version allows you to exit Windows, as
well as provides more than twice as many keystrokes before requiring you to
quit the demo. When running the demo, a dialog box will appear once at 500
keystrokes, and again at 850 keystrokes, to remind you that you are using a
demo product. 50 keystrokes before the demo will stop functioning outSPOKEN
begins to remind you at each keystroke that you should save your work
and quit Windows. The demo will stop working after running for 1000
keystrokes, but you may run it as many times as you wish. When you exit
Windows, outSPOKEN will ask you to wait for 45 seconds before allowing you
to return to DOS. This demo will not function if a Windows debugger is
present. None of the restrictions of the demo apply to the lisenced version
of outSPOKEN for Windows.
 
We have also included a file which will delete outSPOKEN from your hard
disk. Run the file OSINSTAL.EXE to install outSPOKEN and the file
OSDELETE.BAT when you want to remove the outSPOKEN demo from your system.
 
IMPORTANT NOTE ABOUT OSDELETE.BAT:
Running the batch file OSDELETE restores your AUTOEXEC.BAT, WIN.INI, and
SYSTEM.INI files to their pre-outSPOKEN states. This means that any
modifications made to these files while the outSPOKEN demo was installed
will be removed by running OSDELETE.BAT. If you make any changes while this
demo is installed, examin the files with the extension .WAS after running
OSDELETE.BATand make any appropriate modifications to the new AUTOEXEC.BAT,
WIN.INI, or SYSTEM.INI files.
 
Instructions for installing this demo version of outSPOKEN for Windows can
be found in the file CHAP-2.TXT . The file CONTENTS.TXT describes the other
text files included with this demo. PLEASE NOTE: Tactile figures 1-6,
discussed in Chapter 3 of the outSPOKEN for Windows manual, are not
included with this demo version of outSPOKEN for Windows.
 
Feel free to distribute this demonstration software, but only as a complete
package which includes this README file and all the other files which are
on this disk or archive.
 
To order a full outSPOKEN for Windows package contact Berkeley Access at:
 
Berkeley Access
Berkeley Systems, Inc.
2095 Rose STreet
Berkeley, CA 94709
Voice: (510) 883-6280
Fax: (510) 883-6270
Internet: osw@berksys.com
URL: http://access.berksys.com
 
----------------------------------------
More information about outSPOKEN for Windows
Version 1.1
 
----------------------------------------
 
This file contains important information that may not be
included in the outSPOKEN for Windows User Manual or other
documentation, including new features added and bugs fixed in Version 1.1.
 
----------------------------------------
 
If you are viewing this document with Notepad, you should
turn on the Word Wrap feature by pressing Alt-e, followed by a w.
Also, for better viewing in any word processor, this window
may be maximized by pressing Alt-spacebar, followed by an x.
 
----------------------------------------
 
IMPORTANT NOTE TO USERS UPGRADING FROM outSPOKEN FOR WINDOWS VERSION 1.0
 
If you already have outSPOKEN for Windows installed, the simplest way to
upgrade to outSPOKEN 1.1 is to type "COPY A:\*.* C:\OSW" at the DOS prompt.
If the outSPOKEN disk is in a drive other than drive A, replace the letter
A in the above command to reflect the correct drive letter. If outSPOKEN
is installed in a directory other than OSW, replace the destination path
in the above command to reflect the location of your current installation.
You will not be able to overwrite the old outSPOKEN files while the program
is running. The upgrade process can therefore not take place while using
outSPOKEN.
----------------------------------------
 
CONTENTS
 
-New Features in outSPOKEN 1.1
-Before installing outSPOKEN for Windows
-Drivers and Synthesizers Supported by outSPOKEN
-Known Bugs and Notes on Compatibility:
 
* General
* outSPOKEN
* Access Pack
* Ami Pro
* Bookshelf
* Calendar
* Crosstalk
* Dashboard
* Lotus 1-2-3
* Mosaic
* Mouse
* Program Manager
* Quatro Pro
* Random House Webster's
* System Configuration Editor
* Windows Screen Saver
* WinFax PRO
* Word for Windows
----------------------------------------
 
New Features Added in outSPOKEN 1.1
 
READ CURRENT WINDOW -- KPD Plus
This command reads the entire current window from top to bottom without
moving the pointer from its current location.
 
AUTOMATICALLY READ DIALOG BOXES -- Window Preferences sub-dialog
When checked, this option in the Window Preferences sub-dialog reads dialog
boxes automatically when they open. This setting is checked by default.
 
READ REST OF DOCUMENT -- Ctrl-Shft-KPD 3
This command reads an entire text document from the current caret location.
In order for this feature to work, a trackable caret must be present in the
document window.
 
CURSOR NAME -- Shft-KPD Period
This command speaks the name of the current pointer.
 
----------------------------------------
Bugs Fixed in outSPOKEN 1.1
 
1. oSW now supports MS Access, MS Mail and Word Perfect 6.1
 
2. When tabbing between check boxes or radio buttons in a dialog box,
outSPOKEN now announces the current state of the control.
 
3. The outSPOKEN WINDOW MENU (Shft-KPD Slash) is now extremely reliable in
its ability to place the pointer in a given window without bouncing it out
again.
 
4. There should no longer be any problem with loading the outSPOKEN speech
driver into upper memory.
 
5. The pointer no longer jumps unexpectedly when clicking with the actual
mouse button, although there is no speech feedback when the physical mouse is
moved.
----------------------------------------
 
Before Installing outSPOKEN for Windows
 
Before you can install outSPOKEN, the following steps must
be taken:
 
1. Connect your speech synthesizer to the computer according
to the instructions provided by the manufacturer of the
synthesizer.
 
2. Install any software that came with the synthesizer
according to the manufacturer's instructions.
 
3. Install Microsoft Windows. (For information about
installing Windows without sighted assistance, check Appendix C of the
outSPOKEN User Manual.)
Complete instructions on installing outSPOKEN for Windows
can be found in Chapter 2 of the outSPOKEN User Manual.
 
If you already have a synthesizer installed that was being used with another
screen reader, be sure to restore the factory default settings before
installing outSPOKEN. Consult your synthesizer's documentation for
information about default parameters.
----------------------------------------
 
Drivers and Synthesizers Supported by outSPOKEN
 
Drivers for Synthesizers Supported by outSPOKEN are listed
below. Each driver supports one or more synthesizers. If your
synthesizer is missing from this list, contact your
outSPOKEN dealer or Berkeley Systems for assistance.
 
ACCENT.COM
This driver supports Accent PC, Accent SA, and all other
synthesizers that support Accent emulation, including the
Messenger IC, Artic Transport, and KeyNote Gold (check your synthesizer
documentation to find out if this is the case for your hardware).
 
*** Special note for users of the Messenger IC ***
When loading SystemSoft's card services software version
3.1, it is important that you do not use the "/EMS 1" switch on the
"CS.EXE" line, otherwise Windows will not load. SystemSoft
is aware of this bug and has no current plans to fix it. Your
line in the CONFIG.SYS file should look somewhat like the
following:
 
DEVICE=C:\CARDSOFT\CS.EXE
 
If you are using a drive and directory other than
"C:\CARDSOFT" substitute your drive and directory in the statement above.
 
*** Special Note for Keynote Gold Users ***
The Keynote SA and the internal cards both support Accent emulation. Both
devices emulate an internal Accent synthesizer, so port 0 should be
specified during installation of outSPOKEN. The driver called GOLDDEV.SYS
(supplied by the manufacturer) should be specified in your config.sys file
as follows:
 
DEVICE=GOLDDEV.SYS
 
 
APOLLO.COM
This driver supports the Apollo family of synthesizers.
 
ARTIC.COM
This driver supports most Artic synthesizers, including Artic-210, Artic-
215, and VoTalker. The Artic Transport uses Accent emulation (see above).
 
AUDAPTER.COM
This driver supports the Audapter System in serial mode only. Currently,
outSPOKEN does not support the Audapter in parallel mode.
 
BNS.COM
This driver supports most products from Blazie Engineering,
including the Braille'n Speak, Braille'n Speak 640, Braille
Blazer, Braille Lite, and Type'n Speak.
 
DEC-C.COM
This driver supports the DECtalk Classic and the Kurzweil
Personal Reader.
 
DEC-EXP.COM
This driver supports the DECtalk Express synthesizer. In some unusual situations
it may be appropriate to use the DECPC.COM driver instead. If you encounter
problems with this driver see the instructions below on how to use the
DECPC.COM driver with the DECtalk Express.
 
DECPC.COM
This driver supports the DECtalk PC and the DECtalk Express. If you are
using a DECtalk Express, please note that you should specify port 0 during
installation, even though the Express is attached to a COM port. If the
Express does not speak when outSPOKEN is run, take the following steps:
 
DECtalk Express Troubleshooting When Using DECPC.COM:
If the Express is attached to COM1 or COM3, create a DOS text file called
C1C3.DBG on your C drive which contains only the following lines.
 
e 40:0 0 0
e 40:4 0 0
q
 
 
If the DECtalk Express is attached to COM2 or COM4, create a DOS text file
called C2C4.DBG which contains only the following lines.
 
 
e 40:4 0 0 0
e 40:6 0 0 0
q
 
Your AUTOEXEC.BAT file should have commands which run the DECtalk drivers
that came with your synthesizer. After you install outSPOKEN, you will also
have a line in AUTOEXEC.BAT that specifies the outSPOKEN DECPC driver.
Create a line in AUTOEXEC.BAT after the manufacturer's drivers are run, but
before the outSPOKEN driver, that reads as follows:
 
C:\DOS\DEBUG<C1C3.DBG
or
C:\DOS\DEBUG<C2C4.DBG
 
depending on which port your DECtalk is attached to. This should induce your
Express to speak. Be sure to include the full path for the .DBG file you are
using. For example, if your DECtalk Express is connected to COM1 and the
debug file is located in the OSW directory, the line in your AUTOEXEC.BAT
file should read:
 
C:\DOS\DEBUG<C:\OSW\C1C3.DBG
 
These instructions are only relevant when using the DECPC.COM driver with
the DECtalk Express. If you are using the DEC-EXP.COM driver, these debug
steps are not needed.
 
 
DOUBLE.COM
This driver supports the DoubleTalk and DoubleTalk-LT from RC
Systems and the LiteTalk from MicroTalk, in serial and
parallel modes.
 
ECHO.COM
This driver supports the Echo GP.
 
MULTI.COM
This driver supports the MultiVoice synthesizer.
 
SB.COM
This driver supports the SoundingBoard and SpeakOut synthesizers from GW
Micro. Note that the SoundingBoard uses the Port Talk
protocol and needs to be specified as a parallel device
using LPT3. In order to make sure the SoundingBoard is set to the proper
parameters, the following lines need to be specified in the AUTOEXEC.BAT
file or from the command line before running the outSPOKEN SB.COM driver.
Also note that the following commands assume that the SoundingBoard
directory is current.
 
SBLOAD
SB /!l3
C:\OSW\SB P3
 
It may be easier for SoundingBoard users to install outSPOKEN by hand
(Section 2.3) rather than using the installer, because of these
modifications.
 
----------------------------------------
Notes on Compatibility With Other Applications
 
outSPOKEN has been extensively tested with a wide range of software and
hardware. In the vast majority of situations outSPOKEN is extremely reliable
and robust. However, some applications may exhibit unusual behavior when
run with outSPOKEN.
 
The following notes on outSPOKEN's compatibility with
selected applications are intended to cover some common situations,
but do not represent a comprehensive list. There may be
additional issues of compatibility not represented on this list. If you
believe this to be the case, please contact Berkeley
Systems, and we will do our best to assist you.
 
*** General
 
In order to ensure that your data will be safe if you happen
to encounter a crash with any piece of software, we recommend
that write-caching be disabled when using SMARTDRV.EXE. When
calling SMARTDRV.EXE, if you give it the argument for the hard disk
you are using, write caching will be disabled. Type SMARTDRV /? for more
info.
 
*** outSPOKEN
 
1. When using READ REST OF DOCUMENT (Ctrl-Shft-KPD 3), the caret may move
several lines ahead of the speech. This means that when interrupting the
speech, you may need to read up several lines to find the text that was last
spoken. This feature relies heavily on the caret being trackable. Thus in
situations such as italicized text in word (see below), this feature may not
work properly.
 
2. If you are reading an entire window with Ctrl-KPD 3 or KPD Plus and
outSPOKEN is continuing to speak the same information over
and over, press the
Esc key to stop this looping. Note that the Esc key
will be passed on to the application. Thus, if you are in a
dialog box, it will likely be dismissed. Another way to
stop this looping is to move the mouse.
 
3. When reading an entire document with Ctrl-Shft-KPD 3, make sure the
Windows focus is in the document, not the menu bar. If, for example, the
File menu is highlighted, using the READ REST OF DOCUMENT command will pull
down the menu instead.
 
4. Some "System Error" dialogs leave the system in such a
fragile state that the most outSPOKEN can do is automatically read the
System Error dialog. outSPOKEN commands may not work
in these error dialogs. Most "System Error" dialogs, however, are
navigable with outSPOKEN.
 
5. If you are using outSPOKEN navigation commands to read
through a window and your pointer is getting stuck, make sure that
your window is maximized so that all the text is showing within
the window.
 
6. When the user highlights the Control Menu by pressing the Alt key
followed by Left Arrow, the graphic name is not spoken.
 
7. When turning SAY-ON with Ctrl-KPD Enter, remember that
EVERYTHING written to the screen will be spoken. It is
recommended that you toggle off this setting when pulling
down menus or invoking dialogs and windows.
 
8. In some cases outSPOKEN will not be able to function
properly if it is loaded after the application which you are using. Try to
load outSPOKEN before any other applications in Windows.
 
9. When Echo Other is turned on, the Pause key is
incorrectly called Control.
 
10. When using arrow keys to shift highlighting in a combo
box or list box, sometimes both old and new highlighted items are
spoken. The newly highlighted item (the one with the focus) is
spoken second.
 
11. outSPOKEN cannot read the dialog produced by pressing
Ctrl-Alt-Delete.
 
12. When reading by character in a menu bar, and in some
other situations, outSPOKEN skips the space between items, and
does not notify you of this space. This also happens in Program
Manager group windows.
 
13. outSPOKEN's Window Name command (Ctrl-KPD Slash)
does not give the proper response in menus.
 
14. outSPOKEN does not speak the focus when the item the
pointer lands on is a graphic (e.g., iconized buttons).
 
15. The visual representation of a graphic in the Rename
Graphic dialog may look strange and ugly if the graphic has not yet
been displayed on screen. Graphics larger than 32 by 32 pixels
will not fit cleanly into the Rename Graphic window.
 
16. Dimmed menu items are not automatically spoken when they become
highlighted. They can be read with
outSPOKEN navigation commands. This is actually a convenient way of
determining which items are unavailable in a menu.
 
17. Whenever you cannot get to a window, try the TOP
WINDOW command (KPD Slash), and, if that doesn't work, the MENU
BAR command (Shft-KPD 7).
 
 *** Access Pack
 
Access Pack does not link outSPOKEN keys with their
modifiers.
 
*** Ami Pro
 
When using Ami Pro in "Custom 91" view, outSPOKEN may place
the pointer in the wrong position because of rounding off
of pixel positions done by Ami Pro. We recommend "Standard
View".
 
*** Bookshelf
 
We recommend turning the toolbar and other status bars off when using
Bookshelf with outSPOKEN. If the toolbar is turned on, outSPOKEN navigation
will be quite difficult.
 
*** Calendar
 
The phrase "Edit Box" is sometimes spoken twice when reading
with outSPOKEN navigation commands.
 
*** Crosstalk
 
When using SAY-ON in this program, the best success can be
had when the program window is maximized and the session window
is auto-set by the program. This can be done by checking a
check box in the Window dialog of the Session Settings dialog.
 
*** Dashboard
 
When closing dialogs in Dashboard, the pointer tends to move
back to Program Manager.
 
*** Lotus 1-2-3
 
If you are experiencing trouble renaming symbols, try
turning off "Show Icon Descriptions" in the SmartIcons dialog chosen
from the Tools menu. These symbols are described in this dialog and
can thus be defined here. If your outSPOKEN navigation gets stuck
reading down in this dialog, use the RIGHT key (KPD 6) to move beyond the
line.
 
*** Mosaic
 
 1. If you are having trouble launching Mosaic with
outSPOKEN, launch Mosaic first, then switch to Program Manager and launch
outSPOKEN.
 
2. If you are having trouble reading the text of the main Mosaic
window, try turning off the toolbar by making sure "Show
Toolbar" is not checked under the Options menu.
 
*** Mouse
 
outSPOKEN currently only supports use of the left mouse
button. Do not check "Swap Left/Right Buttons" in the Mouse Control
Panel if you want to use outSPOKEN keyboard commands for clicking the
mouse.
 
*** Program Manager
 
Generally, Program Manager works best with Cascaded, rather
than Tiled, windows. It is not necessary to maximize the group
windows, but of course more items will show if you do.
 
Known Bugs with Program Manager:
 
1. Occasionally, outSPOKEN's pointer navigation commands may
get "stuck" on an icon that is partially obscured by the edge of
its group window. Selecting "Arrange Icons" from Program
Manager's Window menu should fix this problem. Maximizing
Program Manager is generally a good idea and may also fix
this problem.
 
*** Quatro Pro
 
The outSPOKEN menu command will not move your pointer to the
menu bar. Press the Alt key with focus following turned on
to move your pointer there.
 
*** Random House Webster's
 
outSPOKEN's caret tracking may malfunction in
this program.
 
*** System Configuration Editor
 
Sometimes when you use outSPOKEN to click the mouse at the
left edge of a line, the click is placed one character to
the right. This actually happens with the physical mouse as
well.
 
*** Windows Screen Saver
 
When this screen saver is active and you enter the outSPOKEN
Preferences dialog, outSPOKEN loses track of what is on the
screen.
 
*** WinFax PRO
 
If you are using an external synthesizer during installation of this
program,
do not allow WinFax PRO to guess the port where you have a modem attached.
 
*** Word
 
1. outSPOKEN cannot locate the caret if it is within italic
text.
 
2. When clicking in italic text, outSPOKEN will place your
caret one character to the left of where you click.
 
3. When text is both highlighted and italicized, outSPOKEN
only tells you of the italicized attribute and not the
highlighting when you use the INFO key.
 
4. outSPOKEN navigation keys will not respect the boundaries
of Word's combo list boxes. Thus your pointer may "fall out"
of them. Instead, in combo list boxes like "File Type," use the
Windows arrow keys with track focus and speak focus turned on.
 
*** Word 6
 
1. After a menu or dialog box goes away, toolbars will
sometimes disappear. To bring them back, first try waiting a few seconds
for an update. If that does not succeed, then try cycling out of Word and
 back again by pressing Alt-Tab.
 
2. Your pointer may get stuck in the Forms toolbar. If so,
turn off "Tool tips" in the Toolbars dialog box selected from the
Options menu.
 
3. If you are not hearing the pre-defined symbols of the
Standard Toolbar, make sure that "Color Buttons" and "Large
Buttons" are not checked in the Toolbars dialog.
