Page 1
11 September 2014 Added changes for v4.7.2
21 July 2014 Added changes for v4.7.1
5 December 2013 Added changes for v4.7.0
31 August 2013 Added changes for v4.6.0
18 June 2013 Initial v4.5.0 version (based on v4.0.4 doc.)
Important Information
Avid recommends that you thoroughly read all of the information in this ReadMe file before installing or
using any new software release.
Note: Search the Avid Knowledge Base (http://www.avid.com/onlinesupport) for the most up-to-date
ReadMe file, which contains the latest information that might have become available after the
documentation was published.
This document describes compatibility issues with previous releases, hardware and software requirements,
software installation instructions, and summary information on system and memory requirements, when
applicable. This document also lists any hardware and/or software limitations.
Note: Since this release of iNEWS will be more widely distributed than previous versions, some notes
on important features and changes have been brought forward from previous ReadMe documents.
Notes that are less important were not brought forward, and users should reference older iNEWS
ReadMe files for additional change information not contained in this ReadMe.
Page 2
Contents
Important Information ............................................................................................................................................ 1
Contents ..................................................................................................................................................................... 2
Compatibility Notes and Issues ................................................................................................................................. 4
iNEWS Client ........................................................................................................................................................ 4
iNEWS Server ....................................................................................................................................................... 4
Workstation/Server Compatibility Chart ............................................................................................................... 4
External Users (LDAP) ......................................................................................................................................... 5
Fast Text Search .................................................................................................................................................... 5
Community Feature ............................................................................................................................................... 5
Command .............................................................................................................................................................. 6
MOS Gateway ....................................................................................................................................................... 6
Console Multiplexer .............................................................................................................................................. 6
Data Receiver ........................................................................................................................................................ 6
Instinct ................................................................................................................................................................... 6
NewsCutter ............................................................................................................................................................ 6
Upgrade Notes and Issues .......................................................................................................................................... 7
iNEWS v4.5.0 ........................................................................................................................................................ 7
iNEWS v4.0 ........................................................................................................................................................... 7
iNEWS v3.6 ........................................................................................................................................................... 7
iNEWS v3.5.0 and FTS v4.0 ................................................................................................................................. 7
Changes between 4.7.0 and 4.7.1 .............................................................................................................................. 7
iNEWS Server ....................................................................................................................................................... 7
Changes between 4.6.0 and 4.7.0 .............................................................................................................................. 8
Large Community Matrix .................................................................................................................................. 8
Small Community Matrix .................................................................................................................................. 8
User Interface .................................................................................................................................................... 9
MOS Duration ................................................................................................................................................... 9
Language Settings.............................................................................................................................................. 9
Changes between 4.5.0 and 4.6.0 ............................................................................................................................ 10
Changes between 4.0.4 and 4.5.0 ............................................................................................................................ 11
Changes between 4.0.3 and 4.0.4 ............................................................................................................................ 11
Changes between 4.0.2 and 4.0.3 ............................................................................................................................ 11
Changes between 4.0.1 and 4.0.2 ............................................................................................................................ 11
Changes between 4.0 and 4.0.1 ............................................................................................................................... 12
Page 3
New Features ........................................................................................................................................................... 13
For iNEWS v4.5.0 ............................................................................................................................................... 13
Interplay Common Services + iNEWS on Shared Host .................................................................................. 13
MOS Redirection ............................................................................................................................................. 13
Online dbvisit .................................................................................................................................................. 13
Project Toolbar Button .................................................................................................................................... 13
ASM (SNMP) Support .................................................................................................................................... 13
Documentation ................................................................................................................................................ 13
For iNEWS v4.0 .................................................................................................................................................. 13
Users ................................................................................................................................................................ 13
Searching ......................................................................................................................................................... 13
BUCKET Queues ............................................................................................................................................ 15
MOS Integration .............................................................................................................................................. 15
Qualified Asian Languages and IMEs ..................................................................................................................... 15
Korean ................................................................................................................................................................. 15
Chinese Simplified .............................................................................................................................................. 15
Chinese Traditional .............................................................................................................................................. 15
Japanese ............................................................................................................................................................... 15
Vietnamese .......................................................................................................................................................... 16
Microsoft Windows Critical Updates ...................................................................................................................... 16
Known Issues and Limitations ................................................................................................................................. 16
Local Database .................................................................................................................................................... 16
Windows 7 and Windows 8 with UAC Enabled ................................................................................................. 16
External Users (LDAP) ....................................................................................................................................... 16
Interplay Common Services 1.5.0 + iNEWS on Shared Host .............................................................................. 17
Plug-ins ................................................................................................................................................................ 18
UNC Paths ........................................................................................................................................................... 18
iNEWS Web Services API .................................................................................................................................. 19
Multiple Monitors ................................................................................................................................................ 19
Macros and Keystrokes........................................................................................................................................ 19
Documentation Errata .............................................................................................................................................. 20
iNEWS Administration Guide ............................................................................................................................. 20
iNEWS Setup and Configuration Guide .............................................................................................................. 20
Technical Support Information ................................................................................................................................ 21
Accessing Online Support ................................................................................................................................... 21
Page 4
Compatibility Notes and Issues This section contains compatibility information related to the iNEWS 4.7.2 release or earlier. Specific
versions are mentioned when pertinent.
iNEWS Client
The iNEWS client software is qualified and supported for use on Windows 8, Windows 7 (32-bit),
Windows 7 64-bit Service Pack 1, Windows Server 2008 R2, and Windows XP Professional (SP2 or SP3).
This version of iNEWS is not officially supported for use on any other Windows operating system,
including the pre-SP1 release of Windows 7 64-bit
The iNEWS 4.0 client software cannot connect to servers earlier than iNEWS 4.0.
The iNEWS 3.5.0 client software cannot connect to servers earlier than iNEWS 3.5.0.
iNEWS Server
The iNEWS Server is qualified and supported for use on Red Hat Enterprise Linux 6.3 64 bit.
The iNEWS Server is qualified in a virtualized environment when the guest OS instance meets the
application‘s minimum system requirements.
Workstation/Server Compatibility Chart
iNEWS
2.8
Server
3.0/1/2
Server
3.3.
Server
3.4/5/6
Server
3.7
Server
4.0
Server
4.5/6
Server
4.7/1/2
Server
2.8
Client
Allowed Allowed Allowed Allowed Allowed Allowed Allowed Allowed
3.0/1/2
Client
Not
allowed
Allowed Allowed Allowed Allowed Allowed Allowed Allowed
3.3
Client
Not
allowed
Not
allowed
Allowed Allowed Allowed Allowed Allowed Allowed
3.4/5/6
Client
Not
allowed
Not
allowed
Not
allowed
Allowed Allowed Allowed Allowed Allowed
3.7
Client
Not
allowed
Not
allowed
Not
allowed
Not
allowed
Allowed Allowed Allowed Allowed
4.0
Client
Not
allowed
Not
allowed
Not
allowed
Not
allowed
Not
allowed
Allowed Allowed Allowed
4.5/6
Client
Not
allowed
Not
allowed
Not
allowed
Not
allowed
Not
allowed
Not
allowed
Allowed Allowed
4.7/1/2
Client
Not
allowed
Not
allowed
Not
allowed
Not
allowed
Not
allowed
Not
allowed
Not
allowed
Allowed
Page 5
External Users (LDAP)
Beginning with version 4.x, Avid iNEWS server allows user authentication via Windows Active Directory;
however, external users are not compatible with the following clients:
iNEWS Workstations earlier than 4.0.0
FTP clients: teleprompters, NewsCutter‘s NRCS Tool
COM clients: NewsCutter's NRCS Tool; Instinct; MOS Gateway's roStorySend and mosObj.
Web Client
Web Access
Interplay Central client earlier than 1.3.0
Fast Text Search
Fast Text Search (FTS) version 4 is required for iNEWS Server version 3.5 and later. FTS 4 is not
supported on any iNEWS Server versions lower than 3.5.
FTS 4 is supported on Windows Server 2008 R2, Windows XP SP3 (32-bit), and Windows Server 2003
SP2 (32-bit). The recommended operating system is Windows Server 2008 R2. A full re-index is required
with an upgrade to FTS 4.
FTS is qualified in a virtualized environment when the guest OS instance meets the application‘s minimum
system requirements.
Community Feature
The iNEWS 3.7 and iNEWS 4.7 releases support 50 Community members, up from 24. This change
caused the iNEWS Community communication protocol to be modified, which breaks compatibility with
earlier versions of servers. For more information, see the ―Changes between 4.6.0 and 4.7.0‖ section of this
ReadMe.
Note: The 3.x releases, prior to 3.5, are designed for “small database” sites only. Versions 3.5 or
later (within the 3.x code stream) may be manually configured for small or large databases,
depending on the needs of the site. And the 4.x releases are designed solely for “large database”
sites—larger than 16GB. For more information about versions 4.0 or later, see the ReadMe
corresponding to the release, available on the Avid Knowledge Base website.
Sites cannot have small database systems in the same community with large database systems.
The 4.0 client can only connect to 4.0 and later servers, whether through community or direct connection.
If a 4.0 server is present in a community, all other servers in the community must be version 3.4.5 or later.
During transition periods, clients should not be upgraded to 4.0 until all servers that client connects to—
directly or through community—are upgrade to 4.0 or later. In this situation, the latest 3.5.x client should
be used until the full community is upgraded.
For iNEWS 3.4.5 to connect via community to iNEWS 3.4.5 or earlier servers, the 3.4.5 servers need to
have a file named /site/env/gnews. The following string must be placed in that file:
GCOMMUNITYSMALLDATABASE=1. See the New Features section of this document for additional
information.
iNEWS Clients cannot be used in a community where any server in their path is of a lower version than the
client.
3.4 clients can connect to 3.4 servers, which can connect through community to 3.4 servers.
3.4 clients cannot connect to pre-3.4 servers directly or through community.
Page 6
3.3 clients can connect to 3.3 and higher servers, which can then connect through community to 3.3
and higher servers.
Clients prior to iNEWS 3.3 do not support the new features in iNEWS 3.3: projects, facets, search
queues, and queue templates.
2.8 clients can connect to 2.8 and higher servers, which can then connect through community to 2.8
and higher server.
The iNEWS 2.8 client software does not support the new features in iNEWS 3.x: combo boxes, check
boxes, story links, URL links, calendar fields, duration fields.
Command
The iNEWS Server is qualified and supported for use with Command 1.0.1 or later.
MOS Gateway
The iNEWS system is qualified and supported for use with MOS Gateway 4.0 or later.
Console Multiplexer
The iNEWS Server requires version 2.0 of the console multiplexer (MUX) software, which is on the
iNEWS installation CD. The console multiplexer cannot currently display Unicode characters. A terminal
emulator that supports Unicode characters can be used if Unicode support is required.
Data Receiver
The iNEWS system is qualified and supported for use with Data Receiver 1.8 or later. iNEWS 3.0 Server
saves data as well-formed XML. Data Receiver SFCs must be updated to deliver well-formed XML. Also,
field tags have changed from <f id=TYPE></f> to <string id=‖TYPE‖></string>.
Instinct
The iNEWS system is qualified and supported for use with Avid Instinct 1.1 and 1.6 or later. After the
iNEWS client software is installed on an Instinct computer, manual registration of the Instinct installation‘s
COM control should be performed: Start > Run > regsvr32 ―C:\Program Files\Avid\Avid iNEWS
Instinct\iNewsCOMU.dll‖.
NewsCutter
The iNEWS system is qualified and supported for use with NewsCutter NRCS Tool 6.1.5 or later. After the
iNEWS client software is installed on a NewsCutter, manual registration of the NewsCutter installation‘s
COM control should be performed: Start > Run > regsvr32 ―C:\Program Files\Avid\Avid
NewsCutter\iNewsCOMU.dll‖. If both NewsCutter and Instinct are on the machine, the Instinct COM
control should be the one you register.
Page 7
Upgrade Notes and Issues This section contains information related to upgrading from previous versions of iNEWS.
iNEWS v4.5.0
Avid recommends when upgrading to iNEWS v4.5 from v4.0.4, that the previous version be uninstalled via
Control Panel and then a ―new install‖ of iNEWS v4.5 be done. Failure to do the uninstall first could result
in a failed upgrade, caused by the presence of a third-party DLL file.
iNEWS v4.0
When a client database is upgraded to v4.0, current projects will get the new BUCKET queue; however,
this queue is not yet indexed, which is required for all stories associated with projects and/or facets. After
the dbrestore, the administrator must run dblines c: to index the new BUCKET queues. After that an
iNEWS user will be able to go to the BUCKET queues and select their preferred index base.
iNEWS v3.6
An auto-upgrade to the iNEWS 3.6 client software on a computer with the Windows XP operating system
will result in an internal error message: Failed to create download directory. Upgrades must be done
manually.
iNEWS v3.5.0 and FTS v4.0
An upgrade to iNEWS 3.5 and FTS 4 requires a full rebuild of each index.
Changes between 4.7.1 and 4.7.2
iNEWS Server
In previous versions of iNEWS, following a software upgrade, users might experience sluggishness while
conducting standard editing tasks at the iNEWS Workstation. This has been fixed with new environment
variable GBUFFERLIMIT set to a value of 4.
The environment variable GBUFFERLIMIT can be added to the /site/env/gnews file to control how many
buffers to allow. This can range from 1 to 4. If GBUFFERLIMIT is not present in /site.env.gnews, then 4
buffers are used. If GBUFFERLIMIT=0 or any numerical value not 1, 2, 3, or 4, then 4 buffers are used.
Having GBUFFERLIMIT=1 results in using a single buffer which was the case prior to this change.
User Interface
In previous versions of iNEWS, copying a selection of text would result in pasting the full body of text
instead of the selected block of text. This has been fixed.
Changes between 4.7.0 and 4.7.1
iNEWS Server
The handling of invalid UTF8 sequences in a story was broken when the iNEWS Server was converted to a
64-bit application in iNEWS 4.7. This has been fixed.
In previous versions of iNEWS, the dblock program was not functional; it always produced the message,
―locatable coding error‖ and exited. This has been fixed.
Page 8
Changes between 4.6.0 and 4.7.0
Large Community Matrix
The iNEWS 3.7 and iNEWS 4.7 releases support 50 community members, up from 24. This change caused
the iNEWS Community communication protocol to be modified. This modification breaks compatibility
with iNEWS 3.6 and iNEWS 4.6 and earlier servers; however, the iNEWS 3.7 and iNEWS 4.7 systems can
be configured to be compatible with the earlier releases.
To take advantage of large communities all iNEWS 3.6 and earlier systems should be upgraded to iNEWS
3.7, and all iNEWS 4.x systems should be upgraded to iNEWS 4.7. It is not recommended to configure
more than 24 community members on iNEWS 3.7 or iNEWS 4.7 until all community members are
upgraded to iNEWS 3.7 or iNEWS 4.7. The following tables shows client version compatibility with
various versions of servers, depending on whether connecting to the server locally or via community.
Large Community
(max 50 members)
Local Server Community Server
v3.7 v4.7 v3.7 V4.7
3.7 Client
4.7 Client
Small Community Matrix
A single community cannot have both small and large community systems. All iNEWS 3.6 and earlier as
well as iNEWS 4.0 to 4.6 are small community systems. Only iNEWS 3.7 and 4.7 can be large community
systems. By default, iNEWS 3.7 and 4.7 are configured to support large community communication;
however, they can be configured as small communities.
Small
Community
(max 24
members)
Local Server
Community Server
v3.5/v3.6 v3.7 v4.5/v4.6 v4.7 v3.5/v3.6 v3.7 v4.5/v4.6 v4.7
3.5 Client
3.7 Client
4.5 Client
4.7 Client
Page 9
To configure iNEWS 3.7 and 4.7 as a small community:
Create the file /site/env/gnews. In this file, place the following line:
GCOMMUNITYSMALLCOMMUNITY=1.
Here‘s how this step looks in a console display:
NRCS-A$ cat /site/env/gnews
GCOMMUNITYSMALLCOMMUNITY=1
The new versions (3.7 and 4.7) will still allow you to enter up to 50 community members, but if configured as a
small community, they will not allow you to use any member after the 24th one. Also, servers won‘t be
displayed in the iNEWS client directory tree.
For troubleshooting purposes, below are the error messages and the cases in which they will appear.
Large community 4.7 to small community 4.6 or lower
local: G###: Error (16) during SETCOMMUNITY to <REMOTE>
remote: C###: Exit: Error communicating with Client (24:Protocol level)
<REMOTE>
User Interface
In previous versions of iNEWS 4.x, a forward slash (/) in a form field ID would break the story form when
the iNEWS story was viewed in Interplay Central. This was fixed by disallowing forward slash characters
in the form field ID.
In previous versions of iNEWS 4.x, the Logged in users dialog box erroneously displays the user‘s ID in
the Real name column. This is fixed.
In previous versions of iNEWS, if a user manually typed , the system would process it as
a file link. This has been fixed. Now, when a space appears after the data is displayed in the story
as text; no link is created.
In previous versions of iNEWS, pasting copied text into a story could cause the cursor to relocate to a
position other than at the end of the pasted block of text. This has been fixed. Now, when text is pasted into
a story, the cursor is positioned at the end of the added text.
In previous versions of iNEWS 4.x, users without write access to the backtime field could not see the
calculated values in field at all. This is fixed.
MOS Duration
Beginning with v4.0, support for MOS time updates in the iNEWS story was enhanced, but this resulted in
an error sometimes when users dragged and dropped Active-X MOS items into iNEWS stories. This is
fixed.
Language Settings
In previous versions of iNEWS 4.x, if a user changed the language for spell check to Australian English,
that setting would not be retained after the user logged out and then back in again. This is fixed.
Page 10
Changes between 4.5.0 and 4.6.0
In previous versions of iNEWS, a menu option ―Play Low-res Video‖ would be available in the Story menu
when Instinct associated a sequence with an iNEWS story.
This option, which was also available in the right-click context menu, let users view low-res video.
Associated with this functionality was an Interplay Server tab in the Queue Properties dialog box.
These features—the tab and menu options—have been removed from iNEWS.
Consequently, the queue SYSTEM.INTERPLAY (/site/dict/queues: Q_INTERPLAY) that was required for
this functionality is no longer necessary, and system administrators may remove it from the database.
In this release of iNEWS, there is a new local print option used to handle printing of segmented scripts in
iNEWS. Interplay Central users can divide iNEWS stories into multiple segments and then use the
segments to time the text and integrate the script with video, audio, and production cues. In previous
versions of iNEWS, these segments were treated as page breaks when printing the scripts from an iNEWS
workstation. For example, a short script with three segment breaks would print out on four pages instead of
Page 11
one. Local print options are stored in iNEWS in the first stories of queues in SYSTEM.STYLES. The new
local print option is called WinSegmentBreakAsPageBreak. Parameter values for this new option are YES
or NO. By default it is set to NO. When set to NO, segment breaks are not treated as page breaks, so the
scripts print out without division. For example, the short script with three segment breaks would print out
on a single page instead of four.
Changes between 4.0.4 and 4.5.0
In previous versions of iNEWS 4, rxnet server failed to close NSML tag. This is fixed.
In previous versions of iNEWS 4, seek server failed with "Searched" bitmap allocation failure message.
This is fixed.
In previous versions of iNEWS 4, it was not possible to unbusy a queue that had a dash (-) in front of it.
This is fixed.
In previous versions of iNEWS 4, editing the body of a story that had one or more MOS items while
monitor server was on but not yet loaded (to the MOS device) lead to Bad Event ID errors in MOS
Gateway after the monitor load. This is fixed.
In previous versions of iNEWS 4, line breaks were stripped from production cues. This is fixed.
In previous versions of iNEWS 4, the Chinese close quotation mark for a book name was not saved
properly. This is fixed.
In previous versions of iNEWS 4, invalid text delivery would cause the client software to hang. This is
fixed.
In previous versions of iNEWS 4, in print styles - left and right banners were not displayed blank even if
appropriate settings were applied. This is fixed.
In previous versions of iNEWS, Title Entry removed the text after the cursor point inside Presenter text.
This is fixed.
In previous versions of iNEWS, numeric entries with spaces in them had their order reversed when form
was in the queue view and field was right justified. This is fixed.
In previous versions of iNEWS, form field tooltips no longer gave the correct information. This is fixed.
In previous versions of iNEWS, space characters were valid in date fields, but could not be entered in the
AIR-DATE field. This is fixed.
In the Canadian French version of the iNEWS client software, the Story menu option Search All (which
should‘ve been ―Renuméroter Tout‖) was incorrectly translated. This is fixed.
Changes between 4.0.3 and 4.0.4
In previous releases, the presence of corrupted data caused a third party DLL file (og1200asu.dll) by Object
Grid to hang. This has been fixed.
Changes between 4.0.2 and 4.0.3
In previous releases, cursor movement (typing) would become extremely sluggish in very large iNEWS
stories. This has been fixed.
In previous releases, a story containing a MOS production cue in an iNEWS rundown produces a Bad
Event ID error, which required a user to float and unfloat the affected story. This has been fixed.
Changes between 4.0.1 and 4.0.2
In previous releases, the number pad characters 2 and 6 did not work in the iNEWS story body. This has
been fixed.
In previous releases, the @ starter character was interpreted as an e-mail address in system keyboards. This
broke older system keyboard macros and prevented users from creating new system keyboard macros. This
has been fixed.
In previous releases, line breaks were sometimes stripped from production cues. This has been fixed.
Page 12
In previous releases, the cursor focus appeared at the start of pasted text instead of at the end. This has been
fixed.
In previous releases, some sites running RedHat 6 experienced failed logins with the error
―setMaxProtocolLevel failed.‖ These sites also had corrupt t/u index files and corrupt Monitor Device
Status ISAM files. Logins can fail when the t/u index file is corrupt and monitor can fail when the Monitor
Device Status file is corrupt. This has been fixed.
Changes between 4.0 and 4.0.1
In previous releases, dragging and dropping text between production cues could crash the iNEWS client
under Windows XP. This has been fixed.
In previous versions of iNEWS, diskcopy performance was slow at high copy levels and over-taxing at low
copy levels. This has been fixed.
In previous versions of iNEWS, if you added "DEKOMOS DEKOMOS" as a mos-map entry, DEKOMOS
items could not be loaded. They produced an "invalid MOS item" error at the client and a "
mosId[dekomos] does not map to device[DEKOMOS]" error at the server. This has been fixed.
In previous versions of iNEWS, there were client Import/Export dialog display issues with top left and right
areas of the navigation bar. This has been fixed.
Page 13
New Features This section contains a listing of new features.
For iNEWS v4.5.0
Interplay Common Services + iNEWS on Shared Host
This version of iNEWS provides the ability for a site to run a single non-clustered instance of Interplay
Common Services (v1.5.0 or later) on one of its iNEWS servers as a shared-host server. For more
information, see the new publication Avid iNEWS and ICS Integration Guide.
MOS Redirection
This version of iNEWS provides support for MOS Redirection, the ability to have a playout device such as
a character generator automatically download media from a sibling playout device. For more information,
see the new chapter called ―MOS Redirection‖ in the Avid iNEWS Setup and Configuration Guide.
Online dbvisit
This version of iNEWS provides support for online dbvisit, which means system administrators don‘t have
to take the system offline to do database maintenance. The feature requires checkpoint partition to be
active. For more information, see the ―dbvisit‖ section in Appendix A of the Avid iNEWS Setup and
Configuration Guide.
Project Toolbar Button
This version of iNEWS lets users add shortcut buttons to custom toolbars that navigate to any project, facet,
or queue in a project. For more information, see the new section called ―Creating a Shortcut Button‖ in the
Projects chapter of the Avid iNEWS Setup and Configuration Guide.
ASM (SNMP) Support
This version of iNEWS provides support for monitoring iNEWS Server statistics via an SNMP monitoring
application such as Avid System Monitor (ASM). For more information, see the new chapter called ―Avid
System Monitoring‖ in the Avid iNEWS Admin Guide.
Documentation
This version of iNEWS provides a newly revised Doc-Set which includes the Avid iNEWS Admin Guide
and the Avid iNEWS Installation and Configuration Guide.
For iNEWS v4.0
Users
This version of iNEWS provides the optional ability to import users. For more information, see the ―Users‖
chapter in the Avid iNEWS Setup and Configuration.
This version of iNEWS provides the ability to set a user account as an External User. For more
information, see the ―Users‖ chapter in the Avid iNEWS Setup and Configuration Guide.
Searching
Beginning with iNEWS v4.0, date variables have been added as options in the Search Queue Setup and
Find All dialog boxes.
Page 14
For more information about the Date Search options, see the section called ―Date Variables for Searching‖
in the Projects chapter of the Avid Setup and Configuration Guide.
Page 15
BUCKET Queues
The iNEWS newsroom computer system now offers BUCKET queues as part of its existing Projects
feature. Also, iNEWS lets users create new stories inside of Projects in either the ALL or FACET queues,
as well as in the new BUCKET queue added to all projects. The procedures for doing so are provided in the
Projects chapter of the Avid iNEWS Setup and Configuration Guide.
MOS Integration
Avid iNEWS v4.0 now lets users insert MOS object placeholders within iNEWS stories in either the story
form or as a story‘s production cue. The procedures for doing so are provided in the ―The Database:
Directories, Queues, and Stories‖ chapter in the Avid iNEWS Setup and Configuration Guide:
Qualified Asian Languages and IMEs
Korean
The following Korean IME (standard Windows IME) is tested and qualified:
Korean Input System (IME 2002)
Known Issue – While the Korean-text queue navigation works correctly, the Go To > Destination menu
option does not allow direct navigation to folders with Korean-text names.
Chinese Simplified
The following Chinese Simplified (PRC) IME (standard Windows IMEs) is tested and qualified:
Microsoft Pinyin IME 3.0
WangMa Wubi 86
WangMa Wubi 98
Chinese Traditional
The following Chinese Traditional IMEs (standard Windows IMEs) are tested and qualified:
New ChangJie
New Phonetic
ChangJie
Phonetic
DaYi
The following Chinese Traditional IMEs (3rd party IMEs) have had minimal testing done and are not yet
qualified or supported:
Boshamy (WuXiaMi)
Natural Input
Japanese
The following Japanese IME (standard Windows IME) was tested and qualified:
Microsoft Standard IME 2002 version 8.1
Page 16
Vietnamese
The following Vietnamese IMEs were tested and qualified:
UniKeyNT 3.6
o Input Methods: Telex and VNI
o Character Set: Unicode
Vietkey 2000 Build 10727
o Input Method: Telex
o Character Set: Unicode Pre-Compound
Known Issue with both Vietnamese IMEs - Certain Vietnamese characters do not get inserted correctly
via keyboard macro when the IME is set to Vietnamese input. The workaround for this issue is to set the
IME to English input before starting the macro.
Microsoft Windows Critical Updates Avid recognizes that it is very important to be able to deploy Microsoft security patches to our Windows-
based products as quickly as possible. We recommend that systems be kept up to date in order to maintain
the highest level of security and encourage you to install all critical operating system updates provided by
Microsoft.
In the unlikely event that one of these updates causes an issue, it is recommended that you uninstall the
update and contact Avid customer support as soon as possible. Avid will investigate the incompatibility and
if necessary, will provide a software update or work around to allow our products to properly function with
the Microsoft update in question.
Known Issues and Limitations
Local Database
To download print styles and story forms to your local computer for use when working offline, you must
have Read Access to the iNEWS System directories where styles and forms are located. This is by design.
Windows 7 and Windows 8 with UAC Enabled
When User Access Control (UAC) is turned on, users cannot drag-and-drop text from an outside
application, such as Microsoft Word, into iNEWS.
Workaround:
Use Ctrl+C and Ctrl+V to copy and paste the text between applications.
External Users (LDAP)
Beginning with version 4.x, Avid iNEWS server allows user authentication via Windows Active Directory;
however, external users are not compatible with the following clients:
iNEWS Workstations earlier than 4.0.0
FTP clients: teleprompters, NewsCutter‘s NRCS Tool
COM clients: NewsCutter's NRCS Tool; Instinct; MOS Gateway's roStorySend and mosObj.
Web Client
Web Access
Interplay Central client earlier than 1.3.0
Page 17
Interplay Common Services 1.5.0 + iNEWS on Shared Host
The HP G7 and G8 were observed to declare the RAID1 as /dev/sdb and the RAID5 as /dev/sdc during
Linux installation, and then change them to /dev/sda and /dev/sdb between iNEWS pre-install and iNEWS
Server install. This can cause /etc/udev/rules.d/10-udev-iNEWS rules to point to the incorrect device. If the
iNEWS installer cannot find an /rp5 or /rp5backup, verify that the partitions in 10-udev-iNEWS.rules
match the drives displayed in fdisk.
The /etc directory is configured for group write. This causes sendmail to malfunction.
Workaround:
Remove the group write, using the following command:
chmod g-w /etc
Depending on versions and upgrade order, upgrades to newer ICS or iNEWS versions may resolve or
introduce limitations.
There are currently no known limitations when ICS is installed before iNEWS; however, there are several
known limitations if iNEWS is installed before ICS, and they are:
The iNEWS pre-installation script enables httpd. This can interfere with ICS installation.
Workaround:
Before installing ICS, disable httpd with the following commands:
service httpd stop
chkconfig httpd off
The ICS installer uses a local copy of rsyslog.conf.
Workaround:
To re-enable iNEWS logging after ICS is installed, you must add these two lines to the bottom of
/etc/rsyslog.conf, and then restart rsyslog:
local0,local1,local2,local3,local4,local5,local6.*
/var/log/iNEWS/iNEWS.log
local0,local1,local2,local3,local4,local5,local6.* /dev/console
The Linux firewall is re-enabled with each reboot.
Workaround:
Disable the firewall with the following commands:
service iptables stop
chkconfig iptables off
Stop the firewall after reboot by adding the following line to the bottom of /etc/rc.local:
/etc/init.d/iptables stop
The ICS installer overwrites crontab.
Workaround:
If crontab is in use to schedule actions, make note of the current configuration ( ), and
then replace the configuration after ICS installation.
Page 18
Plug-ins
Some plug-ins, such as AMG Journalist, will not paint correctly in iNEWS.
Workaround:
To resolve the painting problem issue, use the following procedure.
Note: AMG Journalist is used in the procedure as a plug-in example.
1. In the iNEWS executable directory, create a new text file named ActiveXRedraw.txt.
For 64 bit workstations, the directory is located at: C:\Program Files (x86)\Avid\iNEWS\
For 32 bit workstations, the directory is located at: C:\Program Files\Avid\iNEWS\
2. Open the registry editor, using regedit in the Run dialog box.
3. Select Edit > Find > AMG Journalist and locate the CLSID for the plug-in.
For 64 bit workstations, the CLSID is located at:
Computer\HKEY_CLASSES_ROOT\Wow6432Node\CLSID\
For 32 bit workstations, the CLSID is located at:
Computer\HKEY_CLASSES_ROOT\CLSID\
4. Take the CLSID, which is the folder name, and put it into the ActiveXRedraw.txt file.
5. Save the file.
6. Reload iNEWS. The painting problem for plug-ins like AMG Journalist will be resolved.
UNC Paths
As a result of the server-side URL changes in iNEWS 3.4.2, UNC paths with spaces no longer work
correctly in the iNEWS client software. In a future version of the iNEWS client software, these links will
be client-only, allowing a user to launch them from the iNEWS Workstation without saving them as URLs
on the iNEWS Server.
iNEWS integration with Intelliscribe printing should be configured at 300 DPI with "Enhanced Features"
disabled. Setting a higher DPI or enabling enhanced features can cause long delays in printing.
Page 19
There are screen painting issues when the Vertigo Xmedia plug-in and the Aurora Assignment List plug-in
(version 7 or later) are both installed on the same client. The Xmedia splash screen can cause the Xmedia
tree to be inaccessible.
Workaround: When this issue occurs, the workaround is to rename or remove skinCrafter3_vs2008.dll
from the Assignment List installation directory.
iNEWS Web Services API
The iNEWS Web Service API cannot be undeployed via the Tomcat management interface when Tomcat is
running on a Windows host.
To undeploy in Windows:
1. Stop the Tomcat service
2. Delete the inewswebservice file and folder from the Tomcat webapps directory.
3. Place the new .war file into the webapps directory.
4. Start the Tomcat service.
Note:Undeployment through the management interface works correctly if the Tomcat service is
running on a Linux host.
Multiple Monitors
If running the iNEWS client software on a dual monitor workstation, there are some key issues you could
encounter:
If the application is maximized when closed, it will be maximized on the primary monitor when it is
reopened, regardless of which monitor it was on when closed.
Moving a user from a dual monitor machine to a single monitor machine, such as an undocked laptop,
could result in the application opening to a screen that no longer exists.
Workaround: Right click on iNEWS in the Windows taskbar and select Move. Then press one of the
arrow keys on the keyboard; this will lock the application‘s window to the mouse. You can then move
the mouse pointer onto the screen and the iNEWS main window will move with it.
Macros and Keystrokes
Some PCs, when upgraded from Internet Explorer 6 to Internet Explorer 7 or 8, will experience issues with
macros that perform several functions in rapid succession; the macros might not complete all assigned
activity in iNEWS. Avid is working with Microsoft on this issue, which is most apparent with macros that
trigger the Local Print dialog box or the User Preferences dialog box.
Workaround: Place the name of the dialog box after the K_WINDOW token value immediately following
the keystroke that opens the dialog box. For instance, instead of just {ctrl p} to open the Local Print dialog,
the macro should be: {ctrl p}{window Local Printing}. The text following ‗window‘ must match exactly
the name of the dialog box as it appears in the title bar. The ‗K_WINDOW /window‘ token can be changed
in /site/dict/keymacros.
Another available workaround is to add {pause <#>} statements of one or two seconds to problem macros
at the point in the macro where activity ceases. In the example of the Local Printing macros, the pauses are
likely needed when typing a name of a printer or changing a print style.
Page 20
Documentation Errata
iNEWS Administration Guide
In Chapter 4 titled Database Management, there is a section called ―Using dbserver and dbfree to Obtain
Information,‖ which provides a procedure on page 53 for obtaining an accurate idea of how much space is
being used. In step 1 of that procedure, the user is told to type the following: dbserver 16000000
It should be dbserver 34000000 to reflect the maximum database size in blocks and ensure that the
DEAD queue is emptied.
In Chapter 4 titled Database Management, there is a section called ―Cleaning Your Database with Online
Dbvisit,‖ which provides a procedure on page 60 for performing an online dbvisit. In that procedure, in step
3b, the user is instructed to type online to bring the system online. This step should be:
Type startup to start the system. This will put the system online as well as start up all iNEWS devices.
iNEWS Setup and Configuration Guide
In Chapter 2 titles The iNEWS Console, on page 35, there is a note about multi-server system configuration
the erroneously mentions ―four-server systems.‖ Avid does not sell or qualify 4-server systems; therefore,
the note should be:
The examples shown here are for the more common two-server system configuration, but an iNEWS system
can have three servers (A, B, and C). For three-server systems, use log file names that correspond to each
server’s letter assignment.
In Chapter 5 titled The Database: Directories, Queues, and Stories, there is a section called ―Interplay
Server Tab,‖ which provides information about a feature that has since been removed from the software.
This section is obsolete.
In Chapter 13 titled Servers, there is table providing parameter and definitions for SYSTEM.MAP. The
<timeout> parameter is described as follows: Enter a duration by typing D or d before a numeric value. An
uppercase D denotes a duration in hours, and a lowercase d denotes a duration in minutes.
This is inaccurate. The parameter is not case sensitive, so D or d before a four-digit numeric value is the
same. The correct syntax is D (or d) followed by hhmm with the hh representing hours and mm for
minutes. For instance, one hour would look like this: D01 or d01. One minute would look like this: D0001
or d0001. Five and a half hours would look like this: D0530 or d0530.
In Appendix B titled System Files, there is a section called ―SYSTEM.INTERPLAY.‖ This describes a
queue that was previously required for a feature that has since been removed from the software. This
section, which was also published in Appendix B of the Avid iNEWS Administration Guide, is obsolete.
Page 21
Technical Support Information Most products feature a number of coverage options. Avid Assurance service offerings are designed to
facilitate your use of Avid solutions. Service options include extended telephone coverage, automatic
software maintenance, extended hardware warranty, and preferred pricing on replacement parts. Offerings
and options may vary by product and are not available for all products.
For more information regarding Avid service offerings, visit www.avid.com/support or call Avid Sales at
800-949-AVID (800-949-2843).
Program availability and details might vary depending on geographic location and are subject to change
without notice. Contact your local Avid office or your local Avid Reseller for complete program
information and pricing. However, if you need help locating an Avid office or Avid Reseller near you,
please visit www.avid.com or call in North America 800-949-AVID (800-949-2843). International users
call 978-275-2480.
Accessing Online Support
Avid Online Support is available 24 hours per day, 7 days per week. Search the Knowledge Base to find
answers, to view error messages, to access troubleshooting tips, to download updates, and to read/join
online message-board discussions.
To access Avid Online Support:
Go to www.support.avid.com .
Note: Supplemental documentation for this release, if available, is provided on the Knowledge Base.
For the latest up-to-date information, browse the Knowledge Base at Avid Online Support.