=================================================================

                        EXTRA! for Windows
                           Version 4.0
                          Release Notes
=================================================================

Copyright 1989-1994 by                   Attachmate Corporation
Attachmate Corporation                   February 1994
All rights reserved


------------
INTRODUCTION
------------

This file contains late-breaking information pertaining to this 
release of EXTRA! for Windows. Please be certain to read the 
important message below concerning the installation of this 
product.


--------------------------------------------
IMPORTANT INFORMATION REGARDING INSTALLATION
--------------------------------------------

WE RECOMMEND THAT YOU REMOVE ANTI-VIRUS SOFTWARE BEFORE INSTALLING 
EXTRA! FOR WINDOWS. SEE YOUR ANTI-VIRUS SOFTWARE DOCUMENTATION FOR 
INSTRUCTIONS. YOU MAY RE-INSTALL YOUR ANTI-VIRUS SOFTWARE AFTER 
EXTRA! IS INSTALLED.

IF YOU ARE GOING TO INSTALL EXTRA! FOR WINDOWS AND HOST
GRAPHICS OPTION FOR WINDOWS YOU MUST INSTALL EXTRA! FOR
WINDOWS FIRST.  

WE DO NOT RECOMMEND EGA SCREEN RESOLUTION FOR THIS PRODUCT.
            

Listed below are the main topics covered in this file:

*IPX/SPX to the Novell SAA      *DLC to IBM PCOM Gateway
 Gateway or IPX to the          
 Attachmate Gateway

*Virtual DLC Device Driver      *DLC and Communication Check
                                 Reminder 510

*Configuration Considerations   *Running Windows in Standard 
                                 Mode          

*Dedicated LU Support in        *Host Type Ahead 
TN3270 

*Keyboard Information           *Turkish Font Support          

*Light Pen Support              *OS/2 (2.x) and EXTRA!          

*Printer Emulation              *DOS HLLAPI Tunnel              

*RTM EXTRA4W.INI Parameter      *EXTRA! BASIC Language          

*Sample Macros                  *Contest


--------------------------------------------------------------
IPX/SPX TO NOVELL'S SAA GATEWAY OR IPX TO ATTACHMATE'S GATEWAY
--------------------------------------------------------------

If you connect via IPX/SPX to Novell's SAA Gateway or via IPX to the
Attachmate Gateway, you now need to have a copy of Novell's file
NWIPXSPX.DLL in your WINDOWS directory.  If you do not 
have a copy of this file available, please contact Attachmate
and we can make it available to you.

For IPX connections to the Attachmate Gateway, you no longer need
to use the TSR IPXINTFC.COM. IPX connectivity now uses NWIPXSPX.DLL 
and VIPX.386 (provided by Novell).  Remove IPXINTFC.COM from your 
AUTOEXEC.BAT.

If you are using either of these connectivities in Windows 3.1 
standard mode, you need to load the Novell TSR TBMI2.COM before 
you load Windows. TBMI2.COM should be available in your Novell 
directory. For additional standard mode requirements, see the 
section below, "Running Windows in Standard Mode."


------------------------------------------
DLC TO IBM PERSONAL COMMUNICATIONS GATEWAY
------------------------------------------

If you connect via DLC to an IBM Personal Communications 
Gateway (PCOM) version 1.1, you must select the PC3270 gateway option 
in the DLC configuration dialog box. For versions of the PCOM gateway 
later than 1.1, do not select the PC3270 option.


-------------------------
VIRTUAL DLC DEVICE DRIVER
-------------------------

VATMDLC.386 is a new virtual device driver for EXTRA! for Windows that 
allows you to connect to the host via a token-ring DLC connection. This 
Windows driver replaces the DOS TSR (terminate and stay resident) 
driver (DLCINTFC.EXE) that you formerly needed to run with EXTRA! for 
Windows. When Windows is running in enhanced mode, except for a 
few specific situations (such as running EXTRAWIN under Windows 
standard mode), we suggest that you use VATMDLC.386 instead of 
DLCINTFC.EXE.


VATMDLC.386 and DLCINTFC.EXE
----------------------------

Both of these drivers interact with a DLL that EXTRA! uses for DLC 
connections. This DLL (ATMDLC.CDD) is compatible with both 
VATMDLC.386 and DLCINTFC.EXE. However, some changes have been 
added to ATMDLC.CDD for VATMDLC.386. Therefore, you must use the 
most recent copy of ATMDLC.CDD if you are also using VATMDLC.386.
If you are using the VATMDLC.386 driver, do not run DLCINTFC.EXE. 
If you do, then VATMDLC.386 will detect the other program and won't 
load. If you do want to use VATMDLC.386, make sure you remove 
DLCINTFC.EXE from any batch files (such as the AUTOEXEC.BAT) that 
might run it automatically.


Loading VATMDLC.386
-------------------

