Jon, I too have thought seriously about making it work using assembly. I don't see the need for anything to have to be absolutely coded in 'C'. Regardless of the application. And I have been using assembly for a long enough time to be able to make the PIC do just about anything I want it to with only a little trouble. So, if you want to work on this, count me in. Let me know how you need me to do, and we'll go from there. Regards, Jim > > Unless the rules have changed, I believe that the program must not >> > only be written in C, but specifically in HiTech C. >> >> ...thus disqualifying the vast majority of PIC developers, especially >> those who don't do it for a living with employer money. I could very >> well be wrong, but isn't HT PICC by far the most expensive compiler >> you can find for the PIC? >> >> I'm sure it's a nice product (though I do prefer CCS), but at $850 the >> price is simply too steep for me. >> > I agree, its nice, but way too expensive, and I'm suprised HTsoft didnt > offer some prize as an incentive for people to buy their compiler- not > that I would though. > > I was going to give it a go with some kind of C.. rules or not, I dont > really have much desire for a RTOS for my pic collection or a 40Gb hard > drive.. just more stuff to loose when it all goes wrong :) .. but most > likely it will ultimately be written in assembler so any and all can > use it regardless of the language they use. No prizes, but it would be > neat anyway. > > If anyones interested on making this a collaborative project ( assembly > language) feel free to email me jon@hayseed.net and maybe we can get > this working... I look forward to masses of emails tomorrow :) > > Jon Baker > jon@hayseed.net > > -- > http://www.piclist.com hint: The PICList is archived three different > ways. See http://www.piclist.com/#archives for details. -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details.