Autodesk MCI Animation Driver Full Screen: In order to use the 320x200 fullscreen feature on VGA displays, the WIN.INI file must be updated. The following lines should be added. [AAPLAY Animation] FullScreen=AAVGA.DLL Other settings in the [AAPLAY Animation] Section: DualScreen=xxx: Can be yes or no. No indicates that windows is using the VGA, and the full screen driver must share the VGA with windows. Yes indicates that the Windows is using a monitor other than the VGA and the driver does not need to share the VGA with Windows. Default is no. HardwareDirect=xxx: Can be yes or no. Yes causes the full screen driver to directly access the VGA hardware for playing the animation. No causes the full screen driver to use the Microsoft supplied DisplayDIB function to play the animation. DisplayDIB is supposed to be version independant, but it disables all Windows tasks other than the current task, which causes MCI sound to fail. Default is yes. Implementatin Dependant Behavior The install sets the Autodesk Animation Driver as Animation1. capability: returns driver capabilities can eject - returns false can play - returns true can record returns false can reverse - returns false can save - returns false can stretch - returns false compound device - returns true device type - return "animation" fast play rate - returns 25 normal play rate - returns 15 has audio - returns true has video - returns true slow play rate - returns 8 uses files - returns true uses palettes - returns false windows - returns 8 close: Closes the animation info: returns animation information file - returns animation name product - returns "Autodesk Animator (TM) Animation" window text - returns current animation caption open: opens an animation alias xxxx - sets alias nostatic - returns not supported error parent hwnd - set parent window. If hwnd is 0, will create a full screen animation shareable - returns not supported error style xxxx - sets animation window style type xxxx - sets MCI type to animation pause: Pauses playing animation play: plays an animation fast - plays animation at twice designed speed. from xxx - starts animation at frame xxx. to xxx - stops animation at frame xxx. reverse - returns not supported error. scan - returns not supported error. slow - plays animation at half designed speed. speed xxx - playes animation at requested speed. put: places the animation on the screen. Default centers animation on screen. destination at x y h w - positions animation on screen. source at x y w h - sets visible portion of animation. souce at 0 0 0 0 will show entire animation. realize: returns not supported error. set: Sets driver items. Returns not supported except for: time format frames - time format must be frames. status: returns status of animation current track - returns 1 forward - returns true length - returns length of animation in frames. Not supported for animation scripts. media present - returns true mode - returns "pause", "play" or "stop" number of tracks - returns 1 palette handle - returns not supported error position - returns current position. Not supported for animation scripts. ready - returns true speed - returns animation speed. time format - returns "frames" window handle - return animation Window handle. step: Steps animation reverse - returns not supported error by xxxx - steps xxxx frames. Default is 1. stop: Stops animation. update: returns not supported error. where: returns current animation positions destination - returns animation position on screen. source - returns visible animation area. window: changes state of animation window. handle xxxxx - returns not supported, unless xxxxx is default. state xxxx - changes window state. text xxxx - changes window caption.
To compile the sample source code do the following: 1) Make sure the header files (located on the Set One disk in \source\misc) are on the include search path. 2) Copy libentry.asm to the directory of the dll you are compiling (located on the Set One disk in \source\misc). 3) Execute the Microsoft Make Utility (NMAKE.EXE) using the make file located in the dll directory
This file contains important and latest information of Developer
Kit for Sound Blaster Series.
1. Disk Organization
Developer Kit for Sound Blaster Series (SBK) diskettes are
organized into the following subdirectories:
\DRIVER : contains various drivers
\C : include files, libraries and example programs
for Microsoft C and Turbo C
\BASIC : include files, libraries, quick libraries and
example programs for QuickBasic and Basic PDS
7.1
\TPASCAL : include files, Turbo Pascal Unit (TPU) and
example programs for Turbo Pascal 6
In the subdirectory \C, files are further organized into
subdirectories as follow:
\INCLUDE : include files for Microsoft C and Turbo C
\LIB : libraries for Microsoft C and Turbo C
\MSC : example programs for Microsoft C
\TC : example programs for Turbo C
The C example programs are organized into subdirectories under
\MSC and \TC as follow:
\CDAUDIO : example for CD audio
\EFFECT : example for fade and pan effect
\GENERAL : general examples
\INCLUDE : loaddrv.c include file
\MIDI : examples for MIDI I/O
\MUSIC : examples for FM music
\SPEECH : examples for Text-to-Speech
\VOICE : examples for voice I/O
In the subdirectory \BASIC, files are further organized into
subdirectories as follow:
\CDAUDIO : example for CD audio
\EFFECT : example for fade and pan effect
\GENERAL : general examples
\INCLUDE : include files
\LIB : libraries and quick Libraries
\MIDI : examples for MIDI I/O
\MUSIC : examples for FM music
\SPEECH : examples for Text-to-Speech
\VOICE : examples for voice I/O
In the subdirectory \TPASCAL, files are further organized into
subdirectories as follow:
\CDAUDIO : example for CD audio
\EFFECT : example for fade and pan effect
\GENERAL : general examples
\MIDI : examples for MIDI I/O
\MUSIC : examples for FM music
\SPEECH : examples for Text-to-Speech
\VOICE : examples for voice I/O
\UNIT : include files and TPU
For the two BASIC languages, if you are compiled within the
integrated environment, you have to use QBSBC.QLB and QB7SBC.QLB
for QuickBasic and Basic PDS 7.1 respectively. If you are
compiled and linked from the DOS command line, the libraries to
be used are then QBSBC.LIB and QB7SBC.LIB respectively.
The voice and music files, DEMO.VOC, DEMO1.VOC and FFARES.CMF
used in the Basic, C and Turbo Pascal example programs are
located in the root directory.
2. Drivers
Developer Kit for Sound Blaster Series covers the whole series of
Sound Blaster audio cards' programming. Each of the card has it
respective drivers. These drivers are located in the \DRIVER
directory and distinguished by the file name and extension. They
are included in the SBK distribution disks for your development.
You do not have to include them with you product. We will
distribute the drivers to our users through our large distribution
network.
The drivers in the \DRIVER directory are not the actual name used.
You have to copy them to their target path and name before you can
use them. Remember to use the correct drivers for the respective
card.
Table below shows the cards' drivers and their target path and
name:
Cards Drivers Target Path and Name
----- ------- --------------------
1. SB SB15.CTV \SB\DRV\CT-VOICE.DRV
SB15.CTD \SB\DRV\CTVDSK.DRV
SB15.SFM \SB\SBFMDRV.COM
SB15.AUX \SB\DRV\AUXDRV.DRV
2. SBMCV SB15.CTV \SB\DRV\CT-VOICE.DRV
SB15.CTD \SB\DRV\CTVDSK.DRV
SB15.SFM \SB\SBFMDRV.COM
SB15.AUX \SB\DRV\AUXDRV.DRV
3. SB20 SB20.CTV \SB\DRV\CT-VOICE.DRV
SB20.CTD \SB\DRV\CTVDSK.DRV
SB15.SFM \SB\SBFMDRV.COM
SB15.AUX \SB\DRV\AUXDRV.DRV
4. SBPRO SBPRO.CTV \SBPRO\DRV\CT-VOICE.DRV
SBPRO.CTD \SBPRO\DRV\CTVDSK.DRV
SBPRO.SFM \SBPRO\SBFMDRV.COM
SBPRO.AUX \SBPRO\DRV\AUXDRV.DRV
All the Sound Blaster audio cards are using the same Text-to-
Speech SBTALKER.EXE driver found on the \DRIVER directory.
************ End of README.TXT ************
***************************************************************************** HSIN-LIN COMPUTER CO.,LTD. Micro Video Software Application Version 3.0a ***************************************************************************** Software installation To install the Micro Video onto your hard disk, start Windows first, then select Run command of the File menu in the Program Manager. Run INSTALL.EXE from the enclosed floppy diskette, then follow the instructions to complete installation. Windows must already be installed and you must have at least 700kB of disk space free to install Micro Video. After installation completed,Care must be taken that Micro Video ONLY operates in Windows Standard or Enhanced mode. You can double-click this icon whenever you want to run Micro Video. Running the DOS demo program There is a demo DOS application in the MICVIDEO directory(default directory) which create avideo window, moves and resides it,pans live video,loads a Targa image,zooms and pans the zoomed image. It also saves and reloads images using different file formats. To run this demo program, go to that directory and type DEMO. Running the Micro Tuner DOS program There is also a Micro Tuner DOS program in the MICVIDEO directory(default di- rectory) that lets you run the Micro Tuner directly in the DOS enviroment. To run this program, go to that directory and type TUNDOS. If you have any questions please call our Technical Support Department at 886-02-3123700. We hope you enjoy using the product!
***************************************************************************** HSIN-LIN COMPUTER CO.,LTD. Micro Tuner Software Application Version 2.3 ***************************************************************************** Software installation To install the Micro Tuner onto your hard disk, start Windows first, then select Run command of the File menu in the Program Manager. Run INSTALL.EXE from the enclosed floppy diskette, then follow the instructions to complete installation. Windows must already be installed and you must have at least 55kB of disk space free to install Micro Tuner. After installation completed,Care must be taken that Micro Tuner ONLY operates in Windows Standard or Enhanced mode. You can double-click this icon whenever you want to run Micro Tuner. Running the Micro Tuner DOS program There is also a Micro Tuner DOS program in the TUNER directory(default direc- tory) that lets you run the Micro Tuner directly in the DOS enviroment. To run this program, go to that directory and type TUNDOS. If you have any questions please call our Technical Support Department at 886-02-3123700. We hope you enjoy using the product!
***************************************************************************** HSIN-LIN COMPUTER CO.,LTD. Micro Video Software Application Version 3.0a ***************************************************************************** Software installation To install the Micro Video onto your hard disk, start Windows first, then select Run command of the File menu in the Program Manager. Run INSTALL.EXE from the enclosed floppy diskette, then follow the instructions to complete installation. Windows must already be installed and you must have at least 700kB of disk space free to install Micro Video. After installation completed,Care must be taken that Micro Video ONLY operates in Windows Standard or Enhanced mode. You can double-click this icon whenever you want to run Micro Video. Running the DOS demo program There is a demo DOS application in the MICVIDEO directory(default directory) which create avideo window, moves and resides it,pans live video,loads a Targa image,zooms and pans the zoomed image. It also saves and reloads images using different file formats. To run this demo program, go to that directory and type DEMO. Running the Micro Tuner DOS program There is also a Micro Tuner DOS program in the MICVIDEO directory(default di- rectory) that lets you run the Micro Tuner directly in the DOS enviroment. To run this program, go to that directory and type TUNDOS. If you have any questions please call our Technical Support Department at 886-02-3123700. We hope you enjoy using the product!
CDPLAYER FOR WINDOWS AND DOS
The program on this disk is version 3.2 of our Windows and DOS audio CD
Playing programs. They provides complete control over the playing of audio
CDs and the ability to catalogue your collection and browse through it.
You may contact Jupiter Software by EMail - CompuServe: 100140,2134
or pbrace@cix.compulink.co.uk
****************************************************************************
This disk contains the following files:
README 1ST This file
UPDATE TXT Upgrade history
LICENCE TXT Shareware licence
ORDER FRM An order form you can use to register
INSTALL BAT Batch file to install CDP4DOS
README DOS Readme file for CDP4DOS (includes installaion
instructions)
MANUAL DOS Manual for CDP4DOS
CDPLAYER EXE CDP4DOS program (shreware version)
CDTSR EXE CDTSR program (demo version)
README WIN Readme file for CDP4WIN
INSTALL WIN Installation insructions for CDP4WIN
MANUAL WIN Manual for CDP4WIN
SETUP EXE Installation program for CDP4WIN
APPSETUP INF Used by SETUP
PLAYER EXE CDP4WIN program (shareware version)
PLAYER HLP CDP4WIN help file
UPGRADE1 EXE Program to upgrade from 1.0 to 1.1 )
UPGRADE3 EXE Program to upgrade from 1.1 to 3.0 ) as UPGRADE.ZIP
============================================================================= WinCD(tm) Professional - Version 1.10 ============================================================================= To install WinCD Professional. Execute SETUP.EXE. ----------------------------------------------------------------------------- New Features of WinCD Professional: * WinCD Professional database is now contained in the files 'discdbXX.INI' where XX = 1 through 20. WCDP.INI now contains only configuration information for the operation of WinCD Professional. * The Track field has been increased from 30 characters to 60 in order to allow for longer song titles and additional information. * Compatibility Mode (accessible through the Configure dialog) adds additional support for various system configurations. * WinCD Professional now corrects for improper header information contained in some audio CDs. * Minor performance enhancements and fixes. ----------------------------------------------------------------------------- Thank you for using WinCD Professional. Apriori Software Corporation
( ªÖöA⥠r ÿΦe9åæ¼@2 ╙ ╕Ωa6&C!ö▄d:¢Dπ Ǭs0ÖαΣπ|@µ 3╬@╨T.l0═╬éI║tr6╨ì&≤t░─o:╤!╤öR-ì á
Icon Hear-It Icon Hear-It
Version 1.0
July 25, 1992
Welcome to version 1.0 of Icon Hear-It.
Please read through this Readme.txt file. It contains important information
not available when the manual was printed.
Icon Do-It Users
Icon Hear-It replaces Icon Do-It during installation. Since Icon
Hear-It contains all the functions of Icon Do-It plus more, you can simply
erase Icon Do-It from your hard drive.
Sound
If you do not hear any sound please try assigning the sound again.
If that doesn't work, check and make sure the HEARITFX
directory exists beneath Windows and that the TASOUNDS directory exists
beneath ICONHEAR. The TASOUNDS directory CANNOT be moved, nor can the
files beneath it be deleted. You will lose your talking applications
if Icon Hear-It cannot find these sound files.
You can erase all or some of the files in HEARITFX without damaging
Icon Hear-It. But, you will lose any of the preattached sounds whose
file you have deleted or moved. However, after relocating this directory
you can reattach these sounds.
Icon Hear-It supports all .wav files. You can use your own sounds
with Icon Hear-It by clicking through the directory list boxes to the
directory that contains your .wav files and following the instructions
outlined in the User's Guide for attaching sounds.
Sound Board Not Being Used
If you have a sound board installed (i.e. Sound Blaster, Ad Lib,
Thunder Board, etc) and the sounds are still being played through
the PC Speaker:
1. Go into Control Panel, then Drivers.
2. Check to make sure your sound driver is installed.
3. Remove the Sound Driver for PC-Speaker.
You will be prompted that this sound driver is required by your system,
do you really want to remove it. Click Yes. You will then be asked
if you want to restart Windows, also Click Yes.
If you are still not getting sound through your sound card you will
need to edit your SYSTEM.INI file located in your Windows directory.
You can use NOTEPAD or DOS EDIT to do this.
Towards the bottom of this file, you will see a section similar to the
following:
[drivers]
Wave=mvspeakr.drv
Replace the words mvspeaker.drv with the name of your speaker driver.
Then, save the file and restart Windows.
Adding Push Buttons
If you add a push button and give it a sound, you will see it in the
Track All Icon Hear-It Sounds window. But, if you unattach the sound,
the push button will be removed from this list. The preattached push buttons will
always remain in the list whether you unassign their sounds or not.
Speaker Driver Setup
The Speaker Driver Setup push button in the Options Window works ONLY with
the speaker driver installed with Icon Hear-It. When loading, if
Icon Hear-It detects a sound board or speaker driver already on your
system, it will not allow you to use it Speaker Setup.
If you do not have a sound board or other speaker driver installed
and you still can't access the Speaker Driver Setup, you need to edit your
system.ini file and remove the line :
Wave= speakerdrivername
from underneath the [Drivers] section. The next time Icon Hear-It loads,
it will write a new "Wave = " with its own speaker driver.
DOS Applications that Use Sound
If you have attached a sound to an icon for a DOS based application
that uses sound, you may get an error messager saying your sound card
is in use by another program. This is happening because the DOS
application accesses the sound board directly and if it is in use
by Windows, (which it would be if it was playing the sound attached
to the icon) it cannot be accessed again by DOS.
Icon Make-It Icon Hear-It
Version 1.0
December 2, 1992
Welcome to version 1.0 of Icon Make-It.
Please read through this README.TXT file. It contains important information
not available when the manual was printed.
Icon Hear-It Lite:
This version of Icon Make-It contains a "Lite" version of our commercial
product Icon Hear-It. Hear-It Lite, contains some but not all of the
functionality of the full version. If you would like more information
on Icon Hear-It, please call Moon Valley Software at 602-375-9502.
Sound in Icon Hear-It Lite
If you do not hear any sound please try assigning the sound again.
If that doesn't work, check and make sure the HEARITFX
directory exists beneath Windows.
You can erase all or some of the files in HEARITFX without damaging
Icon Hear-It Lite. But, you will lose any of the preattached sounds whose
file you have deleted or moved. However, after relocating this directory
you can reattach these sounds.
Icon Hear-It Lite supports all .wav files. You can use your own sounds
with Icon Hear-It by clicking through the directory list boxes to the
directory that contains your .wav files and following the instructions
outlined in the User's Guide for attaching sounds.
Speaker Driver Setup
The Speaker Driver Setup push button in the Options Window works ONLY with
the speaker driver installed with Icon Hear-It. When loading, if
Icon Hear-It detects a sound board or speaker driver already on your
system, it will not allow you to use it Speaker Setup.
If you do not have a sound board or other speaker driver installed
and you still can't access the Speaker Driver Setup, you need to edit your
system.ini file and remove the line :
Wave= speakerdrivername
from underneath the [Drivers] section. The next time Icon Hear-It loads,
it will write a new "Wave = " with its own speaker driver.
Kofax Image Processing Platform (KIPP) for MS-Windows
RELEASE NOTES for KIPP Version 1.21.13: $Date: 19 Dec 1991 14:55:12 $
Kofax Image Products
3 Jenner Street
Irvine, CA 92718
(714)727-1733
(714)727-3144 FAX
(714)727-3538 BBS (Kofax Connection)
=========================
DOCUMENTATION CORRECTIONS
=========================
See Release Notes
====================
GENERAL INSTALLATION
====================
The installation program used to install KIPP, INSTALL, is
licensed software provided by Knowledge Dynamics Corporation.
INSTALL is Copyright (c) 1987 - 1989 by Knowledge Dynamics
Corporation which reserves all copyright protection worldwide.
INSTALL is provided to you for the exclusive purpose of
installing KIPP.
An installation procedure is provided for installing the KOFAX
drivers. See the section "Installing the Driver Files" for
information on installing the drivers.
Install the files found in directory \WINDOWS in the DOS
execution "PATH" or in your Windows directory (ie. C:\WINDOWS).
After installing the KIPP files, you will need to modify your system.ini
file in your Windows 3.0 directory. Locate the section labeled 386ENH, and
add the line "device=VKFD.386" to take advantage of 386 enhanced mode.
===========================
INSTALLING THE DRIVER FILES
===========================
Required driver files:
---------------------
INSTALL.EXE, KF9XDRV.EXE
Files required only for PS/2 installations:
------------------------------------------
@7055.ADF
In the KIPP 1.2 release an installation utility has been provided
to simplify driver installation. To install drivers for your system,
invoke the INSTALL.EXE utility, and follow the instructions on the
screen. INSTALL.EXE will extract the compressed driver files from
the KF9XDRV.EXE file and write the required files into the specified
directory.
==================
LOADING THE DRIVER
==================
After running the INSTALL.EXE utility, a directory will exist on your
hard disk (c:\KOFAX by default) that will contain the file KF9X00.EXE.
When the KF9X00.EXE program is invoked, it will load the KIPP driver
onto your 9100/9200. For automatic driver loading, the KF9X00.EXE should
be called from your autoexec.bat file at system initialization.
The following help and configuration data is available with the
"KF9X00 -help" command:
Firmware and Configuration Loader for the KF9x00 Engines.
Copyright (c) Kofax Image Products, 1989-1991. All rights reserved.
Usage: kf9xl <param1> ... <param15> (to load only)
or kf9xc <param1> ... <param15> (to load & install)
<param1> -f=<fname> load firmware file <fname>
-f=@<fname> load firmware/config files listed in <fname> file
-f=@ load list of firmware/config files in 'FWLOAD.FIL'
-f load firmware file 'FWLOAD.OUT'
<param2> -l=<fname> load configuration file <fname>
-l=@<fname> load firmware/config files listed in <fname> file
-l=@ load list of firmware/config files in 'KFCLOAD.FIL'
-l load configuration file 'KFCLOAD.KFI'
<param3> -g=<address> start adapter executing at specified address
-g start adapter executing at entry point or NMI vector
-ng do not start adapter after loading.
<param4> -i=<iobase> address adapter at specified io address (AT bus)
<param5> -z=<intsel> interrupt level assigned to adapter (AT bus)
<param6> -p=<slotid> select adapter slot (MC bus only).
-pp=<val> parallel printer port select for HP III (1-4).
-ps=<val> serial printer port select for HP III (1-4).
<param7> -t test adapter before loading using 'kf9xd.exe'
-t=<fname> test adapter before loading using <fname> program
<param8> -j it's a KF9100 adapter (no VRAM).
<param9> -c cumulative firmware load -- prior load(s) valid
<param10> -s=<val> assign software interrupt (to install driver)
<param11> -lid=<val> associate logical id <val=0..7> with current load
<param12> -lnm=<text> associate text string with current load
<param13> -v or -q verbose or quiet (very) load
<param14> -k remove TSR from memory.
<param15> -h or ? display help screen.
Switch prefix '-' and value separator '=' are optional.
Examples:
C> REM MUST CD TO KOFAX DIRECTORY BEFORE LOADING THE DRIVER
C> CD C:\KOFAX
C> REM INSTALL DRIVER
C> KF9X00
Copyright (c) Kofax Image Products 1991. All rights reserved.
KF9100/9200 1.21 Driver installed at 0x62
C> REM UNINSTALL THE DRIVER
C> KF9X00 -K
====================
NOTES - NEW FEATURES
====================
SOUND BLASTER 16 README.TXT
===========================
This file contains information not available at the printing of the
manual. Please read all the sections before you proceed with the
installation.
This file contains the following sections:
1. Software Installation
2. Hardware Configuration
3. Hardware Installation of Wave Blaster
4. Sound Blaster 16 Mixer Control
5. Creative Soundo'LE
6. Voice Utilities
7. Sound Drivers Installation Utility (INSTDRV.EXE)
8. Maximum Recording Rates For Sound Blaster 16
9. Creative Compact Disc Player
10. Advanced Signal Processor
11. Using Windows QSound Control Panel
12. Manual Errata
13. Acknowledgement
1. SOFTWARE INSTALLATION
The installation program, INSTALL.EXE will modify your
AUTOEXEC.BAT and CONFIG.SYS files. Your original files will be
renamed with the extension B~K.
WINSETUP will NOT set up the drivers and applications properly if
your BLASTER environment strings are incorrectly set. Please make
sure that these environment strings are set properly before
running WINSETUP.EXE. You may enter "SET" at the DOS prompt to
check the environment settings. Refer to your Sound Blaster
manual for more details on the BLASTER and SOUND environment
strings.
Normally, WINSETUP.EXE needs to be run only once. If the hardware
settings of your sound card needs to be changed, use the DRIVER
applet in CONTROL PANEL to change the settings of your Windows
drivers. Refer to your Windows manual for more details on the
DRIVER applet.
2. HARDWARE CONFIGURATION
Run SBCONFIG.EXE to configure your card if you change the default
DMA channels 1 and 5, or interrupt 5. To avoid conflicts with
Adaptec 1542 card change DMA 5 to 6 or 7.
Remember to REBOOT your system
3. HARDWARE INSTALLATION OF WAVE BLASTER
If you want to installing a Wave Blaster, make sure that you
connect your CD-ROM drive to the Sound Blaster 16 Multi-CD
Interface Card using the CD-ROM data cable first. You can then
proceed to install Wave Blaster.
4. SOUND BLASTER 16 MIXER CONTROL
SB16MIX.EXE
-----------
This mixer can only be accessed when you are in video mode 3 (text
mode - 80x25 lines in 16 colors) or 4 (graphic mode - 40x25 lines
in 4 colors). If you are using any other video mode, a single
line version of the mixer will appear. No mixer control is
available if you select a video mode above 13h (Enhanced video
mode).
5. CREATIVE SOUNDO'LE
Creative Soundo'LE uses the hard disk as the working space.
Recording and playback are done directly to your hard disk.
Creative Soundo'LE also supports compressed wave files. You may
record or play compressed wave files using Soundo'LE. The
graphical Signal Indicator will not be updated when you use
compressed files.
6. VOICE UTILITIES
Below is a list of the limitations and capabilities of the
following utilities :
WAV2VOC .EXE - Able to support ALAW, uLAW and ADPCM
compressed files.
VOC2WAV .EXE - Does not support 16-bit compressed files.
VOCN2O .EXE - Does not support 16-bit compressed files.
7. SOUND DRIVERS INSTALLATION UTILITY (INSTDRV.EXE)
The program INSTDRV.EXE will not change the default DMA and IRQ
settings of the CTWMEM.DRV and CTWDSK.DRV drivers. Current
applications using these two drivers obtain the card's settings
from the BLASTER environment string.
8. MAXIMUM RECORDING RATES FOR SOUND BLASTER 16
The sampling rate used for recording is largely influenced by your
computer's main processor. The following maximum recording rates
are suggested when you use 16-bit digital audio under Windows:
╔═══════════════════════╤══════════════════════╗
║ SYSTEM │ RECORDING RATE ║
╠═══════════════════════╪══════════════════════╣
║ │ ║
║ 386 and above │ Stereo - 44KHz ║
║ │ Mono - 44KHz ║
║ │ ║
╟───────────────────────┼──────────────────────╢
║ │ ║
║ 386 SX and below │ Stereo - 22KHz ║
║ │ Mono - 44KHz ║
║ │ ║
╚═══════════════════════╧══════════════════════╝
For optimal performance under Windows, configure your audio card
for 16-bit DMA (Direct Memory Access). Refer to your Sound
Blaster 16 Getting Started Manual for more information on setting
up the audio card to use a 16-bit DMA channel.
9. CREATIVE COMPACT DISC PLAYER
Double click the "QCD readme" icon in the Sound Blaster 16 group
windows for more informations.
10. ADVANCED SIGNAL PROCESSOR
For users with Advanced Signal Processor, the Advanced Signal
Processor files (*.CSP) MUST be located in the Sound Blaster 16
CSP sub directory (example C:\SB16\CSP) when you use any
compression technology.
11. USING WINDOWS QSOUND CONTROL PANEL
The QSound effect cannot be enabled or disabled during a wave
playback. The enabling or disabling of QSound effect will only
affect the next wave playback.
The QSound Control window works in low priority mode. When an
application like Creative Mosaic uses QSound, the control panel
becomes inactive. When you quit the application that uses QSound,
the Control window will become active again.
* Note : QSound application program is only available on Sound
Blaster 16 with Advanced Signal Processor.
12. MANUAL ERRATA
Technical Support for Creative Labs
The ZIP Code has been changed from 74973 to 74075.
The BBS number has been change from 408-428-6660 to
405-742-6660.
13. ACKNOWLEDGEMENT
The current version of SB16FM.DRV is from Voyetra Technologies.
******** END OF README.TXT ********
Midisoft Studio For Windows, Version 3.10 Beta *** Note To Beta Testers: *** The new features that need special testing are ... - Undo (for Cut/Paste operations) - Metronome via MIDI - Saving of screen positions - Higher ruler resolutions including triplets - Saving MIDI File Type 0 (RIFF will not be supported) - Auto-Notation parameter changes, including recognition of triplets - Support for a wider range of Time Signatures - The humanize feature of Quantize - Auto-justification of printed page - New View Settings options - Click and Drag of notes and regions in Score View - Triplets - The new interactive Mixer screen Features that are not completed and should not be tested yet: - System Exclusive - Auto-transpose for printing ***************************** Information For New Users Thank you for purchasing Midisoft Studio for Windows. We greatly look forward to satisfying your sequencing needs now and for many years to come. Unless you have already done so, please mail us your product registration card, so that we can automatically send you a free song disk, and information about upcoming product upgrades and updates. We encourage you to contact us with any comments or questions that may arise as you use our program. Midisoft Technical Support; PO Box 1000; Bellevue WA 98009; USA; FAX 206-883-1368. ISSUES YOU MIGHT ENCOUNTER WITH THIS RELEASE: 1) If you find that occasionally you lose the mouse cursor, you might be encountering a hardware conflict between Mouse and MIDI that occurs rarely in Enhanced-mode Windows (on VERY FEW machines). If you use our program in Standard-mode Windows (Start Windows with WIN/S), this problem disappears. 2) If you have trouble getting MIDI Input, the problem is very likely a hardware interrupt conflict. Take inventory of the other cards you have in your system, and make sure the MIDI card has a unique interrupt level and I/O address. Note: The Windows Drivers for MIDI use Interrupts only for MIDI In, not for MIDI Out. So if MIDI Out (playing) seems to work fine, that is NO indication that you have your card's interrupt set correctly. 3) If you have trouble getting playback, we recommend you simplify your test configuration by simply using the Media Player provided in Windows. This program will play back any of the MIDI files provided with Midisoft Studio provided that you have configured your MIDI Mapper to playback the low channels (1-10). If you can successfully get the MIDI Mapper to playback within Windows, then you will be able to get Midisoft Studio to playback by selecting MIDI Drivers/ Multimedia Drivers/MIDI Mapper from the Setup Menu. 4) When in Score View, if you have trouble selecting notes to edit, you might try changing the clef to make sure the notes appear on the staff. Another option is to start a Click & Drag region from within the staff and end it outside the staff. Similarly, to select rests (for the Splice Cut/Paste operations), do so by selecting click & drag region that includes the rest. 5) If you are running on a 1-2Mb computer, your usage of memory will affect the operation of our program. We recommend that you use HIMEM.SYS (to access the high 384K Extended Ram), but don't tie up any RAM into SMARTDRV.SYS. If Studio for Windows claims not to have enough memory, Windows might not be correctly detecting high memory. On a 1 Mb configuration, we recommend you ascertain that Windows has at least 600K available before running Studio for Windows. You can check your available memory by selecting "About Program Manager" in the Windows Program Manager's Help menu. We do not run in 640K machines (and thus not Real Mode Windows), nor do we suggest using Expanded RAM (Windows runs best using EXTENDED RAM, not EXPANDED). Special note: This may not be possible if you are using Windows 3.1. As mentioned on our box, the minimum RAM requirement for Windows 3.1 and Midisoft Studio is 2 Meg. 6) Because Midisoft Studio for Windows' MIDI drivers require instant access to memory, problems can be avoided by not using memory managers (such as earlier versions of QEMM) which intercept and map memory calls. We recommend that you simply use the HIMEM.SYS driver that comes with Windows. Similarly, TSR programs that are feeding off your computer's clock can also cause problems. If you are getting machine crashes or lock ups, we suggest clearing out your machine's startup files (AUTOEXEC.BAT, CONFIG.SYS) to the bare minimum (even remove DOS shells) and try running Studio for Windows again before contacting our technical support department. Specifically, remove non-essential entries in your CONFIG.SYS and AUTOEXEC.BAT files, as well as bringing down the FILES= and BUFFERS= values in your CONFIG.SYS. If you are using DOS 5 (or later), also make sure that you have a DOS=HIGH entry in CONFIG.SYS. 7) Currently, our stand-alone Roland drivers are more efficient and more robust than those included in Windows 3.1. For this reason, we recommend that if you have a Roland-compatible or Midisoft Midiface card, use our drivers instead of those in the Win31/Multimedia Extensions. To do so, select "Midisoft Drivers" from the "MIDI Interface" dialog box. 8) A little hint about changing a note's pitch: Use the SHARP and FLAT tools (in the note palette) to click on a note and change by a half-step. This can be used repeatedly to change a pitch as far as you desire. ABOUT THE DEMO SONGS In addition to publishing music sequencing and notation programs like Studio for Windows and Recording Session for Windows, Midisoft also publishes MIDI data and music education software from which the following demo songs have been taken. Among these products are: The Midisoft Multimedia Music Library--A collection of original MIDI music for use in multimedia presentations. A World of Music--15 volumes of MIDI sequences of all types ranging from classical to jazz to pop. Music Mentor--A music enterntainment and education program that combines text and graphics with simple animation and MIDI-generated sound to make learning about music fun. How the Songs Are Set Up These songs were created on Roland SC-55 Sound Canvas sound modules. They conform to the new General MIDI standard for MIDI sequence publication. Each song file includes setup information at the beginning of each track that specifies patch, volume, pan, reverb, and chorus settings for each instrument. These files will, of course, sound their best on a Sound Canvas or another Roland GS MIDI device, but they should work just fine on any equipment that uses the General MIDI patch assignments. That includes many new products by Yamaha, Korg, and other companies, as well as most internal sound cards like Ad Lib, Sound Blaster, and Pro AudioSpectrum. A_BRIDGE.MID This is an excerpt from a piece called "A Bridge to Cross" composed by Tracy Hurst for the Midisoft Multimedia Music Library. ANOTHER1.MID This is an excerpt from a piece called "Dance Party" composed by Tracy Hurst for the Midisoft Multimedia Music Library. ARABESQ.MID This is an excerpt from the 1st Arabesque by Claude Debussy performed here by George Litterst. This piece was taken from A World of Music: The Impressionist Collection, a collection of pieces by Impressionist composers. BFLATBLS.MID BBBLUES.MID These are standard B-flat blues that you can use to practice blues soloing. BOURLESQ.MID This is a piece called "Bourlesq" written by Leopold Mozart (Wolfgang's father). It was taken from Music Mentor. CLAIRDLN.MID This is an excerpt from the Claire de Lune by Claude Debussy performed here by George Litterst. This piece was taken from A World of Music: Classical Favorites, Piano, a collection of famous classical piano pieces. CLEMENTI.MID This is a keyboard sonata by Muzio Clementi performed by George Litterst. It was taken from Music Mentor. FUGUE.MID This is a short fugue by Johann Pachelbel, sequenced by George Litterst. This piece was taken from Music Mentor. FURELISE.MID This is an excerpt from Fur Elise by Beethoven performed here by George Litterst. This piece was taken from A World of Music: Classical Favorites, Piano, a collection of famous classical piano pieces. GIGUE.MID This is a gigue by J. S. Bach performed by Sheila Waxman. JUSTDRUM.MID This is a collection of drum patterns created by Tracy Hurst for A World of Music:DrumBeats. PEERGYNT.MID This an excerpt from Grieg's Peer Gynt Suite sequenced by Ben Hippen. This piece was taken from A World of Music: Classical Favorites, Orchestral. POLONAZE.MID This is an excerpt from Chopin's Military Polonaise performed by George Litterst. PRELUDE.MID This is a prelude by J. S. Bach performed by Sheila Waxman. RAGTUNE.MID This is a piano piece by Tracy Hurst that was taken from the Midisoft Multimedia Library. RAINSONG.MID This is an excerpt from a piece composed by Tracy Hurst that was taken from the Midisoft Multimedia Music Library. ROCKNOUT.MID This is an excerpt from a piece composed by Tracy Hurst that was taken from the Midisoft Multimedia Music Library. SWEETHRT.MID This is an excerpt from a piece composed by Tracy Hurst that was taken from A World of Music: Pop Building Blocks. Credits Music Mentor, A World of Music, and the Midisoft Multimedia Music Library as well as all the sequences included here were created for Midisoft Corporation by Music Technology Associates . Music Technology Associates is a Boston, Massachusetts-based group of music and computer professionals who provide product development and consulting services to companies in the music technology industry. Midisoft Studio for Windows and Midisoft Recording Session were created at the Midisoft Corporation world headquarters in Redmond, Washington. For information about additional products Midisoft Corporation PO Box 1000 Bellevue, WA 98009 VOICE: (206) 881-7176 FAX: (206) 883-1368
This file contains information that was not available
at the time the MediaBlitz documentation went to press.
Reuse and redistribution of clip media
=======================================
Remember, you are not authorized to use the MediBlitz
sound files for broadcast or public performance. Also,
all MediaBlitz files are subject to the Asymetrix MediaBlitz
License Agreement, even if you have modified them or used
them to add to or create new files.
Error when using Windows 3.0
=============================
If you are running MediaBlitz under Windows 3.0 and opening
and closing ToolBook applications that do a restore system
in the enterbook handler without forwarding the enterbook
message, you may receive an Unrecoverable Application Error.
This will not occur if you are using Windows 3.1.
Event synchronization with .MMM and .AWM files
================================================
If you have created a score with MacroMind Director or
Gold Disk Animation Works files, make sure that other clips
in the score begin playing before the animation file plays
or after the animation file has finished playing. MediaBlitz
does not receive its timer event messages when either of these
file types are playing.
Palette for 256-color bitmaps
==============================
If you are combining 256-color bitmaps with the 256-color
bitmaps shipped with MediaBlitz, you may want to apply the
ASYM5.PAL palette file to each of your bitmaps to prevent
palette conflicts. All 256-color bitmaps included with
MediaBlitz use this palette. For more information regarding
color and bitmaps see the card titled "Bitmaps in Sample
Scores" included in this package.
Slower computers
=================
If you are playing very complex scores with overlapping clips
and files on a machine at or near the minimum requirements for
MediaBlitz while in ScoreMaker, the timeline ticker may
continue to move after the last item in the score has played.
Press Esc to stop the ticker.
One score limit
================
You can only play one clip or score at a time in MediaBlitz and
Multimedia ToolBook. To stop a clip or score before it plays to
the end, press Esc. When you launch a score while another score
is playing, the first score will terminate in it's current position
and the new score will start.
Changes to environment files made by MediaBlitz setup
======================================================
Changes to your AUTOEXEC.BAT:
During Setup, MediaBlitz adds the MediaBlitz directory, the
Runtime ToolBook directory, and the ToolBook multimedia
extensions directory to the front of your path statement.
Changes to your WIN.INI:
If you did not have a previous version of TBOOK or ToolBook
installed, MediaBlitz adds the ToolBook file extension,
TBK=TBOOK.EXE ^.TBK to the [Extensions] section of your
WIN.INI.
If you install the version of TBOOK that comes with
MediaBlitz and have a previous association for the .TBK
extension in your WIN.INI, the setup program will give
you the choice of changing the file association to
reference this version of TBOOK.
Setup will add the file associations (FLI and FLC) for
the Autodesk Animator driver to the [MCI Extesions] section
of WIN.INI. You can install this driver from Disk 1 of
MediaBlitz installation set using the Windows Control Panel.
Additional environment files
=============================
MediaBlitz adds two .INI files during setup. ASYM.INI points to
common files used by Asymetrix applications. MDIABLTZ.INI
stores the paths to each MediaBlitz application and the values
defined in the MediaBlitz Preferences dialog box.
Notes on Music Mentor 1.02 Here are a few last minute notes on Music Mentor that could not be included the user's manual. Using Music Mentor with Recording Session If you are using Music Mentor with Midisoft Recording Session for Windows, make sure you set up Recording Session's MIDI interface parameters before switching to Session from within Music Mentor. Also, make sure that Session's MIDI settings with regard to the choice of MIDI driver and the use of the MIDI Mapper are the same as Music Mentor's MIDI settings. If you are running Windows 3.1, Music Mentor's default MIDI setting is to use the Multimedia MIDI Driver. Any time Mentor is using the Multimedia MIDI Driver it will also be using the MIDI Mapper. For more information on this, see the section in your user's manual on setting up Music Mentor for MIDI. Running on Two Megabyte Machines If you experience performance or reliability problems using Music Mentor on machines with two megabytes of memory, try the following things: Turn off SMARTDRV by taking the line that launches SMARTDRV out of your AUTOEXEC.BAT file and restarting your computer. On two meg machines, we do not recommend using Music Mentor when SMARTDRV is on. Free up as much memory as possible before launching Music Mentor. Ideally, only the Program Manager should be open. If you have an MPU-401-compatible MIDI device, use the Midisoft MIDI Driver instead of the Multimedia MIDI Driver in Music Mentor's MIDI Setup dialog. The Midisoft MIDI Driver is faster and more efficient. Running at Screen Resolutions Larger Than 640 x 480 Music Mentor was designed for use at 640 x 480. If you don't want to run Music Mentor in this resolution, preferring instead to run at 800 x 600 or 1024 x 768, you should be aware that the size of the text will change, and in some cases may be difficult to read because it is so small. Some makers of high resolution video cards include larger-than- normal screen fonts for use in these situations. We have found that on some systems, this may cause some of the text in Music Mentor to "spill out" over its field boundaries. Text is either cut off or overruns another graphic object. The problem is caused because you have switched to different screen fonts in order to make better use of the increased resolutions. You always have the option, of course, of not switching to different screen fonts, and in this case, Music Mentor should look fine. The only screen font Music Mentor uses is Helvetica, so it is only when a new font is substituted for Helvetica that this becomes a problem. Another Font-Related Issue Users who run Music Mentor in conjunction with on-the-fly type scaling software like Adobe Type Manager and Bitstream FaceLift may notice that some text looks slightly out of place on screen. This happens when the type scaling program takes over the "rasterization" (on-screen drawing) of the Helvetica screen font. Though we have not come across any situations where this is a serious problem that prevents use of the program, if it bothers you you can probably correct it by altering the sizes of screen fonts that your type scaling program will draw and returning the drawing of the affected Helvetica fonts back over to Windows itself.
REVISED CATALOG: INFO ON THE ON-LINE BIBLE COLLEGE
Full Page Color Driver Fix ========================== These instructions apply only to using the Full Page Color virtual screen. If you are using a board based on the TSENG ET4000 chip you will have to install the special program on the More Windows VGA screen driver disk. It is called TSENG.COM. It should be installed in the AUTOEXEC.BAT file in the root directory of the drive you boot DOS from. The directions are shown below. If you have any questions concerning these instructions please call Technical Support at 510-426-5355 8AM-5PM PST. Some of the boards which use the TSENG chip set are: 1. Orchid Prodesigner 2 2. Speedstar VGA Directions on Installing the TSENG Fix ====================================== 1. Copy TSENG.COM from the More Windows disk to the root directory of the drive you boot from. Most likely C:\ 2. Use SYSEDIT or Notepad to open your AUTOEXEC.BAT file. 3. Add the following to your AUTOEXEC.BAT file TSENG CLS 4. Reboot the computer to install this driver.
Autodesk Multimedia Explorer 1.0
Readme.doc MEREADME-1
October 7, 1991
Please see the Autodesk Multimedia Explorer(TM) READ ME FIRST
Installation Card included in the package for information on how to
install the software from Microsoft(R) Windows(TM) or DOS. The
instructions on the card supersede all installation procedures and
disk content tables described in the Autodesk Animator Reference
Manual and in the Autodesk Animation Player for Windows Reference
Manual.
Demo Files
==========
Besides the package contents listed on the READ ME FIRST
installation card, there are hundreds of additional animation and
image files included on the CD-ROM. You can view these demos directly
from the CD by going to the root directory of the CD and typing DEMO.
If you are running under Microsoft Windows and install Autodesk
Animation Player for Windows, the program automatically creates icons
for the demos. Six icons appear in your Animation window: 2D Animations,
ALL Animations (this demo takes about 2 hours to run), Misc Animations,
Animator Clips, AutoShade Animations, and 3D Studio Animations.
Double-click on one of these icons to run the associated demo.
The playback speed of the demo flics depends on the speed setting with
which they were saved and on the speed of your CD-ROM drive. They
include sound, which you can hear if you have Microsoft Windows with
Multimedia Extensions and sound equipment.
Autodesk Animation Player for Windows
=====================================
This section contains information pertinent to Autodesk Animation
Player(TM) for Windows version 1.0.
Converting an Animation File
----------------------------
It is recommended that you convert animation files to be used with
Autodesk Animation Player for Windows with the Convert Anim
option, located in the File menu. This may help maintain the
correct colors in an animation, and eliminate "flashes" that can
sometimes occur between animations while playing a script.
Microsoft Windows uses 20 of the 256 colors available for the
Windows desktop, leaving only 236 colors available for your
animation. Convert Anim converts the animation palette to a palette
that is more compatible with Windows. For more information about
Convert Anim, see the Autodesk Animation Player for Windows
Reference Manual.
Errata
------
Autodesk Animation Player for Windows Reference Manual, page 26:
o Videodisc. If you want to play a portion of a videodisc,
select this device. Identify the sound by specifying a
start time and stop time in this format:
from pos to pos
In this case, pos (position) is a time in hh:mm:ss format.
Your videodisc player might display position in this format,
or it might display position as a frame number. To convert
from frame numbers to time, divide by 30 to get seconds, and
then convert to hh:mm:ss format. The from position must
be at least 1 second. For example, enter
from 0:0:1 to 0:4:0
to play 4 minutes on the disc.
Autodesk Animator 1.02
======================
This section includes information pertinent to Autodesk
Animator(TM) 1.02 that was not included in the Autodesk Animator
Reference Manual.
MACRO: A LEARNING TOOL
----------------------
Included in your package is the macro recording Welcome.rec.
Use this macro to explore step by step many Autodesk
Animator tools and techniques; you can watch an animation being
created. Some of the animation effects you will see are optical
motions, color cycling, shadowing, and various ink and tool image-
enhancing effects.
Follow these steps to run the Welcome.rec macro:
First, load the Welcome.rec macro:
1. Select Record from the Extra menu.
The Macro Recording menu appears.
2. Select Files from the Macro Recording menu.
The Files panel appears.
3. Click on Load.
A panel listing available macro files appears.
4. Click on the Welcome.rec macro file (the filename
appears in the file entry box.)
5. Click on OK and right-click on the drawing screen
to return to the Home panel.
Next, run the Welcome.rec macro:
1. Select Record from the Extra menu.
2. Select Use Macro from the Macro Recording menu.
The Welcome.rec macro begins.
Press [Esc] to stop the macro any time during playback.
After the macro has ended, play back the animation:
o Go to the Home panel at the bottom of the screen and
click on the set of double-arrows in the middle of the
panel.
Note: When using the Repeat Macro command for a macro that
changes the default tools and inks, be sure to include a
Reset at the end of the macro when it is created. This will
ensure that the slider bar is set to the proper position for
accurate tool/ink selection during playback.
SCRIPT FILE MOVIES
------------------
The file Movies is a sample script file that plays animations
in a continual loop. You can edit this file to include any
filenames you want, to create your own movie. Assuming
aaplay.exe is in the same directory, type AAPLAY MOVIES to run
the script.
Note: Press [Esc] to stop the file Movies any time while it's
playing. This script file is not compatible with Autodesk
Animation Player for Windows.
For more information on script files, see appendix E, "The Autodesk
Animator Player" in the Autodesk Animator Reference Manual.
PLAYER - LOCKED KEYBOARD
-------------------------
If you locked your keyboard during playback (if you used a Ctrl-
combination), pressing the [Break] key temporarily halts
playback. To resume playback, press the spacebar.
SUMMASKETCH TABLET
------------------
If you installed Autodesk Animator for a SummaSketch tablet and
want to run the Converter program with a tablet as well, you should
put the Autodesk Animator configuration file (aa.cfg) in the same
directory as convert.exe.
You cannot install a SummaSketch Tablet to run with the Player
program. Use the Keyboard Alternatives if you have a tablet, or
install a mouse to select Menu items in the Player.
When switching between a Stylus and a Puck, you must reconfigure
from the Extra Menu. This ensures that the buttons on each
device perform correctly.
VGA/MCGA DISPLAYS
-----------------
Sometimes when you start your computer, the VGA mode of a display
card is not correctly initiated. If this hardware mishap
occurs, Autodesk Animator cannot recognize your display card as
a VGA and this error message appears: "Not a VGA/MCGA
display. Sorry."
If you have a VGA display, first be sure that it is correctly
installed. Next, power down your system and try again.
TEMPORARY DRIVES AND VDISKS
---------------------------
When you use a temp disk or a VDISK that is full, a requestor box
appears and you can choose a new drive. If that disk is
dangerously full, an alert box appears. If you continue to use the
program at this point without securing disk space, satisfactory
results are not guaranteed.
MARQUEE BOX
-----------
When using functions that require the marquee box, it will appear
on screen as moving dashes. It will also appear as a solid color
if the palette has been squeezed to a very small number. If you
want to return the marquee box to moving dashes, turn on the FIT
and ALL buttons and select Default from the Value Menu.
KEY COLOR
---------
Clear from the Pic Menu will set the screen to the current key
color. New from the Flic Menu will keep the screen set at color
register 0, black.
FONTS
-----
The font army24.fnt supplied on Disk #4 is an ALL CAPS font. This
font is not meant to be used for upper- and lowercase text.
PANELS
------
When looping back through a series of panels, an alert box appears
asking you to r-click on screen rather than clicking on the panel
button to return to the panel you want.
TWEENING
--------
Pg. 109 in the Autodesk Animator Reference Manual and pg. 100 in
the Autodesk Animator Tutorial states that the start shape should
have as many or more points than the end shape. This has been
updated in Autodesk Animator v1.01. The start shape can have more
points or less points than the end shape.
ERROR MESSAGES
--------------
"Drive (x) has (x) Free Bytes. 200000 Recommended for Error Free
Operation. Use (x) anyway?"
This occurs when a temp drive has less than 200k available during
an operation or a temp drive with less than 200k is chosen as a
result of a file truncated error message. Select a drive that
contains over 200,000 bytes free. If you decided to use the full
temp drive anyway, proper functionality is not guaranteed.
"Shape too big to fill"
This message occurs when tweening or rendering a filled shape in
the optics panel that is too large. Decrease the size of the shape
and render it once again.
"Cannot create directory entry"
This occurs when the maximum number of files for a directory has
been reached. Delete unnecessary files and try again.
FLIMAKER
--------
The script filename is the minimum requirement for a valid command
line argument following the Flimaker command. For example:
flimaker [-v] <filelist>
A file extension is not required within a script file. Autodesk
Animator Flimaker searches first for a .rnd then a .sld file. If it
finds neither, it reports ">>[filename] File not found,
skipping..." and continues to read the file.
NOTE: If both .rnd and .sld files are included in the script
without extensions and have the same filename, Autodesk Animator
Flimaker processes them both as .rnd files.
You can add comments to the script file with an * at the beginning
and end to identify the comment line. For example:
* this script file results in a four-frame .fli file.*
Once a script file has been processed, the total number of frames
compiled is displayed. For example:
"4 frames compiled. Autodesk Animator file
<filename>.fli successfully created."
You can install the AutoShade(R) RDVGA ADI(R) driver and use it
with the Record option in AutoShade to create .rnd files. This
driver automatically sets the correct shaderdfile settings.
If an incorrect shaderdfile rendering is offered, a message appears
and a bat file is created that sets the proper shaderdfile setting
in the current directory.
"**ERROR: Improper render file format. [640,444,1,1,256,15,16]
** Please replace bad.rnd **
Autodesk Animator Flimaker 1.01 can process .rnd files
produced by AutoShade 1.1x, regardless of computer type. The
.rnd file MUST be a VGA 320x200x256 resolution file.
Please refer to appendix F in your "Autodesk Animator Reference
Manual."
A message appears if the program doesn't find a file during
processing. The script file continues to compile as long as files
are found.
">>[fliname] File not found, skipping.......
Nothing to process."
AUTODESK ANIMATOR CONVERTER
---------------------------
The Autodesk Animator Converter utility program requires a mouse or
a SummaSketch tablet to run. See appendix D "The Autodesk Animator
Converter" for more information on using the Converter program.
You can load 256 PCX files into Autodesk Animator Converter.
You can load large PCX files into Autodesk Animator Converter.
Then you can use the slide option to capture a portion of the image
on screen that you want to save to a file.
NOTE: The largest possible PCX files have been accommodated.
We don't recommend that you use the Scale option to render
large PCX files. You might have memory problems.
You cannot load .gif files larger than 640x480 into Autodesk
Animator Converter; you cannot load scanner files containing very
few columns and many rows (i.e., files produced by hand scanners
might not convert successfully).
TRADEMARKS
----------
The following trademarks of Autodesk, Inc. are registered in the
U.S. Patent and Trademark Office: AutoShade and ADI.
The following are also Autodesk trademarks: Autodesk Animator and
Autodesk Animator Flimaker.
COPYRIGHT
---------
RESTRICTED RIGHTS LEGEND
Use, duplication, or disclosure by the
Government is subject to restrictions
as set forth in subparagraph (c) (1) (ii)
of the Rights in Technical Data and
Computer Software clause at DFARS
252.227-7013.
In order to allow Autorun for Windows to work with a variety of program managers, it now looks for the profile string 'PMClass' in the ARW.INI file. The default string is 'PROGMAN'. If you use a program manager other than Microsoft's Program Manager, then this profile string must be set to the window's CLASS name. To aid you in finding out what the class name is, a utility is provided (PEEPER.EXE). Simply run PEEPER in windows. From the system menu, select the 'Peer into window' option. The cursor changes to a set of peering eyes. When the cursor crosses a window, that windows title and class name will appear in PEEPER's window. When the correct title/class name appears, click the left mouse button. This will freeze the names and discontinue the peering process. At this point you can use notepad or whatever to edit the ARW.INI file, adding or changing as required. The file's contents should look something like : [Events] Windows=3002 Active=0 View=2002 PMClass=NewClassName The order of the profile strings is not important and the strings are not case sensitive.
Notes on Music Mentor 1.02 Here are a few last minute notes on Music Mentor that could not be included the user's manual. Using Music Mentor with Recording Session If you are using Music Mentor with Midisoft Recording Session for Windows, make sure you set up Recording Session's MIDI interface parameters before switching to Session from within Music Mentor. Also, make sure that Session's MIDI settings with regard to the choice of MIDI driver and the use of the MIDI Mapper are the same as Music Mentor's MIDI settings. If you are running Windows 3.1, Music Mentor's default MIDI setting is to use the Multimedia MIDI Driver. Any time Mentor is using the Multimedia MIDI Driver it will also be using the MIDI Mapper. For more information on this, see the section in your user's manual on setting up Music Mentor for MIDI. Running on Two Megabyte Machines If you experience performance or reliability problems using Music Mentor on machines with two megabytes of memory, try the following things: Turn off SMARTDRV by taking the line that launches SMARTDRV out of your AUTOEXEC.BAT file and restarting your computer. On two meg machines, we do not recommend using Music Mentor when SMARTDRV is on. Free up as much memory as possible before launching Music Mentor. Ideally, only the Program Manager should be open. If you have an MPU-401-compatible MIDI device, use the Midisoft MIDI Driver instead of the Multimedia MIDI Driver in Music Mentor's MIDI Setup dialog. The Midisoft MIDI Driver is faster and more efficient. Running at Screen Resolutions Larger Than 640 x 480 Music Mentor was designed for use at 640 x 480. If you don't want to run Music Mentor in this resolution, preferring instead to run at 800 x 600 or 1024 x 768, you should be aware that the size of the text will change, and in some cases may be difficult to read because it is so small. Some makers of high resolution video cards include larger-than- normal screen fonts for use in these situations. We have found that on some systems, this may cause some of the text in Music Mentor to "spill out" over its field boundaries. Text is either cut off or overruns another graphic object. The problem is caused because you have switched to different screen fonts in order to make better use of the increased resolutions. You always have the option, of course, of not switching to different screen fonts, and in this case, Music Mentor should look fine. The only screen font Music Mentor uses is Helvetica, so it is only when a new font is substituted for Helvetica that this becomes a problem. Another Font-Related Issue Users who run Music Mentor in conjunction with on-the-fly type scaling software like Adobe Type Manager and Bitstream FaceLift may notice that some text looks slightly out of place on screen. This happens when the type scaling program takes over the "rasterization" (on-screen drawing) of the Helvetica screen font. Though we have not come across any situations where this is a serious problem that prevents use of the program, if it bothers you you can probably correct it by altering the sizes of screen fonts that your type scaling program will draw and returning the drawing of the affected Helvetica fonts back over to Windows itself.
Release Notes for EZSound FX Version 2.01 SECTIONS 1) Using EZSound FX, Windows 3.1, and the Sound Blaster Pro or Pro AudioSpectrum Plus/16 2) Removing EZSound FX from your system. ============================================================================= 1) Using EZ Sound FX with Windows 3.1 and the Sound Blaster Pro or the Mediavision Pro AudioSpectrum 16 or Pro AudioSpectrum Plus ============================================================================= The new version of the Sound Blaster Pro and the Pro AudioSpectrum Plus and Pro AudioSpectrum 16 use a new synthesis chip from Yamaha called the OPL3. The Multimedia drivers put this chip into a mode that is not compatible with EZSound FX. To let EZSound know that you are using one of these boards you must select the Multimedia Extensions/Win 3.1 option in PANELFX which is specific to your board. If you are using the Sound Blaster Pro you should be using the Board Type: Multimedia Extensions/Win 3.1 SBPro If you are using the Mediavision Pro AudioSpectrum Plus or 16 you should be using the Board Type: Multimedia Extensions/Win 3.1 PAS+/16 All other boards use the standard Board Type: Multimedia Extensions/Win 3.1 If you have a board which is using the Multimedia Extensions and doesn't work with Music FX, it is possible that it is using the OPL3. You can let EZSound know that your board has an OPL3 by editing the SFSOUND.INI file. Under the section [FM] you will have to change the OPL3=No line to OPL3=Yes. ============================================================================= 2) Removing EZSound FX from the SYSTEM.INI file. ============================================================================= If you are having problems and would like to remove EZ SOUND FX, from your system you must change two entries in your SYSTEM.INI file found in your WINDOWS directory. First: Under the section [boot] you will find 3 lines that read something like the following: ;EZSound FX Driver sound.drv=sfsound.drv ;sound.drv=mmsound.drv Remove the commented ";EZSound FX Driver" line and the following line with the sound.drv=sfsound.drv or sound.drv=sfsnd.drv. Also remove the ; on the 3rd line to reenable your old sound driver. Second Under the section [386Enh] you will find 2 lines that read ; The line device=vclmad.386 is used by EZSound FX device=vclmad.386 Delete these 2 lines from the file. This will remove all system dependent drivers from your system and return you to your original setup for Windows. You will also find a file in your EZSound installation directory called SETUP.LOG which contains a list of all files which were installed on your system by EZSound FX.
Release Notes for EZSound FX Version 2.01 SECTIONS 1) Using EZSound FX, Windows 3.1, and the Sound Blaster Pro or Pro AudioSpectrum Plus/16 2) Removing EZSound FX from your system. ============================================================================= 1) Using EZ Sound FX with Windows 3.1 and the Sound Blaster Pro or the Mediavision Pro AudioSpectrum 16 or Pro AudioSpectrum Plus ============================================================================= The new version of the Sound Blaster Pro and the Pro AudioSpectrum Plus and Pro AudioSpectrum 16 use a new synthesis chip from Yamaha called the OPL3. The Multimedia drivers put this chip into a mode that is not compatible with EZSound FX. To let EZSound know that you are using one of these boards you must select the Multimedia Extensions/Win 3.1 option in PANELFX which is specific to your board. If you are using the Sound Blaster Pro you should be using the Board Type: Multimedia Extensions/Win 3.1 SBPro If you are using the Mediavision Pro AudioSpectrum Plus or 16 you should be using the Board Type: Multimedia Extensions/Win 3.1 PAS+/16 All other boards use the standard Board Type: Multimedia Extensions/Win 3.1 If you have a board which is using the Multimedia Extensions and doesn't work with Music FX, it is possible that it is using the OPL3. You can let EZSound know that your board has an OPL3 by editing the SFSOUND.INI file. Under the section [FM] you will have to change the OPL3=No line to OPL3=Yes. ============================================================================= 2) Removing EZSound FX from the SYSTEM.INI file. ============================================================================= If you are having problems and would like to remove EZ SOUND FX, from your system you must change two entries in your SYSTEM.INI file found in your WINDOWS directory. First: Under the section [boot] you will find 3 lines that read something like the following: ;EZSound FX Driver sound.drv=sfsound.drv ;sound.drv=mmsound.drv Remove the commented ";EZSound FX Driver" line and the following line with the sound.drv=sfsound.drv or sound.drv=sfsnd.drv. Also remove the ; on the 3rd line to reenable your old sound driver. Second Under the section [386Enh] you will find 2 lines that read ; The line device=vclmad.386 is used by EZSound FX device=vclmad.386 Delete these 2 lines from the file. This will remove all system dependent drivers from your system and return you to your original setup for Windows. You will also find a file in your EZSound installation directory called SETUP.LOG which contains a list of all files which were installed on your system by EZSound FX.
PLEASE READ
-------------------------------------------------
By using the following Windows 3.1 Driver Library (the "Software"), you
are hereby agreeing to the included license agreement. Please review
the file LICENSE.TXT.
The PC Speaker driver may not produce high quality sound on all computer
systems. The performance of the PC Speaker driver is largely dependent
upon the hardware itself. Microsoft does not guarantee that the speaker
driver will work with all computer systems.
"Enable interrupts during playback" Setup Option
------------------------------------------------
By default, the PC Speaker driver disables all interrupts while playing
sounds for optimal sound quality. As a result, you will noticed that
the mouse cursor, keyboard or other processes will not respond while
sounds are being played through the PC Speaker. You can set PC Speaker
to enable interrupts for serial port activity and mouse movements in the
PC Speaker setup dialog, at the expense of sound quality.
To set this option:
- Run Control Panel
- Open the Drivers icon
- Select the Sound Driver for PC Speaker from
the list of Installed Drivers
- Choose Setup
- Select or clear the Enable interrupts during
playback check box.
Note: It may be necessary to select option when running some
communication applications.
Using the PC Speaker driver with AST systems
--------------------------------------------
If you experience problems using the PC Speaker driver on an AST system,
you should contact AST Technical Support at 1-800-727-1278.
Using Media Player with the PC Speaker driver
---------------------------------------------
The version of Media Player provided with Windows 3.1 does not play
*.WAV files with the PC Speaker driver. To play *.WAV files, you should
use Sound Recorder. Windows 3.1 will install the Sound Recorder icon in
your Accessories Program Manager group.
Speaker Driver Setup
The Speaker Driver Setup push button in the Options Window works ONLY with
the speaker driver installed with Icon Hear-It. When loading, if
Icon Hear-It detects a sound board or speaker driver already on your
system, it will not allow you to use it Speaker Setup.
If you do not have a sound board or other speaker driver installed
and you still can't access the Speaker Driver Setup, you need to edit your
system.ini file and remove the line :
Wave= speakerdrivername
from underneath the [Drivers] section. The next time Icon Hear-It loads,
it will write a new "Wave = " with its own speaker driver.
MCS Stereo ReadMe File
===============================================================================
Version 1.02
The MIDI files included with MCS Stereo assume "Extended" MIDI Patch Maps.
Make sure you have chosen the Extended MIDI Patch Map in the Midi Mapper
Applet of the Control Panel. The Control Panel may be accessed through the
"Main" group in the Program Manager or by pressing the "Settings" button in
the MCS Stereo MIDI Player.
Normally, if a portion of a WAV file is highlighted, the "Edit Sample" dialog
box will only play the selected area. To play the entire file without
deselecting the currently marked area, hold the <Ctrl> key while pressing the
"Play" button in the "Edit Sample" dialog box.
------------------------------------------------------------------------------
Version 1.01
Environment switching buttons were added in the Standard Environment and the
Enhanced Remote control.
The scan buttons for the Remote Control Digital Recorder were changed to skip
buttons. Used to skip forward or backward in the current playlist. (Changed
to maintain functionality consistency between Digital Recorder, CD Player and
MIDI Player controls in the Remote Control)
------------------------------------------------------------------------------
The manual incorrectly states that Animotion technical support is available on
Compuserve in the Multimedia Vendors forum. The forum has instead been set up
in the MIDI Vendors forum. To access Animotion technical support through
Compuserve, type GO ANIMOTION at any CIS prompt. The BBS number and technical
support policies are still as stated in the manual.
------------------------------------------------------------------------------
A new section has been added to the MCSINIT.INI file since the manual was
printed. You should find the following entries which were not described in
the manual:
[EditSample]
FastGraph=0
InitialDisplayTime=10
AlwaysCollect=0
These entries were added to improve the capabilities of the Edit Sample
dialog box, which is used for editing WAV files.
The first entry, "FastGraph", selects the algorithm used to display the
waveform. By default, FastGraph is set to 0. Change the entry to
"FastGraph=1" to enable the FastGraph option.
If you are using the product on a slower machine or editing large files, you
may find the FastGraph option provides faster display performance.
However, the FastGraph option is not as accurate in it's display of the
waveform.
The "InitialDisplayTime" parameter specifies the largest amount of time (in
seconds) that are displayed when the file is initially loaded. This may be
adjusted from 1 to 999 seconds.
The "AlwaysCollect" parameter is used to control the memory optimization
functions of the Edit Sample dialog box. The default value is 0, and should
only be changed if a file seems to "hang" after modifications which alter
the file's size.
------------------------------------------------------------------------------
Additional information for users who have attached the output of their
CD-ROM drive to the Auxiliary port of their sound card.
If your sound board has a CD audio line-in port, yet you have
found it necessary to attach the audio output of the CD-ROM drive to
the auxiliary line-in port, you will find it impossible to control
the CD Volume in the Enhanced CD player. This section will detail
how to make MCS Stereo best utilize your sound board's auxliliary
line-in to control the volume of your CD player.
The "Volume" section on page 3-23 of the MCS Stereo User's Manual
describes a procedure which assigns the auxiliary port of the sound
card to MCS Stereo's logical CD volume control. After this operation
the Enhanced CD Player's volume controls will adjust the volume of the
sound card's auxiliary port as will the buttons labeled "CD" on the Remote
Control Mixer. Because both the Standard Environment Mixer and the
Enhanced Mixer rely, not on MCS Stereo's logical associations, but instead
on the patch names as reported by the sound card's mixer driver, the
user must still adjust the "Aux" sliders to change the CD's volume
when using either the Standard Environment Mixer or the Enhanced Mixer.
Alternatively, the user may also change the default patch names that
the mixer driver will use to correspond to the changes made in
the MCSINIT.INI file. We think that this is a very reasonable
solution that most users would prefer.
The following instructions are meant for those who have the problem
described above. These instructions are to supercede those given on
page 3-23 of the manual.
Step 1. Install MCS Stereo if has not been previously installed.
--------------------------------------------------------------------
Step 2. Switch MCS Stereo's logical auxiliary and CD associations
---------------------------------------------------------------------
a) Use Windows' notepad (or any other editor which will write
straight ASCII files) and load "MCSINIT.INI" from the directory
containing Windows.
b) Locate the [LINECONFIG] section and examine the entries
labled "CD_AUDIO" and "AUXILIARY", then swap the line
numbers associated with both devices.
Example: If your sound board is a Media Vision Pro Audio Spectrum,
then you would make AUXILIARY=LINEIN03 and CD_AUDIO=LINEIN02 as
demonstrated below.
[LINECONFIG]
PRODUCT=Media Vision Pro Audio/CDPC
MASTER=LINEOUT00
RECORDIN=LINEOUT01
CD_AUDIO=LINEIN03 <---------- CD_AUDIO=LINEIN02
DIGITAL_RECORDER=LINEIN05 |
MIDI=LINEIN00 |
AUXILIARY=LINEIN02 <---------- AUXILIARY=LINEIN03
MICROPHONE=LINEIN04
Step 3. Changing the default mixer driver patch names.
-------------------------------------------------------
a) Search for the [drivers] section in the file "SYSTEM.INI" located
in the directory where Windows has been installed. Locate the
"mixer" entry in the [drivers] section and note the filename
that has been assigned to the "mixer" entry.
b) Use an editor capable of writing straight ASCII to edit "WIN.INI"
located in the directory where Windows was installed. Find the
section name corresponding to the filename found in step 3a.
c) After finding the appropriate section name, search the section's
"LineIn" entries for the patch names of "AUX" and "CD".
(The patch names appear in the first field immediately after
the '=' on each line.) Next, swap the numbers associated with
these patches.
Example: If your sound board is a Media Vision Pro Audio Spectrum,
then you would replace the '3' in the line that contains
"LineIn3=AUX" to '4' and you would replace the '4' in the line
that contains "LineIn4=CD" to '3' as show below.
------------------ Change this '3' to '4'
|
[mvmixer.drv] |
LineIn1=SYNTH | MUS] PLAY L= 0% R= 0% @=0000
LineIn2=MIXER | MIX] PLAY L= 91% R= 91% @=0000
LineIn3=AUX <--- AUX| PLAY L= 77% R= 77% @=0000
LineIn4=CD <--- CDA| PLAY L= 46% R= 46% @=0000
LineIn5=MIC | MIC| PLAY L= 60% R= 60% @=0000
LineIn6=WAVE | WAV] PLAY L= 0% R= 0% @=0000
LineIn7=SPKR | SPK] RECORD L= 13% R= 23% @=0000
LineOut1=MASTER \ AMP| PLAY L= 56% R= 56% @=0000
StereoEnhance=ON \
Loudness=OFF \
Bass= 66 \---------------- Change this '4' to '3'
Treble= 75
SaveSettingsOnWindowsExit=YES
--------------------------------------------------------------------------------
Wired For Sound Release Notes 1.00 This version has 52 sounds recorded at 11Khz. Call the order hotline at 1-800-338-2629 or 1-800-426-8288 CA for a list of available sounds. Ask about our Business Preferences. What if my sounds don't play loud enough? Try repositioning your PC speaker so that it is close to the front of the PC. You can tape it to an edge that gives you the best sound. If you still have problems we would recommend that you purchase The Sound Source from Walt Disney and call Aristosoft about the additional software disk which supports it. What if my sounds play to slow or to fast? 1. This could be because the turbo button on your PC was changed while in the windows session. Wired for Sound senses the speed of your PC automatically at the start of your windows session. 2. It could be that Wired for Sound has not sensed your PC speed correctly. To force Wired for Sound to sense to a preset speed add the following text to your WIN.INI file: [DSOUND] Volume=100 Shift=0 EDelayValue=30 To change the speed of playback, adjust EDelayValue until the play back is to your liking. You need to restart Windows each time you change it.
Release Notes for Legacy Version 1.1
Memory Requirements
Legacy is designed to run in Windows 3.0 protected mode (standard or
386 enhanced). For optimal performance when running Legacy, your
system should have 2MB of memory. Your system should have an
additional 1MB of memory if you run DDE with Legacy. You should also
have an additional 1MB of memory for each application, such
as a spreadsheet application, that you use concurrently with Legacy.
Beyond these requirements, your system should have an additional 1MB of
memory if you use Legacy in a network environment.
Legacy Registration
During setup, you will be asked for your registration number. After
installation, you can find this number by choosing About Legacy from
the Help pulldown menu.
WIN.INI
If you remove the SHARE command in your AUTOEXEC.BAT file, a
message will appear when you open Legacy. To remove the message,
open your WIN.INI file and scroll to the Legacy section. Change
the ShareWarning entry to ShareWarning=0.
Conserving Disk Space
The online tutorial uses 1.4MB of disk space and the
templates use 600K of disk space. To conserve disk space,
you can remove the templates and/or the online tutorials. You can
re-install the templates and online tutorials at any time without
having to completely re-install Legacy.
Removing and Reinstalling Windows
Legacy copies a needed graphics file, MGXWMF.DRV, into the
WINDOWS\SYSTEM directory. If you ever delete Windows (which includes
this directory), you should make a copy of the MGXWMF.DRV file first,
then copy it back into the WINDOWS\SYSTEM directory after you reinstall
Windows. Otherwise, you'll have to reinstall Legacy after you reinstall
Windows.
Running Legacy on the Network Version of Windows
The network version of Windows does not have a system directory. If
you are installing Legacy with the network version of Windows, you must
edit the setup.inf file to remove the reference to the system directory.
1. From the File Manager, choose Run from the File menu.
2. In the Command Line, type the word "notepad" followed by a space
and the word "setup.inf"
3. Choose OK.
The setup.inf file appears on the screen.
4. In the middle of the file, the following command appears:
EXPAND 3:MGXWMF.DRZ W:SYSTEM\MGXWMF.DRV (for 3-1/2" disks)
or
EXPAND 2:MGXWMF.DRZ W:SYSTEM\MGXWMF.DRV (for 5-1/4" disks)
Delete the word SYSTEM\ by positioning the insertion point to the
right of the slash mark and backspacing until the insertion point
is next to the colon after the W.
5. The command should now read as follows:
EXPAND 3:MGXWFM.DRZ W:MGXWMF.DRV (for 3-1/2" disks)
or
EXPAND 2:MGXWFM.DRZ W:MGXWMF.DRV (for 5-1/4" disks)
Running the Tutorial
You must run the Tutorial from within Legacy.
Reference Manual
Trademark Page
Addition:
Add the following citations,
"Novell is a registered trademark and NetWare is a trademark of
Novell, Inc.
MultiMate Advantage and Multimate Advantage II are trademarks of
Ashton-Tate Corporation.
3Com is a registered trademark and 3+Open are trademarks of
3Com Corporation.
THE PROXIMITY/WILLIAM COLLINS SONS & CO. LTD. HYPHENATION
SYSTEM.
(C)Copyright 1985
William Collins Sons & Co. Ltd.
Legal & Medical Supplement (C)Copyright 1982
Merriam-Webster, Inc.
(C)Copyright 1982, 1985 All Rights Reserved
Proximity Technology Inc."
CH 1 Starting Legacy
Page 1-6
Addition:
Add the following note, "If you open an existing Legacy
document from DOS or by using the Run command in the File
menu, the software searches for the document in the
following manner. First it checks whether the document
exists in the current directory; then it checks whether the
document exists in the Chapter directory set under
Preferences. If the document does not exist in either of
those two locations, a new Legacy document with that name
is opened in the Chapter directory, if one is set. If a
Chapter directory is not set, a new Legacy document with
that name is opened in the current directory. If you want
to open a document that exists in an alternate location,
change to the directory it is located in, or type a
full pathname."
Page 1-11
Correction:
The language selected under Preferences determines the
hyphenation patterns, lexicon, and thesaurus that are used.
Under "Setting Automatic Hyphenation," the third bullet should
read, "Hyphenation points are determined by checking a set of
patterns developed for a particular language. The set of
patterns used to calculate hyphenation points is determined by
the language you've selected under Preferences. If you've chosen
a language for which hyphenation patterns aren't available, the
following message appears when you start typing in the document:
Cannot find hyphenation file [drive:]\pathname\filename
If hyphenation patterns aren't available, the document won't be
hyphenated."
Page 1-14
Addition:
Add the following section.
"Setting the Language
You can specify the language you want used when checking
spelling, hyphenation patterns, and when using the thesaurus.
If you've selected a language other than the default and you
don't have the spelling, hyphenation, or thesaurus files needed
for the alternate language, when you use these features, a
message appears indicating that the files are not installed.
1. In the File menu, choose Preferences.
The Preferences dialog box appears.
2. Choose Language.
The Language Preference dialog box appears.
3. Click the down arrow in the Language box.
The drop-down list box appears.
4. Select the language you want to use.
5. Choose OK to close the Language Preferences dialog box.
6. OK
Note: You may purchase additional language supplements, called
'Lexicons,' from NBI supplies."
CH 2 Viewing Documents
Page 2-2
Correction:
When you click the Next and Previous Page icons, the insertion
point moves to the next or previous page. The last sentence in
the last procedure should read, "The insertion point appears on
the next page."
Page 2-3
Correction:
The Go To options move the insertion point. Under "Using the Go
To Options," the second sentence in the introductory paragraph
should read, "When you use these options, the insertion point
moves to the specified page or location."
Page 2-4
Addition:
Add the following note, "If a frame is selected and you use
a Go To option to move to a different page, the specified page
will be selected (or a dependent frame will be selected if it
has an X and Y origin of zero). An exception to this is when
you choose the Link command in the Format menu and then use
a Go To option to move to a different page. In this case, the
specified page will not be selected, which allows you to
select the frame that you want to be linked to the previous
frame."
Addition:
Add the following note, "When you use a Go To option to move
the insertion point to another page, and the specified page
contains a dependent frame at the top of the page, the
insertion point will be placed on the page frame in the first
available space. If the dependent frame covers most of the
space on a page frame so that there is no space for the
insertion point to appear, the insertion point will be placed
under the dependent frame. If the dependent frame has an X and Y
origin of zero, the insertion point will be placed in the dependent
frame.
Page 2-18
Addition:
Under "Referring to Copyright Information," add the following to
the end of the introduction, "Copyright information for the
thesaurus and spelling dictionaries is available through the
Copyright command in the Control menus of the Thesaurus and
Check Spelling dialog boxes."
CH 3 Editing and Formatting Text
Page 3-3
Correction:
You use the scroll arrows or scroll box to move to a different
page without moving the insertion point. Under "Selecting Text
Across Pages," step 2 should read, "Use the scroll arrows or
scroll box to move to the end of the text you want to select."
Page 3-14
Correction:
With Windows 3.0, dithering of text is supported on some
monochrome printers. Under "Changing Text Color," the first
sentence of the second note should read, "With monochrome
monitors and/or some printers, dithering isn't possible with
text nor is display of non-dithered colors like red."
Page 3-19
Correction:
The keyboard assignment listed for a blocked hyphen is
incorrect. Under "Inserting a Blocked Hyphen," step 4 in
the procedure should read, "Choose Blocked Hyphen
(Shift+Ctrl+H)."
Correction:
The keyboard assignment listed for a discretionary hyphen is
incorrect. Under "Inserting a Discretionary Hyphen," step
4 in the procedure should read, "Choose Discretionary Hyphen
(Ctrl+H)."
Page 3-20
Correction:
The keyboard assignment listed for positive kerning is
incorrect. Under "Kerning with Pre-Set Amounts of Space,"
step 4 in the procedure should read, "Choose Positive Kerning
(Ctrl and the Equals key) or Negative Kerning (Ctrl and the Minus
key)."
CH 4 Using Word-Related Utilities
Page 4-7
Correction:
The graphic of the Check Spelling dialog box is incorrect. The
command buttons have been rearranged and a Done button has been
added.
Page 4-8
Correction:
You can also close the Check Spelling dialog box by choosing
the Done command button. Step 4 in the first procedure should
read, "Choose Done."
Page 4-12
Correction:
The language selected under Preferences determines the
hyphenation patterns, lexicon, and thesaurus that are used.
Under "Setting Automatic Hyphenation," the second bullet should
read, "Hyphenation points are determined by checking a set of
patterns developed for a particular language. The set of
patterns used to calculate hyphenation points is determined by
the language you've selected under Preferences. If you've chosen
a language for which hyphenation patterns aren't available, the
following message appears when you choose Automatic Hyphenation:
Cannot find hyphenation file [drive:]\pathname\filename
If hyphenation patterns aren't available, the document won't be
hyphenated."
Page 4-13
Correction:
Under "Updating Hyphenation," the last sentence in the second
paragraph should read, "The hyphenated text will rehyphenate as
you change the layout of the page; however, any new text you add
will not be hyphenated."
Page 4-14
Addition:
Add the following paragraph at the end of the introduction, "For
non-U.S. versions, the thesaurus provides only synonyms.
Consequently, in the dialog box, the drop-down list box that
allows you to choose between synonyms, antonyms, etc., is
removed. In addition, because definitions are not provided,
the definitions list box is removed."
CH 5 Using Styles
Page 5-25
Correction:
With Windows 3.0, dithering of text is supported on some
monochrome printers. Under "Creating a Style," the first
sentence of the second note should read, "With monochrome
monitors and/or some printers, dithering isn't possible with
text (including dropped initial characters) nor is display
of non-dithered colors like red."
CH 7 Using Properties
Page 7-15
Addition:
Add the following note, "Both automatic scrolling options
are deactivated in documents that are upgraded from Legend
2.x to Legacy."
CH 9 Creating a Table of Contents, Index, or List
Page 9-9
Correction:
Index entries with Automatic Page # activated and index
entries with Automatic Page # deactivated can both be
included in a single document. Remove the last paragraph.
CH 11 Generating Graphics
Page 11-10
Correction:
Under "Creating a White or Black Object," change the default
fill pattern from "solid black" to "transparent." You can
replace the transparent fill pattern in the drop-down list
box with white or black.
Page 11-16
Addition:
Add the following note, "If you select a text object and
open the Format Character dialog box, none of the emphasis
check boxes will be selected, regardless of the current
emphasis option of the text object."
Page 11-18
Addition:
Under "Resizing Objects by Using the Mouse," add the following
note, "You can change an ellipse to a circle, a rectangle to a
square, an arc to a circular arc, or a line to a 45 degree line
by pressing the Ctrl key while dragging a corner handle of the
object."
CH 12 Importing and Exporting
Page 12-2
Addition:
In the note, add the following after the entry Informix
SmartWare(R) II, "(import only)."
Page 12-3
Correction:
The Display Warnings option is available only for DCA/RFT,
OASys, and Informix SmartWare II. In the first bullet, the
second and third sentences should read, "This option is
available only when importing DCA/RFT, OASys, and Informix
SmartWare II. When importing these text formats, the Display
Warnings check box is not checked in the default setting."
In the remainder of the bullet, delete references to other
import types.
Page 12-6
Addition:
Add the following note, "Certain files may not have
distinguishing characteristics that allow them to be recognized
as a particular type of file. Examples are GSA Navy DIF and
WordPerfect 4.x. When importing such files, you may encounter
the following message:
Source file not correct import file type. Continue with import?
Choosing Yes will allow the import to continue."
Correction:
Remove the second note and replace it with the following,
"In most cases, when importing text, both proportional and
non-proportional fonts are imported as Courier. The font
size of the imported text may be slightly different from
the font size of the original text."
Page 12-7
Addition:
After "Importing Formatted ASCII," add the following subhead
and paragraph:
"Importing and Exporting ANSI Text
You may import or export ANSI text. This may be especially
desirable when you are working with international text,
because the ANSI character set contains more international
characters than the ASCII set."
Page 12-8
Addition:
Under "Importing OASys," add the following note, "If you
import an OASys document and the document contains special
characters created using the ANSI character numbers 168,
174, 178, 179, 184, or 185, those special characters will
not be imported. However, they can be re-created in Legacy."
Page 12-14
Correction:
Replace the first sentence of the first note with the
following, "If no cells are selected and the table contains
content, the following message appears after step 5: If
you continue then the current table frame content will be
lost."
Page 12-17
Addition:
Add the following note, "A variety of graphics applications
can produce files in Computer Graphics Metafile (CGM) format.
The following are application-specific strategies for preparing
CGM graphics for import into Legacy.
Windows Applications
With the Windows 3.0 versions of graphics applications, for best
results, use the Clipboard to cut and paste between the
application and Legacy.
Micrografx(R) Designer(TM) 3.0
--If you export the graphic as a .CGM file, use the CALS export
type.
--.DRW files import more accurately than .CGM files.
COREL DRAW
--When exporting a graphic as a .CGM file, choose the options
'Selected Objects Only' and 'Preserve All Artistic Attributes.'
Arts and Letters(R)
--There are three CGM export types plus various resolutions.
All work well. Using a higher resolution will create a
larger export file and therefore use more disk space. You can
experiment for best results.
Non-Windows Applications
Lotus(R) Freelance(R) Plus
--.CGM files import to Legacy successfully. You may need to
adjust the colors of objects after importing.
Harvard Graphics(TM)
--.CGM files exported from the main application and from Draw
Partner(TM) import into Legacy successfully. You may need to
adjust the colors of objects after importing.
Image Builder(TM) 2.1
--There are two CGM export options: 'Filled Fonts' and
'Hardware Fonts.' Filled Fonts preserve the fonts used in
Image Builder. Use this option for the most accurate import
of text objects. Use Hardware Fonts if you want Legacy to
recognize the imported objects as text objects."
Addition:
Add the following note, "When importing graphics, a blank
message box can appear if the system is low on memory. To
remove the message box, click the OK button that appears at
the bottom of the message box. Due to the low memory, the
graphic may only be partially imported. If the import is
incomplete, you can choose Select All in the Edit menu and
then the Del key to delete the import. Then you can take
steps to release more memory and re-import the graphic.
To release more memory to the system, close any unnecessary
applications that are running and/or restart Windows. In
addition, if you are running on a network, run stand-alone
instead."
Addition:
Add the following note, "If you create text within Designer or
Charisma(TM) and import the file, the text can't be edited and
will not print correctly. There are two ways you can use text
with Designer and Charisma graphics. The first method can be
used only if you have outline fonts installed on your system and
you're working with Designer 3.01 or Charisma 2.0. With this
method, you create the text in an editor such as Notepad and cut
and paste the text into Designer or Charisma. Then you
change the text to the outline font you want, save the file,
and import it into Legacy.
The second method is to create the Designer or Charisma graphic
without text. After you import the graphic, you can add the
text by placing transparent Legacy text frames over the graphic
frame."
Page 12-18
Correction:
In the first note, the extension for Microsoft Paint Bitmap is
".BMP." Add the entry "Microsoft Paint" and give it
the extension ".MSP."
Page 12-23
Addition:
Add the following note, "If a Legacy document has DDE links
to multiple applications and you allow Legacy to open each
of those applications, be sure you have enough memory to
run all of the applications simultaneously.
If a Legacy document has DDE links to, for example, an Excel
spreadsheet and chart, two Excel applications will be opened
(one for the spreadsheet and one for the chart). You can
avoid having two Excel applications opened by opening the
Excel application before you open Legacy. When you open
Excel, also open all of the linked files that you'll be
using in the Legacy document."
CH 13 Using Mail Merge and Print
Page 13-3
Correction:
The graphic of the Select Mail Database dialog box is
incorrect. In the dialog box, the option Use Field Names from
First Record should read, "Use First Record for Mail Variable
Names."
Page 13-3
Correction:
You don't have to choose Use First Record for Mail Variable Names
prior to choosing View in the Select Mail Database dialog box.
In the second procedure, the first step should read, "Optionally,
choose Use First Record for Mail Variable Names."
Correction:
After choosing View, all of the fields are displayed in the list
box. In the second procedure, the second to last sentence
should be replaced with, "The total number of fields appears
next to Number of Fields. The list box displays all of the
fields."
Page 13-6
Addition:
Add the following Note: "If you print a document to a
printer directly connected to your computer through an
RS232C port, the document may not print if the Transmission
Retry time set in the Windows Control Panel is too small.
The Transmission Retry number represents the interval (in
seconds) that the computer will wait before it quits
sending a document to the printer. The default
Transmission Retry time may be too small if you are
trying to print documents containing complicated drawings,
color/gray scale bitmap images, and/or vector fonts such as
Script, Modern, and Roman. The Transmission Retry time
depends on the size and complexity of the document, the
interface between the printer and the computer (serial or
parallel), and the amount of memory the printer has. The
Transmission Retry box is accessed by double clicking on
the Printers icon in the Windows Control Panel and then
choosing Configure."
Add the following Note: "The 1.1 version of Legacy offers
improved print performance of graphics on the HP LaserJet.
To take advantage of this enhancement, you will need to
delete any graphics you imported while working in 1.0 and
re-import them from their original source."
Add the following Note: "If you encounter a problem printing
text, repaginate or scroll through the document so that all
graphics frames are displayed, then save the document. Text
should then print correctly."
Designing High-Impact Documents
Three additional templates are provided in the template directory that
are not summarized in chapter 5. They are
~KYBD.CHP allows you to create keyboard quick reference
cards that list the styles and property sets
that you've assigned to function keys.
~REPORT5.CHP provides another design for a report.
~TRIP.CHP provides a design to use to summarize the
results of a business trip.
The template ~ENVEL.CHP is set up for an HP LaserJet
Series II printer using a PCL(R)-HP print driver. If you have a
different printer, you need to change the locations of the frames for
the inside and mailing addresses so that they are aligned properly
for the type of printer that you have.
The following additions/corrections are to the summaries of the styles
and property sets used in specific templates. The templates themselves
are correct and require no modification.
CH 5 Using the Legacy Templates
Page 5-15
Addition:
For the style "first para," add
"Positioning: Space Above 36 pts"
Page 5-19
Correction:
For the style "time/topic," change to
"Font: Tms Rmn 18pt Bold"
Page 5-21
Addition:
For the style "agenda," add
"Positioning: Space Above 36pts"
For the style "time," add
"Positioning: Space Below 12pts"
Page 5-25
Addition:
For the style "agenda," add
"Positioning: Space Below 2.9 pts"
For the style "date," add
"Positioning: Space Below 21.6 pts"
For the style "day," add
"Font: Underline"
For the style "time/item," add
"Positioning: Left Indent 1", Space Below 10.1 pts"
Correction:
Change the style "time/items" to "time/item"
5-27
Addition:
For the style "titletext," add the word "Custom" after
"Ruling Lines"
5-33
Correction:
For the style "title," change to
"Positioning: Space Below 28 pts; Alignment Centered"
5-41
Correction:
Remove the property set "Text"
5-43
Addition:
For the property set "Header," add the word "Custom" after
"Border"
Page 5-45
Addition:
For the style "third.level," add
"Special Effects--Bullet: Hyphen"
Page 5-47
Addition:
For the style "center.title," add
"Positioning: Space Below 21.6pts"
Correction:
For the property set "PageText," change Border--Outer Line to
"Outer Line 4pts"
Page 5-49
Correction:
For the property set "PageText," change Border--Outer Line to
"Outer Line 4pts"
Page 5-51
Addition:
For the style "bullet," add
"Positioning: Space Below 2pts"
For the style "date," add
"Color: Intensity 100%"
For the style "mainhead," add
"Color: Intensity 100%"
For the style "tagline," add
"Color: Intensity 100%"
Page 5-53
Correction:
For the property set "PageText," change Columns: Second to
"Columns: Second 2.350"
SMALLTALK/V (R) WINDOWS 1.1
README.TXT file
Important Information - Please Read Me
--------------------------------------
This file contains important information about the contents of
Smalltalk/V Windows 1.1 files and some details about the software
not covered in the handbook. This file addresses the following
topics:
I. Installation of Smalltalk/V Windows 1.1
II. Contents of the Smalltalk/V Windows 1.1 files
III. MicroSoft Windows 3.0 Configuration
IV. Known Problems
An accompanying file, DEVTOPIX.TXT contains very important information
regarding packaging an executable for delivery as an application.
DEVTOPIX.TXT contains these sections:
- Notes to Smalltalk/V Windows 1.0 users
- New features of Smalltalk/V Windows 1.1
- New public methods of Smalltalk/V Windows 1.1
- Tips, Tricks and Solutions
- Sending messages from non-Smalltalk/V application to Smalltalk/V
- Application Delivery vs Development
- API Calls Using the Pascal and C Calling Conventions
- Starting Up a Standalone Application
- Command Line Arguments
- Changing Standalone Application Icon and Startup Screen
- Cross-language Debugging
- Saving the Image
I. INSTALLATION OF SMALLTALK/V WINDOWS 1.1
Smalltalk/V Windows 1.1 is supplied on a single 3.5 inch diskette and
on two 5.25 inch diskettes in compressed format. Both 3.5 inch and
5.25 inch disks are included.
To install Smalltalk/V Windows 1.1, first bring up Microsoft Windows.
Insert Disk 1 (of either size) into a disk drive, such as A:. Next,
select the "Run..." menu item from the Microsoft Windows Program Manager
File menu. Now enter the following text:
a:\install
into the prompter box and click the "OK" button. The install program
will ask for the directory (default is C:\VWIN on your hard disk)
into which to expand and install the files. IF YOU ARE UPGRADING TO
SMALLTALK/V WINDOWS 1.1 FROM SMALLTALK/V WINDOWS 1.0, YOU SHOULD
SUPPLY A DIRECTORY NAME OTHER THAN YOUR SMALLTALK/V WINDOWS 1.0
DIRECTORY. For information on upgrading to Smalltalk/V Windows 1.1
from Smalltalk/V Windows 1.0, refer to the 'Notes to Smalltalk/V
Windows 1.0 Users' section in DEVTOPIX.TXT.
A subdirectory of the new Smalltalk/V Windows 1.1 directory, called
TUTORIAL, will be created to contain the Smalltalk/V tutorial files,
and a subdirectory called EXAMPLES will be created to contain the
Smalltalk/V example files. If you want to put the .DLL files in a
different directory, you may copy them to that directory using the
File Manager. However you must make sure that the correct directory
is mentioned in your PATH environment variable.
If the installation is successful, a new Program Group with the title
Smalltalk/V will be created. It contains an icon labeled Smalltalk/V.
To run Smalltalk/V Windows, you simply double-click on this icon.
II. CONTENTS OF THE SMALLTALK/V WINDOWS 1.1 FILES
After installation, files are organized on your hard disk as follows:
Your chosen Smalltalk/V Windows directory: (C:\VWIN is the default):
readme.txt - this file
devtopix.txt - application development topics
v.exe - your image of objects
vw.exe - run this to start Smalltalk development
vwbas11.dll - code for Smalltalk/V Windows 1.1 base classes
vwdev11.dll - code for Smalltalk/V Windows 1.1 development
classes
vwsrc11.dll - Smalltalk/V Windows 1.1 Smalltalk source code
vwfloat.dll - floating point primitive methods when no math chip
vwabort.dll - the abort procedure for PostScript printing
vwdlgs.dll - dialog box resources used by Smalltalk/V
vwsignon.dll - Smalltalk/V's sign-on dialog box
vwfont.dll - the procedure for enumerating fonts
vwvm11.dll - Smalltalk/V Windows 1.1 primitive methods
examples subdirectory:
286towin.txt - differences between Smalltalk/V Windows 1.1 and
V 286
apic.txt - examples of C API calls with C calling convention
diff.txt - list of methods that have been changed since
Smalltalk/V Windows version 1.0
dialogs sub-subdirectory:
Contains dialog box examples and "file-inable" FormattedEntryField
and FormattedStaticText classes.
frmttden.txt - formatted edit field documentation
frmttden.cls - formatted edit field source code
frmttdst.txt - formatted static text documentation
frmttdst.cls - formatted static text source code
incometx.st - income tax installation code
incometx.txt - income tax documenation
incometx.cls - income tax source code
txflngdl.cls - tax filing dialog source code (used by income tax)
txincmdl.cls - tax income dialog source code (used by income tax)
txlbldlg.cls - tax label dialog source code (used by income tax)
vhclslsd.txt - vehicle sales dialog documentation
vhclslsd.st - vehicle sales dialog installation code
vhclslsd.cls - vehicle sales dialog source code
turtldlg.txt - turtle dialog documentation
turtldlg.st - turtle dialog installation code
turtldlg.cls - turtle dialog source code
contrldm.txt - control demo documentation and source code
iconedit sub-subdirectory:
Contains the Smalltalk icon editor. This icon editor greatly simplifies
the task of changing the Smalltalk application icon.
iconedit.txt - icon editor documentation
iconedit.st - icon editor installation code
iconedtr.cls - icon editor source code
icon.cls - icon class source code
vwdlgs sub-subdirectory:
Contains sample resource-only DLL source code. vwdlgs.dll is the
actual resource-only (dialog-only) DLL used by Smalltalk/V Windows 1.1.
vwdlgs.txt - documentation on vwdlgs.dll
vwdlgs. - make file for vwdlgs.dll
vwdlgs.dlg - dialog source file for vwdlgs.dll
vwdlgs.rc - resource compiler source file for vwdlgs.dll
vwdlgs.c - c source file for vwdlgs.dll
vwdlgs.def - definition file for constructing vwdlgs.dll
vwsignon sub-subdirectory:
Contains the source code for signon.dll. This source code can
be modified to produce a custom signon screen.
vwsignon.txt - documentation on vwsignon.dll
vwsignon. - make file for vwsignon.dll
vwsignon.c - c source file for vwsignon.dll
vwsignon.dlg - dialog source file for vwsignon.dll
vwsignon.rc - resource compiler source file for vwsignon.dll
vwsignon.def - definition file for constructing vwsignon.dll
libentry.obj - DLL entry routine object file
balloon.ico - balloon icon displayed in signon dialog
dashbord sub-subdirectory:
This is a control panel of dials and gauges that are interrelated such
that when one dial/gauge is changed with the mouse, the others are
changed according to their predefined interrelationships. This uses DDE
to connect to Microsoft Excel. Files in the "dashbord" directory are:
dashbord.txt - documentation and installation info
cntrlapp.cls - control apparatus source code
dashbord.cls - dashboard source code
dashbord.st - dashboard installation code
dash.doc - Microsoft Word document for demo dashboard DDE
dash.xls - Microsoft Excel document for demo DDE
dde sub-subdirectory:
This is for Dynamic Data Exchange documentation and examples.
dde.txt - description of DDE example
vwindde.doc - Microsoft Word document to install Smalltalk
expression evaluator
ddetstcl.cls - DDE example client source code
ddetstsr.cls - DDE example server source code
polygon sub-subdirectory:
This demo shows ViewManager managing multiple windows.
polygon.txt - description for installing polygon demo
plygnsnd.cls - polygon sound view
polygnvw.cls - polygon ViewManager
prim sub-subdirectory:
The following files are used in constructing primitives written in C
to be accessed from Smalltalk. The C source code for the vwfloat.dll
is included as an example of user-defined primitives.
fixdptrs.h - C variables for fixed object pointers
objects.h - C structs defining object formats
userprim.txt - more information about user primitives
userprim.mac - C macros for object access
vwfloat.c - C source for floating point emulation
vwfloat.def - definition file for constructing DLL
vwfloat - vwfloat.dll make file
libentry.asm - Windows Dynamic Link Library entry routine
fredrwng sub-subdirectory:
Drawing editors - there are two complete window applications, a freehand
drawing paint program and a low-level bit editor. Files are:
fredrwng.txt - documentation and installation information
biteditr.cls - bit editor source code
fredrwng.cls - free drawing source code
fredrwpn.cls - FreeDrawingPane class
fredrwng.st - free drawing installation code
puzzle15 sub-subdirectory:
A simple game which uses GraphPanes and outline fonts. The files are:
puzzle15.cls - number puzzle source code
puzzle15.txt - puzzle installation code
tutorial subdirectory:
The following tutorial files are to be accessed with the Disk Browser
while reading the Tutorial and Programming Handbook. The number in
the file name identifies the chapter in the book where the tutorial
is presented.
chapter.2 - Smalltalk/V environment
chapter.3 - objects and messages
chapter.4 - control structures
chapter.5 - classes and methods
chapter.6 - inheritance
chapter.7 - streams and collections
chapter.8 - debugging
chapter.9 - graphics
chapter.10 - windows
chapter.11 - object-oriented development
chapter.12 - application development: case study
The following are used as part of the tutorial. The number in the file
name usually identifies a book chapter where the source code is used.
animal6.st - first look at the animal hierarchy
animal7.st - animals with pattern matching
animal10.st - animals in a window
class10.st - animal class definitions
class12.1in - sales window first part
class12.2in - sales window second part
class12.3in - sales window third part
comevent.cls -sales comm class definition (chapter 12)
comevnts.in - sales comm object creation (chapter 12)
dog1.bmp - bitmaps for the dog pictures
dog2.bmp - bitmaps for the dog pictures
dog3.bmp - bitmaps for the dog pictures
dog4.bmp - bitmaps for the dog pictures
habitat7.st - a habitat for animals
network7.st - a network of nodes
network9.st - a network of nodes with graphics
nodes7.st - the network nodes
nodes9.st - the network nodes with graphics
striplf.pc - line feed example file
window1.st - first window example (chapter 10)
window2.st - second window example (chapter 10)
window3.st - third window example (chapter 10)
window4.st - fourth window example (chapter 10)
window5.st - fifth window example (chapter 10)
wrdindx8.st - class WordIndex, to learn about the debugger
III. MICROSOFT WINDOWS 3.0 CONFIGURATION
Microsoft Windows must be configured to run either in enhanced or
standard mode. Smalltalk/V Windows will not run in real mode.
If you have less than 4 MB of RAM total, you should free up as much
memory as possible by removing any RAM disks, or by reducing the size
of your disk-caching buffer (refer to Optimizing Windows in the
Microsoft Windows User's Guide).
If you have an 80386 or 80486 CPU, we recommend that you install a
permanent swap file. This will improve the performance of Smalltalk/V
and other Windows applications, especially on systems with 4 MB or
less of RAM (refer to Optimizing Windows in the Microsoft Windows
User's Guide).
IV. KNOWN PROBLEMS
We are aware of a rare problem where Microsoft Windows can display a
message box reporting 'Insufficient Memory' when trying to run an
application, after exiting Smalltalk. If this occurs, continue to
try to load the application; it will eventually load.
Copyright 1991 Digitalk, Inc.
◎ 改版说明 ◎
1.52版 :
1.增加了在选电话号码时可一次多笔选择
2.修正印表机拦截後产生的档案有会格式错误的问题
3.加快印表速度
2.00版 : 5/25/92
1.增加定时传送功能
2.可在倚天,震汉,国乔 三种中文下使用
3.增加详细状态显示
4.减少执行所需之记忆体
◎ 改版說明 ◎
1.52版 :
1.增加了在選電話號碼時可一次多筆選擇
2.修正印表機攔截後產生的檔案有會格式錯誤的問題
3.加快印表速度
2.00版 : 5/25/92
1.增加定時傳送功能
2.可在倚天,震漢,國喬 三種中文下使用
3.增加詳細狀態顯示
4.減少執行所需之記憶体
************************************************************************
Traveling Software, Inc.
18702 North Creek Parkway
Bothell, Washington 98011
(206) 483-8088
************************************************************************
The Latest About LapLink Pro
Version 4.00
Welcome to LapLink Pro. The following notes include information that was
not available at the time the manual was printed. It also contains hints
for running LapLink Pro with specific kinds of hardware and software.
************************************************************************
If you're a new LapLink owner, be sure to mail in your registration card
to ensure that you will be notified of future releases of LapLink Pro.
************************************************************************
TABLE OF CONTENTS
I. Modem Phone Numbers--Using Access Prefix and Account Suffix
II. How the File Display Filters Affect Deletes, Copies, and Moves
III. Hidden Files, Read-only Files, and System Files
IV. Remote Install Tips and Notes
V. Compression and the Selected Port
VI. Using LapLink Pro with Other Traveling Software Products
VII. Hardware Information
A. When LapLink Pro Does Not Recognize a Mouse or Port
B. The Xircom Parallel Port Multiplexor
C. Problems with Parallel Connections
D. Incompatible or Problem Modems
E. System Clock Speed
VIII. Miscellaneous Manual Corrections
IX. Screen Savers and Memory-Resident Programs (TSRs)
X. When File Lists Are Not Sorted
XI. Working with Windows 3.0
A. Installing LapLink Pro in Windows
B. Suggestions for Working in the 386 Enhanced Mode
C. Running LapLink Pro in the Background
D. Windows and 9600 Baud Modems
XII. Getting Technical Support
XIII. Making Suggestions to Improve LapLink Pro
------------------------------------------------------------------------
I. MODEM PHONE NUMBERS--USING ACCESS PREFIX AND ACCOUNT SUFFIX
Since the LapLink Pro User's guide was written, two features have been
added to the Dial Modem dialog: Access Prefix and Account Suffix. You
can find instructions for using them in LapLink's on-line help.
Basically, these features let you create long phone numbers. When you
check the [ ] Use boxes, LapLink Pro attaches any number in the Access
Prefix record to the beginning of the number and any number in Account
Suffix to the end. It dials the resulting number.
Use Access Prefix to enter a number to dial out of a hotel or office--
"9," is common. Or, use it to enter an often used area code or country
code.
Use Account Suffix to enter a credit card number. Or, if your office
phone system requires you to type in an account number for long distance
calls, type it in here. If you have a WATS access code, it too could be
entered as an Account Suffix.
CAUTION: WHENEVER YOU DISPLAY THE DIAL MODEM DIALOG, THESE NUMBERS ARE
DISPLAYED. TAKE ANY PRECAUTIONS NECESSARY TO PREVENT UNAUTHORIZED
PERSONS FROM OBTAINING YOUR ACCOUNT NUMBERS.
To add the numbers, select the appropriate line and choose the <Modify>
button. In both numbers, commas may be used to pause dialing while the
phone system catches up to the modem. You can use as many commas as
needed for the length of the required pause.
------------------------------------------------------------------------
II. HOW THE FILE DISPLAY FILTERS AFFECT DELETES, COPIES, AND MOVES
The "File Display Options" command (Options menu) lets you show or hide
files. Files cannot be selected if they are hidden. Since hidden files
cannot be selected, they also cannot be copied, moved, or deleted.
This also holds true when you are working with directories and
subdirectories. (Subdirectories are indirectly selected when the Include
Lower Level Subdirectories copy option is enabled.)
For example, suppose you have set the "File Display Options" to display
only *.EXE and *.COM. If you select a directory and delete it, only the
.EXE and .COM files will be deleted. The directory structure and any
other files will remain in place.
If you want to delete, copy, or move an ENTIRE, directory, choose "File
Display Options" and check Show All Files first.
------------------------------------------------------------------------
III. HIDDEN FILES, READ-ONLY FILES, AND SYSTEM FILES
In order to protect important files, DOS allows files to have
"attributes." These include:
* Hidden--The file does not show up when you use the DIR command
(without special switches) and is not deleted when you type DEL *.*.
* Read-only--The file cannot be deleted or edited but does show up
with the DIR command.
* System--The file has the same characteristics as a hidden file (it's
not normally shown or deleted) and is essential to the functioning
of DOS or another program.
Since LapLink Pro's main function is to simplify file management, it
lets you copy, move, and delete these types of files.
In a file list, hidden files are followed by an H; Read-only by an R;
and System by an S. WHEN YOU SEE ANY OF THESE CHARACTERS FOLLOWING A
FILE NAME, ALWAYS BE SURE YOU DO NOT NEED THE FILE BEFORE YOU DELETE IT.
In the file list mode, only one letter--H, R, or S--can be shown. If a
file has more than one attribute, an S will be shown before an H or R;
and an H will be shown before an R. For example if a file is both hidden
and read-only it will show as H; if a file has all three attributes, it
will show as S.
Because hidden files and system files are so rare, LapLink Pro does not
have a copy option that deals with them. They are displayed and can be
deleted as easily as other files.
The only files that are not displayed in a LapLink file list are those
that have both the hidden and system attribute AND are located in the
root directory of the disk. This is to protect two important files that
are always in the root directory of a bootable MS-DOS disk: IO.SYS and
MSDOS.SYS (they have slightly different names if you are using IBM DOS).
Because these files must be present in order to boot the disk, LapLink
Pro does not show them, or allow you to copy or delete them.
Read-only files are not as rare, and LapLink Pro offers two ways to
protect them. First, any time you make a selection and delete, LapLink
Pro will check the selection to see if it contains any read-only files.
If so, a warning box asks if you are sure you want to go on with the
deletion. Second, there is a copy option called Overwrite Read-only
Files. When the option is ON, a file WILL BE ALLOWED to copy over the
read-only file. When this option is OFF, LapLink Pro will not
automatically allow you to copy or move a file onto a read-only file of
the same name. Instead, the files are placed in a list from which you
must force the file transfer.
------------------------------------------------------------------------
IV. REMOTE INSTALL TIPS AND NOTES
Remote DOS Commands--When you use remote install, a user must type
commands on the remote PC. These commands are documented both in the
LapLink Pro User's Guide and in the instructions you see when you issue
the "Remote Install" command. If you have a problem with remote install,
always check to make sure the commands have been typed exactly as they
are shown in the instructions.
The remote user should be aware that some commands that he or she types
prevent the DOS prompt (C:>, for example) from displaying. And, the
final command, CTTY COMx, will make the remote PC appear to "lock up" as
the process begins.
Baud Rates--If you can't make remote install work over a cable, try
reducing the baud rate. You should reduce the rate from Automatic to
57,600 baud.
For modem remote installs, the transfer of the LapLink Pro program takes
place at 2400 or 1200 baud, even if both modems are capable of higher
speeds. This is because the initial modem connection is established by
the DOS MODE command, and once a modem connection is established the
speed cannot be changed. After the remote install, if both modems are
capable of higher speeds, you might want to hang up and change to a
higher speed (the remote user must also do this). Then, re-establish the
connection by dialing normally.
When LapLink is Already on the Target--If LapLink is already on the
target and the program is available on the DOS path, the remote's copy
of LapLink Pro will start and the remote install will not take place.
Over a modem, however, the resulting connection may not be seen. The
solution is to hang up. Have the remote user start LapLink Pro and you
can then dial the connection normally.
------------------------------------------------------------------------
V. COMPRESSION AND THE SELECTED PORT
Even though you can manually turn the Compressed Data Transfer copy
option on or off, LapLink Pro may override your selection to enhance
transfer speeds. Specifically, if you have the option on and you are
using a parallel port in the accelerated (8-bit) mode, compression is
ignored (the parallel accelerated mode is more efficient by itself).
If you are running LapLink Pro under low memory conditions, compression
may be turned off automatically. The option will remain off until you
turn it on again with the "Copy Options" command.
When you are using a modem it is almost always more efficient to run
with compression on.
------------------------------------------------------------------------
VI. USING LAPLINK PRO WITH OTHER TRAVELING SOFTWARE PRODUCTS
Because WinConnect, DeskLink, and the LapLink III Device Driver compete
with LapLink Pro for port usage, using them with LapLink Pro may require
experimentation. In most cases, you need to delete the LapLink Pro
configuration file (LLPRO.CFG), start the other program, and then start
LapLink Pro. This causes LapLink Pro to re-check all available ports and
it then only uses the ports that are not currently in use by the other
program. (Note: When you delete LLPRO.CFG all Copy Options and Control
Panel settings are returned to their default values.) If you need help
with this procedure, call Traveling Software technical support.
Battery Watch Pro is compatible with LapLink Pro, but as with other
TSRs, you should avoid popping up the Battery Watch screen during a file
transfer.
------------------------------------------------------------------------
VII. HARDWARE INFORMATION
------------------------------------------------------------------------
A. When LapLink Pro Does Not Recognize a Mouse or Port
When you exit LapLink Pro, it saves a configuration file called
LLPRO.CFG. Among other things, this file saves the current port
information as shown by the "Port/Modem Setup" command.
This means that if you install a mouse AFTER using LapLink Pro, the
mouse will not be available the next time you start LapLink Pro. To
enable the mouse, choose the "Port/Modem Setup" command and select the
port to which the mouse is connected. Then, choose <Reset>. LapLink Pro
will check the port and show that it is using the mouse.
If you have been using a mouse but now want to use the port for LapLink,
use the same procedure.
For best results, you should also exit LapLink Pro and turn your PC off
and back on again.
------------------------------------------------------------------------
B. The Xircom Parallel Port Multiplexor
LapLink Pro has been designed to work with parallel ports that have a
Xircom Parallel Port Multiplexor. However, the system must first be set
up properly.
First, the LapLink parallel cable must be attached to the "A" port of
the multiplexor.
Second, you must make a change with the "Port/Modem Setup" command:
Choose the command, and in the Port/Modem Setup dialog, select the
parallel port with the multiplexor. In the next dialog place an x in the
Force Standard (4-bit) mode check box and choose <OK>. If you do not
make this change, the Multiplexor may try to switch between the printer
and the cable during the middle of a copy.
------------------------------------------------------------------------
C. Problems with Parallel Connections
Regardless of the communication program, some combinations of laptop PCs
cannot connect with each other, and a few cannot communicate in parallel
mode at all. Serial mode must be used with these combinations.
When you try to connect these problem PCs in parallel, LapLink Pro may
display a message--"Attempting to Connect"--and the system may "lock
up." One or both of the PCs may need to be restarted.
If you have problems connecting between two particular machines contact
Traveling Software technical support.
------------------------------------------------------------------------
D. Incompatible or Problem Modems
LapLink Pro is incompatible with modems that run at speeds less the
1,200 baud.
In addition, some external modems WILL NOT accept a modem remote
install. Internal modems do not exhibit this behavior. But, due to the
way the DSR pin is powered, these external modems will not accept data
when the remote user types: TYPE CON >COMx.
The easiest solution for PCs that use these modems is to install LapLink
Pro directly from disk. You may also be able to prepare a remote modem
to accept a remote install by using a communication program other than
the DOS MODE command. For further information, call Traveling Software
Technical Support.
------------------------------------------------------------------------
E. System Clock Speed
In very rare instances, after running LapLink Pro, the system clock on a
few PC models (including the PS/2 Model 50) seems to speed up. That is,
the time advances too quickly. If your PC seems to "gain time" after
running LapLink Pro, restart and exit LapLink Pro again. This usually
returns the speed to normal. Rebooting your PC will have the same
effect.
------------------------------------------------------------------------
VIII. MISCELLANEOUS MANUAL ADDITIONS AND CORRECTIONS
Using the "Make Directory" command.
The manual erroneously states that you can type a path when you create a
directory. This is not true. You can only type a valid directory name
(up to 8 characters optionally followed by a period and up to 3 more.)
The new directory is ALWAYS created as a subdirectory of the current
directory.
Using the "Clone Drive" command.
The "Clone Drive" command will not proceed if there is a possibility
that it will cause a previously bootable target disk to become
unbootable. This is a function of the DOS versions the disks use and
whether the drive is used to boot (start-up) the PC. The table below
shows you when Clone Drive will work:
Source ----> Target DOS Version Clone Drive Works?
-------- -------- ----------- ------------------
Boot Boot Same yes
Boot non-Boot Any yes
non-Boot non-Boot Any yes
Boot Boot Different no
non-Boot Boot Any no
Remote Install Over Modems
During remote install, the clock on the local PC will lose time. If this
occurs, you can use the TIME command from the DOS command line to reset
your PC's clock. Rebooting the PC may perform the same function. See
your PC and DOS manual for more information.
In addition, sometimes the way a remote modem is set up will prevent
LapLink from remotely installing. Check the LapLink Pro Modem Tips and
Reference Guide for tips on preparing a remote modem for remote
installation.
Changing Your PC's Name
When you change your PC's name, the change will not be reflected on the
remote PCs during the current LapLink session. The next time you use
LapLink Pro, the new name will be shown.
Using the "Synchronize" Command
During Synchronize, copies are made in both directions and LapLink needs
to check BOTH PCs to see if there is enough room to hold the files.
First, one PC is checked; if there is enough room, the newer files are
copied. Then, the process proceeds in the opposite direction.
Because of this two-step operation, Synchronize will be halted if either
drive becomes full. This can happen during the first copy or the second.
Running Setup Programs Directly from LapLink Pro
CAUTION: DO NOT USE LAPLINK PRO TO LAUNCH A SETUP PROGRAM THAT IS USED
TO CHANGE CMOS MEMORY. YOUR PC MAY BECOME UNBOOTABLE.
For example, most laptop setup programs let you change power-saving
measures and the type of installed hard disk. Always exit LapLink Pro
before you use such a program. Setup programs are meant to be run stand-
alone and often reboot your PC. They should not be run from most shell
programs.
Using [Ctrl+Break] to Exit LapLink Pro
If LapLink Pro "locks up" you may still be able to exit the program by
pressing [Ctrl+Break]. If you use this procedure however, any options
changes that you have made in the current session will not be saved.
------------------------------------------------------------------------
IX. Screen Savers and Memory-Resident Programs (TSRs)
LapLink Pro allows most TSRs to pop-up during its operation. However,
you should not pop-up such programs during an active file transfer. The
PCs may become disconnected and the file transfer halted.
If you are using a screen saving device--either a software program that
you have purchased or the power-saving feature built into a laptop--the
screen saver may interfere with LapLink Pro. For example, if a remote
user has a connection with your PC and the screen saver activates, it
may cause the connection to be dropped.
This is because some screen savers block access to ports and others take
CPU (processing) power away from LapLink Pro.
If you want to set up a PC to receive remote modem calls, you should not
run a screen-saving program while LapLink Pro is active.
------------------------------------------------------------------------
X. When File Lists Are Not Sorted
Under some conditions your file lists may not be sorted, even if you
have specified a sort order with the "File Display Options" command
(Options menu). Two factors contribute to this condition: 1) The amount
of memory available to LapLink Pro, which you can check with the "System
Information" command in the Options menu; and 2) the number of files in
the directory. (In low memory situations, any directory containing more
than 150 to 200 files may be susceptible; with the maximum amount of
memory, failure to sort will not occur until there are about 2000
files.)
When a file list cannot be sorted, the files are displayed in the order
that they occur on your disk. Because of the lack of sorting, the quick
method of finding a file in the list is disabled--i.e. you can't press a
letter key to move to the file you want to find. However, the "Find
File" command (Disk menu) will still function. If you wish to select a
number of files that begin with the same letter but the list is
unsorted, you can use the "Select By" command on the Select menu.
------------------------------------------------------------------------
XI. WORKING WITH WINDOWS 3.0
------------------------------------------------------------------------
A. Adding LapLink Pro to Windows
1. The LapLink Pro installation program installs two files especially
for use with Windows 3.0: LLPRO.PIF and LLPRO.ICO. First, ensure
that the files are located in the same directory as LLPRO.EXE. If
they are not, copy the files from your LapLink Pro distribution
disk.
2. Next, start Windows. From the Program Manager, choose the program
group (window) into which you want to place LapLink Pro. Then issue
the "New" command from the File menu. In the next dialog, choose
"Program Item" (the default) and OK. The "Program Item Properties"
dialog box is displayed next.
3. In the Command Line box, type LLPRO.PIF. Or, if you didn't allow the
install program to add the LapLink Pro directory to your PATH
statement, type the path and the file name--for example,
C:\LLPRO\LLPRO.PIF. Don't click OK yet.
4. Select the Change Icon button. In the File Name field in the next
dialog, type LLPRO.ICO. (As in step 3, you may also need to include
the path to the file.) After clicking OK, the icon should appear in
the chosen group.
NOTE: The LLPRO.PIF file does not allow LapLink Pro to function
while the application is minimized. That is, you cannot transfer
files while LapLink Pro is running in the background. Traveling
Software has not tested background operation extensively. There are
many Windows setup and hardware configurations that will prevent
background operation completely. If you would like to try however,
see "Running LapLink Pro in the Background" later in this file.
5. To start LapLink Pro under Windows, double-click the LapLink Pro
icon.
NOTE: If double-clicking does not start LapLink Pro, you may also have
to customize LLPRO.PIF. Use the Windows PIF Editor application and add
the LapLink directory to the Program Filename or Start-up Directory
fields. For more information see your Windows documentation.
------------------------------------------------------------------------
B. Suggestions for Working in the 386 Enhanced Mode
Under the Windows 386 Enhanced Mode, applications "contend" for the use
of devices such as serial and parallel ports. Because of this, you may
experience difficulties with LapLink Pro communications. The following
solutions will allow more robust connections.
*****Serial Port Solutions*****
Because of the way Windows 3.0 controls serial ports, LapLink Pro's
higher speeds may not be available. You have two solutions. You can
reduce the LapLink Pro's transfer mode and baud rate. Or, you can turn
off Window's serial port buffering. With the first solution you will
only be able to transfer files at a reduced rate. With the second
solution, LapLink will transfer as fast as it does directly from DOS,
but LapLink Pro cannot be used at the same time as other programs that
use the serial port (such as the Windows Terminal application).
a. Changing the Transfer Mode or Baud Rate
To change the transfer mode:
1. Start LapLink Pro and choose the "Port/Modem Setup" command from the
Options menu. A dialog is displayed that shows both serial and
parallel ports. Select the serial port you are using for LapLink.
2. Place an X in the Force Standard (3-wire) Mode field.
3. Close both dialogs by selecting <OK> and then <Done>.
If you still experience communication problems, use the same method but
change the Max Baud Rate from Automatic to a lower value. 57,600 baud
may work but you may need to try as low as 19,200.
b. Turning Off Windows 3.0 Serial Port Buffering
NOTE: Although this solution will increase CABLE communication speed, it
may hamper modem communications. If you intend to use both a modem and a
cable, you may have to experiment to find the most optimal solution.
Your Windows default directory (usually C:\WINDOWS) contains a file
called SYSTEM.INI. This file contains many Windows environment settings
and is integral to the performance of Windows. Two lines in the [386
Enh] section of the file--device=*VCD and device=*COMBUFF--partially
control contention and buffering of serial ports. In the instructions
that follow, you edit SYSTEM.INI to turn these devices off.
CAUTION: ALWAYS MAKE A BACKUP OF THE SYSTEM.INI FILE BEFORE CHANGING IT.
WITHOUT A VALID SYSTEM.INI FILE WINDOWS WILL NOT RUN!
To edit your SYSTEM.INI file:
1. Using a text editor, open SYSTEM.INI. You can use the LapLink Editor
or the Windows Notepad application.
2. Search for the following two lines in the [386 Enh] section:
device=*vcd
device=*combuff
3. At the beginning of each line type a semicolon (;), so that they
look like the following:
;device=*vcd
;device=*combuff
4. Save the file and restart Windows.
*****Parallel Port Solutions*****
In most cases, LapLink Pro maintains parallel connections in all Windows
modes. If you experience problems in the 386 Enhanced mode, however, you
may want to add the following line to your SYSTEM.INI file:
SGrabLPT=#
For example, if you cannot connect over LPT1 add a line that reads:
SGrabLPT=1
The line does not normally appear in SYSTEM.INI. The line has the effect
of directing all of the ports "traffic" through the main Windows
program. Remember, anytime you edit SYSTEM.INI be sure to make a back up
the file first.
------------------------------------------------------------------------
C. Running LapLink Pro in the Background
Because of the way Windows "schedules" DOS background tasks, it is
difficult to configure Windows to allow background communication for any
DOS communication program, including LapLink Pro. And, there are many
Windows setup and hardware configurations that will prevent background
operation completely. Therefore, Traveling Software does not recommend
background operation, and the Windows PIF file that is shipped with
LapLink Pro (LLPRO.PIF) is not set up for background functionality.
However, if you want to try LapLink Pro in the background, you can edit
the PIF file and check the Background box. You will also need to
increase the number for background task priority.
If you just want to try to use LapLink Pro in the background for one
session without editing the PIF file, use the Settings command from the
LapLink Pro window's system menu. See your Windows documentation for
details.
In addition to these changes here are two more tips:
* If you are running Windows in the 386 Enhanced mode, open the
Windows Control Panel and choose 386 Enhanced. Make sure that the
Exclusive in Foreground option is NOT checked. (When on, this option
prevents any DOS application from running in the background.)
* Try not to run other DOS applications while transferring files in
the background.
------------------------------------------------------------------------
D. Windows and 9600 Baud Modems
If you are using a 9600 baud modem with Windows 3.0, you should be aware
that without modification, Windows may often "lock up" when running ANY
modem communications at 9600 baud. Unfortunately, this also includes
LapLink Pro. The problem is most notable when using a slower 80386SX PC.
There are two solutions to this problem:
* Edit your SYSTEM.INI file to increase the number of characters that
are buffered by the serial port. This allows the buffer to "keep up"
with the modem's high speed.
* In LapLink Pro, set your modem to run in the 2400 baud mode. This is
a stable solution but forces your modem to run at a slower rate.
To edit SYSTEM.INI:
CAUTION: ALWAYS MAKE A BACKUP OF THE SYSTEM.INI FILE BEFORE CHANGING IT.
WITHOUT A VALID SYSTEM.INI FILE WINDOWS WILL NOT RUN!
1. Using a text editor, open SYSTEM.INI. You can use the LapLink Editor
or the Windows Notepad application.
2. Search for the following two lines in the [386 Enh] section:
device=*vcd
device=*combuff
Make sure these lines have not been turned off. (This read me
recommends turning the lines off to permit higher speeds for CABLE
connections only, not modem connections.)
3. After these lines add a line that reads:
COMxBuffer=4096
For x, use the number of the serial port to which the modem is
attached. (For example, if the modem is attached to COM1 the line
would be:
COM1Buffer=4096)
This line increases the number of buffered characters from 128 to
4096.
4. Save the file and restart Windows.
To use a 9600 baud modem at 2400 baud:
1. Choose the "Port/Modem Setup" command from the Options menu and
select the port to which the modem is attached. If there are two
initialization strings for your modem model, choose the one that
ends in "@2400 baud."
2. Choose the <Setup Port> button and set the Maximum Baud Rate to
2,400.
------------------------------------------------------------------------
XII. GETTING TECHNICAL SUPPORT
If you have a question or need Technical Support, the following sources
are available:
In the U.S., Traveling Software telephone Technical Support is available
from 8:00 a.m. to 5:00 p.m., (Pacific Time) Monday-Friday at (206) 483-
8088. Please have your serial number ready before calling.
If you want to contact the TSI Technical Support bulletin board, set
your modem to dial (206) 485-1736. Use the following settings for your
communications program:
Baud rate 2400
Parity None
Data bits 8
Stop bits 1
On GEnie type "LAPTOPS" to join the Laptops RoundTable. Then enter the
Laptops Bulletin Board and type "SET 3" to go to Traveling Software
Technical Support. Answers to the most frequently asked questions can be
found there. To sign up for GEnie call (800) 638-9636 (Voice).
For support in Europe, call +44 (0734) 321 154.
In Australia and New Zealand, Traveling Software products are sold and
supported by PC Extras. In Australia, phone (02) 319 2155; in New
Zealand, phone (09) 59 7834
For a complete listing of Traveling Software addresses and fax and phone
numbers see the back of the LapLink Pro User's Guide.
------------------------------------------------------------------------
XIII. MAKING SUGGESTIONS TO IMPROVE LAPLINK PRO
Traveling Software is constantly looking for ways to improve its
products. Over the years, our customers have been the ones who have
provided some of the best product improvement suggestions.
We encourage you to send us your comments, criticisms, and ideas. We
will try to implement your requests in future versions.
You may address your comments to:
Traveling Software, Inc.
LapLink Pro Suggestions
18702 North Creek Parkway
Bothell, WA 98011
NOTE: For the LapLink Pro installation program, LHA was used to create a
self-extracting compressed file. LHA is a copyright of Yoshi, 1991. All
rights reserved.
Compiled October 11, 1991.
The Latest About LapLink V
Version 5.0
Welcome to LapLink V. If you're a new LapLink owner, be sure to
mail in your registration card to ensure that you will be
notified of future releases.
**************************************************************
********* *********
********* IMPORTANT! If you are using LapLink V *********
********* over a network or modem be sure to read *********
********* the first two sections of this document. *********
********* By default, connections are limited until *********
********* you make the changes they describe. *********
********* *********
**************************************************************
-CONTENTS-
I. You MUST change Security to Allow Incoming Connections
II. Important Notes for Network Users
A. To use Network Connections You MUST Enable Them First
B. Checking for Windows 3.1 or Windows for Workgroups
Compatibility
C. The Xircom Pocket Ethernet Adapter
III. Quitting LapLink if It "Freezes"
IV. Remote Install and TSRs
V. More Windows 3.1 Notes
A. Multiple LapLink V Windows
B. Non-standard Port IRQs
C. RangeLAN
VI. More Information About Security
A. Using SUBST to Secure Lower-Level Directories
B. When Security Creates Read-Only Files
C. Sharing Address Book (or Security) Files
VII. Starting LapLink V with Command Line Switches
VIII. Using LapLink V with OS/2 2.0
A. DOS Session Settings
B. Making Peer-to-Peer NetWare Connections
C. Changing CONFIG.SYS for Serial Cable Connections
IX. Computer Names, Passwords, and User Names
X. The Xircom Parallel Port Multiplexor
XI. Using LapLink V with Other Traveling Software Products
XII. Getting Technical Support
XIII. Making Suggestions to Improve LapLink V
-----------------------------------------------------------------
I. You MUST change Security to Allow Incoming Connections
With the capabilities of this release, ANY modem or network user
may connect to your PC. For that reason, the LapLink security
system is now enhanced.
By default, the security system is set to allow cable connections
only. You can make OUTGOING connections to modem or network
users, but you must change the default before other modem or
network users can make INCOMING connections to your PC.
To change the default, use the Security Setup command on the
Connections menu:
-If you don't want to use security at all, choose the Anyone
option and then the OK button. CAUTION: If you have enabled the
network or modem port, any user will then have FULL ACCESS to
any file on your PC, without supplying a password at all.
-If you want a one-password/unlimited access solution, as was
present in LapLink Pro, choose the User List Only option. On the
next dialog, leave the User Name field set to Default User, and
type a password in the Password field. Then, highlight all your
disks and choose the Entire Drive button. CAUTION: With this
setup, any user that provides the password will have FULL ACCESS
to any file on your PC.
-If you want to take full advantage of the new security features,
follow the instructions on pages 106-113 of the LapLink V User's
guide. The suggested procedure calls for you to provide very
limited access to the default user and grant less restrictive
access to specifically named users. With this setup, users that
connect and are not in your list will only have access to the
files defined for the default user. Users that are in your list
may have greater rights.
-----------------------------------------------------------------
II. Important Notes for Network Users
A. To use Network Connections You MUST Enable Them First
When you first install LapLink V, you can make neither OUTGOING
nor INCOMING network connections. (This default provides an extra
measure of security for your files and also lets network
administrators control the amount of data transferred over the
network, if they desire.)
-To allow network connections, choose the Port/Modem Setup
command from the Options menu. Choose the Network button to
change the state to Enabled. Then choose Done.
This allows you to make OUTGOING connections immediately. To
allow INCOMING connections, be sure to change Security Setup as
described in the previous section.
NOTE: Enabling network connections has a very minor impact on
network traffic. When files are transferred, no disk space is
used on the server, only the disks on the connected workstations
are affected.
B. Checking for Windows 3.1 or Windows for Workgroups
Compatibility
Outside of Windows (directly from DOS) any attached network
workstation can make peer-to-peer network connections if the
network is running Novell NetWare versions 2.2 or 3.11.
If LapLink "locks up" after you start it in Windows 3.1 or
Windows for Workgroups, however, you'll need to check the Windows
network configuration. You can use a tool provided with LapLink V
to check:
First, start the network from DOS and log on to the network.
Then, from your LapLink directory type the following command:
NETINFO [windows path]
For example, if Windows is installed in C:\WINDOWS, type:
NETINFO C:\WINDOWS
-If Windows is set up correctly, you will see a message like:
Netware Shell Version-> 3.26 OK
IPX/SPX Version -> 1.20 OK
NETWARE.DRV -> Found
*VNETBIOS -> Found
VNETWARE.386 -> Found
VIPX.386 -> Found
Your Network drivers are current.
Your SYSTEM.INI file specifies the necessary drivers to
support LapLink peer-to-peer connections.
-If the message reports that your network drivers are not
current, or that SYSTEM.INI does not specify the necessary
drivers, you should re-run the Windows or Windows for Workgroups
Setup program. If you specify Novell for the type of
network, the correct drivers and changes should be made
automatically. (You may need your Windows or Windows for
Workgroups installation disks when you run Windows setup.)
NETINFO checks the following information:
1. The following network drivers must be in memory:
NETX.COM version 3.26
IPX.COM version 3.10
(IPX.COM may be replaced with LSL.COM version 1.20 and
IPXODI.COM version 1.20).
2. SYSTEM.INI must contain the following lines:
----WINDOWS 3.1----
Under the [boot] section header:
network.drv=netware.drv
Under the [386Enh] section header:
network=*vnetbios,vnetware.386,vipx.386
----WINDOWS FOR WORKGROUPS----
Under the [boot] section header:
network.drv=wfwnet.drv
secondnet.drv=netware.drv
Under the [boot.description] section header:
network.drv=Microsoft Windows for Workgroups
(version 3.1)
Under the [386Enh] section header:
network=vnetbios.386,vnetsup.386,vredir.386,vserver.386,
vbrowse.386,vwc.386
secondnet=*vnetbios,vnetware.386,vipx.386
C. The Xircom Pocket Ethernet Adapter
In order to make a network connection under Windows with this
device, you must have the latest Xircom NetWare drivers.
For PE2ODI.COM the version should be 1.44, dated 10/30/92 (NOT
version 1.27, dated 6/4/92). For the PE2IPX.COM the version
should be 1.44, dated 10/30/92 (NOT version 1.27, dated 6/7/92).
Contact Xircom for the latest drivers.
NOTE: To make a network connection over a parallel port with the
Xircom adapter, you should DISABLE the parallel port to which the
adapter is connected. For example, if the adapter is attached to
LPT1, use the Port/Modem Setup command to disable LPT1. Disabling
prevents LapLink from trying to use the port for cable
connections.
-----------------------------------------------------------------
III. Quitting LapLink if It "Freezes"
If LapLink V will not respond to your keystrokes, it may be in a
"timed-out" state. If LapLink appears frozen, press [Ctrl+Break].
LapLink will exit. If you changed any options however, the
changes will be lost.
-----------------------------------------------------------------
IV. Remote Install and TSRs
If you experience problems with remote install, check the remote
PC for installed TSRs (memory-resident programs). Some PCs will
not accept a remote install if certain TSRs are in memory.
TSRs that are known to cause problems include DOSKEY (available
with DOS 5.0 and above) and SHARE. NDOS which replaces DOS's
COMMAND.COM is also known to prevent remote installs when
installed on the remote PC.
To uninstall a TSR, you'll usually need to reboot the PC. First
check the AUTOEXEC.BAT file. If there is a line that starts the
TSR, edit AUTOEXEC.BAT and place a "REM" at the beginning of the
line. For example, if there is a DOSKEY line in your AUTOEXEC.BAT
file, change it to:
REM DOSKEY
Then, reboot the PC. Try running remote install again. You can
add the TSR back later by removing the REM.
To start the remote PC without NDOS, use a DOS boot disk to boot
the PC. After the remote install is complete you can reboot the
PC normally.
-----------------------------------------------------------------
V. More Windows 3.1 Notes
A. Multiple LapLink V Windows
We do not recommend opening more than one instance of LapLink V
during a given Windows session. This can cause particular
problems if LapLink is enabled for network peer-to-peer
transfers.
B. Non-standard Port IRQs
If some of your serial ports use non-standard IRQs (this is
common if you are using a PS/2 with COM3 and COM4) you may have
to edit your SYSTEM.INI file to allow the use of the port with
the non-standard IRQ.
If you have problems communicating over a serial port using IRQ
2, check your SYSTEM.INI file for a line in the [386Enh] section
that reads:
COMxIRQ=2
and change the IRQ to 9. For example:
COMxIRQ=9
C. RangeLAN and Windows 3.1
LapLink V will not function if you are using a RangeLAN network
connector and Windows 3.1. With RangeLAN LapLink V may only be
run directly from DOS.
-----------------------------------------------------------------
VI. More Information About Security
A. Using SUBST to Secure Lower-Level Directories
The LapLink V security system lets you permit or deny access to
any directory located immediately in the root of your drives. If
you need finer-grained security, you can make use of the DOS
SUBST (substitute) command.
SUBST lets you assign a drive letter to a given path. For
example, suppose your hard disk has this partial structure:
C:\-
|
--DATA\-
|
--SALES\
|
--GOALS\
If you use this SUBST command:
SUBST G: C:\DATA
Then DOS will treat C:\DATA like it is a drive named G:. You can
then deny access to C:\DATA but allow access to the G:\SALES or
G:\GOALS directories individually because they are immediately at
the root of G:
If you want to use SUBST for security, you should include the
SUBST command in your AUTOEXEC.BAT file so that the "substituted"
drive is available anytime you start LapLink V. For more
information about the SUBST command, see your DOS manual.
B. When Security Creates Read-Only Files
If you assign read-only access to a drive or directory, then a
remote user will see the files in the drive or directory as
read-only. If the user then copies the files, they will arrive at
his or her PC marked as read-only.
IN ORDER TO EDIT THE FILE THE USER WILL HAVE TO CHANGE THE
READ-ONLY ATTRIBUTE OF THE FILE. To change the attribute, use the
DOS ATTRIB command.
For example, if a directory contains a number of read-only files,
they can all be edited (given read/write access) if the following
command is issued:
ATTRIB -R *.*
For more information about ATTRIB, see your DOS manual.
C. Sharing Address Book (or Security) Files
We do not recommend exchanging your Address Book (TSI.PBK) or
Security List (TSI.PWD) files with other users. If another user
must use your Address Book, however, you should use the Local
Password command and remove the extra security provided by the
command.
Choose Local Password and un-check the file you want to exchange.
The other user should also remove this protection. Then, copy
TSI.PBK to the remote user. Once the user has successfully viewed
the Address Book, he or she can reinstate Local Password
protection.
If you copy your Address Book to another user with the Local
Password enabled, the user will have to provide the Local
Password you designated on your PC before he or she can use the
Address Book.
-----------------------------------------------------------------
VII. Starting LapLink V with Command Line Switches
You can start LapLink V with the following command line switches:
LL5 /p[path] Tells LapLink where to look for its support
files. Most useful if LapLink V is on a
read-only disk.
LL5 /43 or Tells LapLink to use more lines on your
LL5 /50 display. If your monitor is EGA, 43 lines are
displayed; VGA monitors display 50.
LL5 /s Starts LapLink in the short menu mode. During
the session, long menus cannot be turned back
on.
LL5 /g If you can start LapLink V but the screen
appears blank, /g may allow you to see
the LapLink screen. This will force LapLink
to the non-graphic (no icon) mode.
LL5 recording Starts LapLink and causes LapLink to run the
named recording. The recording file must be
located in the LapLink directory.
-----------------------------------------------------------------
VIII. Using LapLink V with OS/2 2.0
To install LapLink V for OS/2, run the LapLink Install program
directly from DOS (not in an OS/2 DOS window). Start LapLink
directly from DOS and use the Port/Modem Setup command to make
sure the ports you want to use are enabled.
With the default OS/2 configuration you will then be able to use
parallel and modem connections in the foreground. If you make
the changes described in section A (below), modem connections
will be improved and you'll also be able to transfer files in
the background.
NOTE: Under OS/2 modem speeds are limited to 9600.
To make peer-to-peer network connections, read section B. If
you want to make serial cable connections read section C.
A. DOS Session Settings
In order for LapLink V to function correctly in a DOS session or
window, you must change the DOS session settings:
1. Open the OS/2 System folder. Then open the Command Prompts
folder.
2. Right-click either the DOS Window or DOS Full Screen icon.
3. Open the Settings notebook, select the Session tab, and choose
the DOS Settings button.
4. Change or ensure the following settings:
COM_HOLD on
DOS_BACKGROUND_EXECUTION on
DOS_BREAK on
DOS_HIGH on
HW_TIMER on
IDLE_SENSITIVITY 100
VIPX_ENABLED on (This is for network connections only and
will only be available if you make the
changes in section B., below.)
You should then be able to open a DOS Window or Full Screen
session and make serial, parallel, and modem connections. For
network connections, read the instructions below.
B. Making Peer-to-Peer NetWare Connections
In order to make a NetWare connection, the OS/2 NetWare Requestor
must be installed for OS/2. In addition you must open a DOS box
and start the DOS NetWare drivers. You must also change the OS/2
CONFIG.SYS file.
-Editing the OS/2 CONFIG.SYS file
Open CONFIG.SYS and check for a line that reads:
DEVICE=VIPX.SYS or REM DEVICE=VIPX.SYS
If the line has the "REM" at the beginning, delete it so it looks
like:
DEVICE=VIPX.SYS
You'll then need to restart your PC.
-Starting the NetWare Drivers
First, log on to the network using your usual OS/2 procedures.
Next, you'll need to obtain the DOS NetWare drivers from your
system administrator. Then open a DOS box and start the drivers
in order.
For example:
LSL.COM <--- NetWare Link Support Layer
XXXXXX.COM <--- A specific driver for your network card
NETX.COM <--- NetWare Workstation Shell
NOTE: You do not need to start IPXODI.COM. Under OS/2 that
functionality is provided by VIPX.SYS.
After you start the drivers, you should then be able to start
LapLink V and make network connections. You might wish to create
a DOS batch file that starts the drivers and then LapLink V.
C. Changing CONFIG.SYS for Serial Cable Connections
To make serial cable connections under OS/2, edit the OS/2
CONFIG.SYS file. However, making this change may prevent
stable modem connections.
If you want to use serial cables, find the line that reads:
DEVICE=[path]\VCOM.SYS
and disable it by adding "REM" before the line so that it reads:
REM DEVICE=[path]\VCOM.SYS
You will need to restart OS/2.
NOTE: For the most consistent serial cable performance, use the
LapLink V Port/Modem Setup command and set the serial port to
"Polled."
-----------------------------------------------------------------
IX. Computer Names, Passwords, and User Names
We do not recommend using high-order ASCII characters in computer
names, passwords, or user names. When stored by LapLink,
characters are converted to upper-case which may not correspond
to the lower-case letters. This is especially a problem with
passwords which are not displayed on your screen.
-----------------------------------------------------------------
X. The Xircom Parallel Port Multiplexor
LapLink V has been designed to work with parallel ports that have
a Xircom Parallel Port Multiplexor. However, the system must
first be set up properly.
First, do NOT use the port-switching software that comes with the
multiplexor. (LapLink V contains code that causes the multiplexor
to automatically switch ports, so the port-switching software is
unnecessary. Not using the switching software has the additional
benefit of freeing more memory for your applications.)
Second, the LapLink parallel cable must be attached to the "A"
port of the multiplexor. The printer cable should be attached to
"B."
Third, you must make a change using the "Port/Modem Setup"
command (Options menu):
Choose the command, and in the Port/Modem Setup dialog, select
the parallel port with the multiplexor. In the next dialog place
an x in the Force Standard (4-bit) mode check box and choose
<OK>. If you do not make this change, the Multiplexor may try to
switch between the printer and the cable during the middle of a
copy.
NOTE: There is one case where a connection involving a Xircom
parallel port multiplexor does not work: The PC with the
multiplexor is running LapLink V from DOS. It is connecting via
parallel cable to a PC running LapLink V from Windows, and the PC
with Windows has installed the LapLink V enhanced port drivers.
To allow these two PCs to connect, either start Windows on the PC
with the multiplexor and then start LapLink. Or quit Windows on
the PC without the multiplexor and then start LapLink.
-----------------------------------------------------------------
XI. USING LAPLINK V WITH OTHER TRAVELING SOFTWARE PRODUCTS
LapLink V is not compatible with LapLink Pro and you cannot
connect to another PC running LapLink Pro.
Because WinConnect, DeskLink, and the LapLink III Device Driver
compete with LapLink V for port usage, using them with LapLink V
may require experimentation. In most cases, you need to delete
the LapLink V configuration file (TSI.INI), start the other
program, and then start LapLink V. This causes LapLink V to
re-check all available ports and it then only uses the ports that
are not currently in use by the other program. (Note: When you
delete TSI.INI many options are returned to their default
values.) If you need help with this procedure, call Traveling
Software Technical Support.
Battery Watch Pro is compatible with LapLink V, but as with other
TSRs, you should avoid popping up the Battery Watch screen during
a file transfer.
-----------------------------------------------------------------
XII. GETTING TECHNICAL SUPPORT IN THE U.S.
If you have a question or need Technical Support, check the
numbers in your user manual.
If you want to contact the TSI Technical Support bulletin board,
set your modem to dial (206) 485-1736. Use the following settings
for your communications program:
Baud rate 2400 or 9600
Parity None
Data bits 8
Stop bits 1
-----------------------------------------------------------------
XIII. MAKING SUGGESTIONS TO IMPROVE LAPLINK V
Traveling Software is constantly looking for ways to improve its
products. Over the years, our customers have been the ones who
have provided some of the best product improvement suggestions.
We encourage you to send us your comments, criticisms, and ideas.
We will try to implement your requests in future versions.
You may address your comments to:
Traveling Software, Inc.
LapLink V Suggestions
18702 North Creek Parkway
Bothell, WA 98011
Compiled February 15, 1993
****************************************************************************
NOTES ON MICROSOFT MAIL REMOTE, VERSION 3.0
****************************************************************************
This document (README.TXT) contains important information that supplements
the documentation for Microsoft Mail Remote.
This document covers the following topics:
A. How to print these notes
B. Specifying the amount of memory for the Listen program
C. Recommended Script Size Limits
D. Mixing Remote and Postoffice Language Versions
E. Modem Script Files
A. HOW TO PRINT THESE NOTES
============================
To print these notes:
1. Type: copy readme.txt printer:
Replace "printer:" with the port to which your printer is connected,
such as lpt1.
2. Press ENTER.
To print to a postscript printer, open this document in Windows Notepad,
Windows Write, or any word processor application, and choose the Print
command.
B. SPECIFYING THE AMOUNT OF MEMORY FOR THE LISTEN PROGRAM
==========================================================
Use the -Y option to specify the amount of memory in kilobytes for the
Listen program. If you do not specify the amount of memory, 32K is used.
The minimum amount you can specify is 12K and the maximum amount is 36K.
Format: LISTEN [-Ynn]
For example, to handle a larger modem script, start LISTEN with 36K of
memory:
LISTEN -Y36
C. RECOMMENDED SCRIPT SIZE LIMITS
==================================
For best performance, run the Transmit program with 112K of memory
available and use a script no larger than 5K. Run the Listen program
with 128K of memory available and scripts no larger than 3.5K. While
larger scripts may be used, you may be short of memory when receiving
mail.
D. MIXING REMOTE AND POSTOFFICE LANGUAGE VERSIONS
==================================================
To use Microsoft Mail Remote with a postoffice of a different
language, the same language version of the MS-DOS client as the
Remote client must first be installed. Then choose the Remote
Regenerate command in the Administrator program before creating
the Remote Data Disk for the Remote user. This creates the correct
template files for the Remote client.
For example, to use the French Remote client on a German
postoffice, the French MS-DOS client must be installed on the
postoffice.
E. MODEM SCRIPT FILES
======================
The following script files are available for modems tested for
use with Microsoft Mail.
MODEM SCRIPT FILES FOR NORTH AMERICA
====================================
- Null Modem NULMODM.SCR
- Hayes Smartmodem 1200 USHAYS12.SCR
- Hayes Smartmodem 2400 USHAYS24.SCR
- Hayes V-series Smart 9600 USVSER96.SCR
- Hayes V-series Ultra 9600 USULTR96.SCR
- IBM 5853 2400bps modem USIBM524.SCR
- Microcom AX Series modems USMRCM96.SCR
- Multitech MultiMdm 224E/V32 USMLTC96.SCR
- Telebit TrailBlazer 9600bps USTLBT96.SCR
MODEM SCRIPT FILES FOR FRANCE
=============================
- Andrsn/Jacbsn 9634 @2400b FRANJA96.SCR
- Compaq Internal 2400bps FRCMPQ24.SCR
- Kortex 1200bps modems FRKRTX12.SCR
- Kortex 2400bps modems FRKRTX24.SCR
- PNB Amazone 2400bps FRPNBA24.SCR
- PNB Niagara 2400bps FRPNBN24.SCR
- PNB Amazone Pocket 2400b FRPNBP24.SCR
- Quadri Campouce 2400bps FRCAMP24.SCR
- Quattro TM2496 2400bps FRQUAT24.SCR
- USRobotics Courier HST USRCRHST.SCR
- USRobotics Courier V32 USRCRV32.SCR
MODEM SCRIPT FILES FOR CENTRAL EUROPE
=====================================
- Digitec ALF 2400 II GEALF24.SCR
- Digitec ALF 2400 MNP GEALFM24.SCR
- Digitec Dialog 2400 GEDILG24.SCR
- Digitec Dialog 2400 MNP GEDLGM24.SCR
- Digitec Dialog 2400 Pro. GEDLGP24.SCR
- Digitec Personal Line 2400 GEDIGP24.SCR
- Digitec Prs. Line 2400 MNP GEDIGM24.SCR
- Fury 2402 TI 2400bps GEFURY24.SCR
- Longshine Shine 2400 GESHIN24.SCR
- MicroLink 2410T2 2400bps GEMCLK24.SCR
- MicroLink 9624T2V 2400bps GEML9624.SCR
- Toshiba Laptop int. 2400 GETOSH24.SCR
MODEM SCRIPT FILES FOR SWEDEN
=============================
- DiCom 9600 V42 Modem SWDICM96.SCR
- Motorola Codex-series 9600 SWMCDX96.SCR
- Multitech MultiModem V32 SWMTMM96.SCR
- USRobotics HST Courier V32 SWUSRHST.SCR
MODEM SCRIPT FILES FOR THE UNITED KINGDOM
=========================================
- BT NS 2232B 9600bps UKBTNS96.SCR
- Dowty Mayze & Quattro 96 UKMAZQAT.SCR
- Hayes 2400bps modems UKHAYS24.SCR
- Hayes Ultra & VSeries UKULTRAV.SCR
- Miracom V32 & Courier HST UKMRCMCR.SCR
- Quattro 2400bps modem UKQUAT24.SCR
These six script files support the following set of modems:
* The British Telecomm NS 2322B modem.
* The Dowty set of modems including Quattro24, Mayze 24,
Mayze 96, and Quattro 96.
* The Hayes and Ultra set of modems including Ultra 96,
V series 9600, V series 2400, and the Hayes 24 Smartmodem.
* The Miracom (U.S. Robotics) set of modems including
V.32, Courier HST, and Dual Standard.
----------------------------------------------------
NOTE: Microsoft Product Support Services will answer questions
only about modems in this list or those listed in the Setup
program.
* * * * * *
----------------------------------------
Microsoft Mail for PC Networks version 3.2
README File
----------------------------------------
(C) Copyright Microsoft Corporation, 1991-93
This document (README.TXT) contains important information that supplements
the Microsoft Mail version 3.2 manuals and online help provided in this
package. The manuals include the Microsoft Mail Administrator's Guide, the
Technical Reference manual, and the User's Guides for the MS-DOS client,
Windows-based and Presentation Manager clients, and Macintosh client.
This document covers the following topics:
A. How to print these notes
B. Information for Microsoft Mail administrators
C. External Mail program features not described in the Administrator's
Guide
D. Information for users of the MS-DOS client software
E. Information for users of the Windows-based client software
F. Information for users of the Presentation Manager client software
G. Information for users of the Macintosh client software
A. HOW TO PRINT THESE NOTES
===========================
To print these notes:
---------------------
1. Type: copy readme.txt printer:
Replace "printer:" with the port to which your printer is connected,
such as lpt1.
2. Press ENTER.
To print these notes from Microsoft Windows:
--------------------------------------------
To print README, open README.TXT in Windows Write, Microsoft Word, or another
word processor. Then select the entire document and format the text in 10-
point Courier before printing.
B. INFORMATION FOR MICROSOFT MAIL ADMINISTRATORS
================================================
This section covers the following topics:
1. Microsoft Mail Technical Reference
2. Supplementary Modem Scripts
3. Directory of text files installed by Setup
4. Modem Script return codes and external retries
5. Multiple modem messages in a script response buffer
6. Setting up Eicon Gateway software
7. Moving a user already defined in the Destination
Postoffice Address List
8. Import Utility example correction
9. Unencrypted password option no longer required for Novell
10. MS-DOS External and LAN MAN opportunistic locking
B.1. Microsoft Mail Technical Reference
---------------------------------------
The Microsoft Mail Technical Reference manual describes features that
administrators and programmers can use to extend and customize Mail in the
Windows environment. For information not included in the Technical Reference,
see the README.TXT file on the Technical Reference Server Programs disk.
B.2. Supplementary Modem Scripts
--------------------------------
Modem scripts used with the External Mail program are installed in the
postoffice directory when you run the Setup program (SETUP.EXE). The
Supplementary Modem Scripts disk contains additional modem scripts. For a
list of modem script files and installation instructions, see the README.TXT
file on the Supplementary Modem Scripts disk.
B.3. Directory of Text Files Installed by Setup
-----------------------------------------------
The Microsoft Mail Setup programs install the following text files in the
server programs directory you specified.
FILE CONTAINS
---- --------
ADMIN.TXT Administrator program error and status messages
CLIENT.TXT MS-DOS client and Macintosh client program error messages
DIRSYNC.TXT Directory Synchronization error and status messages
DISPATCH.TXT Dispatch program error messages for MS-DOS and OS/2
DYNADMIN.TXT Dynamic Drive Administrator program error messages
EXTERNAL.TXT External Mail program error messages for MS-DOS and OS/2
IMPORT.TXT Local User Import program error messages, LAN Manager and
Novell Extract Utility error messages
OS2MTA.TXT Readme file for the Microsoft Mail Multitasking MTA
README.TXT This file
SETUP.TXT Microsoft Mail Setup program error messages
SWITCHER.TXT Information about changing Mail System Drivers using the
Microsoft Mail System Selector
B.4. Modem Script Return Codes and External Retries
---------------------------------------------------
Processing of certain return codes from modem script files differs from
versions of Microsoft Mail prior to version 3.2. When the Call script returns
a result code of NoCarrier (4), NoDialTone (6), Busy (7), or NoAnswer (8),
the External program now increases the retries count on all mail that was
queued to be sent. If the retry count exceeds the number for the routing, the
mail is returned to the sender.
If a script you customized for a previous version of Mail is to be used with
the External Mail program version 3.2, check to see if the retry count on
script return codes 4, 6, 7, and 8 was used. If the script was designed so
that return code was not expected to increase the retries count, recompile
the script using return code 9--External does not increase the retry count if
encounters a script return code 9.
For more information about writing script files, see Appendix E, "Script
Files," in the Microsoft Mail Administrator's Guide.
B.5. Multiple Modem Messages in a Script Response Buffer
--------------------------------------------------------
When the External Mail program receives a message from a connected modem,
multiple messages can be put into the response buffer. If you are writing a
custom script or using a script from the Supplementary Scripts disk that was
written for modems manufactured outside of North America, use the ISIN
operator to check the response buffer. This is especially important for
incoming call messages.
Change the search for response return codes from:
if (response = "2^M")
to:
if ("2^M" isin response)
For more information about writing script files, see Appendix E, "Script
Files," in the Microsoft Mail Administrator's Guide.
B.6. Setting up the Eicon Gateway Software
------------------------------------------
For information about installing the Eicon Gateway software, see the Eicon
documentation and Appendix F, "X.25 Settings for Mail," in the Microsoft Mail
Administrator's Guide. Your Eicon setup must match the configuration of the
line leased from your X.25 carrier. Values vary by carrier and installation--
confirm all values set by the ECCFG program with your carrier.
The Microsoft Mail Administrator's Guide provides information about
parameters that are critical when setting up the Eicon board and software.
For the configuration option Number Of TVCs, a value of 004 is suggested. The
correct value depends on the line installed--a different value could be
appropriate for your configuration.
B.7. Moving a User Already Defined in the Destination Postoffice Address List
-----------------------------------------------------------------------------
You can use the Move User utility to move locally defined users between
postoffices. If you attempt to move User X from Postoffice A to Postoffice B,
and there is already an external address for User X in Postoffice B's
Postoffice Address List (POL), you are asked for another alias for user X
before you can move the user.
To avoid this situation, be sure that the external address for a user is
deleted on the destination postoffice before you move the user.
B.8. Import Utility Example Correction
--------------------------------------
On page 322 in the Microsoft Mail Administrator's Guide, in the section
"Examples of Running Import," the third example is incorrect.
The example should be:
import admin -ppassword -gsnads -x -fh:\snads.txt
B.9. Unencrypted Password Option No Longer Required for Novell
--------------------------------------------------------------
If you are running Microsoft Mail on a Novell network, and you are upgrading
your postoffice from a version of Microsoft Mail prior to 3.0, remove the SET
UNENCRIPTED PASSWORDS=ON option from the AUTOEXEC.NCF files. This setting was
previously required to properly configure dynamic drives for the External
Mail program.
B.10. MS-DOS External and LAN MAN opportunistic locking
-------------------------------------------------------
If External is running on a MS-DOS LAN MAN workstation with opportunistic
locks enabled, External may hang the workstation when trying to recover from
critical errors. When this occurs, External stops delivering mail and the
workstation must be restarted.
To avoid manually restarting the workstation, take one of these two
preventative measures:
1. In your LANMAN.INI file Workstation Section [workstation] turn off
opportunistic locking of files by turning off bit 0 in the wrkheuristics
entry. See appendix B of the Microsoft LAN Manager Administrator's Reference.
2. Use the External option RebootOnCE to automatically restart the
workstation on critical errors. See section C.2 in this document for more
details.
C. EXTERNAL MAIL PROGRAM FEATURES NOT DESCRIBED IN THE ADMINISTRATORS GUIDE
===========================================================================
This section covers the following topics:
1. Generic script file included with the Server
2. Automatically rebooting MS-DOS External on critical errors
3. Specifying X.25 facilities and user data
C.1. Generic Script File Included with the Server
-----------------------------------------------------
A new generic script file for Hayes-compatible modems is included with the
Microsoft Mail for PC Networks MS-DOS server version 3.2. The script file,
USGNERIC.MDM, is designed to operate with any modem compatible with the Hayes
AT command set. The generic script does not set the baud rate--the baud rate
is set using the Config Serial Baud-rate command in the Administrator
program.
The generic script is installed in the GLB directory of the postoffice
directory you specify when running the Setup program (SETUP.EXE). To use this
script, specify the option CommScript=USGNERIC in the External Mail program.
For more information about specifying scripts in the External Mail program,
see Chapter 12, "Setting Up the External Mail Program," in the Microsoft Mail
Administrator's Guide.
C.2. Automatically Rebooting MS-DOS External on Critical Errors
---------------------------------------------------------------
A critical error is generated by MS-DOS when an unrecoverable situation
occurs in an application. When this happens, the message "Abort, Retry,
Fail?" is displayed--to continue using the application, the user must
respond. If, when MS-DOS External is running, a network connection fails due
to a problem at the file server, this type of critical error occurs. The MS-
DOS External Mail program traps the error and stops moving mail on the failed
connection, but continues to move mail on other connections. External tries
to re-establish the failed connection and MS-DOS successfully reconnects if
the condition that caused the critical error has been corrected.
In some environments, network redirectors become unstable following a
critical error. There is a possibility that the MS-DOS External Mail program
will not be able to re-establish the postoffice connection and will hang. If
this occurs, the computer on which the External Mail program is running must
be rebooted. Instead of manually rebooting the computer, you can specify an
External Mail program option to reboot automatically.
To specify automatic rebooting when critical errors occur, specify RebootOnCE
in the EXTERNAL.INI file. For example:
[External]
RebootOnCE
C.3. Specifying X.25 Facilities and User Data
---------------------------------------------
This section describes how to specify X.25 facilities and user data for mail
exchanged with other postoffices or mail received from Remote client users
through an X.25 public carrier. To set up X.25 communications for Microsoft
Mail, see Appendix F, "X.25 Settings for Mail," in the Microsoft Mail
Administrator's Guide.
By adding the following entries to an External .INI file, you can indicate
which facilities to initiate for an X.25 communication session. For
information about creating an External .INI file, see Chapter 12, "Setting Up
the External Program," in the Microsoft Mail Administrator's Guide.
You can specify one or more of these options to apply to all instances or for
a specific instance. You can also specify the call user options for each
postoffice being called.
If you specify the same option as a shared instance and as a specific
instance, External only initiates the specific instance. If, for call user
data, you specify only a specific postoffice, the last call user data entry
in the shared or specific instance is used. If you enter conflicting options
or if options are missing, the External program uses the option it finds
last.
X25CallFacilities option
Syntax: X25CallFacilities=[network/postoffice:]$value[$value]...
Use X25CallFacilities to specify which X25 call facility to initiate.
For a list of call facility codes, see your X.25 manual.
Specify the facility code in hexadecimal notation. Each hexadecimal value
must be prefixed by a dollar sign ($) and be a value from 0 to 9 and A to
F. You can specify up to 128 hexadecimal values. The maximum length cannot
exceed 401 characters.
For example, to reverse the charges when communicating with the SERVER1
postoffice on LAN1, where the facility code is hexadecimal 01 and its
parameter is hexadecimal 01, you would specify
X25CallFacilities=LAN1/SERVER1:$01$01
X25CallUserData option
Syntax: X25CallUserData=[network/postoffice:]$value[$value]...
Use X25CallUserData to specify the information to be validated by
External at the destination postoffice, or for call routing. For a list of
valid entries for call user data, see your X.25 manual.
Specify the data in hexadecimal. Each hexadecimal value must be prefixed by
a dollar sign ($) and be a value from 0 to 9 and A to F. You can specify up
to 128 hexadecimal values. The maximum length cannot exceed 406 characters.
You can specify this option for each postoffice if you need to. If you
specify both the postoffice and the data, the data you specify will be used
for validation. If you specify only the postoffice, External uses the
X25CallUserData specified for the shared instance.
X25ListenFacilities option
Syntax: X25ListenFacilities=$value[$value]...
Use X25ListenFacilities to specify which X25 listen facility to
initiate in a specify External instance. For a list of listen facility
codes, see your X.25 manual.
Specify the facility code in hexadecimal notation. Each hexadecimal value
must be prefixed by a dollar sign ($) and be a value from 0 to 9 and A to
F. You can specify up to 128 hexadecimal values. The maximum length cannot
exceed 384 characters.
For example, if facility code is hexadecimal 01 and its parameter is
hexadecimal 01, you would specify X25ListenFacilities=$01$01
X25ListenUserData option
Syntax: X25ListenUserData=$value[$value]...
Use X25ListenUserData to specify the information that External uses to
check against the incoming X.25 communication.
Specify the data in hexadecimal. Each hexadecimal value must be prefixed by
a dollar sign ($) and be a value from 0 to 9 and A to F. You can specify up
to 128 hexadecimal values. The maximum length cannot exceed 401 characters.
If this option is specified, the incoming call request packet must contain
identical user data; if it does not, the call is rejected.
Troubleshooting X.25 Facilities and User Data
If you use the LogVerbose option, all facility and user data is recorded in
the SESSION.LOG file.
If you do not enter the syntax of the .INI entry correctly, External stops
with the message "Invalid option specified in .INI: <option>." If the .INI
entry is syntactically correct, but the values you specified are
incorrect, a connection failure at the X.25 session layer could occur.
Note: Postoffices not defined or correctly specified in the Administrator
program, or incorrectly specified in the .INI file, cause External to stop.
If you use the LogVerbose option, a failure at the X.25 session level is
recorded and displayed on the External Remote Postoffice screen. The logged
information consists of the error type, such as a Call error or Read error,
and three or more octets of data. The first octet is the cause code, the
second octet is the diagnostic code, and the remaining octets are the Eicon
or Atlantis internal error codes.
Note: An octet is a two digit hexadecimal value.
For example, using the Eicon board, if a call failed, the following error
code could be displayed:
Call error:
00 42 12
The cause code of 00 and diagnostic code of 42 mean that a TD cleared the
call due to an invalid facility code (such as rejecting a reverse charge call
request). The third group of data, octet 12, specifies the Eicon or Atlantis
specific internal error code. The Atlantis internal error code is two octets.
The internal error code assists Microsoft Product Support Services (PSS) in
solving your problem.
The Atlantis version displays 4 bytes of data instead of 3. The first 2
bytes are the cause and diagnostic as per X.25 specifications. The last 2
bytes describe the return code made by the Atlantis X.25 services. This code
used by PSS.
D. INFORMATION FOR USERS OF THE MS-DOS CLIENT
=============================================
This section covers the following topic:
1. Connection time-out with Microsoft LAN Manager version 2.0
2. Saving an attachment with a long filename
3. Incompatible support files
4. Micro should be run before the MS-DOS 5.0 DOSSHELL
5. Micro should use the -f option with graphics applications
D.1. Connection Time-out with Microsoft LAN Manager version 2.0
---------------------------------------------------------------
Long spans of inactivity while the MS-DOS client is connected to a postoffice
on a LAN Manager version 2.0 server may lead to misleading error messages
such as "Disk Full" when the client is used again. This is caused by a
connection time-out with LAN Manager version 2.0 and does not occur with LAN
Manager version 2.1. If this occurs, change the KEEPCON line in the
LANMAN.INI file to KEEPCON=0.
D.2. Saving an Attachment with a Long Filename
----------------------------------------------
If a user has a problem accessing files from another program that were
created or saved by Microsoft Mail, ask him or her to remove any spaces in
the filename when saving the attachment in Microsoft Mail.
D.3. Incompatible Support Files
-------------------------------
If a user receives the message "Error file is not accessible. Check server
connection", it could be caused by a conflict between the user running the
MS-DOS client version 2.1 and the MS-DOS client version 3.0 installed on the
postoffice. To solve this problem, either upgrade the user to the MS-DOS
client version 3.0 or install MS-DOS client version 2.1 on the postoffice.
D.4. Micro Should be Run Before the MS-DOS 5.0 DOSSHELL
-------------------------------------------------------
The Micro mail notification TSR does not operate correctly when invoked from
an MS-DOS session started after starting DOSSHELL. To use Micro with the MS-
DOS shell, start Micro and then start DOSSHELL.
D.5. Micro Should Use the -F Option with Graphics Applications
--------------------------------------------------------------
If applications that switch the video into graphic modes are used, including
DOSSHELL in graphics mode, ask users to start Micro with the -F option.
However, due to variances in VGA hardware, problems could still occur when
using this option.
E. INFORMATION FOR USERS OF THE WINDOWS-BASED CLIENT
====================================================
This section covers the following topics:
1. Exporting Folders to a Transport Message File
2. Mail and SHARE.EXE
3. The MMF File
4. Accessing mail using more than one client
5. Send and receive privileges
6. Checking for new mail
7. Sending a bitmap as an attachment
8. Using Mail with Windows for Pen Computing
9. Deleting Message file backups
E.1. Exporting Folders to a Transport Message File
--------------------------------------------------
Do not use the Export Folders command on the File menu to copy folders into a
primary message storage file, such as the MSMAIL.MMF or MS_ATT.MMF file. If
users do, the Personal Address Book (PAB) in the destination primary message
storage file is overwritten. To avoid this problem, have users export the
folders to a temporary file (for example, FOLDER.MMF), and then use the
Import Folder command on the File menu to copy the folders into the other
primary transport message storage.
E.2. Mail and SHARE.EXE
-----------------------
If the user's message file (.MMF) is located on their local hard disk, they
must run SHARE.EXE before starting the Mail Windows-based client. Mail will
not start if they have not run SHARE.EXE.
SHARE.EXE is needed because the file that contains messages could be accessed
by other mail-related applications. It is important that each program
accessing your messages is able to lock portions of the file and protect
other mail-related applications from overwriting information in the file.
If the message file is located on the postoffice, SHARE.EXE is not needed.
IMPORTANT: When running Mail in Windows for Workgroups version 3.1 in 386
enhanced mode, VSHARE.386 is loaded automatically, so SHARE.EXE is not
needed.
E.3. The MMF File
-----------------
The Mail Windows-based client has many features such as the message finder,
offline composition, and an API that allows software developers to write new
applications that help manage your messages. These features require a new
file format for storing messages. With the new format, all messages are
stored in one file, with the extension MMF. Using one file makes backing up
and moving messages very easy. The MS-DOS and Macintosh clients cannot read
the new file format.
To convert messages from the old format to the new MMF format, Mail includes
a utility called CONVERT.EXE. For information about running CONVERT.EXE, see
the User's Guide for the Window's based client.
This message file can be kept on the postoffice server or on a local disk. If
it is kept on the postoffice, and the network connection to the postoffice is
broken, the message file is inaccessible to Mail. If the user runs Mail
offline in this case, Mail creates a temporary message file for use offline.
When Mail is run online again, it uses the message file on the postoffice and
messages created while offline are not in this file.
A user can create message files other than their primary message file. These
are created when using the Backup command on the Mail menu, the Export
Folders command on the File menu, or by creating a temporary offline file as
mentioned above. To access these message files, the user specifies the name
of the file in the command line when starting Mail, as follows:
msmail.exe /f <filename>
Mail opens the specified message file instead of the user's primary message
file, and starts offline. To revert to the user's primary message file, run
Mail without the /f parameter.
E.4. Accessing Mail using More than One Client
----------------------------------------------
If a user stores their primary message file locally but also dials in to the
Mail system with a modem, or uses a client in addition to the Windows client,
the user should select the Copy Inbox On Postoffice check box in the Server
dialog box.
To display the Server dialog box, choose the Options command from the Mail
menu, and then choose the Server button. A copy of the message file is
retained on the postoffice, providing the user with an up-to-date version of
their message file when they dial in.
E.5. Send and Receive Privileges
--------------------------------
The Presentation Manager client does not notify the user if he or she has no
send or receive privileges. For example, if a user with no receive privileges
checks for new mail, the user is informed that there are no new messages--not
that he or she has no receive privileges.
E.6. Checking for New Mail
--------------------------
The setting in the Options dialog box that controls how often Mail checks for
new mail also controls how often Mail checks the Outbox for messages to
submit to the postoffice. If it seems that messages are taking too long to
appear, remember that a message first waits in the Outbox and then waits
again until Mail checks for new messages. For example, if a user specifies
that Mail check for new mail every 3 minutes, they could wait up to 6 minutes
before receiving the new mail.
E.7. Sending a Bitmap as an Attachment
--------------------------------------
If a user sends a bitmap created in Paintbrush or another graphics
application, the recipient may not be able to view the bitmap if they are
using a monitor with a different resolution.
E.8. Using Mail with Windows for Pen Computing
----------------------------------------------
Although Mail is pen aware, there are some cases, such as running the Setup
program, where the user is not be able to write directly into a Mail edit
control. To use pen for input in these cases, run the Pen Palette in the
background.
E.9. Deleting Message File Backups
----------------------------------
In some circumstances, when Mail encounters problems in the message file
(.MMF), the user is asked if Mail should repair the file. Each time the
message file is repaired, Mail makes a backup copy of the file in the
directory containing the message file. The first backup file is named
<file>.BAK, where <file> is the name of the original message file. Subsequent
backup files are named <file>.001, <file>.002, and so on. For message files
stored on the postoffice, the <file> name is a number defined for the user
(for example, 00000021). For message files stored locally on the user's
computer, the <file> name is defined by the user. These backup files can be
deleted by the user or administrator.
F. INFORMATION FOR USERS OF THE PRESENTATION MANAGER CLIENT
===========================================================
This section covers the following topics:
1. Installing and running the Presentation Manager Client
2. About dialog box statistics
3. The MMF File
4. Accessing Mail using More than One Client
5. Send and receive privileges
6. Checking for new mail
7. Sending a bitmap as an attachment
8. Saving messages as files
9. Associating applications and files extensions
10. Copying file attachments to the Clipboard
11. Security setting in the MSMAIL.INI file
F.1. Installing and Running the Presentation Manager Client
-----------------------------------------------------------
The programs for the Windows-based and Presention Manager clients are on the
disks labeled Windows-based Client, Windows-based and OS/2 Presentation
Manager Workstation Software. To install the clients on the network, follow
the instructions in the Microsoft Mail Administrator's Guide.
On OS/2 version 2.0, users can run the Windows-based client. To set up the
Windows-based client, run the Setup program.
On OS/2 version 1.x, users must run the PM client. To set up the PM client,
run the Pmsetup program from an OS/2 window by typing PMSETUP at the OS/2
prompt.
F.2. About Dialog Box Statistics
--------------------------------
In the Presentation Manager client, the values for Memory and Disk Space in
the About dialog box may not be accurate.
F.3. The MMF File
-----------------
In Presentation Manager client version 3.2, all messages are stored in one
file, with the extension MMF--one file makes backing up and moving your
messages very easy. The MS-DOS and Macintosh clients cannot read the new file
format.
To convert messages from the old format used prior to version 3.0 to the new
.MMF format, use the Mail utility called CONVERT.EXE. For information about
running CONVERT.EXE, see the Microsoft Mail User's Guide for the Windows-
based client.
F.4. Accessing Mail using More than One Client
----------------------------------------------
If a user stores their primary message file locally but also dials in to the
Mail system with a modem, or uses a client in addition to the Windows client,
the user should select the Copy Inbox On Postoffice check box in the Server
dialog box.
To display the Server dialog box, choose the Options command from the Mail
menu, and then choose the Server button. A copy of the message file is
retained on the postoffice, providing the user with an up-to-date version of
their message file when they dial in.
F.5. Send and Receive Privileges
--------------------------------
The Presentation Manager client does not notify the user if he or she has no
send or receive privileges. For example, if a user with no receive privileges
checks for new mail, the user is informed that there are no new messages--not
that he or she has no receive privileges.
F.6. Checking for New Mail
--------------------------
The setting in the Options dialog box controlling how often Mail checks for
new mail also controls how often Mail checks the Outbox for messages to
submit to the postoffice. If it seems that messages are taking too long to
appear, remember that a message first waits in the Outbox and then waits
again until Mail checks for new messages. For example, if a user specifies
that Mail check for new mail every 3 minutes, they could wait up to 6 minutes
before receiving the new mail.
F.7. Sending a Bitmap as an Attachment
--------------------------------------
If a user sends a bitmap created in Paintbrush or another graphics
application, the recipient may not be able to view the bitmap if they are
using a monitor with a different resolution.
F.8. Saving Messages as Files
-----------------------------
If the user uses the Save As command on the File menu to save a message as a
text file, the text is saved in the ANSI code page. Extended characters may
not be preserved if the text file is opened in an application other than
Microsoft Mail.
F.9. Associating Applications and Files Extensions
--------------------------------------------------
The user can view an attachment by double-clicking it; however, to do this
in Presentation Manger, a section must be added to the WIN.INI file in their
OS2\DLL directory, in the following format:
[Extensions]
ext=c:\extapp.exe ^.ext
xls=c:\excel\excel.exe ^.xls
Type the file extension, an equal sign, the path and name of the application
to be to run, a space, a carat (^), and the file extension.
The carat is replaced with the name of the attachment. For example, if you
double-click a file called NAME.EXT, Mail executes the command "c:\extapp.exe
name.ext".
F.10. Copying File Attachments to the Clipboard
-----------------------------------------------
Users should not copy file attachments to the Clipboard--the Presentation
Manager Clipboard cannot handle file attachments.
F.11. Security Setting in the MSMAIL.INI File
---------------------------------------------
When using the Presentation Manager client, do not set Security=1 in
MSMAIL.INI. If Security=1 is set, the user cannot use the task switcher to
restore the application when they minimize Mail. The Security setting in
MSMAIL.INI controls whether a password is required to restore Mail when it is
minimized. If Security is set to 1, a password is required.
G. INFORMATION FOR USERS OF THE MACINTOSH CLIENT
================================================
This section covers the following topics:
1. Working offline with the Macintosh client
2. Attaching an object to a forwarded message
G.1. Working Offline with the Macintosh Client
----------------------------------------------
Under System 7, the user can use the Macintosh client to compose mail or
access private folders on a local drive even if the postoffice server is not
available. To use this feature, they select the Save My Name And Password
option button in the Preferences dialog box.
If the server goes down while the user is using Mail, they can reconnect
without leaving the Mail application. To do so, they should use the Chooser
to connect to the server--Microsoft Mail will find the postoffice.
G.2. Attaching an Object to a Forwarded Message
-----------------------------------------------
If the user is forwarding a message and want to send an attachment (OLE
object), have the user send the attachment in a separate message. Messages
attached to a forwarded message are not transmitted when the message is sent.
----------------------------------------
Microsoft Mail for PC Networks version 3.2
README File
----------------------------------------
(C) Copyright Microsoft Corporation, 1991-93
This document (README.TXT) contains important information that supplements
the Microsoft Mail version 3.2 manuals and online help provided in this
package. The manuals include the Microsoft Mail Administrator's Guide, the
Technical Reference manual, and the User's Guides for the MS-DOS client,
Windows-based and Presentation Manager clients, and Macintosh client.
This document covers the following topics:
A. How to print these notes
B. Information for Microsoft Mail administrators
C. External Mail program features not described in the Administrator's
Guide
D. Information for users of the MS-DOS client software
E. Information for users of the Windows-based client software
F. Information for users of the Presentation Manager client software
G. Information for users of the Macintosh client software
A. HOW TO PRINT THESE NOTES
===========================
To print these notes:
---------------------
1. Type: copy readme.txt printer:
Replace "printer:" with the port to which your printer is connected,
such as lpt1.
2. Press ENTER.
To print these notes from Microsoft Windows:
--------------------------------------------
To print README, open README.TXT in Windows Write, Microsoft Word, or another
word processor. Then select the entire document and format the text in 10-
point Courier before printing.
B. INFORMATION FOR MICROSOFT MAIL ADMINISTRATORS
================================================
This section covers the following topics:
1. Microsoft Mail Technical Reference
2. Supplementary Modem Scripts
3. Directory of text files installed by Setup
4. Modem Script return codes and external retries
5. Multiple modem messages in a script response buffer
6. Setting up Eicon Gateway software
7. Moving a user already defined in the Destination
Postoffice Address List
8. Import Utility example correction
9. Unencrypted password option no longer required for Novell
10. MS-DOS External and LAN MAN opportunistic locking
B.1. Microsoft Mail Technical Reference
---------------------------------------
The Microsoft Mail Technical Reference manual describes features that
administrators and programmers can use to extend and customize Mail in the
Windows environment. For information not included in the Technical Reference,
see the README.TXT file on the Technical Reference Server Programs disk.
B.2. Supplementary Modem Scripts
--------------------------------
Modem scripts used with the External Mail program are installed in the
postoffice directory when you run the Setup program (SETUP.EXE). The
Supplementary Modem Scripts disk contains additional modem scripts. For a
list of modem script files and installation instructions, see the README.TXT
file on the Supplementary Modem Scripts disk.
B.3. Directory of Text Files Installed by Setup
-----------------------------------------------
The Microsoft Mail Setup programs install the following text files in the
server programs directory you specified.
FILE CONTAINS
---- --------
ADMIN.TXT Administrator program error and status messages
CLIENT.TXT MS-DOS client and Macintosh client program error messages
DIRSYNC.TXT Directory Synchronization error and status messages
DISPATCH.TXT Dispatch program error messages for MS-DOS and OS/2
DYNADMIN.TXT Dynamic Drive Administrator program error messages
EXTERNAL.TXT External Mail program error messages for MS-DOS and OS/2
IMPORT.TXT Local User Import program error messages, LAN Manager and
Novell Extract Utility error messages
OS2MTA.TXT Readme file for the Microsoft Mail Multitasking MTA
README.TXT This file
SETUP.TXT Microsoft Mail Setup program error messages
SWITCHER.TXT Information about changing Mail System Drivers using the
Microsoft Mail System Selector
B.4. Modem Script Return Codes and External Retries
---------------------------------------------------
Processing of certain return codes from modem script files differs from
versions of Microsoft Mail prior to version 3.2. When the Call script returns
a result code of NoCarrier (4), NoDialTone (6), Busy (7), or NoAnswer (8),
the External program now increases the retries count on all mail that was
queued to be sent. If the retry count exceeds the number for the routing, the
mail is returned to the sender.
If a script you customized for a previous version of Mail is to be used with
the External Mail program version 3.2, check to see if the retry count on
script return codes 4, 6, 7, and 8 was used. If the script was designed so
that return code was not expected to increase the retries count, recompile
the script using return code 9--External does not increase the retry count if
encounters a script return code 9.
For more information about writing script files, see Appendix E, "Script
Files," in the Microsoft Mail Administrator's Guide.
B.5. Multiple Modem Messages in a Script Response Buffer
--------------------------------------------------------
When the External Mail program receives a message from a connected modem,
multiple messages can be put into the response buffer. If you are writing a
custom script or using a script from the Supplementary Scripts disk that was
written for modems manufactured outside of North America, use the ISIN
operator to check the response buffer. This is especially important for
incoming call messages.
Change the search for response return codes from:
if (response = "2^M")
to:
if ("2^M" isin response)
For more information about writing script files, see Appendix E, "Script
Files," in the Microsoft Mail Administrator's Guide.
B.6. Setting up the Eicon Gateway Software
------------------------------------------
For information about installing the Eicon Gateway software, see the Eicon
documentation and Appendix F, "X.25 Settings for Mail," in the Microsoft Mail
Administrator's Guide. Your Eicon setup must match the configuration of the
line leased from your X.25 carrier. Values vary by carrier and installation--
confirm all values set by the ECCFG program with your carrier.
The Microsoft Mail Administrator's Guide provides information about
parameters that are critical when setting up the Eicon board and software.
For the configuration option Number Of TVCs, a value of 004 is suggested. The
correct value depends on the line installed--a different value could be
appropriate for your configuration.
B.7. Moving a User Already Defined in the Destination Postoffice Address List
-----------------------------------------------------------------------------
You can use the Move User utility to move locally defined users between
postoffices. If you attempt to move User X from Postoffice A to Postoffice B,
and there is already an external address for User X in Postoffice B's
Postoffice Address List (POL), you are asked for another alias for user X
before you can move the user.
To avoid this situation, be sure that the external address for a user is
deleted on the destination postoffice before you move the user.
B.8. Import Utility Example Correction
--------------------------------------
On page 322 in the Microsoft Mail Administrator's Guide, in the section
"Examples of Running Import," the third example is incorrect.
The example should be:
import admin -ppassword -gsnads -x -fh:\snads.txt
B.9. Unencrypted Password Option No Longer Required for Novell
--------------------------------------------------------------
If you are running Microsoft Mail on a Novell network, and you are upgrading
your postoffice from a version of Microsoft Mail prior to 3.0, remove the SET
UNENCRIPTED PASSWORDS=ON option from the AUTOEXEC.NCF files. This setting was
previously required to properly configure dynamic drives for the External
Mail program.
B.10. MS-DOS External and LAN MAN opportunistic locking
-------------------------------------------------------
If External is running on a MS-DOS LAN MAN workstation with opportunistic
locks enabled, External may hang the workstation when trying to recover from
critical errors. When this occurs, External stops delivering mail and the
workstation must be restarted.
To avoid manually restarting the workstation, take one of these two
preventative measures:
1. In your LANMAN.INI file Workstation Section [workstation] turn off
opportunistic locking of files by turning off bit 0 in the wrkheuristics
entry. See appendix B of the Microsoft LAN Manager Administrator's Reference.
2. Use the External option RebootOnCE to automatically restart the
workstation on critical errors. See section C.2 in this document for more
details.
C. EXTERNAL MAIL PROGRAM FEATURES NOT DESCRIBED IN THE ADMINISTRATORS GUIDE
===========================================================================
This section covers the following topics:
1. Generic script file included with the Server
2. Automatically rebooting MS-DOS External on critical errors
3. Specifying X.25 facilities and user data
C.1. Generic Script File Included with the Server
-----------------------------------------------------
A new generic script file for Hayes-compatible modems is included with the
Microsoft Mail for PC Networks MS-DOS server version 3.2. The script file,
USGNERIC.MDM, is designed to operate with any modem compatible with the Hayes
AT command set. The generic script does not set the baud rate--the baud rate
is set using the Config Serial Baud-rate command in the Administrator
program.
The generic script is installed in the GLB directory of the postoffice
directory you specify when running the Setup program (SETUP.EXE). To use this
script, specify the option CommScript=USGNERIC in the External Mail program.
For more information about specifying scripts in the External Mail program,
see Chapter 12, "Setting Up the External Mail Program," in the Microsoft Mail
Administrator's Guide.
C.2. Automatically Rebooting MS-DOS External on Critical Errors
---------------------------------------------------------------
A critical error is generated by MS-DOS when an unrecoverable situation
occurs in an application. When this happens, the message "Abort, Retry,
Fail?" is displayed--to continue using the application, the user must
respond. If, when MS-DOS External is running, a network connection fails due
to a problem at the file server, this type of critical error occurs. The MS-
DOS External Mail program traps the error and stops moving mail on the failed
connection, but continues to move mail on other connections. External tries
to re-establish the failed connection and MS-DOS successfully reconnects if
the condition that caused the critical error has been corrected.
In some environments, network redirectors become unstable following a
critical error. There is a possibility that the MS-DOS External Mail program
will not be able to re-establish the postoffice connection and will hang. If
this occurs, the computer on which the External Mail program is running must
be rebooted. Instead of manually rebooting the computer, you can specify an
External Mail program option to reboot automatically.
To specify automatic rebooting when critical errors occur, specify RebootOnCE
in the EXTERNAL.INI file. For example:
[External]
RebootOnCE
C.3. Specifying X.25 Facilities and User Data
---------------------------------------------
This section describes how to specify X.25 facilities and user data for mail
exchanged with other postoffices or mail received from Remote client users
through an X.25 public carrier. To set up X.25 communications for Microsoft
Mail, see Appendix F, "X.25 Settings for Mail," in the Microsoft Mail
Administrator's Guide.
By adding the following entries to an External .INI file, you can indicate
which facilities to initiate for an X.25 communication session. For
information about creating an External .INI file, see Chapter 12, "Setting Up
the External Program," in the Microsoft Mail Administrator's Guide.
You can specify one or more of these options to apply to all instances or for
a specific instance. You can also specify the call user options for each
postoffice being called.
If you specify the same option as a shared instance and as a specific
instance, External only initiates the specific instance. If, for call user
data, you specify only a specific postoffice, the last call user data entry
in the shared or specific instance is used. If you enter conflicting options
or if options are missing, the External program uses the option it finds
last.
X25CallFacilities option
Syntax: X25CallFacilities=[network/postoffice:]$value[$value]...
Use X25CallFacilities to specify which X25 call facility to initiate.
For a list of call facility codes, see your X.25 manual.
Specify the facility code in hexadecimal notation. Each hexadecimal value
must be prefixed by a dollar sign ($) and be a value from 0 to 9 and A to
F. You can specify up to 128 hexadecimal values. The maximum length cannot
exceed 401 characters.
For example, to reverse the charges when communicating with the SERVER1
postoffice on LAN1, where the facility code is hexadecimal 01 and its
parameter is hexadecimal 01, you would specify
X25CallFacilities=LAN1/SERVER1:$01$01
X25CallUserData option
Syntax: X25CallUserData=[network/postoffice:]$value[$value]...
Use X25CallUserData to specify the information to be validated by
External at the destination postoffice, or for call routing. For a list of
valid entries for call user data, see your X.25 manual.
Specify the data in hexadecimal. Each hexadecimal value must be prefixed by
a dollar sign ($) and be a value from 0 to 9 and A to F. You can specify up
to 128 hexadecimal values. The maximum length cannot exceed 406 characters.
You can specify this option for each postoffice if you need to. If you
specify both the postoffice and the data, the data you specify will be used
for validation. If you specify only the postoffice, External uses the
X25CallUserData specified for the shared instance.
X25ListenFacilities option
Syntax: X25ListenFacilities=$value[$value]...
Use X25ListenFacilities to specify which X25 listen facility to
initiate in a specify External instance. For a list of listen facility
codes, see your X.25 manual.
Specify the facility code in hexadecimal notation. Each hexadecimal value
must be prefixed by a dollar sign ($) and be a value from 0 to 9 and A to
F. You can specify up to 128 hexadecimal values. The maximum length cannot
exceed 384 characters.
For example, if facility code is hexadecimal 01 and its parameter is
hexadecimal 01, you would specify X25ListenFacilities=$01$01
X25ListenUserData option
Syntax: X25ListenUserData=$value[$value]...
Use X25ListenUserData to specify the information that External uses to
check against the incoming X.25 communication.
Specify the data in hexadecimal. Each hexadecimal value must be prefixed by
a dollar sign ($) and be a value from 0 to 9 and A to F. You can specify up
to 128 hexadecimal values. The maximum length cannot exceed 401 characters.
If this option is specified, the incoming call request packet must contain
identical user data; if it does not, the call is rejected.
Troubleshooting X.25 Facilities and User Data
If you use the LogVerbose option, all facility and user data is recorded in
the SESSION.LOG file.
If you do not enter the syntax of the .INI entry correctly, External stops
with the message "Invalid option specified in .INI: <option>." If the .INI
entry is syntactically correct, but the values you specified are
incorrect, a connection failure at the X.25 session layer could occur.
Note: Postoffices not defined or correctly specified in the Administrator
program, or incorrectly specified in the .INI file, cause External to stop.
If you use the LogVerbose option, a failure at the X.25 session level is
recorded and displayed on the External Remote Postoffice screen. The logged
information consists of the error type, such as a Call error or Read error,
and three or more octets of data. The first octet is the cause code, the
second octet is the diagnostic code, and the remaining octets are the Eicon
or Atlantis internal error codes.
Note: An octet is a two digit hexadecimal value.
For example, using the Eicon board, if a call failed, the following error
code could be displayed:
Call error:
00 42 12
The cause code of 00 and diagnostic code of 42 mean that a TD cleared the
call due to an invalid facility code (such as rejecting a reverse charge call
request). The third group of data, octet 12, specifies the Eicon or Atlantis
specific internal error code. The Atlantis internal error code is two octets.
The internal error code assists Microsoft Product Support Services (PSS) in
solving your problem.
The Atlantis version displays 4 bytes of data instead of 3. The first 2
bytes are the cause and diagnostic as per X.25 specifications. The last 2
bytes describe the return code made by the Atlantis X.25 services. This code
used by PSS.
D. INFORMATION FOR USERS OF THE MS-DOS CLIENT
=============================================
This section covers the following topic:
1. Connection time-out with Microsoft LAN Manager version 2.0
2. Saving an attachment with a long filename
3. Incompatible support files
4. Micro should be run before the MS-DOS 5.0 DOSSHELL
5. Micro should use the -f option with graphics applications
D.1. Connection Time-out with Microsoft LAN Manager version 2.0
---------------------------------------------------------------
Long spans of inactivity while the MS-DOS client is connected to a postoffice
on a LAN Manager version 2.0 server may lead to misleading error messages
such as "Disk Full" when the client is used again. This is caused by a
connection time-out with LAN Manager version 2.0 and does not occur with LAN
Manager version 2.1. If this occurs, change the KEEPCON line in the
LANMAN.INI file to KEEPCON=0.
D.2. Saving an Attachment with a Long Filename
----------------------------------------------
If a user has a problem accessing files from another program that were
created or saved by Microsoft Mail, ask him or her to remove any spaces in
the filename when saving the attachment in Microsoft Mail.
D.3. Incompatible Support Files
-------------------------------
If a user receives the message "Error file is not accessible. Check server
connection", it could be caused by a conflict between the user running the
MS-DOS client version 2.1 and the MS-DOS client version 3.0 installed on the
postoffice. To solve this problem, either upgrade the user to the MS-DOS
client version 3.0 or install MS-DOS client version 2.1 on the postoffice.
D.4. Micro Should be Run Before the MS-DOS 5.0 DOSSHELL
-------------------------------------------------------
The Micro mail notification TSR does not operate correctly when invoked from
an MS-DOS session started after starting DOSSHELL. To use Micro with the MS-
DOS shell, start Micro and then start DOSSHELL.
D.5. Micro Should Use the -F Option with Graphics Applications
--------------------------------------------------------------
If applications that switch the video into graphic modes are used, including
DOSSHELL in graphics mode, ask users to start Micro with the -F option.
However, due to variances in VGA hardware, problems could still occur when
using this option.
E. INFORMATION FOR USERS OF THE WINDOWS-BASED CLIENT
====================================================
This section covers the following topics:
1. Exporting Folders to a Transport Message File
2. Mail and SHARE.EXE
3. The MMF File
4. Accessing mail using more than one client
5. Send and receive privileges
6. Checking for new mail
7. Sending a bitmap as an attachment
8. Using Mail with Windows for Pen Computing
9. Deleting Message file backups
E.1. Exporting Folders to a Transport Message File
--------------------------------------------------
Do not use the Export Folders command on the File menu to copy folders into a
primary message storage file, such as the MSMAIL.MMF or MS_ATT.MMF file. If
users do, the Personal Address Book (PAB) in the destination primary message
storage file is overwritten. To avoid this problem, have users export the
folders to a temporary file (for example, FOLDER.MMF), and then use the
Import Folder command on the File menu to copy the folders into the other
primary transport message storage.
E.2. Mail and SHARE.EXE
-----------------------
If the user's message file (.MMF) is located on their local hard disk, they
must run SHARE.EXE before starting the Mail Windows-based client. Mail will
not start if they have not run SHARE.EXE.
SHARE.EXE is needed because the file that contains messages could be accessed
by other mail-related applications. It is important that each program
accessing your messages is able to lock portions of the file and protect
other mail-related applications from overwriting information in the file.
If the message file is located on the postoffice, SHARE.EXE is not needed.
IMPORTANT: When running Mail in Windows for Workgroups version 3.1 in 386
enhanced mode, VSHARE.386 is loaded automatically, so SHARE.EXE is not
needed.
E.3. The MMF File
-----------------
The Mail Windows-based client has many features such as the message finder,
offline composition, and an API that allows software developers to write new
applications that help manage your messages. These features require a new
file format for storing messages. With the new format, all messages are
stored in one file, with the extension MMF. Using one file makes backing up
and moving messages very easy. The MS-DOS and Macintosh clients cannot read
the new file format.
To convert messages from the old format to the new MMF format, Mail includes
a utility called CONVERT.EXE. For information about running CONVERT.EXE, see
the User's Guide for the Window's based client.
This message file can be kept on the postoffice server or on a local disk. If
it is kept on the postoffice, and the network connection to the postoffice is
broken, the message file is inaccessible to Mail. If the user runs Mail
offline in this case, Mail creates a temporary message file for use offline.
When Mail is run online again, it uses the message file on the postoffice and
messages created while offline are not in this file.
A user can create message files other than their primary message file. These
are created when using the Backup command on the Mail menu, the Export
Folders command on the File menu, or by creating a temporary offline file as
mentioned above. To access these message files, the user specifies the name
of the file in the command line when starting Mail, as follows:
msmail.exe /f <filename>
Mail opens the specified message file instead of the user's primary message
file, and starts offline. To revert to the user's primary message file, run
Mail without the /f parameter.
E.4. Accessing Mail using More than One Client
----------------------------------------------
If a user stores their primary message file locally but also dials in to the
Mail system with a modem, or uses a client in addition to the Windows client,
the user should select the Copy Inbox On Postoffice check box in the Server
dialog box.
To display the Server dialog box, choose the Options command from the Mail
menu, and then choose the Server button. A copy of the message file is
retained on the postoffice, providing the user with an up-to-date version of
their message file when they dial in.
E.5. Send and Receive Privileges
--------------------------------
The Presentation Manager client does not notify the user if he or she has no
send or receive privileges. For example, if a user with no receive privileges
checks for new mail, the user is informed that there are no new messages--not
that he or she has no receive privileges.
E.6. Checking for New Mail
--------------------------
The setting in the Options dialog box that controls how often Mail checks for
new mail also controls how often Mail checks the Outbox for messages to
submit to the postoffice. If it seems that messages are taking too long to
appear, remember that a message first waits in the Outbox and then waits
again until Mail checks for new messages. For example, if a user specifies
that Mail check for new mail every 3 minutes, they could wait up to 6 minutes
before receiving the new mail.
E.7. Sending a Bitmap as an Attachment
--------------------------------------
If a user sends a bitmap created in Paintbrush or another graphics
application, the recipient may not be able to view the bitmap if they are
using a monitor with a different resolution.
E.8. Using Mail with Windows for Pen Computing
----------------------------------------------
Although Mail is pen aware, there are some cases, such as running the Setup
program, where the user is not be able to write directly into a Mail edit
control. To use pen for input in these cases, run the Pen Palette in the
background.
E.9. Deleting Message File Backups
----------------------------------
In some circumstances, when Mail encounters problems in the message file
(.MMF), the user is asked if Mail should repair the file. Each time the
message file is repaired, Mail makes a backup copy of the file in the
directory containing the message file. The first backup file is named
<file>.BAK, where <file> is the name of the original message file. Subsequent
backup files are named <file>.001, <file>.002, and so on. For message files
stored on the postoffice, the <file> name is a number defined for the user
(for example, 00000021). For message files stored locally on the user's
computer, the <file> name is defined by the user. These backup files can be
deleted by the user or administrator.
F. INFORMATION FOR USERS OF THE PRESENTATION MANAGER CLIENT
===========================================================
This section covers the following topics:
1. Installing and running the Presentation Manager Client
2. About dialog box statistics
3. The MMF File
4. Accessing Mail using More than One Client
5. Send and receive privileges
6. Checking for new mail
7. Sending a bitmap as an attachment
8. Saving messages as files
9. Associating applications and files extensions
10. Copying file attachments to the Clipboard
11. Security setting in the MSMAIL.INI file
F.1. Installing and Running the Presentation Manager Client
-----------------------------------------------------------
The programs for the Windows-based and Presention Manager clients are on the
disks labeled Windows-based Client, Windows-based and OS/2 Presentation
Manager Workstation Software. To install the clients on the network, follow
the instructions in the Microsoft Mail Administrator's Guide.
On OS/2 version 2.0, users can run the Windows-based client. To set up the
Windows-based client, run the Setup program.
On OS/2 version 1.x, users must run the PM client. To set up the PM client,
run the Pmsetup program from an OS/2 window by typing PMSETUP at the OS/2
prompt.
F.2. About Dialog Box Statistics
--------------------------------
In the Presentation Manager client, the values for Memory and Disk Space in
the About dialog box may not be accurate.
F.3. The MMF File
-----------------
In Presentation Manager client version 3.2, all messages are stored in one
file, with the extension MMF--one file makes backing up and moving your
messages very easy. The MS-DOS and Macintosh clients cannot read the new file
format.
To convert messages from the old format used prior to version 3.0 to the new
.MMF format, use the Mail utility called CONVERT.EXE. For information about
running CONVERT.EXE, see the Microsoft Mail User's Guide for the Windows-
based client.
F.4. Accessing Mail using More than One Client
----------------------------------------------
If a user stores their primary message file locally but also dials in to the
Mail system with a modem, or uses a client in addition to the Windows client,
the user should select the Copy Inbox On Postoffice check box in the Server
dialog box.
To display the Server dialog box, choose the Options command from the Mail
menu, and then choose the Server button. A copy of the message file is
retained on the postoffice, providing the user with an up-to-date version of
their message file when they dial in.
F.5. Send and Receive Privileges
--------------------------------
The Presentation Manager client does not notify the user if he or she has no
send or receive privileges. For example, if a user with no receive privileges
checks for new mail, the user is informed that there are no new messages--not
that he or she has no receive privileges.
F.6. Checking for New Mail
--------------------------
The setting in the Options dialog box controlling how often Mail checks for
new mail also controls how often Mail checks the Outbox for messages to
submit to the postoffice. If it seems that messages are taking too long to
appear, remember that a message first waits in the Outbox and then waits
again until Mail checks for new messages. For example, if a user specifies
that Mail check for new mail every 3 minutes, they could wait up to 6 minutes
before receiving the new mail.
F.7. Sending a Bitmap as an Attachment
--------------------------------------
If a user sends a bitmap created in Paintbrush or another graphics
application, the recipient may not be able to view the bitmap if they are
using a monitor with a different resolution.
F.8. Saving Messages as Files
-----------------------------
If the user uses the Save As command on the File menu to save a message as a
text file, the text is saved in the ANSI code page. Extended characters may
not be preserved if the text file is opened in an application other than
Microsoft Mail.
F.9. Associating Applications and Files Extensions
--------------------------------------------------
The user can view an attachment by double-clicking it; however, to do this
in Presentation Manger, a section must be added to the WIN.INI file in their
OS2\DLL directory, in the following format:
[Extensions]
ext=c:\extapp.exe ^.ext
xls=c:\excel\excel.exe ^.xls
Type the file extension, an equal sign, the path and name of the application
to be to run, a space, a carat (^), and the file extension.
The carat is replaced with the name of the attachment. For example, if you
double-click a file called NAME.EXT, Mail executes the command "c:\extapp.exe
name.ext".
F.10. Copying File Attachments to the Clipboard
-----------------------------------------------
Users should not copy file attachments to the Clipboard--the Presentation
Manager Clipboard cannot handle file attachments.
F.11. Security Setting in the MSMAIL.INI File
---------------------------------------------
When using the Presentation Manager client, do not set Security=1 in
MSMAIL.INI. If Security=1 is set, the user cannot use the task switcher to
restore the application when they minimize Mail. The Security setting in
MSMAIL.INI controls whether a password is required to restore Mail when it is
minimized. If Security is set to 1, a password is required.
G. INFORMATION FOR USERS OF THE MACINTOSH CLIENT
================================================
This section covers the following topics:
1. Working offline with the Macintosh client
2. Attaching an object to a forwarded message
G.1. Working Offline with the Macintosh Client
----------------------------------------------
Under System 7, the user can use the Macintosh client to compose mail or
access private folders on a local drive even if the postoffice server is not
available. To use this feature, they select the Save My Name And Password
option button in the Preferences dialog box.
If the server goes down while the user is using Mail, they can reconnect
without leaving the Mail application. To do so, they should use the Chooser
to connect to the server--Microsoft Mail will find the postoffice.
G.2. Attaching an Object to a Forwarded Message
-----------------------------------------------
If the user is forwarding a message and want to send an attachment (OLE
object), have the user send the attachment in a separate message. Messages
attached to a forwarded message are not transmitted when the message is sent.
3.1 LAN PACKAGE README FILE There are two additions to the new features incorporated in Version 3.1 of the cc:Mail LAN Package that were not added in time to be included in the Version 3.1 Release Notes. They include: o cc:Mail DOS Shell o HOME and END Keys Edit Subjects and Titles CC:MAIL DOS SHELL cc:Mail users running the 3.1 LAN Package on their MS-DOS PCs can now return to DOS and enter DOS commands without leaving the cc:Mail application by using cc:Mail's new DOS shell feature. To return to DOS from within cc:Mail, users must be at a cc:Mail menu. The DOS shell feature cannot be accessed from within a cc:Mail message, message item, or while addressing a cc:Mail message. To access the DOS shell: o Press F9 while at a cc:Mail menu . The Microsoft MS-DOS copyright screen appears along with the DOS prompt showing your current drive and directory. o Type any DOS command you desire and press ENTER. The DOS command is executed as any other DOS command. o When you are finished entering DOS commands, type EXIT at the DOS prompt. You are returned to the cc:Mail menu you were using when you entered the DOS Shell. HOME AND END KEYS The HOME and END keys now move the cursor when you are editing the Subject: line of a cc:Mail message, and while editing message item titles. Press END to move the cursor to the right end of the subject or the message item title. Press HOME to move the cursor to the left end of the line. The HOME and END keys also move the cursor to the left and right ends of the text item margin line while you are setting the left and right text item margins . Press END to move the cursor to the right end of the margin line. Press HOME to move the cursor to the left end of the margin line. RUNNING CC:MAIL WITH WINDOWS If you run the cc:Mail Version 3.1 LAN Package with Microsoft Windows, you must create a PIF file named MAIL.PIF using the Program Information (PIF) Editor. Type the following information in the PIF Editor screen: Program Name: MAIL.EXE Program Title: cc:Mail KB Required: 350 KB Desired: 350 USAGE: Full Screen [X] Program Switch: (*) Graphics/Multiple Text Screen Exchange: (*) Graphics/Text Close Window on Exit [X] You may put your own name and password in the Parameters field. The Initial Directory field may be blank, or be a private work area. Include the TONE parameter in the Notify and Messenger DOS command lines to prevent the pop-up window from conflicting with the Windows screen.
This document contains information that does not currently appear in
the manual.
------------------------------ General Info -------------------------------
Running both the DOS and Windows versions of cc:Mail:
It is NOT a good idea to have both the DOS and Windows versions
of cc:Mail running at the same time. If you modify the data of
your mail account (e.g. delete messages from the Inbox) using one
program, you will easily confuse the other instance of cc:Mail.
If you want to run the DOS version of cc:Mail, close the Windows
version first, and vise-versa.
cc:Mail for Windows viewer filters:
cc:Mail for Windows provides a facility for viewing the contents of
files attached to messages in their original format. For example,
if you receive the Windows chess.bmp file, you can see that image by
double-clicking on that item in the Message Item list.
The special routines which enable cc:Mail to display different file
formats are contained in filters. If you look in the cc:Mail for
Windows program directory, you will find files with the ".FLT"
extension. These are the cc:Mail file viewing filters. For example,
the file "BMP.FLT" is the filter used when viewing Windows bitmap files.
We will be providing users with additional filters for other file
formats as they become available.
* Note: If you have a file attachment that you wish to view, and
cc:Mail doesn't have the filter for that particular format, you may
be able to <SHIFT>-double-click on it to launch an application that
does support the file format. cc:Mail indicates that such an
application is available by using the icon that represents the
application on Window's Program Manager desktop, for the item in the
cc:Mail Message Item list.
ccBackup
A new small utility program called ccBackup has been written to
make it easier to backup a cc:Mail database. The program and it's
documentation are included on this diskette in the CCBACKUP
subdirectory. Note that the ccBackup program is NOT installed
automatically by the installation program.
Launching MS-DOS or Windows Versions of cc:Mail from Windows Notify
Windows Notify supports launching either cc:Mail for MS-DOS or
cc:Mail for Windows. When cc:Mail for Windows is installed, it
automatically configures Windows Notify to launch cc:Mail for
Windows. It does this by setting the value assigned to the
"Notify" keyword in the [cc:Mail] section of the WIN.INI file
to 1 ("Notify=1"). If you install cc:Mail for Windows and
still want Windows Notify to launch cc:Mail for MS-DOS, change
WIN.INI so that the value assigned to the Notify keyword is 0
("Notify=0").
Technical MAIL.PIF Issues
To launch DOS Mail from Notify you MUST use a .PIF file.
Windows Notify executes MAIL.PIF, which in turn executes MAIL.EXE.
The order that Windows 3.0 will normally search for MAIL.PIF and
MAIL.EXE is 1) in the directory where WNOTIFY.EXE is located, 2) in
the WINDOWS directory, and 3) in the directories named in your
DOS PATH.
If Windows Notify is located on a network and individual users
need to customize the MAIL.PIF file, the copy of MAIL.PIF in
the same directory as WNOTIFY.EXE should be deleted. Then each
user can place a customized MAIL.PIF in their WINDOWS directory
and it will be used.
If MAIL.PIF is modified to include an explicit path in the
"Program Filename" field (e.g. "M:\CCMAIL\MAIL.EXE"), Windows
will use that path to find MAIL.EXE rather than using the
algorithm described above. However, MAIL.EXE is normally in
the same directory as WNOTIFY.EXE, so this should not be
necessary.
The directory that MAIL.EXE will use as its default directory
for reading and writing files is specified in the "Start-up
Directory" field of MAIL.PIF ("C:\" in the distributed
MAIL.PIF). If this field is blank, the start-up directory is
the directory Windows Notify was executed from, which is
generally incorrect because MAIL.EXE requires the user to have
file creation and write privileges in the start-up directory.
The "Optional Parameters" field in MAIL.PIF must be left blank.
Automatic Directory Exchange
If you are going to be using Automatic Directory Exchange, please
read the README.TXT file which is distributed with that product for
additional issues which may affect you.
Installation on '486 Workstations
On some '486 workstations, the installation program may indicate a
spurious error ("Invalid Drive Letter or Drive Not Ready. Press
ESC") when you select "Start Installation". If this occurs, press
Esc (as indicated) to dismiss the error, and the installation will
proceed correctly.
"Bank-shot" Routing
There is a method to bypass the 200 name limit on mailing lists
when using multiple post offices, known as "bank-shot routing."
More information is available from the new cc:Mail Technical
Support bulletin board system.
---------------------------------- Tips -----------------------------------
cc:Mail and other applications:
When launching applications from within cc:Mail for Windows, some do not
allow a second copy (multiple instances) of the program to be run. In
this case, the currently running application normally posts a message
box notifing the user of this condition. For example, Microsoft Word
v1.1 displays a message box which reads: "Microsoft Word -
Word is already running". These messages obviously vary from
application to application. You also may find that some
applications do not post any message box but instead restore the
previous instance of the running application, ala cc:Mail. In this
case, the application which was launched by cc:Mail has exited even
though you are presented with the application (first instance), just as
if you switched tasks to the other application. As a rule of thumb,
make sure there are no other instances of the attachment application
running prior to running it from within cc:Mail, unless you know it runs
multiple instances.
When an application is launched from cc:Mail, it should be closed before
you come back to work in cc:Mail. If you try to "re-open" cc:Mail, you
are presented with a message box asking if you want to:
1. Resume editing the attachment (YES)
2. Go on to another application, besides cc:Mail (NO)
3. Close the attachment application and return to cc:Mail (Cancel)
In the case of #3 (Cancel), if the associataed application is a DOS
application, you'll want to make sure that you have "Allow Close when
Active" turned on in the program's information file (PIF). This allows
you to cancel the application at this point and return to cc:Mail
without attaching the file. However, the easier way of cancelling an
attachment would be to simply exit the application and cancel when
prompted for a file prefix.
Clipboard folders and private mailing lists:
You may notice, if you cut and paste messages or addresses,
that special folders and/or mailing lists named "clipboard"
appear in the Folder List and/or the Mailing List windows.
These contain the results of a cut or copy operation of messages
or addresses. The contents of a "clipboard" will be copied into
a destination list when you perform the paste operation.
The user is allowed to perform a limit number of actions on these
lists. (e.g. while you are not allowed to open a clipboard list,
you may delete it.)
NOTES ON MICROSOFT MAIL GATEWAY TO FAX ====================================== This document supplements the information in the Microsoft Mail Gateway to FAX Administrator's Guide and includes the following topics: - Including extended characters in PROFILE.GLB - Saving changes when using PROFILE.EXE - Viewing faxes with Windows for Workgroups - PPB.EXE missing when no MS-DOS client installed - Gateway to Fax not deleting temporary DCX files - Sending attachments through a GammaLink board For additional information, see also the Microsoft Mail Gateway to Fax Release Notes. Including extended characters in PROFILE.GLB ============================================ If you have difficulty entering extended characters into the PROFILE.GLB file using PROFILE.EXE, use a standard text editor instead. Saving changes when using PROFILE.EXE ===================================== When using PROFILE.EXE, you must press ENTER to accept your changes before quitting PROFILE.EXE. If you do not, even if you indicate that modifications should be saved, the last change will not be saved. Viewing faxes with Windows for Workgroups ========================================= If you are using Windows for Workgroups, and you haven't upgraded your Windows clients with the client shipped with the Microsoft Mail and Schedule+ Extensions to Windows for Workgroups product, you need to do the following two things to view faxes: - Copy FAXVIEW.EXE and FAXVIEW.HLP to the Windows directory. These files are in the Microsoft Mail and Schedule+ Extensions to Windows for Workgroups product. - To associate .DCX files with FAXVIEW.EXE, add the following line to the [Extensions] section of WIN.INI: dcx=C:\WINDOWS\FAXVIEW.EXE ^.dcx PPB.EXE missing when no MS-DOS client installed =============================================== PPB.EXE is used by the Gateway to FAX to spool faxes to a printer. The Gateway to FAX Administrator's Guide states incorrectly that this file is copied to the Microsoft Mail executables directory when you install the server. Actually this file is copied when you install the MS-DOS client. If you haven't installed the MS-DOS client, and want to spool faxes to a printer, install the MS-DOS client. Gateway to FAX not deleting temporary DCX files =============================================== If temporary files created by the Gateway to FAX are not being deleted from the network drives, store the temporary files on the gateway PC instead. To control the location of the temporary files created by the Gateway to FAX, do the following: 1. Create a subdirectory on the hard drive of the gateway PC. 2. Move the fax logo file to this subdirectory. 3. In PROFILE.GLB, change the location of the fax logo file to reflect the new location. All temporary files will be placed in this directory and deleted when required. Storing the temporary files locally also reduces network traffic. Sending attachments through a GammaLink board ============================================= The only kind of attachments that can be sent when using a GammaLink board are DCX and Text attachments. You can not send PCX attachments.
*********************************************************************
BitFax/OCR for Windows
Version 2.0
BIT Software, Inc.
README.DOC
July 15, 1992
*********************************************************************
Welcome to BitFax/OCR for Windows. The following contains important
information that was not available when the User's Manual was printed.
____________________________________________________________________
Upgrading from BitFax for Windows version 2.0
Since BitFax for Windows version 2.0 uses the same transmit and receive
logs and the same phone book (PHNBOOK.DBF) as BitFax/OCR, we suggest you
install BitFax/OCR in your existing BitFax for Windows directory. This
way you can keep your existing phone book records and transmission
records. BitFax/OCR will not overwrite your phone book and log files,
but it will overwrite your old program files.
If you install BitFax/OCR in a different directory, you can use your old
phone book by copying the phone book file (PHNBOOK.DBF) to the
BitFax/OCR directory.
____________________________________________________________________
Upgrading from BitFax for Windows version 1.0x
BitFax/OCR for Windows will not be able to use your old transmit and
receive logs created from BitFax 1.0x. The Transmit Log and Receive Log
in BitFax/OCR are more comprehensive and use a different format.
The phone books, however, are the same, so you can keep your existing
phone book records. Just copy your old phone pook file (PHNBOOK.DBF) to
the BitFax/OCR for Windows directory.
____________________________________________________________________
Upgrading from BitFax for DOS
If you are upgrading from BitFax for DOS to BitFax/OCR for Windows, you
can keep your existing Phone Book. Simply copy your old Phone Book
file(FAXBOOK.DBF) to the BitFax/OCR for Windows directory and rename it
PHNBOOK.DBF. You can use the DOS COPY command to copy your old Phone
Book to the BFOCR directory. For example:
COPY C:\BITFAX\FAXBOOK.DBF C:\BFOCR\PHNBOOK.DBF.
The Phone Book in the Windows version is called PHNBOOK.DBF.
____________________________________________________________________
Special Note
* OCR Accuracy
The accuracy of optical character recognition depends on the quality
and resolutions of the original fax. BitFax/OCR works best with faxes
that are clearly printed and sent in Fine mode (200 by 200 dpi). How
you send a fax in Fine mode depends on the fax machine you are using.
Most fax machines have a Mode or Resolution button that lets you
change the resolution. Before your associates send you a fax, they
should change the resolution from Normal or Standard to Fine.
____________________________________________________________________
Application Notes
* Microsoft Works for Windows
Before you can send a fax from Microsoft Works, you must first choose
BitFax as your default printer. Unlike most Windows applications,
Microsoft Works uses only the default printer and does not allow you
to switch between printers. To choose BitFax as your default printer,
open Windows Control Panel in the Main group window, double-click the
Printer icon and select BitFax on COMx. If you are using Windows 3.0,
double-click the BitFax selection to set it as the default printer. If
you are using Windows 3.1, select the BitFax driver and click on the
Set as Default Printer button.
* WordPerfect for Windows
When you choose BitFax Driver as your printer, select the Windows
option in the Printer Drivers section of the Select Printer dialog
box.
INTRODUCTION Quick Fax Cover Sheet (QFCS) is a convenient shareware program for printing facsimile cover sheets under Windows 3.x. It allows the user to set up default sender information which will load whenever QFCS is started as well as the option to select alternate sender information. It also allows the user to set up a database of frequently used receivers along with their fax numbers. Fax cover sheets may also be saved to disk for later reference. The user may opt to engage a log file to record details of all printed cover sheets. A Quick-Icon control panel plus a graphical system to drag and drop Senders, Receivers and saved cover sheets insures ease of use. All system specific fonts are supported as well as provision for alignment adjustment. Custom logos and bitmaps may be included on the cover sheet (requires 300 DPI non-postcript printer) 6 custom logos are included. All user configurable settings are saved in a standard INI file format. FILES INCLUDED * QFCS.EXE - MAIN PROGRAM FILE * QFCS.HLP - HELP INFO CALLED FROM HELP MENU * QFCS.IDX - HELP PROGRAM INDEX FILE * DEFAULT.DAT - DEFAULT SENDER DATA ALT1.DAT - ALTERNATE SENDER EXAMPLE * RECEIVER.DB - DEFAULT RECEIVER DATABASE FILE SAMPLE.FAX - SAMPLE FAX COVER SHEET * STATUS.DLL - DYNAMIC LINK LIBRARY * PSETUP.DLL - DYNAMIC LINK LIBRARY * ENUMFONT.DLL - DYNAMIC LINK LIBRARY FAXHIST.LOG - EXAMPLE OF HISTORY LOG FILE README.TXT - INITIAL INSTRUCTIONS LOGO1-6.BMP - 6 SEPARATE LOGO FILES IN BITMAP FORMAT COMPLOGO.BMP - EXAMPLE OF A COMPANY LOGO INCLUDING ADDRESS, PHONE, ETC. INSTALL.EXE - QFCS INSTALLATION PROGRAM INSTALL.INF - INSTALLATION DATA * Denotes files necessary for program function. INSTALLATION Execute INSTALL.EXE from within Windows. Install will create a sub-directory of your choice, copy all distribution files and create a Program Manager Group for QFCS if you desire OR you may manually copy all distribution files to the directory of your choice (you may delete README.DOC after review).Use Windows Program Manager, the Windows Setup program or an equivalent process to install.Requires VBRUN100.DLL, not included - (Can be downloaded as VBRUN.ZIP in Compuserve MS Windows Advanced Forum). FIRST TIME USE Complete help for first time use is available from the Help menu or by pressing the F1 key. UPGRADING If you have been using a version of QFCS older than V2.0, do not use your existing *.DAT (Sender) files. A new field was added in V2.0 that provides for a description of the Sender, if you try to load the existing file two error messages will result "Input Past End Of File" & "File Already Open" - You will probably have to re-boot your system at this point so DON'T USE OLD *.DAT FILES!. Erase your old *.DAT files before installation! The RECEIVER.DB file is still compatible, however due to the file handling structure of V2.0+, no other *.DB files other than RECEIVER.DB are usable. If you created other *.DB files for different categories of receivers they will no longer be accessible from the program. When re-installing - copy QFCS.EXE, QFCS.HLP, QFCS.IDX, DEFAULT.DAT, RECEIVER.DB, SAMPLE.FAX and STATUS.DLL to a new subdirectory and then copy your existing RECEIVER.DB into the subdirectory overwriting the new RECEIVER.DB file. Any existing cover sheet .FAX files from version 2.0 may be loaded, however, only the first line of notes text will be loaded since this version now has a single multi line text box instead of the previous four single line boxes. Version 2.30 now requires all three .DLL files (STATUS.DLL, PSETUP.DLL and ENUMFONT.DLL) to function. Existing QFCS.INI or QFCSR.INI files may be deleted since, starting with V2.3, a standard INI file in the Windows directory is created. >END
------------------------------------------------------------------------------- WinFax PRO 3 README Notes November 12, 1992 =============================================================================== The following information reflects changes made since the WinFax PRO User's Guide went to press, and should be reviewed prior to running WinFax PRO. See also the document entitled Late Breaking News, if one is included in your WinFax PRO package. Where applicable, these notes cross reference sections in the WinFax PRO User's Guide. Filling in Cover Pages (page 3-17) ---------------------------------- Use the Windows text editing quick keys to cut (Ctrl+X), copy (Ctrl+C) and paste (Ctrl+V) text in Cover Page Filler. Moving Phonebooks (page 4-2) ---------------------------- To move a phonebook created in WinFax to a new directory ... 1. Create a new directory for the phonebook files. 2. From either DOS or the Windows File Manager, copy the phonebook files to the new directory. A phonebook actually consists of seven files - two database (.DBF) and five index (.NDX) files. For example, the default WinFax phonebook consists of the following files: DEFAULT.DBF DEFAULTG.DBF DEFAULT1.NDX DEFAULT2.NDX DEFAULT5.NDX DEFAULT6.NDX DEFAULT7.NDX 3. Go to WinFax, and select the Phonebook List command. 4. From the Phonebook List dialog, delete the reference to the phonebook you just moved from the list. 5. While still on the Phonebook List dialog, select Add. From the Add Phonebook dialog, reselect the main phonebook .DBF file (such as DEFAULT.DBF) from its new directory location. Installing and Running WinFax (page A-9) ---------------------------------------- To use WinFax PRO with a non-standard COM port in Windows, add a setting such as one of the following to the [386Enh] section of your Windows SYSTEM.INI file: COM3Irq=5 COM3Base=03E8 or COM4Irq=5 COM4Base=02E8 The IRQ 5 replacement is suggested for most systems, as it is the interrupt for LPT2, and most likely to be available. WINFAX.INI Considerations ------------------------- If you delete your WINFAX.INI file at any time, most of the WinFax program preference settings that were contained in the file will be recreated when you next run the program. However, the settings for graphic formats that can be loaded into WinFax (chiefly the Cover Page Designer) are not recreated, and must be restored by copying the following back into your WINFAX.INI file: [WinFax Importers] Windows Bitmap (*.bmp)=BMP,DTIFLBMP.DLL,*.DIB;*.BMP Windows Metafile (*.wmf)=WMF,DTIFLWMF.DLL,*.WMF TIFF (*.tif)=TIF,DTIFLTIF.DLL,*.TIF PC Paintbrush (*.pcx)=PCX,DTIFLPCX.DLL,*.PCX GEM Image (*.img)=IMG,DTIFLIMG.DLL,*.IMG GEM Metafile (*.gem)=GEM,DTIFLGEM.DLL,*.GEM Mac Paint (*.bin)=PNT,DTIFLPNT.DLL,*.BIN Encap. Postscript (*.eps)=EPS,DTIFLEPS.DLL,*.EPS Gr. Interchange (*.gif)=GIF,DTIFLGIF.DLL,*.GIF WinFax (*.fxs)=FXS,DTIFLFXS.DLL,*.FXS Cover Your Fax and Adobe Type Manager ------------------------------------- The "Cover Your Fax" fax cover pages included with WinFax PRO 3.0 were designed in Windows 3.1 using the True Type fonts Arial, and New Times Roman. If you are running Windows 3.1 with the True Type Fonts enabled, then you can ignore this section. If, however, you are running Windows 3.0 with Adobe Type Manager, or you are running Windows 3.1 and you have opted to use ATM with True Type disabled, add the following lines to the ATM.INI file located in the Windows directory. It is recommended that you cut & paste the information into the target file. If your copy of ATM includes Arial MT and TimesNewRomanPS but does not include Helvetica or Times, add the following two lines to the [Aliases] section of the ATM.INI file... Arial=Arial MT Times New Roman=TimesNewRomanPS If your copy of ATM includes Helvetica and Times but does not include Arial MT or TimesNewRomanPS, add the following lines to the [Aliases] section of the ATM.INI file... Arial=Helvetica Times New Roman=Times To view a list of the fonts included in your installation of ATM, open the ATM Control Panel and check in the Installed ATM Fonts: list box.
------------------------------------------------------------------
Delrina WinFax PRO 4.0 README Notes March 20, 1994
==================================================================
The following information reflects changes made since the Delrina
WinFax PRO Setup Guide and User's Guide went to press, and should
be reviewed prior to running WinFax.
Where applicable, these notes refer to specific sections in the
appropriate manual.
WinFax online help can provide you with detailed information when
you need it most -- while you are using WinFax. To get help from
any dialog or window in WinFax, press F1.
Important Information
=====================
Unfortunately, due to unforeseen circumstances, Delrina is unable
to offer the Fax MailBox Service or the remote retrieval feature
at this time.
We ask that you ignore all references to Delrina Fax MailBox
Service or the remote retrieval capability in your WinFax PRO
manuals and other materials.
We apologize for any inconvenience this recent change may have
caused.
General
=======
Load SHARE.EXE for installing and running WinFax
------------------------------------------------
Running SHARE is strongly recommended, both for installing and
running WinFax PRO 4.0.
SHARE is a DOS program that provides file sharing and locking
capabilities. Running SHARE prevents a file or database record
from being edited by two applications at the same time, which
might result in data loss. Using SHARE with WinFax is recommended
if several people have a common phonebook on a network, or
otherwise share data. SHARE also enhances OCR and phonebook
functionality.
The command to load SHARE can be run at the DOS prompt, or
added to your AUTOEXEC.BAT or CONFIG.SYS file. Check your
DOS manual for the setting suitable for your system.
Upgrading from a previous version of WinFax
(Setup Guide, page 2-10)
-------------------------------------------
If you install WinFax PRO 4.0 in a different location than your
old version of WinFax, your old send and receive logs are NOT
automatically linked or converted. To create a folder containing
your old sent and received faxes:
1. In the WinFax main module, open the Send Log or Receive Log
window.
2. In the Folder list, double click New Folder. The New Archive
folder dialog appears.
3. Type a folder name.
4. Click Select. The Archive Filename dialog appears. Specify or
select the location of your old send and receive log file. The
file name is STATUS.FTM and is located in your old
\WINFAX\DATA directory. Click OK.
5. In the New Archive folder dialog, click OK.
Creating an archive folder for old send and receive events does
not move the actual fax images to your new WinFax directory. Do
not delete your old WinFax \DATA directory or your archived
events will be lost.
You can use the same procedure to import old archive folders. An
archive folder has an .FTM extension.
Comma pause time and credit card dial strings
---------------------------------------------
The default comma pause time in WinFax PRO 4.0 is 2 seconds, and
you cannot modify this value from within the program. During
installation, the WinFax Setup program will detect if you have set
a comma pause time value of greater than 2 in a previous version
of WinFax. If detected, any existing credit card dial strings will
be automatically supplemented with additional commas up to what
the Credit Card Number field will accommodate within its 20-
character limit. Each comma in the dial string will be replaced
with the appropriate number of additional commas (rounding up).
For example, if the comma pause time was set to 3 seconds in
WinFax PRO 3.0, a credit card string of ...
82,,123456
... would change to ...
82,,,,123456
If you have used commas for pauses in dial prefixes or phone
numbers in any phonebook records, you must adjust those
individually after installing WinFax PRO 4.0.
Fax-a-File/File Transfer Considerations
---------------------------------------
If you have a Class 1 or CAS fax/modem, you can use Fax-a-File
for transferring binary files. Check the following list for a
description of the event transmission types supported by
your fax/modem.
* Class 1 fax/modems support the following Fax-a-File event
transmission types:
BFT
---
When you select BFT, WinFax determines the capabilities of
the remote device and sends your event using either of the
following BFT formats:
- Microsoft At Work(TM), Microsoft's BFT format with advanced
security features for sending key-encrypted and digitally
signed events. The recipient must be running software that
supports Microsoft At Work -- for example, Windows for
Workgroups 3.11 -- with a Class 1 fax/modem.
- Standard CCITT T.434 binary file transfer
The recipient must be using a BFT-capable fax device, such
as a Class 1 fax/modem with the appropriate fax software.
Some fax machines can also receive BFT events.
Compressed BFT
--------------
Compressed BFT provides faster WinFax to WinFax file transfer,
because files are sent compressed. The recipient must be
running WinFax PRO 4.0 or later with a Class 1 fax/modem. When
sending, you can change to this transmission type by selecting
Compressed BFT from the Send By drop-down list in the Schedule/
Modify Events dialog.
* CAS fax/modems support the SatisFAXtion event transmission type
-- an Intel CAS BFT format. Both you and the recipient must be
running CAS software and fax/modems that support Intel
SatisFAXtion file transfer.
* Class 2 fax/modems do not support Fax-a-File transmissions.
With a Class 2 fax/modem, you can send conventional faxes only.
When defining recipients in phonebooks, you have two choices in
the Connections section of the Phonebook Recipient dialog -
either Fax and BFT, or Fax and SatisFAXtion. When sending to a
recipient defined as BFT, WinFax determines what kind of device
it is communicating with, and uses the Microsoft At Work or T.434
protocol, as appropriate.
At the time you are sending an event, you have three options,
available from the Send By drop-down list in the Schedule/Modify
Events dialog: Fax, BFT and Compressed BFT. When you choose
Compressed BFT, WinFax determines whether it is communicating
with another computer that is running WinFax PRO 4.0, and uses
the Compressed BFT protocol, as appropriate. If the recipient is
not WinFax, but is running software that supports Microsoft At
Work, such as Windows for Workgroups 3.11, with a Class 1 fax/
modem, WinFax sends using the Microsoft At Work protocol.
* Microsoft At Work is a trademark of Microsoft Corporation.
Disabling Microsoft PC Fax with Windows for Workgroups 3.11
-----------------------------------------------------------
If you are running Windows for Workgroups 3.11, the WinFax Setup
program will disable Microsoft PC Fax if it detects this fax
utility on your system. The Setup program checks your
MSMAIL.INI file for the following:
[EFAX Transport]
LocalFax=1
If LocalFax=1 is detected, or this section is not present,
the WinFax Setup program adds or modifies the setting
as follows:
[EFAX Transport]
LocalFax=0
You cannot install WinFax while MS PC Fax is running. If the
Setup program detects that the utility is running, you are
prompted to exit the install, close PC Fax and restart the
WinFax Setup program.
The Setup progam will also remove the Fax menu from your
Microsoft Mail client, by removing the following lines from
your MSMAIL.INI file:
[Custom Menus]
Fax=3.0;Fa&x;Window;View or change fax queue, settings, and options.
[Custom Commands]
FaxOpts=3.0;Fax;&Options...;0;faxopt.dll;3;;System Fax Options;msfax.hlp;-1;
FaxMgr=3.0;Fax;&Queue...;1;faxopt.dll;4;;Fax Queue;msfax.hlp;-1;
FaxAnswer2=3.0;Fax;&Mode...;2;faxopt.dll;7;;Change Fax Answer or Online Mode;msfax.hlp;-1;
FaxSecur=3.0;Fax;Advanced &Security...;3;faxopt.dll;5;;Fax Security;msfax.hlp;-1;
FaxSep1=3.0;Fax;;4
FaxCheck=3.0;Fax;&View New Faxes!;5;faxopt.dll;8;;Check for New Fax Messages;msfax.hlp;-1;
FaxAnswer=3.0;Fax;&Answer Now!;6;faxopt.dll;6;;Answer Fax Modem;msfax.hlp;-1;
FaxHelp=3.0;Help;&Fax;1;faxopt.dll;2;;Fax Help;msfax.hlp;-1;
You can easily restore these lines, which resets these options
to the defaults. Go to Control Panel, double click the Fax icon,
then click OK in the Fax Modems dialog.
Tutorial 3 - Viewing and Marking Up a Fax
-----------------------------------------
On page 14-26 of the Delrina WinFax PRO User's Guide, the note
should read: "DRAFT.TIF should be located in your \WINFAX\COVER
subdirectory."
On page 14-32, in the procedure for adding a stamp, you do not
have to select the TIFF graphic file for the stamp you want to
add. When you open the Stamp dialog, the predefined stamps that
come with WinFax, and any other stamps you created, are listed
there. Click the stamp you want to use -- which, in the case of
this tutorial, is DRAFT -- then click OK. The stamp appears on
your page.
CAS restriction on maximum number of log entries
------------------------------------------------
If you use WinFax with a CAS fax/modem, WinFax may experience
problems storing events in your logs after a certain number of
entries are logged. The CAS fax software that comes with your
fax/modem maintains its own log of send and receive events. If
the number of entries in the CAS log exceeds the allowable
maximum, error messages such as "CAS DOS Error: Invalid data"
appear, and events fail.
To handle this problem, run the Setup program for your CAS fax
software and verify or increase (to a maximum of 999) the
allowable number of CAS log entries. To help stay within this
limit, delete all unnecessary log entries from WinFax, which also
removes the duplicate entries from the CAS log. This problem may
occur more frequently if you are running Windows for Workgroups
3.11.
Using WinFax with Intermission and the Opus 'n Bill screen saver
---------------------------------------------------------------
When using WinFax with Intermission and Opus 'n Bill, your screen
may intermittently display a blank screen instead of the selected
screen saver module. Before it activates the screen saver,
Intermission checks to see if the Opus 'n Bill screen saver
module might conflict with WinFax trying to send or receive
faxes. The blank screen display ensures that fax transmissions
are not interrupted.
Maximum ten keywords, billing codes and prefixes
in drop-down lists
------------------------------------------------
The drop-down lists for keywords, billing codes and dial prefixes
can store the ten most recently used entries. If you have ten
entries in one of these lists and add one more, the new entry and
the nine most recently added entries are saved. The oldest entry
in the list is removed. You can specify keywords and billing
codes in the Schedule/Modify Events dialog, and dial prefixes in
the Send Options and User Setup dialogs. The ten-entry limit
applies to what is displayed in the drop-down lists only, and
not the total number of keywords and billing codes you can
specify for your faxes.
Phonebooks maintain duplicate records to avoid data loss
--------------------------------------------------------
If you import an ASCII data record to a WinFax phonebook, and the
phonebook already contains a recipient record with the same name
and company, a duplicate recipient record is created. Similarly,
if you copy multiple recipient records with the same name and
company to another phonebook, WinFax does not merge or overwrite
records.
Using the WinFax OLE Template option with
Microsoft Word for Windows 6.0
-----------------------------------------
If you are creating an OLE cover page in WinFax using Microsoft
Word 6.0, select the Insert option in WinFax (Cover Page/OLE/
Insert). If you select Template instead of Insert, you will not
be able to close Word 6.0 and return to WinFax.
WINFAX.INI Considerations
-------------------------
If you delete your WINFAX.INI file at any time, most of the
WinFax program preference settings in the file are recreated when
you next run the program. However, the settings for graphic
formats that can be loaded into WinFax (chiefly the Cover Page
Designer) must be restored by copying and pasting the following
back into your WINFAX.INI file:
[WinFax Importers]
Windows Bitmap (*.bmp)=BMP,DTIFLBMP.DLL,*.DIB;*.BMP
Windows Metafile (*.wmf)=WMF,DTIFLWMF.DLL,*.WMF
TIFF (*.tif)=TIF,DTIFLTIF.DLL,*.TIF
PC Paintbrush (*.pcx)=PCX,DTIFLPCX.DLL,*.PCX
GEM Image (*.img)=IMG,DTIFLIMG.DLL,*.IMG
GEM Metafile (*.gem)=GEM,DTIFLGEM.DLL,*.GEM
Mac Paint (*.bin)=PNT,DTIFLPNT.DLL,*.BIN
Encap. Postscript (*.eps)=EPS,DTIFLEPS.DLL,*.EPS
Gr. Interchange (*.gif)=GIF,DTIFLGIF.DLL,*.GIF
WinFax (*.fxs)=FXS,DTIFLFXS.DLL,*.FXS
Delrina WinFax PRO Setup Guide
==============================
[WfxPbLinks] and PackRat (page 4-23)
------------------------------------
The examples on this page should read:
* For PackRat versions 3.x or 4.1, change the first parameter to:
PackRat=1,c:\packrat\packrat.exe,PackRat,System,PACK3
* For PackRat version 4.0, change the second parameter to:
PackRat4.0=1,c:\packrat\packrat.exe,PackRat,System,PACK3
* For PackRat version 5.0, add the following line:
PackRat5.0=1,c:\packrat\packrat.exe,PackRat,Phonebook,PackRat
Delrina WinFax PRO User's Guide
===============================
Filling In WinFax Cover Pages (page 3-24)
-------------------------------------------------
The commands for changing text color and justification are not
available on the Text menu in WinFax Cover Page Filler. You can
use these commands -- Black Text, White Text, Left Justify,
Center Justify, Right Justify -- to customize your cover page
text in Cover Page Designer or when previewing and annotating
faxes.
Dialing a Fax Number Manually (page 3-31)
-----------------------------------------
To help ensure a successful fax transmission when dialing
manually, perform step #5 of this procedure as follows.
- Pick up the telephone handset and dial the recipient's fax
number.
- As soon as you finish dialing the number, click Send Now to
release the held fax.
- When the WinFax Status dialog reads "Connecting..." and you
hear your fax/modem pick up the line (go "off hook"), hang up
the telephone handset immediately.
Receiving Faxes Manually (page 4-3)
-----------------------------------
To help ensure a successful fax reception when receiving manually
on a shared voice/fax line, do the following.
- If you pick up the telephone handset and hear an incoming fax
call, select the Manual Receive Now command.
- When the WinFax Status dialog reads "Answering..." and you hear
your fax/modem pick up the line (go "off hook"), hang up the
telephone handset immediately.
Spell Checking Recognized Text (pages 9-12 and 9-13)
----------------------------------------------------
The spell checking options described here are not available.
Using WinFax DDE Macro Commands (page 11-7)
-------------------------------------------
DDEPoke supports one item only, SendFax. The items listed in
table -- recipient, setcoverpage, fillcoverpage, attach,
resolution and showsendscreen -- are actually commands for use
with the SendFax item. See the examples of DDEPoke commands in
the WinFax online help for the correct usage of the SendFax item
in a DDEPoke statement.
IMPORTANT
Late Breaking FAXGrabber Information
The following information is not included in the
FAXGrabber User's Guide. Each separate topic is
separated from others by five asterisks (*****).
*****
FILE COMPRESSION ON DISTRIBUTION DISKS
FAXGrabber is distributed in compressed files on diskettes.
If you need to copy a single file from a diskette onto your
hard disk, you must use the EXPAND.EXE program included on
disk 3 (5.25" media) or disk 4 (3.5" media). Compressed
files can be identified by an underscore in the last
character of the filename. For example, FAXGRAB.EXE when
compressed becomes FAXGRAB.EX_.
To decompress a file, copy the EXPAND.EXE program to your
hard disk, then type:
EXPAND d:filename.ex_
where d: is the letter of the diskette drive, filename is
the name of the file, and ex_ is the filename extension
ending in an underscore.
*****
RE-PROCESSING FAXES
If necessary, you may be able to re-process faxes that
FAXGrabber has already processed. The procedure for
re-processing faxes only works if the CALERA.INI file
specifies DELETE=0. (If DELETE=1, incoming fax images
are deleted as soon as FAXGrabber processes them.)
Refer to the "Configuration File Settings" section
of the FAXGrabber User's Guide for information on
how to change CALERA.INI settings and on the usage
of the DELETE= setting.
To re-process all faxes in the fax software's "received"
log, follow these steps:
1. Using a text editor (or the text editing function of
your word processor), edit the CALERA.INI file.
The CALERA.INI file is located in your Windows
directory.
2. Find the line that begins with:
Time Stamp=
for example,
Time Stamp=3765648915
3. Change the line to:
Time Stamp=0
4. Save the CALERA.INI file.
When you launch FAXGrabber, ALL faxes in the fax board's
received log will be re-processed. When you quit
FAXGrabber, the Time Stamp setting will be returned
to a valid value so that only new faxes will be processed
next time you launch FAXGrabber.
*****
FAXit SUPPORTED VERSIONS
FAXGrabber supports Alien Computing's FAXit for Windows
application, version later than 2.0d. Earlier versions may
not be compatible. Contact Alien Computing for an upgrade,
if necessary:
Alien Computing
337919 50th Street East
Palmdale, CA 93550 U.S.A.
(805) 947-1310
(805) 947-1387 (fax)
*****
FRECOM AND ENHANCED MODE
Frecom fax software for DOS does not work properly in
Windows 386 Enhanced Mode. Frecom recommends running this
application program in Standard Mode, by starting Windows
as follows:
WIN /S
Frecom's Windows software does not have this limitation.
*****
NORTON DESKTOP FOR WINDOWS, VERSION 2.0
When installing FAXGrabber with Norton Desktop for Windows,
Version 2.0, the FAXGrabber icon may appear in black and
white, or may appear as a generic DOS program icon. To correct
this situation, follow these steps:
1. With Norton Desktop for Windows running, select the
FAXGrabber program icon by clicking it once.
2. From the File menu, select Properties.
3. Click the Icon button.
4. Click once on the FAXGrabber icon that appears.
5. Click the OK button.
6. From the Configure menu, choose Save Configuration.
FaxMaster 1.0 Release Notes CAS-Standard Fax/Modems If you use a fax/modem that adheres to the CAS standard, call FaxMaster product support for an update disk. The software in this box does not support CAS. Locating the FaxMaster... Command You must run a special installation macro to set up FaxMaster with the following applications: Word for Windows 2.0 WordPerfect Excel 3.0 Ami Pro 2.0 See Chapter 2, Getting Started, for detailed instructions on installing FaxMaster with these programs. Note: When setting up Excel 3.0, open the file faxlink.xlm in your FaxMaster directory, not the file omniscan.xlm. The FaxMaster... command appears in the Windows Control menu with the following applications: Lotus 123 PFS:WindowWorks Ventura Publisher WingZ Pull down the Control menu by clicking on the small rectangle in the far upper-left corner of your application window. FaxMaster... will not appear as a menu item with some applications. If you have a recently released Windows application, Register the application as described in Chapter 2, Getting Started. If the FaxMaster... command still does not appear in the File or Control menus, press the CTRL-SHIFT-F hot-key combination. Pressing this hot-key combination is the same as selecting FaxMaster... in the File menu. If the hot-key combination conflicts with your application, select a different hot key by selecting System in the FaxMaster Setup menu. If an error message tells you that FaxMaster won't work with the application, view faxes by opening FaxMaster from the Program Manager. Send faxes by using the following method. Sending from an Application Without the FaxMaster... Command FaxMaster uses your fax/modem hardware like a printer: to send a fax, you select the FaxMaster driver in your printer setup. 1. Select Printer Setup in your application's File menu. The Printer Setup dialog box will appear. If you cannot choose a printer driver from the dialog box, select the FaxMaster printer driver via the Windows Control Panel. Open the Control Panel, select Printers, and highlight the FaxMaster driver. 2. Select the FaxMaster printer driver. If necessary, click Connect to set up the FaxMaster driver with the COM port your fax/modem is set to. 3. Click OK. 4. Select Print... in the application's File menu. 5. Click OK. The Dial Fax dialog box will appear. Fax/Modem to Fax/Modem Transmissions Some computer fax/modem hardware will not accurately transmit fax data to another computer fax/modem unit. If you have difficulty sending or receiving faxes between two fax/modems, consult your fax/modem's manufacturer for information about compatibility issues. Viewing Cover Pages in the Transmit Log FaxMaster does not display cover pages of faxes you have sent. To review a cover page, highlight the thumbnail of the fax in the Log view. Select Fax Statistics in the Help menu and click Cover Page. The dialog box will list any text message or bitmap file you sent with the fax's cover page. Editing Recognized Text In Text view, FaxMaster displays recognized text in three colors: Blue indicates a word was spell-checked and replaced; Green indicates a word was not found in the dictionary and is probably incorrect; Red indicates an unrecognizable character. If Exported Text Appears in a Narrow Column When you export text from FaxMaster directly into another application, text may appear in a narrow column on the left side. This is because the margins in your application are larger than the margins in the fax. Make the margins in your application smaller and re- import the text. User Dictionary FaxMaster automatically spell-checks your fax after recognizing text. It checks words against both the main dictionary and the personal, user dictionary. If the word isn't found in either dictionary, FaxMaster may replace it with a word that it considers correct. If your faxes contain many words not found in a standard dictionary, add these words to the user dictionary; you can build a custom word list that includes special words used in your profession. FaxMaster will then recognize them as correctly spelled. Select User Dictionary in the Setup menu to edit entries in the user dictionary. This dialog box lists all the words currently in the user dictionary. The edit box on the right lets you add a word to the list. To display a word in the edit box, you can either type the word or highlight the word in the list box. You will then have the following options: Add Click this to add the word in the edit box to your user dictionary. Delete Click this to delete the word in the edit box or a word highlighted in the list box from your user dictionary. You can add all the words from a particular document to your personal dictionary or save your word list as a text file by using the Import and Export features. Import This lets you add words in a text file to your user dictionary. For example, you may want to add technical terms from a particular document. The Import dialog box prompts you for a file name; enter the file name of the document that contains words you want in your user dictionary. The program will go through the text file, discard words already in the main or user dictionaries, and add the words that are left to your user dictionary. The imported text file can be any document or word list in ASCII format. Most word processors can convert a file into ASCII format; see your program's documentation. Export This lets you save your user dictionary as a text file. When you select Export, a dialog box will prompt you for a file name and destination. You can use the text file in other dictionaries or save it for later use with FaxMaster. OK This saves your edited dictionary and exits the User Dictionary option. Cancel This exits the User Dictionary function without saving any changes. Application Notes Graphics Applications - Exporting Text FaxMaster will not export text directly into some graphics applications. In FaxMaster, copy the text to the Windows clipboard. Then paste it into your work within your graphics application. Ami Pro 2.0 To export text directly from FaxMaster to Ami Pro, you'll need to install the Ami Pro RTF file format converter. See your Ami Pro documentation for instructions. Ami Pro version 1.2 does not work with this release of FaxMaster. Excel 1.0, 2.0 These applications do not work with this release of FaxMaster. Legacy, Lotus 123 You may export only one fax page of text directly into these applications. If you're working with a multiple-page fax, save all the fax text as a file and then import the file. PageMaker Before exporting text to PageMaker, toggle the PageMaker Autoflow option (available in the Options menu) on. Ventura Publisher You may export only one fax page of text directly into Ventura. If you're working with a multiple-page fax, save all the fax text as a file and then import the file. WingZ After you select the FaxMaster... command, the FaxMaster window will move behind WingZ. Press the Alt-Tab key combination to move the FaxMaster window to the front. Word for Windows 1.0 This application does not work with this release of FaxMaster. Scanners Fujitsu scanners are currently incompatible with Windows 3.1 and are not supported in this release of FaxMaster. Sharp scanners are not supported in this release of FaxMaster.
FaxMaster 1.01 Release Notes CAS-Standard Fax/Modems If your fax/modem adheres to the CAS standard: 1. Install your CAS-compatible hardware according to the manufacturer's instructions. 2. Install FaxMaster; when the Transmit Setup dialog box appears, select CAS in the Hardware/Port list box. Intel Fax/Modems If you have a SatisFAXtion Model 400e board, follow the Intel Release Notes carefully to be sure your board is set up to work within Windows 3.1. You must have Intel's FaxAbility and SatisFAXtion software installed on your hard disk. The SatisFAXtion Model 100 may reverse the characters of the receiver ID. The receiver ID appears in Receive Log view below the thumbnail of the received fax. The ID is provided for informational use only and does not affect FaxMaster performance. When Sending to an HP LasetJet Fax: De-select "Send Fax Header" in the Options section of the Dial Fax dialog box. If you send a fax header, the receiver of the fax may get a blank page between each received fax page. Locating the FaxMaster... Command You must run a special installation macro to set up FaxMaster with the following applications: Word for Windows 2.0 WordPerfect Excel 3.0 Ami Pro 2.0 See Chapter 2, Getting Started, for detailed instructions on installing FaxMaster with these programs. Note: When setting up Excel 3.0, open the file faxlink.xlm in your FaxMaster directory, not the file omniscan.xlm. The FaxMaster... command appears in the Windows Control menu with the following applications: Lotus 123 PFS:WindowWorks Ventura Publisher WingZ Pull down the Control menu by clicking on the small rectangle in the far upper-left corner of your application window. FaxMaster... will not appear as a menu item with some applications. If you have a recently released Windows application, Register the application as described in Chapter 2, Getting Started. If the FaxMaster... command still does not appear in the File or Control menus, press the CTRL-SHIFT-F hot-key combination. Pressing this hot-key combination is the same as selecting FaxMaster... in the File menu. If the hot-key combination conflicts with your application, select a different hot key by selecting System in the FaxMaster Setup menu. If an error message tells you that FaxMaster won't work with the application, view faxes by opening FaxMaster from the Program Manager. Send faxes by using the following method. Sending from an Application Without the FaxMaster... Command FaxMaster uses your fax/modem hardware like a printer: to send a fax, you select the FaxMaster driver in your printer setup. 1. Select Printer Setup in your application's File menu. The Printer Setup dialog box will appear. If you cannot choose a printer driver from the dialog box, select the FaxMaster printer driver via the Windows Control Panel. Open the Control Panel, select Printers, and highlight the FaxMaster driver. 2. Select the FaxMaster printer driver. If necessary, click Connect to set up the FaxMaster driver with the COM port your fax/modem is set to. 3. Click OK. 4. Select Print... in the application's File menu. 5. Click OK. The Dial Fax dialog box will appear. Fax/Modem to Fax/Modem Transmissions Some computer fax/modem hardware will not accurately transmit fax data to another computer fax/modem unit. If you have difficulty sending or receiving faxes between two fax/modems, consult your fax/modem's manufacturer for information about compatibility issues. Viewing Cover Pages in the Transmit Log FaxMaster does not display cover pages of faxes you have sent. To review a cover page, highlight the thumbnail of the fax in the Log view. Select Fax Statistics in the Help menu and click Cover Page. The dialog box will list any text message or bitmap file you sent with the fax's cover page. Editing Recognized Text In Text view, FaxMaster displays recognized text in three colors: Blue indicates a word was spell-checked and replaced; Green indicates a word was not found in the dictionary and is probably incorrect; Red indicates an unrecognizable character. If Exported Text Appears in a Narrow Column When you export text from FaxMaster directly into another application, text may appear in a narrow column on the left side. This is because the margins in your application are larger than the margins in the fax. Make the margins in your application smaller and re-import the text. User Dictionary FaxMaster automatically spell-checks your fax after recognizing text. It checks words against both the main dictionary and the personal, user dictionary. If the word isn't found in either dictionary, FaxMaster may replace it with a word that it considers correct. If your faxes contain many words not found in a standard dictionary, add these words to the user dictionary; you can build a custom word list that includes special words used in your profession. FaxMaster will then recognize them as correctly spelled. Select User Dictionary in the Setup menu to edit entries in the user dictionary. This dialog box lists all the words currently in the user dictionary. The edit box on the right lets you add a word to the list. To display a word in the edit box, you can either type the word or highlight the word in the list box. You will then have the following options: Add Click this to add the word in the edit box to your user dictionary. Delete Click this to delete the word in the edit box or a word highlighted in the list box from your user dictionary. You can add all the words from a particular document to your personal dictionary or save your word list as a text file by using the Import and Export features. Import This lets you add words in a text file to your user dictionary. For example, you may want to add technical terms from a particular document. The Import dialog box prompts you for a file name; enter the file name of the document that contains words you want in your user dictionary. The program will go through the text file, discard words already in the main or user dictionaries, and add the words that are left to your user dictionary. The imported text file can be any document or word list in ASCII format. Most word processors can convert a file into ASCII format; see your program's documentation. Export This lets you save your user dictionary as a text file. When you select Export, a dialog box will prompt you for a file name and destination. You can use the text file in other dictionaries or save it for later use with FaxMaster. OK This saves your edited dictionary and exits the User Dictionary option. Cancel This exits the User Dictionary function without saving any changes. Application Notes Graphics Applications - Exporting Text FaxMaster will not export text directly into some graphics applications. In FaxMaster, copy the text to the Windows clipboard. Then paste it into your work within your graphics application. Ami Pro 2.0 To export text directly from FaxMaster to Ami Pro, you'll need to install the Ami Pro RTF file format converter. See your Ami Pro documentation for instructions. Ami Pro version 1.2 does not work with this release of FaxMaster. Excel 1.0, 2.0 These applications do not work with this release of FaxMaster. Legacy, Lotus 123 You may export only one fax page of text directly into these applications. If you're working with a multiple- page fax, save all the fax text as a file and then import the file. PageMaker Before exporting text to PageMaker, toggle the PageMaker Autoflow option (available in the Options menu) on. Ventura Publisher You may export only one fax page of text directly into Ventura. If you're working with a multiple-page fax, save all the fax text as a file and then import the file. WingZ After you select the FaxMaster... command, the FaxMaster window will move behind WingZ. Press the Alt-Tab key combination to move the FaxMaster window to the front. Word for Windows 1.0 This application does not work with this release of FaxMaster. Scanners Fujitsu scanners are currently incompatible with Windows 3.1 and are not supported in this release of FaxMaster. Sharp scanners are not supported in this release of FaxMaster.
FaxWorks Windows, Release 2.50
==============================
Contents
========
* Changes and new features in this version
* Upgrading from previous versions of FaxWorks
* Quick-start installation (for those who don't want to read the manual!)
* Font compatibility and installation information
* Special notes - check this section to see if your fax hardware is special
Changes for release 2.5 (NOT IN THE MANUAL)
===========================================
1) The new Dial Options command in the Phonebook Options menu
allows you to specify a dialing prefix (e.g. 9 plus a comma to
get an outside line on your phone system), AND a dialing suffix
(e.g. a calling card number or long distance account access
code). For numbers dialed FROM the US (both internal and
international), the calling-card support automatically replaces
the leading 1 (or 011 for international) with a 0 (or 001).
2) The User Details dialog (accessed from the User... button in the
FaxWorks Driver Setup dialog) allows you to change the cover sheet
title (the default is "FaxWorks Cover Sheet"), and the cover sheet
subtitle (the default is "Sent by <your fax board name>".
3) Full support for Rockwell 224ATF Class 1 devices has been added.
4) The new Class 1 driver supports the new DellFax firmware.
5) Many new drivers have been added (the install program now lists
over 80 fax boards, modems, machines and PCs!).
6) FaxWorks now provides a DDE interface which allows DDE-capable
applications to specify fax destinations via DDE commands. See
the READDDE.TXT file for further information.
7) Uninstall is provided for those users wishing to remove FaxWorks
from one system in order to re-install it on another. Uninstall
removes all traces of FaxWorks from a system, including: WIN.INI
settings, SYSTEM.INI settings, files in the Windows directory,
files in the FaxWorks directory, transmitted and received fax
files, phonebook files and logs. Uninstall sometimes does not
complete if SHARE is loaded. If Uninstall causes messages about
"SHARE Violations", unload Windows and then modify the AUTOEXEC.BAT
file to comment out the line that starts SHARE. Then you may
restart Windows and run Uninstall. Remember to restore AUTOEXEC.BAT
once you have completed Uninstall.
To Uninstall - run A:UNINSTALL /U where A: is the drive where the
installation disk is located.
8) FaxWorks is now fully compatible with both Windows- and DOS-based data
communications applications. When running a data communications
application (such as Terminal, Crosstalk, Procomm, Compuserve,
Prodigy, etc.), FaxWorks AUTOMATICALLY switches the modem into
"Data" mode, waits for the data communications application to
terminate (queueing any faxes to be transmitted), then resets
the modem to "Fax" mode and carries on faxing. You don't have to
"switch off" FaxWorks in order to run a data communications
program, OR remember to "switch on" FaxWorks again afterwords.
9) FaxWorks now supports drag-and-drop. When the FaxWorks icon is at the
bottom of the screen you can fax documents without opening the
application that owns them by dragging the document files from
the File Manager and dropping them onto the FaxWorks icon. FaxWorks
then automatically opens the application owning the document, asks
it to print it to the FaxWorks driver, and closes it after printing.
Upgrading from previous versions of FaxWorks
============================================
If upgrading from an older version of FaxWorks, first delete Fax*.*
files in the FaxWorks programs directory (normally C:\FaxWorks), AND
in the main Windows directory (normally C:\WINDOWS), for example:
C:\> del c:\FaxWorks\fax*.*
C:\> del c:\windows\fax*.*
C:\> del c:\windows\system\fax*.*
It is recommended that you delete these files from OUTSIDE
Windows (as shown above, from the DOS prompt).
Removing this version of FaxWorks
=================================
If you wish to remove this version of FaxWorks, just install the
installation diskette and run "A:UNINSTALL /U" from the File/Run
menu of the Program Manager. This operation will sometimes conflict
with DOS "SHARE" and so you should boot your system with SHARE
disabled to uninstall FaxWorks.
Quick-start Installation
========================
****** Do not attempt to run the FaxWorks install program if you have
*NOTE* DOS FASTOPEN utility installed in your system.
******
1) Load Windows, then depending on which menu/shell you're using:
2) Program Manager: Choose File/Run and type A:INSTALL
File Manager: Click on the -A- drive or press Ctrl+A,
then open A:\ and run INSTALL.EXE
MS-DOS Executive: Click on the -A- drive or press Ctrl+A,
then run INSTALL.EXE
All others: Select the A: drive as the CURRENT DRIVE, and
run INSTALL.EXE
(Substitute the drive containing the FaxWorks release disk, if not A:)
3) Enter the directory to install FaxWorks in, and your Windows directory
4) Select your FAX board from the list
5) Press OK and files will be copied; change disks if prompted
6) Set FaxWorks options; User Details and Directories are most important
7) To send a FAX, issue File/Print from any Windows application
Font Installation
=================
Adobe Type Manger:
------------------
FaxWorks is fully compatible with Type Manager. If you have Postscript soft
fonts (Type 1 or Type 3) you must have Adobe Type Manager in order to
use them with FaxWorks.
Bitstream FaceLift:
-------------------
FaxWorks is fully compatible with FaceLift. However, if you install
FaxWorks AFTER FaceLift, you must run the FaceLift Control Panel, open
the Printers icon, select FaxWorks and check the "Assign SHELL-Driver"
check box. Finally, make sure you use the Bitstream font names (such
as Dutch and Swiss) rather than the Windows font names (e.g. Helv and
Times) when using FaceLift with FaxWorks.
Windows fonts:
--------------
For best results, use the Windows Control Panel to install from the
Microsoft Windows release disk(s) provided with the Windows retail package
the CGA RES and VGA RES fonts.
See your Windows user guide for details on installing fonts using the
Control Panel.
FontWare Drivers:
-----------------
This release comes with drivers for BitStream's FontWare, versions 2.0
and 3.0. To install the FontWare drivers, you must first have
FontWare installed on a hard drive, then:
1) Select the A: drive and run FWINSTAL from the DOS prompt
(Substitute the drive containing the FaxWorks release disk, if not A:)
2) Provide FWINSTAL with the drive & directory where FontWare is installed
3) FWINSTAL automatically installs the FontWare 2 or FontWare 3 drivers
4) Run FontWare and select FaxWorks as the current printer (with the desired
orientation and resolution) from the FontWare control panel, then re-
generate any fonts you have previously built for your screen or printer.
This assures 3-way WYSIWYG among screen, printer and FaxWorks.
Z-Soft's SoftType, & Other Font Managers:
-----------------------------------------
SoftType, and any other font manager that generates Windows GDI
fonts, can be used to generate fonts for FaxWorks using the following
resolution information.
Standard Resolution, Portrait: Horizontal 204dpi; Vertical 98dpi
Standard Resolution, Landscape: Horizontal 98dpi ; Vertical 204dpi
Fine Resolution, Portrait: Horizontal 204dpi; Vertical 196dpi
Fine Resolution, Landscape: Horizontal 196dpi; Vertical 204dpi
Incompatible Font Managers:
---------------------------
A number of font managers available for Windows operate by providing
enhanced printer drivers for a certain number of common printers,
such as the Hewlett Packard LaserJet series. Since this type of font
manager replaces the existing printer driver it will not provide font
support for FaxWorks. Examples of this type of product are Publishers
Powerpack from Atech and SuperPrint from Zenographics.
-------------------------------------------------------------------
See the FaxWorks User's Guide for more information on the installation
and use of FaxWorks Windows, and Windows and FontWare fonts.
--------------------------------------------------------------------
Special Notes
=============
* The install program makes a backup copy of your WIN.INI
file, named WININI.OLD.
Intel Fax Boards
----------------
If using an Intel fax board (SatisFAXtion or Connection CoProcessor),
you will occasionally get a CAS error message from FaxWorks while in
Windows. A Connection CoProcessor will indicate "CAS
FindFirst/FindNext failed" and a SatisFAXtion will indicate "CAS
GetDate or GetTime failed".
These messages are the result of a queue file bug in the Intel
software. The problem can be solved by deleting the ENTIRE queue
subdirectory within the Intel software directory. The default
directory name for the Connection CoProcessor is C:\CONNECT\QUEUE and
for SatisFAXtion is C:\FAX\QUEUE. Once all files (*.*) have been
deleted from this directory, you MUST reboot your computer so that
the Intel software can create new, empty queues. The above message
will then not be displayed any longer by FaxWorks.
IMPORTANT: Before deleting all files in the queue directory, make
sure that you have no pending fax transmissions (unsent documents)
and that all received documents and files have been viewed, printed
or saved. Deleting the queue directory files will result in loss of
any unsent transmissions or unread receives.
Intel SatisFAXtion
------------------
There are no other special requirements for the Intel SatisFAXtion
board except that the Communicating Application Specification Manager
(CASMGR.EXE - see Intel documentation for details) must be loaded and
running BEFORE you enter Windows and generate faxes with FaxWorks.
Since the Intel install program sets up your system so that CASMGR is
always loaded and running, you shouldn't have to change anything. If,
however, you get a message from FaxWorks complaining that the CAS
Manager is not loaded, you might have to adjust your AUTOEXEC.BAT
file so that it loads the CASMGR before running Windows.
Intel Connection CoProcessor
----------------------------
The Intel Connection CoProcessor Application Manager version 1.12 or
newer (CCAM.EXE - see Intel documentation for details) must be loaded
and running BEFORE you enter Windows and generate faxes with FaxWorks.
Since the Intel install program sets up your system so that CCAM is
always loaded and running, you shouldn't have to change anything. If,
however, you get a message from FaxWorks complaining that CCAM is not
loaded, you might have to adjust your AUTOEXEC.BAT file so that it
loads CCAM before running Windows.
In addition to the above,
1) If you are using a 386-based PS/2 (MCA) machine, you need to get
an update to the CONNECT.SYS driver from Intel.
2) If you are using CCAM version 1.11 or previous, you need to get an
update to a newer version from Intel. While waiting for the upgrade,
copy the CCAMMLTI.COM program from this disk into your CONNECT
directory and add it to your AUTOEXEC.BAT file.
To do this, first check CCAM's version number. Make sure you are
at a DOS prompt, and then change to the directory where you
installed the Intel software (normally C:\CONNECT) and run CCAM.
A message similar to the following will be displayed:
Connection CoProcessor Applications Manager (CCAM)
Version x.xx
If the version number displayed is 1.11 or LESS, do the following
when you are at a DOS prompt (assuming the FaxWorks program disk is
in A: and the Intel software is installed in C:\CONNECT;
substitute your drive/directories if different):
COPY A:CCAMMLTI.COM C:\CONNECT
Once CCAMMLTI.COM is copied, you need to add it to your AUTOEXEC.BAT
file. To do this, you must first load AUTOEXEC.BAT into an
editor (EDLIN or some other DOS editor will do, so will NOTEPAD
in Windows) and find the line which says:
C:\CONNECT\CCAM C:\CONNECT\CCAM.CFG
and add IMMEDIATELY FOLLOWING that line, the line:
C:\CONNECT\CCAMMLTI
Save the modified AUTOEXEC.BAT and reboot your computer. Make
sure that following the CCAM signon you see a message similar to:
CCAM-MULTI: Enable CCAM Multitasking
...
CCAM is running multitasking
xxx bytes used
Brooktrout Fax-Mail
-------------------
1) Do not load the background program (RESXMIT) in high memory.
FaxWorks requires RESXMIT to be loaded low.
JT-FAX 9600 (Hayes, Quadram or Asher)
-------------------------------------
1) FaxWorks does NOT support the JT-FAX 4800 products.
2) Do not run the JT-FAX FAX program when the background
program (SCH) is installed. Both of these programs communicate
with the JT-FAX board. If both programs are resident conflicts
will arise.
3) Conflicts with expanded memory managers (QEMM, 386Max etc): If
you are using an expanded memory manager be sure to exclude the area
of memory used by the JTFAX board from use by the memory manager.
The PC communicates with the JTFAX board thru the use of a shared
memory buffer. This buffer is 2048 bytes in length and has a default
base address of CC00:0. The actual base address may be different, check
the switch settings on the JTFAX board.
Failure to exclude the JTFAX memory buffer from the memory manager
will allow the memory manager to use the JTFAX buffer for various
memory management functions. If this situation arises, FaxWorks will
not be able to send or receive fax messages.
Hewlett Packard Laser Jet Fax
-----------------------------
1) Install the software provided by Hewlett Packard before
attempting to install or use FaxWorks.
2) Avoid attempting to send a FAX and print a document at the same
time. Currently there is no mechanism to avoid this problem,
exercise caution.
3) When sending particularly dense or complex FAX pages, the
system may appear to 'freeze' or become very slow. This is a
temporary situation, the system will recover when the offending page
has been transferred to the Laser Jet Fax.
General notes for fax devices that use the Background Scheduler
---------------------------------------------------------------
The background scheduler is used by the following fax
products: JTFAX 9600, Sierra SendFax based devices, HP Laser Jet Fax,
Class 1, and Class 2 fax devices.
The background scheduler is responsible for sending and receiving (if
your hardware is capable of receiving) faxes in the 'background'.
The scheduler is implemented as a DOS Terminate but Stay Resident (TSR)
program. As a TSR you must load or unload the scheduler while at the DOS
prompt and not while in Windows.
To remove the scheduler from memory (unload) type the following
command from the DOS prompt (without the quotes): "SCH /S".
General notes for serial FAX devices
------------------------------------
If your FAX device is an external device that connects to the computer
via a serial port, or it is an internal board that can be configured
to use COM1 thru COM4, it is a serial device. It is important to
note that both COM1 and COM3 share interrupt channel 4 and that COM2
and COM4 share interrupt channel 3. This means that you should not
configure you FAX device to use the same interrupt channel as an
other active serial device. For example, if you have a serial mouse
on COM1, do not configure your FAX device to use COM3.
US Robotics/Touchbase WorldPort 24/96
-------------------------------------
1) FaxWorks requires WorldPort firmware version 2.7 or greater. To
determine the version of firmware in your modem run the Windows
Terminal program, or some other communications software, and type the
command "ATI3" and press the Enter key. The modem will respond with
an identification string, eg.
WORLDPORT2496USa2.6
The end of the string contains the version number. If you have
version 2.6 or earlier, please contact TouchBase and obtain an
upgrade. As of June '91, the current firmware version is 3.2.
Pacific Image Communications, Inc.
README.TXT: ReadMe for PIC SuperFax Version 5.00.05 for Windows
October 15, 1992
*******************************************************************************
* *
* Please not the following address, phone number, and fax number *
* changes. These changes have taken effect as of October 1, 1992. *
* *
* Pacific Image Communications, Inc. *
* 919 South Fremont Avenue, Suite 238 *
* Alhambra, CA 91803 *
* Tel: 818-457-8880 *
* Fax: 818-457-8881 *
* *
*******************************************************************************
Welcome to SuperFax for Windows!
--------------------------------
Please read this document carefully; it contains important information
not included in the SuperFax User's Guide. You may also want to print
this file for future reference.
Topics covered in this document include:
* Installing SuperFax
* New Features
- Automatic Fax Board Detection
- Background Operation
- Support of 14,400 bps Fax Modems
* Common SuperFax Problems
* Bug Fixes from 5.00.4 to 5.00.5
You will also find it helpful to view the diagnostics and troubleshooting
section in Appendix A of SuperFax User's Guide. If you still have questions
after reviewing Appendix A and this Readme file, call our Technical
Support line for assistance. In the United States and Canada, call
(818) 457-8880.
INSTALLING SUPERFAX
===================
Please ensure that there is at least 1.5 MB of free hard disk space
before installing the Superfax software. After installation, please
ensure that there is adequate free disk space (at least 1.0 MB) for the
communication software to store incomming faxes.
The SuperFax installation program is a WINDOWS based program. That is,
the INSTALL program can only be run within the WINDOWS environment. DO NOT
select the "DOS" icon in Windows and try to run the SuperFax Install program
in the DOS shell.
To INSTALL SuperFax:
1. Insert the SuperFax Install diskette into drive A.
2. If WINDOWS is already started, select the RUN option from the
PROGRAM Manager menu and type: A:\INSTALL.
Otherwise,
Type A: to switch to the A drive.
Assuming the search path contains the WINDOWS programs directory,
Type WIN INSTALL and press ENTER to start Windows and Superfax
Installation routine.
For additional installation procedures, please refer to the
SuperFax User's Guide.
NEW FEATURES
============
AUTOMATIC FAX BOARD DETECTION
The SuperFax Installation program has been improved with a new feature --
the Automatic Fax Board Detection. This feature enables you to automatically
configure your fax modem among all the various typs of modems so that it could
operate flawlessly under its manufacturer's specifications. The Auto
Fax Board Detection should correctly detect all the Class 1 and Class 2
modems existed today. If you have any problems with sending or receiving
a fax, please contact your local dealer or Pacific Image Communications, Inc.
BACKGROUND OPERATION
We have just added the background fax operation starting with the
software version 5.00.03. This feature enables you to continue using
any Windows applications while the fax is being sent or received.
With this feature, the SuperFax program would no longer freezes the
entire Windows operations during fax operations.
Please keep in mind that you should only perform normal Windows operations
during background fax transmissions. Certain Windows operations, such as
sizing an application window, may interfere with the performance of the
fax program running in the background mode, thus resulting in fax
communication errors.
14.4 Kbps FAX MODEM SUPPORT
SuperFax is staying ahead of the communications game by supporting the
newest advances in today's technology. Now you can utilize the 14.4
Kbps transmission capabilities that your fax board has incorporated
(check your fax board manual to see if supports 14.4 Kbps). As with
any leading edge technology, there will most likely be some unresolved
problems, please set the communications rate to 9600 bps or lower.
To set the communications rate to 9600 (or lower), select the Set FAX
Parameters option from the Fax menu. Now, select 9600 (or lower) from
the RATE field. Highlighting HIGHEST will result in setting the fax
board to it's highest possible transmission rate. The SuperFax instal-
lation will determine and set itself to the highest transmission rate
available from your fax board.
however enter FOOTER.LGO as the file name for the footer section.
COMMON SUPERFAX PROBLEMS
========================
I) Group or item-icons for the SuperFax application are not created.
This usually happens when the Program Manager Window does not appear.
(For instance, the Program Manager Window will disappear when
the NORTON Desktop For Windows is running).
To fix the problem:
1. Run Program Manager (choose Run... from the File menu, then
type PROGMAN).
2. Minimize it (not necessary, but convenient).
3. Re-Run the SuperFax's install program.
Bug Fixes
=========
The problems listed below were some problems that were found in SuperFax
5.00.04. They have been corrected and the fixes are reflected in the
latest version - SuperFax 5.00.05. If you have a previous version,
you may or may not have been effected by these problems.
1. Too long of a delay in executing a Batch Fax.
2. Sending a fax from Notepad resulted in a fax with very small fonts.
3. When rotating an image, a line towards the center of the image
remained unaltered (portion of image not rotated).
4. Sharing Violations were found on some files.
5. Memory depleted after sending 300 faxes.
6. Operations that require considerable CPU time would not release
control to other programs in the Windows multitasking environment.
7. Cannot print to HP DeskJet 500C
Pacific Image Communications Inc.
README.TXT: 請參閱SuperFax5.00.08中文版讀我檔案(README.TXT)
May.18,1993
請注意下面兩項台灣分公司設立及美國總公司遷移特別通知:
* 台灣分公司設立(Oct. 10 , 1992)
地址: 台北市新生南路一段50號402室
電話: 02-3935941
傳真: 02-3929244
* 美國總公司遷移(Oct. 1 , 1992)
地址: 919 South Fremont Avenue,Suite 238
Alhambra, CA 91803
電話: (818)457-8880
傳真: (818)457-8881
歡迎您選用SuperFax5.00.08中文版,它是目前台灣唯一全部中文化視窗通信軟體,該
軟體國際版本已在全世界一百三十七個國家中銷售數百萬套,被認為是EIA Class
I/II傳真數據機中功能最多且相當穩定及好用的視窗通信軟體.同時它首先採用影像
傳真最新設計運用工作檔案夾方式來傳真,讓使用者操作時倍感方便.
當您剛使用SuperFax5.00.08中文版視窗通信軟體時,請先仔細的閱讀該檔案,因它提
供許多最新資料尚未放入操作手冊中,如您希望用來參考時,可利用列表機直接印出.
README.TXT內容包括:
* 在安裝SuperFax5.00.08時,應注意事項.
* SuperFax5.00.08新增功能
- 自動偵測傳真卡及設定.
- 背景操作.
- 支援FaxV.17 - 14.4BPS.
* 指導客戶如何自行設計傳真封面.
* SuperFax5.00.08故障排除.
當您使用SuperFax5.00.08遇到問題時,請依照下面方式處理:
* 直接參閱線上輔助檔案,自動診斷及故障排除方法.
* 參閱操作手冊中附錄A.
* 或撥電話請求技術支援.
- 東南亞: (886-2)3935941
- 美加歐: (818)4578880
安裝SuperFax5.00.08時,應注意事項:
- 安裝前硬碟至少有1.5 MB 空間容量.
- 安裝後硬碟至少有1.0 MB 以上空間容量來儲存傳真資料.
- 安裝SuperFax5.00.08中文版時,一定要在Microsoft C-Windows下執行.
- 安裝SuperFax5.00.08中文版時,磁片要放入磁碟機A或B中.
- 如C-Windows已執行時,請鍵入 A:\INSTALL.
- 否則請鍵入 A:\WIN INSTALL 再按ENTER,同時啟動C-Windows及SuperFax.
- 詳細情行請參閱SuperFax操作手冊.
- 安裝SuperFax5.00.08後,請重新再啟動電腦系統一次.否則會出現"錯誤13791".
新增功能
* 自動偵測傳真卡及設定: SuperFax軟體將自動判別傳真卡為ClassI或ClassII
及各種Chip-Set Firmware,然後協助使用者自動設定.
* 背景操作: SuperFax同時支援幕前及背景操作,使用者可任意選擇.
* 支援FaxV.17 - 14.4BPS: SuperFax一直是通信界的領導者,目前第一位發表支援
最高速傳真CCITT V.17也就是一般所謂的14.4BPS,但一定要傳真卡的Firmware有
支援CCITT V.17.
SuperFax5.00.08故障排除:
* 問題: 無法起動SuperFax圖示時,(當Program Manger Window 不出現時這個問題
經常發生)
例: 當NORTON Desktop For Window應用程式在執行時,
則Program Manger Window 將消失掉.
故障排除: 1.) 執行Program Manger(在檔案明細中選擇"執行"選項 )
2.) 縮小到最小尺寸(不是一定必需,但比較方便)
3.) 重新再裝置SuperFax5.00.08一次.
DosFax PRO 2.0 Readme Notes May 25, 1992 =============================================================================== Loading DosFax PRO TSR's in High Memory ======================================= Do not use DOS 5.0 or any other memory management utilities (e.g. QEMM, 386 Max) to load FAXCOM.EXE into high memory. The size and architecture of the TSR does not permit high memory loading.
PROCOMM PLUS for Windows - README.WRI
Script Files Supplied with PROCOMM PLUS for Windows
If you choose to install the Windows ASPECT sample scripts, a number of sample scripts included on your distribution disks will be copied to your ASPECT directory. To run a script, click on the Action Bar Script File drop-down list box, select the desired name and click on the Run Script icon.
Note: README.WAX, HOST.WAX and its accompanying files HOST.WAS, SUBS.WAS and HOSTUTIL.WAS are copied to your ASPECT directory automatically during installation - these files should not be deleted.
The following scripts may be of special interest to you:
MCI.WAX:
This script acts as a MCI Mail message "manager", allowing you to create mail messages offline and upload them automatically. The script can call MCI and download any mail you have waiting with the click of a single button - once you've read the messages, you can print, save or delete them.
The first time you run the script it will prompt you for your MCI Mail username and password, which it stores in the file MCI.PRM. Although the password will be encrypted, please note that you should not rely on this as the only method of security for your password.
You can create "INSTANT" MCI Mail (which is sent to another MCI user), "FAX" mail (which is sent as a fax to the location you specify) and "PAPER" mail (which is sent as a letter via the U.S. Mail). You can also log on interactively for a normal MCI Mail session.
LOGIN.WAX
This script creates log-in scripts and Dialing Directory entries for several popular on-line services and bulletin board systems, including CompuServe, GEnie, BIX and Dow Jones, as well as the DATASTORM BBS. LOGIN.WAX also includes a list of CompuServe access numbers, so you can specify a convenient local number during installation.
DEMO.WAX:
This script will familiarize you with the many features of PROCOMM PLUS for Windows by leading you through a "guided tour" of the program! The demo includes a tutorial on the Action Bar, examples of custom applications, simulations of on-line communications sessions and examples of several terminal emulations.
Note: Some of the color GIF pictures and graphics in the DEMO script will lose contrast and resolution when displayed on a monochrome system.
ROADTRIP.WAX
This script performs "intelligent" management of your Dialing Directory when you're travelling. It prompts for your "home" area code - the code assumed when the directory was created - and for the current area code, allowing you to adjust the Dialing Directory for numbers within your home area code and the current area code.
Sample log-on scripts for TBBS, WildCat, RemoteAccess and PCBoard bulletin board systems are also included. You can edit these scripts and customize them with the correct values for your User ID, password and phone number.
General Information
Windows 3.1 "Drag and Drop" Support:
PROCOMM PLUS for Windows supports the Windows 3.1 implementation of "drag and drop" for several file types. Capture files (.CAP), source and compiled Windows ASPECT scripts (.WAS/.WAX) and Dialing Directory (.DIR) files operate as drag and drop files within the Terminal window. To use this feature, open an application that supports drag and drop - for instance, the Windows 3.1 File Manager - select the filename, drag it anywhere within the PROCOMM PLUS for Windows application window and release the mouse button. You can also drag and drop a file onto the PROCOMM PLUS for Windows icon when the program is running in a minimized state.
Capture files are replayed just as if you had used the Playback menu item.
Script files are compiled, if necessary, before execution. Your script can resize the PROCOMM PLUS for Windows main application window (if necessary).
A Dialing Directory file is immediately loaded as the current directory, and its entries replace those in the Rapid Dial menu.
You can also drag one or more picture files (.GIF) to the GIF Viewer window when it's running as a stand-alone application. The viewer window must be already open.
Finally, both the Dialog Editor and User Window Builder allow you to drag and drop an appropriate source file within their application windows for automatic loading.
The On-line Help Facility:
Although your PROCOMM PLUS for Windows manual set and the On-line Help facility contain substantially the same information, the Help facility contains script examples, descriptions and some text that couldn't be included in the manuals - and, of course, it also allows you to quickly browse related information or search for a specific topic. Therefore, if you need additional information on a program or Windows ASPECT command, make sure to refer to the Help facility!
132 Column Emulation Support:
The following terminal emulations now support 132 columns:
ADM 31
ATT 605 and 4410
TTY
TVI 922 and 955
All DEC terminals except VT-52
WYSE 50, 75 and 100
Upgrading your Display Driver:
If you're running PROCOMM PLUS for Windows under Windows 3.1 and you're using a display driver provided by the manufacturer of your graphics adapter, be sure the driver supports operation under Windows 3.1. Earlier drivers written for Windows 3.0 operation may cause unpredictable results within PROCOMM PLUS for Windows, the GIF Viewer and the User Window Builder under Windows 3.1.
For example, if you're using a Diamond SpeedStar graphics adapter and you attempt to view GIF pictures with a higher resolution than that supported by your current Windows 3.0 display driver, PROCOMM PLUS for Windows may not set the color palette correctly. This problem occurs whenever the viewer displays such a GIF picture (including during the download process). An updated Windows 3.1 Diamond driver will fix this problem - PROCOMM PLUS for Windows requires version 1.08 or later of the Diamond display driver for correct operation.
For more information about upgrading a custom display driver, please contact the manufacturer of your graphics adapter.
Setting the Modem DTE Rate:
PROCOMM PLUS for Windows sets the DTE baud rate between the modem and the computer to the highest speed supported by the modem. "Slower" PCs - or PCs not equipped with a 16550 UART chip - may drop characters at very high speeds (for example, a 286 machine running at 38400 bps or greater). If this occurs, open the Connections dialog from the Setup window, select Modem Setup and choose a lower baud rate. Click on OK, then click on OK again to exit the Connection dialog - finally, select Save from the Setup window File menu to save your changes to disk.
Using PROCOMM PLUS for Windows with COM3/COM4 or IRQ3/IRQ4:
If you are using Windows 3.0 or 3.0a AND your modem does not use IRQ3 or IRQ4:
Windows 3.0/3.0a will not recognize "non-standard" IRQ lines (IRQ's other than IRQ3 and IRQ4). Since this is a limitation with versions 3.0 and 3.0a (and not PROCOMM PLUS for Windows), we recommend that you upgrade to Windows 3.1 if your modem operates on IRQ2, IRQ5, or IRQ7. You may also be able to change the modem's IRQ setting to IRQ3 or IRQ4, but you should ensure that the new configuration doesn't cause the modem to share an interrupt with another installed device (such as a mouse).
If you are using Windows 3.0, 3.0a, or 3.1 AND your modem uses COM3 or COM4:
Depending on your PC, Windows may not recognize a modem using COM3 or COM4 if the COM port's interrupt is shared by another device. COM1 and COM3 share the same default IRQ4 - therefore, you couldn't use a modem on COM3 while COM1 is installed, nor could you use a modem on COM4 while COM2 is installed. We recommend that you move modems currently on COM3 or COM4 that share IRQ lines to a standard, non-shared IRQ. Windows 3.0/3.0a do not support the use of non-standard IRQ lines.
Note: This limitation does not apply to Micro-Channel IBM PS/2's or EISA-bus computers with an EISA serial card; these architectures support shared IRQs.
If you are using Windows 3.1 AND your modem uses a non-standard COM port or IRQ line:
1] Open the Windows Control Panel and run the Ports utility.
2] Select a COM port number and click on Settings.
3] Click on Advanced.
4] Enter the base port address and IRQ of the modem.
Please refer to your Microsoft Windows 3.1 User Guide for additional information.
User Window Builder Objects:
Objects placed within the User Window Builder workspace need no longer remain within the left and top borders.
Hiding Meta Keys:
To hide the Meta keys for a Dialing Directory entry, select the [None] item from the Meta File drop-down list box for that entry.
Mouse Double Click Settings:
The User Manual omits the discussion of the Mouse Double Click options found in the Setup System Settings dialog; these options determine the action PROCOMM PLUS for Windows will take if you double-click on the first character of a word in the Terminal window or the Scrollback buffer.
If Send character is selected, the character under the mouse cursor will be sent to the remote system. If Send word is selected, PROCOMM PLUS for Windows sends the entire string under the mouse cursor (up to the next space character).
You can also specify whether a carriage return should be sent after the character or word - this makes the mouse double-click feature convenient for sending single-character commands or filenames.
Using PROCOMM PLUS for Windows with CompuServe:
For best performance when calling CompuServe, select 8 data bits, no parity and 1 stop bit in the Port Settings dialog, and enable the "Strip bit 8" option in the Setup Terminal Settings dialog.
Note: If you're using VIDTEX emulation, Strip bit 8 is enabled by default. However, if you're using another emulation, remember to turn this setting OFF (or save your terminal settings under a new name) to prevent problems with other connections.
Cache Software Conflicts:
If PROCOMM PLUS for Windows reports unexplained CRC errors as you download at higher baud rates, we recommend that you disable the "write cache" option offered by most cache software - for example, the Windows program SMARTDRV.EXE.
Using ZMODEM with WildCat Bulletin Boards:
The ZMODEM protocol "Skip GIF" feature will not work correctly with the internal ZMODEM protocol offered by some versions of Mustang Software's WildCat BBS software - if you're calling a WildCat bulletin board that does not use DSZ.COM as an "external" protocol, do not use the Skip GIF option while downloading.
Windows ASPECT Information
New Runtime Error Messages:
These error messages were added to assist in debugging scripts that use the SET commands dealing with paths and filenames, which cannot set SUCCESS or FAILURE. The messages can be suppressed with the statement SET ASPECT RANGECHK OFF.
Error 7: Invalid or unexpected path
Error 8: Invalid extension
Error 9: Item not found
Error 10: File creation error
SUCCESS, FAILURE and FOUND System Variables:
For clarity and convenience, two new conventions have been added to Chapter 2 of the Windows ASPECT Script Language Reference Manual: the label "S/F" next to a command name title indicates the command sets the SUCCESS and FAILURE system variables, while the label "FOUND" indicates the command sets the FOUND system variable. For further information on these variables, please refer to the section entitled "System Variables" at the end of Chapter 2 of the Windows ASPECT Script Language Reference Manual.
Any Windows ASPECT command that sets the SUCCESS and FAILURE system variables can be used directly in a conditional expression - however, with the exception of the NOT command, no other commands, operands or operators may occur within the same conditional expression. For example:
if chdir "c:\backup" ; valid
if not chdir "c:\backup" ; valid, NOT precedes command
if !chdir "c:\backup" ; NOT valid, no operators allowed
Sending Alt, Shift and Ctrl Keys:
To send a lone Alt, Ctrl or Shift key to an application - without another key in combination - encode the key value using both the shift state and the virtual key code; for example, to send an Alt key, you could use the statements SENDKEY ALT VK_MENU or SENDVKEY 0x0412.
Note: An application should never attempt to send key combinations listed as "not mapped" in the Keyboard Mapper facility.
Range Checking and Debug Mode:
When a Windows ASPECT script is compiled for debug, range checking is now forced ON (even if the script has issued the SET ASPECT RANGECHK OFF statement). This forces examination of all possible errors within the script (which might have been overlooked if range checking was suppressed).
When a script compiled for debug uses the EXECUTE or CHAIN commands, debug mode will be disabled (except when the script executed next has also been compiled for debug).
When a value is out-of-range, Windows ASPECT will prompt the user for permission to exit the script; if the user answers no, execution will continue wit the a value within the acceptable range (typically, this value is the lowest valid value). When an out-of-range error occurs within a SET command, the current value of the item being set is retained and the action associated with that SET command is performed with the current value.
If range checking is set OFF, the prompt is not displayed and script execution continues as described above, just as if the user had replied no to the prompt.
New Windows ASPECT System Variables:
$DIALCOUNT
This integer variable contains the number of entries within the current Dialing Directory.
$DDIRFNAME
This string variable contains the fully-qualified path of the current Dialing Directory file.
Changes to Windows ASPECT System Variables:
$D_LASTDATE
This variable now contains a long value representing both the last call date and time for the currently-accessed Dialing Directory entry. Note that $D_LASTDATE now returns a value in timeval format - for more information on the timeval format, please refer to the "Conventions" section at the beginning of Chapter 2 in your Windows ASPECT Script Language Reference Manual.
$KEYHIT
This variable is incorrectly labelled as a string value in the Windows ASPECT Script Language Reference Manual; it should be designated as an integer value. Additionally, $KEYHIT now returns the number of keys currently available in the Windows ASPECT keyboard buffer; if the buffer is empty, $KEYHIT returns 0.
Changes to Windows ASPECT Commands:
o Two new SET TERMINAL commands have been added:
SET TERMINAL UPDATE INCREMENTAL|BLOCK|FAST
Specifies which method will be used to update the Terminal window display with new data: incremental, block or fast. For more information on these values, see the description of the Setup window Terminal dialog in Chapter 5 of your User Manual.
SET TERMINAL VIEWCURSOR NO|YES
Determines how incoming data is displayed when the Terminal workspace is smaller than the logical size for the current emulation. For more information, see the description of the Setup window Terminal dialog in Chapter 5 of your User Manual.
o The syntax for the two commands UWUTOWIN and WINTOUWU now carry an additional option, USERWIN|BACKGROUND, in the Windows ASPECT Script Language Reference Manual. Since UWU measurements are converted differently for an object tied to the User window,specify the option corresponding to the object's USERWIN|BACKGROUND setting to ensure the coordinates are calculated correctly.
o When multiple selections are made from a listbox, the file which will store the selections will not be updated until the listbox is no longer the focus and another control is active. The same is also true of editbox controls - the contents of the edit box are not placed into the associated global variable until the editbox is no longer the focus. The contents of a file editbox are not written to disk until the dialog is terminated, and no changes are written to disk if the dialog is exited with the Esc key, Close menu item or the Cancel pushbutton.
o The following dialog box control limits were increased from 8 to 16:
NORMAL PUSHBUTTON
UPDATE PUSHBUTTON
ICON
ICONBUTTON
VTEXT
GROUPBOX
This change does not affect the defined return values in $DIALOG, since each control range is at least 20 digits apart.
o A setting of 0 for the Make attempts field in the Dialing Directory Options dialog now causes PROCOMM PLUS for Windows to redial forever until interrupted by the user.
o The METAFILE command now has an additional dialogbox statement syntax:
METAFILE left top width height filespec
The filespec parameter is a global string variable specifying the filename containing the Metafile (.WMF) file to be displayed.
o The commands SET ASCII LINEPACE and SET RAWASCII LINEPACE now accept values ranging from 0 to 999.
o The FTEXT command is listed with incorrect syntax in the Windows ASPECT Script Language Reference Manual - the correct command syntax should read:
FTEXT left top width height gstrvar [HSCROLL|long]
Note that FTEXT accepts either of the optional parameters, but not both in combination.
o The GETDISK command now returns the currently-active disk drive designator into a string variable, including the colon (for example, "c:").
o The DIALLOAD command will not create disk directories if the specified path doesn't exist - for example, if you attempt to load the file "C:\TEST\NEW.DIR" and the directory \TEST doesn't exist, PROCOMM PLUS for Windows will not create the \TEST directory. Instead, the Dialing Directory file NEW.DIR is created in the default Dialing Directory path specified in the Setup System Settings dialog.
o The RUN command is listed with incorrect syntax in the Windows ASPECT Script Language Reference Manual - the correct command syntax should read:
RUN filespec [MINIMIZED|MAXIMIZED|HIDDEN] [intvar]
o A negative value is now ignored by the PRINTMARGIN command, and will not change the margin value.
o The command SET TERMINAL TABSTOPS is spelled incorrectly in the Windows ASPECT Script Language Reference Manual - the correct command should read:
SET TERMINAL TABSTOP integer
o A negative value is now ignored by the SET PRINT MARGINS statement, and will not change the margin value.
o The FETCH command now returns three values for the SET PRINT ORIENTATION statement: FETCH returns a 1 for Portrait, a 2 for Landscape and 0 if the orientation is not supported by the selected printer device.
o The optional DEFAULT keyword is ignored by the SET CONNECTION TYPE command if SET DIALACCESS is a non-zero value (for example, when changing the Connection type in a Dialing Directory entry). If specified, it will not change the default connection specified in the Setup window.
GETFILE and SENDFILE Protocols:
The protocol parameter in the GETFILE and SENDFILE commands corresponds to one of the default protocol keywords; if an index is specified, the integer value corresponds to the protocol index, which reflect the same ordering as they appear in the PROCOMM PLUS for Windows Setup Protocol drop-down listbox. Depending on the action and the protocol, a filespec may be required.
GETFILE SENDFILE
Index Name filespec filespec
0 ZMODEM NO YES
1 KERMIT NO YES
2 XMODEM YES YES
3 1KXMODEM YES YES
4 1KXMODEMG YES YES
5 YMODEM NO YES
6 YMODEMG NO YES
7 CISB NO NO
8 ASCII YES YES
9 RAWASCII YES YES
For more information, please refer to the definitions of GETFILE and SENDFILE in your Windows ASPECT Script Reference Manual.
DOS and RUN Commands:
When a path is not provided for the application executed with either of these commands, PROCOMM PLUS will search for the application first within the default directory (specified by the SET ASPECT DEFAULTPATH command). If the application is not found there, the search continues to the Windows home directory, the Windows system directory, the directories specified by the PATH environment variables and any mapped network directories. If the application filename has no extension, a default of .EXE is assumed.
Trapping Keys in Windows ASPECT:
Windows ASPECT can only receive keys typed when the PROCOMM PLUS for Windows main application window is active; therefore, your scripts will not recognize characters you type into other windows or dialog boxes. This is also true of the Ctrl-Break sequence used by Windows ASPECT to display the runtime debugging dialog or terminate "dead-end" commands like PAUSE and WAITFOR.
If you've SET ASPECT KEYS ON in your script, keys typed while the PROCOMM PLUS for Windows main application window is active will be "buffered" (or stored) until they are retrieved with the KEYGET command. If you SET ASPECT KEYS OFF, a KEYGET command will pause script execution until the main application window is active and a key is pressed.
Windows ASPECT Reserved Words:
The following words have been added to the list of Windows ASPECT reserved words:
$DDIRFNAME
$DIALCOUNT
$DIALQUEUE
FAST
INCREMENTAL
MOVEOBJECT
NOPAINT
UWUTOWIN
VIEWCURSOR
WINTOUWU
Although they appear in Appendix B, the following words are NOT reserved words in Windows ASPECT:
CMDMODE
ENDSESSION
NETCON
NETDISCON
NETMENU
SERVERNAME
Also, please note that the reserved word SUCCESS was incorrectly printed with a trailing semicolon.
Additional Thanks:
In addition to those listed in the Help menu About window and the manuals, DATASTORM TECHNOLOGIES, INC. would like to thank the following people for their help in the production of PROCOMM PLUS for Windows:
Chris Brandow
Kitty Sundahl
Tim Kilgore
Larry McKinley
Fred Perkins
Chuck Spohr
Howard Myers
DATASTORM TECHNOLOGIES, INC. would also like to thank James Fair of the Fishing Hole BBS for the use of his animated ANSI artwork in the script DEMO.WAX.
SYMANTEC--PETER NORTON GROUP
README.TXT--March 03, 1993
Copyright 1993 Symantec Corp. All Rights Reserved.
Release Notes
Norton pcANYWHERE for Windows
Version 1.0
Welcome to Norton pcANYWHERE for Windows!
-----------------------------------------
Please read this document carefully; it contains important
information not included in the documentation. You may also
want to print it for future reference.
CONTENTS
========
1. NORTON pcANYWHERE AND WINDOWS 3.0
Novell NetWare
Data Rates
COM Ports
2. GENERAL INFORMATION
Naming Your Computer
Installing the Host
Uninstalling the Host
Changing Host Options
Loading Mouse Drivers
Starting the Gateway and Host TSRs
Norton Desktop for Windows
pcANYWHERE and CTL3D.DLL
Online Terminal Mode
Mouse Clicks
3. CHANGING HARDWARE DRIVERS
4. PHYSICAL/LOGICAL FONTS
5. PRINTING
Printing From the Host
Printing with the Remote Only Setting
6. pcANYWHERE 4.5
Configuration Files
Online Menu
Uninstalling
7. DOS TSR
Minimizing the Host Icon
File Transfer
Resident Mode
Quick Connect
8. COMMAND LINE OPTIONS
For WINAW.EXE
For AW5HOST.EXE
9. COMMUNICATIONS DRIVERS
Telebit ACS
Interrupt 14 drivers
10. NETWORKS
Novell NetWare
Artisoft LANtastic
11. WORKSTATIONS
Installation
DOS TSR
12. REMOVING pcANYWHERE
13. SCRIPTS
Commands and Variables
Operator Precedence
1. NORTON pcANYWHERE AND WINDOWS 3.0
=====================================
Novell NetWare
--------------
Windows 3.0 users may experience problems with NetWare IPX
connections due to a problem in the driver supplied with
Windows 3.0. You can obtain a new driver (VPIX.386) from
your Microsoft or Novell representative.
Data Rates
----------
Serial connections under Windows 3.0 have been found to be
most stable at data rates below 19.2K bps. If a connection
of 19.2K bps or higher is required while running Windows 3.0
we recommended that the Host TSR be in memory.
COM Ports
---------
In Windows 3.0 environments, the Host's COM port cannot be
shared. For example, if you have the Host TSR in memory, no
calls out can be made from this machine without first
unloading the Host DOS TSR.
2. GENERAL INFORMATION
=======================
Naming Your Computer
-------------------------
The following characters are not valid characters for use in
your COMPUTER NAME. This is to insure that the name you
choose for your computer is acceptable to your network
environment.
\ / : ; , * ? . " < > = + | [ } _ '
Installing the Host
-------------------
If you did not install the Windows or Full-screen DOS Host
when you installed pcANYWHERE, you can do so without having
to reinstall the entire program.
To install the Host:
1. Double-click the Host Install icon in the pcANYWHERE group
window.
2. Check the "Allow this computer to be controlled from
another computer" checkbox to allow your computer to act
as a Host.
3. Check the "Allow remote users to run full screen DOS
Applications" checkbox to run the DOS TSR. The DOS TSR
allows remote users to exit from Windows to DOS and to run
full screen DOS Applications.
4. Click OK.
5. Click Exit to DOS.
6. Reboot your computer.
Uninstalling the Host
---------------------
You should uninstall the Host when you need to make changes
to your computer's display, keyboard or mouse. See "Changing
Hardware Drivers" later in this document for more
information.
To uninstall the Host:
1. Double-click the Host Install icon in the pcANYWHERE group
window.
2. Uncheck the "Allow this computer to be controlled from
another computer" checkbox.
3. Click OK.
4. Click Restart Windows.
Changing Host Options
---------------------
If the Host is loaded (that is, the DOS TSR is in memory or
the Windows Host is minimized), any changes made in the
Configure Host Operations dialog box or the Be a Host dialog
box will not take effect until the Host is canceled and
restarted.
Loading Mouse Drivers
---------------------
The pcANYWHERE install program will try to locate the Host
TSR line in your AUTOEXEC.BAT file after any mouse drivers.
If you add mouse drivers to your AUTOEXEC.BAT, be sure to add
them before the Host TSR line.
Starting the Gateway and Host TSRs
----------------------------------
The Gateway and Host TSRs are DOS programs, and as such must
be started before you start Windows. Attempting to start them
after you have started Windows is unsupported.
Norton Desktop for Windows
--------------------------
If you install while using Norton Desktop for Windows as your
Windows shell, then switch to Program Manager as the shell,
you will need to set up a group box for pcANYWHERE. Please
refer to your Windows manual for information on setting up
group and items for Program Manager.
pcANYWHERE and CTL3D.DLL
-------------------------
pcANYWHERE supplies a copy of a DLL called CTL3D. This DLL is
placed in your WINDOWS\SYSTEM directory. This DLL is supplied
by Microsoft with many applications. If you install other
applications after installing pcANYWHERE and experience a
loss of 3D effect, your new applications may have overwritten
our version of CTL3D with an older one. To fix this you can
copy this DLL from your pcANYWHERE distribution diskettes to
the SYSTEM directory.
Online Terminal Mode
--------------------
The Edit menu option in the 'Online Terminal' has no 'copy'
command. This is because any information selected in the
terminal is automatically placed in the copy buffer.
Mouse Clicks
------------
Due to communications delays, you may need to alter the
'double click' speed for your mouse. By lowering the delay
rate, Windows will respond better to double clicking during a
connection. For more information on changing the mouse
settings, see your Windows User's Guide.
3. CHANGING HARDWARE DRIVERS
=============================
Whenever you install a new monitor, keyboard or mouse, or
change display resolution, you generally must also run
software that comes with the device. This software changes
entries in your SYSTEM.INI file. After installing pcANYWHERE,
care must be taken not to change entries in your SYSTEM.INI
file without uninstalling pcANYWHERE first. pcANYWHERE relies
on the settings it places in this file. Modifications may
effect the program execution. For more information, see
"Installing the Host" and "Uninstalling the Host" earlier in
this document.
For example, programs that let you change screen resolution
for your display adapter actually change the display driver
in your SYSTEM.INI file. This overwrites information needed
by pcANYWHERE.
4. PHYSICAL/LOGICAL FONTS
==========================
pcANYWHERE provides the ability to change how fonts are used
during a connection. pcANYWHERE users can change the
'logicalfonts' section in the WINDOWS\PCAW.INI file to select
one of two modes, LOGICAL or PHYSICAL fonts. Users can
experiment with the setting to effect initial connection
speed and the general look of some applications run remotely.
The default setting has been found to be appropriate for most
environments.
[font]
logicalfonts=<number>
If this section is not included in the PCAW.INI file,
pcANYWHERE defaults to logicalfonts=0.
number meaning
------ -------
0 pcANYWHERE Host sends extra data to the Remote for
each character displayed in order for the character
to appear correctly on the Remote's screen. While
this setting gives you the best representation of
the Host's screen, pcANYWHERE has to send more data
which may cause your pcANYWHERE session to slow
down slightly. You should use this setting for the
following situations:
* The Remote does not have the same fonts
installed at the Host.
* Connecting to a 4.5x Host. pcANYWHERE 4.5
always sends physical font information. If you
connect to a pcANYWHERE 4.5x Host with
logicalfonts=1, Windows text will not appear
correctly on the Remote's screen.
* Connecting to a VGA Host with an EGA Remote.
Text may not appear correctly with
logicalfonts=1. While in a DOS Window,
horizontal lines may appear unless
logicalfonts=0.
1 Logical font information instructs pcANYWHERE to
send the name of the fonts in use by the Host
system. If the Remote has the same font,
pcANYWHERE uses it to display the hosts screen as
accurately as possible. If the Remote system does
not have the same font, the Windows environment
selects the closest matching font available. This
will improve text speed slightly at the risk of
getting incorrect font data on your screen.
5. PRINTING
============
Printing From the Host
----------------------
In order to print from the Host, the port must be changed on
the Host computer to LPT1.DOS in the Windows Control Panel.
Choose the Printer icon, click the Connect button, then
select the port.
Printing with the Remote Only Setting
-------------------------------------
If printing is set up for Remote Only, pcANYWHERE will start
printing when the Remote computer brings up the Online Menu
or ends the session.
6. pcANYWHERE 4.5
==================
Configuration Files
-------------------
The first-time that pcANYWHERE for Windows is run, any
existing pcANYWHERE 4.5 configuration files that are in the
personal directory will be automatically scanned and new
pcANYWHERE for Windows 1.0 files will be built from them.
This will not alter the existing 4.5 configuration files. We
do recommend backing up any existing 4.5 configuration files
prior to installing pcANYWHERE 1.0 as a precaution.
Online Menu
-----------
pcANYWHERE 4.5 users should note that double clicking on the
'In Session' icon will display the Online Menu. This replaces
the 'hotkey' sequence in pcANYWHERE 4.5.
Uninstalling
------------
Care must be taken if users want to run pcANYWHERE 4.5 and
pcANYWHERE for Windows 1.0 on the same computer. Symantec
recommends uninstalling one product before installing the
other. This will avoid any conflicts and provide the best
results.
7. DOS TSR
===========
Minimizing the Host Icon
------------------------
If the Host DOS TSR is loaded in memory with the -m=r switch
set, the switch setting will override the 'Minimize While
Waiting' checkbox in the Configure Host Operations dialog box
and the Host will always be minimized while it waits for a
call.
File Transfer
-------------
pcANYWHERE for Windows 1.0 provides File Transfer
capabilities in the Windows host module( Winhost.exe ). The
DOS TSR provided with pcANYWHERE 1.0 still requires the
Windows host for file transfer capabilities.
To Set Up the Windows Host:
* Run the pcANYWHERE for WINDOWS Host install and check both
checkboxes (Allow this computer to be controlled from
another computer and Allow remote users to run full screen
DOS applications) on the first screen that comes up.
Or,
* Check the Auto Start Host checkbox in the Configure Host
Operation dialog box.
Resident Mode
-------------
After installing pcANYWHERE for Windows 1.0 and prior to
loading the DOS TSR, you must run pcANYWHERE and set up your
hardware information and Computer Name. Without doing this
the DOS TSR can not properly execute.
Quick Connect
-------------
When the DOS TSR is launched, it reads configuration settings
from the Be a Host dialog box. If you change Quick Connect
settings for the Host while the TSR is in memory, the
message, "TSR is busy with another device" will appear. This
is not an error condition. If you require the ability to
change settings dynamically, simply remove the TSR from
memory prior to launching pcANYWHERE.
8. Command Line Options
========================
For WINAW.EXE
-------------
The Windows Host (WINAW.EXE) can have the following command
line arguments:
-i=<userid> User-id (only used when administrator
installation used)
-o=r Remote operation
-o=h Host operation
Operating mode:
-m=d Dial
-m=w Wait for a Call
-m=v Voice First
-m=s Run a script (for -o=r only)
-n=<host_entry> Host directory entry (for -o=r and -
m=d, w, v)
-s=<online_serv_entry> online service directory entry (for -
o=r and -m=d, w, v)
-n=<script_filename> script filename (for -o=r and -m=s
only)
-n=<phone_number> phone number to dial for Host dial
operation (for -o=h and -m=d only)
-c=<hardware_setup> hardware setup for Host operation (for
-o=h only)
Examples:
Remote operation to dial a Host (administrator install):
WINAW -i=userid -o=r -m=d -n=A HOST ENTRY
Host operation to wait for a call (standard install):
WINAW -o=h -m=w -c=MODEM CONFIGURATION
For AW5HOST.EXE
---------------
The DOS TSR (AW5HOST) can have the following command line
arguments:
-I=<userid> User-id (only used when administrator
installation used)
-M=R Start the Host in resident mode. (inactive)
-M=A Start the Host to accept a call at any time (in
background)
-M=W Start the Host to wait for a call (in
foreground)
-W=<path> DOS path to your Windows directory. This is not
required if the -I=xxxxx is used.
-P=<path> DOS path to your configuration files. This is
not required if you are using a "AW="
environment string or if the configuration files
are in the current directory.
The Gateway TSR also uses the -I and -P command line
arguments, with the same requirements as listed above.
9. COMMUNICATIONS DRIVERS
==========================
Telebit ACS
-----------
You will need PDWSINF.EXE (provided by Telebit) to register
as a Telebit Asynchronous Communication Server (ACS) Host
when using the Host DOS TSR.
You will need the Windows driver WSINF.DLL (provided by
Telebit) in order to use a Telebit ACS without the DOS host
TSR.
Interrupt 14 drivers
--------------------
INT 14 drivers work with Data Rates of up to 9600 bps.
10. NETWORKS
============
Novell NetWare
--------------
To be an IPX Host in Standard mode, Windows requires you to
first load TBMI2.COM. This file is provided with Windows
version 3.1; you can obtain this file from your Microsoft
representative.
Some older versions of pcANYWHERE for DOS recommended
remarking out VIPX.386 from the SYSTEM.INI file. If you have
one of these versions installed, you should remove the remark
from the VIPX.386 line prior to installing pcANYWHERE 1.0.
Artisoft LANtastic
------------------
It is recommended that users should avoid installing
pcANYWHERE 1.0 on a LANtastic Server Node. You may experience
difficulty in establishing connections in this configuration.
In Windows Setup, the system setting for Network should be
'Microsoft Network (or 100% compatible).'
11. WORKSTATIONS
================
Installation
------------
In an effort to provide an efficient installation, pcANYWHERE
administrative installs do not search network drives for a
previously installed version of pcANYWHERE for WINDOWS.
DOS TSR
-------
Care should be taken when setting up your AUTOEXEC.BAT file
to load the DOS host TSR. If your host is set for a network
connection, be sure to place the line to load the DOS TSR
AFTER your 'login' procedure.
12. REMOVING pcANYWHERE
=======================
If you want to remove pcANYWHERE files, it is highly
recommended that you use the Remove pcANYWHERE icon to
uninstall pcANYWHERE.
Only the program files are removed by the uninstall program--
you must remove the configuration files manually.
13. SCRIPTS
===========
Commands and Variables
----------------------
$DATE
The format of the date returned by this variable is MM/DD/YY.
$DTR
This environment variable is not supported. Reading $DTR will
always return a value of 0.
COPY
The Copy command copies only individual files. Wildcards such
as * and ? are not allowed. If wildcards are used, no files
are copied.
DEL
The Delete command deletes only individual files. Wildcards
such as * and ? are not allowed. If wildcards are used, no
files are deleted.
DESCRIPTION
The Description command is not listed in the Script manual.
Refer to the Tools Reference in the pcANYWHERE Editor for
information.
FIND FIRST and FIND NEXT
These commands will search for the specified file within the
current directory, not the entire drive.
INTEGER
This statement defines a variable as an integer (a numeric
value without a decimal portion).
Example:
INTEGER A
(Defines A as a integer variable.)
SET FILE ATTR
This command sets the attributes of a file. The integer
value is constructed by adding the values of the desired
attributes. For example, a new attribute value of 7 sets a
file as read-only, hidden, and system. A value of 0 will
clear all attributes from the file.
The file attributes are set as follows:
Attribute Value
--------- -----
Read-only 1
Hidden 2
System file 4
Volume label 8
Subdirectory 16
Archive bit 32
Example:
SET FILE ATTR "C:\DATA.FIL" 1
(Sets data.fil to a read-only file.)
STRING
This statement defines a variable which will hold a quantity
of alphanumeric characters. The length of the string is
defined using square brackets ([ ]).
Example:
STRING A[50]
(Defines A as a string variable which can hold up to 50
alphanumeric characters.)
CANVAS FOR WINDOWS RELEASE NOTES
This file contains information that was not included in the Canvas for Windows documentation, as well as corrections to the manuals. A separate text file, QTREADME.TXT, describes the QuickTime tool that is included with Canvas.
If you need additional information, please call Deneba Software's Customer Support Department at (305) 596-5644.
We welcome your comments and suggestions regarding Canvas. Many enhancements to our products have been based on input from users, so please call or write us with your comments. Our mailing address is Deneba Software, 7400 S.W. 87th Ave., Miami, FL 33173. The phone number is (305) 596-5644.
------------------------------------------------------------
CHANGES TO THE INSTALLATION PROCEDURE
Canvas installation options differ slightly from the description on Page xvi of the Canvas for Windows User's Manual. In the Custom Installation dialog box, you can clear the appropriate check boxes if you do not want to install the included TrueType fonts, tutorial files, or other program components.
Other installation changes:
Step 6 - To specify a directory and drive location for Canvas, choose the Set Location button.
Step 7 - To begin installation, choose the Install button. The Pause button referred to after Step 7 does not appear.
CANVAS TUTORIALS
Correction to the tutorial in Chapter 4 of the User's Manual: On Page 4-4, replace Step 4 with the following:
Click the word "Width" and it changes to read "Right." Double-click the number in the box adjacent to "Right" to highlight the number.
Clarification of Step 2, Page 4-7: The Style Sets submenu is in the Text menu.
COLOR SETS
Canvas is shipped with 12 color sets, which are files of colors that can be loaded into the Colors palette. Four of the color sets are PANTONE(R) system colors: COATED.PAL, UNCOATED.PAL, PROCESS.PAL, and PROSIM.PAL. The other color sets contain various colors in the RGB and CMYK color systems. The BASIC.PAL color set contains the colors of the default Canvas Colors palette.
COMMAND KEYBOARD SHORTCUTS
In the menus shown in Appendix D of the Reference Manual, some letters are incorrectly underlined. Refer to the menus in the program for the correct letters to use with ALT to choose commands.
COPYING GUIDES
Correction to the Edit Special command (User's Manual, Page 17-9), under "Copy Guides": To paste guides into a Canvas document after using the Copy Guides option, choose the Paste Special command (not the Paste command) from the Edit menu. In the Paste Special dialog box, choose the Paste button to paste the guides into the document.
FINDING COLORS
Canvas will search for named colors in the Colors palette. When you specify text to search for, Canvas selects the first color in the palette whose name includes the text. The documentation (User's Manual, Chapter 23, and Reference Manual, Pages 46 and 48) incorrectly describes use of asterisks and spaces when you search for a color.
To find a color whose name includes "red," (such as "Red 150" or "Reddish Brown"), type "red" in the Find Color dialog box. You can also type a number to select a color whose name includes the number. This is useful for selecting PANTONE(R) colors, which are named by number.
For more information on colors, see Chapter 23 in the User's Manual, "Using Color in Canvas."
LEADING IN TEXT OBJECTS
The height of text ascenders and descenders is defined differently on Macintosh and Windows systems. Therefore, automatic leading (line spacing) factors will not translate correctly when documents created on one system are opened on the other.
A new feature of Canvas for Windows and Canvas 3.5 for Macintosh allows you to standardize the baseline of text objects among Macintosh and Windows systems to ensure correct leading across platforms. In the Type Specifications dialog box, whenever the number in the Factor box is preceded by a minus sign, Canvas interprets the number as an ascender height percentage, not as a Leading Factor.
Use the following procedure to specify the correct percentage: Choose the Type command from the Text menu to open the Type Specifications dialog box. In the Factor box (under Leading), type "-80" (minus 80) to specify that ascender height is 80 percent of text size. This is the setting recommended by typesetters.
After setting the ascender height percentage, you can type any leading amount (in points) in the Addition box. For single spacing, type the same number as the text size. For 1 1/2 and double spacing, multiply the text size by 1.5 or 2, respectively.
MACINTOSH DOCUMENT COMPATIBILITY
To open documents created by Canvas for Windows on a Macintosh computer, you must use Version 3.5 or later of Canvas Macintosh and the Windows I/O external tool must be active in Canvas on the Macintosh.
MACROS TOOL
Correction to the Macros tool (Reference manual, Page 128), under "Using modifier keys": The ALT key is not a modifier for placing unlinked MacrObjects in a document.
To place an unlinked MacrObject in a document, draw the MacrObject normally, then choose the Unlink option from the Macros submenu in the Object menu.
PEN MANAGER
The DOS file name of the Pen Manager external tool has been changed from PEN.CVT to PENMGR.CVT
PICTURE OBJECTS
A picture object in a Canvas Macintosh document will appear as a box with an X if the document is opened in Canvas for Windows. A picture object in a Canvas for Windows document will appear as a box with an X if the document is opened in Canvas Macintosh. These objects will display correctly when the documents are opened on the original platforms.
If you want a picture object to be visible when you move a document between Windows and Macintosh versions of Canvas, you should convert the object first. You can determine if an object is a picture object by selecting it and choosing the Object Specs command in the Object menu. The Type box shows a picture frame when a picture object is selected.
To convert a picture object in Canvas Windows so it can be viewed in Canvas Macintosh, select the object and choose the Object Specs command in the Object menu. From the Type box, select group ("G"). Choose the OK button.
To convert a picture object in Canvas Macintosh so it can be viewed in Canvas Windows, select the object and copy it to the Clipboard by pressing Command-C. Hold down Shift and choose Paste Without Comments in the Edit menu. Remove the original object from the document and position the pasted object in its place.
POSTSCRIPT I/O TOOL
Correction to the Reference manual (Page 200), under "Saving EPSF files": The EPSF I/O external tool should be the PostScript I/O external tool.
POSTSCRIPT PRINTING IN WINDOWS 3.0
If you run Canvas under Windows 3.0, and you want Adobe Type 1 format fonts to be downloaded to a printer, you must have version 3.4 or later of the Microsoft PostScript printer driver.
To see what version of the printer driver is installed on your system, select Printers in the Windows Control Panel. Select a printer that uses the PostScript driver, select the "Setup" button, and then select the "About" button.
SAVING CGM FILES
Correction to the Reference manual (Page 200), under "CGM export restrictions": CGM files support the Copy pen mode. They do not support the Or pen mode.
SAVING TIFF FILES
An additional option, a check box labeled "Selection Only," has been added to the TIFF Export Options dialog box (Reference Manual, Page 205). If you select this check box, only the selected objects in the document are included in the TIFF file that Canvas creates. If you clear the check box, the TIFF file will contain an image of all objects in the document.
SPOT COLORS
When printing or saving color separations in which you want one or more spot colors to appear, you must designate the colors as spot colors (in the Color Manager or Color Info dialog boxes) before they are applied to objects in the document. For more information on spot colors and color separations, see Chapter 22, "Going to press," and Chapter 23, "Using color in Canvas," in the User's Manual.
TIPS FOR USING VARIOUS FILE FORMATS
Canvas can open documents that have been saved in a variety of file formats. When you open a file that was created in another program, however, data can be lost because of non-standard options or extensions to common file formats.
If you experience problems when opening a file that was created in another program, try the following: In the other program, re-save the document using the default or general settings for the chosen file format. Avoid proprietary options or variations of common file formats to help ensure successful transfer of files to Canvas.
TOOL LOADER EXTERNAL TOOL
The Tool Loader external tool is always active. It does not appear in the tool list in the ToolPicker dialog box, and it cannot be deactivated like other external tools.
*************************
VISIO 2.0 README.TXT FILE
*************************
This file contains important, late-breaking information about Visio. We recommend you read this file and keep a printed copy with your Visio documentation. For important network-specific information, be sure to read (and print) the NETWORK.TXT file in the Visio directory.
Tip: If necessary, choose Word Wrap from the Notepad Edit menu to wrap the text within the document window.
----------------------------------
REPLACING VISIO 1.0 WITH VISIO 2.0
----------------------------------
When you install Visio 2.0 on top of Visio 1.0, copies of the Visio 1.0 templates and stencils can be saved in a separate subdirectory.
---------------------------------------
OPENING VISIO 2.0 FILES WITH VISIO 1.0
---------------------------------------
You cannot use Visio 1.0 to open files created using Visio 2.0. If you try to open a Visio 2.0 file by using the Open command from the Visio 1.0 File menu, Visio displays a message that says you're using the wrong version of Visio. If you try to open a Visio 2.0 file by double-clicking the filename in the Windows File Manager, Visio 1.0 displays an internal error message, which does not describe the problem. If you get this message and suspect the file you're trying to open was created in Visio 2.0, you can confirm it by trying to open the file using the Open command from the File menu.
-------------------------
VISIO 2.0 INSTALLED FILES
-------------------------
The following lists show the files copied to your hard drive if you install the complete version of Visio in the default location:
Setup copies these program and text files to the Visio directory:
NETWORK.TXT
PROGREF.HLP
README.TXT
VISIO.EXE
VISIO.HLP
VISIOLIB.DLL
Setup copies these import and export filter files to the Filters subdirectory:
EBBMP9.FLT
EBBMP9.INI
EBPCX9.FLT
EBPCX9.INI
EBTIF9.FLT
EBTIF9.INI
EMCGM9.FLT
EMCGM9.INI
EMDXF9.FLT
EMDXF9.INI
EMPCT9.FLT
EMPCT9.INI
EMPS_9.FLT
EMPS_9.INI
IMCGM9.FLT
IMCGM9.INI
IMDXF9.FLT
IMDXF9.INI
IMPCT9.FLT
IMPCT9.INI
IMPS_9.FLT
IMPS_9.INI
IMWMF9.FLT
IMWMF9.INI
IRPCX9.FLT
IRTIF9.FLT
ISGDI9.DLL
ISGDI9.INI
Setup copies these sample drawing files, which use shapes from the stencils that come with Visio, to the Samples subdirectory:
BLOCK.VSD
FLOWCHRT.VSD
NETWORK.VSD
ORGCHART.VSD
Setup copies these template (.VST) and stencil (.VSS) files to the Template subdirectory:
BASIC.VSS
BASIC.VST
BLOCK.VSS
BLOCK.VST
BORDER.VSS
CALLOUT.VSS
CHART.VSS
CHART.VST
CLIPART.VSS
CONNECT.VSS
EE_BASIC.VSS
EE_BASIC.VST
EUROPE.VSS
FLOWCHRT.VSS
FLOWCHRT.VST
FORMS.VSS
FORMS.VST
MAP.VSS
MAP.VST
NETWORK.VSS
NETWORK.VST
ORGCHART.VSS
ORGCHART.VST
PRACTICE.VSS
PRACTICE.VST
PROJMGT.VSS
PROJMGT.VST
SPACEPLN.VSS
SPACEPLN.VST
STATES.VSS
SYMBOLS.VSS
WORLD.VSS
Setup copies these DLL files to the Windows System subdirectory:
OLE2.DLL
OLE2PROX.DLL
OLE2DISP.DLL
OLE2NLS.DLL
COMPOBJ.DLL
STORAGE.DLL
OLE2.REG
OLE2AUTO.REG
VBRUN300.DLL
VBOA300.DLL
Setup copies this quick tour file to the Tutorial subdirectory:
VISTUTOR.EXE
Setup copies these files to the Add-ons subdirectory and to the Library and Stndoc subdirectories within the Add-ons subdirectory:
VISCONST.BAS
VISREG.BAS
MAIN.BAS
REPORT.FRM
PROGRESS.FRM
STNDOC.VST
SELSTENC.FRM
STNDOC.ICO
STNDOC.MAK
INVNTRY.HLP
INVNTRY.VSL
STNDOC.EXE
The Visio setup program also creates a Drawings subdirectory (a place to store your drawings).
-------------------------
VISIO AND OLE 2 DLL FILES
-------------------------
If you have trouble running Visio, make sure all the OLE 2-related DLL files are installed and in the correct location. All of the following files must be installed in the Windows System subdirectory to run Visio:
OLE2.DLL
OLE2PROX.DLL
OLE2DISP.DLL
OLE2NLS.DLL
COMPOBJ.DLL
STORAGE.DLL
If any of these files are missing, reinstall Visio. If you're running Visio from a network server, see your system administrator.
If you have further trouble, make sure there is only one copy of these files on your hard disk in a location where Windows can find them. If you have multiple copies, either delete the extra copies or move them to a location where Windows can't find them. (Windows looks in your drive path, the application subdirectories, the Windows directory, and the Windows System subdirectory.)
----------------------------------
VISIO 2.0 AND WINDOWS REGISTRATION
----------------------------------
At the end of the installation process, the Visio setup program displays a dialog box asking if you want to run Visio. To ensure that Visio is correctly registered in the Windows REG.DAT file (a file that contains information about the capabilities of each application), we recommend that you run Visio by choosing Run VISIO Now in the dialog box.
If you suspect that Visio is not properly registered (for example, if Windows displays an error message saying it cannot find the source application when you double-click an embedded Visio object in another application), you can force the registration process by choosing Run from the Windows Program Manager File menu and typing the Visio path followed by /r. For example:
c:\Visio\visio.exe /r
If Visio displays error messages saying OLE2 and OLE2AUTO are improperly registered, you can register them manually by using the Microsoft Registration Information Editor. For details, see section A.2 in the NETWORK.TXT file installed in the Visio directory.
-------------------------------------
SCREEN IMAGES AND IMPORTED EPS FILES
-------------------------------------
EPS files have two parts: The PostScript code used to print the image and an optional screen image used to display the image on the screen. When exporting EPS files, most graphics applications either automatically include a screen image or give you the option to include one. If you are given the option and you plan to use the EPS file in a Visio drawing, you should include the screen image (which is sometimes referred to as the TIFF preview). Otherwise, the EPS image may not be correctly displayed in or printed from Visio.
----------------------------------------
DISPLAYING AND INSTALLING TRUETYPE FONTS
----------------------------------------
If fonts in a dialog box don't display properly, check to see that TrueType fonts are installed in the Control Panel.
To check for TrueType fonts:
1. Open the Main program group in the Windows Program Manager.
2. Double-click the Control Panel icon.
3. Double-click the Fonts icon.
4. Make sure that (at a minimum) all the TrueType fonts that ship with the latest version of Windows appear in the list of installed fonts.
To add TrueType fonts:
1. Choose the Add button.
2. If no fonts are displayed, locate the Windows System subdirectory (from the Windows main directory). A list of TrueType fonts appears.
3. Highlight the TrueType font(s) to be added and choose OK.
------------------------
ATI ULTRA PRO VIDEO CARD
------------------------
When using the Ultra Pro/Mach 32 video card and the driver (dated April 1993) made by ATI Technologies, objects with fills may print as black. Version 2.0 of the driver solves this problem. To get the driver, call ATI Customer Support at 416-882-2626, or download a copy from CompuServe. (Type GO ATITECH at the ! prompt.)
---------------------
PRINTING ROTATED TEXT
---------------------
On HP LaserJet III and other PCL printers, if rotated text does not print where you expect it to, try printing with Print TrueType as Graphics enabled. To enable this setting, choose Print Setup from the File menu, choose Options, make sure the Graphics Mode option is set to Raster, then check the Print TrueType as Graphics option. If this solves the problem, you may want to make this change permanently using the Windows Control Panel.
--------------------------------------------------
USING THE MICROSOFT(R) WINDOWS(TM) PRINTING SYSTEM
--------------------------------------------------
If you have trouble printing rotated text using the Microsoft
Windows Printing System product, use Notepad or another text
editor to add the following line to the [Application] section
of your VISIO.INI file:
TextBaselineAlignment=0
Unless you are running VISIO over a network, the VISIO.INI file
can be found in the same directory as your VISIO.EXE file, usually
\VISIO. When running VISIO from the network, VISIO.INI is placed
in your Windows directory, usually \WINDOWS.
---------------------------------------------------
PRINTING ON HP LASERJET III and LASERJET 4 PRINTERS
---------------------------------------------------
If you use an HP LaserJet III or 4, be sure to use the latest version of the printer driver from Microsoft or Hewlett-Packard. The original drivers released with Windows 3.1 were version 31.1.89 for LaserJet III and 31.1.03 for LaserJet 4. The current versions, as of this writing, are version 2.1 for the LaserJet III used with the Universal Printer driver version 3.1.2, and version 31.V1.20 for LaserJet 4.
If you receive Error 21 (Print Overrun) messages when you print to the HP LaserJet 4, try these workarounds:
* Use the Windows Control Panel to verify that you are using the 31.V1.20 printer driver or later. Updates to the LaserJet 4 driver can be obtained in the CompuServe (HPPERI forum) or through HP.
* Set the correct amount of printer memory in the Control Panel. Please refer to the printer documentation for information on how much memory you need.
* Set the graphics mode to Raster rather than HP-GL/2. Although the HP-GL/2 mode is faster, often you can print more complicated pages using the Raster mode.
* Try using the Page Protect feature for the paper size you're using. Please refer to the documentation that came with your printer for additional information on the Page Protect feature.
* Try printing at 300 dpi rather than 600 dpi.
* If none of the above options help, install the HP LaserJet III driver in addition to the HP LaserJet 4 driver. Use the HP LaserJet III driver to print at 300 dpi to the HP LaserJet 4 printer.
--------------------------------------------
PRINTING ON HP DESKJET 500C or 550C PRINTERS
--------------------------------------------
When you print in Color mode on an HP DeskJet 500C or 550C with a version 3.0 printer driver, TrueType text prints as long bands. To fix this problem, set your dithering to anything other than Standard (the default). To change this setting in Visio, choose Print Setup from the File menu, choose the DeskJet printer (if it is not already selected), choose Options, choose More, then choose any Dithering option but Standard. To make this change permanent, set it using the Windows Control Panel.
Note that after you print using one of these printers, Visio is no longer the active application. To bring Visio back to the foreground, type Ctrl+Esc to open the Windows Task List dialog box, choose Visio from the applications list, and then choose Switch To to make Visio the active application.
Note: Use the method described above to make Visio the active application. Do not double-click the Visio icon. Double-clicking the icon opens another instance of Visio.
-----------------------------
PRINTING FROM WORDPERFECT 5.2
-----------------------------
When you print a Visio drawing in WordPerfect, it might look significantly different from the way it looks when you print it in Visio. This might be related to the printer driver you are using with WordPerfect. Visio created your drawing with a reference to the printer driver selected in the Print Setup dialog box in Visio. To make the printed drawings look more similar, use the same printer driver in WordPerfect that you use with Visio.
Although you may be printing to the same printer from both applications, in WordPerfect you have the option of using either the WordPerfect printer driver or the Windows printer driver. If you have been using the WordPerfect printer driver to print Visio drawings from WordPerfect, try choosing the Windows printer driver in the WordPerfect Select Printer dialog box.
------------------------------------------
ZEOS 486-33 CPU & FLOATING POINT EXCEPTION
------------------------------------------
The Award BIOS 3.10, 452-005-01, found in some ZEOS 486-33 machines (and possibly in other computer makes and models), does not handle floating point errors correctly. Floating point errors cause these machines to hang (stop responding). Floating point exceptions are most likely to result from using the Union or Fragment commands. If Visio displays an error message telling you that a floating point exception has occurred, try to save your work (if possible), then close Visio and Windows and restart your computer.
To correct this problem, you need an updated BIOS. ZEOS owners can contact ZEOS Technical Support at 612-633-7337 voice, 800-228-5390 toll-free, or 612-633-4607 FAX. Owners of other machines can contact the manufacturer of their machine.
--------------------------------------------------------------
USING VISUAL BASIC'S OLE AUTOMATION FEATURES TO CONTROL VISIO
--------------------------------------------------------------
The following information describes workarounds for problems we have found using the OLE Automation features of Visual Basic.
1. Don't use complex expressions as parameters to methods. If you chain several methods together in an expression and then pass that expression as the parameter to another method call, Visual Basic allocates temporary storage for the expression and never releases it. If you do this enough times, Visual Basic eventually crashes. For example, the following code causes an Application Error in Visual Basic:
Dim visio As Object ' Visio application object
Dim wins As Object ' Window collection
Set visio = GetObject( , "visio.application")
Set wins = visio.Windows
For i = 1 To 1000
k = wins.Item(wins.Count).Index
Next
To work around the problem, replace the body of the loop with:
For i = 1 To 1000
cnt = wins.Count
k = wins.Item(cnt).Index
Next
2. You must use square brackets around the method names that conflict with Visual Basic keywords:
Arrange
Close
Delete
Print
For example,
visio.Windows.[Arrange]
If you don't use square brackets, Visual Basic displays the following message:
"Method not applicable for this object"
3. Visio generates unique run-time error codes for different types of OLE Automation errors. Visual Basic, however, ignores these error codes and converts them all to a generic OLE Automation error--Error 440. This is a Visual Basic 3.0 issue that should be resolved in the next release.
4. Be careful when using default properties. Visual Basic calls the default property for an object even after an exception has occurred. This generally results in an Application Error in OLEDISP.DLL. For example, in some circumstances the following statement generates an Application Error:
Set page = doc.Pages(1)
In this example, Item is the default property for collections. If calling the Pages method generates an exception for whatever reason, the previous statement will cause an Application Error.
To work around the problem, replace the previous statement with:
Set page = doc.Pages.Item(1)
---------------- VISIO README.TXT ---------------- November 1, 1992 USING THE HP LASERJET III PRINTER --------------------------------- If you use the Hewlett-Packard LaserJet III printer driver, version 31.3.89, and get unexpected results printing text with TrueType fonts, try enabling the Print TrueType as Graphics option. To enable this setting, select Print Setup from the File menu, click on the Options button, and check the Print TrueType as Graphics box. PRINTING TIP - SETTING UP YOUR DRAWING -------------------------------------- For best results, select the printer that will be your final output device in Printer Setup before you start to draw. Changing printers after the fact can sometimes cause text to re-break to the letter widths of the new printer. PRINTING ROTATED TEXT USING THE PRINT TRUETYPE AS GRAPHICS OPTION ----------------------------------------------------------------- If you experience unexpected results printing rotated text using an HP LaserJet or other PCL printer, try printing with the Print TrueType as Graphics box checked. To enable this setting, select Print Setup from the File menu, click on the Options button, and check the Print TrueType as Graphics box. NON-BREAKING JUSTIFYING SPACEBAND --------------------------------- Visio supports a non-breaking justifying spaceband. To use this feature, make sure you have enabled the numeric keypad by pressing the Num Lock key, then hold down the Alt key and type 018 on the numeric keypad. ENHANCING PERFORMANCE --------------------- For general information on enhancing your system's performance, please refer to Chapter 14, Optimizing Windows, in your Windows manual. Visio performs certain functions faster when a floating point math co-processor is available and enabled. ZEOS 486-33 CPU & FLOATING POINT EXCEPTION ------------------------------------------ The Award BIOS 3.10, 452-005-01, found in some ZEOS 486-33 machines and possibly in other computer makes and models as well, does not correctly handle floating point exceptions. As a result, floating point errors will cause these machines to hang (that is, to stop responding). Floating point exceptions are most likely to be the result of a Union or Fragment operation. If Visio displays an error message telling you that a floating point exception has occurred, try to save your work (you may not be able to), then close Visio and Windows, and reboot your computer. To correct this problem with the Award BIOS 3.10, 452-005-1, an updated BIOS is required. ZEOS owners can contact ZEOS Technical Support at 612-633-7337 voice, 800-228-5390 toll-free, or 612-633-4607 FAX. Owners of other machines can contact the manufacturer of their machine. DISPLAYING AND INSTALLING TRUETYPE FONTS ---------------------------------------- If fonts in your dialog box don't display properly, check to see that your TrueType fonts are installed in the Control Panel. To check for TrueType fonts: -Open the Main program group in the Windows Program Manager. -Double-click on the Control Panel icon. -Double-click the Fonts icon. -Make sure that (at a minimum) Arial TrueType fonts appear in the list of installed fonts. To add TrueType fonts, if needed: -Click on the Add button. -If no fonts are displayed, select the System subdirectory from the Windows main directory. A list of TrueType fonts will appear. -Highlight TrueType font(s) to be added and click OK.
For a sample of T2A's finished product, type the EXAMPLE.ANS to your screen. You must have Ansi.Sys or the eqivalent loaded in order to view ansi files. Or use a program such as A_TYPE from Ron Huskies/Intersoft. The ENHANCED.TXT,ANS,ASC files are samples from the registered version. These will help show the differences between the FREE version and the REGISTERED/ENHANCED version.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
%%% ASW-1440 v3.3 %%%
This disk contains Adaptec's Novell solution for all AHA-1540s (AT to SCSI),
all AHA-1542s (AT to SCSI with floppy controller), all AHA-1640s
(Microchannel to SCSI), all AHA-1740s (EISA to SCSI), and all AHA-1744s
(EISA to differential SCSI).
The directory tree structure of this disk is as follows:
ROOT ----- NET286 ----- VER3_1
| |
| --- VER3_2
|
--- NET386.30
|
|
|
--- NET386.31
|
|
|
--- NET386.311
If required, please consult your DOS manual on how to move around the
directory tree.
Within a subdirectory, you will find a README.TXT file describing the
driver(s) contained in that subdirectory.
This disk provides the following NetWare drivers:
-----------------------------------------------------------------------------
1.) AHA-1540/1542/1640 (AHA-1740/1744 in standard mode) Driver For NetWare
286 v2.15 and NetWare 286 v2.2.
(\NET286.215\VER3_1)
or
(\NET286.215\VER3_2)
-----------------------------------------------------------------------------
2.) AHA-1540/1542/1640 (AHA-1740/1744 in standard mode) Driver For NetWare
386 v3.0.
(\NET386.30)
-----------------------------------------------------------------------------
3.) AHA-1540/1542/1640 (AHA-1740/1744 in standard mode) Driver For NetWare
386 v3.1.
(\NET386.31)
-----------------------------------------------------------------------------
4.) AHA-1740/1744 (enhanced mode) Driver For NetWare 386 v3.1.
(\NET386.31)
-----------------------------------------------------------------------------
5.) AHA-1540/1542/1640 (AHA-1740/1744 in standard mode) Driver For NetWare
386 v3.11.
(\NET386.311)
-----------------------------------------------------------------------------
6.) AHA-1740/1744 (enhanced mode) Driver For NetWare 386 v3.11.
(\NET386.311)
-----------------------------------------------------------------------------
NOTE: The standard mode of the AHA-1740/1744 is software/driver compatible
with the AHA-1540/1542. The enhanced mode of the AHA-1740/1744 uses
a new high performance interface. This mode can directly access up
to 4 GBytes of memory!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
DC2000 README File Revision 1.03
On this diskette you will find device drivers for the DC2000
VL-Bus IDE Disk Controller.
DC2000.SYS (Version 1.40) is the driver for DOS
DC2000.386 (Version 1.20) is the driver for Microsoft Windows 3.1
N2000310.DSK (Version 1.10) is for Netware 386 3.10.
N2000311.DSK (Version 1.10) is for Netware 386 3.11.
+===============================================+
| DOS Driver for DC2000 VL-Bus IDE Controller |
+===============================================+
The file DC2000.SYS is the DOS driver for the DC2000 disk controller. You
will need it in the following situations:
- Your DC2000 has no on-board external BIOS to take the advantage of
the high speed 32-bit VL-Bus.
- Your DC2000 has an on-board external BIOS, but it can not work under the
default Turbo mode. You need to select the operating mode every time
when you power up or reboot your system.
Please follow the steps below to install the driver for DOS.
- Follow the installation steps as described in the DC2000 Installation
Guide and bring up your DC2000.
- Copy the driver DC2000.SYS to your system in the appropriate path.
- Add the following statement to your CONFIG.SYS file:
device = [drive:][\path\] DC2000.sys [/F or /T] [/W]
where [drive:] and [\path\] point to the directory that contains the
the DC2000.sys file. The parameters F, T and W define the operating mode
as follows:
F : DC2000 working in the Fast mode
T : DC2000 working in the Turbo mode (default operating mode)
W : DC2000 working in the 16 bit data access mode (If motherboard
CPU has a 16-bit external data bus. for examples,
IBM 486 SLC2....)
Note: If no parameter is specified, the DC2000 will be set to
run under the default Turbo and 32 bit data access mode.
Under Fast(F) mode, the DC2000 supports 32-bit VL-Bus IO. Under Turbo
(T) mode, the DC2000 not only supports 32-bit VL-Bus IO, it also supports
the read/write multiple commands. Since read/write multiple commands
allow the host to access disk data in multiple-sector blocks, the Turbo
mode will usually be faster.
Note that not all IDE drives support the read/write multiple commands.
Usually, you may set your DC2000 to run under the Turbo mode. When
your system is brought up, the driver DC2000.sys will automatically
issue an Identify Drive command to check if the attached IDE drive(s)
support the read/write multiple commands. In case your drive(s) does
not support the read/write multiple commands, the DC2000 will
automatically be forced to run under the Fast mode.
Note: Some IDE drives may not support the read/write multiple commands
properly. If your DC2000 can not access the attached drive(s) properly
under the default Turbo mode, you have to specify the parameter as "F".
Example:
If the DOS driver DC2000.SYS resides in the root directory of the
drive C:, and you want your DC2000 to run under TURBO mode, add the
following statement to the file CONFIG.SYS.
device= c:\DC2000.sys
Add the following statement if your DC2000 has to run under the
Fast mode:
device= c:\DC2000.sys /f
+========================================================+
| Microsoft Windows version 3.1 disk driver for DC2000 |
+========================================================+
The file DC2000.386 is the Microsoft Windows 3.1 disk driver for the
DC2000 controller.
While Microsoft Windows version 3.1 supports 32-bit disk access, the
disk data transfer between host and the IDE adapter is still limited
by the 16-bit ISA bus. If you want to speed up your hard drives under
Windows through the 32-bit VL-Bus, you will need this driver. In addition,
the driver also allows your host to access the disk data through the
faster "read/write multiple" commands.
Please follow the steps below to install the driver for DC2000.
1. Copy the driver DC2000.386 to your system in the appropriate path.
It is recommended that the driver DC2000.386 be copied to the Windows
SYSTEM directory.
2. Check if the following lines exist in the [386Enh] section of your
SYSTEM.ini file.
[386Enh]
32BitDiskAccess=ON
device=*int13
If the statements do not exist, add them into the [386Enh] section.
If the statements exist, but 32BitDiskAccess is set to "OFF", you
need to change it to "ON".
3. Delete the "device=*wdctrl" device setting.
Delete the command line "device=*wdctrl" from the [386Enh] section
of your SYSTEM.INI file, if it exists.
4. Install the virtual device "DC2000.386".
Add the following command lines in the [386Enh] section of the
SYSTEM.INI file:
device=[drive:][\path\]DC2000.386
DisksAccessMode=[Fast or Turbo] [/W]
The [drive:] and [\path\] point to the directory that contains
DC2000.386 file. Note that the setting must specify the full path
of the device driver DC2000.386.
The setting of disk_access_mode specifies the disk access mode as
follows:
Fast : DC2000 working in the Fast mode
Turbo : DC2000 working in the Turbo mode (default)
W : DC2000 working in the 16 bit data access mode
(If motherboard CPU has a 16-bit external data bus.
for examples, IBM 486 SLC2....)
Note : If no parameter is specified, the DC2000 will
be set to run under the default Turbo and 32 bit data
access mode.
Under Fast mode, the DC2000 supports 32-bit VL-Bus IO. Under Turbo
mode, the DC2000 not only supports 32-bit VL-Bus IO, it also supports
the read/write multiple commands. Since read/write multiple commands
allow the host to access disk data in multiple-sector blocks, the Turbo
mode will usually be faster.
Note: Not all IDE drives support the read/write multiple commands.
Usually, you may set your DC2000 to run under the Turbo mode. When
your system is brought up, the driver DC2000.386 will automatically
issue an Identify Drive command to check if the attached IDE drive(s)
support the read/write multiple commands. In case your drive(s) does
not support the read/write multiple commands, the DC2000 will
automatically be forced to run under the Fast mode.
Note: Some IDE drives may not support the read/write multiple commands
properly. If your DC2000 can not access the attached drive(s) properly
under the default Turbo mode, you have to specify the parameter as
"Fast".
+=======================================+
| Netware 3.xx disk driver for DC2000 |
+=======================================+
Please follow the steps below to install the driver for Netware 3.10.
Use N2000311.DSK instead of N2000310.DSK in the following procedure when
you are installing Netware 3.11. Note that you don't need to load the
ISADISK.DSK when you are installing the Netware driver for DC2000.
1. After you have installed the DC2000, bring up the Netware server
until the prompt ":" appears on the screen.
2. Type the following command after the ":" prompt:
:load N2000310 [/F or /T] [/W] port=1f0 int=e
The parameters F, T and W define the operating mode as follows:
F : DC2000 working in the Fast mode
T : DC2000 working in the Turbo mode (default operating mode)
W : DC2000 working in the 16 bit data access mode
(If motherboard CPU has a 16-bit external data bus.
for example, IBM 486 SLC2....)
Note: If no parameter is specified, the DC2000 will be set to
run under the default Turbo and 32 bit data access mode.
Under Fast(F) mode, the DC2000 supports 32-bit VL-Bus IO. Under Turbo
(T) mode, the DC2000 not only supports 32-bit VL-Bus IO, it also supports
the read/write multiple commands. Since read/write multiple commands
allow the host to access disk data in multiple-sector blocks, the Turbo
mode will usually be faster.
Note that not all IDE drives support the read/write multiple commands.
Usually, you may set your DC2000 to run under the Turbo mode. When
your system is brought up, the driver will automatically issue an
Identify Drive command to check if the attached IDE drive(s) support
the read/write multiple commands. In case your drive(s) does not
support the read/write multiple commands, the DC2000 will
automatically be forced to run under the Fast mode.
Note: Some IDE drives may not support the read/write multiple commands
properly. If your DC2000 can not access the attached drive(s) properly
under the default Turbo mode, you have to specify the parameter as "F".
+================================+
| UNIX Driver V1.1 for DC2000 |
+================================+
******** Install UNIX Driver ********
This driver is for AT&T UNIX SVR 4.0 and SCO UNIX 3.2.4. The driver
is provided in another diskette of your DC2000 package. Please follow
the steps below to install the UNIX driver:
1. Insert the diskette which contains the UNIX Driver into drive A:
and type the following command after the prompt "#":
# installpkg
2. The following message will be shown on the screen:
Will the DC2000 controller be in TURBO or FAST mode
(T/F)? (default=T)
Please answer 'T' or 'F' to select the DC2000 operating mode.
3. Next, message will be shown on the screen:
Does the mainboard CPU have a 16-bit external data bus
(for examples,IBM 486 SLC2 ...) instead of 32-bit bus
(Y/N)? (default=N)
Please answer 'Y' or 'N' to fit the feature of the mainboard CPU.
The installation procedure will continue.
4. Done! if you are running AT&T UNIX SVR 4.0.
5. If you are running SCO UNIX, type the following commands after the
driver is installed.
# cd /
# shutdown -y -g0 -i6
The commands will shutdown and reboot your system with the new kernel.
******** Change Operating Mode *******
If you want to change the operating mode after your system has been
brought up with the new kernel, please type the following command:
# ptisetmode
The following message will be shown on the screen:
This command will rebuild the kernel and shutdown the system
automatically.
Do you really want to proceed with it (Y/N)? (default=N)
Please answer 'Y' or 'N'.
The following message will be shown on the screen to ask you which mode
will be set:
Will the controller be in TURBO or FAST mode
(T/F)? (default=T)
Please answer 'T' or 'F' to fit your need.
Then, message will be shown on the screen:
Does the mainboard CPU have a 16-bit external data bus
(for examples,IBM 486 SLC2 ...) instead of 32-bit bus
(Y/N)? (default=N)
Please answer 'Y' or 'N' to fit the feature of the mainboard CPU.
******** Remove the Driver ********
If you want to remove the driver and recover to the original hard disk
device driver, please type the following command after the prompt #:
# removepkg
Some installed package name(s) will be shown on the screen. Please
choose "DC2000 UNIX Driver". The remove procedure will continue.
If you are running the SCO UNIX, please type the following commands to
shutdown and reboot your system:
# cd /
# shutdown -y -g0 -i6
+==============================+
| Trademarks Acknowledgement |
+==============================+
VESA is a registered trademark of the Video Electronics Standards
Association. VL-Bus is a trademark of the Video Electronics Standards
Association.
MS-DOS and Windows are registered trademarks of Microsoft Corporation.
PC, PC-AT and OS/2 are registered trademarks of IBM Corporation.
Xenix is a registered trademark of Santa Cruz Operation Corporation.
Unix is a registered trademark of American Telephone and Telegraph Corp.
Netware is a registered trademark of Novell Corporation.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
SIDE software diskette information
The following information is available in this README file:
* EZ-SCSI New Features
* EZ-SCSI Manual Installation
* EZ-SCSI CD-ROM Drive Support
* NetWare driver Information
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
EZ-SCSI NEW FEATURES
Adaptec EZ-SCSI v2.03 includes the following new features:
1. Supports single-session/multisession Photo CD drives*
2. Supports SCSI-2 compliant CD-ROM drives*
3. Includes Windows-based Photo CD Viewer application
4. Includes updated list of Third Party applications
5. Includes Windows-based CD Player, available in full size or mini
6. Supports Adaptec AIC-6360 based products
7. Supports "floppy" format on removable media disks
8. Includes Adaptec SCSI Group in Windows
* See list of supported drives below
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
EZ-SCSI MANUAL INSTALLATION
To manually install the EZ-SCSI files onto your hard disk, follow
this example:
c:\
md scsi
xcopy a:\*.* scsi
cd scsi
lha x ezscsi.lzh
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
EZ-SCSI CD-ROM DRIVE SUPPORT
The following drives have been tested by Adaptec with Adaptec
EZ-SCSI v2.03. All drives support both audio and data. Photo CD is
supported where indicated:
Firm-
Name Model ware SCSI Photo CD
---- ----- ----- ---- --------
Chinon * CDS 431 H48 1 single-session
CDS 435 M62 1 single-session
CDS 535 Q08 2 multisession
Denon * DRD 253 V 1 single-session
LMSI * CM 214 .12 1 single-session
CM 215 .13 2 multisession
NEC CDR 38 1 2 multisession
** CDR 55 1 1 multisession
* CDR 72 E 1 single-session
CDR 73 1.2 1 single-session
* CDR 74 1 1 single-session
CDR 74 1.0a 1 single-session
CDR 74-1 1 2 multisession
* CDR 84 1 1 single-session
CDR 84 1.0a 1 single-session
CDR 84-1 1 2 multisession
Panasonic 501 family 1.0B/C 1 single-session
Matsushita CR 532 2.0A 2 multisession
CR 532 2.5A 2 single-session
CR 533 1.1a 2 multisession
Philips CD-463 ? 2 multisession
Pioneer DRM 600 806 1 single-session
DRM 604X 2401 1 single-session
Sony CDU 541-01 2.6A 1 single-session
CDU 561 1.8K 2 multisession
CDU 561-31 1.8i 2 multisession
CDU 6211-10 2.6A 1 single-session
TEAC CD 50 1 2 multisession
Texel DM 3024 1.10 2 multisession
DM 5024 1.10 2 multisession
DM 3028 3.00 2 multisession
DM 5028 3.00 2 multisession
Shinaken 3021 1.04 1 single-session
Shinaken 5021 1.04 1 single-session
Toshiba TM 3301E 2162 2 multisession
TX 3401TA 2 2 multisession
TXM 3201A1 3332 1 single-session
XM 3101BME 3232 1 no
XM 3301B 272 2 single-session
* These drives do not directly support Photo CD. However, by adding
/XAEMUL to the ASPICD.SYS command line, in your CONFIG.SYS, we will
emulate support for single-session Photo CD on these drives.
** This drive does not support parity. Please consult the troubleshooting
section of the users manual for information on using this drive.
NOTE: The JVC XR-W1001 CD-ROM drive has temporarily been removed from
our list of supported CD-ROM drives.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
NetWare DRIVER INFORMATION ABOUT ASW-1240 v1.3
This disk contains Adaptec's NetWare solution for SIDE adapter.
The directory tree structure of this disk is as follows:
ROOT ══╦══ NET286.215
║
║
╠══ NET286.22
║
║
╠══ NET386.31
║
║
╚══ NET386.311
If required, please consult your DOS manual on how to move around the
directory tree.
Within a subdirectory, you will find a README.TXT file describing the
driver(s) contained in that subdirectory.
-----------------------------------------------------------------------------
This disk provides the following drivers:
1.) NetWare 286 v2.15 SCSI Disk Driver.
(\NET286.215)
2.) NetWare 286 v2.2 SCSI Disk Driver.
(\NET286.22)
3.) NetWare 386 v3.1 SCSI Disk Driver and ASPI Manager. Includes full
support for removable disk/optical drives.
(\NET386.31)
4.) NetWare 386 v3.11 and above SCSI Disk Driver and ASPI Manager. Includes
full support for removable disk/optical drives.
(\NET386.311)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=