HTTP Server/TCP不再响应

也许这是我所面临的中小企业问题。看看我的线程HTTP://www. McCHIP.COM/FUMMS/M956930.ASPXIT应该被固定在新版本的Orthor中，否则您可以使用Runad附带的文件。



      以下为原文

   
Maybe it is the sme problem that I had. Have a look at my thread http://www.microchip.com/forums/m956930.aspx 
It supposed to be fixed in the new version of Harmony, otherwise you can use the file attached by rainad.

谢谢你！我开始读，这是一个很长的线索，我会彻底检查一遍，然后让你知道。我希望这是问题；下一个版本的和声是什么？我在这里迷路了。是1.10还是2.0X？谢谢Stephane。



      以下为原文

    Hello
 
Thank you!! I started to read, this is a very long thread, I will go over it completely and let you know. I hope that is the issue ;)
 
What is the next version of Harmony? I am lost here. Will it be 1.10 or 2.0x?
 
Thanks Stephane.
 

嗨，有2个版本的和声并行：版本V1.XX，这是遗留版本，它只是维护版本V2.XXB，这是beta版，将成为生产版本今年晚些时候。所有新的特性仅在6个月后才在V2.XX中引入。此外，bug修复大部分是在V2.XXX中完成的，2个版本在一周内启动。首先是V1.XX，然后是V2.XXX，最新版本是V1.10和V2.02B.请注意，和声V1.XX必须使用MHC插件V1.X.X.X（默认插件），和声V2.XX必须使用MHC插件V2.Y.Y.YAS和声V2.XXB源于V1.YY，这是非常稳定的（对我的意见）。它不像是从头开始的空白测试版。我想从bug修复和新特性中获益，因此我只使用V2.XXX。



      以下为原文

    Hi,
There are 2 versions of Harmony in parallel :
The version v1.xx which is the legacy versions and it just maintained
The version v2.xxb which is beta and will become the production version later this year. All new features are only introduced in v2.xx since 6 months. Also the bug fixes are mostly done in V2.xx
Everytime the 2 versions are launched within one week. First v1.xx and then v2.xx
Currently, the latest versions are v1.10 and v2.02b.
Please note that Harmony v1.xx MUST use MHC plugin v1.x.x.x (default plugin) and Harmony v2.xx MUST use MHC plugin v2.y.y.y
As Harmony v2.xxb is derived from v1.yy it is very stable (to my opinion). It is not like a blank new beta version starting from scratch. 
I want to benefit from bug fixes and new features and therefore I only use v2.xx
Regards

谢谢你的细节，从1点到2点有多难？好像是从1点到1点。Stephane。



      以下为原文

    Hello
 
Thank you for the details.
How hard is it to move from 1.x to 2.x? Like it is from 1.x to 1.y?
 
Stephane.

去看邮局！哇，太复杂了！如果我想使用修复，这意味着我首先需要升级到和声2。我应该得到2.02b，我必须得到2.01b？你也在谈论一个改变：这是需要的吗？非常感谢，Stephane。



      以下为原文

    Hello
 
Read the post! Whooo, that was complex!
If I want to use the fix, this would mean I first need to upgrade to Harmony 2.x? Should I got for 2.02b of I must go for 2.01b?
Also you are talking about a change:
 
 
Is this needed to do it?
 
Thank you very much, Best Regards, Stephane.

如果你不使用图形库，从V1.09移动到2.02B就不会那么困难了。在这种情况下，它可能会做很多工作。在这一点上，V1.XX是简单的bug修复。一些人报告了2.0X版本的稳定性问题。我的V2.00的快速测试没有。



      以下为原文

    Moving from v1.09 to 2.02b will not be that hard if you are not using the graphics library. In that case it maybe a lot of work.
V1.xx is down to simple bug fixes at this point.
Some people have reported stability issues with 2.0x versions. My quick test of v2.00b did not.

您好，我只是想更新，但是我不能。要么我先更新插件，它不想加载，要么我尝试更改Harmony版本，前一个插件失败。步骤是什么？Stephane。



      以下为原文

    Hello
 
I am just trying to update but I can't.
Either I start by updating the plugin and it does not want to load or I try to change the Harmony version and the previous plugin fails.
 
What are the steps?
 
Stephane.

