NAM 0.30

So. The subject can call bosses based on the current time. Naturally only if
you have a watch. For this, the CmosDrv.C driver from Lara Croft 4.50 is used.

Interesting fact. NAM version 0.23 was released on January 26, 2001, i.e. exactly a year ago.

Currently, work is underway on the frecks. There will be a
release within the next week.

I took into account Vivid's wishes. Will be implemented in future
versions.

P.S. I have an idea to make a register, i.e. instead of the line:
{NAM}{0.3b/Noncommercial}{Unregistered}
It will be something like:
{NAM}{0.3b/Noncommercial}{Registered to Sergey Zotov}
Question. What do similar lines look like for registered soapers?

ZXNet: 500:8462/1 ~/ <~ http://zs80.chat.ru/
Fido: 2:5057/21.93 /_ _> ftp://zx-museum.org.ru/zs/

Sat 26 Jan 2002, at 20:26:03 Sergey Zotov told All about NAM 0.30

SZ> So. The subject can call bosses based on the current time. Naturally only
SZ> if
SZ> you have a watch. For this, the CmosDrv.C driver from Lara Croft
SZ> 4.50 is used.

Thanks for that. Otherwise, I already called Megus a couple of times with a modem when I accidentally copied the wrong Namov setup to the ramdisk (in one setup - only Fido (CM
node), in another - ZXNet (22:00 - 06:00) and Fido).

SZ> Interesting fact. NAM version 0.23 was released on January 26, 2001, i.e. exactly a year
SZ> ago.

Funny. ;)

SZ> I took into account Vivid's wishes. It will be implemented in the next
SZ> versions.

I hope and wait. ;)

SZ> P.S. I have an idea to make a register, i.e. instead of the line:
SZ> {NAM}{0.3b/Noncommercial}{Unregistered}
SZ> There will be something like:
SZ> {NAM}{0.3b/Noncommercial}{Registered to Sergey Zotov}
SZ> Question. What do similar lines look like for registered soap writers?

I don’t know. Why is this recorder needed at all?

Bye, Sergey.
WBR, Vivid^Brainwave.

SZ> {NAM}{0.3b/Noncommercial}{Registered to Sergey Zotov}
SZ> Question. What do similar lines look like for registered soapers?

At the discretion of the author ;) For DVM, for example, the name is simply entered there.
By the way, is it necessary to attribute Registered to - the question is very complicated.
In theory, this field is intended specifically for this information, but
traditionally, many software do this attributes.

**EMSI_DAT0134{EMSI}{2:5020/2065@FidoNet 500:95/468@ZXNet}{FFFF}
{8N1}{HYD,HTM}
{FE}{DVMmail}{0.839-W32-TCP/IP-mHTM/Beta2}{Eugene Palenock}
{TRAF}{16BB 6425}
{IDENT}{[FLASH Line 1][Russia, Moscow, Golyanovo]
[Eugene Palenock][7-095-468-****][57600]
[XW,V90C,x2C,V34+,VFC,V32T,H16,V22B,U,Tcd]}
{TRX#}{[3C53CCEB]}{MOH#}{[00007AE0]}2653

Regards, Evgeniy.

... http://2065.da.ru

EP> I hope you will support modern deviations from the standard?
EP> Real LFN, both Russian encodings... Passwords, free codes with paths...

Press Russian encodings! How should I know WHAT SPECIFIC
ENCODER
the file name is encoded in? Are you going to do unicode?

SZ> P.S. I have an idea to make a register, i.e. instead of the line:
SZ> {NAM}{0.3b/Noncommercial}{Unregistered}
SZ> There will be something like:
SZ> {NAM}{0.3b/Noncommercial}{Registered to Sergey Zotov}
SZ> Question. What do similar lines look like from registered soapers?

Here are some pieces from the T-Mail log from my site, maybe this will help you something like:

T-Mail/2607.NT/Noncommercial/Unregistered
NAM/0.2b/Noncommercial/Unregistered
T-Mail/2 608.NT/Noncommercial/1235/88FA6652/FFFF
Dickie/0.08a/Eval

Stanislav

KF> Put pressure on Russian encodings!

If you don’t use it yourself, don’t disturb others!

KF> How should I know WHAT SPECIFIC
KF> ENCODING the file name is encoded in?

See which soaper is on the remote side. Or you can optionally indicate that the request should be sent to
866 or recoded to 1251. In general, you can also automatically
look - if you typed there, then 866, for everyone else - 1251.

KF> Will you do unicode?

I haven’t seen support for such freeware. Those. There is, of course, the invention of mini-html (where menus and simple pages for selecting files are transferred to Hydra), but
it has not received distribution (and use).

28 Jan 02 10:13, Stanislav Udin -> Sergey Zotov:

SU> Here are pieces from the T-Mail log from my site, maybe this will help you somehow:
SU> T-Mail/2607.NT/Noncommercial/Unregistered
SU> NAM/0.2b/Noncommercial/Unregistered

RTFM in English ;) It does not and does not always write data from EMSI to the log.
It has a separate log for EMSI.

