![]() ![]() ![]() |
What LinKT can do for you...
Whenever a connection is established, LinKT tries to recognize the software which is used by the remote station. LinKT detects the following system types:
If these features are enabled, the program checks every incoming packet to see whether the remote-station is initiating a file-transfer using either 7plus or #BIN# and saves the file in the preselected directory.
Using LinKT it is very easy to notify all connected stations that you have to leave your station for some time, e.g. to answer a phone-call or something like that. Just press ALT-A to open the away-dialog. Read on at Chapter 3.2.1: Menu; File - Away
LinKT provides a configurable AX.25-router. You can associate routes with callsigns using the router dialog. Whenever you enter a callsign in the connect dialog LinKT will complete it with the corresponding route.
LinKT provides the two most common compression methods: //COMP - as used in MCUT, SP, WinGT, TNT - and #HUF# of TOP.
//COMP compression can be enabled by sending //COMP ON to the remote station, #HUF# will be activated when pressing <ALT-H>.
We like to emphasize that compression is not encryption and is readable by everyone using the appropriate software. The algorithms may be looked up at the source code
LinKT mainains a log of all connections in ~/.kde/share/apps/linkt/log/
LinKT can automatically upload and download 7plus files, it knows the AutoBIN protocol by Sigi Kluger DK4NB, the successor DIDADIT which has been developed by #1409 and the "Yet another Packet Protocol" (YAPP).
Messageliste from BBS's are transferred to a special selection window, where you can easily choose and manipulate a message. You can read it, kill it, copy it another destination or change its lifetime (if the bbs supports it. You have to specify the format of the message list, using the user-properties dialog. If LinKT doesn't recognize the message list of your homebbs, you have to edit the boxcheck.dat file.
This "Tamagotchi-mode" always shows up when you need it like a
hole in the head, i.e. you are, um, or were doing something extremely
important and the programme decides that it is completely bored. If you are
lucky, this will only happen during compilation and/or at installation time,
and it will not justify any invasive retaliation against your otherwise
unarmed computer. None the less, these digestive malfunctions during operating
sessions are triggered by many and various mechanisms, and their seeming
ability to hit the road out of nowhere makes computing
an algorithm capable of belly-ache prediction slightly beyond impossibility.
But these little dirt-crawlers aren't quite as smart as they
think. Once in a while one of them peeks out right in front of our splendid
fast-action-team and is overrun in less than an instant, giving us the
opportunity to seduce it into the bits and bytes it was made of. Having
successfully completed such a thorough analysis, the firm smartly shifts its
attention to drawing a line beneath the beast's pityful existence. Fooling
with the firm has its price. And so no-one will ever forget, a shiny brass
plate is added to the others in the losers' hall of fame, as it is commonly
referred to by the "ultimately annoyed hackmasters", who have
decided that a simple RTFM! says more than one thousand words. In other
words, kindly read the instructions before flaming us ...
![]() ![]() ![]() |