>Now you made me curious :-) What are the most powerful feature of Hi-Tide >that helps you the most? When writing new C source codes, it is important to secure any related old codes/variables/functions/headers can be watched at the same time on all sub-windows (2x2 is normal, sometime 2x3, occasionally 2x4, my 2nd computer screen is only 15 inch, otherwise, I might just keep 2x4 for easy of use purpose if a 19 inch screen is used. It actually can be used in any style, e.g. 1x1+3x1, 1x3+1x2, etc. I personally like the 2x2 style, which makes me comfortable most of the time.). And, most of the time, they (functions, variables, constants, arraies, etc) are all in the same xxx.C file. When our guys were working on the PICKit 2 source code for the new PTG feature (Programmer-to-go, SPI bused memory, max support memory 4M bytes), this multi-split sub-window feature helps a lots too. One of my engineer spend 8 hours to get familiar with the firmware source code, and about 1 hour to accomplished the enhancements. I was told, without the HI-TIDE V1.2x, he will need at least twice the time to get familiar with the Microchip PICKit 2 C source codes due to the fact the Microchip source code are distributed multiple locations. If you can only watch one function at a time, you will need move your mouse like crazy to catch up the program flow-chart. That's just another success story how tools affect programming efficiency. All PICKit 2 firmware C source code and C# PC source code has been submitted to Microchip PICKit 2 team in the middle of March. Now the C# source code has been successfully integrated into the V2.61 releases (Special thanks to Walter, he left Microchip right after the C# integration and co-working with us). We hope the firmware code will be integrated into the future releases soon. So our work will contribute to the whole PICkit 2 community, especially those who had contributed to this "open-source" programmer. It is a pitty the PICKit 3 can only support max 512K bytes for not yet availbel PTG feature. Our contribution, have makes the PICKit 2 a better choice for any one like the PTG and have a large target Hex files (e.g. most of the PIC24 and some dsPIC33 have now 256K bytes of Memory, those chip's PTG will definitely need large PTG capacity. Our SPI bused design can fulfill those customer need. And our Product line has been using these SPI based PTG funciton ever since Jan-2009.). We have heavily tested both the C firmware code and C# code internally since the middle of January, so far, the PTG feature on our 512K byte, 1M byte, 4M byte version of PICKit 2 prototypes works like a charm. The SPI speed indeed is faster than the 400K I2C bus on both programming downloading and reading. Funny N. Au Group Electronics, http://www.AuElectronics.com -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist