It's nothing spectacular, but it's a thing!
It started as a QBASIC project long ago, now I ported it various 8-bit CBM BASIC dialects to explore the differences.
Features:
-It can translate from text to Morse, or from Morse to text.
-The input can be typed in, or loaded from a file.
-It has different modes of operation, in how it uses the signal marks. I have implemented 3 modes based on what I saw in different programs. The characters of the signal marks can be specified by the user.
-Sound output can be configured too.
-The character output can be saved to disk. It will work even if the output is longer than 255 characters (and also can be loaded back).
Commodore 64 version
Commodore 16 / Plus/4 version
16K Commodore PET version
16K Commodore VIC-20 version
D64 image file download:
https://www.mediafire.com/file/91g2wqbm ... T.d64/file
Might aswell release the QBASIC original:
https://www.mediafire.com/file/04voj860 ... E.BAS/file
And a Commander X16 port:
https://www.commanderx16.com/forum/inde ... ranslator/
Scrubbly Morse Code Translator
Moderator: Lemoners
- 1xWertzui
- William Wobbler
- Posts: 127
- Joined: Sun Dec 10, 2017 12:12 pm
- Location: Bivalybaznád, BAZ megye
- Age: 29
Scrubbly Morse Code Translator
Last edited by 1xWertzui on Sun Mar 28, 2021 8:02 pm, edited 2 times in total.
- TomXP411
- Rick Dangerous
- Posts: 2492
- Joined: Mon Apr 23, 2018 11:17 pm
- Location: The Altair Sector
- Age: 52
Hey. Thanks for this.
I've been collecting Morse trainers. This one seems to work pretty well, although the one thing I'd change is to preset the short/long/mark symbols and mode, so the user doesn't have to enter the same information every time.
I've been collecting Morse trainers. This one seems to work pretty well, although the one thing I'd change is to preset the short/long/mark symbols and mode, so the user doesn't have to enter the same information every time.
Ultimate 64 · C128 · 64C · Turbo Chameleon
Keyrah · Ultimate II+ · SD2IEC · 1541 · 1541-II · 1571
RIP my '84 C= 64
Keyrah · Ultimate II+ · SD2IEC · 1541 · 1541-II · 1571
RIP my '84 C= 64
- 1xWertzui
- William Wobbler
- Posts: 127
- Joined: Sun Dec 10, 2017 12:12 pm
- Location: Bivalybaznád, BAZ megye
- Age: 29
UPDATE: "it can save the output even when it is longer than 255 characters, and also can load it back too"
Yeah... I should have tested it more beforehand if I'm boasting about it. Now fixed.
Except the compiled version simply doesn't want to do it regardless
@TomXP411
There IS a preset for the signal marks. You just have to press d (or return because it is highlighted), and the default settings are used without further question.
Sorry if that menu point is confusing. Originally it was recessed like the sound configuration menu, but when I decided I go for a 16k limit, unnecessary menu code had to be simplified.
Yeah... I should have tested it more beforehand if I'm boasting about it. Now fixed.
Except the compiled version simply doesn't want to do it regardless
@TomXP411
There IS a preset for the signal marks. You just have to press d (or return because it is highlighted), and the default settings are used without further question.
Sorry if that menu point is confusing. Originally it was recessed like the sound configuration menu, but when I decided I go for a 16k limit, unnecessary menu code had to be simplified.
- 1xWertzui
- William Wobbler
- Posts: 127
- Joined: Sun Dec 10, 2017 12:12 pm
- Location: Bivalybaznád, BAZ megye
- Age: 29
Yet another revision, and an urgent one. If anybody keeps a copy from prior to this, update it.
The previous revision of the D64 file had a date of April the 1st, 2021. I didn't imply any jokes by that, it's simply when I was getting around to upload it to the MediaFire storage. However, the joke was on me, because it didn't work!
I only noticed it recently when I randomly downloaded it. The C64 program ran, but within the program accessing the disk for saving/loading failed constanly. I spent almost a day troubleshooting the code, until it turned out that THE D64 FILE ITSELF WAS CORRUPTED, and so were some of the files.
Last time I made the modification on the D64 file with a Java program called Droid64, version 0.17b, which is in alpha stage and does contain warnings that it may have errors, but at the time this was the only viable option to me.
Validating the disk didn't help, so I re-made the D64 file, this time with D64 Editor. The programs on the disk didn't change.
To differetiate this revision from the previous one.
The Disk ID was bumped up form 01 to 02.
The order of some files changed.
There are also 3 sequential files now. These can be loaded for testing disk read. Dollar-B is a test of the longest input the program can take from disk (more or less).
The previous revision of the D64 file had a date of April the 1st, 2021. I didn't imply any jokes by that, it's simply when I was getting around to upload it to the MediaFire storage. However, the joke was on me, because it didn't work!
I only noticed it recently when I randomly downloaded it. The C64 program ran, but within the program accessing the disk for saving/loading failed constanly. I spent almost a day troubleshooting the code, until it turned out that THE D64 FILE ITSELF WAS CORRUPTED, and so were some of the files.
Last time I made the modification on the D64 file with a Java program called Droid64, version 0.17b, which is in alpha stage and does contain warnings that it may have errors, but at the time this was the only viable option to me.
Validating the disk didn't help, so I re-made the D64 file, this time with D64 Editor. The programs on the disk didn't change.
To differetiate this revision from the previous one.
The Disk ID was bumped up form 01 to 02.
The order of some files changed.
There are also 3 sequential files now. These can be loaded for testing disk read. Dollar-B is a test of the longest input the program can take from disk (more or less).
Who is online
Users browsing this forum: No registered users and 0 guests