Release Notes: DynaComm Connectivity Series 9 Release Number: 9.0.0.0 Release Date: July 31, 2007 ================================================================================ Please review this document carefully before installing or running DynaComm Connectivity Series 9, release 9.0.0.0 (DCS 9). These notes contain last-minute product information that may affect your use of the product. ================================================================================ Contents This document contains the following sections: 1.0 Product Overview 2.0 New In DynaComm Connectivity Series 9, release 9.0.0.0 3.0 System Requirements 4.0 Notes on DynaComm Connectivity Series 9 5.0 Updated, Implemented or Fixed in This Release 6.0 Technical Support ================================================================================ 1.0 Product Overview These Release Notes include information relevant to DynaComm Connectivity Series, 9.0.0.0. * Key Features Multi-session capabilities; custom keyboard mapping; OLE compliance; custom toolbar editor; web-to-host connectivity; custom menu editor; ActiveX support; custom hotspot editor; standalone FTP component; event-driven scripting language; Euro symbol support; HLLAPI programming language support; URL user file addressing; Visual Basic(r) Interface (VBI) * Emulations Base Product: ADDS Viewpoint/60; TeleVideo 925/950; ANSI/TTY/SCO-ANSI; Digital VT 52/100/102/220/320/420; AT&T 605/705; Wyse 50/60. Client Options: AT&T 4425; IBM TN3270; HP 700/94; IBM TN5250; Tandem 6530 * File Transfers: Kermit; FTP; XYModem IXF (with Tandem 6530 Client Option installed); ZModem; IND$FILE (with TN3270 Client Option installed) * Connectors: Direct Serial; Telnet; Meridian LAT32; Trace Player; Modem (TAPI) SNA Server (with TN3270 Client Option installed) To view the latest information on any of the above, visit our web site: www.futuresoft.com ================================================================================ 2.0 New In DynaComm Connectivity Series 9, release 9.0.0.0 * New file version numbers In this release, DCS 9 and all add-on Client Option files have a product version of 9.0.0.0. Additional products have the following version numbers: - FutureSoft File Transfer Protocol (FTP): 1.0.0.7 - DynaComm Multi-user Administrator (DMA): 1.0.0.9 * SSH1 and SSH2 protocols. SSH1 is selected by default. SSH2 is selected through the configuration dialog. * Windows Vista operating system certification ================================================================================ 3.0 System Requirements 3.1 DynaComm Connectivity Series, 9.0.0.0 requires one of the following: - Windows 95/98 - Windows NT 4.0 (Workstation or Server) with Service Pack 4 or higher - Windows NT Server, Terminal Server Edition - Windows 2000 Professional - Windows 2000 Server - Windows XP Professional - Windows 2003 Server - Windows Vista 3.2 Client Options All add-on Client Options require installation of the DCS 9 base product. ================================================================================ 4.0 Notes on DynaComm Connectivity Series 9 and all add-on Client Options 4.1 General 4.1.1 Starting DCS 9 from a command line. When starting DCS 9 from a command line, a file may be specified by using local pathing or URL addressing (session [.SES] files only). Verify the proper extension is included in the file name as follows: .SES (session), .DCM (memo), .DCP (script), or .DCT (compiled script). 4.1.2 Re-opening a saved session that was inserted into Wordpad. Saving a document with an embedded session file (whose session properties have been changed) or saving an embedded session file (whose session properties have been changed) does not save the changed session properties to the embedded file. 4.1.3 Using custom fonts on a Windows 95 system. In certain situations, using custom fonts on a Windows 95 system will not allow DCS 9 to display/update the screen in order to print the user- defined fonts. This is caused by a random failure of the API call to Microsoft's StretchBlt() routine. Workaround: If this occurs on your system, resize the screen (Click Minimize then click Maximize) to display the data correctly. This occurs only on Windows 95 systems. Windows NT systems are not affected. 4.1.4 Session file compatibility. All session files created in DCS 7.1.0.2 and up are compatible with DCS 9. However, session files created in DCS 9 cannot be used in DCS 7.1.0.4 and earlier. 4.2 Documentation * DCS 9 technical library includes the following: - DCS 9 Online References Master (contents.chm) - DCS 9 Administrator Online Reference (admnref.chm) - DCSeries Online Reference (dcseries.chm) - FTP Online Reference (fsftp32.chm) - HLLAPI Online Reference (hlapcnfg.chm) - Script Language Online Reference (script.chm) - Visual Basic Online Reference (vbclient.chm) - Getting Started for Users (gs.pdf) - Getting Started for Administrators (gsadmin.pdf) - Script Language Reference (scriptref.pdf) - Getting Started: Using DCS 9 Web with VB and Microsoft FrontPage (Getting Started.doc) - DCS 9 Readme (readme.txt) * Only the Online References are installed. However, any reference can be removed during the install process. * All items are provided on the installation CD-ROM in the /documentation folder. * The most current documentation is available for download 24 hours a day, 7 days a week from the FutureSoft web site at: www.futuresoft.com/documentation. * Send any documentation questions, errors or corrections to docs@futuresoft.com. * Printed documentation can be obtained by contacting your FutureSoft Account Manager at 1-800-989-8908. 4.3 Installation/Setup/Uninstallation 4.3.1 Program group name change with DCS 9. DCS 7.1.0.4 and earlier versions are installed under the program group name of "DCS" or "DynaComm Connectivity Series". The program group name has been changed to "DynaComm Connectivity Series 9". To avoid possible version incompatibilities, uninstall any DCS 7.1.0.4 or previous version of DynaComm Connectivity Series before installing DCS 9. If you install DCS 9 without removing a prior version, both program group names are shown. During an uninstall an error message may appear that states that the uninstall program cannot unregister certain files. This occurs due to a timing issue of the uninstall processes. Continue by clicking OK. The unistall will complete successfully. 4.3.2 Installation methods cannot be mixed. As an end user installing DCS 9 and any client options, you must use the same installation method for the DCS 9 base product, any Client Options, and any additional products. You cannot install some components with one install method and then install other components with a second install method. 4.3.3 Evaluation version installs An evaluation copy is good only for 15 days after the first date of installation. If you need to extend the evaluation period or you receive an error message during an evaluation version install, call your FutureSoft Account Manager at 1-800-989-8908. 4.3.4 Windows 95 Installation Requires Files Supplied With IE5.0 Windows 95 users who do not have Microsoft Internet Explorer 4.0 (IE5.0) must run an additional installation program, DCOM, that contains updated DCOM extensions. Without these extensions, originally supplied by Microsoft, the FS-FTP application and the HLLAPI Auto Launch Configuration Windows 95. When attempting to run HLLAPI Auto Launch Configuration you may receive the error message 'The HLAPSYS.EXE file is linked to missing export ole32.dll:CoResumeClassObjects' To download the latest copy of DCOM, access www.microsoft.com, search for DCOM, request a download. 4.3.5 Command-line options for installing DCS 9. The following command line arguments may be used when installing DCS 9: setup -r Causes SETUP.EXE to automatically generate a silent installation file (.ISS file), which is a record of the installation input, in the Windows folder. 4.3.6 Older versions of shared files. DCS 9 may require newer versions of some files to run correctly. If DCS 9 encounters older shared files during installation, a Question dialog box appears asking if you would like to replace the existing file with the newer copy. Click Yes. The installation program places a copy of the old file in the Shared directory with the same name as the original file. In the event that the newer version of the shared file interferes with your existing software, the older version of the file is still available for your use in the Shared folder. 4.3.7 Individual Methods * Standard Install. DCS 9 can be installed over any version of DCS 9. * DCS 9 Web Server Edition Install. DCS 9 Web server can not be installed over any currently installed version or type of DCS. You must first remove any previous version or type of DCS before installing DCS 9 Web server. DCS 9 Web Server installation allows for selecting all software options that are to be installed in one setup process. Individual Client Options can be installed later, if needed. However, if one Client Option is selected for installation, the base product is automatically selected for installation. * DCS 9 Web Software Development Kit (SDK) Install. DCS 9 Web SDK can not be installed over any currently installed version or type of DCS. You must first remove any previous version or type of DCS before installing DCS 9 Web SDK. DCS 9 Web SDK installation installs the base product and all Client Options in one setup process. There are no separate selections for installing Client Options. 4.4 User Interface 4.4.1 Common dialog boxes may resize. In Windows 98 and Windows 2000, the display function for dialog boxes retains the last-used sizing parameters such that the same values may be applied to the next dialog displayed. This results in the apparent automatic enlargement of small dialog boxes to a larger size. You may see this behavior with dialog box sizes in DCS 9. 4.4.2 Toolbars extend to the right of the application window. When new toolbars are displayed in the application window, they are added to the right of existing toolbars as long as any space exists in the toolbar display area. Toolbars that extend beyond the right edge of the application window can be either a) dragged off the toolbar display area or b) made into a vertical toolbar (Shift+drag). 4.4.3 Session display appearance. A session displays a terminal screen only after a connection is attempted. Therefore, a session window will appear empty if: 1) A saved session is opened, but the session was saved with the Auto Connect option disabled. In this case, the terminal screen appears only after a connection is attempted, or 2) A new session is configured with the Auto Connect option disabled. In this case, the terminal screen appears only after a connection is attempted. The terminal screen remains on display after a session is disconnected. This situation is documented in the script.hlp file in the Display topic. 4.4.4 File Send and File Receive buttons and menu items. Although these buttons and menu items are activated when a session is connected, DCS 9 will only display the file selection and setup dialogs when the host has been prepared to send or receive files. 4.4.5 Using custom fonts on a Windows 95 system. In certain situations, using custom soft fonts on a Windows 95 system will not allow DCS 9 to display/update the screen in order to print the user-defined fonts. This is caused by a random failure of the API call to Microsoft's StretchBlt() routine. Workaround: If this occurs on your system, resize the screen (Click Minimize then click Maximize) to display the data correctly. This occurs only on Windows 95 systems. Windows NT systems are not affected. 4.5 Utilities 4.5.1 Dialog Editor. The Dialog Editor is no longer included in the DCS product. However, you may download an "As Is" version from the FutureSoft BBS by: a. Telnet: Choose the ANSI emulation, select a Winsock Connection and connect to bbs.futuresoft.com or use the following IP Address: 199.165.143.17. b. Modem: Choose the ANSI emulation, select your modem and dial 281-588-6870. 8 databits, 1 stopbit, no parity. 4.5.2 Problems noted with map files. Implementation of a new feature revealed a compatibility issue between DCS 7.1.0.3 and DCS 9. Users who have a current installation of DCS 7.1.0.3 and upgrade to DCS 9 may receive error messages when an attempt is made to open certain map files for the following emulations: - AT&T 605/705 - attribute map files; TV 925 - attribute map files; - Wyse 50/60 - hotspot map files; HP 700/94 - all map files. 4.6 Emulations 4.6.1 AT&T 4425: Removing the AT&T 4425 Client Option. The AT&T 4425 Client Option does not have a separate uninstall program. To remove this client option, run the DCS 9 Setup program, select Modify on the Welcome screen, and uncheck the AT&T 4425 component on the Select Components screen. 4.6.2 HP 700/94: Removing the HP 700/94 Client Option. The HP 700/94 Client Option does not have a separate uninstall program. To remove this client option, run the DCS 9 Setup program, select Modify on the Welcome screen, and uncheck the HP 700/94 component on the Select Components screen. 4.6.3 IBM TN3270 * IND$FILE (CMS mode): Note for application programmers. When sending TN3270E data, if the data byte value is 0xFF, another byte of 0xFF needs to be added to your data stream so the gateway knows the byte 0xFF is data and not a Telnet command. * Model number cannot be changed while connected. Changing the model number while connected to a host would change the presentation space and place the host and emulation out of sync in terms of the presentation space. Therefore, the model number specified in the Session Properties dialog cannot be changed while an IBM TN3270 session is connected. * Removing the TN3270 Client Option. The TN3270 Client Option does not have a separate uninstall program. To remove this client option, run the DCS 9 Setup program, select Modify on the Welcome screen, and uncheck the TN3270 component on the Select Components screen. 4.6.4 IBM TN5250: Removing the TN5250 Client Option. The TN5250 Client Option does not have a separate uninstall program. To remove this client option, run the DCS 9 Setup program, select Modify on the Welcome screen, and uncheck the TN5250 component on the Select Components screen. 4.6.5 Tandem 6530 * Audible alarm must be supported by hardware. Your hardware must support an audible alarm or sound for Ring Bell at Column on the General tab to produce an audible alarm. * Automatic scrolling to the cursor location. The Auto Scroll to Cursor on the Displays tab does not apply to the Tandem 6530 emulation. The session automatically scrolls to the current cursor location. * Clicking on selected text does not deselect it; clicking on scrollbar after selecting text deselects it. This is the default behavior of the mouse buttons. In the Properties dialog for the session, modify the selections on the Mouse tab to reconfigure it. * Field mark is displayed in the same color as field. In some applications, the attribute that marks the beginning of a field will be displayed in the same color as the field. This may be confusing since the field will appear to accept data only from the second field position onward, when it is, in fact, at the start of the field. Workaround: Use the attribute editor to change all attributes containing Underline to match the background color of the rest of the application. Note: Before you can change the attributes, you must disable the option to "Allow host to change the colors" on the General tab in the Session Properties Tandem 6530 Emulation dialog. * History buffer. Tandem 6530 systems do not use a history buffer in Conversational Mode; therefore, history buffer settings do not apply for the DCS 9 Tandem 6530 emulation. Use the vertical scroll bars to view all data that is stored on other areas of the page. * IPX/SPX does not terminate after logging off under Windows NT. After logging off, a connection will not automatically terminate immediately in a Windows NT environment (it must time out). To close the connection immediately, select Disconnect from the Session menu. * Removing the Tandem 6530 Client Option. The Tandem 6530 Client Option does not have a separate uninstall program. To remove this client option, run the DCS 9 Setup program, select Modify on the Welcome screen, and uncheck the Tandem component on the Select Components screen. * Status line options are reset between connections. The top and bottom status lines are reset to their default states (disabled and enabled, respectively) between connections. 4.7 Connectors 4.7.1 Modem Connector. The default properties of the Modem connector are determined by the configuration of the Windows system-level modem properties. These system-level properties are configured via the Modems settings in the Windows Control Panel. Changes made at the system level will affect the options available within DCS 9. However, changes made within DCS 9 do not affect the system-level properties. For example, making changes to the properties of a telephony device listed in the Modem connector will not affect the properties of that device at the system level. Because other applications must have access to these properties, Windows does not allow any one application to make permanent changes to these properties which may affect other applications. Furthermore, such changes cannot be saved to a DCS 9 session file. To make permanent changes to the modem properties for a session that uses the Modem connector, you must make and save the changes via the Modems area of the Windows Control Panel. This is in accordance with TAPI compliance. Information in the Phone Number drop-down list box is not removed, even if these are changed at the system level. The settings of the Modem connector cannot be configured or obtained via script. Removing a telephony device via the Systems area of the Windows Control Panel will not be reflected in the Telephony Devices list of the Modem connector. 4.8 File Transfers 4.8.1 Tracing sessions involving file transfers. Tracing a file transfer will capture the transferred data. It is best to use a hex editor to examine the captured data. Avoid using the trace facility to replay a file transfer. If this is not possible, when replaying a traced session that includes a file transfer, observe the following when working with trace sessions: - Do not send files in small packet sizes. - Automate the transfer as much as possible (for example, do not select Prompt in the If file exists group on the General sub-tab of the Session Properties dialog for all file transfer protocols). - When replaying the trace, all user responses which were recorded must be repeated with identical user responses during the trace. If a different response is given, the trace will not replay correctly. - Replaying the file transfer correctly may not be possible if any element of the file transfer has changed. 4.9 Printing 4.9.1 Log to Printer option in 132-column mode. When using the Log to Printer option in 132-column mode, your output may appear incorrect. The Log to Printer option simply dumps the text from the host to the printer and does not include text attributes. In addition, the same size font is used for both 80- or 132-column modes. To print text with attributes and font information, you must select a text area with the mouse and set the attributes. 4.9.2 Print Screen/SysRq key cannot be mapped for TN3270 and TN5250 emulations. The Print Screen/Sys Rq key cannot be mapped to a function with the Keyboard Mapper. The system will allow you to use the mapping procedures with this key. However, the key will not perform the mapped functions when accessed. 4.10 Scripting 4.10.1 Creating a DCS 9 session with a DCS 9 script. All properties must be explicitly set for the session with the appropriate script command. These commands include the following: APPCONFIG, DISPLAYCONFIG, GENERALCONFIG, CONNCONFIG, EMULCONFIG, XFERCONFIG. 4.10.2 Using Kermit commands with FSIEvent. If Kermit commands are used with FSIEvent, the Kermit FINISH command must be used to end the script. If the Kermit FINISH command is not used, two conditions exist: 1) Kermit commands in the script will appear to not have been executed. 2) Session control is not returned. The commands are actually being executed as written. However, it is true that session control is not returned. Therefore, the FINISH command must be used for correct script execution to occur. 4.10.3 Using extensions for file names coded in scripts. When coding the name of a file as part of a script command or function, be aware that your Windows settings may interfere with the script's ability to locate the file. If your Windows file settings are set to hide extensions, then the file name in the script should not include an extension. This problem occurs primarily with functions such as WindowHnd () which attempt to retrieve information (such as a window handle) based on the name shown in the window title bar. A good coding practice is to use an error-checking routine to verify that the value returned by such a function is not zero, and if it is, to execute a second function with a different window title name. In this case, check once for the filename without an extension, and the second time check with the extension added. See the first two lines of Example 2 in the information on When and Wait below. 4.10.4 Changing menu structures when multiple windows are open. If you change the menu structure via script when multiple windows are open, the list of open windows which appears under the Windows menu will not list any windows until a new window is opened or the active window changes. 4.10.5 Commands * ConnConfig This command cannot be used to configure the Modem connector. To configure a modem via script, you must use the Direct Serial connector. * Connect() This function will always return a value of TRUE for the Direct Serial and Modem connectors, even when the session is not connected to a host. Both of these connectors interact with local hardware (a COM port), and will return a value of TRUE as long as they have established a connection to the COM port. To determine if you have established a connection to a host when using these connectors, create a routine using the Send command (to send data to the host) followed by one of the When commands (to determine whether the host responded). * Display The Display command does not send strings to the host; it only displays text in the session window. However, unlike previous versions of DCS 9, the Display command now works only with connected sessions. Use the Send command to send a string to a host. * File Decrypt This command is not backward compatible with versions of DynaComm Connectivity Series prior to DCS 7.0.0.0. * File Delete File names cannot contain wildcard characters. * File Encrypt This command is not backward compatible with versions of DynaComm Connectivity Series prior to DCS 7.0.0.0. * GetConnConfig() This function cannot be used to obtain the settings of the Modem connector. To obtain settings for a modem connection via script, the session must use the Direct Serial connector. * Send When using metakeys (text enclosed in braces {}) the only valid strings are those listed in the terminal keys area on the Terminal tab in the Keyboard Mapper. These strings apply only to the specific emulation. Additional keys may be added in the future. The optional coordinates for the Send command only work with emulations that support block or page modes, such as TN3270 and TN5250. Cursor positioning coordinates are ignored by other emulations. * When and Wait The DCS 9 architecture uses parallel processing for scripting operations and input/output operations. Therefore, it is possible that a script may send data to and receive data from a host before the script has executed a subsequent Wait or When command (causing the script to hang). For best results, place When commands and routines earlier in the script sequence of execution. Example 1 %hwnd = active() when string "elvis" window %hwnd resume *loop send "" window %hwnd wait resume beep 1 goto loop cancel In Example 1, the When String command has been established before the request for data. This ensures that the data cannot arrive before the script is in a state to check for the data. Example 2 %hWnd = WindowHnd ("Bbs.SES") if %hWnd = 0 %hWnd = WindowHnd ("Bbs") ; note: if the Window Handle is still zero at this point, the script will not work when string 1 "new" window %hWnd resume when string 2 "password" window %hWnd resume when string 3 "(C)ontinue" window %hWnd resume connect %hWnd wait resume send "user name" window %hWnd wait resume send "password" window %hWnd wait resume send "" window %hWnd when cancel string cancel In Example 2, all When String commands have been established before sending data and waiting for the host to respond. Again, this ensures that the data cannot arrive before the script is in a state to check for the data. 4.10.6 Removing the Script Language In this release, the Script Language can be removed as a separate component from the base DCS 9 product but does not have a separate uninstall program. To remove this component, run the DCS 9 Setup program, select Modify on the Welcome screen, and clear Script (under Programming) on the Select Components screen. Note: Certain portions of the script language are required by the VBI. These items are noted with a grayed check mark and will not be removed unless you also choose to remove the VBI. 4.11 Visual Basic Interface (VBI) 4.11.1 Installation The files for the interface are installed under the root directory of the current installation of DynaComm Connectivity Series 9. To install the Visual Basic Interface: 1. Start DCS 9. This registers the FSIEVENT.OCX file. You must start DCS 9 at least once before you can use the component. 2. Start Visual Basic(r) and add the FSIEVENT.OCX to the project Component Toolbox. You may also add the Constants Definition file, DCSCONST.BAS, to your project if desired. This file defines constants that can be used as parameters in command and function arguments. 3. Select the DCS 9 component and drag it onto the project form. The type library is now automatically included in the project. 4.11.2 Removal In this release, the Visual Basic(r) Interface can be removed as a separate component from the base DCS 9 product but does not have a separate uninstall program. To remove this component, run the DCS 9 Setup program, select Modify on the Welcome screen, and clear VB (under Programming) on the Select Components screen. ================================================================================ 5.0 Updated, Implemented or Fixed in This Release * Implemented - SSH2 protocol * Updated - DCS 9 has been certified as an application for use on the Windows Vista operating system ================================================================================ 6.0 Technical Support For prompt and effective service, please be sure to include your company name, address, any applicable phone (or fax) numbers, name and version number of the product for which you need support. The following technical support options are available: * E-mail: support@futuresoft.com * Telephone: Monday through Friday between 08:00 and 17:00 Central Standard Time (CST) 1.281.588.6868 * FAX: 1.281.496.1090 * Ground Mail: Technical Support Services 12012 Wickchester Lane, Suite 600 Houston, Texas 77079-1222 * FTP (files): ftp.futuresoft.com. ================================== END ========================================= Copyright 2007 FutureSoft, Inc. readme.txt DCS 9000 September 28, 2007 sac