<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SOL issue in Intel® Business Client Software Development</title>
    <link>https://community.intel.com/t5/Intel-Business-Client-Software/SOL-issue/m-p/883434#M3510</link>
    <description>&lt;DIV style="margin:0px;"&gt;It's possible that it's failing when it first tried to establish the connection, instead of failing during the ongoing SOL communications (although the fact that you are able to boot to BIOS with a different tool makes that less likely).&lt;BR /&gt;&lt;BR /&gt;By RC Console, do you mean the Manageability Commander in the DTK? If so, I assume you're using the most recent version (likewise for the AMT SDK).&lt;BR /&gt;&lt;BR /&gt;Also, could you tell me a little more about the AMT system you are using? Things like the version of AMT, and version of the MEI driver. This tool might be useful to get that information, if you aren't sure how to get it: &lt;A href="http://communities.intel.com/community/openportit/vproexpert/blog/2008/10/03/iamt-scan-custom-inventory-helps-with-enterprise-activations"&gt;http://communities.intel.com/community/openportit/vproexpert/blog/2008/10/03/iamt-scan-custom-inventory-helps-with-enterprise-activations&lt;/A&gt; &lt;/DIV&gt;</description>
    <pubDate>Mon, 31 Aug 2009 20:40:42 GMT</pubDate>
    <dc:creator>Andrew_S_Intel2</dc:creator>
    <dc:date>2009-08-31T20:40:42Z</dc:date>
    <item>
      <title>SOL issue</title>
      <link>https://community.intel.com/t5/Intel-Business-Client-Software/SOL-issue/m-p/883433#M3509</link>
      <description>Hi,&lt;BR /&gt;When I try to using AMTRedirection.exe(in AMT SDK) to force the SUT(System under test) to boot to BIOS setup,I gotan error message "SOL session closed".Checking MCSOL.cpp(SDK\Windows\Intel_AMT\Samples\Redirection\AMTRedirection),just found the the following snippet&lt;BR /&gt;
