Hint for the Kowalski simulator

[Nightmaretony]

Had to redo, new hard drive, reinstall.

Every time I wen tfor opening source, no delimiters, it looked more like a big block of gibberish.

How to get around that:

open the simulator. Make a new file.

Open your old source in Wordpad

Select all, copy and paste over then save in Kowalski.

[kc5tja]

Or, use a proper text editor that understands both Windows-style and Unix-style line endings, and re-save the file. There also exists conversion tools for this purpose, too.

[Mats]

In Unix there are the standard commands

dos2unix

and

unix2dos

[Nightmaretony]

kc5tja wrote:

Or, use a proper text editor that understands both Windows-style and Unix-style line endings, and re-save the file. There also exists conversion tools for this purpose, too.

Thanks. Didnt know what was going on and tried that one out in a little bit of despair. Still wondering why it zonked all my code like this with fresh reinstalls, though...

[kc5tja]

The code isn't zonked; it's how it was originally saved. Your files apparently have Unix-style line-endings, where each line of text ends with a single linefeed character ($0A). Modern text editors generally can read both, but usually save in Unix-style files, because it eliminates all the conversion hassle you yourself are now experiencing.

Older-school editors still exist, and retain the MS-DOS and CP/M standard of CR/LF pairs. Apparently, Kowalski's program falls under the "needs serious renovation" category.

[Nightmaretony]

K. it only got to me because the change that was done was a fresh XP install. I used my saved reinstaller file and also downloaded with the same result. Since my code and the Kowalski program were the same, I figured something screwball happened in the XP install to the new hard drive.

Thanks on the understanding of it, though