inews Newsroom Computer System

Transcription

1 a inews Newsroom Computer System Version ReadMe Revision History Date Revised Changes Made 9 January 2007 Initial Version 6 February additions listed (Final edit ) Important Information Avid recommends that you read all the information in this ReadMe file thoroughly before installing or using any new software release. Note: Search the Avid Knowledge Base ( 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 inews 2.6 will be more widely distributed than previous inews 2.5.x 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 2.5.x ReadMe files for additional change information not contained in this ReadMe.

2 Contents Important Information... 1 Compatibility Notes and Issues... 4 inews Client... 4 inews Server... 4 Command... 4 ControlAir... 4 MOS Gateway... 4 Console Multiplexer... 4 Data Receiver... 4 Fast Text Search... 4 Instinct... 4 NewsCutter... 4 Teleprompter... 4 Qualified Asian Languages and IME s... 5 Changes made between inews and Support for inews Command... 5 New Features in inews Server... 6 inews Client... 6 Installation Notes and Issues... 7 Upgrading from Previous Versions... 7 inews Client... 7 inews Server... 7 Important inews Changes... 7 New Features in Release New Toolbar Button and Directory Panel Icons... 8 Improved Spellchecking Capabilities... 9 Legacy Client Support... 9 Hardware and Software Changes... 9 User Interface Queue Panel Production Cues Toolbars Server

3 Avid Instinct Highwater/Lowwater Defaults Monitor Txnet/Rxnet Console Commands FTP Interface Forms Mail Validation Remote Search Connections COM Connections Known Limitations Not Supported in inews Fast Text Search (FTS) Miscellaneous SYSTEM.MAP Format Changes Microsoft Windows critical updates Technical Support Information Accessing Online Support

4 Compatibility Notes and Issues The inews release consists of the following versions: inews Server version inews Client version inews Client The inews client software is qualified and supported for use on Windows 2000 Professional (SP4), Windows 2000 Server (SP4), Windows XP Professional (SP2) and Windows Server 2003 (SP1). inews is not officially supported for use on any other Windows operating system. inews Server The inews Server is qualified and supported for use on Red Hat Enterprise Linux 3.0. Command The inews Server is qualified and supported for use with Command 1.0 or later. ControlAir The inews 2.6 system is qualified and supported for use with ControlAir 1.6.x or later. MOS Gateway The inews 2.6 system is qualified and supported for use with MOS Gateway 2.6.x 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 2.6 system is qualified and supported for use with Data Receiver 1.5 or later. Fast Text Search The inews 2.6 system is qualified and supported for use with Fast Text Search 2.5. If upgrading from any FTS version prior to 2.5, a full re-index is required. Instinct The inews 2.6 system is qualified and supported for use with Avid Instinct 1.1 and 1.6 or later. NewsCutter The inews 2.6 system is qualified and supported for use with NewsCutter NRCS Tool or later. Teleprompter The inews 2.6 system supports the following teleprompter software: WinPlus BDL Unicode version WinCue version 1.30 (build 619) 4

5 Qualified Asian Languages and IME s Chinese Simplified The following Chinese Simplified (PRC) IME (standard Windows IME s) is tested and qualified: Microsoft Pinyin IME 3.0 Chinese Traditional The following Chinese Traditional IME s (standard Windows IME s) are tested and qualified: New ChangJie New Phonetic ChangJie Phonetic DaYi The following Chinese Traditional IME s (3 rd party IME s) 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 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 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. Changes made between inews and Support for inews Command inews includes support for inews Command, which is the new playback system replacing AirSpeed Countdown. Syntax Checking changes with inews and Command - There is syntax checking for Command, but it differs slightly from ControlAir. For video, the only checking is for channel values in CA; it 5

6 must be a letter Aa-Za. For command, the channel can be any string. For CGs, Command no longer uses the SYSTEM.RESOURCE stories to look up style information; CA still does. But, with the most recent changes, the monitor must connect to the Command Server at MON ON to obtain a list of valid style names for the channel group and environment. Only the style name is checked for Command. New Features in Maximum number of user groups increased from 250 to 700 In previous versions of inews, the maximum number of user groups on system was 250. This limit has been increased to 700. A dbgen m and dbgen s must be run on the server in order to support this new feature. Spell check language persistence Spell check language is now saved across a user's sessions. Fine control over text shading in script print - Previous versions of inews did not allow control of shading level when printing. Three new printing options have been added to SYSTEM.STYLES. The options allow the user to assign RGB values to the shading levels of Closed Captions, Presenter Instructions, and Machine Instructions. 1. WinCCShading default = 128, 128, 128 defines shading of Closed Captions 2. WinPIShading default = 224, 224, 224 defines shading of Presenter Instructions 3. WinMIShading default = 128, 128, 128 defines shading of Machine Instructions inews Server Monitor uses duplicate addresses for two CGs In certain situations, inews would assign the same address to two CGs in a rundown. This problem has been resolved. Monitor sends message to MOS Gateway out of order Using a set of specific steps, monitor would send messages out of order to the MOS Gateway. This caused a failure to correctly update events on the MOS device. This problem has been resolved. MOS channels assignments are cleared when floating a story In previous versions of inews 2.6, floating a story with a MOS item in the form area would cause the item-channel field to be cleared. The item-channel for a MOS item should not be cleared when a story is floated. This problem has been resolved. TXNET not sending wire distribution codes TXNET was failing to send wire distribution codes when transmitting stories causing a failure to distribute stories correctly on the receiving system. This problem has been resolved. inews Client Read messages not available after closing/opening message bar The inews client software had an issue where read messages would not be available through the up/down arrows after the message bar had been closed and opened. This issue has been resolved. Ctrl+R hot key for toggling search results not working The inews client software had an issue where Ctrl+R would show search results, but it would not hide search results. This issue has been resolved. Spell check is disabled when the cursor is in a production cue The inews client software had an issue where spell check was disabled when cursor focus was in a production cue. This issue has been resolved, and spell check can run in production cues and in the story body. 6

7 MOS Status and Channel assignment are cleared when a story is floated The inews client had an issue where floating a story would cause the MOS status and the channel assignment to be cleared. This issue has been resolved. Custom dictionary words are cleared when maximum dictionary size is exceeded inews had an issue where all custom dictionary words would be cleared if the custom dictionary exceeded the character limit. This issue has been resolved. The character limit for custom dictionaries is now Users who exceed this limit will receive a warning, and their custom dictionary will be truncated to 1024 characters. Alt+Keypad character insertion does not work in story body inews had an issue where characters typed using Alt+Keypad (example: Alt+0225 = á) were not inserted properly into the story body. This issue has been resolved, and the character is inserted when the Alt key is released. Installation Notes and Issues Upgrading from Previous Versions When upgrading to inews from any version earlier than 2.5.3, the following actions must be taken: dbgen m and dbgen s must be run to support the new feature that allows for over 250 user groups to be created on the system. The new maximum limit is 700 user groups. inews Client When installing or upgrading inews on Windows XP or Windows Server 2003, you must have adequate user rights to install the client software. Windows XP/Server 2003 Install as restricted user (will fail) Install as standard user (Power User) (will work) Install as administrator (will work) This is not a restriction in the inews client install, but is a restriction of the Windows operating system in that it is upholding the security restrictions on the PC. Note: During the install procedure, inews client versions 2.5 and higher will not provide an option to upgrade from inews versions 2.1 and lower. Please uninstall inews 2.1 or lower before installing inews 2.5 or higher. inews Server Kernel version EL (and ELsmp) is now the latest qualified version of the Linux kernel. This kernel version is included with RedHat Enterprise Linux 3.0 ES Update 8. Important inews Changes New format for SYSTEM.MAP Beginning with inews 2.5.0, ControlAir and MOS Gateway Server information was separated from the device information. Support for CCU/PCU and MCSPC devices was removed. Refer to the System Map Format Changes section of this document for details on the new map story format. If an old-format SYSTEM.MAP is used the following error is generated: Can t get monitor data on this queue; No devices to monitor. 7

8 The syntax of the /site/config file was changed. Beginning with inews the following keywords are no longer valid: o Net o Driver o Line o Mcspc o Pcu o Printer o Special o Unused o Wire The valid config file syntax for a 2.6 system is: host <system> <computer> reslist <resource 1>... servers <server 1>... com <devid> <IP/ethernet address> <name> <device name> aiws <devid> <IP/ethernet address> <name> <device name> inws <devid> <IP/ethernet address> <name> <device name> resource <devid> <name> <resource i/o device> rsearch <devid> <IP/ethernet address> <name> <device name> server <devid> <name> <notify> <devname> webclient <devid> <IP/ethernet address> <name> <device name> websession <devid> wireserver <devid> <program name> <source name> <'join' or '-'> Wordlength must be between 1 and 100 Beginning with inews 2.5.0, the wordlength parameter in /site/system must be between 1 and 100. Setting the wordlength to 0 for word counting is no longer valid. The inews Server will not connect if the wordlength is out of range. The value for wordlength is now established during the server install; there is no default. Keyboard macro stories must have inws in the index field. Beginning with inews 2.5.0, the following are no longer allowed: anws and asws. VT keyboards are no longer supported. All VT keyboard stories should be removed. Local Databases from inews 2.1.x and earlier are converted at login When you log in to inews 2.6 and you have a local database from an inews 2.1.x or earlier system selected, the stories in the local database will be converted while you login. You will see a progress screen as the conversion takes place. This process could take several minutes, depending on how many stories exists in your local database. New Features in Release 2.6 This section provides information on any previously undocumented enhancements or new features added to this release. New Toolbar Button and Directory Panel Icons The inews 2.6 client has added new graphical icons for the toolbars and the directory panel. 8

9 Improved Spellchecking Capabilities Starting in inews 2.6, all supported language spell check dictionaries are installed with the inews client. As a result, you can now set the spellchecking language on the fly and spell check your desired language quickly and easily. This can be done by selecting Tools-Set Language. See the picture below: Legacy Client Support Legacy inews clients can now connect to the inews 2.6 server. Previously, only inews 2.6 clients could connect to an inews 2.6 server. Legacy clients consist of: inews 1.2.x through inews 2.1.x Web Client 1.0 Pre-2.6 COM clients The character set to use for legacy client sessions is controlled by the environment variable LEGACY_CHARSET in /exc/.profile on the inews server. The inews server will install and configure this automatically when you install the server software. The LEGACY_CHARSET environment variable needs to be entered as follows in /exc/.profile: export LEGACY_CHARSET=<code page> The default character set configured is CP1252. You can see a list of available character sets by typing iconv l. Hardware and Software Changes The following changes were made to inews Version

10 User Interface Server Queue Panel Writable Total-Time field A new feature has been added that allows users to manually enter a time into the Total-Time field, similar to the way you can manually enter a time into the Audio-Time field. The writable Total-Time field will allow users to manually enter a time value for the entire story that will override the time entries for the Audio-Time, Tape-Time, and Runs-Time fields. Production Cues Default production cues cause Story Save Failed error in zoom mode Previous versions of inews would result in a Story Save Failed error if the master story form contained two or more production cues. The problem would occur when you inserted a new story (with a form that contained two or more production cues) while in zoom mode and then tried to save the story. This problem has been fixed. Special formatting causes Story Save Failed error Previous versions of inews would fail to save certain types of formatted text that was pasted into a production cue. Pasting Normal (Web) formatted text from MS Word would result in the story not being saved properly to the server. This problem has been fixed. Moving production cues with the "Delete Production Cue" confirmation turned on Previous versions of inews prompted the user to confirm production cue deletion when the cue was actually just being dragged elsewhere in the story. This issue has been fixed. Toolbars Right-clicking in the toolbar area with no workspaces open causes crash Previous versions of inews would crash if the user did a right click in the toolbar area when there were no open workspaces. This problem has been fixed. Avid Instinct Avid Interplay Instinct 1.6 no longer licensed by the inews Server Beginning with inews server, Avid Interplay Instinct 1.6 is no longer licensed by the inews server, rather Instinct 1.6 will be licensed by the Interplay Engine. However, older Instinct versions, such as 1.0 and 1.1 will still be licensed via the inews server. Due to this change, the /site/config file will now have two types of Instinct resources, including a NEW resource type called aiws for Avid Interplay Instinct sessions (the iiws resource will still exist for older Instinct versions, such as 1.0 and 1.1). The aiws resource will be identical to the way the previous Instinct ( iiws ) resources were defined in /site/config, except they are now called aiws and they are not actually licensed. The sole purpose of the aiws resource type is to allow Instinct to connect into inews to see the inews stories database and stories, however the licensing is handled by the Interplay Engine. See the example below for how the aiws and iiws resource types are configured in the /site/config file: ; INTERPLAY INSTINCT 1.6 SESSIONS aiws 700:709 - gnews - ; Interplay Instinct ; INSTINCT 1.1 SESSIONS iiws 710:719 - gnews - ; Instinct 10

11 Invalid anchor contents Some situations when inews communicated with Instinct caused anchor elements to contain invalid IDs or extraneous text. This issue has been fixed. Highwater/Lowwater Defaults Highwater and Lowwater defaults reset Previous versions of inews had the following defaults set in /site/system/: lowwater = 1250, and highwater = These defaults have been changed to and , respectively. Monitor Style names larger than 8 characters marked invalid In previous versions of inews, the monitor program would accept and store CG/SS style names longer than 8 characters, but an issue in the parser would cause it to fail to actually match the longer style names. This has been fixed. Monitor fails to update queue after reordering stories Previous versions of inews would hang when moving and reordering stories containing production cues with Machine Instructions. This would result in mirrored rundown queues failing to update. This problem has been fixed. Txnet/Rxnet Location of Rxnet environment variable changed Beginning with inews 2.5.1, Rxnet environment variable are located in /site/env/rxnet instead of /site/env/nxserver. IO handler locked block problem with Txnet rundown mirroring Some customers were having problems with the IO handler block 1 getting into a locked state when doing rundown mirroring with a sorted queue if the txnet joblist contained the order command. This has been fixed. Rxnet Character Set Option Since inews 2.5.1, Rxnet now supports the CHARSET= SITE command and honors the RXSITECHARSET environment variable setting for the client character set. All data received from the client will be converted from the specified character set into Unicode. The sequence U+HHHH will be converted into a Unicode value where HHHH is the hexadecimal value. Rxnet Sendform Option Since inews 2.5.1, Rxnet now supports the SENDFORM= SITE command and honors the RXSITESENDFORM environment variable setting. A value of 1 means to include embedded forms when exporting a story to a client. A value of 0 means to omit embedded forms. This is the default and the current behavior. This feature allows form stories to be exported. Rxnet check Presenter Read Rate Since inews 2.5.1, Rxnet now checks the contents of the PRESENTER field on incoming stories. The story readrate will be changed if the user name is found. The readrate will be set to the system default if the PRESENTER field is empty. If the PRESENTER name is not found in the user account file, the readrate set in the story is retained. If the environment variable RXNOPRESENTER is present in /site/env/rxnet and is non-zero the old rxnet behavior is used, that is, no readrate adjustment via the PRESENTER field. Rxnet finds attribute changes Rxnet will now pick up changes to the current working directory attributes (permissions and mailbox settings) once per minute. This allows changes to be made without having to restart the FTP connection. Txnet Character Set Option In inews 2.5.1, a charset directive was added to txnet for specifying the character set of the receiving FTP or inews Server. The syntax for the directive is charset <charset>. A list of character sets can be retrieved from Linux by typing the iconv l command. The charset directive must come before the open directive in a txnet joblist. The character set specified in a txnet directive will set the character set on the receiving server, overriding the receiving server s default character set. The SITE CHARSET=<charset> command will be sent whenever a txnet session connects to an 11

12 FTP or inews Server. The default character set is UTF-8 if the charset is not specified in the joblist. Here is an example joblist: scan txnet.source charset CP1252 open nrcs-a txuser put txnet.destination Txnet Sendpassword Option In inews 2.5.1, a sendpassword directive has been added to txnet for sending password for including passwords with user locked stories when they are exported. When the sendpassword directive is specified in a txnet joblist, txnet will include <password>password text</password> in the NSML document that is exported. When such a story is received on an inews 2.5 system, the password will be stored in the story and can be used to view this user locked story. When using the sendpassword directive with an easy locked story, the username used in the txnet joblist will be the user that controls the easy lock on the receiving inews 2.5 system. Console Commands Maketab commands have changed - While the maketab program remains the same, the makeccutab program has been removed and the makemctab program has been renamed to makemontab. Dbrestore Character Set Option - A CCS option was added to dbrestore in inews for restoring database from pre-2.5 systems. The syntax for the option is CCS <charset>. A list of character sets can be retrieved from Linux by typing the iconv l command. For example, to restore an inews 2.0 database that used the English 1252 codepage, you would add the -CCS CP1252 option to your dbrestore command. New option to view user group numbers in gtraits A new gtraits option (-number) was added that allows you to view the number of a user group when using the list- option. See example below: gtraits -number list- list t has been removed The list t command is no longer supported. list s should be used to display session information. Dbvisit not checking mailbox file for enough records As part of the group number increase, dbvisit, invoked through configure i, now checks for a sufficient number of mailboxes. The configure will not complete if too few mailboxes are present. Utraits clone option now copies custom toolbars In previous versions of inews the utraits clone option would not copy customer toolbars to cloned users. This has been fixed. FTP Interface Allow cd.. command to get to root directory In previous versions of inews, if a user did not have read access to a queue or folder above their current directory, they could not use the cd.. command to traverse back up to the root directory. Now, in an effort to allow clients to easily get back to the root directory from wherever they may currently be, the cd.. will allow users to move directories up even if they don t have read access to that directory. Listing the contents of a directory without having read access is not allowed. An example benefit from this is better integration with the NewsCutter NRCS tool. Forms Cannot sort on AUDIO-TIME field Previous versions of inews did not allow sorting on the AUDIO-TIME field. This functionality has been added. 12

13 Mail Server name appended to user ID Server name is now stripped from mail recipient names. Validation Validation server creates messages for invalid user Previous versions of inews generated validation queue error messages that were sent to a nonexistent user account. This issue has been fixed, and the proper user receives the error messages. Remote Search Connections Remote Search client version checking has been removed - The inews 2.6 server no longer uses the SYSTEM.CLIENT.RS-VERSIONS queue for doing version checking of Remote Search clients. The version checking of Remote Search clients was deemed unnecessary and was removed. Therefore, the SYSTEM.CLIENT.RS-VERSIONS queue can also be removed. COM Connections COM client version checking has been removed - The inews 2.6 server no longer uses the SYSTEM.CLIENT.COM-VERSIONS queue for doing version checking of COM clients. The version checking of COM clients was deemed unnecessary and was removed. Therefore, the SYSTEM.CLIENT.COM-VERSIONS queue can also be removed. Known Limitations This section provides information on known limitations that were not addressed in this release. Any available workaround procedures are also documented, when possible. Note: For limitations related to compatibility of this release with previous versions/other products, see the section of this document entitled, Compatibility Issues. Not Supported in inews 2.6 PCUs are not supported. This includes support for System Printing and the MCT. Wire ingest must be configured through an Avid Data Receiver. MCS PCs are not supported. The SEP format is not supported for txnet. A sendpassword directive was added to replace the SEP format password element. See the inews Server enhancements below for more information. Fast Text Search (FTS) Regular re-indexing may be required due to FTS database corruption problem There is a known issue with the FTS version where the FTS database can become corrupted and require re-indexing of the stories in order for FTS searching to work properly again. Miscellaneous Wire distribution Urgency level is overwritten by the last destination listed If the same destination is listed for multiple category code patterns, the urgency level setting (SILENT, FLASH, BULLETIN, URGENT) used when that destination is included in a story distribution will be the setting on the last occurrence of the destination in the wire distribution list for a given wire. Using same username in inews 2.1 and 2.6 is not recommended If a user will be connecting into both an inews 2.1 and inews 2.6 systems, it is recommended that the user create separate usernames for each system. Using the same username to log in to inews

14 and inews 2.6 will cause that user s preferences to become corrupted. This is an unlikely scenario but could occur at large customer sites that have multiple inews systems. Titling/CG templates not functional when connecting via 2.1 client inews 2.1 and prior clients connecting to a 2.6 server will not be able to access character graphics functionality. Connect to Service not functional when connecting via 2.1 client inews 2.1 and prior clients connecting to a 2.6 server will not be able to access connect to service functionality. System Print is not supported after inews 2.1 inews 2.1 and prior clients have an option for system printing, but the client connection will terminate if system printing is attempted from a 2.1 client that is connected to a 2.6 server. SYSTEM.MAP Format Changes Overview: The format for entering device information in the SYSTEM.MAP story has changed significantly. SYSTEM.MAP stories from earlier releases of inews, Avstar, AvidNews or Avid Netstation must be modified for the monitor server to execute. One reason for the change is that, beginning with the 2.5 release, only ControlAir and MOS Gateway device managers are supported. CCU/PCU and MCS PC device managers are no longer available. The changes simplify configuration of CA and MOS Servers. The Rundown Information line does not change. The format for that line is still 5 fields separated by white space: <RD queue> <EL directory> <CL queue> <monitor group> <monitor offtime/duration> Device information lines are changed. Now, ControlAir or MOS Gateway server information is added on a separate line, followed by a separate device information line for each device manager configured on that server. The available configuration options have not changed, but the format for entering them has. Some options, like backup server and device alias, which were previously separated by a comma (,) have become separate, required fields. The backup server and CAWS form fields are entered on the server information line. The obsolete update field was removed. The CG address range and the still store stack are now separate fields from the drive and directory information. A new field for the CG template drive and directory was added. New Format: The information line for a server contains 4 fields separated by white space: <server type> <server name> <backup server> <CAWS form> The options for server type are CASVR and MOSSVR. The server name is the network resolvable address of the server machine. The backup server field may contain a placeholder if no backup server is configured. If the CAWS form field contains a placeholder, the story form assigned to the composite list queue will be used. If no composite list queue is configured, the story form assigned to the rundown queue will be used. For best performance, a CAWS form should be created and assigned here. That form should contain only the title and pagenumber fields and all other fields configured for display in the CAWS story rows. All device information lines share three required fields, device type, device name and alias name, followed by device-dependent information. The alias name field may contain a placeholder if an alias is not used. A device alias name provides a means to enter generic production cues into stories which may be resolved to different device names when those stories are copied to different rundown queues. The default alias name for any device manager is the device type. When a production cue is processed, the device name in the cue is compared to the device list for that rundown. If no match is found, the alias list is searched. If a match is found in that list, the production cue is assigned to the corresponding device manager. Duplicate device names are not allowed. 14

15 However, alias names are not checked for uniqueness. If an alias applies to two or more devices, the first in the list will be selected. Still store and CG drive and directory fields still use a colon (:) to separate two components. A placeholder (-) or single colon will cause both to be empty. CG devices can now specify a separate drive and directory where template messages are stored on the CG. In the past, template messages had to be stored in the same directory where the completed messages are built. The CG address offset field is optional. If entered, it is the number of CG addresses to skip when a new story is parsed before assigning new addresses for the next story. When new CG's are added to a story in a monitored rundown, the monitor program re-assigns all the addresses within that story to keep them contiguous. Using this option will reduce the number of times adding a new CG causes the address range to shift to a higher set of numbers. The format for each of the four device types is: video <device name> <alias name> <channel assignment agent> ss <device name> <alias name> <drive>:<directory> <stack name number> cg <device name> <alias name> <msg drive>:<msg dir> <tmpl drive>:<tmpl dir> <start address> <end address> <address offset> mos <device name> - Examples: For example, a video device manager airspace and cg device manager max on server casvr1 would change from: video airspace@casvr1 update bcs-bcw 3 cg max@casvr1 update - C:MAX: to casvr casvr1 - bcs-bcw video airspace - 3 cg max - C:MAX If these device managers were configured on separate ControlAir Servers video and fonts, the new format would be: casvr video - bcs-bcw video airspace - 3 casvr fonts - bcs-bcw cg max - C:MAX Here s an example where all the options are used: video airspace@casvr,bsvr update bcs-bcw 3 cg max@casvr,bsvr update - C:MAX: cg deko1,deko@casvr,bsvr update - C:MSG: ss pbox@casvr,bsvr update - shared::900 mos sony@mosgw update - becomes: casvr casvr bsvr bcs-bcw video airspace - 3 cg max - C:MAX

16 cg deko1 deko C:MSG ss pbox - shared: 900 mossvr mosgw - - mos sony - Note: The new format allows the addition of a different template message drive and directory for the CG devices. For example, you could add a template drive and directory to the max device like this: cg max - C:MAX D:TEMPLATES Microsoft Windows critical updates Avid recognizes that it is very important to be able to deploy Microsoft security patches to our Windowsbased 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. 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 s service offerings, visit or call Avid Sales at AVID ( ). 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 or call in North America AVID ( ). International users call 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 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. 16

17 Copyright and Disclaimer Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc. The software described in this document is furnished under a license agreement. You can obtain a copy of that license by visiting Avid's Web site at The terms of that license are also available in the product in the same directory as the software. The software may not be reverse assembled and may be used or copied only in accordance with the terms of the license agreement. It is against the law to copy the software on 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 or mechanical, including photocopying and recording, for any purpose without the express written permission of Avid Technology, Inc. Copyright 2007 Avid Technology, Inc. and its licensors. All rights reserved. Attn. Government User(s). Restricted Rights Legend U.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 by or on behalf of a unit or agency of the U.S. Government, all rights with respect to this Software and documentation are subject to the terms of the License Agreement, pursuant to FAR (a) and/or DFARS (a), as applicable. Trademarks 888 I/O, Adrenaline, AirPlay, AirSPACE, AirSPACE HD, AirSpeed, AniMatte, AudioSuite, AudioVision, AutoSync, Avid, Avid DNA, Avid DNxcel, Avid DNxHD, AVIDdrive, AVIDdrive Towers, Avid Mojo, AvidNet, AvidNetwork, AVIDstripe, Avid Unity, Avid Unity ISIS, Avid ISIS, Avid Xpress, AVoption, AVX, CamCutter, ChromaCurve, ChromaWheel, Command, DAE, D-Fi, D-fx, Digidesign, Digidesign Audio Engine, Digidesign Intelligent Noise Reduction, DigiDrive, Digital Nonlinear Accelerator, DigiTranslator, DINR, DNxchange, D-Verb, Equinox, ExpertRender, FieldPak, Film Composer, FilmScribe, FluidMotion, HIIP, HyperSPACE, HyperSPACE HDCAM, IllusionFX, Image Independence, Intraframe, is9, is18, is23, is36, LaunchPad, Lo-Fi, Magic Mask, make manage move media, Marquee, Matador, Maxim, MCXpress, Media Composer, MediaDock, MediaDock Shuttle, Media Fusion, Media Illusion, MediaLog, Media Reader, Media Recorder, MEDIArray, MediaShare, Meridien, MetaSync, MissionControl, NaturalMatch, Nearchive, NetReview, NewsCutter, Nitris, OMF, OMF Interchange, OMM, Open Media Framework, Open Media Management, ProEncode, Pro Tools, QuietDrive, Recti-Fi, RetroLoop, rs9, rs18, Sci-Fi, Softimage, Sound Designer II, SPACE, SPACEShift, SpectraGraph, SpectraMatte, Symphony, Trilligent, UnityRAID, Vari-Fi, Video Slave Driver, VideoSPACE, and Xdeck are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries. inews, inews ControlAir, and Media Browse are either registered trademarks or trademarks of inews, LLC. All other trademarks contained herein are the property of their respective owners. inews ReadMe Rev. A 21 March