File Manager

File Manager

File : /home/mcamail/www/www/tm4winnt.htm

<html>

<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Microsoft FrontPage Express 2.0">
<title>tm4-winnt</title>
</head>

<table border="0">
 <tr>
 <td bgcolor="#727DCD">&nbsp;</td>
 <td bgcolor="#727DCD">FAQ
 ID #724 </td>
 <td bgcolor="#727DCD">&nbsp;</td>
 <th align="left" bgcolor="#727DCD">TeleMagic 4.5 &amp; Windows NT/2000</th>
 <td bgcolor="#727DCD"> 
 </td>
 <td bgcolor="#727DCD">&nbsp;</td>
 </tr>
 <tr>
 <td>&nbsp;</td>
 <td valign="top" width="20%">Question: 
 ~~~~~~~~~&nbsp;
 Answer: 
 ~~~~~~~
 Opportunistic Locking
 &nbsp;
 TCP/IP WINS 
 
 &nbsp;
 &nbsp;
 100MB Switch
 &nbsp;
 &nbsp;
 &nbsp;
 Permissions
 &nbsp;
 Disable Anti Virus Software
 &nbsp;
 &nbsp;
 &nbsp;
 
 Maximum Throughput for FIle Sharing
 &nbsp;
 
 Pentium 200 w/ 64MB ram 
 &nbsp;
 
 Config.sys Files=150-250
 
 Config.nt Files=150-250
 &nbsp;
 
 Win95 Vredir.vxd?
 </td>
 <td>&nbsp;</td>
 <td>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? 
 
 
 Aside from meeting TeleMagic System Requirements
 identified in article <a
 href="http://www.telemagic.com/support/kcenter/kbread.asp?results=YES&amp;id=16&amp;lv=0">System
 Requirements</a> additional items that affect TeleMagic
 performance are outlined below: 
 
 1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 Opportunistic Locking - &quot;Opportunistic Locking&quot;
 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 <a
 href="http://search.support.microsoft.com/kb/c.asp?fr=0&amp;SD=GN&amp;LN=EN-US">Q129202</a>. 
 
 2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 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.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 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.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 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.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Network
 Shares &amp; Permissions - TeleMagic users need to be
 provided with &quot;Read, Write, Modify, Erase and File
 Scan&quot; 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.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Anti
 Virus - Anti Virus programs should not be configured to
 scan TeleMagic &quot;Data Files&quot;. The TeleMagic Data
 Files are files with extensions of &quot;DBF&quot;,
 &quot;FPT&quot; and &quot;CDX&quot;. Scanning of
 TeleMagic program files (*.EXE, *.APP ...etc) can be
 performed as normal. 
 
 7.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 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.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Windows
 NT Server Service - Setting the &quot;Maximum throughput
 for File Sharing&quot; within the Server service on the
 NT4 Server will improve performance. Similar settings can
 be set on a Windows 2000 server by setting
 &quot;Background Services&quot; within Performance
 Options. 
 
 Client Configuration 
 ~~~~~~~~~~~~~~~~~~~~~ 
 
 1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 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.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 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 &amp; Win '98. For Windows NT &amp; 2000 the
 performance is improved by setting the
 &quot;Files=150&quot; 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
 &quot;Field Experience&quot; has shown that in some
 environments it has been necessary to configure a minimum
 of &quot;Files=150&quot; in the Config.nt for TeleMagic.
 Again, in some environments, not setting the files
 statement in the config.nt has resulted in an
 &quot;Unable to Open File&quot; error. 
 
 3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 Microsoft Windows Redirector: Various versions of Windows
 '95 have required an update to the &quot;Virtual
 Redirector&quot; group of files. For more details please
 refer to TeleMagic Knowledge Base article <a
 href="kbread.asp?id=521&amp;lv=0">521</a>. The Virtual
 Redirector update file (VRDRUPD.EXE) is available from
 Microsoft FTP site at: 
 
 <a href="ftp://ftp.microsoft.com/softlib/mslfiles">ftp.microsoft.com/softlib/mslfiles</a>. 
 
 4.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 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 &quot;Microsoft Client for
 Netware Networks&quot; or &quot;Microsoft Client Service
 for Netware&quot; (Windows NT/2000) should be installed
 and configured at the client workstation. The
 &quot;Client 32 drivers for Novell&quot; 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. </td>
 <td valign="top" width="30%">Marketing
 Center Associates 
 Box 18432 
 Boulder CO 80308-1432
 303-581-9296
 <a href="mailto:Steve@telemagicusa.net">Steve@telemagicusa.net</a>
 &nbsp;
 </td>
 <td>&nbsp;</td>
 </tr>
 <tr>
 <td>&nbsp;</td>
 <td>Last updated 03/26/2001</td>
 <td>&nbsp;</td>
 <td>Excerpted from the SageUS/TeleMagic
 web site Knowlegebase. <a
 href="http://www.telemagic.com/support/kcenter/kbread.asp?results=YES&amp;id=724&amp;lv=0">http://www.telemagic.com/support/kcenter/kbread.asp?results=YES&amp;id=724&amp;lv=0</a></td>
 <td>&nbsp;</td>
 <td>&nbsp;</td>
 </tr>
</table>
</body>
</html>

Press this button to

Size:

Height:

File Manager Main Menu