Well, I thought this was gonna work, and I'll bet it will, but it's giving me fits. It looks like it may have something to do with using the "0" to know where the end of my string is in EEPROM. My screen goes blank (most of the time), when the program try to display one of those on the 2nd line of the display. Since I've never been able to get the display to show a number ending in "0" (zero), I thought maybey that had something to do with it, so I cahnged it to "99". With "99" in there, now it won't display a string that has a "c" in it past the string. For examle "Activity" is displayed ad "A"..."PicPrEvt" is displayed as "Pi". So I changed it to "1" and then "Ready" was displayed as "eady", so I just shut it off without going further through the menu.

I'm using portB interrupts to detect when i push a couple of push buttons to set it up. This has never been a problem in the past since I haven't been sing EEPROM to store the strings, but i wonder if that could have something to do with it?

Here's the subs that I call before doing an LCDOUT for line one and two:
lcdone: LCDOut $fe, 1 : LCDOut $fe, 2 ' Position cursor at home
Return
lcdsec: LCDOut $fe, $C0 ' Move to 2nd line on LCD
Return

Again, this has always worked fine too before using the EEPROM, so not sure that it has anything to do with it either. Do I need to somehow check and see if the EEPROM actually go read before placing the results in the LCDOUT command? If so, how would I do that without having to compare it to a string and then end up using all of that space again? Any help would be much apreciated..it's driving me wacky. ;-)