试图让传统的Hi-Tech C项目再次运作

也许这会有帮助：http://www. cul.euu/~eb.…/PcToo/Stutual.HTML。



      以下为原文

    Maybe this will help: http://www.cs.ucr.edu/~eb.../pictools/install.html

FicroMicrochip收购高科技并更名为XC8。如果版本9xx加上，您可能会迁移。这将是更大的工作更老的产品。我假设你先安装MPLAB8？我不会打扰MPLAB 7除非你的版本很老。转到安装文件夹并检查自述文件。



      以下为原文

    Fisrt Microchip Bought Hi-tech and renamed it XC8.  You may be able to migrate expecilly if the Version 9.XX Plus.  It would be more work for older products.  I assume you install Mplab8 first?
I would not Bother with Mplab 7  unless you version is very old.  Go to the install folder and check the Readme.

与Microchip MPLAB IDE的集成取决于您正在安装的高科技PICC-18工具套件的版本。PICC-18 V980的最新版本具有IDE集成工具作为Windows安装程序的一部分。PICC-18编译器的早期版本有一个单独的EXE来执行与MPLAB的集成。如果您对MPLAB IDE和PICC-18版本有一点更具体的话，我们也许可以建议一种更好的安装方法。编译器仍然在MPLABX V4.05中工作，编译器和链接器在代码大小而不是IDE方面很重要。请记住，所有旧的CRAP都在Windows上运行。如果从VM运行这个，那么在虚拟USB主机接口上运行的电路调试工具可能会遇到一些问题。



      以下为原文

   
The integration with the Microchip MPLAB IDE depends on the version of the HI-TECH PICC-18 Toolsuite you are installing.

The latest version for PICC-18 v9.80 has the IDE integration tool as part of the Windows installer. Earlier versions of the PICC-18 compiler had a separate EXE to perform the integration with MPLAB.

If you could be a bit more specific with regard to the versions of MPLAB IDE and PICC-18 we could perhaps suggest a better installation method.

As a side note the most recent archive of all of the "old" compilers still work from MPLABX v4.05, and it is the compiler and linker that matter when it comes to code size not the IDE.

Remember that all of the old crap runs on Windows. If you are running this from a VM then you may have some issues with the In-Circuit-Debug tools running on the virtual USB host interface.

谢谢大家。您提供的链接工作，除了它不包括PIC18编译器。请看我的另一个回复到DAN1138。注意，我确实有一个带有许可密钥的PICC-18编译器，但是不能计算出如何使它工作。



      以下为原文

    Thanks jtemples.  The link you provided worked, except that it doesn't include the compiler for PIC18.  Please see my other post reply to dan1138.  Note, I do have a PICC-18 compiler with license key, but can't figure out how to make it work...

谢谢DA1138。我会根据你的建议尝试一些事情，否则，也许你（和/或其他人）可以帮助我到达我需要的地方。我衷心感谢它。现在我有一个WMXP虚拟箱VM与MPLAB 8.56和HETECH V961安装。我还有一个旧的工作空间。当我打开工作区时，它提到我需要更改工具链。我把工具链变成了唯一一个可用的高科技条目，它是“高科技通用工具套件”，包含“高科技的ANSI C编译器”，位于“C：程序文件高科技软件PICC971Abin PICC.exe”。但是，当我尝试构建时，我在输出窗口中得到了一个错误：“没有有效的安装的高技术编译器驱动程序”。从这里我被卡住了。我做了谷歌错误，发现提到UAC，但这是Windows XP，我相信最早的UAC。我作为唯一的管理员用户运行（没有命名为“管理员”）。请注意，我有这些原始安装文件，并且包含一个许可证文件。即使我得到上面的工作，它可能不支持PIC18设备。我认为以上的原因可能是一个死胡同。另外，我发现在过去几个月的低水平背景下，我得到了一个文件夹“C:HiTHIGPIC18”，它包含了4/10/2002的“bin PICC18.exe”。我相信这是我需要关注的地方。但是，这似乎是一个已经安装的文件夹，我想我一定是复制了它，也许是一个长期死机遗留机器的长期死机VM。为了确认这个信念，我注意到树中的所有文件夹都是最近的日期，10/9/2017，但是所有的文件内容都是4/10/2002。这意味着内容是15年多，但我去年十月将文件夹复制到我的VM C驱动器上。不幸的是，我不记得从哪里得到这个，我不认为我有原始的安装“程序”，它会设置DLL和注册表项其他东西（那些是不好的东西丢失），或者路径或MPLAB文件的更改（比如创建工具链条目）。就要这样，我如何手动将这个工具链添加到MPLAB中注册的工具链列表中。然而，写了上面一段，我担心绕过了WindowsXP安装。几十年前，例如在Win 3.1后面，没有注册表，软件设计者把自己的DLL放在自己的文件夹中。复制安装（和窃取，不幸的）软件是容易的。但是通过WIN95或每当创建注册表时，复制安装不再有效，因为注册表没有设置，DLL或COM的或其他东西在Windows文件夹中，而不是应用软件文件夹。因此，接下来我该怎么办？我想我需要找到一个对应于这个PIC18文件夹的原始安装文件，也许是通过搜索旧的VM文件结构，ORB）再次启动Google，看看我是否可以找到一个简化的PICC-18安装教程。S！



      以下为原文

    Thanks dan1138.  I will try a few things based on your advice, and then otherwise perhaps you (and/or others) can help me get to where I need to be.  I sincerely appreciate it.
 
Right now I have a WinXP VirtualBox VM with MPLAB 8.56 and HITECH v9.71 installed.  I also have an old legacy workspace.  When I open the workspace, it mentions that I need to change toolchain.  I change the toolchain to the only available Hi-Tech entry found, which is "HI-TECH Universal Toolsuite", containing "HI-TECH ANSI C Compiler", located at "C:Program FilesHI-TECH SoftwarePICC9.71abinpicc.exe".    When I try to build, however, I get an error in the output window: "No valid installed HI-TECH compiler drivers".  From here I'm stuck.  I did Google that error and found mention of UAC, but this is Windows XP which I believe predates UAC.  I am running as the only user which is administrator (not named "Administrator").  NOTE that I have the original install files for these, and included is a LICENSE FILE.
 
Even if I get the above to work, it might NOT support PIC18 devices.  I think the above may be a dead end because of this.
 
Alternatively, I find that over the past few months of low level background effort on this, I have come to have a folder "C:HITECHPIC18" that contains "binpicc18.exe" dated 4/10/2002.  I believe that THIS is where I need to be focusing.  However, it appears that this is a folder that's already the result of an install, and I think I must have copied it, perhaps from a long dead legacy VM of a long dead legacy machine.  To confirm this belief, I notice that all the folders in the tree are dated recently, 10/9/2017, but all the file contents are 4/10/2002.  This implies that the contents are 15+ years old, but that I copied the folder onto my VM C drive just last October.  Unfortunately, I don't recall from where I got this, and I don't think I have the original install "program" that would have set up DLL's and registry entries other things (those are bad thing to be missing), or paths or changes to MPLAB files (such as creating toolchain entries).
 
MY NEXT QUESTION was going to be, how can I manually add this toolchain to the list of registered toolchains in MPLAB.  However, having written the above paragraph, I become worried about having bypassed the Windows XP install.  Decades ago, back around Win 3.1 for example, there was no registry and software designers put their DLL's in their own folder.  Copying to install (and stealing, unfortunately) software was easy.  But by Win95 or whenever the registry was created, copying to install no longer works, because the registry isn't set and the DLL's or COM's or other things are in a windows folder, not an application software folder. 
 
Therefore, what should I do next?  I am thinking I need to either
A) Try to find the original install files that correspond to this PIC18 folder I have, perhaps by searching through old dead VM file structures, or
B) Start Googling again to see if I can find a streamlined PICC-18 install tutorial.
 
Otherwise, I'm just spinning in circles!

我突然取得了一些进步。我检查了旧邮件，发现了一些许可帮助。现在我安装了MPLAB 8.56和高科技835PL3。它运行成功。然而，它是在演示模式，并将在20天内退出。嗯，我确实有我旧的许可证重复在旧电子邮件。我只是不知道该怎么办。也就是说，我如何告诉HealthTeal835PL3关于我的许可证？安装过程中没有询问。



      以下为原文

    I suddenly made some progress.  I checked old email, found some licensing help.  Now I have MPLAB 8.56 and HI-TECH 8.35PL3 installed.  It RUNS SUCCESSFULLY.  However, it's in demo mode and will quit in 20 days.  Well, I do have my old license key repeated in that old email.  I just don't know what to do with it.  That is, how do I tell HI-TECH 8.35PL3 about my license?  It didn't ask during install.

