>> ... and of course it is ...
> Translation: As I suspected it would be.

so the OP will know where to look for the answer to a similar problem 
next time. don't (just) give them food, learn them how to grow crops

>> Lazy...
> 
> Translation:
> 
> 1.     I'm standing in as a locum.
> or
> 2.     I'm tired of posting here anyway.
> or
> 3.    ... ?

3. it can be considered a bit impolite to ask a question without first 
looking in top few the most obvious places.

I have no idea what a locum is meant to be?

>> MCLR shoud *not* be left open. And you should *not*
> try to use "internal MCLR" at this stage. There is
> no reason to go into details at this stage, just
> don't try it...
> 
> Translation:    This snippet of valuable information , 
> unlike the other, may not be obvious from the data sheet for 
> a beginner but I'm not going to tell you why. Just trust me 
> on this. After all, what option do you have?

MCLR should not be left open, this is perfectly clear from both the 
datasheet, the programming documentation, and from the meaning of the pin.

The fact that internal MCLR can cause problems is not clear from the 
obvious sources, so it seems a good idea to me to give that hint to the 
OP, or should JE have kept that to himself?

The explanation for this problem is complex, and the link (to the 
microchip forum) can be found in earlier posts. I don't understand why 
you seem to critisise JE here. Is it for bidden to give a very important 
hint without also giving the (very long and complex) explanation (that 
is available elswhere, explained by probably the only person why realy 
understand it)?

-- 

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu

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