IC3 Advanced Configuration Options

• Font Exclusion List
• IC3 MMOS.INI Options Applying to All Products
• IC3 NetManager MMOS.INI Options
• IC3 NetManager and Player MMOS.INI Options
• IC3 Designer and Player MMOS.INI Options
• IC3 Designer MMOS.INI Options
• IC3 Player MMOS.INI Options
• IC3 Add-on EX MMOS.INI Options

Font Exclusion List

Scala uses intelligent file transfer to avoid uploading or downloading files that are already present. However, font licensing rules generally require that fonts be transmitted with their documents (Scala scripts), which defeats the benefit of intelligent file transfer. This is not a big issue with Western fonts because of their comparatively small size, but with Asian fonts this can be a significant issue.

Starting with Release 7, IC3 Designer supports a "font exclusion list". In an InfoChannel network, if a set of fonts is known to be pre-installed on all players, then naming these fonts in the font exclusion list will cause them to be not included by default when publishing to InfoChannel networks. (By default, fonts not on the exclusion list are published as normal.)

In the Advanced Publish Options menu, the Include Fonts? option still allows you to exclude all fonts. If you choose to include fonts, the new Exclude Standard Fonts? option lets you control whether the fonts on the exclusion list are excluded or transmitted.

The list of excluded fonts itself is an XML file that can be found at:

Modifying this file is straightforward, but care must be taken to only list fonts that are indeed present on all players. Otherwise, a player may receive a script without all the necessary fonts, which can produce an incorrect display and run-time errors.

Advanced Configuration Using MMOS.INI

Most IC3 products have a variety of advanced configuration options available through the use of the MMOS.INI file. MMOS.INI is a file that lives in the program's installation folder, e.g. D:\Scala\ICPlayer or C:\Program Files\Scala\ICDesigner3, or wherever your Scala product(s) are installed. Normally, each installation folder can have its own MMOS.INI file with its own settings.

In Release 6 and earlier, the MMOS.INI file is in ANSI format. Starting with Release 7, the MMOS.INI file can be UTF-8, in which case it should begin with the UTF-8 byte-order mark, which consists of the hexadecimal values EF BB BF.

The MMOS.INI file begins with the optional byte-order mark, followed by the word [Scala] as shown inside square brackets, followed by one or more lines of the form

Anything after a semi-colon is treated as a comment and is ignored by the Scala applications.

Here is a simple example:

and so on.

You may find you already have an MMOS.INI file. If you do, you may wish to review which settings are already in force. But remember, anything after a semi-colon is a comment and does not have any effect.

If you do not have an MMOS.INI file, it is a simple matter to make one in any text-editor such as Notepad.

IC3 MMOS.INI Options Applying to All Products

• WIN32_RootDataFolder: Control the location of all Scala config files, logs, settings, temporary files, etc.
  WIN32_RootDataFolder = path

  When set, Scala data that is normally stored under the Windows-standard configuration areas is stored instead under the specified path. Also the Scala temporary folder appears under the specified path. Thus, most of the locations where Scala reads and writes files can be controlled.

  This is the simplest way to move the locations where such files are stored. There are additional MMOS.INI keywords to move specific folders such as the Content and InstalledContent folder, but it is often better to move them all with this one keyword.

• DIALOG_OutputUTF8: Force Scala logs to be in the UTF-8 Unicode format.
  DIALOG_OutputUTF8 = 1

  When set, Scala log files such as ic.log and the Billing EX logs will be stored in UTF-8 even on Western installations of Scala.

• LOG_Days: Control how many days worth of logs are kept by the Scala applications.
  LOG_Days = n

  Tells Scala to retain n days worth of logs. Logs past this number will be removed from the system. The default value is seven days.

  (For Player starting with Release 7.4, you may use the setting in ConfigIC instead.)

• WININET_DefaultTimeoutInSeconds: In some case, FTP transfers would fail to time out correctly. In Release 6d, this was fixed with a default time-out of 5 minutes. The default can be overridden via the MMOS.INI variable.
  WININET_DefaultTimeoutInSeconds=n

  (Added in Release 6d, no longer needed as of Release 7)

• WININET_EnableServUDirectoryCacheKludge: The directory caching of the Serv-U FTP server can return incorrect results. Scala recommends that directory caching be disabled when using the Serv-U FTP server. However, if this is not possible you can enable a workaround by adding this to your MMOS.INI:
  WININET_EnableServUDirectoryCacheKludge = 1

  (The workaround will hurt media transfer performance.)

