Page 1 of 1
Hint for the Kowalski simulator
Posted: Wed Oct 22, 2008 12:33 am
by 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.

Posted: Wed Oct 22, 2008 3:57 am
by 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.
Posted: Fri Oct 31, 2008 10:44 pm
by Mats
In Unix there are the standard commands
dos2unix
and
unix2dos
Posted: Tue Nov 11, 2008 6:12 pm
by Nightmaretony
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...
Posted: Wed Nov 12, 2008 1:23 am
by 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.

Posted: Sat Nov 22, 2008 5:25 am
by 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
