TeleMagic 4.5 & Windows NT/2000

Question: I am considering the use of a Microsoft NT Network and would like to place TeleMagic on my NT File Server. Are their settings that I should activate, or items that I should be aware of to improve TeleMagic performance?

Answer: Aside from meeting TeleMagic System Requirements identified in article System Requirements additional items that affect TeleMagic performance are outlined below:

1. Opportunistic Locking - "Opportunistic Locking" is a file locking/file sharing method on the NT Server that inhibits the operation of TeleMagic and should be disabled on the NT Server that houses TeleMagic. More detailed information on this function and settings can be found in the Microsoft Knowledge Base, article Q129202.

2. Network Protocols - Wherever possible the only protocol that should be used is TCP/IP. Multiple protocols tend to impede performance. If possible, when using TCP/IP a WINS (Windows Internet Name Service) server should be established to perform NETBIOS name resolution as opposed to having the client perform the name resolution through broadcast or LMHOSTS file. Alternatively, name resolution can be handled through a DNS server (Domain Name Service).

3. Network Bandwidth - Wherever possible, the clients and server should be using 100MB Network Interface Cards along with a 100MB Switch. Ideally, the server and clients should reside on the same Network Segment.

4. Windows NT Services - TeleMagic is using the NT Server as a file server. TeleMagic Enterprise does not contain any services that would run as a Service on NT. Therefore any unnecessary services that run on the NT Server can take away possible performance gains for the server and TeleMagic.

5. Network Shares & Permissions - TeleMagic users need to be provided with "Read, Write, Modify, Erase and File Scan" permissions to the files and folders that contain TeleMagic on the NT Server. Share and or NTFS permissions may need to be established in order to provide the appropriate permissions.

6. Anti Virus - Anti Virus programs should not be configured to scan TeleMagic "Data Files". The TeleMagic Data Files are files with extensions of "DBF", "FPT" and "CDX". Scanning of TeleMagic program files (*.EXE, *.APP ...etc) can be performed as normal.

7. Primary Domain Controllers - If the Primary Domain Controller is responsible for other server, users and printing activities, it is not recommended that it be utilized as the TeleMagic File Server. However, in an environment where only one server exists, and the PDC is configured on a small network (1 to 10 users), then dual configuration as the File Server for TeleMagic should not result in any unreasonable performance.

8. Windows NT Server Service - Setting the "Maximum throughput for File Sharing" within the Server service on the NT4 Server will improve performance. Similar settings can be set on a Windows 2000 server by setting "Background Services" within Performance Options.

Client Configuration
~~~~~~~~~~~~~~~~

1. Client workstations should be an absolute minimum of Pentium 200 with 64MB of RAM, and in some environments may not be acceptable. In this instance, consider using a Pentium II or Pentium III-450 or better. Faster processors and memory on the Client workstation will dramatically improve TeleMagic performance. Better Video Cards will also improve the overall performance of TeleMagic. This is true with most applications.

2. File Handles - TeleMagic is a 32-bit application and we have found that performance is improved when using a minimum of 150 File Handles specified within the Config.sys for Win '95 & Win '98. For Windows NT & 2000 the performance is improved by setting the "Files=150" in the Config.nt.

Note: The Config.nt within Windows NT/2000 is used to configure the environment for Windows 16-Bit and or DOS applications. TeleMagic 4.5 is a 32-bit application and "Field Experience" has shown that in some environments it has been necessary to configure a minimum of "Files=150" in the Config.nt for TeleMagic. Again, in some environments, not setting the files statement in the config.nt has resulted in an "Unable to Open File" error.

3. Microsoft Windows Redirector: Various versions of Windows '95 have required an update to the "Virtual Redirector" group of files. For more details please refer to TeleMagic Knowledge Base article 521. The Virtual Redirector update file (VRDRUPD.EXE) is available from Microsoft FTP site at:

ftp.microsoft.com/softlib/mslfiles.

4. Client 32 drivers: Wherever possible the Microsoft client (Client for Microsoft Networks) should be installed and configured as the primary interface to resources on a Microsoft network. When it becomes necessary to connect to Novell servers then the "Microsoft Client for Netware Networks" or "Microsoft Client Service for Netware" (Windows NT/2000) should be installed and configured at the client workstation. The "Client 32 drivers for Novell" should only be installed when absolutely necessary. Our tests have shown that all Netware resources are available using the Microsoft Client for Netware excluding the administrative functions.

 

-- End of FAQ #724

FAQ ID #724

Product Related: TeleMagic 4.x

Last Updated:
July 26, 2000