When you configure for DLC, EXTRA! makes some modifications to 
your SYSTEM.INI file.  In the [386Enh] section, the following line 
is added:

   device=C:\EXTRAWIN\VATMDLC.386

where EXTRAWIN is the program directory for EXTRA!.  In addition, a 
new section is added called [Vatmdlc].  This section contains 
parameters used by VATMDLC.386.  EXTRA! automatically chooses 
parameters that should be appropriate for your configuration.

You will be prompted to restart Windows for the changes made to 
SYSTEM.INI to take effect.


----------------------------------------
DLC AND COMMUNICATION CHECK REMINDER 510
----------------------------------------

If your workstation is connected via DLC to the Host and the 
Physical Unit drops, the EXTRA! Operator Information Area (OIA) 
will display a Communication Check Reminder 510 indicating loss 
of communication with the host.  At the same time, the 
Condition of Connection field will be set to all blanks.  
If, however, you send a SYSREQ (System Request) to the host, 
a stick man will appear in the Condition of Connection field.  
This is an incorrect status and will be corrected in a later 
update.  


----------------------------
CONFIGURATION CONSIDERATIONS
----------------------------

If you change a terminal or printer session configuration and then 
start the same session using the following procedure, your changes 
will not be reflected in the open session:

1) Using EXTRA! Configurator, you edit a session, but do not save 
   the changes.

2) Using EXTRA! Terminal or EXTRA! Printer, you open the session 
   that you just edited.

To avoid this problem, save the configuration before opening the 
session from the EXTRA! program group. Or, simply open the edited 
session from the EXTRA! Configurator.

Note also that if you save a configuration but have an incorrect 
EXTRA! path in your WIN.INI file, the configuration will appear
to have been saved successfully, but will not be saved.

IBM ThinkPad Configuration
--------------------------

EXTRA! for Windows require that you use IBM Token ring drivers for 
DLC Connectivity with an IBM ThinkPad.  If you are having trouble 
configuring the IBM token ring adapters, here is a sample 
config.sys that you might want to refer to. 

(Please Note that there are assumptions made about the drive and 
path for the drivers and these should be modified by you in accordance 
with your thinkpad's directory structure.  Further it is assumed that 
the Shared RAM for the token ring adapter starts at 0xC8000.  This 
might be different in your case and should be adjusted accordingly.)

REM ******************************************************************
REM EMM Driver and version driver.  Remember to *EXCLUDE* 
REM the shared RAM
REM ******************************************************************
DEVICE     = C:\WINDOWS\EMM386.EXE NOEMS X=C800-D1FF
DEVICEHIGH = C:\DOS\SETVER.EXE
REM ******************************************************************
REM IBM Thinkpad Drivers
REM ******************************************************************
DEVICEHIGH = C:\THINKPAD\IBMDSS01.SYS /S0=2
DEVICEHIGH = C:\THINKPAD\IBMDOSCS.SYS
DEVICEHIGH = C:\THINKPAD\DICRMU01.SYS /MA=C800-D1FF
DEVICEHIGH = C:\THINKPAD\$ICPMDOS.SYS
REM DEVICEHIGH = C:\IBMAUDIO\AUDIODD\TPAUDDD.SYS
REM ******************************************************************
REM IBM Token Ring Lan Support Drivers
REM ******************************************************************
DEVICEHIGH = C:\THINKPAD\CS20TOK.SYS RS=4 MMIO=CC00 IRQ=9 SRAM=C800,16
DEVICEHIGH = C:\LSP\DXMA0MOD.SYS 001
DEVICEHIGH = C:\LSP\DXMC0MOD.SYS N ,C800,0,0,0
DEVICEHIGH = C:\LSP\DXMT0MOD.SYS  ES=2 EST=2 O=Y


--------------------------------
RUNNING WINDOWS IN STANDARD MODE
--------------------------------

If you are running in Windows 3.1 Standard mode, you must 
manually install E4WTIMER.EXE (a standard mode device 
driver) by including it in your AUTOEXEC.BAT file and 
rebooting..
 
This driver allows your communications line to remain active when 
you shell out to DOS, or do task-switching with another DOS 
application.
 
This driver remains in your workstation's memory even if you are 
not using EXTRA!. If you need to unload E4WTIMER.EXE to save 
memory, exit to DOS and type the following command:

  path\E4WTIMER /U            ;path=the path to the directory
                              ;containing your EXTRA! files


------------------------------------------
DEDICATED LU SUPPORT IN TN3270 CONNECTIONS
------------------------------------------

Additional enhancements have been made to the TN3270 configurator 
that will allow you to customize the Terminal Type negotiation 
string to include a specific host resource (logical unit).  
Note that this feature only applies to TN3270 servers that 
support this ability (e.g., the Open Connect Systems (OCS) 
Gateway).

