FTN software for ZX

╔═════════════════════════════════ ═════════════════════════════
║Forward by Felix Knyazev
╠══════════════════════════════ Apiya: ZXNET.SOFT
║From: Felix Knyazev (500:812/1.509)
║To: Kirill Frolov (500:812/23.25)
║Subject: "FTN software for ZX"
║Date: Wednesday 22 November 2000 (04:35:04)
╚══════════ ══════════════════════════ ══════════════════════════

====================== beginning of the forward =======================

Greetings, Kirill!

[Tuesday 21 November 2000] at [11:55:02] Kirill Frolov wrote a letter to
Vladimir Klymus.
They discussed the topic "FTN software for ZX". Let's continue what we started...

[skip]

VK>> It’s so difficult to understand that hobeta makes it possible to transfer
VK>> and
VK>> restore tr-dos files without any problems
VK>> (disappearance of
VK>> start address, data loss, idiocy)?

KF> Have you seen ZXZIP? Some clever people also like it,
KF> it turns out to be a hobeta in
KF> a hobeta.

I will publicly express my “XO” on this matter:

When I receive a file (from the network, for example. I’m still a REAL person, no matter how strange
it sounds.), the first thing I look at is its extension. It depends on what this file is and the sequence of my further actions to process itthe
file itself. If I see *.$Z - everything is _immediately_ clear and understandable to me - this is ZXZIP, i.e.
DeHobeta -> ZXUNZIP. Hooray! Everything is as simple as snow in winter! It saves both time and
nerve cells (see below), which, as is known, are not restored. Also
everything is clear and understandable to me when I see *.zip (in small letters!) - this is a PKZIP archive.

And then something like *.ZIP (in capital letters) or even worse -
*.Z (*.z) falls down. What is this???!!! :-E After all, PKZIP archives are now actively used on Speck! Then the pandemonium begins. Let's look at the beginning of the file
(_additionally_ loading some viewer thread): aha! the first two bytes of "PK" are a
PKZIP archive. It is _without_problems_ (due to the incomplete file extension, the check
for a PKZIP archive is carried out using the internal structure of the file) is set against
spekkovsy PKUNZIP (praise the authors!). OK, we've sorted that out.

One thing remains: under *.ZIP there is a ZXZIP archive hidden (there were exceptions. This
turned out to be a WANTED ZXZIP archive! i.e. again, at the "request" of ZXUNZIP
some kind of viewer is additionally loaded. Creepy...). But what about the extensions *.Z
(*.z, *.ZiP, *.ziP, etc.) for the ZXZIP archive?! Here
_specific_hemorrhoids_ begin - you need to add this 'Z' (+ variations, see above) to 'ZIP' in the disk doctor (again additional
loading!), otherwise ZXUNZIP will curse dirty
(it just won't show it)archive)!

People, let's save our time and nerve cells when working on Speck!!!

ZXZIP - *.$Z
PKZIP - *.zip (in small letters!)

Naturally, if you _locally_ exchange ZXZIP archives with the same
Melon, then you can (should) not bother if there is a connection between you appropriate
agreement.

Sincerely, Felix.

[I ZX]
-+- Lara Croft v4.50
+ Origin: We are all beta testers in this life... (500:812/1.509)

======================= end of forward =======================

Sincerely, Felix.

[I ZX]

Press RESET immediately, Felix!

22 Nov 00 04:35, Felix Knyazev wrote to Kirill Frolov:

FK> And then something like *.ZIP (in capital letters) or worse
FK> falls - *.Z (*.z). What is this???!!! :-E After all, on Speck now

[...] skip.

First, we open it up, then we look at what’s inside - if it’s PK, then set it up
pkunzip, if the file name, then put the ZIP extension and run zxunzip. And if some smart guy wants this file, then a pandemonium begins: you need to find the dehobeta, find the second piece of the file (it will be cut), among a dozen such pieces (and all with the same name) select the one you need and find it. And so
ten times in a row. And then it turns out that inside this zxzip all the files are once again
wanted (why???).

FK> People, let's save our time and nerve cells when working on
FK> Speck!!!

FK> ZXZIP - *.$Z
FK> PKZIP - *.zip (in small letters!)

FK> Naturally, if you _locally_ transferring ZXZIP archives with the same
FK> Melon, then you can (should) not want to, if there is
FK> an appropriate agreement between you.

All your reasoning can be reduced to the opposite: let's save time
and nerve cells and /never/ want to use zxzip and text files!

ZXZIP - *.Z *.ZXZ *.ZIP (lastoption is preferable)
PKZIP - *.zip

Naturally, if you like sex with a computer, then you can locally
want everything...

Besides everything else, for _not_ using the hobby you can bring
one more argument - the remains of long zxzip archives are not cut into pieces
17 bytes each.

In general, it’s time to switch to using other archivers.
Well, at least hrip.

* Crossposted in REAL.SPECCY

KF> All your reasoning can be reduced to the opposite:
KF> let's save time
KF> and nerve cells and /never/ want to use zxzip and text
KF> files!

KF> ZXZIP - *.Z *.ZXZ *.ZIP (the last option
KF> is preferable)
KF> PKZIP - *.zip

*.ZXZ - I didn’t like it, but in general
if this is made a standard, then you won’t have to worry about anything
except for basic and some code files.

By the way, the length of basic files can be selected such that the extension becomes *.Bas
or *.BAS, with almost any
length of the file itself, which is usually loaded with a 3D13 monolad
sector by sector, then you won’t have to bother either.

KF> Besides everything else, for _not_ using
KF> you can give
KF> one more argument - the remnants of long zxzips
KF> archives are not cut into pieces of 17 bytes.

Felix simply did not mean the general case, but spoke about short
zips (single-file), modestly keeping silent about large ZIP-elephants.

KF> In general, it’s time to switch to using more other
KF> archivers.
KF> Well, at least hrip.

it’s still early or, as you might say, it’s too late ;)

Thank you for your attention.

24 Nov 00 01:29, Evgeny Goljakov wrote to Kirill Frolov:

EG> *.ZXZ - I didn’t like it, but in general
EG> if this is made a standard, then you won’t have to worry about anything,
EG> except basic and some code files.

If these If you pack basic files with zip, then you don’t need a job at all.

EG> By the way, the length of basic files can be selected such that the extension
EG> becomes *.Bas or *.BAS, with almost any length of the file itself,
EG> which is usually loaded with a 3D13 monolad sector by sector, then also
EG> you won’t have to worry.

You’ll have to. Don't write nonsense.

...
KF> You'll have to. Don't write nonsense.

Arguments to the studio.

Thank you for your attention.

EG>>> By the way, the length of basic files can be selected such that the extension
EG>>> becomes *.Bas or *.BAS, with almost any length of the file itself,
EG>>> which is usually loaded with a 3D13 monolad sector by sector, then also
EG>>> you won’t have to worry.

...
KF> If the extension is BAS, then the length of the file is not any, but
KF> 'S'*0x100+'A'.

based on what you wrote, this is not the length of the file, but the length of the basic
part of the file with the extension BAS (A maybe it's just data).

KF> And so on until the length of the file is measured in bytes, and
KF> not sectors --

read the underlined

KF> piece is lost at the end (most of the file).

Lara correctly processes the sector length of the juyuki and even a smaller
part of the file is not lost.

What programs did you mean that everything is lost there?

Thank you for your attention.