At last.. an idiot even I can rip into.

"Indeed, however these are well documented in the manual."

Yep, but no-one mentioned the manual, and the gut is still having problems remarkably similar to those as detailed in the manual. Lets let him decide whether the suggestions were helpful shall we?

"How 'stack intensive' do you think printf() is? Note that printf() failures caused by passing too many arguments are not related to its stack usage."

Oh yes they are. It even says so in the manual. Isn't that right?

"Those examples will both fail, but not for the reasons you have given."

Do tell us all precisely why.

"If you're running out of stack space the last thing you'd want to do is move variables into idata."

Wrong again. Its not the only thing you can do, and it depends on where you stack has been placed. We all assume that he he's compiled a simple example to get the LCD working, and that the stack is low-down in data memory. Lots of people when they get to this stage don't even know that they can use idata when things get tight.

The first thing to do when printf() falls over when passed too much is to split it up into several calls. This uses less stack space. He did that and it worked. What does that tell you Don?

"You need to fix your delay function."

Just plain wrong. Please tell us all again exactly why you think it needs work, and I'll will happily put you straight. Otherwise STFU!

Regards,
Murray R. Van Luyn.