???? invalid lazy-loaded byte code: ast-lock-mode

[Edwin Earl Ross]

The file COBOL.el was created using NT XEmacs and saved. Now when I try to
load it, I get the following message: "invalid lazy-loaded byte code:
ast-lock-mode." In addition, NT XEmacs will not exit, it gives the same
message.

Moreover, when I open this file in NOTEPAD, it is not a text file. The end
of lines have been replaced with $(^*%*! up characters.

Edwin Earl Ross
If computers are so damn fast,
why are we always waiting on them?

[Jan Vroonhof]

"Edwin Earl Ross" <Edwi...@yahoo.com> writes:

> The file COBOL.el was created using NT XEmacs and saved. Now when I try to
> load it, I get the following message: "invalid lazy-loaded byte code:
> ast-lock-mode." In addition, NT XEmacs will not exit, it gives the same
> message.

Something has been corrupted I think. XEmacs doesn't use lazy-loading
of byte-code at the moment.

> Moreover, when I open this file in NOTEPAD, it is not a text file. The end
> of lines have been replaced with $(^*%*! up characters.

Are sure it is not simply saved with Unix (or Mac) end-of-line
characters?

Jan

[Edwin Earl Ross]

I updated the packages, and afterward this happened. I reloaded XEmacs from
the binary download, and XEmacs started working OK again. However, it did
replace all the \n with something else. I had to fix those manually.

"Jan Vroonhof" <vroo...@frege.math.ethz.ch> wrote in message
news:bypusoo...@bolzano.math.ethz.ch...