如果我是你，我现在尝试将你的版本1.09中的文件TCPIpHymReals.c与我的线程中的POST第62条中的一个文件进行比较，看看是否存在很多差异（我不确定这个文件在VER中有多大的不同）。在2.01B版本中，1.09和2.01b应该是相同的。这两个文件之间的差异是：原始的TCPIpMyMealg.C：固定的TCPI.Maung.Ciff.CF，情况下，您可以替换该文件并查看它是否工作。



      以下为原文

   
If I were you, I would try for now to compare the file tcpip_manager.c in your version 1.09 with the one in post #62 in my thread and see if there are many differences (I am not sure how much different is this file in ver. 1.09 and 2.01b - it should be the same)
In version 2.01b the differences between the two files were:
Original tcpip_manager.c:
static const TCPIP_FRAME_PROCESS_ENTRY TCPIP_FRAME_PROCESS_TBL [] =
{
    // frameType // pktTypeFlags // moduleId
    // 1st layer handling
    {TCPIP_ETHER_TYPE_ARP, TCPIP_MAC_PKT_FLAG_ARP, TCPIP_MODULE_ARP}, // ARP entry

#if defined(TCPIP_STACK_USE_IPV4)
    {TCPIP_ETHER_TYPE_IPV4, TCPIP_MAC_PKT_FLAG_IPV4, TCPIP_MODULE_IPV4}, // IPv4 entry
#else
    {0, 0, TCPIP_MODULE_IPV4}, // IPv4 not processed
#endif // defined(TCPIP_STACK_USE_IPV4)

#if defined(TCPIP_STACK_USE_IPV6)
    {TCPIP_ETHER_TYPE_IPV6, TCPIP_MAC_PKT_FLAG_IPV6, TCPIP_MODULE_IPV6}, // IPv6 entry
#else
    {0, 0, 0}, // IPv6 not processed
#endif // defined(TCPIP_STACK_USE_IPV6)

#if defined(TCPIP_STACK_USE_LLDP)
    {TCPIP_ETHER_TYPE_LLDP, TCPIP_MAC_PKT_FLAG_LLDP, TCPIP_MODULE_LLDP}, // LLDP entry
#else
    {0, 0, 0}, // LLDP not processed
#endif // defined(TCPIP_STACK_USE_LLDP)

    // add other types of supported frames here

};
Fixed tcpip.manager.c
static const TCPIP_FRAME_PROCESS_ENTRY TCPIP_FRAME_PROCESS_TBL [] =
{
    // frameType // pktTypeFlags // moduleId
    // 1st layer handling
    {TCPIP_ETHER_TYPE_ARP, TCPIP_MAC_PKT_FLAG_ARP, TCPIP_MODULE_ARP}, // ARP entry

#if defined(TCPIP_STACK_USE_IPV4)
    {TCPIP_ETHER_TYPE_IPV4, TCPIP_MAC_PKT_FLAG_IPV4, TCPIP_MODULE_IPV4}, // IPv4 entry
#else
    {TCPIP_ETHER_TYPE_UNKNOWN, 0, TCPIP_MODULE_IPV4}, // IPv4 not processed
#endif // defined(TCPIP_STACK_USE_IPV4)

#if defined(TCPIP_STACK_USE_IPV6)
    {TCPIP_ETHER_TYPE_IPV6, TCPIP_MAC_PKT_FLAG_IPV6, TCPIP_MODULE_IPV6}, // IPv6 entry
#else
    {TCPIP_ETHER_TYPE_UNKNOWN, 0, 0}, // IPv6 not processed
#endif // defined(TCPIP_STACK_USE_IPV6)

#if defined(TCPIP_STACK_USE_LLDP)
    {TCPIP_ETHER_TYPE_LLDP, TCPIP_MAC_PKT_FLAG_LLDP, TCPIP_MODULE_LLDP}, // LLDP entry
#else
    {TCPIP_ETHER_TYPE_UNKNOWN, 0, 0}, // LLDP not processed
#endif // defined(TCPIP_STACK_USE_LLDP)
If that's the case, you could replace this file and see if it works.

谢谢你的大力帮助！这实际上是我首先做的，但是从1.09到2.02b的文件有很多不同之处。现在我要做的，现在你给我的差异，以2.01b，是看，正如你建议，如果我不能只是应用修复在1.09.谢谢你，Steph



      以下为原文

    Hello
 
Thanks for your great help!!
 
This is in fact what I did first but the files from 1.09 to 2.02b have lots of differences. What I will do, now that you provided me with the differences to 2.01b, is to see, as you suggested if I cannot just apply the fix in 1.09.
 
What about ?
 
Thank you Steph