SZ> P.S. I have an idea to make a register, i.e. instead of the line:
SZ> {NAM}{0.3b/Noncommercial}{Unregistered}
SZ> There will be something like:
SZ> {NAM}{0.3b/Noncommercial}{Registered to Sergey Zotov}
SZ> Question. What do similar lines look like for registered soapers?

Here is a line from a commercial t-soap.

T-Mail/2607.NT/C10/1953/000F734C/FF55

[...skipped...]

Goodbye, Alexey.

EP> See what kind of soaper is on the remote side.

:-) It’s probably hard to explain to a Unixoid that the encoding should be determined by
the installed software. :-)))))))))))))))))))))))))))

In general, don’t make a crooked thing even more crooked,
from ancient times, an alternative
encoding was used under the standardized name cp866,
and then the terrible Mazda came to Russian land
and said that we would have 1251.

And in general it’s hard to imagine that a spektrumist
would need freck file
"And this is Vasya Pupkin's essay after a severe hangover.doc"

Do not clutter the task with unnecessary problems.

ZXNet: 500:8462/1 ~/ <~ http://zs80.chat.ru/
Fido: 2:5057/21.93 /_ _> ftp://zx-museum.org.ru/zs/

ZXNet: 500:8462/1 ~/ <~ http://zs80.chat.ru/
Fido: 2:5057/21.93 /_ _> ftp://zx-museum.org.ru/zs/

EP> See what soaper is on the remote side.

And then what? Here you see I have qico-0.46/linux.
What is my encoding? Yes, it can be anything!
Usually KOI-8R, but there are also CP-1251 and CP-866 for different people.
Guess by frequency analysis? There is not enough text.
For DOS/Windows, nothing is clear either. There is no need to become a stupid
American and naively believe that besides your native one, there are no other languages ​​in the world
, and therefore no coding. Maybe on the remote
side there is Greek, or even Chinese encoding - in your local
the necessary characters MAY SIMPLY NOT APPEAR.

THE ONLY ENCODING EVERYONE HAS IS AMERICAN ASCII 7-bit.
For everything else, it is only possible to use unicode, no way not
standardized.

EP> Either optionally indicate that the request should be sent to 866 or
EP> recoded to 1251. In general, you can also automatically look - if
EP> was washed there - then 866, for everyone else - 1251.

This is how lame software is written. You need to think beyond your own ()(), that is,
imagine
that the world is round, and there are many different time zones, encodings and much more.

KF>> Are you going to do unicode?
EP> I haven’t seen support for such hacks.

So how do you do it if the old software only understands 7-bit
encoding
(among the Americans, for example). Where in the worldin the standards is something written
about Russian letters?
But nowhere, they are not there, at best a reference to ASCII, at worst only
implied...

EP> That is. There is, of course, the invention of mini-html (where menus and simple pages for selecting files are transmitted on Hydra), but it has not received distribution (and
EP> use).

That is, the direct participation of the user is implied?

FILE REQUESTS WITH RUSSIAN NAMES ARE NOT SUPPORTED. ALL. PERIOD.
To do this, you need to use more different file transfer protocols.

29 Jan 02 01:19, Kirill Frolov -> Eugene Palenock:

KF> FILE REQUESTS WITH RUSSIAN NAMES ARE NOT SUPPORTED. ALL. PERIOD.

If you don’t see anything further than your Linux, it doesn’t mean that there’s nothing else
there.

Russian freqs are supported by T-Mail, Argus, KittenMail, DVMMail, and almost all
SRIF managers I know. Thus, 90% of nodes technically allow
fracking files with Russian names.

Therefore, this must be taken into account and supported in the subject.