From the Terminal Type drop-down list box in the Resource dialog 
box, select from Terminal Type IBM-3278 or IBM-3279 then edit 
the field to reflect the syntax below:

IBM-327x-model_type[-E][@luname]

where:

x indicates the terminal type

-model_type indicates the screen size (model 2, 3, 4, or 5)

-E is an optional parameter that specifies Extended Attribute 
Bytes

@luname is an optional parameter that specifies an LU name 
defined on the TELNET server. The name, found in the logmode 
definitions of the LU, can be up to eight characters in length.

Note that if either the model screen size or terminal type do not 
match the LU characteristics as defined on the TELNET server, 
the terminal type negotiations will fail.  Also, if the model 
screen size in the custom terminal type negotiation string does 
not match the one specified in the Add Session or Edit Session 
dialog box, EXTRA! will not display the correct model screen 
size.


---------------
HOST TYPE AHEAD
---------------

When running a session in coax CUT mode, the host type ahead 
feature is not available; in CUT mode the controller has control
over keystrokes.


---------------------
KEYBOARD INFORMATION        
---------------------

Using a Key Tronic 122-Key Keyboard
-----------------------------------

To use the Key Tronic 122-key keyboard, Windows must be set up 
to support its "All AT type keyboards (84-86 key)" keyboard 
driver. Run Windows' Setup program if it is not configured 
for this driver.

You must also configure EXTRA! for the "Key Tronic 3270/PC
Attachmate Map."

If your Key Tronic 122-key keyboard starts beeping, or some
keys stop working, add the following line to your WIN.INI file.

    TypeAhead=2047

Put this line in the [Windows] section of the file, right after 
the KeyboardSpeed line.

The TypeAhead parameter sets the size of a queue used by Windows.
This queue temporarily holds information such as keystrokes, 
error messages, and mouse activity. The setting we suggest 
(2047) uses approximately 30K of memory.

IMPORTANT: Do not set the Typeahead parameter to a value greater 
than 2047. This is the maximum size to which the queue can be 
set in Windows.


Using an IBM PS/2 Host-Connected 122-Key keyboard
-------------------------------------------------

To use the IBM PS/2 Host-Connected 122-key keyboard, install the
Windows driver supplied by IBM with the keyboard.  Configure
EXTRA! for the "IBM PS/2 Host connected 122 key keyboard."


--------------------
TURKISH FONT SUPPORT
--------------------

For complete Turkish font support, you will need to order the 
Turkish Font Disk, part number 110802.40.  Contact your local 
Attachmate Sales Office for details.


-----------------
LIGHT PEN SUPPORT
-----------------

The Light Pen Support function is only available if you are
using a DFT connection to communicate to the mainframe.


---------------------
OS/2 (2.X) AND EXTRA!
---------------------

To run EXTRA! for Windows in the OS/2 (2.x) environment you must 
first configure the virtual DOS machine. To do this follow the 
instructions below.

1. Highlight the DOS icon with your left mouse button, then with 
   your right button, click once to bring up the icon menu.

2. Click once on the Open arrow then click on Settings. This brings 
   up the configuration screen.

