iNEWS v4.0.3 ReadMe - Avid

Version 4.0.3 ReadMeiNEWS ® Newsroom Computer SystemVersion 4.0.3 ReadMeDate RevisedChanges Made25 February 2013 Added information for v4.0.3.28 November 2012Added information for v4.0.2. See Changes between 4.0.1 and 4.0.2Improved description of Fast Text SearchImproved description of support for a virtualized environment. SeeiNEWS Server.23 October 2012 Added information for v4.0.111 September 2012 Initial v4.0 version (based on v3.5.3 doc.)Important InformationAvid recommends that you thoroughly read all of the information in this ReadMe file before installing orusing any new software release.Note: Search the Avid Knowledge Base (http://www.avid.com/onlinesupport) for the most up-todateReadMe file, which contains the latest information that might have become available afterthe 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, whenapplicable. This document also lists any hardware and/or software limitations.Note: Since this release of iNEWS will be more widely distributed than previous versions, somenotes on important features and changes have been brought forward from previous ReadMedocuments. Notes that are less important were not brought forward, and users should referenceolder iNEWS ReadMe files for additional change information not contained in this ReadMe.1

Version 4.0.3 ReadMeContentsImportant Information ............................................................................................................................................ 1Compatibility Notes and Issues ................................................................................................................................. 5Fast Text Search .................................................................................................................................................... 5Workstation/Server Compatibility Chart ............................................................................................................... 5Community Feature ............................................................................................................................................... 5iNEWS Client ........................................................................................................................................................ 6iNEWS Server ....................................................................................................................................................... 6Command .............................................................................................................................................................. 6MOS Gateway ....................................................................................................................................................... 6Console Multiplexer .............................................................................................................................................. 6Data Receiver ........................................................................................................................................................ 6Instinct ................................................................................................................................................................... 6NewsCutter ............................................................................................................................................................ 6Teleprompter ......................................................................................................................................................... 6Installation Notes and Issues ..................................................................................................................................... 7iNEWS v4.0 ........................................................................................................................................................... 7FTS v4.0 .............................................................................................................................................................. 11FTS Installation and Configuration Procedure ................................................................................................ 11Upgrade Notes and Issues ........................................................................................................................................ 17iNEWS v4.0 ......................................................................................................................................................... 17iNEWS v3.5.0 and FTS v4.0 ............................................................................................................................... 17Changes between 4.0.2 and 4.0.3 ............................................................................................................................ 17Changes between 4.0.1 and 4.0.2 ............................................................................................................................ 18Changes between 4.0 and 4.0.1 ............................................................................................................................... 18Changes between 3.5.3 and 4.0 ............................................................................................................................... 18Server ................................................................................................................................................................... 18Searching ............................................................................................................................................................. 18Workstation ......................................................................................................................................................... 20Spell-checker ....................................................................................................................................................... 21MOS Integration .................................................................................................................................................. 21New Features ........................................................................................................................................................... 21For iNEWS v4.0 .................................................................................................................................................. 21Users ................................................................................................................................................................ 21Searching ......................................................................................................................................................... 21BUCKET Queues ............................................................................................................................................ 212

Version 4.0.3 ReadMeKnown Issues and Limitations ................................................................................................................................. 33Plug-ins ................................................................................................................................................................ 33UNC Paths ........................................................................................................................................................... 34Keyboards ............................................................................................................................................................ 34iNEWS Web Services API .................................................................................................................................. 34Multiple Monitors ................................................................................................................................................ 34Macros and Keystrokes........................................................................................................................................ 34Technical Support Information ................................................................................................................................ 35Accessing Online Support ................................................................................................................................... 354

Version 4.0.3 ReadMeCompatibility Notes and IssuesThis section contains compatibility information related to the iNEWS 4.0 release or earlier. Specificversions are mentioned when pertinent.Fast Text SearchFast Text Search (FTS) version 4 is required for iNEWS Server version 3.5 and later. FTS 4 is notsupported 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 isWindows 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 minimumsystem requirements.Workstation/Server Compatibility Chart2.8 Server 3.0/1/2 Server 3.3. Server 3.4/5 Server 4.0 Server2.8 Client Allowed Allowed Allowed Allowed Allowed3.0/1/2 Client Not allowed Allowed Allowed Allowed Allowed3.3 Client Not allowed Not allowed Allowed Allowed Allowed3.4/5 Client Not allowed Not allowed Not allowed Allowed Allowed4.0 Client Not allowed Not allowed Not allowed Not allowed AllowedCommunity FeatureThe 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 shouldbe 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 tohave 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 additionalinformation.iNEWS Clients cannot be used in a community where any server in their path is of a lower version than theclient.• 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.• 3.3 clients can connect to 3.3 and higher servers, which can then connect through community to 3.3and higher servers.• Clients prior to iNEWS 3.3 do not support the new features in iNEWS 3.3: projects, facets, searchqueues, and queue templates.• 2.8 clients can connect to 2.8 and higher servers, which can then connect through community to 2.8and higher server.5

Version 4.0.3 ReadMe• The iNEWS 2.8 client software does not support the new features in iNEWS 3.x: combo boxes, checkboxes, story links, URL links, calendar fields, duration fields.iNEWS ClientThe iNEWS client software is qualified and supported for use on Windows 7 (32-bit), Windows 7 64-bitService Pack 1, Windows Server 2008 R2, and Windows XP Professional (SP2 or SP3). This version ofiNEWS is not officially supported for use on any other Windows operating system, including the pre-SP1release 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 ServerThe iNEWS Server is qualified and supported for use on Red Hat Enterprise Linux 6.x 64 bit.The iNEWS Server is qualified in a virtualized environment when the guest OS instance meets theapplication’s minimum system requirements.CommandThe iNEWS Server is qualified and supported for use with Command 1.0.1 or later.MOS GatewayThe iNEWS system is qualified and supported for use with MOS Gateway 4.0 or later.Console MultiplexerThe iNEWS Server requires version 2.0 of the console multiplexer (MUX) software, which is on theiNEWS installation CD. The console multiplexer cannot currently display Unicode characters. A terminalemulator that supports Unicode characters can be used if Unicode support is required.Data ReceiverThe iNEWS system is qualified and supported for use with Data Receiver 1.8 or later. iNEWS 3.0 Serversaves data as well-formed XML. Data Receiver SFCs must be updated to deliver well-formed XML. Also,field tags have changed from to .InstinctThe iNEWS system is qualified and supported for use with Avid Instinct 1.1 and 1.6 or later. After theiNEWS client software is installed on an Instinct computer, manual registration of the Instinct installation’sCOM control should be performed: Start > Run > regsvr32 “C:\Program Files\Avid\Avid iNEWSInstinct\iNewsCOMU.dll”.NewsCutterThe iNEWS system is qualified and supported for use with NewsCutter NRCS Tool 6.1.5 or later. After theiNEWS client software is installed on a NewsCutter, manual registration of the NewsCutter installation’sCOM control should be performed: Start > Run > regsvr32 “C:\Program Files\Avid\AvidNewsCutter\iNewsCOMU.dll”. If both NewsCutter and Instinct are on the machine, the Instinct COMcontrol should be the one you register.TeleprompterThe iNEWS system supports the following teleprompter software: WinPlus BDL Unicode version 6.8.7.3and WinCue version 1.30 (build 674 or higher).6

Version 4.0.3 ReadMeInstallation Notes and IssuesiNEWS v4.0• Changes to the iNEWS Server installation include the addition of domain information to /etc/krb5.conf.This is necessary for sites that require User ID validation through an LDAP server for an External Useraccount.An iNEWS user account can be set as an External User when added to the database via a setting in the AddNew User dialog box.The purpose of the External User account is for the User ID credentials to be validated on an LDAP serverinstead of the iNEWS Server. For this external validation to work, customer domain information must beentered in the /etc/krb5.conf file during the iNEWS Server installation.Below is a sample of the updated iNEWS v4.0 server installation procedure:1. Set up user authentication.Initializing Kervberos configuration…The default realm is ‘EXAMPLE.COM’. Do you wish to change it? [y/n] yEnter the default realm: global.wavd.comDo you wish to set the default realm to “”? [y/n] yCreating certificate…• With iNEWS v4.0, you can import users from LDAP servers. There are many ways of acquiring a list ofLDAP users, various applications that can export LDAP information in LDIF and/or CSV formats; thefollowing procedure is one option.To import users from an LDAP server:1. Find domain and currently logged in LDAP server.7

Version 4.0.3 ReadMea. In a Windows MSDOS prompt from local computer, run the command:echo %UserDnsDomain%Example output: GLOBAL.WAVD.COMb. Run the command: echo %LogonServer%Example output: \\MSN-DC01c. From the output given, combine the results to make up the name of the logged in LDAP server onthe domain. For example, using the previous sample output: msn-dc01.global.wavd.com2. Find LDAP server on the domain to get the port number.In a console session on the iNEWS Server, run the command in the following format:dig +short-t srv_ldap._tcp.The User DNS Domain is the output obtain in the previous step of this procedure. For instance, type:dig +short-t srv_ldap._tcp.global.wavd.comExample output: 0 100 389 kai-dc01.global.wavd.com0 100 389 ldn-dc01.global.wavd.com0 100 389 msn-dc01.global.wavd.comThese sample results show all LDAP servers on the domain. The third set of numbers in the results isthe port number; in this case, it is 389.3. Search LDAP server from the iNEWS Server and create output file of users.a. Obtain Kerberos ticket-granting ticket by running the command:kinit b. When prompted, provide the Windows domain password. This will result with the accountbeing cached on the iNEWS Server so the credentials can be used by the ldapsearch function.c. Create a script file to search an LDAP server by starting a document on the local workstationin Notepad.For example:ldapsearch\-H ldap://msn-dc01.global.wavd.com:389 \-b DC=global,DC=wavd,Dc=com \“(&(objectClass=person)(sAMAccountName=bri*)(sAMAccountType=80 5306368))” sAMAccountName cn sn mail objectclass \kdestroyIn the example, ldapsearch\ is the ldap command. The -H line is a URL for the AD server.The port number (389) shown in the example is the same sample port used in previous stepsof this procedure. The -b line is the searchbase. It is possible that DC=global is not needed.The last line of the search is the query followed by the attributes that you want to see. Youonly need samaccountname and cn. The example is a set of three matching criteria that arejoined together via the Boolean ampersand (&). The syntax is to enclose each term inparentheses and to prefix a set with the Boolean operator. So you see the ampersand (&)before the 3 criteria and the set is enclosed in parentheses.This example search limits the user account names, “sAMAccountName”, to those startingwith “bri”. The “sAMAccountType” value is a Windows defined value for a user account. Itmight not be needed in the script you create, but note that the last term appears as if it has acarriage return. It does not have a carriage return before =80—it only appears that waybecause of margin settings for this document. Make sure the script that you create does nothave carriage returns either.8

Version 4.0.3 ReadMed. Name the .txt file what you want, minus the tag (.txt). Copy script file from Windowsworkstation to /tmp/ directory on the iNEWS Server, using the WinSCP ftp utility.e. Convert the script file to linux via a PUTTY session to the iNEWS Server. Go to the /tmp/directory by typing cd /tmp/, and then run Dos2Unix by typing:dos2unix f. Run the script file to see it return results by typing:sh-x /tmp/Example results:+ ldapsearch ldap://msn-dc01.global.wavd.com:389 -bDC=global,DC=wavd,DC=com'(&(objectClass=person)(sAMAccountName=bri*)(sAMAccountType=805306368))' sAMAccountName cn sn mail objectclassldap_initialize( ldap://msn-dc01.global.wavd.com:389/??base )Note: The utraits user input will only inport the cn and sAMAccountName attributes (shown asbold italics below).# extended LDIF## LDAPv3# base with scope subtree# filter:(&(objectClass=person)(sAMAccountName=bri*)(sAMAccountType=805306368))# requesting: sAMAccountName cn sn mail objectclass## John Doe, Users, Engineering, AVID Technology Inc,global.wavd.comdn: CN=John Doe,OU=Users,OU=Engineering,OU=AVID TechnologyInc,DC=global,DC=wavd,DC=comobjectClass: topobjectClass: personobjectClass: organizationalPersonobjectClass: usercn: John Doesn: DoesAMAccountName: jdoemail: john.doe@wavd.com# Jane Smith, Users, North America, AVID Technology Inc,global.wavd.com9

Version 4.0.3 ReadMedn: CN=Jane Smith,OU=Users,OU=North America,OU=AVID Technology Inc,DC=global,DC=wavd,DC=comobjectClass: topobjectClass: personobjectClass: organizationalPersonobjectClass: usercn: Jane Smithsn: SmithsAMAccountName: jsmithmail: jane.smith@wavd.com# search referenceref:ldap://DomainDnsZones.global.avidww.com/DC=DomainDnsZones,DC=global,DC=wavd,DC=com# search resultsearch: 2result: 0 Success# numResponses: 4# numEntries: 2# numReferences: 14. After the output is verified as good, dump exported users to file by typing:sh –x /tmp/ > /tmp/Note: It will appear as if the command is halted. Technically, it is halted. What you don’t see isthe “Enter LDAP Password:” prompt for the password used in the –D parameter of the scriptfile. So after you enter the command, when it halts, enter the password. In a few moments, thelinux prompt will be back, and the file will be placed in /tmp/ directory.This file is then used to import new users into iNEWS.5. Importa. Users from output file.Users in output file are imported into iNEWS using the utraits command. There are two file types thatcan be imported, csv and ldif. Common output of active directory query will be ldif. Sometimescustomers might export their users to csv file eliminating the work above. You can also use the ‘list’option in utraits to create a comma separated output from ldif output, or just use ‘list’ to verify the datato be imported into iNEWS. In each scenario a template user that already exists in the iNEWS systemis used as the clone user. Every user in the output file will be imported using the template user’ssettings and password. If you choose to give these imported users a different startup password than10

Version 4.0.3 ReadMewhat is used by the template user, you will need to include the ‘password’ option of utraits as well.Otherwise imported users will first login using the password of the template user, then be forced tocreate their own unique password.‣ Import users into iNEWS from output file, using the standard ldif format.Type: utraits ldif: clone passwordextern-user +eu‣ Import users into iNEWS from .csv file.Type: utraits csv: clone passwordextern-user +euExample output for either import method:User jdoe addedUser jsmith added2 user records addedRunning a list u j* command or logging in as the users will verify that the users are nowimported into the system.Note: To create a .csv file from an ldif output file, run the utraits command in the followingformat: utraits ldif: list > .b. Group names from output file• Run the query script without the OU values• Note the OU values from the query results as these will tell you the group names• Modify –b value to include OU group data• Save script and rerunYou now have a query that will segregate based on groups6. Use the kdestroy command to delete the Kerberos ticket-granting ticket.FTS v4.0• An FTS server installation supports up to 50 iNEWS systems.FTS Installation and Configuration ProcedureThe new installation and configuration procedure for FTS server version 4 is provided here.To install and configure FTS:1. Navigate to the FTS folder on the iNEWS installation DVD and click Setup.exe.11

Version 4.0.3 ReadMeThe InstallShield Wizard starts and displays a Welcome dialog box.2. Click Next.The License Agreement dialog box appears.3. Read the Avid Software License Agreement, accept the terms, and click Next.12

Version 4.0.3 ReadMeThe Destination Folder dialog box appears.4. (Optional) Click Change if you want to alter the default installation location. Otherwise, you canaccept the default and click Next.5. Click Install when you are ready to begin the installation.When the InstallShield Wizard completes the installation successfully, the following dialog box13

Version 4.0.3 ReadMeappears.6. Select the Launch Avid FTS Configuration check box and click Finish.You are now ready to configure the system. The Fast Text Search configuration window appears.By default, no services are active.7. Click Configure to configure the FTS_1 services.14

Version 4.0.3 ReadMeThe default configuration values will appear, as shown in the following illustration.8. Set the Active field to ACTIVE.9. Set the System Name to the name of the iNEWS system to be associated with this service.10. (Optional) Modify the ports and index path.11. Click Save.A warning might appear to indicate if the Index Path Folder, indicated in the Index Path field, doesnot exist.12. Click Yes to create the folder at the configured path.The firewall exceptions, service configurations, and index path are created at this time.13. Click Back to return to the main configuration window and start the services. The configurationwindow will now display the active services with the configured system name.14. Configure additional systems by selecting unused FTS_# entries from the list.15

Version 4.0.3 ReadMeStopping and starting services should be performed from the Fast Text Search configurationwindow, using the Pause and Play buttons next to the relevant system name. Even though theservices will appear in the Windows Services list, all stopping and starting should be performedfrom the FTS management UI.15. By default, logs and index bases are stored in C:\ProgramData\Avid\FTS in Windows Server 2008R2 and in C:\Documents and Settings\All Users\Avid\FTS in Windows XP and 2003.If FTS needs to be uninstalled, all FTS entries should be set to “DISABLED” prior to theuninstall.Below is sample output from ftsdebug…NRCS-A$ ftsdebug index statisticsService name: ftsindex1Version: 4.0.0.33Process id: 2364Started: 12/20/11 07:30:47Debug value: 0Tuning:onIndex Base:C:\ProgramData\Avid\FTS\NRCSiNEWS System: nrcsPort: 6100Current Index: 000Total Documents: 39736Requests Serviced: 95081000 File sizes (KB): 25702/25660 16376/1 15823 116

Version 4.0.3 ReadMeDocuments: 34076 Added: 39724 Removed: 5651 Replaced: 3Purged: 0001 File sizes (KB): 592/543 572/1 1215 1Documents: 3174 Added: 3174 Removed: 11 Replaced: 11Purged: 0003 File sizes (KB): 2540/2528 2547/1 1086 1Documents: 2486 Added: 2486 Removed: 2 Replaced: 2Purged: 0010 File sizes (KB): 4/0 4/1 3 1Documents: 0 Added: 7 Removed: 7 Replaced: 0 Purged:0An index rebuild is required when upgrading to FTS 4.To build the iNEWS index:‣ Perform the following commands:• ftsdebug index statistics — This confirms communication with the FTS Indexservice.• ftsdebug search statistics — This confirms communication with the FTS Searchservice.• list c fts — This displays the ftsseek and ftsindex device numbers (ftsseek# andftsindex#).• stop — This stops the FTS devices.• dbpurge system.index 0 — This clears any unhandled index requests.• dbpurge system.fts 0 — This clears any unhandled search requests.• dbtraits . reindex > /dev/null & — This creates an index request for eachindexed queue. The output is sent to /dev/null because of output volume.Note: Alternatively, more important wires and recent archives can be added to the index beforeadding the full database during the reindexing.• start — This restarts the FTS devices.Upgrade Notes and IssuesThis section contains information related to upgrading from previous versions of iNEWS.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. Afterthe dbrestore, the administrator must run dblines c: to index the new BUCKET queues. After that aniNEWS user will be able to go to the BUCKET queues and select their preferred index base.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.0.2 and 4.0.3• In previous releases, cursor movement (typing) would become extremely sluggish in very large iNEWSstories. This has been fixed.17

Version 4.0.3 ReadMe• In previous releases, a story containing a MOS production cue in an iNEWS rundown produces a BadEvent 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 hasbeen fixed.• In previous releases, the @ starter character was interpreted as an e-mail address in system keyboards. Thisbroke older system keyboard macros and prevented users from creating new system keyboard macros. Thishas been fixed.• In previous releases, line breaks were sometimes stripped from production cues. This has been fixed.• In previous releases, the cursor focus appeared at the start of pasted text instead of at the end. This has beenfixed.• 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 DeviceStatus ISAM files. Logins can fail when the t/u index file is corrupt and monitor can fail when the MonitorDevice 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 queues could crash the iNEWS clientunder Windows XP. This has been fixed.• In previous versions of iNEWS, diskcopy performance was slow at high copy levels and over-taxing at lowcopy levels. This has been fixed.• In previous versions of iNEWS, if you added "DEKOMOS DEKOMOS" as an 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 rightareas of the navigation bar. This has been fixed.Changes between 3.5.3 and 4.0Server• In previous version of iNEWS 3, iNEWS worked on 32-bit operating systems with 1k blocks. Beginningwith iNEWS v4.0, this has changed. The iNEWS newsroom computer system version 4.0 runs on RHEL 664-bit with 4k blocks.• User credentials are now passed to server using encryption. This functionality happens on the backend andis invisible to iNEWS users, so there is no change to the user interface.• In previous versions of iNEWS 3, forced logouts from the server would lose the user's last known locationand instead default to Project tree view the next time they logged into iNEWS. This is fixed.• In previous versions of iNEWS 3, UTF16 code was being replaced with the wrong surrogate code. This isfixed.Searching• Beginning with iNEWS v4.0, date variables have been added as options in the Search Queue and Find Alldialog boxes.18

Version 4.0.3 ReadMeThe options are documented in more detail in the following table:OptionTodayTomorrowDescriptionRange = 00:00:00 through 23:59:59 of present dayRange = 00:00:00 through 23:59:59 of tomorrow19

Version 4.0.3 ReadMeOptionYesterdayNext WeekThis WeekLast WeekNext MonthThis MonthLast MonthNext QuarterThis QuarterLast QuarterDescriptionRange = 00:00:00 through 23:59:59 of yesterdayRange = 00:00:00 of next Sunday through 23:59:59 of next SaturdayRange = 00:00:00 of this Sunday through 23:59:59 of this SaturdayRange = 00:00:00 of prior Sunday through 23:59:59 of prior SaturdayRange = 00:00:00 of the first day of next month through 23:59:59 of the lastday of next monthRange = 00:00:00 of the first day of this month through 23:59:59 of the lastday of this monthRange = 00:00:00 of the first day of prior month through 23:59:59 of the lastday of prior monthRange = 00:00:00 of the first day of first month of next quarter through23:59:59 of the last day of last month of next quarterRange = 00:00:00 of the first day of first month of this quarter through23:59:59 of the last day of last month of this quarterRange = 00:00:00 of the first day of first month of prior quarter through23:59:59 of the last day of last month of prior quarterNote: Quarters are defined as:1 st quarter = January 1 st through March 31 st2 nd quarter = April 1 st through June 30 th3 rd quarter = July 1 st through September 30 th4 th quarter = October 1 st through December 31 stNext YearThis YearLast YearRange = 00:00:00 January 1 st through 23:59:59 December 31 st of next yearRange = 00:00:00 January 1 st through 23:59:59 December 31 st of this yearRange = 00:00:00 January 1 st through 23:59:59 December 31 st of prior yearWorkstation• In previous versions of iNEWS, when a new user account was created without MAIL and NOTES queues,messages would appear informing you that those queues could not be found. Beginning with iNEWS v4.0,MAIL and NOTES queues are automatically created when new user accounts are made; therefore, pop-upwarnings about queues not being found no longer appear.• In previous versions of iNEWS 3, stories that contained invalid encoded characters would fail to ingestproperly. This is fixed.• In previous versions of iNEWS 3, {Alt} combination keystrokes would insert bad characters after using theSGT application. This is fixed.• In previous versions of iNEWS 3, queue's named with special characters, and queues inside folders namedwith special characters could not be searched against because the special character corrupted the searchstring. This is fixed.• In previous versions of iNEWS 3, some characters were not copy and pasted from iNEWS story body toother 3rd party products such as Microsft Word. This is fixed.20

Version 4.0.3 ReadMe• In previous versions of iNEWS, duplicate WIRES.DISTRIBUTION lines would cause wires to terminatethe news program. This is now fixed.• In previous versions of iNEWS 3, story links inside script templates were not active without userintervention to add a space or carriage return to the end of the story link instead of being activeimmediately upon import. This is fixed.Spell-checker• In previous versions of iNEWS 3, certain lines of text would cause iNEWS to hang when spell check wasrun. This is fixed.• In previous version of iNEWS 3, when cursor was placed inside of a word, spell check would find aspelling error for the last part of that word. This is fixed.MOS Integration• In previous versions of iNEWS 3, spaces could be entered into the item-channel field that would be sent tothe MOS device, which would result in the wrong channel assignment. This is fixed.• In previous versions of iNEWS 3, editing stories with MOS cues in the Web client would add a spacebetween the AMCPID and template ID, which could cause problems with some customer automation. Thisis fixed.• In previous versions of iNEWS 3, MOS time updates were not updating their times in the iNEWS story.This is now supported.New FeaturesThis section contains a listing of new features.For iNEWS v4.0Users• This version of iNEWS provides the optional ability to import users. For more information, see“Installation Notes and Issues” on page 7.• This version of iNEWS provides the ability to set a user account as an External User. For moreinformation, see “Installation Notes and Issues” on page 7.Searching• In this version of iNEWS, the searching and Find-All features were enhanced to include user-definable datevariables. For more information, see “Searching” on page 18.BUCKET Queues• The iNEWS newsroom computer system now offers BUCKET queues as part of its existing Projectsfeature. 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 as follows:To create new story inside of a project:1. On the Project tab, navigate to the project’s queue in which you want to add the story, such as:BUCKET, ALL, or FACET.2. Create the new story.• New stories created in either the BUCKET or ALL queues are automatically associated to theproject and cannot be de-associated from it, although they can be associated to any other project orfacet as well.The following illustration shows a newly created story in the ALL queue, associated to theEducation project.21

Version 4.0.3 ReadMeThe following illustration shows a newly created story in the BUCKET queue, associated to theEducation project.• New stories created in the FACET queue are associated to the FACET by default and displayedinside of it. De-association of a story created in the FACET queue does not delete the story fromthe project’s bucket.22

Version 4.0.3 ReadMeMOS Integration• iNEWS v4.0 now lets users insert MOS object placeholders within iNEWS stories in either the story formor as a story’s production cue. The procedures for doing so are as follows:To insert a MOS object placeholder:1. Right-click while mouse pointer is either in the Story Form panel or in the Story Text panel.2. Select Insert Placeholder.3. Select the MOS device.4. Enter a new slug or use the default.23

Version 4.0.3 ReadMe5. (Optional) Enter a description.6. Click OK.If you right-clicked in the Story Form panel, the new MOS object placeholder appears in the storyform.If you right-clicked in the Story Text panel, the new MOS object placeholder appears as a productioncue in the Instruction panel.The MOS device user can update the placeholder with a real ID and object by turning on or loading themonitor server. MOS Gateway will then return data back to iNEWS where the placeholder is located ineither the story form (below at left) or production cue (below at right).For iNEWS v3.5FTS• The iNEWS Server now logs a diagnostic when any queue is added or removed from indexing. This featureallows tracking index rebuild progress without scheduling ftsdebug index statistics commands. The firstdiagnostic reports the start of indexing, and the second diagnostic reports total number of documentsindexed.Dec 22 10:20:03 NRCS-B S120: Queue WIRES.ALL::add:0:-1:-1:024

Version 4.0.3 ReadMeDec 22 10:23:24 NRCS-B S120: Queue WIRES.ALL 11226 addsBlockmode Command• Some customers send many changing stories via FTP to third party FTP servers. This can consume manyTCP port numbers and with a large TIME_WAIT setting prevents the reuse of those port numbers. Thiscan lead to “port exhaustion,” that is, no ports available for further transfers. When using Stream TransferMode, the end-of-file is denoted by the closing of the data connection, hence the need for a new connectionfor every transfer. Block Transfer Mode includes end-of-file information in the data so the data connectioncan be kept open for successive data transfers. This can be used when the iNEWS proprietary FAST modecannot be used.The syntax is: blockmode [no|yes]If Yes or No is not declared, blockmode all by itself assumes a value of Yes.Note: To function correctly, the blockmode command must be placed after thescan/bscan/poll/bpoll command and before the open command. The blockmode command willtake precedence over the fast command default.For iNEWS v3.4.5This section contains a listing of new features implemented in iNEWS v3.4.5.CommunityBecause of upcoming expansion to allow databases larger than 16GB, the iNEWS Communitycommunication protocol was modified. This modification breaks compatibility with iNEWS Server version3.4.4 and earlier. iNEWS 3.4.5 still supports Community communication with either iNEWS 3.4.5 orearlier for systems with a small database, but for those with large databases, Community communication issupported only with iNEWS 3.4.5 and later. Both simultaneously are not supported. All 2.x and 3.x serversshould be upgraded to at least 3.4.5 when a large database server is added to the community.By default, iNEWS 3.4.5 is configured to support Community communication with large databases. Eventhough it is still a 16GB database, a 3.4.5 default configuration is considered a large database in regard toiNEWS Community.To configure iNEWS 3.4.5 as a small database:‣ Create the file /site/env/gnews. In this file, place the following line:GCOMMUNITYSMALLDATABASE=1.For example:NRCS-A$ cat /site/env/gnewsGCOMMUNITYSMALLDATABASE=1Rules:• A single community cannot have both small and large databases.• iNEWS 3.4.4 and earlier cannot be in a community with large database servers.• Large database servers cannot be in a community with small database servers.• iNEWS 3.4.5 can be in a community with iNEWS 3.4.5 if both systems have the sameGCOMMUNITYSMALLDATABASE setting, large or small.25

Version 4.0.3 ReadMeTroubleshooting:Below are the error messages and the cases in which they will appear:Case3.4.5 Largeconnecting to 3.4.4 orearlier3.4.4 or earlierconnecting to 3.4.5Large3.4.5 Largeconnecting to 3.4.5Small3.4.5 Smallconnecting to 3.4.5LargeError Messagelocal: G###: Error (1) during SETCOMMUNITY to remote: C###: Cannot service request: eBlocal: G###: Unable to set community server number with (9)remote: C###: Cannot participate in small database communitylocal: G###: Unable to set community server number with (9)remote: C###: Cannot participate in large database communitylocal: G###: Unable to set community server number with (9)remote: C###: Cannot participate in small database communitySYSTEM.MAP SyntaxThe SYSTEM.MAP syntax has changed slightly. For iNEWS Command (wnasvr) CGs, there is now anoptional sixth column. When blank, the value defaults to YES. When this column is set to "NO," iNEWSmonitor will not validate style names before sending CGs to Command. This change allows the loading ofCG items to the Command playlist before they exist in Command’s inventory. wnasvr cg For iNEWS v3.4.0This section contains a listing of new features implemented in iNEWS v3.4.0.Mapcheck UtilityThe mapcheck utility validates all stories in a designated queue. Errors are produced for any syntaxviolations, missing queues (rundown, composite, or event), and trait omissions.For example, typing mapcheck -f system.map at the console will make the system analyze allstories in SYSTEM.MAP. It sets the monitored trait for any listed rundowns that do not have the trait set,and it reports any syntax errors in SYSTEM.MAP. Mapcheck should be run after an upgrade to 3.4 and aspart of error investigation.NRCS-A$ mapcheckusage: mapcheck [-v] [-f] Flagsf - Fix monitored traitv - Verbosevv - Very verbosevvv - Very very verbose26

Version 4.0.3 ReadMeSYSTEM.MAP QueueThe entire SYSTEM.MAP queue is now used to define rundowns. The behavior is similar to theSYSTEM.RESOURCE queue, where separate stories can be used to segregate rundown definitions intocategories, such as ”morning”, “afternoon”, and “evening”. Multiple small stories are easier to manage andmaintain than the one large story used previously.Restrictions:• A single rundown’s definition cannot span stories.• The same rundown cannot appear in separate stories; only the first instance will be consulted.For iNEWS v3.3.0This section contains a listing of new features implemented in iNEWS v3.3.0.Desktop IconThe iNEWS v3.3 client software has a new desktop icon on the workstation. The new icon is shown at left.Projects and Facets• The iNEWS system now supports projects and facets. Projects are a way of categorizing stories by topic sothat news teams working on a particular topic can find everything related to it in a single place, withoutmoving or copying original source information within the database. Facets are sub-topics of projects thatprovide additional granularity. For more information about projects and facets, see the iNEWS Projectschapter in the Avid iNEWS v3.3 Setup and Configuration Guide.Search Queues• The iNEWS system now supports search queues. A search queue is a special queue that stores a predefinedquery of indexed queues, along with its own queue form and read group. When users with properread access open a search queue, a fast text search (FTS) is activated, and the results are delivered to theworkspace in the Queue panel instead of the Search Results pane. For more information about searchqueues, see the section called “Search Queues” in the Database: Directories, Queues, and Stories chapter ofthe Avid iNEWS v3.3 Setup and Configuration Guide.Queue Templates• The iNEWS system now provides a Copy From Template button in the Directory/Queue Properties dialogbox. Templates are created as queues in SYSTEM.PROPERTIES, and once created, they can be used tohelp speed up the process of configuring directories or queues in the iNEWS database. For example, aqueue named SYSTEM.PROPERTIES.RUNDOWN can be created and assigned all standard rundowntraits: Inverted, Refresh, Monitored, Save All, etc. When a user selects the Copy From Template button,they will see "RUNDOWN" as an option. Selecting that option will apply the traits fromSYSTEM.PROPERTIES.RUNDOWN to the queue they are currently editing. For more information aboutcopying queue templates, see the section called “Database Traits Summary” in the Database: Directories,Queues, and Stories chapter of the Avid iNEWS v3.3 Setup and Configuration Guide.For iNEWS v3.1.0This section contains a listing of new features implemented in iNEWS v3.1.0.27

Version 4.0.3 ReadMeScript Templates• iNEWS now supports a new feature called Script Templates. Script templates are templates created by anadministrator for users to quickly insert predefined text into stories. The database structure for scripttemplates is the same as the structure used for forms and lists:SYSTEM.SCRIPT-TEMPLATES..For example, if a standard weather story has a set of production cues and presenter text that are always thesame, you can create a story in SYSTEM.SCRIPT-TEMPLATES.W.WEATHER. In this story, place thestandard text, presenter text, and production cues found in the weather story. After the template story issaved, the template is available to users via the Story menu or through an option in the Story Text subpanel’scontext menu.To use a script template:1. Right-click in the Story Text sub-panel.2. Select Insert Script Template. A Templates dialog box will appear with a list of all availabletemplates.3. Enter the name or select the template from the list.4. Click OK.After the template is chosen, the template is inserted in the story’s body at the cursor position.Note: This new feature can replace the use of complex macros currently used to insert templatematerial.NewsCutter media• iNEWS can now stream material created using the NewsCutter NRCS Tool 8.0.5 feature that inserts aproduction cue into the story when a user creates a new sequence from a story. If the production cue is notcreated when the sequence is created, iNEWS will not be able to stream the mixdown. Depending on theNewsCutter version used to create the production cue, the cue displayed in the iNEWS client will either bea full MOB ID or simply a read-only {N}.For iNEWS v3.0.0This section contains a listing of new features implemented in iNEWS v3.0.0.Hyperlinks• iNEWS now supports the addition of hyperlinks in the story body. Links can be in the form of http:// orwww. E-mail addresses are also recognized. A user preference is available defining whether clicked links28

Version 4.0.3 ReadMewill launch into an Internet Explorer workspace within the iNEWS application, or into the user’s defaultbrowser outside of the iNEWS application.Story links• iNEWS now supports creating story links. When focus is on a story, the context menu and the story menuhave available the “Copy story link to clipboard” option. When this option is selected, it creates a story linkon the user’s clipboard. This link can be pasted into another story and will appear as:inews:////. Clicking the link will create a new workspace displayingthe linked story.Comboboxes• Form fields can now be assigned predefined values. When these fields are used in a form, the user ispresented with a drop-down list instead of a text field. These fields are called comboboxes.To create a combobox:1. Edit a field property or insert a new field.You will notice a new section named Type on the right side of the Form Properties dialog box.2. Select the Combobox radio button.• Include Blank Row means there will be a blank row provided before the list entries.• Editable means a user can type their own value into the combobox in addition to selecting apre-existing value• The New button allows the administrator to create ad-hoc values that will appear in thecombobox, instead of using a system list or group• The Delete button removes an existing entry.• The Up/Down buttons are used to reorder the values in the combobox.• The Add List/Group button presents a dialog to the user in which they can select system listsand groups to be added to the combobox. will appear in front of a group name, and will appear in front of a list name.• The color boxes show the current system colors. Colors can be assigned to individual entriesor to entire groups and lists. To add a color, select the entry row and then select the desiredcolor. A "," will appear after the entry, indicating which color index is assigned to theentry.Check boxes• A new field type, check box, is now available in forms. Any user-created field type can be assigned as acheck box. The values saved are "1" for checked and blank for unchecked, allowing use with raw queriesand affects-ready. Check boxes can be selected with the mouse or with the spacebar. Check boxes willalways have the "Text alignment" attribute set to "Center."Duration• A new field type, duration, is now available in forms. Any user-created field type can be assigned as aduration field. Duration fields use spinners to display duration in the form, HH:MM:SS.29

Version 4.0.3 ReadMeCalendar• A new field type, calendar, is now available in forms. Any user-created field type can be assigned as acalendar field. Calendar fields use spinners to set and store dates. The dates default to a time of 00:00:00,but times can be added if more specificity is needed.Field write groups• Individual fields can now be assigned write groups. Only group members and superusers are permitted toedit those fields. The write group is assigned in Form Properties.Editorial groups• Another group type, editorial group, has been added to iNEWS. Members of the editorial group can delete,move, float, and break stories. If no editorial group is assigned, the relevant permissions apply to the writegroup to stay consistent with previous functionality.Colors• There is now a queue that holds system colors. By default, the colors reside in the queueSYSTEM.COLORS (/site/dict/queues:Q_COLORS sytem.colors). The first story in SYSTEM.COLORSdefines the system's colors.The syntax is a four-column list. The first column is the index of the color, from 1 to 10. The secondcolumn is the RGB red value. The third column is the RGB green value. The fourth column is the RGBblue value. The color values are numerical, from 000 to 255.Example:1 255 000 000 ; red2 000 255 000 ; green3 255 255 000 ; yellowOnly indexes 1 to 10 are accepted. Syntax errors in SYSTEM.COLORS will cause no colors to bedisplayed.Community: When in a community, the colors displayed for a client will be the colors of the local server,regardless of the location of the queue they are currently viewing.Lists• The ability to create system lists has been added. By default, the lists reside in the directorySYSTEM.LISTS (/site/dict/queues:Q_LISTS /system.lists). The structure of the SYSTEM.LISTS directoryis the same as the SYSTEM.FORMS structure, where the first character in the list's name defines whichsub-folder holds the list. For example, a list called "format" is the first story in the queueSYSTEM.LISTS.F.FORMAT.The lists are used for combobox form fields.The syntax of a list is a two-column story. The first column holds the text value. Double-quotes should beused if special characters or spaces are used in the text value. The second column holds the backgroundcolor index value. The second column is optional, and no color is used if the column is blank.Example, using the colors defined above: SYSTEM.LISTS.S.STOPLIGHT30

Version 4.0.3 ReadMeStop 1Go 2"Slow Down" 3"No Light"; the value "Stop" has a red background color; the value "Go" has a green background color; the value "Slow Down" has a yellow background color; the value "No Light" has no background colorPlay Interplay Low-res Streams• Low-res streams created by Interplay 2.0.1 and later can now be played through the iNEWS client. SeveralInterplay components are required for this workflow: iNEWS Instinct, Interplay Transcode, InterplayStream Publish, Interplay Media Services, and Interplay Stream Server. QuickTime 7.5 must also beinstalled on the iNEWS client machine.• When Instinct associates a sequence with an iNEWS story, the iNEWS client will display a context optioncalled “Play Low-res Video.” When this option is selected, iNEWS will contact the Interplay server toretrieve the streaming URL. If the sequence has been mixed down and published to a streaming server,iNEWS will then disconnect from the server and open a QuickTime window inside the iNEWS client. TheQuickTime application will automatically play the available stream.• The queue SYSTEM.INTERPLAY (/site/dict/queues: Q_INTERPLAY) must exist for this workflow to besupported. The first story in SYSTEM.INTERPLAY is a four-column story. The first column is the indexof the Interplay server, starting with 0. The second column is the hostname of the Interplay server. Thisname must be resolvable by the iNEWS Workstation. The third column is an optional column holding theusername to be used when connecting to Interplay. The fourth column is an optional column holding thepassword to be used when connecting to Interplay. If the third and fourth columns are blank, the iNEWSusername and password will be used to connect to Interplay.o 0 interplay1o 1 interplay2 streamuser streampass• Interplay servers can be assigned to individual directories using the dbtraits command or theDirectory/Queue Properties dialog. All directories default to Interplay 0.o dbtraits show.sports interplay 1o dbtraits show.weather interplay 2• ‘list d-i ’ displays the Interplay server associated with the directory.Qualified Asian Languages and IMEsKoreanThe 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 menuoption does not allow direct navigation to folders with Korean-text names.31

Version 4.0.3 ReadMeChinese SimplifiedThe following Chinese Simplified (PRC) IME (standard Windows IMEs) is tested and qualified:• Microsoft Pinyin IME 3.0• WangMa Wubi 86• WangMa Wubi 98Chinese TraditionalThe following Chinese Traditional IMEs (standard Windows IMEs) are tested and qualified:• New ChangJie• New Phonetic• ChangJie• Phonetic• DaYiThe following Chinese Traditional IMEs (3 rd party IMEs) have had minimal testing done and are not yetqualified or supported:• Boshamy (WuXiaMi)• Natural InputJapaneseThe following Japanese IME (standard Windows IME) was tested and qualified:• Microsoft Standard IME 2002 version 8.1VietnameseThe following Vietnamese IMEs were tested and qualified:• UniKeyNT 3.6ooInput Methods: Telex and VNICharacter Set: Unicode• Vietkey 2000 Build 10727o Input Method: Telexo Character Set: Unicode Pre-CompoundKnown Issue with both Vietnamese IMEs - Certain Vietnamese characters do not get inserted correctlyvia keyboard macro when the IME is set to Vietnamese input. The workaround for this issue is to set theIME to English input before starting the macro.Microsoft Windows Critical UpdatesAvid recognizes that it is very important to be able to deploy Microsoft security patches to our Windowsbasedproducts as quickly as possible. We recommend that systems be kept up to date in order to maintainthe highest level of security and encourage you to install all critical operating system updates provided byMicrosoft.In the unlikely event that one of these updates causes an issue, it is recommended that you uninstall theupdate and contact Avid customer support as soon as possible. Avid will investigate the incompatibility and32

Version 4.0.3 ReadMeif necessary, will provide a software update or work around to allow our products to properly function withthe Microsoft update in question.Known Issues and LimitationsPlug-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.33

Version 4.0.3 ReadMeUNC Paths• As a result of the server-side URL changes in iNEWS 3.4.2, UNC paths with spaces no longer workcorrectly in the iNEWS client software. In a future version of the iNEWS client software, these links willbe client-only, allowing a user to launch them from the iNEWS Workstation without saving them as URLson the iNEWS Server.• Third-Party IntegrationiNEWS 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 inprinting.• 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 Xmediatree to be inaccessible.KeyboardsWorkaround: When this issue occurs, the workaround is to rename or remove skinCrafter3_vs2008.dllfrom the Assignment List installation directory.• Some early versions of iNEWS 3 created NSML links in SYSTEM.KEYBOARDS. When the dblinescommand fixes those links, they become invalid keyboards. To repair the keyboards, remove the excesswhitespace at the beginning and the middle of the keystroke line.iNEWS Web Services API• The iNEWS Web Service API cannot be undeployed via the Tomcat management interface when Tomcat isrunning on a Windows host.To undeploy in Windows:Multiple Monitors1. Stop the Tomcat service2. 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 isrunning on a Linux host.• If running the iNEWS client software on a dual monitor workstation, there are some key issues you couldencounter:• If the application is maximized at close, 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 thearrow keys on the keyboard; this will lock the application’s window to the mouse. You can then move themouse 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 withmacros that perform several functions in rapid succession; the macros might not complete all assigned34

Version 4.0.3 ReadMeactivity in iNEWS. Avid is working with Microsoft on this issue. This issue is most apparent with macrosthat 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 followingthe 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 exactlythe name of the dialog box as it appears in the title bar. The ‘K_WINDOW /window’ token can be changedin /site/dict/keymacros.Another available workaround is to add {pause } statements of one or two seconds to problem macrosat the point in the macro where activity ceases. In the example of the Local Printing macros, the pauses arelikely needed when typing a name of a printer or changing a print style.Technical Support InformationMost products feature a number of coverage options. Avid Assurance service offerings are designed tofacilitate your use of Avid solutions. Service options include extended telephone coverage, automaticsoftware maintenance, extended hardware warranty, and preferred pricing on replacement parts. Offeringsand 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 at800-949-AVID (800-949-2843).Program availability and details might vary depending on geographic location and are subject to changewithout notice. Contact your local Avid office or your local Avid Reseller for complete programinformation 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 userscall 978-275-2480.Accessing Online SupportAvid Online Support is available 24 hours per day, 7 days per week. Search the Knowledge Base to findanswers, to view error messages, to access troubleshooting tips, to download updates, and to read/joinonline 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 KnowledgeBase. For the latest up-to-date information, browse the Knowledge Base at Avid Online Support.35

Version 4.0.3 ReadMeCopyright and DisclaimerProduct specifications are subject to change without notice and do not represent a commitment on the part ofAvid Technology, Inc.The software described in this document is furnished under a license agreement. You can obtain a copy of thatlicense by visiting Avid's Web site at www.avid.com. The terms of that license are also available in theproduct in the same directory as the software. The software may not be reverse assembled and may be used orcopied only in accordance with the terms of the license agreement. It is against the law to copy the softwareon any medium except as specifically allowed in the license agreement.No part of this document may be reproduced or transmitted in any form or by any means, electronic ormechanical, including photocopying and recording, for any purpose without the express written permission ofAvid Technology, Inc.Copyright © 2013 Avid Technology, Inc. and its licensors. All rights reserved.Attn. Government User(s). Restricted Rights LegendU.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are “commercial computer software” or“commercial computer software documentation.” In the event that such Software or documentation is acquired byor on behalf of a unit or agency of the U.S. Government, all rights with respect to this Software anddocumentation are subject to the terms of the License Agreement, pursuant to FAR §12.212(a) and/or DFARS§227.7202-1(a), as applicable.TrademarksAdrenaline, AirSpeed, ALEX, Alienbrain, Archive, Archive II, Assistant Avid, Avid Unity, Avid Unity ISIS, AvidVideoRAID, CaptureManager, CountDown, Deko, DekoCast, FastBreak, Flexevent, FXDeko, iNEWS, iNEWS Assign, iNEWSControlAir, Instinct, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, Interplay, ISIS,IsoSync, LaunchPad, LeaderPlus, ListSync, MachineControl, make manage move | media, Media Composer, NewsCutter,NewsView, OMF, OMF Interchange, Open Media Framework, Open Media Management, SIDON, SimulPlay, SimulRecord,SPACE, SPACEShift, Sundance Digital, Sundance, Symphony, Thunder, Titansync, Titan, UnityRAID, Video the WebWay, VideoRAID, VideoSPACE, VideoSpin, and Xdeck are either registered trademarks or trademarks of AvidTechnology, Inc. in the United States and/or other countries.All other trademarks contained herein are the property of their respective owners.Avid iNEWS v4.0.3 ReadMe • 9390-65146-00 D • 2 March 2013This document is distributed by Avid in online (electronic) form only, and is not available in printed form.36