We also need to take into account the possibility of LFN requests (all win32 soapers support LFN
fraking).

SZ> no.

Will it be? This tells the remote side how many
bytes we are going to transfer to it.

It’s not difficult to calculate... Immediately before
the {IDENT} field is written '{TRAF}{0 0}'
In its argument there are 2 hexadecimal numbers separated by
a space. 1st number - number of bytes of unpacked traffic
(i.e. just pkt files), 2nd number - number of bytes of total
other traffic (but excluding simple pkt).

Here for example:
**EMSI_DAT014A{EMSI}{2:5020/2065@FidoNet}{1234}{8N1}
{HYD,HTM}{FE}{DVMmail}{0.839-W32-TCP/IP-mHTM/Beta2}
{Eugene Palenock}{TRAF}{63D - [NAM][0.30/ZX-Spectrum][Unregistered]

SZ>> Naturally
SZ>> only if you have a watch. For this, the driver
SZ>> CmosDrv.C from Lara Croft 4.50 is used.

AM> Thanks for that. Otherwise, I already called Megus a couple of times when
AM> accidentally copied the wrong Namov setup to the ramdisk (in one setup -
AM> only fido (CM node), in the other - ZXNet (22:00 - 06:00) and fido).

I have 2 nodes - one night, the other - CM. Which night one is the first and when I
NAM launch, I press break and the first node is skipped.

[Killed.]

ZXNet: 500:8462/1 ~/ <~ http://zs80.chat.ru/
Fido: 2:5057/21.93 /_ _> ftp://zx-museum.org.ru/zs/

EP> Thus, 90% of nodes technically
EP> allow fracking files with Russian names.
EP> Therefore, this must be taken into account and supported in the subject.

God forbid. You’d better conduct a survey among real-life people, whether they need long names or not, otherwise it will turn out like a joke
about Indians.

EP> (all win32 soapers support LFN freqs).

Well, if they do support it under win32, then of course
for Speckies it needs to be implemented at least with a stake in the tooth!
:-)

KF>> PERIOD.
EP> If you don’t see anything further than your Linux, it doesn’t mean that
EP> there is nothing else.

Well, I also support everything... in koi-8... is it necessary?

EP> Russian freqs are supported by T-Mail, Argus, KittenMail, DVMMail, and
EP> almost everyone I know SRIF managers. Thus, 90% of
EP> nodes technically allow you to frack files with Russian names.

Answer a simple question: let’s say I have the Ukrainian locale installed and
there is a file name with the letter “i with two dots” (it cannot be drawn in a letter just
due to encodings). Your locale is Russian, without this letter. What happens
when
you frack such a file? The national question arises very acutely...
Or am I a typical German from Germany and my locale is German, there are no Russian letters at all - what will I get from your files? Bnopnu. On the contrary, the same thing.

EP> Therefore, it is necessary to take this into account and support it in the subject.

Therefore, you cannot be prohibited from writing curved software, but I would
ask you not to raise national
issues in the international echo!

And the question in general is no longer national, but purely technical. And it’s not
a fact
that even Windows will have Russian encoding, or specifically cp-1251. And in the axle
too...
THERE ARE NO STANDARDS. The fact that something is supported somewhere is a GLITCH. What are the files?were
successfully
transferred from point A to point B - an accident. To exclude abnormal
situations, normal
software must reject such file names, because otherwise it is unknown what
glitches this
could lead to. Do you know about MS-DOS (aka CP/M) and the Russian "r"? Or if I now
fuck
characters with a code less than 32 (it allows me...) into a name and send it, then I am sure
that on most
of the systems a wide variety of problems will arise, up to and including crashing of the
mailer. Or if
I insert “/” or “\” into the name, then you can also achieve interesting results on
crooked software.

EP> You also need to take into account the possibility of LFN requests (all win32
EP> soapers support LFN freks).

They are supported by everyone, except for all kinds of DOS... again, Windows can
allow
incorrect characters in the name, but another system does not, or vice versa.

KF>> ENCODING is the file name encoded?
SZ> Standard FILES request.

Who said that it is standard? And nothing is written there about encodings...

KF>> Are you going to do unicode?
SZ> 256 encodings %) Do I look like an idiot?

And it’s useless until other software learns to support it.

KF>> PERIOD.

EP> If you don’t see anything further than your Linux, this does not mean that
EP> there is nothing else.