3. Select the Session tab to view the WIN-OS/2 Settings box. 
   (If the Settings box does not appear on your screen, check to 
   see if the WIN 0S/2 Full Screen radio button is selected. Click 
   the WIN-OS/2 Settings box to view the configuration settings 
   menu.

4.  Make certain that the settings have the proper values assigned 
    as listed below.

         Setting               Value
         -------               -----
    DOS_background_execution   On
    DOS_device                 LAN support program (DLC, NetBIOS)
    DOS_high                   Off
    DOS_lastdrive              Users last local logical drive (A-Z)
    HW_ROM_TO_RAM              On (performance boost)
    IDLE_sensitivity           100%


-------------------------------
PRINTER EMULATION:  PAGE LAYOUT
-------------------------------

If you want to change the amount of text printed on each page, we
suggest you choose Page Layout from the Options menu of the Printer
Emulator.  Select values for the Characters Per Line and Lines Per 
Page fields, then click on the Select Best Fitting Font button.  
EXTRA! will choose the font that provides the nearest match with 
your choices.


-----------------
DOS HLLAPI TUNNEL
-----------------

HLLAPI applications that were written for the DOS version of 
EXTRA! can run under Windows using the "DOS HLLAPI Tunnel," 
HLLSERV.EXE (located in the \EXTRAWIN directory). This program 
displays an icon on the bottom of the screen to indicate that 
it is running in the background.


-------------------------------------------
RESPONSE TIME MONITOR EXTRA4W.INI PARAMETER
-------------------------------------------

The HostRTM EXTRA4W.INI parameter documented in Appendix A 
of the EXTRA! for Windows User's Guide is not supported.  The 
HostRTM parameter setting can be present in your EXTRA4W.INI 
file, but will be ignored by EXTRA!. 


---------------------------------
EXTRA! FOR WINDOWS BASIC LANGUAGE
---------------------------------

The Wait and WaitHostQuiet Functions
------------------------------------

The Wait function documented in the EXTRA! for Windows BASIC 
Language Reference Manual is not supported. The original Wait 
functionality has been added to and enhanced in the WaitHostQuiet 
function with the addition of two new parameters. The new syntax 
for WaitHostQuiet is:

rc% = WaitHostQuiet(SettleTime%, TimeOut%)

where:

rc% is the return value.

SettleTime% is the amount of time, in milliseconds, that the 
function waits from the time the X() clock remains absent from 
the OIA on the host screen until the function returns. (Note 
that 1000 milliseconds is equal to one second.)

TimeOut% is the amount of time, in seconds, that the function 
will wait for the X() clock to disappear. After TimeOut% has 
elapsed, the function returns even if the X() clock has still 
not disappeared.

Once the X() clock has disappeared, the function returns after 
SettleTime% has elapsed.

If SettleTime% or TimeOut% is not supplied, SettleTime% will 
default to 5000 milliseconds, and TimeOut will default to 60 
seconds.

Example:

rc% = WaitHostQuiet(4000,30)

waits for the X() clock to be cleared from the OIA for 4 seconds 
(4000 milliseconds) and will timeout if this condition is not 
fulfilled in 30 seconds.


Scope of EXTRA! BASIC Global Variables
--------------------------------------

With EXTRA! BASIC, the scope of global variables extends beyond 
a single macro. This means that if you run two macros from the 
same terminal sessions and they both use a global variable of 
the same name then the initial value of the global variable in 
the second macro will be the same as the value of that variable 
when the first macro terminates.  For example:

macro1.ebm
Global Foo As Integer
Sub Main
    Foo = 5   'Assign Foo the value 5
End Sub

macro2.ebm
Global Foo As Integer
Sub Main
    Print Foo 'If macro2 is run after macro1, this will print '5'
End Sub

Note that this behavior occurs among macros launched from 
the same client (e.g., the EXTRA! Macro Editor, Terminal Session 
A, Terminal Session B, and so forth). If you launch one macro 
from another using the RunEXTRAMacro function, the second macro 
will not have the same launching client and therefore will not 
share global space.  In general, it is a good idea to initialize 
your global variables unless you are purposely sharing them 
between macros.


EXTRA4W.INI [Macro] Entries
---------------------------

There are two entries in the EXTRA4W.INI file that affect EXTRA! 
BASIC macros: IncludePath and SearchPath. Both entries can 
contain semicolon-delimited lists of directories.

IncludePath

The IncludePath setting allows you to specify the path that 
EXTRA! will use in searching for EXTRA! BASIC header files (.EBH). 
By default, EXTRA! searches your system (\EXTRAWIN) and user 
(\EXTRAWIN\USER) directories. You will need to modify this setting 
if you have header files in other directories.  However, make sure 
you include \EXTRAWIN\USER in your new IncludePath as well.

SearchPath

The SearchPath setting specifies the path that EXTRA! uses when 
searching for macros to run.  Note that this entry overrides 
(rather than augments) the default behavior of searching for 
macros in the user directory. Be sure to include \EXTRAWIN\USER 
in your SearchPath if you want that directory to be searched 
too.

Example:

EXTRA4W.INI
.
.
.
[Macro]
IncludePath = C:\EXTRAWIN;C:\EXTRAWIN\USER;C:\EBH
SearchPath = C:\EXTRAWIN;C:\EXTRAWIN\USER;C:\E4WMACRO
.
.
.


-------------
SAMPLE MACROS
-------------

Additional sample macros were included in the product after 
the documentation was sent to print. Refer to your \EXTRAWIN\USER 
directory to determine which macros are not listed in Chapter 6 
of the EXTRA! for Windows User's Guide.


-------
CONTEST
-------

Announcing the 1994 Attachmate Enterprise Solutions Showcase.

Attachmate will soon be launching the Enterprise Solutions Showcase 
contest. This contest will offer fantastic prizes and awards to 
Attachmate customers who have developed applications with Attachmate 
products or who are using Attachmate products in a unique and creative 
manner. Judging categories include: 1) End User Utilities, 2) Group 
Applications, and 3) Enterprise Connectivity Solutions. The contest is 
open to all Attachmate customers, worldwide.

For more information about the 1994 Attachmate Enterprise Solutions 
Showcase contest, please call or write the Attachmate Marketing 
Department, 1-800-426-6283 ext. 6423. For international calls, please 
dial 1-206-644-4010.

Attachmate Corporation
Marketing Department
3617 131st Avenue SE
Bellevue, WA  98006 USA


------------------
END OF E4WREAD.TXT
------------------