• SSCOMMON_ForceNeverUseWininetForFTP: If a proxy server has been selected in the LAN Settings of Microsoft's Internet Options, IC3 will fall back to the Wininet FTP client, which was always used in Release 6 and earlier. To force use of the Release 7 (and up) built-in FTP client, add this to your MMOS.INI:
  SSCOMMON_ForceNeverUseWininetForFTP=1

  (Added in Release 7.1)

• TCPIPTOOLS_FTPClientKeepAliveCommandChannel: Setting this instructs the FTP client to set the socket "keep-alive" option on the FTP command channel. This can resolve certain command-channel timeouts that can sometimes be caused by intervening firewalls or routers. To enable this, add the following to your MMOS.INI:
  TCPIPTOOLS_FTPClientKeepAliveCommandChannel=1

  (Added in Release 7.2)

IC3 NetManager MMOS.INI Options

(See additional options that apply to both IC3 NetManager and Player.)

• SSERVER_ReplaceRemoteFTPRootFolder: Give players a different URL to the transmission workspace.

  The Transmission Workspace Location setting in NetManager can be an FTP URL. This URL is used by both NetManager and by the Players for uploading and downloading files. In unusual network configurations, the player may need to use a different URL for accessing the same place (and it does need to be the same place). Use:

  SSERVER_ReplaceRemoteFTPRootFolder = ftp://user:password@ftp.domain.com/path

  in NetManager's MMOS.INI file to cause NetManager to instruct the Players to use this alternate URL, while NetManager continues to use the one specified in System Settings.

• SSERVER_HNSDefaultResubmitDeliveryPriority: When the broadcast priority feature of Hughes package delivery is enabled, then a selector allows control over the priority of the resubmitted job. The default priority for resubmitted jobs is controlled by adding this to your MMOS.INI:
  SSERVER_HNSDefaultResubmitDeliveryPriority=n
  where n can be 0 (low priority), 1 (medium priority), or 2 (high priority).

  (Added in Release 7.4)

• SSERVER_EnableIPMulticastSettingsOverride: If you set the mmos.ini keyword
  SSERVER_EnableIPMulticastSettingsOverride=1
  then you can specify three additional data items per Broadcast Server, namely:
  • Group IP Address
  • Multicast Interface Address
  • Maximum Transmission Speed
  These effectively override the matching settings within the Broadcast Server, allowing the user to create multiple virtual Broadcast Server entries within NetManager, each pointing at the same physical Broadcast Server, but having unique values for the above properties.
• NETMANAGER_EnterpriseOnConsole: NetManager Enterprise can now officially be used console-style. This is essentially a single-user version of NetManager Enterprise, allowing functionality such as groups and broadcasting. Add this to your MMOS.INI:
  NETMANAGER_EnterpriseOnConsole=1
  then invoke the NetManagerConsole.exe application after starting the NetManager engine.

IC3 NetManager and Player MMOS.INI Options

These MMOS.INI Options apply to both IC3 Network Manager and IC3 Player:

• SSCOMMON_EncryptionKey: Set custom encryption key for protecting usernames / passwords.

  The InfoChannel Network encrypts all usernames and passwords that are transmitted or stored. Health monitoring messages are also encrypted, and job command files and responses are sealed as well. You can select your own custom encryption key by setting:

  SSCOMMON_EncryptionKey = encryption-key-string

  Set this on both NetManager and all Players or else things will not function. Note that there is no support for migrating stored usernames/passwords from one key to another, so this key is best established from the beginning.

  encryption-key-string should be 5-7 characters in length (40 to 56 bits).

• SSCOMMON_ChineseAndKoreanLegacyCompatibility: Prior to Release 7.3.1, there was a bug in Player and NetManager which prevented Chinese and Korean installations of Windows from interoperating with installations in other languages.

  In newer releases, this is fixed by default for new networks. However, for existing Chinese or Korean networks, there are two options:

  • The legacy option allows the existing network to continue to run, but in NetManager and all current and future Players, you must add the following to each MMOS.INI file:
    SSCOMMON_ChineseAndKoreanLegacyCompatibility=1
    In the legacy option, interoperability with other languages will not be supported.
  • The modern option is the default (no MMOS.INI keyword required), but existing Chinese and Korean networks will need their Player settings and their NetManager databases and settings rebuilt. Once this is done the network will work again, and interoperability with other languages will be possible.

  The installer will detect affected systems and warn the user.

  The NetManager Install Software Update command will automatically add the MMOS.INI keyword to any affected player because in this case it is certain that the legacy option is desired (otherwise the player will become remotely broken).

  (Added in Release 7.3.1)

