Mike:

Thanks for your reply.

>Not sure about this, maybe your editor is saving control characters in
>the file.

I think you're right. How do I find out? They aren't visible on the screen
so you can't select and delete them.


>>and 125 "Illegal condition" EOF (even though there is no
>>character visible at that position);
>
>There *must* be an 'end' directive at the bottom of the file.  Not having
>it was just a warning with the old MPASM but a fatal error with the
>windows one.
>

Right, there is one at the end. This error is right at the beginning.



> and 131 "Processor
>>type is undefined" (but it's in the include file).
>
>I always put a 'processor' directive at the top of the main assembly
>file.  The include files supplied with MPLAB don't define the processor.
>Maybe there are bugs in using the old 'LIST P=' method.
>

OK, I tried using the directive Processor PIC16C54. It results in an Error
132: unknown processor (16C54
                                )
with the close parenthesis on the next line as shown above.

>>
>>In the other case, it usually chokes on every line, with a
>>Warning 205
>>"Found directive in column 1" and an
>>error code 122 "Illegal opcode".
>
>I think this happens when the processor type is not defined.  None of the
>opcodes are legal without defining a processor first.

Bingo! When I added the processor directive, they all disappeared. But that
left me with the errors noted above.

The other Mike suggested a hex editor. Would that show hidden characters
and allow me to delete them? Where would I find such an animal.

Thanks for your help,
Reg