Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dc01.r1000.mx.aol.com (Internet Inbound) with ESMTP id 2E18838000152; Sun, 29 Apr 2012 19:22:58 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1SOdR8-0008Vb-OG for rs_out_1@blacksheep.org; Mon, 30 Apr 2012 00:21:50 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1SOdR7-0008VS-Ux for rsgb_lf_group@blacksheep.org; Mon, 30 Apr 2012 00:21:49 +0100 Received: from nm7.bullet.mail.ird.yahoo.com ([77.238.189.21]) by relay1.thorcom.net with smtp (Exim 4.77) (envelope-from ) id 1SOdR6-0002Nl-5N for rsgb_lf_group@blacksheep.org; Mon, 30 Apr 2012 00:21:48 +0100 Received: from [77.238.189.48] by nm7.bullet.mail.ird.yahoo.com with NNFMP; 29 Apr 2012 23:21:47 -0000 Received: from [212.82.108.227] by tm1.bullet.mail.ird.yahoo.com with NNFMP; 29 Apr 2012 23:21:47 -0000 Received: from [127.0.0.1] by omp1004.bt.mail.ird.yahoo.com with NNFMP; 29 Apr 2012 23:21:47 -0000 X-Yahoo-Newman-Id: 85998.6306.bm@omp1004.bt.mail.ird.yahoo.com Received: (qmail 14913 invoked from network); 29 Apr 2012 23:21:46 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MIMEOLE:X-Antivirus:X-Antivirus-Status; b=CuIPbxIvH3V6jdxtF3k+1o59JaqIKcDu4dMGVXDF6WqSsFY0pbmpVqQAs3tBfTTAPjbt2jMvk7lb5SKXRhlNZ5e55HhZZPcwyvB8jwQ/y7StszaaZyJajBBFFecLKk9ga1cS9YaEfwAzZHCofRWZTambKkRV5PdvGn10Z3xT/Pw= ; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=s1024; t=1335741706; bh=+0Lw+51hT8j4SZJrmH+vUFYD9UX47TAcUxQuIN09Vsw=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MIMEOLE:X-Antivirus:X-Antivirus-Status; b=Sn+pSI+9KV7oOZlzc0+gmxRO0+AGw4AUWoJExERg4HyRo3Y2h/I/lCwRvGsrYl1qfkLidNVgVbewmZ3FLY2/PSkuZ2qgCpn/9rf2IuiYRkWx8D3EckqQuLEs8duyvs4YssvN+Y7jMo7uvyqKnBztMPKPrZN16tLNNUeRshPT3/k= X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 62Q6ZgsVM1lSEEJdm.8e5WEqKiTRjT.5NaJPnN_0VKBPvZo JXo8Yd4fDhyS_wYh4nkR13PdzAQ.cbiSaJEYsasf1XIyRzmxglBTC_cWgava 8dlIxL2QOSkjQfoU8urviiaPZ0EBlrRf_vDtk0yBEHQtK4T0LFGSdS2IdQL3 uMt.LOvnUysZvkQcROnI4yzjSu7V_66UHt4JaIBYmcTgjZhkLjOmvBs0Dcc. GWw93FuEQ2dj.P5n8FOc3kGGWev32aI8OjppjyBfcBH50r0sIiCoGoIXf36a 5Xvy9dRW7cA1dZHldgKPk40J.AVTWsTcjX6P6lEHLvBz5Td.ucgSDdT.Qh2L 5QHZEXrIP3T.SrxmH55Wl3SAY6UJVZXSNjda49l3Ihil32yy53WKYYQh1z14 58hGCwQqB6qQnsSmzlVxmMjymOoFncmAMJf.Hccsyl6GoCco8NbVz0IM- X-Yahoo-SMTP: fpz.2VeswBBs59bVshRPmMN51lcO2lgFRIvE4XTqE8dRwOxd70E- Received: from lark (alan.melia@109.155.42.60 with login) by smtp827.mail.ukl.yahoo.com with SMTP; 29 Apr 2012 16:21:46 -0700 PDT Message-ID: <008701cd265e$e1819680$4001a8c0@lark> From: "Alan Melia" To: References: <4F9D18DA.3030707@talktalk.net> <1335738784.91970.YahooMailNeo@web171604.mail.ir2.yahoo.com> Date: Mon, 30 Apr 2012 00:21:54 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.2001 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.2001 X-Antivirus: avast! (VPS 120429-1, 29/04/2012), Outbound message X-Antivirus-Status: Clean X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi Peter my success is much higher than that BUT I have found some PICs wont program correctly on some programmers though the s/w indicates the ought to. I would say if you are not using a Microchip programmer and s/w this might be part of the cause.?? This is one I have run into. [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [77.238.189.21 listed in list.dnswl.org] 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 33d261536bb1467bb13d5764461d5ec4 Subject: LF: Re: PIC Projects with no HEX code Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:412604864:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-AOL-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-m019.2 ; domain : btinternet.com DKIM : fail x-aol-sid: 3039ac1d40814f9dcd52377a X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Hi Peter my success is much higher than that BUT I have found some PICs wont program correctly on some programmers though the s/w indicates the ought to. I would say if you are not using a Microchip programmer and s/w this might be part of the cause.?? This is one I have run into. Reasons for lack of source inclusde, shyness and not wanting to be cricised for poor or naive programming. Producing commented source is quite a labour intensive job. If an "outsider" is to understand exactly what you have done. Many who reuse chunks of code cant be bother with the hassle Then I have seen code "stolen" and used for profit making ventures, or 98% copied, without any reference to the originator. Does it matter.....well it does to some people. The code is the majority of the investement in a PIC project. Remember a assembly coders stock-in-trade is a large collection of small routines which he used continually to achieve standard operations. Because these are used more than once they are usually well tested. I like to see source because I can learn how to write it myself from other peoples approaches. The most exasperating thing is if you suspect a bug (not just not working, but an exotic one) you have no way of. helping the originator Alan G3NYK ----- Original Message ----- From: "M0FMT" To: Sent: Sunday, April 29, 2012 11:33 PM Subject: LF: PIC Projects with no HEX code Success rate is about 10% on projects with the HEX code attached. If people don't want their projects duplicated then don't publish them FCS!!! Its pointless! M0fmt exasperated!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!