IC3 Designer and Player MMOS.INI Options

These MMOS.INI Options apply to both IC3 Designer and IC3 Player:

• MEDIA_InstalledContent:

  Normally, when a Scala script references some media, that media is sent along with the script when the script is published to an InfoChannel Network. However, any media that is Linked Content is not sent with the script that references it. Such content either needs to be sent separately, using the Send Content NetManager command, or needs to be installed, delivered, or generated on the player.

  (Note: When installing, delivering, or generating content on the Player, the ScalaIntegration DLL contains useful features you should understand and use.)

  When resolving references to Linked Content, the Scala software first looks in the Content folder, and if the file is not found there, it looks in the InstalledContent folder. The reason for two folders and the essential difference is that:

  • The Content folder is managed by the Player network engine, i.e., things sent via Send Content are placed here.
  • The InstalledContent folder is for content managed outside of ICPlayer, e.g., placed here by Reporter or by any custom integration application.
  One big difference is that the Delete Unused Content command will not touch files in the InstalledContent folder.

  By default, the Content and InstalledContent folders are placed side-by-side as

  Documents and Settings\All Users\Documents\Scala\Content
  Documents and Settings\All Users\Documents\Scala\InstalledContent

  but the WIN32_RootDataFolder keyword overrides this to

  WIN32_RootDataFolder\Documents\Content
  WIN32_RootDataFolder\Documents\InstalledContent

  Setting MEDIA_InstalledContent can be useful for:

  • IC3 Designer, to support a group of authors who wish to have their Linked Content shared on a LAN. (Set MEDIA_InstalledContent to a shared folder on the network.)
  • IC3 Player, for installations with a hand-delivered ("sneaker-net") partition or folder location. (Set MEDIA_InstalledContent to the desired partition or folder location.)
  • IC3 Player, for installations with multiple players at one site where bandwidth over the internet to that site is more critical than bandwidth over the LAN at that site. (Add an additional player (or designate one player) as that site's "Linked Player", and use Send Content to deliver large video files to the Linked Player only. For all other players, set their MEDIA_InstalledContent to the regular content folder of the Linked Player. When the other players reference the video as linked content, they will play it over the LAN each time is is needed.)

  (Added in Release 4)

• DESKTOP_Borderless/TopMost/CustomPosition: IC3 Player can now run on the desktop as a top-most borderless window of arbitrary or full size. You can specify the left, top, width and height. As an example, add this to your MMOS.INI:
  DESKTOP_Borderless = 1
  DESKTOP_TopMost = 1
  DESKTOP_CustomPosition = 100 50 800 600

  Omitting DESKTOP_CustomPosition will make the window fill the primary display.

  These options are also supported by IC3 Designer.

  (Added in Release 4)

• SOUND_DisableCDAudio: To disable CD-audio within the Sound EX, add:
  SOUND_DisableCDAudio = 1

  to your MMOS.INI file. In order to play CD-audio, the Sound EX normally has to lock the CD drive when playback begins, making the drive unavailable for CD-ROM data use. This setting ensures the drive can always be used for data, on systems that do not need CD-audio.

  (Added in Release 6)

• DSHOWRENDER_OverlayKeyColorBGR: Lets you set the overlay key color used for Movie() and MovieClip() elements. The default value is a very dark green. You can override with any color other than true black by using:
  DSHOWRENDER_OverlayKeyColorBGR = 0xBBGGRR

• DSHOWRENDER_UseSafestRecognition: When Scala tries to identify files as video, it sometimes needs to invoke third-party CODECs installed on the system. Rare combinations of these CODECs with certain media files can crash. By setting
  DSHOWRENDER_UseSafestRecognition = 1

  Scala will only use more conservative ways to identify video files.

• Various Hollywood Plus settings: When using the MCI MPEG EX with the Hollywood Plus card, consider the following settings:
  
  HOLLYWOODPLUSMCIKLUDGE = 1
  MCIKLUDGE_SHRINKSWITCHOUTDISABLE = 1
  MCIMPEGWATCHDOGTIMEOUTMS = time in milliseconds
  MCIMPEGFAILEDCMD = path to program

  HOLLYWOODPLUSMCIKLUDGE=1 causes Scala to explicitly turn off video when done, and has a workaround to provoke the hardware driver to release its resources.

  MCIKLUDGE_SHRINKSWITCHOUTDISABLE = 1 shrinks the time in which the Scala switch-out detection is disabled.

  MCIMPEGWATCHDOGTIMEOUTMS = n creates a watchdog that triggers a custom command after n milliseconds of non-response to an MCI command. Set MCIMPEGFAILEDCMD to the program that should be run when this occurs.

• XDRAW_AlwaysSingleBuffer: Scala uses double- or triple-buffering to achieve smooth graphical effects. (This means the program is drawing into a different copy of screen memory than what's displayed, and then flips the new one into view in place of the old one.) On various SiS chipsets, and on the VIA "Nehemiah" chipset, the act of flipping buffers consumes a lot of CPU. This can result in sub-ideal performance, and becomes more acute with the changes in Release 6. To work around this, you can force single-buffering by adding this to your MMOS.INI:
  XDRAW_AlwaysSingleBuffer = 1

  (Added in Release 6)

• XDRAW_CommitToVideoBufferWithCPU: Instructs Scala to use the CPU to commit display updates to the video buffer using the CPU. This optimization can noticably reduce the time it takes to update the display on some nVidia-based cards, which helps keep the frame rate as high as possible. This optimization is most noticable when wiping in large foreground elements that cause a significant portion of the display to change from one frame to the next. Scala is investigating whether this change is also an improvement on other cards. To try it out, add this to your MMOS.INI:
  XDRAW_CommitToVideoBufferWithCPU = 1

  (Added in Release 6a)

• OPTIBASE_IgnoreHardware: When set, the Optibase EX will cleanly work in the absence of the hardware. This can be useful for example when using the Publish Server to publish scripts with Optibase events, using a Designer that does not have the Optibase card installed.
  OPTIBASE_IgnoreHardware=on

  (Added in Release 6d)

• ANIMEX_AllowEarlyPrepare: WinDVD 5 can crash with the back-to-back movie playback optimizations introduced in Release 7.1. As a workaround, those optimizations can be disabled by adding this to your MMOS.INI:
  ANIMEX_AllowEarlyPrepare=0

  (Added in Release 7.1)

  (WinDVD 3 and WinDVD 4 do not have this problem. It is possible that some revision of WinDVD 5 may address the problem as well.)

• DSHOWRENDER_IgnoreIncompleteStateChange: If when playing a streaming video, you encounter an error that The operation could not be performed because the filter is not running, this can be resolved by setting the MMOS.INI keyword:
  DSHOWRENDER_IgnoreIncompleteStateChange=1
  (We may enable this by default in the future)

  (Added in Release 7.3.1)

• XDRAW_SimulateFullScreenVBlankFlip and XDRAW_SimVBlankSleepThreshold: These settings enable a workaround for frame-synchronized display updates, to benefit certain ATI systems and for VIA S3 systems. The traditional approach used to work well but broke down on ATI Radeon-based devices with recent drivers. On such systems, the drivers end up consuming excessive CPU which badly impacts performance. The VIA S3 chipset always had this issue. To enable the workaround, add the following to your MMOS.INI file:
  XDRAW_SimulateFullScreenVBlankFlip=1
  A companion MMOS.INI setting can be used to fine-tune behavior:
  XDRAW_SimVBlankSleepThreshold=3
  This governs how close to the estimated start of vertical blank Scala switches to an accurate but CPU-intensive way of waiting. Setting the number too high will use too much CPU and affect performance. Setting the number too low can cause the vertical blank to be missed, producing a visual stutter. The default value of 3 milliseconds should be OK in most cases.

  (Added in Release 7.4)

IC3 Designer MMOS.INI Options

(See additional options that apply to both IC3 Designer and Player.)

IC3 Player MMOS.INI Options

(See additional options that apply to both IC3 Designer and Player, and to both IC3 NetManager and Player.)

• SSCLIENT_TurnOn/OffAtHour: Restrict ICPlayer network activity to certain hours.

  You can specify a start and stop time for any Scala network communication. For example, you can say:

  SSCLIENT_TurnOnAtHour = 18
  SSCLIENT_TurnOffAtHour = 8

  This tells ICPlayer to restrict its InfoChannel network activity to the hours between 6 pm and 8 am. No network traffic (and no auto-dialing) will occur between 8 am and 6 pm.

  Note that this also means no health monitoring activity during the "off" hours. You will need to set a suitable Overdue Heartbeat Tolerance value in NetManager's System Settings to avoid players being reported as dead during these "off" hours.

  (Added in Service Pack 2)

• SSCLIENT_ThrottleFTPMaxKiloBitsPerSecond: To throttle player network bandwidth consumption, use:
  SSCLIENT_ThrottleFTPMaxKiloBitsPerSecond = n

  where n is the number of kilobits per second (kilobit = 1000) to which Player should limit its average data rate when actively transferring.

  (Added in Release 5. Starting with Release 6, also governs health monitoring traffic)

  (Starting with Release 7.4, you may use the settings in ConfigIC instead.)

• SSCLIENT_TurnOn/OffFTPThrottleAtHour: To control the hours when player network bandwidth throttling applies, use:
  SSCLIENT_ThrottleFTPMaxKiloBitsPerSecond = n
  SSCLIENT_TurnOnFTPThrottleAtHour = 7
  SSCLIENT_TurnOffFTPThrottleAtHour = 22

  to throttle FTP data transfer to a rate of n kbps during the business hours of 7 am till 10 pm. Outside those hours (i.e. from 10 pm until 7 am the next morning), FTP downloads occur at maximum possible speed because throttling is turned off during that period.

  (Starting with Release 7.4, you may use the settings in ConfigIC instead.)

• SSCLIENT_OverrideJobLogin...: Allow per-player User Name and Password to access job data.

  Normally, all players will retrieve their job data using the User Name and Password specified for the Transmission Workspace Location in NetManager's System Settings.
  For networks where the players need to log in with per-player credentials, the new MMOS.INI keyword

  SSCLIENT_OverrideJobLoginFromCustomSettings = 1

  tells the players to instead use the per-player User Name and Password (already established in ConfigIC for accessing the job commands) to also access the job data in the Transmission Workspace Location.

  For systems where the Player's Job Folder is a shared folder, then there is no existing User Name and Password. In that case, use the MMOS.INI keyword:

  SSCLIENT_OverrideJobLoginURL = ftp://user:password@ftp.domain.com/path[:port]

  to specify the replacement User Name and Password. The ftp.domain.com/path[:port] must match the transmission workspace — otherwise the account information will not be altered.

• NETIC_Reboot: Control whether the ICPlayer network engine reboots or restarts when it processes a Reboot job command. The normal behavior is to reboot, but if you want the network engine to restart without rebooting, set:
  NETIC_Reboot = off

• RUNIC_Reboot: Control whether the ICPlayer graphical engine reboots or restarts if it abnormally exits.

  Normally, if the ICPlayer graphical engine or the ICPlayer network engine exits abnormally, the PC will be rebooted. Set:

  RUNIC_Reboot = off

  to cause these engines to be restarted without the PC being rebooted.

• SSCLIENT_DiskSpaceToUseForLogFiles/MaximumNumberOfLogFiles: Limit the accumulation of transmission-log files on the player. Normally, the player will accumulate up to 500 transmission-log files, or a total of 10 MB of such files, whichever comes first. For example, to reduce these limits by half, you could say:
  SSCLIENT_DiskSpaceToUseForLogFiles = 5000000
  SSCLIENT_MaximumNumberOfLogFiles = 250

• SSHEALTH_ErrorIfPlayerOffNMinutes: Controls how many minutes the player's graphical engine is allowed to be stopped before the player's network engine sends an alert to NetManager. For example, you could say:
  SSHEALTH_ErrorIfPlayerOffNMinutes = 15

  to allow 15 minutes to pass before the alert is reported.

  (Added in Release 6d)

  (Starting with Release 7.4, you may use the settings in ConfigIC instead.)

• SSCLIENT dial-up connection warning-limits: a family of options to set up certain dial-up connection warning-limits, and report an error back to NetManager if those limits are exceeded. (In order for the network to continue to function, the Player will continue to dial after the warning-limits are exceeded — the error report back to NetManager is there to alert the operator.)

  Select a combination of settings based on what you are interested in monitoring. In turn, this is usually based on how you pay for telephone and internet service.

  • SSCLIENT_ResetDialupStatisticsEveryNHours: Sets the length of the warning-period over which the dial-up connection warning-limits apply. After this many hours, the measurements are reset. There will be a maximum of one error reported back to NetManager per period.
    SSCLIENT_ResetDialupStatisticsEveryNHours=n

    The default value is 24 hours.

    (Added in Release 7.1)

  • SSCLIENT_ErrorIfDialupConnectedMoreThanNHours: Sets a warning-limit based on total connect time. If a player is connected for this many hours per warning-period, the warning-limit error will be reported.
    SSCLIENT_ErrorIfDialupConnectedMoreThanNHours=n

    The default value is 0 (unlimited). Use this setting if you are charged based on the amount of time your dial-up connection is active.

    (Added in Release 7.1)

  • SSCLIENT_ErrorIfDialupAttemptedMoreThanNTimes: Sets a warning-limit based on the number of dial-up attempts. If a player makes more than this number of attempts per warning-period, the warning-limit error will be reported.
    SSCLIENT_ErrorIfDialupAttemptedMoreThanNTimes=n

    The default value is 0 (unlimited). Use this setting if you are charged per dial-up attempt (regardless of whether or not the call succeeded).

    (Added in Release 7.1)

  • SSCLIENT_ErrorIfDialupConnectedMoreThanNTimes: Sets a warning-limit based on the number of successful dial-up connections. If a player makes more than this number of successful connections per warning-period, the warning-limit error will be reported.
    SSCLIENT_ErrorIfDialupConnectedMoreThanNTimes=n

    The default value is 0 (unlimited). Use this setting if you are charged per completed dial-up connection (e.g., some minimum charge for making the connection).

    (Added in Release 7.1)

  • SSCLIENT_ErrorIfDialupFailedMoreThanNTimes: Sets a warning-limit based on the number of failed dial-up connections. If a player makes more than this number of failed connection attempts per warning-period, the warning-limit error will be reported.
    SSCLIENT_ErrorIfDialupFailedMoreThanNTimes=n

    The default value is 0 (unlimited). Use this setting if you are having problems with an excessive number of dial-up failures. However, keep in mind that if a player cannot connect due to dialup failures it will not be able to report this error to Network Manager until it has connected successfully.

    (Added in Release 7.1)

• SSHEALTH_BillingLogUploadDelayHours: When nightly retrieval of billing logs is enabled, this setting governs the delay after midnight before the player uploads its billing logs. Using the mmos.ini setting
  SSHEALTH_BillingLogUploadDelayHours=h
  tells the player to delay for a random amount up to h hours after startup or midnight, before connecting to upload billing logs.

  (Added in Release 7.3.1)

• SSHEALTH_HeartbeatStartupMaximumDelayMinutes: With health monitoring enabled, a player sends its first heartbeat immediately upon startup. In order to balance network loads (e.g. when players restart at about the same time due to scheduled reboots, maintenance jobs, etc.), the first heartbeat is now delayed by a random amount in the range of zero to ten minutes. The range of random delay can be customized with the MMOS.INI keyword:
  SSHEALTH_HeartbeatStartupMaximumDelayMinutes=n

  (Added in Release 7.3.2)

• SSHEALTH_LogUploadMaximumDelayMinutes: With nightly log retrieval enabled, a player uploads its log file immediately after midnight. In order to balance network loads, the nightly upload is now delayed by a random amount in the range of zero to ten minutes. The range of random delay can be customized with the MMOS.INI keyword:
  SSHEALTH_LogUploadMaximumDelayMinutes=n

  (Added in Release 7.3.2)

IC3 Add-on EX MMOS.INI Options

VCR EX

• COMO_Pause: The VCR EX waits 1000 ms between successive commands it sends to the MPEG-2@Disk deck. This value can be adjusted using the new MMOS.INI setting for the MPEG-2@Disk deck:
  COMO_Pause=n

  The manufacturer recommends a range of 500 to 1000 ms.

• COMO_UseStopAfterPlayTrack: Certain MPEG-2@Disk units have special firmware that stops the deck automatically after playing a single track. With such a device, add the new MMOS.INI setting for the MPEG-2@Disk deck:
  COMO_UseStopAfterPlayTrack=0

  to prevent Scala from issuing an unnecessary Stop command, which does nothing but add a delay.

TV Tuner EX

• DSHOWRENDER_TVCaptureWidth/Height: For most TV tuner cards (not including the Hauppauge cards), you can now specify the size of the "capture window", i.e. the resolution at which the original image is grabbed. Use the MMOS.INI variables
  DSHOWRENDER_ChangeTVCaptureToYUV=1
  DSHOWRENDER_TVCaptureWidth=width
  DSHOWRENDER_TVCaptureHeight=height
  Best results are usually obtained when you choose a width and height that evenly divides into the width and height of your TV standard.
• DSHOWRENDER_UseHauppaugePVRx50Kludge: To use the Hauppauge PVR 250 or PVR 350 card with the TV Tuner EX, set the following in your MMOS.INI:
  DSHOWRENDER_UseHauppaugePVRx50Kludge = 1

  (Added in Release 6b. Starting in Release 7.4, use the TV Tuner hardware selector instead.)