install-windows-7.xml 9.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158
  1. <section id="install-windows-7">
  2. <title>
  3. Toolkit Installation on <productname>Windows 7</productname>
  4. </title>
  5. <para>
  6. The <productname>Windows</productname> version of the toolkit comes pre-compiled and ready to install and run using the native <application>Windows Installer</application>. You may copy and distribute installation file <filename>plc-utils-x.x.x.msi</filename>. Users merely click on the file to install the package and may discard it afterwards. This method of installation permits remote installation over anetwork.
  7. </para>
  8. <para>
  9. The version of the Windows Installer used here needs Microsoft <productname>.NET Framework 1.1</productname> to work correctly. Newer versions of the <productname>.NET Framework</productname> will not work. The <productname>.NET Framework</productname> must be installed before the toolkit is installed or the <productname>Windows Installer</productname> will report depenency errors and refuse to complete installation. Multiple versions of the <productname>.NET Framework</productname> can coexist under <productname>Windows 7</productname>. The <productname>.NET Framework</productname> needed is included in the toolkit <filename>support</filename> folder.
  10. </para>
  11. <tip>
  12. <para>
  13. Users on the QCA corporate network may be able to download installer <ulink url='ftp://appslinux01.qca.qualcomm.com/windows/dotnetfx.exe'>ftp://appslinux01.qca.qualcomm.com/windows/dotnetfx.exe</ulink> then execute it by right-clicking on the file and and selecting option Run As Administrator.
  14. </para>
  15. </tip>
  16. <para>
  17. Failure to <link linkend='removal-windows-7'>remove previous toolkit versions</link> on some systems may result in the message &quot;Another version of this product is already installed&quot; when trying to install a new version. You may want to remove prior version before starting toolkit installation.
  18. </para>
  19. <para>
  20. Windows versions of toolkit programs that communicate with powerline devices all need <productname>WinPcap</productname> from <ulink url="http://www.winpcap.org/install/default.htm">winpcap.org</ulink> to read and write Ethernet frames. <productname>WinPcap</productname> may be installed before or after toolkit installation but tools that access powerline devices will not run without it. You may want to install <productname>WinPcap</productname> before starting toolkit installation. If you have <productname>Wireshark</productname> installed then you probably already have <productname>WinPcap</productname> installed. A recent copy of <productname>WinPcap</productname> is included in the toolkit <filename>support</filename> folder.
  21. </para>
  22. <tip>
  23. <para>
  24. Users on the QCA corporate network may be able to download installer <ulink url='ftp://appslinux01.qca.qualcomm.com/windows/WinPcap_4_1_2.exe'>ftp://appslinux01.qca.qualcomm.com/windows/WinPcap_4_1_2.exe</ulink> then execute it by right-clicking on the file and selecting option Run As Administator.
  25. </para>
  26. </tip>
  27. <section>
  28. <title>
  29. Obtaining the Toolkit
  30. </title>
  31. <para>
  32. QCA customers can download the toolkit from the QCA Customer FTP Site.
  33. </para>
  34. <para>
  35. QCA employees may be able to download the toolkit from the QCA Application Engineering World FTP site <ulink url='ftp://appslinux01.qca.qualcomm.com/toolkit/plc-utils/'>ftp://appslinux01.qca.qualcomm.com/toolkit/plc-utils/</ulink>. There are several installers available for Windows. Each installs a subset of the toolkit. Download the desired installer files to your local machine then execute them by right-clicking on them and selecting option "Run as Administrator".
  36. </para>
  37. </section>
  38. <section>
  39. <title>
  40. Installing the Toolkit
  41. </title>
  42. <para>
  43. Older toolkit programs were installed in folder <filename>C:\Program Files\Atheros\Toolkit</filename> by default but now they are installed in <filename>C:\Program Files (x86)\Qualcomm Atheros\Powerline Toolkit</filename> instead. If you slect a different folder during installation then remember it for the next step.
  44. </para>
  45. <figure>
  46. <title>
  47. Windows Installer Dialogue
  48. </title>
  49. <mediaobject>
  50. <imageobject>
  51. <imagedata fileref='Win7-installer-dialogue.png' align="center" />
  52. </imageobject>
  53. </mediaobject>
  54. </figure>
  55. <para>
  56. Accept install defaults.
  57. </para>
  58. </section>
  59. <section>
  60. <title>
  61. Setting the PATH variable
  62. </title>
  63. <para>
  64. <application>Toolkit</application> programs have command line interfaces and must be run from an open console window. To simplify program access and minimize the typing required, add the toolkit installation path mentioned above to the <envar>PATH</envar> environment variable by following steps listed below. If you have <constant>Administrator</constant> privileges then we recommend that you edit the system <envar>PATH</envar> variable; otherwise, you may need to create and/or edit a user <envar>PATH</envar> variable.
  65. </para>
  66. <figure>
  67. <title>
  68. Control Panel System Dialogue
  69. </title>
  70. <mediaobject>
  71. <imageobject>
  72. <imagedata fileref='Win7-system-settings.png' format='PNG' align="center" />
  73. </imageobject>
  74. </mediaobject>
  75. </figure>
  76. <para>
  77. This following example illustrates how to create a user PATH variable which will be appended to the system path variable.
  78. </para>
  79. <orderedlist>
  80. <listitem>
  81. <para>
  82. On the <command>Start</command> menu, select the <command>Control Panel</command> option.
  83. </para>
  84. </listitem>
  85. <listitem>
  86. <para>
  87. On the <command>Adjust system settings</command> page, select the <command>System</command> icon.
  88. </para>
  89. </listitem>
  90. <listitem>
  91. <para>
  92. On the <command>View basic informtion about your computer</command> page, select the <command>Advanced system settings</command> option.
  93. </para>
  94. </listitem>
  95. <listitem>
  96. <para>
  97. On the <command>System Properties</command> dialog, press the <command>Environment Variables</command> button.
  98. </para>
  99. </listitem>
  100. <listitem>
  101. <para>
  102. On the <command>Environment Variables</command> dialog box, do one of the following:
  103. <orderedlist>
  104. <listitem>
  105. To edit the system PATH variable, scroll down the <command>System variables</command> list and select the system <command>PATH</command> variable then press the <command>Edit</command> button. On the <command>Edit System Variable</command> dialogue box, append the installation path to the <command>Variable value</command> field.
  106. </listitem>
  107. <listitem>
  108. To edit or create the user PATH variable, scroll down the <command>User variables</command> list and select the user <command>PATH</command> variable, if it exists. Otherwise, create the user PATH variable by pressing the <command>New</command> button. If you have a <command>New User Variable</command> dialog box then enter "PATH" in the <command>Variable name</command> field and the toolkit installation path in the <command>Variable Value</command> field. Otherwise, if you have a <command>Edit User Variable</command> dialogue box, append the installation path to the <command>Variable value</command> field.
  109. </listitem>
  110. </orderedlist>
  111. </para>
  112. </listitem>
  113. <listitem>
  114. <para>
  115. Press the <command>OK</command> button.
  116. </para>
  117. </listitem>
  118. </orderedlist>
  119. <para>
  120. Environment variable changes made here do not take effect until a console window is opened. This means that you may need to close and then reopen console windows that depend on the changes. It is a good idea to immediately open a console window and execute a toolkit command in order to confirm that the <constant>PATH</constant> variable is properly defined.
  121. </para>
  122. </section>
  123. <section id="removal-windows-7">
  124. <title>
  125. Removing the Toolkit
  126. </title>
  127. <para>
  128. To remove an existing version of the Qualcomm Atheros <application>Powerline Toolkit</application> from your system, follow the steps listed below. If the toolkit is not installed on your system then omit these steps. If you are unsure, you can follow them to determine if you have the toolkit installed or you can attempt to install, anyway, and return here if installation is prevented.
  129. </para>
  130. <figure>
  131. <title>
  132. Control Panel Add/Remove Dialogue
  133. </title>
  134. <mediaobject>
  135. <imageobject>
  136. <imagedata fileref="Win7-remove-program.png" align="center"/>
  137. </imageobject>
  138. </mediaobject>
  139. </figure>
  140. <orderedlist>
  141. <listitem>
  142. <para>
  143. On the <command>Start</command> menu, select the <option>Control Panel</option> option.
  144. </para>
  145. </listitem>
  146. <listitem>
  147. <para>
  148. On the <command>Adjust system settings</command> page, select the <command>Programs and Features</command> icon.
  149. </para>
  150. </listitem>
  151. <listitem>
  152. <para>
  153. On the <command>Uninstall or change a program</command> page, scroll down and select the appropriate QCA <option>Powerline Toolkit</option> entry then press the <option>Remove</option> pushbutton. There may be several different QCA Powerline Toolkit entries so be sure to select the correct one.
  154. </para>
  155. </listitem>
  156. </orderedlist>
  157. </section>
  158. </section>