I answer as the author of the subject. YOU CAN WRITE ANY FILE NAMES YOU WANT - EVERYTHING WILL BE TRANSMITTED 1 TO 1 WITHOUT ANY CHANGING! My ZX Word supports 3
encodings. Freq in the subject will not allow you to write in Russian. And I have never seen Russian names on frecks before. Moreover, I have never seen long
names on freqs!

EP> Russian freqs are supported by T-Mail, Argus, KittenMail, DVMMail, and
EP> almost
EP> all the SRIF managers I know. Thus, 90% of nodes technically
EP> allow you to frack files with Russian names.

EP> Therefore, this must be taken into account and supported in the subject.

Whichever one you write in, it will be sent to that one. If you compose a .req outside the subject.

EP> You also need to take into account the possibility of LFN queries (all win32 soapers
EP> support LFN freeframes).

EP> Will it be?

At 0.30 no. In 0.3x, in general, probably yes.

EP> This tells the remote side how many
EP> approximately bytes we are going to transfer to it.

I know. :)

EP> It’s not difficult to count it...

It’s like saying. If you support attach, you will have to do a full
analysis of all pkt... It seems to me that the realist will fall asleep while he waits...

EP> Immediately before
EP> the {IDENT} field is written '{TRAF}{0 0}'

[Killed.]

I am aware of this. :). I like it. So be it! :) Only for t-mail via "." - 2607.NT...
But these are minor things.

ZXNet: 500:8462/1 ~/ <~ http://zs80.chat.ru/
Fido: 2:5057/21.93 /_ _> ftp://zx-museum.org.ru/zs/

SZ> software, if possible, I'm trying to register it. And by any means - both
SZ> legal and not. ;)

This won’t make it any less glitchy. ;)

Bye, Sergey.
WBR, Vivid^Brainwave.

ZXNet: 500:8462/1 ~/ <~ http://zs80.chat.ru/
Fido: 2:5057/21.93 /_ _> ftp://zx-museum.org.ru/zs/

SZ> the file is transferred 1 to 1 => in what encoding everything is there and you need to
SZ> send requests. Am I wrong?

In most cases I am right. About where to send the request. Although in my
x.zip
there is a list /recoded/ into 866 encoding...

The whole question is in what encoding to write to the disk (not the file, but its name).
You don’t know what encoding it is in. And on the spec, the de facto standard is CP866.

SZ> That's how to say it. If you support attach, you will have to do
SZ> a full analysis of all pkt... It seems to me that the realist will fall asleep while waiting for
SZ>...

Why?
If there are attachments, then you will still have to analyze the pkt.
Here only reading from track 0 of the file size will be added (and, anyway
you will have to read).

By the way, how will you attach transmit - before the accompanying pkt
or after? Need to go to pkt. Because if after, then if the connection is broken, pkt
may leave alone. Or leave 2 times.

30 Jan 02 09:29, Sergey Zotov -> Eugene Palenock:

SZ> I have never seen Russian names on frecks.

I can put it down ;)

SZ> Moreover, I have never seen long names on frecks!

But I’ve had this for 2 years now. Only long names, and with
spaces and dots (for frecks you need to use appropriate
modern mailers like DVMMail, and not stupid T-Mail)

AS>> T-Mail/2607.NT/C10/1953/000F734C/FF55

SZ> And what does this mean? 8) What are these hexes talking about?
C10 - for 10 lines
1953 - serial number (decimal)
000F734C - CRC32
FF55 - post serial number (hexadecimal)

Goodbye, Alexey.

AS> C10 - for 10 lines
AS> 1953 - serial number (decimal)
AS> 000F734C - CRC32
AS> FF55 - post serial number (hexadecimal)

Zabej on this crap.

ZXNet: 500:8462/1 ~/ <~ http://zs80.chat.ru/
Fido: 2:5057/21.93 /_ _> ftp://zx-museum.org.ru/zs/

EP> modern soapers like DVMMail,

Let's collect all the Windows bastards and will
try to make it fit.

EP> How will the LFN file be accepted?

- Castrate the name by length (you can first kill
spaces and others non-kosher
characters in the line)
- If the name contains the characters N>128, then either do not accept the file
or write it as it is, then let Evgeny himself understand
what it was and in what encoding.

EP> Keep in mind that there are 2 standards for transmitting LFN names, argus and tmyl.

You are trying so hard to find a solution to an imaginary problem
that you can only envy yours perseverance.