嗨，有2个编译器从HiTeCH到8位设备。我猜你安装了PIC10/12/16编译器而不是PIC18编译器。你可以从这里下载老的HiTee编译器：HTTP://www. McCHIP.COM/Dealth-Tooals/DeaveSosialSeaveSeCurk，用于“高科技C档案”的问候。



      以下为原文

    Hi,
there were 2 compilers from HiTech for 8 bits devices.
My guess is that you installed the PIC10/12/16 compiler instead of PIC18 compiler.
You can download the old Hitech compilers from here :
http://www.microchip.com/development-tools/downloads-archive
Search for "HI-TECH C Archive"
Regards
 

啊哈，我找到了活动。但是它要求更多的信息。我有一个“序列号”。但我没有“注册号”或“激活键”。



      以下为原文

    Ah ha, I found activiate.exe.  But it asks for more info.  I have a "serial number".  But I don't have a "registration number" or "activation key".

对于MPLAB集成，您可能需要UnvialSoalStudio-1.37安装程序。您是否确实需要使用编译器的HCPIC18-STD-835PL3版本？如果这个版本不支持你的PIC18目标，那么PICC18189980YWY版本是你的下一个最佳选择。从我已经能够找到的许可证是一个节点锁定类型，需要一个由高科技产生的密钥为特定的计算机安装完成。可能的是，您的许可证密钥可能不再在新VM安装中起作用。在因特网上有一些关键的发电机可以用来激活老的PICC18编译器。一个谷歌搜索短语“高科技通用RSA KEGGEN V2.2”可能会出现一个FTP网站或两个。



      以下为原文

   

For MPLAB integration you may need the UniversalToolsuite-1.37 installer.

Do you know for certain that you need to use the HCPIC18-std-8.35PL3 version of the compiler?

If this version does not support your PIC18 target then the PICC_18_9_80_win version is your next best choice.

From what I have been able to find the license was a node-locked type that requires a key generated by HI-TECH for the specific computer the installation is done on. It is possible that your license keys may no longer function in your new VM installation. There are key generators floating around the internet that can be used to activate old PICC18 compilers. A google search for the phrase "HI-TECH Universal RSA Keygen v2.2" may turn up an ftp site or two.

如果你有许可证代码，而不是密钥文件，你可以尝试联系：SWVIGRIGN @ MICHCHIP.COM他们应该能够生成它，也许告诉你你是什么版本。它应该是一个长串的字母和数字。我认为他是正确的，9.71是PICC而不是PICC18。



      以下为原文

    If you have the license code but not the key file you can try contacting: swlicensing@Microchip.com
They should be able to generate it and maybe tell you what version you are at.
It should be a long string of letters and numbers.
I think he is right, 9.71 is PICC not PICC18

NKurzman，让我假设一个假设：你的咖啡壶在煮一杯的时候开始使用四倍的水。去制造商的网站，发现，因为你搬到一个新房子，咖啡壶已返回免费模式。要把它拿到许可证模式，只需发送你的购买证明和地址，并得到一把钥匙。所以你这样做，然后发现你的咖啡机不再是当前的模型，你需要联系传统的支持。遗产支持告诉你，他们找不到一个记录，你的咖啡机的序列号的许可证已经被转移到你的地址，你能提供一份原始发票的副本。在提供所要求的文件之后，你被告知知道如何制作钥匙的人已经离开了几个星期，所以请耐心等待。这个故事只是一个类比，所以不能与现实世界中的任何情况特别相关，但是请考虑以下问题：假设如何？你会很有耐心吗？你有可能寻求其他的解决方案来满足你的咖啡需求吗？



      以下为原文

    @NKurzman,
Let me pose an hypothetical situation:

So your coffee maker started using four times as much water when brewing a cup. Going to the manufacturers web site and find that because you moved to a new house the coffee maker has returned to free mode. To get it to license mode just send in your proof of purchase and your address and get a key. So you do that then find that your coffee maker is no longer a current model, you need to contact legacy support. Legacy support tells you that they cannot find a record that the license for the serial number of your coffee maker has been transfered to your address and could you please provide a copy of the original invoice. After providing the requested documentation you are told that the person that knows how to make the keys is off for a few weeks so please be patient.

