Installation. Imagine communications v11 ADC

PDF

Dokument

Annonce

ADC Device Server v11.61.4

Installation, Configuration, and Operations Reference

Installation

The Pre-installed Application

The Automation system comes with all of the necessary software already installed. If, for some reason, the operating system and ADC Device Server v11 software need to be reinstalled, a bootable CD-ROM is supplied for each Device Server (and client PC) in your system. This CD-ROM contains a compressed image of the Device Server’s hard drive at the time the system was delivered. The CD-ROM does not contain your custom build of

Device Server software or any configuration changes you or your Customer Support

Engineer may have made to the system during commissioning.

NOTE: It is essential to back up your Device Server software and configuration files

(ADC100NT.INI, LISTCONF.INI, HANDLES.INI) to another location before attempting to reinstall the operating system. These files are usually located in the “C:\Server” folder on the

Device Server.

IMPORTANT: NetBIOS hotfix for 64 bit OS: The following only affects ADC v11.x running under a 64 bit OS. When running 64 bit Server 2008 or Windows 7, there is an issue where client names are retained after an abnormal disconnect, requiring the name to be changed in order to reconnect. In turn, this means that the customer eventually runs out of logins and must restart the device server. It turns out that this is an OS issue and there is a Microsoft hotfix to correct it; http://support.microsoft.com/kb/2633667/en .

To Reinstall Windows OS (if required)

To reinstall the Windows Operating System on your Device Server, you will need to boot directly from the Windows Installation CD. To do this, ensure the computer's BIOS has been configured to boot from the CD-ROM drive before it attempts to boot from the hard drive:

1. Reboot the computer.

2. Press <Del> when prompted to enter the BIOS setup utility.

3. Select Advanced CMOS Setup and press <Enter>.

4. Press the <down arrow> to highlight 2nd Boot Device, and press <Page Up> or <Page

Down> until CDROM has been selected.

5. Press the <down arrow> to highlight 3rd Boot Device, and press <Page Up> or <Page

Down> until IDE-0 has been selected.

6. Press <ESC>, then <F10>, and <Y> to Save current settings and exit.

7. Make sure the supplied Windows Installation CD is in the CD-ROM drive and allow the computer to reboot.

ADC Device Server v11.61.4

Installation, Configuration, and Operations Reference Installation

8. When the computer reboots, it will look for a bootable CD-ROM. When it finds one, it will display "Press any key to boot from CD". Press <Enter>.

Default .ini Settings

When the INI file does not exist, the following ini items are assigned a Default value of True

(enabled) for the following Device Server's List Properties.



Recue on Media Changes



Update Cued event on media changes



Only Thread Next AO Event



Update On-Air Time



Auto Ripple Times



Keep List Threaded



Release Tension When Cued



Tension After Up Counter



Play Hard Hits



Contact Start



Update Final UpCount Durations

Confirm the Application Icon Command Line

Before running the ADC Device Server application, you may wish to check that the command line for the application is written correctly.

1. Right-click on the ADC100NT icon on the Device Server’s desktop, and then select

“Properties”.

2. In the window that opens, select the “Shortcut” tab.

ADC Device Server v11.61.4

Installation, Configuration, and Operations Reference Installation

3. In the target field, the command line should read C:\Server\adc100nt.exe MAIN. The

“MAIN” in the command line is the application name for this instance of the Device Server application.

Your backup Device Server may be configured to run as backup, so the name designation may be “BACKUP”.

4. Each instance of the Device Server application on the LAN must have a unique application name. The names used are optional. You may rename your Device Server application name to suit your needs.

NOTE: If you change the application name for your Device Server, the command lines for all client applications must be changed accordingly. If not, the client applications will not be able to log into the Device Server.

CAUTION: The path name should not have spaces, otherwise quotation marks are automatically placed around the path. If quotation marks appear around the path, all command line syntax must be placed outside of the quotation marks.

For example,



Correct: C:\ADCServer\adc100nt.exe MAIN



Correct: “C:\ADC Server\adc100nt.exe” MAIN



Incorrect: “C:\ADC Server\adc100nt.exe MAIN”



Incorrect: C:\ADC Server\adc100nt.exe MAIN

IMPORTANT: While up o 16 characters are allowed, it has been discovered that only the

first 10 characters are observed. For each name of main and backup Device Servers that

share the same naming convention, one character must be unique in the first ten characters.

In the following example, while the names are the same to a point, notice that the tenth character is different:

• Main-playout Name: POD100-DSA-SVR01

ADC Device Server v11.61.4

Installation, Configuration, and Operations Reference

• Backup-playout Name: POD100-DSB-SVR02

5. When finished, click OK.

Installation

Improving Transfer Speed via NetBIOS Over

TCP/IP

The Database access speed between the File Server and Air Client is slower when running on Windows XP Pro than it is on Windows 2K. The following procedure details how to improve the performance when running on Windows XP Pro.

Perform this procedure on all of the computers that will run Windows XP Pro and communicate using NetBIOS over TCP/IP in the order the information is provided below.

Create a Backup of the computer registry

If you do not know how to create this Backup, consult “How To Use Backup to Back Up Files and Folders on Your Computer in Windows XP”, (Q308422), at: http://support.microsoft.com

WARNING: Serious problems might occur if you modify the registry incorrectly. These

problems might require that you reinstall your operating system.

Determine which NIC is set to LANA Number 0

If you do not have LANACFG.EXE, it is available at: http://corporate.windowsupdate.microsoft.com/ .

1. Place LANACFG.EXE into a directory, double click on it, and it will self-install.

2. From the Desktop click Start > Run…, type “cmd” in the Open: field of the Run window, and then click OK.

3. Type C:\>lanacfg showlanapaths and identify which NIC is set to LANA Number 0.

ADC Device Server v11.61.4

Installation, Configuration, and Operations Reference

Determine the IP Address of the NIC that is set to LANA Number 0

Installation

1. From the Desktop click Start > Run…, type “cmd” in the Open: field of the Run window, and then click OK.

2. Type C:\>ipconfig /all

3. Locate the name of the NIC that is set to LANA Number 0 and note the IP Address

Enter the New Registry Entry

1. From the Desktop click Start > Run…, type “regedit” in the Open: field of the Run window, and then click OK.

2. Double click on HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services,

TCP/IP, Parameters, and then Interfaces.

3. Highlight, (one at a time), an item in the Interfaces sub tree.

4. Look on the right side of the screen for the IP Address of the NIC that is set to LANA

Number 0.

5. With the correct item in the Interfaces sub tree highlighted, right click on the right side of the screen, and pop-up named New will appear.

6. Place the cursor on New, select DWORD Value, and type in TcpAckFrequency.

7. Double click on TcpAckFrequency, enter 1 into the “Value data:” window, and click OK.

8. Close the Registry Editor, disable and then re-enable this NIC, or reboot the computer.