Winword.exe (the Microsoft Word executable) is automatically loaded in the background (invisibly) whenever an EXTRA! session is started. This technical note provides a workaround for this issue.
The Productivity features of EXTRA! X-treme are installed and enabled by default. The spell checking productivity feature uses Winword.exe to function.
Starting in EXTRA! X-treme version 9.0 SP2, EXTRA! no longer uses Winword.exe for spell checking, so this problem no longer exists.
To prevent Winword.exe from launching when EXTRA! is started, disable the spell checking feature. There are several ways to accomplish this; select the method below that works best in your environment.
Method 1: Change the EXTRA! Productivity Options for an Existing Session
Follow these steps to disable spell checking in an existing session of EXTRA!
- In EXTRA!, click Options > Settings.
- Under Categories, select Productivity.
- Clear the Enable Spell Checking check box, and then click OK.
- Click File > Save Session.
- Close your session.
The next time you start your EXTRA! session, spell checking will be disabled and Winword.exe will not be started.
Method 2: Change the EXTRA! Productivity Options for all New Sessions
Follow these steps to disable spell checking in EXTRA! new session templates.
- Close all EXTRA! sessions.
- Navigate to "Program Files\Attachmate\EXTRA!\Sessions\ENU\Template."
- There are three files in the Templates folder, 3270.edp (for 3270 connections), 5250.edp (for 5250 connections), and Async.edp (for Telnet connections). Edit the template file or files that are used in your network environment.
Open the appropriate template file in a text editor, such as Notepad.
- Scroll down to the [Productivity] heading.
- Change the "EnableSpellChecking=YES" entry to "EnableSpellChecking=NO."
- Save the file.
Once the template file is updated, all new session are started with spell checking disabled. This change has no effect on existing saved sessions.
Note: In version 8.x, disabling the EXTRA! spell checking feature does not resolve this issue. To use this workaround, first upgrade to EXTRA! X-treme version 9.0 or 9.0 SP1, then follow the steps provided above for these versions.
Legacy KB IDThis article was originally published as Attachmate Technical Note 2317.
This information was originally published as Attachmate SupportWeb solution IRE2882.