This story is just an analogy, so cannot be specifically relevant to any situation in the real world, but please consider these questions:

How hypothetically patient would you be?

It is just possible that you would seek for other solutions to fill your coffee needs?

这个编译器不支持PIC18.MPLAX X仍然支持高科技V9编译器，并且你不必愚弄所有工具套件的东西，它自动配置。它可以导入你的MPLAB 8项目。



      以下为原文

   
 
This compiler does not support the PIC18.
 
MPLAB X still supports Hi-Tech V9 compilers, and you don't have to fool with all of the tool suite stuff, it configures automatically.  And it can import your MPLAB 8 project.

丹：是的，不是。你有一个完美的项目，并希望做出一些小的改变。切换到新编译器可能会导致问题发生，需要进行更多的测试。遗留产品的R.O.I是什么？在这种情况下，他应该能够让它发挥作用。如果项目是在预OCG编译器上完成的。有工作将它移植到XC8。在这种情况下，他们需要做出最好的选择。1。始终备份编译器和密钥。2。总是在代码中写入编译器版本。并确保你更新它。



      以下为原文

    Dan yes and no.
You have a perfectly working project and want to make minor changes. Switching to a new compiler could cause issues to apper and require much more testing. What is the R.O.I on a legacy product.
In this case he should be able to get it working. If the project was done on a pre OCG compiler. There will be work to port it to XC8.
They will need to make the desision about the best way in this case.

1. Always back up compilers and Keys.
2. Always write the compiler version in the code. And make sure you update it.

请注意，我已经离开论坛几天了。我看到很多新的帖子。这不是时间有效地阅读所有这些，但非常感谢这些产品。我读了最后一个来自NKurzman，谁击中钉子头部，以及隐含的部分以前的转换。注意我的问题已经解决（到目前为止）。我现在在我的VM上运行MPLAB V856，还有我从FTP获得的高技术PICC-18 V835PL3：//编译器Ro:C0MP！0511 @ FTP.Microchip .com／。建立，但在超慢演示模式和20天的警告。然后，鉴于我已经有了一个旧的遗留许可证，我得到了SW.ReavigeMigChIP.COMTO的帮助，使我的许可证再次生效。当然，现在我发现我的更改太复杂了，无法简单地编辑、构建和运送给我的客户进行测试（因为我已经在他们的遗留产品上做了很多次）。相反，我需要调试和分析。织补。现在我想让我的旧ICD 3工作（我给我的ICD 2给这个客户）。是的，我看到了一个关于VM的警告，我意识到了这些担忧。我即将发布一个新的问题。张贴后，我会回来这里，并把一个链接，希望一个或多个你看我。非常感谢，非常感谢你的帮助。-赫尔穆特



      以下为原文

    Please note I've been away from the forum for a few days.  I see a lot of new posts.  It's not time effective to read all of them, but thanks very much for the offerings.  I did read the last one from NKurzman, who hit the nail on the head as well as implied parts of the prior conversion.
 
NOTE MY PROBLEM HAS BEEN SOLVED (so far).  I now have MPLAB v8.56 running on my VM, along with specifically HI-TECH PICC-18 v8.35PL3 that I got from ftp://Compilers-RO:C0mP!0511@ftp.microchip.com/  .   That built, but in super slow demo mode and a 20-day warning.  Then, given that I already had an old legacy license, I got assistance from SW.Licensing@microchip.com to get my license working again.  Now it builds in a snap and offers to do so forever.
 
OF COURSE, now I find my changes are too complex to simply edit, build, and ship to my customer to test (as I have done many times on their legacy products).  Instead, I need to debug and analyze.  DARN.  Now I'm trying to get my old ICD 3 working (I gave my ICD 2 to this customer).  Yes, I saw a warning from someone about the VM, and I am aware of such concerns.  I'm about to post a new question about that.  After posting, I'll come back here and put a link, in hopes that one or more of you look into that for me.
 
Thanks VERY, VERY much for all of your assistance.
 
-Helmut

http://www. McCux.com……1033 915ASPX？树=真



      以下为原文

    http://www.microchip.com/...1033915.aspx?tree=true