 |
|
I. Overview
A. Release History
II. Functionality
A. Platforms Supported
B. Basic Functionaliy
1. Emulations
2. Connectors
3. File Transfer Protocols
4. Tools/User Interface
a. Attribute Mapper
b. Stylus Properties
c. Hotspot Editor
d. Macro Editor
5. Documentation/Help
C. Enhancements and Related Products
1. Client Options
III. Technical Specifications
A. Minimum Recommended System Requirements
B. Installation
1. General
2. Installation Procedure
3. Custom Installation Procedure
C. Registry Modifications
D. Directory Structure
E. Icons
F. Configuration/Initialization Files
This Technical Profile is intended to provide in-depth information about DynaComm Connectivity Series for
Windows CE (DCS/CE) features, specifications and configuration. Information in this document pertains to the
most current release of the product (see the Product Release History below).
DCS/CE is designed to provide users with the flexibility to integrate host mainframe and minicomputer systems
with a handheld PC-based Windows environment. Optional client emulation components including TN3270, TN5250,
Tandem 6530, HP700/94 and AT&T 4425 are fully integrated into the product when installed.
| |
| Version |
Release Date |
Release Status |
| DCS/CE 3.0.0.0 |
June 11, 1999 |
Latest Release |
| DCS/CE 2.0.0.0 |
September 15, 1998 |
Supported |
| DCS-H/PC 1.0.0.0 |
June 15, 1998 |
Supported |
|
|
Return to top
- Windows CE 2.11 and greater
Return to top
- ADDS VP/60
- ANSI BBS (ANSI, TTY and SCO ANSI extensions)
- AT&T 605/705
- Digital VT-52, 100, 101, 102, 220, 320 and 420
- TeleVideo 925/950
- Wyse 50/60
- Direct Serial
- Modem (TAPI)
- Telnet (TCP/IP)
Return to top
DCS/CE provides users with several tools to customize their workspace and automate common tasks.
| |
| Purpose: |
Allows users to create and save custom color maps which associate host character attributes to
local display colors. |
| Accessed via: |
Session: Properties: Emulations: Attributes |
| Configuration: |
Host character attributes are displayed with their current video characteristics. Users can modify
the foreground and background colors and assign display attributes such as Blink and Reverse Video. |
| Settings stored: |
Color maps are saved in the application subdirectory with the extension .acm. The name of the color
map assigned to the current session is stored in the corresponding session file under the [EMULATION] heading. |
| Defaults: |
Each emulation shipped with the Core Product or with Client Options has a default color map associated
with it. If the user wishes to use a different color map than the default, existing .ACM files can be
loaded from the Map File drop-down list box. |
| Scope: |
Color map settings apply only to the session for which they are selected. |
|
Return to top
| |
| Purpose: |
Allows the user to configure custom stylus or mouse click functionality which can be saved to a session file. |
| Accessed via: |
Session: Properties: Stylus |
| Configuration: |
The stylus can be set to: make box selection, make line selection, send character, select word, send word,
send selected text, move cursor to stylus point or perform light pen touch (IBM emulations only). These
tasks can be set to execute either with a single or double click of the stylus, with or without a modifier
key depressed. |
| Settings stored: |
All settings are stored in the session file in the application subdirectory. |
| Defaults: |
The display module provides the default settings for this option. |
| Scope: |
Stylus Properties settings apply only to the session for which they are selected. |
|
Return to top
| |
| Purpose: |
Allows the user to configure hotspots on the terminal screen. |
| Accessed via: |
Session: Properties: Emulations: Properties: Hotspots |
| Configuration: |
The user can select text that, when received from the host application, becomes a “hotspot” on the
terminal screen and is displayed as a button. Clicking the button with the mouse or stylus carries
out the associated action. |
| Settings stored: |
Hotspot files are saved in the application subdirectory with the extension .hot. The name of the
hotspot file assigned to the current session is stored in the corresponding session file under the
[EMULATION] heading. |
| Defaults: |
Each emulation shipped with the Core Product or with Client Options has a default list of commonly-used
hotspot strings. |
| Scope: |
Hotspot settings apply only to the session for which they are selected. |
|
Return to top
| |
| Purpose: |
Allows the user to construct macros to automate simple host tasks, such as automatic logon. |
| Accessed via: |
Session: Properties: General |
| Configuration: |
The macro editor provides an interface to walk the user through construction of a macro file by
listing all the available commands and prompting for parameters where necessary. |
| Settings stored: |
Macros are saved in the application subdirectory with the extension .mcr. The name of the macro
file assigned to the current session is stored in the corresponding session file under the [MACRO] heading. |
| Defaults: |
There are no defaults for the macro editor. If it is not needed, the macro.dll file can be deleted
from the installation to reduce the footprint. |
| Scope: |
Macro settings apply only to the session for which they are selected. |
|
Return to top
All DCS/CE documentation is available online. The following table lists the documents and the associated help
files, which are located in the DCS/CE installation directory.
Please Note: All help files are installed on the desktop PC only to help reduce the footprint on the handheld device.
| |
| Title |
Help File Name |
| DCS/CE Help |
DYNACE.HLP |
| AT&T 4425 Client Option Help |
ATT4425.HLP |
| HP 700/94 Client Option Help |
HP70094.HLP |
| Tandem 6530 Client Option Help |
TANDEM.HLP |
| TN3270 Client Option Help |
IBM.HLP |
| TN5250 Client Option Help |
IBM.HLP |
|
|
Return to top
DCS/CE has several Client Options—sold separately—which provide additional emulation and host connectivity
capabilities when installed with the DCS/CE Core Product. Currently available Client Options are outlined below.
Installation of a Client Option adds emulator and any required file transfer modules to the application subdirectory,
adds any necessary color and keyboard maps and adds the help files to the DCS/CE installation directory on the
companion PC. After installation, the new emulator/file transfer(s) are integrated into the product and are
available from the appropriate tab of the Session Properties dialog.
| |
| AT&T 4425 Client Option |
Provides AT&T 4425 terminal emulation. Online documentation is included in the file ATT4425.HLP.* |
| HP 700/94 Client Option |
Provides HP 700/94 terminal emulation. Online documentation is also included in the file HP70094.HLP.* |
| Tandem 6530 Client Option |
Provides Tandem 6530 terminal emulation and IXF file transfer. Online documentation is also included
in the file TANDEM.HLP.* |
| TN3270 Client Option |
Provides IBM 3270 terminal emulation, IBM 3287 printer emulation and IND$FILE file transfer
capability. Online documentation is also included in the file IBM.HLP.* |
| TN5250 Client Option |
Provides IBM 5250 terminal emulation and IBM 3812 printer emulation. Online documentation is also
included in the file IBM.HLP.* |
|
*NOTE: The help files are installed on the desktop PC, not on the Windows CE-powered device.
Return to top
-
DCS/CE currently supports the MIPS, SH3, SH4, StrongARM and Intel processors running Windows CE 2.11 and
greater. Additional processors will be added as the market dictates.
- 8 megabytes of RAM
- 8 megabytes of ROM (required with Windows-based Terminals)
Product installation sizes by processor type (in bytes):
| |
| Module |
MIPS |
SH3 |
SH4 |
StrongARM |
| DCS/CE Core Product |
2,434,000 |
1,879,504 |
1,880,528 |
2,004,432 |
| AT&T 4425 Client Option |
99,840 |
73,728 |
73,728 |
82,944 |
| HP 700/94 Client Option |
227,840 |
172,544 |
172,544 |
188,416 |
| Tandem 6530 Client Option |
385,536 |
281,088 |
281,088 |
310,784 |
| TN3270 Client Option |
330,376 |
269,448 |
269,960 |
286,856 |
| TN5250 Client Option |
349,320 |
283,784 |
284,808 |
298,120 |
|
Also note that macro.dll and kbmeditr.dll may be deleted from the installation if they are not required in
order to reduce footprint. In addition, any terminal emulations, file transfers and connectors that are not
required may be deleted, as described in section III B3.
Return to top
DCS/CE ships on seven 3.5 inch floppy diskettes.
The installation of DCS/CE performs the following main functions, in this order:
-
Checks the Registry to see if a previous version of DCS/CE is installed. If a previous version is found,
it launches the component install/uninstall SETUP program.
- Displays License Agreement and retrieves user registration data.
-
Allows the user to select a complete, compact or custom installation, and creates a new program directory
or lets user select existing directory.
- Prompts for a program folder name, and copies the user files.
- Prompts user for seven diskettes (if applicable).
- Modifies the Windows Registry (see below).
- Creates program folders and shortcut icons if selected by user.
- Displays the release notes if selected by user.
-
After installation of the DCS/CE Core Product to the desktop is completed, DCS/CE then downloads the
installation files to the Windows CE-powered device through Windows CE Services.
-
Windows CE Services asks the user to check the device to see if any further steps are necessary to
complete the installation.
Return to top
Below is a table showing the names of files that may be deleted when the corresponding connector, emulator,
tool or utility is not required. Deleting unnecessary files will free memory for other applications.
| |
| Connectors |
| Connector Not Required |
Delete this file |
MIPS* |
SH3* |
SH4* |
StrongARM* |
| Direct Serial |
comdir.con |
44K |
34K |
34K |
35K |
| Modem |
comtapi.con |
73K |
61K |
61K |
62K |
|
| |
| Emulators |
| Emulation Not Required |
Delete this file |
MIPS* |
SH3* |
SH4* |
StrongARM* |
| ADDS VP/60 |
addsvp60.emu |
52K |
39K |
39K |
44K |
| AT&T 605/705 |
att605.emu |
222K |
150K |
150K |
167K |
| TeleVideo 925/950 |
tv950.emu |
162K |
126K |
126K |
137K |
VT-Series and AT&T 605
(see note 2 below) |
vtseries.dll |
144K |
102K |
102K |
111K |
| VT-Series |
vt420.emu |
160K |
114K |
114K |
126K |
| Wyse 50/60 |
wyse.emu |
159K |
115K |
115K |
133K |
|
| |
| Tools/Utilities |
| Tool/Utility Not Required |
Delete this file |
MIPS* |
SH3* |
SH4* |
StrongARM* |
| Macros |
macro.dll |
50K |
39K |
39K |
40K |
| Keyboard Mapping |
kbmeditr.dll |
36K |
32K |
32K |
32K |
|
*File size in bytes.
Notes:
- ANSI-BBS is the default emulator. As such, this file should NOT be deleted.
-
The VT-Series and AT&T 605 emulation file (vtseries.dll) can be deleted ONLY if the VT-Series AND AT&T
605 emulations are not needed. This file is used by both VT-Series and AT&T 605 emulations.
-
With only the ANSI emulation and the Telnet connector installed, the smallest achievable file size is:
- MIPS CPU: 1,008,452 bytes
- SH3 CPU: 801,092 bytes
- SH4 CPU: 801,604 bytes
- StrongARM CPU: 837,444 bytes
NOTE: The MFCCE211.dll must be present for DCS/CE to operate. If it is not already installed on your device,
DCS/CE will automatically install it. The file size is:
- MIPS CPU: 537,428 bytes
- SH3 CPU: 392,019 bytes
- SH4 CPU: 392,019 bytes
- StrongARM CPU: 397,139 bytes
Return to top
DCS/CE modifies the Windows Registry as noted below. This information is provided for Application
Administration personnel, not the casual user. Since InstallShield is used for automatic installation
and uninstallation, users have no need for this detailed information.
[HKEY_CURRENT_USER\Software\FutureSoft\DCSCE]
Settings stored here include: Telnet hostname and port settings.
[HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES]
Session files (.ses) are registered with the Windows shell under these keys to create an association with DynaCE.EXE.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
Uninstall\DCSCEDeinstKey]
This entry stores the pointer to the DCS/CE Uninstall string (on the desktop PC).
Return to top
Return to top
| |
 |
DynaCE.EXE is the DCS/CE main executable. This executable can take existing session files
as command line parameters, launching the session at startup. By default, it is installed in
the Windows directory. |
|
Return to top
| |
| NAME |
TYPE |
DEFAULT LOCATION |
DESCRIPTION |
| Registry Entries |
Registry |
HKEY_CURRENT_USER\
Software\FutureSoft\DCSCE |
See Registry Modifications above. |
| *.ACM |
BINARY |
Application subdirectory |
User-defined attribute/color maps for a specified emulation. |
| *.CAB |
BINARY |
Installation directory
(on desktop PC) |
Uninstall files, used by Add/Remove Programs to properly uninstall Core Product or Client Options. |
| *.CAB |
BINARY |
Installation directory
(on desktop PC) |
Program files for a specific processor type. |
| *.HOT |
BINARY |
Application subdirectory |
User-defined hotspot files for a specified emulation. |
| *.KBM |
BINARY |
Application subdirectory |
User-defined keyboard maps for an emulation. |
| *.MCR |
BINARY |
Application subdirectory |
User-defined macro files. |
| *.SES |
TEXT |
Application subdirectory |
Session properties (connector, emulation, file transfer protocol, display, general, stylus). |
|
Return to top
|
|