&lt;P&gt;void MCSOL::run ()&lt;BR /&gt;{&lt;BR /&gt;BYTE sol_data[MAX_SOL_MESSAGE];&lt;BR /&gt;int len;&lt;BR /&gt;BOOL more = FALSE;&lt;/P&gt;
&lt;P&gt;int iReturn = 0; // Return value of recv function&lt;BR /&gt;char szClientA[MAX_SOL_MESSAGE]; // ASCII string &lt;BR /&gt;fd_setrset;&lt;BR /&gt;FD_ZERO(&amp;amp;rset);&lt;BR /&gt;//timeout every second&lt;BR /&gt;//in order to check the exit flag&lt;BR /&gt;struct timeval tv;&lt;BR /&gt;tv.tv_sec =0;&lt;BR /&gt;tv.tv_usec =10;&lt;BR /&gt;struct sockaddr_in remote_addr;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;do {&lt;/P&gt;
&lt;P&gt;//Poll the SDKLIB for incoming data&lt;BR /&gt;do{&lt;BR /&gt;len = MAX_SOL_MESSAGE;&lt;BR /&gt;memset (sol_data, 0x0, MAX_SOL_MESSAGE);&lt;BR /&gt;IMRResult res = IMR_SOLReceiveText(_activeClient, sol_data, &amp;amp;len);// retrieve stored SOL text from SDK&lt;BR /&gt;&lt;STRONG&gt;if(res != IMR_RES_OK){&lt;BR /&gt;string messg = _T("SOL Session closed. ");&lt;BR /&gt;messg += resultToString(res);&lt;BR /&gt;MessageBox (NULL, messg.c_str(), TEXT("Client"), MB_OK | MB_SYSTEMMODAL);&lt;BR /&gt;&lt;/STRONG&gt;_exitThread = true;&lt;BR /&gt;break;&lt;BR /&gt;}&lt;BR /&gt;if (len &amp;gt; 0){&lt;BR /&gt;//Send the buffer to the HT&lt;BR /&gt;if(!_sendDataToHT(sol_data,len)){&lt;BR /&gt;_exitThread = true;&lt;BR /&gt;break;&lt;BR /&gt;}&lt;BR /&gt;}&lt;BR /&gt;}while (len);&lt;BR /&gt;&lt;BR /&gt;The reason may be res != IMR_RES_OK.&lt;BR /&gt;Then I use RC Console to force SUT to boot to BIOS setup,the SUT restarts immediately and boots to BIOS setup.&lt;BR /&gt;I want to knowwhat causes the issue,and the differences between the two tools toimplement the function.&lt;BR /&gt;Any help would appreciate.&lt;/P&gt;</description>
      <pubDate>Sun, 30 Aug 2009 14:30:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Business-Client-Software/SOL-issue/m-p/883433#M3509</guid>
      <dc:creator>joey-dong</dc:creator>
      <dc:date>2009-08-30T14:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: SOL issue</title>
      <link>https://community.intel.com/t5/Intel-Business-Client-Software/SOL-issue/m-p/883434#M3510</link>
      <description>&lt;DIV style="margin:0px;"&gt;It's possible that it's failing when it first tried to establish the connection, instead of failing during the ongoing SOL communications (although the fact that you are able to boot to BIOS with a different tool makes that less likely).&lt;BR /&gt;&lt;BR /&gt;By RC Console, do you mean the Manageability Commander in the DTK? If so, I assume you're using the most recent version (likewise for the AMT SDK).&lt;BR /&gt;&lt;BR /&gt;Also, could you tell me a little more about the AMT system you are using? Things like the version of AMT, and version of the MEI driver. This tool might be useful to get that information, if you aren't sure how to get it: &lt;A href="http://communities.intel.com/community/openportit/vproexpert/blog/2008/10/03/iamt-scan-custom-inventory-helps-with-enterprise-activations"&gt;http://communities.intel.com/community/openportit/vproexpert/blog/2008/10/03/iamt-scan-custom-inventory-helps-with-enterprise-activations&lt;/A&gt; &lt;/DIV&gt;</description>
      <pubDate>Mon, 31 Aug 2009 20:40:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Business-Client-Software/SOL-issue/m-p/883434#M3510</guid>
      <dc:creator>Andrew_S_Intel2</dc:creator>
      <dc:date>2009-08-31T20:40:42Z</dc:date>
    </item>
    <item>
      <title>Re: SOL issue</title>
      <link>https://community.intel.com/t5/Intel-Business-Client-Software/SOL-issue/m-p/883435#M3511</link>
      <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="margin-top: 5px; width: 100%;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/334038"&gt;Andrew Schiestl (Intel)&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt;
&lt;DIV style="margin:0px;"&gt;It's possible that it's failing when it first tried to establish the connection, instead of failing during the ongoing SOL communications (although the fact that you are able to boot to BIOS with a different tool makes that less likely).&lt;BR /&gt;&lt;BR /&gt;By RC Console, do you mean the Manageability Commander in the DTK? If so, I assume you're using the most recent version (likewise for the AMT SDK).&lt;BR /&gt;&lt;BR /&gt;Also, could you tell me a little more about the AMT system you are using? Things like the version of AMT, and version of the MEI driver. This tool might be useful to get that information, if you aren't sure how to get it: &lt;A href="http://communities.intel.com/community/openportit/vproexpert/blog/2008/10/03/iamt-scan-custom-inventory-helps-with-enterprise-activations"&gt;http://communities.intel.com/community/openportit/vproexpert/blog/2008/10/03/iamt-scan-custom-inventory-helps-with-enterprise-activations&lt;/A&gt; &lt;/DIV&gt;
&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;BR /&gt;Thanks for your reply.&lt;BR /&gt;Version of AMT:6.0&lt;BR /&gt;ME FW:6.0.0.1161&lt;BR /&gt;Version of MEI driver:6.0.0.1161&lt;BR /&gt;The Platform:Q57&lt;BR /&gt;CPU:lynnfield.&lt;BR /&gt;&lt;BR /&gt;RC Console is a tool just like remote conctrol in SDK.&lt;BR /&gt;I have used the Manageability Commander to test the functions,it failed also.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Sep 2009 15:01:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Business-Client-Software/SOL-issue/m-p/883435#M3511</guid>
      <dc:creator>joey-dong</dc:creator>
      <dc:date>2009-09-01T15:01:32Z</dc:date>
    </item>
  </channel>
</rss>

