...I just pointed out that....guess we were thinking alike.  I'm just considering going in and making these changes no charge, just to make it easier to support going forward.  Like I have extra time to do this, but well worth while to do before it bites me or someone else again.


--- On Tue, 6/17/08, Olin Lathrop <olin_piclist@embedinc.com> wrote:

> From: Olin Lathrop <olin_piclist@embedinc.com>
> Subject: Re: [PIC] 16F887 and corrupted RAM/EEPROM
> To: "Microcontroller discussion list - Public." <piclist@mit.edu>
> Date: Tuesday, June 17, 2008, 6:38 AM
> alan smith wrote:
> > The
> > original author used the cblock directive, but
> hardcoded some
> > variables at the bottom end of the RAM, and as I added
> some
> > additional variables it wrote over the top a couple of
> these.
> 
> So anyone out there still wonder why you should always use
> RES to reserve
> RAM?
> 
> 
> ********************************************************************
> Embed Inc, Littleton Massachusetts,
> http://www.embedinc.com/products
> (978) 742-9014.  Gold level PIC consultants since 2000.
> -- 
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist


      
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist