packet:history
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
packet:history [2025/06/10 14:15] – g4klx | packet:history [2025/06/10 14:19] (current) – g4klx | ||
---|---|---|---|
Line 71: | Line 71: | ||
I believe RP closed down sometime in the late 1990s, although by then I was doing other things and was no longer responsible for it. | I believe RP closed down sometime in the late 1990s, although by then I was doing other things and was no longer responsible for it. | ||
- | ===== KA9Q Net/NOS ===== | + | ===== KA9Q NET/NOS ===== |
In the TAPR DCC proceedings were articles by Phil Karn KA9Q about his developments. He wrote an MS-DOS program that offered a terminal with a great many commands that implemented, | In the TAPR DCC proceedings were articles by Phil Karn KA9Q about his developments. He wrote an MS-DOS program that offered a terminal with a great many commands that implemented, | ||
Line 83: | Line 83: | ||
One of my diversions was acquiring an Acorn Archimedes in the late 1980s. This was a marvelous machine, using an early iteration of the ARM processor, and for its time was a very powerful computer. Mine had 4MB of RAM, and although a little quirky, the operating system was pretty impressive. The OS used cooperate multitasking and required each program to voluntarily give up access to the CPU regularly. People were already using KA9Q NET/NOS under emulation on the Archimedes but the experience wasn't very pleasant. I decided to port KA9Q NET to the architecture. | One of my diversions was acquiring an Acorn Archimedes in the late 1980s. This was a marvelous machine, using an early iteration of the ARM processor, and for its time was a very powerful computer. Mine had 4MB of RAM, and although a little quirky, the operating system was pretty impressive. The OS used cooperate multitasking and required each program to voluntarily give up access to the CPU regularly. People were already using KA9Q NET/NOS under emulation on the Archimedes but the experience wasn't very pleasant. I decided to port KA9Q NET to the architecture. | ||
- | I chose the NET version because the central commutator loop lent itself to giving up the CPU after each iteration to allow the whole machine to multitask. I did add the ability to have a separate window for each session, AX.25, TELNET, etc. I ported the software in about one day. I was very pleased with the results and so were a number of other people since it ran much quicker and was also a good neighbour on the computer. I maintained that software for a few years before getting into Linux. | + | I chose the NET version because the central commutator loop lent itself to giving up the CPU after each iteration to allow the whole machine to multitask. I did add the ability to have a separate window for each session, AX.25, FTP, TELNET, etc. I ported the software in about one day. I was very pleased with the results and so were a number of other people since it ran much quicker and was also a good neighbour on the computer. I maintained that software for a few years before getting into Linux. |
I can now say that I know Phil very well, and have met him a number of times. He's moved on from packet radio, and I recommend his KA9Q Radio project if you want to try something exciting. | I can now say that I know Phil very well, and have met him a number of times. He's moved on from packet radio, and I recommend his KA9Q Radio project if you want to try something exciting. |
packet/history.txt · Last modified: by g4klx