MELON&freq
ZXNet echo conference «real.speccy»
Urgently need a Melon who can frack files! And a detailed description of this process
(how a letter is formatted in the chest, what needs to be written in area, from, to, subj, what
flags to set, how to then use this letter in a melon)?
Well, that’s all, All, for now.
Alexander Grokholsky was with you
[I ZX] Spawn/Last Masters Group/X-Project Association
...
12 Jan 00 01:47, Alexander Groholsky wrote to All:
AG> We urgently need a Melon who knows how to frack files! And a detailed description of this
AG> process (how is a letter formatted in the chest, what should be written in the
AG> area, from, to, subj, what flags to set, how to use this
AG> letter in the melon later)?
It’s time to add the question to the offtopic list. You need melon 1.90.
Or Dickie. Or STS...
Kirill Frolov. [ZX]
KF> It’s time to add the question to the offtopic list. You need melon 1.90.
^^^^^^^^^^
KF> Or Dickie. Or STS...
^^^^^^
And where can I get them?
Well, that’s all, Kirill, for now.
KF>> melon
KF>> 1.90.
AG> And where can I get them?
I have melon 1.90. In addition to the new function in it, it also
“thinks” much faster, which I really liked.
Don’t worry about it, Alexander!
Dale
Regarding the Very Wild Mailer, you can kick me - maybe I’ll bring him to a form acceptable for posting... although, most likely, you don’t need him - he’s under
isdos. someone would write a help...
[ WBR, Oleg. ]
[ 15:20 17 January XXXV A.S. ]
16 Jan 00 16:28, Alexander Groholsky wrote to Kirill Frolov:
KF>> It’s time to add the question to the off-topic list. You need melon 1.90.
AG> ^^^^^^^^^^
17 Jan 00 15:20, Oleg Grigoriev wrote to Alexander Groholsky:
OG> needed - he is under arrest. If only someone would write a help...
Correct the help from Ksenia.
Kirill Frolov. [ZX]
KF>>> melon 1.90. And where can I get them?
AP> I have Melon 1.90. In addition to the new function in it, it
AP> also “thinks” much faster, which I really liked.
Just wondering how this should work?
I created the following letter in Lara:
________________________________________________________________
From: Musa Khaybullin 2:5085/1.65
To : ONIX Station 2:5085/1
Subj: HDD.ZIP
________________________________________________________________
KF> Help from Ksenia podppav.
I and so increasingly know.
[ WBR, Oleg. ]
[ 20:37 19 January XXXV A.S. ]
19 Jan 00 00:16, Musa Khaybullin wrote to Alexander Pashenko:
MK> Just wondering how this should work?
MK> I created the following letter in Lara:
Lara is NOT NECESSARY for frecks. There’s no way to understand this?
You need any text editor to make a file ????????.REQ
and write file names in it, one on each line. This is called
like the WaZ00 request type and is supported by many mailers.
Kirill Frolov. [ZX]
Finally, I learned how to design letter:
┌────────────────────────────
│ From: Your name Your address │
│ To : Anything Boss address │
│ Subj: List of files or files │
└─────────────────────────────
In addition, it is _required_ to set the
Files request flag in this letter (in Lara it is in the list of flags), after which you
can upload this letter to a pkt disk. The file extension needs to
be renamed to .REQ, and you can send this message to the boss.
KF> Lapa is NOT NEEDED for frecks. There is no way to understand this?
Look above - the Files request flag must be set.
KF> You need any text editor to create a file
KF> ????????.REQ
The name is also not any. For Melon to want to send a file,
the name must begin with the letter L .
Don't be rude, Musa!
Dale
21 Jan 00 21:36, Alexander Pashenko wrote to Musa Khaybullin:
AP> Finally, I learned how to format a letter:
AP> ┌────────────────────────────────
AP> │ From: Your name Your address │
AP> │ To : Anything Boss address │
AP> │ Subj: List of files or files │
AP> └──────────────────────────────── ─────────────────────────────┘ AP> In addition, it is _required_ to set the
AP> Files request flag in this letter (in Lara it is in the list of flags), after which you
AP> can upload this letter to a pkt disk. The file extension needs to
AP> be renamed to .REQ, and you can send this message to the boss.
HAVE YOU TRIED THIS? Doesn't work?
It's time to give a thumbs up for this, disinformation in its purest form...
KF> Yes, Melon won’t send you anything at all until you in
KF> take STS
KF> hands and correct it.
If the name can be anything, then why bother with Melon?
Make the file name “L”, extension “REQ”, and Melon 1.90 willingly
sends him. ^^^^^^^^^^
But the option with the editor that you said didn’t work for me either. The file "L???????.REQ" is sent, but no response comes.
^^^ ^^^^^^^^^^^^^^^^
So for now we still have to dig for options.
Sincerely, Sasha.
KF>> file requests, but you don’t need to know about that...
AP> Tell me in more detail, please.
I’m not entirely sure myself.
The following flags determine the types of file requests (file request and file
updaterequest)
supported by the system:
XA Bark and WaZOO file/update requests
XB Bark file/update requests, WaZOO file requests
XC Bark file requests, WaZOO file file/update
XP Bark file/update requests
XR Bark and WaZOO file requests
XW WaZOO file requests
XX WaZOO file/update requests
Below are the meanings of these flags for some mailers.
+---------------------------------------+
| XA Frontdoor <1.99b |
| Frontdoor 2.01+ |
| Dutchie 2.90c |
| Binkleyterm >2.1 |
| D'Bridge <1.3 |
| Bink/+ |
| TIMS |
+---------------------------------------+
| XB Binkleyterm 2.0 |
| Dutchie 2.90b |
+---------------------------------------+
| XC Opus 1.1 |
+---------------------------------------+
| XP Seadog |
+---------------------------------------+
| XR Opus 1.03 |
| RavelMail |
+---------------------------------------+
| XW Fido >12M |
| The Brake! |
| SFMail |
| FHMail |
| Tabby |
| G.P.Mail |
+---------------------------------------+
| XX D'Bridge 1.30 |
| Frontdoor 1.99b |
| InterMail 2.01 |
| T-Mail |
+---------------------------------------+
| None QMM |
+---------------------------------------+
In practice, I only met with XW.
This is as I wrote - the file ????????.REQ, and inside each line there is
one file name.
KF> Are you sure that requests are generally supported there?
Yes, I talked to my boss at Zx-Net. Later at work he looked at what was happening when I tried to frack. T-mail
accepted requests, but cursed that he didn’t know _who_ these
requests were coming from, like, “What kind of bastard is trying to frack files?”.
KF> Practice on a familiar T-Mail writer, for example,
KF> maybe
KF> there’s something wrong inside the file, maybe something else what...
If my boss doesn’t forget, he’ll put a letter on hold for me - a request for a Freck from mine to his address. I have already agreed with him.
Sincerely, Sasha.
The same rake happened with one boss, he had t-mail/nt.
The meaning is this: the file name 'req' should be _the_same_ as the name of the "floshnik"
('*.flo'). These "flos" are generated for the Real Dickie-Mailer under iS-DOS.
This file (.flo) is a list of files and paths to them (pkt,
for example) that need to be sent to the boss.
Example:
=======
Boss - 2:5030/885
"Floshka" - '13A60375.flo'
13A6 is 5030 in hex form
0375 is 885 in hex form
Accordingly, the file for fracking should be '13A60375.REQ'.
Try this.
If I sent the boss a file like
'FILE.REQ' by Melon (wildly hacked by one person :), then the file was sent, but in response - no answer, no hello.
Sincerely, Felix.
[I ZX]
AP> 1.80 can only send *.PKT, and 1.90 can also send *.REQ.
You can’t do that, but I sent everything.
AP> Yes, I talked to my boss Zx-Net. Then at work
AP> he looked at what was happening when I tried to fracking. T-mail
AP> accepted requests, but cursed that he didn’t know _from whom_ these
AP> requests were coming, saying, “What kind of bastard is trying to freck files?”.
And then someone already wrote - the file name should consist of
network number and node number.
AP> If my boss doesn’t forget, he will put a letter on hold for me -
AP> request for fragging with mine to his address. I already agreed with him.
You don’t need a letter.
WRITE:
XXXXYYYY.REQ file name, inside each line the file name.
XXXX = network number in HEX form
YYYY = node number in HEX form
For example, for a request from node 2:5030/827.0 file name will be 13a6033b.req.
FK> The same rake happened with one boss, he had t-mail/nt.
Mine has exactly the same ;)
FK> The meaning is this: the file name 'req' should be _the same_ as
FK> the name of the "floshnik" ('*.flo'). These "flash drives" are generated for
FK> Real Dickie-Mailer under iS-DOS. This file (.flo)
FK> is a list of files and their paths (pkt,
FK> for example) that need to be sent to the boss.
FK> Example:
FK> =======
FK> Boss - 2:5030/885
FK> "Floshka" - '13A60375.flo'
FK> 13A6 is 5030 in hex form
FK> 0375 is 885 in hex-video
FK> Accordingly, the file for fracking should be
FK> '13A60375.REQ'.
FK> Try this.
Thank you very much, it finally worked, the files flew in!
True, I only tried the WAZOO request ;)
In the future it would be nice to make a modification in Melon, if it encounters a file
*.REQ, then let it calculate it for itself name from the number of the station where he is currently calling and with that name and sends ;)
Long life and prosperity to you, Felix!
With best wishes, Musa Khaybullin.
Hurray! I finally managed to frack the file. Here's how it worked out for me:
- Take a regular text editor and type in the names of the files that
you want to frack (one file name per line)
- Then the resulting file is renamed as follows:
Take the address of the station from which you want to frack the file and translate it into HEX
For example:
2:461/16, 461->01CD
16->0010
And the extension is renamed to REQ
The name turns out to be 01CD0010.REQ
- Then MELON1.90 is taken and forward
Well, that's all, All, for now.
[skip]
MK> In the future it would be nice to make an improvement in Melon, if
MK> he encounters a *.REQ file, then let him calculate the name
MK> from the number of the station where he is currently calling and with that
MK> name and send ;)
In the future you should switch to Dickie-Mailer under iS-DOS (provided that
your modem though 2400/v42bis or higher) and
get imbued with all the rules of this event. ;)
[skip]
FK>> In the future you should switch to Dickie-Mailer under iS-DOS
MK> I already tried ;( But I couldn’t set it up at all ;)
Where did the problems arise? The modem connection diagram (Misha Kondratiev?) and
BASIC_48 firmware support working with modem interrupts (/NMI)?
FK>> (provided that your modem is at least 2400/v42bis or higher)
MK> Mine costs 14400/v42bis ;)
Especially!
FK>> and get into everything rulez of this event. ;)
MK> I would be glad ;)
Does your computer have a hardware clock (RTC)? According to what scheme?
FK> Where did the problems arise?
There was a rake - I set the boss's address in the configs - 2:5085/1, but he still
called somewhere at 2:5030/**.
FK> Does the modem connection diagram (Misha> Kondratiev?) and BASIC_48
FK> firmware support working with modem interrupts (/NMI)?
Yes it does.
MK> Not there yet ;( But I hope to install it soon according to Gluck’s scheme ;)
MK> It seems like I bought all the parts today ;)
You need a modernized Gluck one so that 7 bits from EFF7 are not checked.
Well, there’s more compatibility ;-)
Well, I’ve confused everyone here myself I got confused then - the circuit where M1
is wound up works exactly the same as where M1 is not wound up. And I messed up everything with the logic of the Z80 bus, but for some reason they believed me (and didn’t check) and started M1...
MK> 2:5085/1, and he still called somewhere at 2:5030/**.
Here's an example piece of cfg-shnick for your case:
================== begin of file "Dickie.cfg" 2:5085/1.65 2:5085/1
EMSI_ADDRESSES 1 ;for this case
PREFIXSUFFIX ATDP/| ;namep fill with "pulse"
DOMAIN FidoNet.org FidoNet nolist 1 2 3 4 5 6; for FIDO
PASSWORD password 2:5085/1 ;your papol (password) on EMSI
DIAL +7-812- /
DIAL +7- 8W/
DIAL + 8W10/
PHONE 2:5085,YZ.YZ XX u 2:5085/1 +flags
================ end of file "Dickie.cfg" =================
[skip]
MK>> Not there yet ;( But I hope to install it soon according to the Gluck scheme ;)
MK>> It seems like I bought all the parts today ;)
KF> You need a modernized Gluck one so that 7 bits from EFF7 are not
KF> checked. Well, there is more compatibility ;-)
How is that?
KF> Well, I confused everyone here and I got confused myself then - the circuit where
KF> M1 is turned on works exactly the same as where M1 is not turned on. And I messed up everything with
KF> the logic of the Z80 bus, but for some reason they believed me (and didn’t
KF> check) and started M1...
Long life and prosperity to you, Kirill!
Sincerely, Musa Khaybullin
08 Feb 00 22:00, Felix Knajzev wrote to Musa Khaybullin:
FK> ALIAS 2:5085/1.65 2:5085/1
^^^^^ You can throw this out...
FK> DIAL +7-812- /
^^^^^
FK> DIAL +7- 8W/
FK> DIAL + 8W10/
Yeah... ;-)
08 Feb 00 19:00, Musa Khaybullin wrote to Kirill Frolov:
KF>> ppedusmotpen), and from his own list. Or you fuck on
KF>> binkleystylovskiu outbound need to?
MK> Throw pliz, and the not increasingly clear.
─ Ppo FTN-technologies. (2:5030/827.2) ─────────────────────────────── SU.FIDOTECH
─
Msg : 77 of 116
From : FAQ Master 2:5020/1159 06 Feb 00
To : All 06 Feb 00
Subj : Su.FidoTech.FAQ [3/3]
────────────── ──────────────────────── ─────────────────────── ────────────────
>[26] Q: How are outbound y BinkleyStyle-mailops opganized?
Comments (TT): in general, this voppos is closer to the theme of SU.MAILER, but
the answers to it pped intepes as a ppimeetpenalised
any conppppostpane FTN.
A: a) (DM)
We have some basic dipectopia. If our adpes is z:n/n.p@domain, then put inside all the files related to yzlams with namespaces of the type z:*/*@domain. The names of
such files consist of two fields on four hexadecimal digits,
unambiguously specifying the network and yzla name (zone and domain, obviously ours.
Pointable namep). Their attachments depending on the
file type can be as follows:
.?lo -- the file containing each of the stpoks in the cotop or the name of the file pped assigned
to the packagingto a remote machine, or empty. If the path to the file is not
complete, but relative (that is, without specifying the drive letter or at least
just "/" or "\" at the beginning), then it is supplemented with the name of the base
directory. The file name can be preceded by one of the symbols - `^', `#'
or `~'. `^' -- delete this file after successful sending, `#' --
cut to zero length, `~' -- ignore the text behind this symbol.
Mailers mark already sent files with it. If all the lines in .?lo-shka
are empty or start with `~' - it can be destroyed with a clear
conscience.
.?ut - type-1 (2, 2+) mail package that needs to be sent to
the appropriate address. During sending, it is assigned a random name
and the extension ".pkt". Here and above, the question is replaced by one of the letters i,
c, f(o), d, h, which corresponds to the mail flavor - immediate, crash,
normal, direct and hold. The "normal" flavour, respectively,
is symbolized by the extension ".flo", and for packages - ".out".
.req - of course, a list of files for the frac. On each line:
"filename_!password", where password is obviously the password, and `_' is a space.
;) It is transmitted during the mail sessionto a remote machine, it is immediately
processed and returned back in a golden shower of files. :-/
xxxxyyyy.bsy is a busy flag. Must be created before
any operation with files xxxxyyyy.*
.pnt is the directory in which mail for points of this
node is stored. The files in it must have as a name a hexadecimal
point number, padded to eight characters with zeros, and one of
extensions - ?lo, ?ut, req and bsy.
If you need to send mail to another zone, then a directory is created with the name
same as the base outbound and an extension of the form .xxx, where .xxx --
hexadecimal number of the destination zone.
To send mail to a network with another domain in the same directory where our base outbound and the outbounds of neighboring zones are located, a directory of the form
"domain.xxx" is created, where xxx, as usual, is the zone number in the network with the domain "domain".
For example, if your main outbound is in the directory c:\BBS\outbound, then the
frek on node 4:3/2.1@Testnet will be in a file with the name
c:\BBS\Testnet.004\00030002.pnt\00000001.req
A: b) (DtZ)
Classical single-zone scheme: we denote outbound as %OUT%. This Example: to point there are two echomail bundles, an attached file and Acceptable Flavors: NETMAIL FILE REQUESTS MANY ZONES MANY DOMAINS .BSY FILES OTHER FILES Depends on the software OS. Bink creates .$$$ (or whatever?) with information from A: c) (PG) There are several contradictions in the answer to this question due to the fact that /------/
directory has no extension.
* Definition. CTL-file is a list of files (usually archmail and
* attachments) that need to be sentto the recipient. (see separately about netmail)
For a node, the name is CTL-file (%04H%04H.%clo) net,node,flavour (those for Crash
5020/730 139C02DA.CLO).
For a point, (%04H%04H.PNT\%08H.%clo) net,node,point,flavour (for Hold
5020/730.43 139C02DA.PNT\0000002B.HLO).
CTLFile contents:
attach (about netmail in general, see below, but message attachments
CORRECTLY should be placed in the CTL file).
#E:\HOST\OUT\89098354.MO0
#E:\HOST\OUT\89098354.MO1
C:\CONFIG.SYS
^E:\HOST\OUT\13FE0065.PKT
H)old C)rash I)mmediate D)irect F) normal (notice: .flo, not .nlo)
The name of the netmail .PKT file is formed according to the same principles, but has
the extension .%cUT Flavor (only in normal now there will be a letter O - those
normal netmail has the extension .OUT).
Netmail lying in the outbound in this way is NOT ATTACHED - those in the CTLfile
it is NOT necessary to write it. During the session, the netmail is renamed to .PKT by the mailer.
They are formed according to the same principle and have the extension .REQ. In principle, they are not
attached (although in BrakyTerme, for example, this is not the case, I know that this is
wrong). The flavor in Bink #23 wasalways defined as Normal. Further, in
later BT+ - it is believed that .REQ is not a reason to call and when
request you need to create an empty CTL file with the desired flavor.
Format of .Req file:
etc.
Importantly: they come with passwords, are written for each file separated by one space
and !, as a rule, Case Sensitive.
Significantly: there are also Update Requests. Please refer to the recommended
literature. Hint: Update Requests also come with passwords :-)
Feature: in principle, according to Bark (if I'm not mistaken) file requests, when sent, must have the name
a lot of software does not do this. In The Brake! generally configurable.
In addition to Default OutBound, the zone of which (almost?) always coincides with Main Aka
Mailer, tosser and netmailpacker, there are Outbound for other zones, the name
of which is a directory with an extension, for example %OUT%.38D (outbound for zone
909)
OutBounds have different names.
Created by tosser/mailer/packer/any other interested software
currently working with the address according to the principle described for CTL with
extension .BSY. If there is a .BSY flag - communicate with CTLor netmail
is prohibited _totally_. For example, if the mailer, after going through EMSI, finds out
that one of the AKAs is busy, it’s worth tearing up the session (and not just exclude AKA, although
you can argue on this topic).
It’s good form to put the seconds of the .BSY file in the number of the line that created it.
Cultural creation algorithm .BSY: create a file with the extension .%X03X
line number and try to rename it to .BSY. If after this the file .%X03X
line number continues to exist, erase it and assume that the address
is busy.
Call/Session, The Brake! creates .TRY with information about the last connection,
BrakyTerm (will) create .%cRQ Flavor - requests for request recovery
etc.
the register of letters in filenames are not always ignored, and *.CUT and
*.cut files are different files in general. As far as I know, for maximum
compatibility in such a situation, it is always better to use lowercase characters when creating
files, and when reading, look for all possible options
(for example, regexp ".*\.[Cc][Ll][Oo]"). Although not all software adheres to these rules, which creates certain problems.
=== Cut===
February 08, 2000 (and it was 10:00 pm then)
Felix Knajzev in his letter to Musa Khaybullin wrote:
FK> Here is an example of a piece of cfg file for your case:
FK> ================= begin of file "Dickie.cfg" =================
FK> ================= end of file "Dickie.cfg" =================
Thanks for the information!
Long life and prosperity to you, Felix!
Sincerely, Musa Khaybullin