again about cmos

Andrey Isaev lied here for Denis Dmitriev, and I
will teach you how to lie!

AI> Ha! the first one was started not by him, but by the company that produced Profi, and
AI> I have such a copy, I had a watch even before
AI> Gluck started making his own, and it was he who did everything
AI> in his own way, not me.
DD> So, couldn’t you say earlier? While the scheme for ports
DD> was being redone.
AI> But there was no need to say this, because the clock there is made stupidly
AI> and conflicts with the rat.

I ask gentlemen of the jury to pay attention to this phrase ^^^^:)

DD> No, I can’t do that - and how can I now support the clock -
DD> in the
DD> config click the subject interface?
AI> Even I don’t know:(

Such watches as Isaev’s are only owned by him. And it’s unlikely
who else will make them.

DD> Personally, I am for the standards that have already been established and embodied in
DD> circuits/boards, that is, for Pros. But there is no circuit diagram, and it is unlikely
DD> this
DD> option will not be with conflict with Pentagon ports.

And not only with Pnevsky ones. Look below the addresses :))))

DD> What are we going to decide, how to work with the subject more normally?
AI> The only request is to store the time in the clock not in
AI> binary-decimal form as Gluck suggested, but just in
AI> binary, and then make them work on Profi
AI>It will be a matter of minutes, you will need to change the addresses of
AI> ports, and you can use my
AI> time setter.

About the installer - I made it for my watch two weeks ago, and Isaev knew very well about it. In addition, this installer gave me a couple of interesting ideas...
And you need to store the data in the way that is most convenient. For constant
time output, it is MUCH easier to work with binary-decimal
data than with binary... Faster - accordingly, however
if you use tables, then it won’t slow down... :)))

And finally, who is the only one who wrote software for the clock???

Who the hell is interested in support? extinct pro??? If only
to do it so that Isaev could then painlessly redo it?

DD> PS: since everything is wrong with Profi, maybe you can give a description of how to
DD> pester the clock?
AI> Same as to those but on other ports:
AI>
AI> ld bc,#7ffd
AI> ld a,#10
AI> out (c),a
AI> ld b,#df
AI> ld a,#20
AI> out (c),a
AI>
AI> After that port #00ff the address register, and the port #00df
AI> data register.

And this is not a perversion????
I forgot to say that you still need to recode the numbers :))))

Be healthy!
Renat Mamedov

So I propose the scheme from ZXNEWS for two reasons:

1. There are fewer glitches in tr-dos and therefore there are fewer glitches.
2. I have...

There is also the most difficult question - in what format (binary-decimal or binary) is the time stored in the clock? IMHO
it’s better in BCD - you can quickly convert to BIN and also
quickly into ASCII, unlike BIN.

Wi7h be57 Wi5he5, FK0.

-+- SMM version 1.08

RM> You said it yourself: in Profi, clock ports conflict with
RM> ports
RM> M-mice! Or do you have no mouse - no problem? :)
AI> I have a mouse and, accordingly, there was also a problem (there was one),
AI> but I have nothing against Gluck ports, but how it
AI> stores time in a watch does not suit me specifically.
DD> Is it possible in another way, on the same microphone?
DD> Ana, please explain, I'm confused: - L
in register #0b, the 2nd bit is responsible for the format in which the time is stored 0- binary decimal 1- binary. Renat has 0 there and in Profi 1 and if I dealt with
port addresses without damage to CP/M, then this is so bad, you need either
one or the other, but all together and the hell will come out at once.

Sincerely, Andrey.

... The hedgehog is a proud bird: you won’t kick it will fly!

The microcircuit is smart - as you order it, so it will be.
And the fact that Isaev doesn’t like it - he will have to mutilate the software for his own
[expleted language] ports will have to be more difficult :).
And if you really need it, this mode is determined programmatically,
so the driver can be universal, then you need it
there will be one 5026/18.42 :))))
And if you want to fuck with data translation, make a binary
system...

I recommend it to everyone read the doc. Only it is on the server
it’s buggy and has errors :))) I’ve already prepared a new one...
I’ll upload it.

Be healthy!
Renat Mamedov

RM> Only he himself has a watch like Isaev’s. And
RM> it’s unlikely that anyone will make them again.
Ah, well then it’s clear. for some reason I decided that this was the Professional standard...

RM> And finally, who is the only one who has written software for the clock???
Well... let's say ;)

[ skip reference to the clock ]

RM> And this is not a perversion????
RM> I forgot to say that we still need to recode the numbers :))))
Yeah.... oh my, I’ll make a separate clock driver, so as not to suffer, and let at least wall chimes be connected to it :)

With the best, Denis.

AI> The only request is to store the time in the clock not in
AI> binary-decimal form as Gluck suggested, but simply in
AI> binary, and then making them work on the Pro
AI> will be a matter of minutes, you will need to change the addresses of the
AI> ports, and the time setter By the way, you can use my
AI>.

Hello, Renat!

27 May 98 Renat Mamedov hoping that DEnis Dmitriev will read,
wrote:

RM> I recommend everyone to read the document. Only it's on the server
RM> it's buggy and has errors :))) I've already prepared a new one...
RM> I'll upload it.

Now you just have nowhere to go! ;)
Glitched - fix it! :)

All the best.
With respect, Roman Milukov.

Yes. Shouldn’t I need to be given something so that the server doesn’t have something buggy and with
errors, huh?

Hasta la vista.
Tim Kelly

KF>
KF> So I propose the scheme from ZXNEWS for two reasons:
KF>
KF> 1. There are fewer glitches in tr-dos and therefore there are fewer glitches.

You are still suggesting it, but it has been working properly for me
for six months now, if not more. Glyukov (except for me :) did not observe.
And if it’s from typdos, it needs to be mutilated again...
in a (c)/ret... and so - soldered it and use it, even from the bass :)))

KF> 2. I have it...

Counterargument: I also have it (for now)

KF> There is also the most difficult question - in what format (
KF> binary-
KF> decimal or binary) is the time stored in hours?
KF> IMHO
KF> is better in BCD - you can convert it to BIN quickly and into ASCII
KF> too
KF> quickly, unlike BIN.

With both hands!!! I know right away who will object :))))

psi. And in general, this conversation began with the fact that DD does not know
how to write hours in the menon...
I suggest: a replacement driver:

start - reading from the register
start+3 - writing to the register

When the clock #11 is not the number #AA in the cell, consider the clock
missing.

In general, mono collect all the options and make a self-configuring driver...

Be healthy!
Renat Mamedov

TK>
TK> Yes. Shouldn't I be given something buggy and with errors on the server?
TK>?

Well, I didn't put it there :)))
The corrected assembly is ready.
Most likely I'll send you the kit:
1) Text description - Rulez.
2) On-screen diagram
3) Driver for isdos
4) Sources for the time installer
I’ll fill it, most likely in the echo, or with soap - as it turns out.

Be healthy!
Renat Mamedov

This is just funny! St. Petersburg alone has several standards!
And Nemo does it to spite Zonov, right? ;) Hardmakers are stingy, and the users' forelocks are flying!
: E~~
Smuk, it seems, is an established standard.
Well, let them sort it out among themselves...
I have Pent, and their fight doesn’t bother me.

Pros understand, it’s a dead office, as far as I’m concerned I know. Watches in Profi
are rare and unfortunate. You can easily and painlessly convert it into
Glitch. IMHO! - maybe someone uses the local CPU/M. :)

“Glitch” is for the Pentagon (or will you order Smuk to buy?! =).
It was discussed here, too lazy to repeat.

What is ZXNEWS?! And *MAS*?! Are these computers like that? I haven't
heard about them!

[...]
AI> use.
DD> Good idea.
DD> How is time stored in SMUC-e?
this is not for me.
DD> And in general, if you can find out from the chip in what format
DD> its time is stored, then you can have a universal option
DD> write
DD> :)
Of course you can, read register #0b and look at the second bit and if it is equal to 0 then
the time is in binary decimal format, and if it’s something else then in
binary.

Hello, Kirill!
25 May 98 Kirill Frolov was pinching in the hope that Denis Dmitriev would read about cmos again, I read it and decided to answer:

DD> Ah, well then it’s clear. for some reason I decided that this was
DD> the Profinian standard...
this is really the Profinian standard! and about those watches that I have, I finally don’t
stammer, although they are Pro-Finnish, but you can’t get to the bottom of them like in
Profi.

Hello, Denis!

Here 28 May 98 Denis Dmitriev, hoping that Renat Mamedov would read, wrote:

DD> Yesss.... oh my, I’ll make a separate clock driver, so as not to
DD> suffer, and let at least wall chimes be connected to it
DD> :)
Wise solution. Just don't do it as a separate file! Otherwise it will be like ZED for half a day
to load.

Hello, Roman!
29 May 98 Roman Milukov was chewing his fingers in the hope that Kirill Frolov would read about cmos again, I read it and decided to answer:

RM> Pros understand, a dead office, as far as I know. Watches in
RM> Pros
RM> are rare and unfortunate.
You are right that they are unsuccessful, but I’m not sure about the rare ones, all boards starting from 4.0 were equipped with a clock.

RM> You can easily and painlessly convert
RM> into
RM> “Glitch”. IMHO! - maybe someone uses the local CPU/M. :)
It’s easy and painless to do this anyway, there’s a decoder built on RT’s, and
and IMHO everyone uses the CPU/M here because It’s much more convenient to type texts there than
here, and the programmer there is normal, at least I haven’t met anything more normal, well, in short, I won’t describe all its advantages, but believe me that
many people use it.

RM> And what is ZXNEWS?! And *MAS*?! Are these computers like that? But I haven’t
RM> heard about them!
ZxNews was such a newspaper in St. Petersburg;) you yourself told me about this number.

AI>> keeping time in a watch doesn’t suit me in particular.
DD> Is it possible in another way, on the same device?
DD> Explain to me, I’m confused :-L

AI> in register #0b The 2nd bit is responsible for the format in which the
AI> time is stored 0 - binary decimal 1 - binary. Renat has 0 there and in Profi 1 and if
with
AI> port addresses I managed without damage to CP/M, then this is so bad, you need
either
AI> one or the other, and all together and the hell will come out at once.

Once again: FROM bcd to bin it is VERY possible to recode FAST.
On the contrary - problems. It is necessary to divide, which takes a LOT of time.
Since data very often needs to be output in ASCII form, then
it is more advisable to store it in a clock in BCD format - from it you can
convert it to ASCII FASTER.

├┤i Renat & DEnis !

[...]

RM> And if you really need it, this mode is determined by software,
RM> so the driver can be universal, then you need it
RM> there will be one 5026/18.42 :))))

this is the most reasonable option.
Determine the format by bit and recode. But from BCD it will be FASTER.

Throw it in.
Just one request - can I have a diagram in the text? with placed
signals/contacts, inscriptions sho/where, etc., in short, as
done in normal circuits. (and it’s possible even with any number of
characters in a line, but better within 64x)

With best wishes, Denis.

KF> BCD or binary ) time in hours KF> store ? IMHO
it’s better in BCD - you can convert KF> to BIN quickly and in ASCII too quickly, in
unlike BIN.
I agree.
But for greater compatibility there will be an auto-detection and accordingly
the driver will issue/receive information in _ASCII_ format!
and with the clock it will fit... ;)

C best, Denis.

RM> Yeah, it's like RAM in Turbo2+ - no one except the developers
RM> can find it! :) And he doesn’t want to. :) - until you get to
RM> it...

In general, you need to create a driver system, and that’s it. Do it everywhere!

With that, Roman, let me say goodbye.
KIR.

[skip]

AI> 2All: someone tell me the thread of this ZxNews, it’s too painful
AI> to read who you want.

41 number? 2.5 disks. Do you want it? ;))))

With this, Andrey, let me say goodbye.
KIR.

RM> didn’t hear them!
AI> ZxNews was such a newspaper in St. Petersburg;) you yourself
AI> told me about this number.
It was. But these names stood on the same level as the names of computers. And I
doubted... And *MAS* - who is this?
And I looked at that information on the clock in ZXNews-35 back then, and there everything was in relation to
the Scorpa board. I thought it was ripped out of SMUK. But it turns out there is a _separate_
standard!

RM> This is just funny! There are several standards in St. Petersburg alone!

[ ]
RM> Smuk, it seems, is an established standard.

but since no one knows the CMOSa addresses in Smuk, or rather
as those who know said, Zonov does not allow this information to be given out,
you have to reinvent the wheel...

And since you are too lazy to buy a smuk for just a watch,
plus then you will also need expander
(since I have an XTR slot), it means the case cover
will not be closed....
Besides, I just don’t like PROF-ROM,
I’m used to 2.95...

RM> What is ZXNEWS?! And *MAS*?! Are these computers like that? But I haven’t
RM> heard of them!
^^^^^^^^^^^^^^
;-)))))))
ZxNews is such a newspaper
*MAS* is such a person...
well, in principle, you can call me a computer... ;-)

KF> I misunderstood... if I published a connection diagram in ZxNews CMOS, the watch is cut according to the same scheme,
then _HOW_ there can be two options???

[ ]

29-05-98 at 10:07:24 Roman Milukov wrote for Kirill Frolov

KF>> You’ll have to. I have already counted: 1.V_Profi. 2. Glitch. 3.Smuk.
KF>> 4.ZXNEWS. 5.*MAS*...
RM> This is just funny! There are several standards in St. Petersburg alone!

[ ]
RM> Smuk, it seems, is an established standard.

but since no one knows the CMOSa addresses in Smuk, or rather
as those who know said, Zonov does not allow this information to be given out,
you have to reinvent the wheel...

And since you are too lazy to buy a smuk for just a watch,
plus then you will also need expander
(since I have an XTR slot), it means the case cover
will not be closed....
Besides, I just don’t like PROF-ROM,
I’m used to 2.95...

RM> What is ZXNEWS?! And *MAS*?! Are these computers like that? But I haven’t
RM> heard of them!
^^^^^^^^^^^^^^
;-)))))))
ZxNews is such a newspaper
*MAS* is such a person...
well, in principle, you can call me a computer... ;-)

KF> I misunderstood... if I published a connection diagram in ZxNews CMOS, the clock is cut according to the same scheme,
then _HOW_ there can be two options???

[ ]
KF>> 1. There are fewer glitches in tr-dos and therefore there are fewer glitches.
RM> Yeah, it’s like RAM in Turbo2+ - no one except the developers
RM> can find it! :) And he doesn’t want to. :) - until you get to
RM>him...

hmm? have you tried?
everything worked fine, and the brakes were not noticeable...

What should I look for?
when I needed data on switching RAM to Turbo2+,
the document was found right there... The one who had this Turbo2+...

Well, that's all
*MAS* with a sledgehammer

-+- handles [left and right]

AI> ^^^ what kind of miracle is this?

YOU ARE A MIRACLE! ;-)))

AI> 2All: someone tell me the thread about ZxNews, it’s too painful to read it.

all ZxNews, or just the article itself about CMOS?

here’s a piece about CMOS

=======================================================================
Connecting to a computer
──────────────────────────

It is necessary to connect the AD0...AD7 signals to the processor data bus.
Connect the /RES (18) signal to /RESET processor (26th pin)

The remaining pins - AS, R/W, /DS need to be connected to address decoders.

Signal state
──────────────────

AS R/W /DC
nothing 0 1 1
select register number 1 1 1
read from register 0 1 0
write to register 0 0 1

For example, on the yellow Scorpio board, pins AS, /DS, R/W signals
can be supplied from m/s D54:

D54/13 through an inverter to AS
D54/11 to /DS
D54/15 on R/W

In this case, the CMOS clock port addresses will be located in the TR-DOS area.

With this switching scheme, only bits 1 and 7 are analyzed, but to
avoid conflicts with other ports, such port addresses are recommended

Selecting register #D8
Reading from register #58
Writing to register#58
=========================================================================

And now I’m just using other addresses
Selecting the #FFF9 register
Reading from the #FF79 register
Writing to the #FF79 register

But since only bits 1 and 7 are analyzed, there is no
“new” option! or
I didn’t understand my answer about “soft” decryption...

2KF: I’ll explain it popularly

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 <- these are the bit numbers
#D8 1 1 0 1 1 0 0 0 #F9 1 1 1 1 1 0 0 1 <- these are the addresses
- - - -

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 <- these are the bit numbers
#58 0 1 0 1 1 0 0 0 #79 0 1 1 1 1 0 0 1 <- these are the addresses
- - - -

Simply with addresses #FFF9 and #FF79 I will 100% not break into anything!

29-05-98 at 15:20:45 Andrey Isaev wrote for Kirill Frolov

KF>> You’ll have to. I have already counted: 1.V_Profi. 2. Glitch. 3.Smuk.
KF>> 4.ZXNEWS. 5.*MAS*...
AI> ^^^ what kind of miracle is this?

YOU ARE A MIRACLE! ;-)))

AI> 2All: someone tell me the thread about ZxNews, it’s too painful to read it.

all ZxNews, or just the article itself about CMOS?

here’s a piece about CMOS

=======================================================================
Connecting to a computer
──────────────────────────

It is necessary to connect the AD0...AD7 signals to the processor data bus.
Connect the /RES (18) signal to /RESET processor (26th pin)

The remaining pins - AS, R/W, /DS need to be connected to address decoders.

Signal state
──────────────────

AS R/W /DC
nothing 0 1 1
select register number 1 1 1
read from register 0 1 0
write to register 0 0 1

For example, on the yellow Scorpio board, pins AS, /DS, R/W signals
can be supplied from m/s D54:

D54/13 through an inverter to AS
D54/11 to /DS
D54/15 on R/W

In this case, the addresses of the CMOS clock ports will be located in the TR-DOS area.

With this connection scheme, only bits 1 and 7 are analyzed, butto
avoid conflicts with other ports, the following port addresses are recommended

Selecting register #D8
Reading from register #58
Writing to register #58
============================================================================

And right now I’m just using other addresses
Selecting register #FFF9
Reading from register #FF79
Writing to register #FF79

But since only bits 1 and 7 are analyzed, there is no
“new” option!

IMHO KF> either couldn’t decompose the addresses bit by bit, or
didn’t understand my answer about “soft” decryption...

2KF: I explain popularly

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 <- these are the bit numbers
#D8 1 1 0 1 1 0 0 0 #F9 1 1 1 1 1 0 0 1 <- these are the addresses
- - - -

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 <- these are the bit numbers
#58 0 1 0 1 1 0 0 0 #79 0 1 1 1 1 0 0 1 <- these are the addresses
- - - -

It’s just that with addresses #FFF9 and #FF79 I 100% won’t break into anything!

Well that’s all
*MAS* with a sledgehammer

-+- handles [left and right]

AI> read what you want.

KC> Number 41? 2.5 disks. Do you want it? ;))))
?!! I don't understand. The number with the clock is 35!? And not 2.5 disks. Was it number 41? Or is this a joke?

RM> didn’t hear them!

KC> :))))))))))
KC> First of all, there was such a newspaper...
:) Yes, I know. I even have the 35th issue, where the connection to the “yellow
Scorp” is described.

KC> The second is the person who published the diagram
KC> of connecting the CMOS in this newspaper... ;)
And here yes... :) There were also authors with first and last names. :)

KC> In general, you need to create a driver system, and that’s it. Doing
KC> everywhere!
That’s also ugly. When you load the flop head, it will fidget around on the disk for half a day until it loads all the drivers. BIOS is needed!

AM> but since no one knows the addresses of CMOSa in the confusion, and
AM> more precisely
AM> as those who know said, Zonov does not allow this information to be given out
AM>, then we have to reinvent the wheel...
Strange! =) Zonov doesn’t want coders to support his standard?..

AM> *MAS* is that kind of person...
Well, now I’ve found out the alias of Alexander Mayorov. :)

AM> finally KF> understood poorly... if I published in ZxNews
AM> the diagram
AM> of the CMOS connection, the watch is connected according to the same scheme,
AM> then _HOW_ there can be two options???
Uff... It’s already easier...
So, more or less normal standard 2 - Glitch and *MAS*.
Let Zonov think about SMUK, since he won’t admit it in a good way? :)

RM> You can easily and painlessly remake
RM> into
RM> “Glitch”. IMHO! - maybe someone uses the local CPU/M. :)
AI> It’s easy and painless to do this anyway, there’s a decoder
AI> on RT’s, and IMHO everyone uses the CPU/M here because

Well, if each of them has a CMOS circuit and if they are all different, then throw
all :), and finally I meant the number where the circuit was published.

RM> Wise decision. Just don't do it as a separate file! And
RM> it will be like ZED will take half a day to load.

It won’t. I will cache the directory. Now I will cache everything - rulez!
;))))

With the best, Denis.

Once on May 29, 98 a letter was sent from Renat Mamedov to Denis Dmitriev:

RM> I suggest: replacement driver:
RM>
RM> start - reading from the register
RM> start+3 - writing to the register
RM>
RM> If the number #AA is not in the clock cell #11, consider
RM> the clock
RM> as missing.

Is it stitched there, in the clock?
Or is it entered programmatically? If it's programmatic, then how can I put it there if the program immediately determines that there is no clock? you can
blindly push it into that register, and then see whether it has been stuffed
or not - that's autoconfig for you :)

In general, since the clocks can be different, I will make a driver
with functions not for writing/reading a register, but for immediately writing/reading
time (transferring time to registers in BCD format or via a stack or
pointer in ASCII form - I haven’t decided yet).

With best regards, Denis.

AM> all of ZxNews, or just the article itself about CMOS?
Just an article about CMOS.
AM> here’s a piece about CMOS
is that all there is about CMOS or just a part?

DD>
DD> Is it stitched there, in the watch?
DD> Or is it programmed? if programmatically, then how can I put it there
DD> if the program immediately determines that there is no clock? you can
DD> blindly push it into that register, and then see whether
DD> whether it was stuffed
DD> or not - here's the autoconfig for you :)

During my watch childhood... In general, even if
there is a watch, sometimes it is necessary to do so that the drivers
do not see them - for example, isdos when working with Mysdos
disks - it stores something on the screen, the clock is buggy.
Sometimes the clock can just glitch :(

DD> In general, since the clocks can be different, I will make a
DD> driver
DD> with functions not writing/reading the register, but immediately
DD> writing/reading
DD> time (transferring time in registers in BCD format or
DD> via the stack or a pointer in ASCII form - I haven’t decided yet).

A la C? via the stack :))) and regarding data transfer:
there are such days, in which are ordinary gaskets...
Sometimes the microcircuit is not ready to transfer data during
second updates. The driver on im2 will begin to slow down.
Therefore, it is best to skip unaccepted data.

That's it.

And the bcd format is mandatory - everyone understands this except Isaev,
even in Montana they store it this way :)))

Be healthy!
Renat Mamedov

DD> Throw it in.
DD> Just one request - can I have a diagram in the text? with
DD> placed
DD> signals/contacts, what/where inscriptions, etc., in short, how
DD> is done in normal circuits. (and it’s possible even with any
DD> number of
DD> characters in a line, but it’s better within 64x)

1)
There won’t be a diagram in the text - I’m, of course, a patriot, but not that
the same :)

2)
The description was new, but my computer is really buggy right now, she
died...

3) When it’s ready, I’ll give Tim a soap so that the server won’t be offended :)

4) in connection with p2, p3 won’t be soon, but I’m too busy.

5) And in general, is it necessary? :(((I’m tired of useless arguments
“I have to work” (c) Ulyanov

6) well, that’s all...

Be healthy!
Renat Mamedov

Fri Jun 05 1998, Renat Mamedov squeezed the keyboard, hoping that the following words would reach Denis Dmitriev
:

RM> 3) When it’s ready, I’ll soap Tim so that the server won’t be offended :)

:)

RM> 4) in connection with p2 p3 will not be soon, but I’m too busy and busy.

Roman Milyukov stopped by here and said that you need music...
If anything, contact Vitalic Svetashov (2:465/204.23). If he wants
to help, there will be music for you... :) Only I understand that you need to
show
something from the game for inspiration to come :)

Hasta la vista.
Tim Kelly

KC> Number 41? 2.5 disks. Do you want it? ;))))

RM> ?!! I don't understand. The number with the clock is 35!? And not 2.5

Personally, it seemed to me that Andrey wanted all the numbers...

RM> of the disc. Was it number 41
RM>? Or is this a joke?

Not a joke. In total, ZxNews published 41 (forty-one) issues.

RM> That’s also ugly. When loading the flop, the disk will fidget for half a day until
RM> loads all the drivers. BIOS is needed!
^^^^^^^^^^
Driver. ;)

And drivers are needed only for those devices that have many options, such as a modem, a clock. Keyboard layout, and that's it.

AI> Well, if each of them has a CMOS circuit and if they

Not in each, but there is something interesting.

AI> all different, then throw in

In appearance they are not very different, but in content... ;)

AI> everything :), but finally I meant that number where

Sir maniac? I don't. I threw ASPECT 9 to Roman M., and it was lost. And throw 2.5
disks...

AI> diagram published.

I can do this. Wait at speed. (maybe...) ;)

Sincerely, Dmitry (SchemeMan) coder, artist and ironworker.
╔═══════════════════╗
· Mr.Gluk & Company ·
╚═══════════════════╝

AI> Yes, we need to cut everything off of it and put it back together, don’t you think this is difficult? and in CP/M they will stop working.

What is “that’s all”? Two or three wires? The port itself needs to be stuck on top, yes. But don’t you think that it’s better for everyone to connect the clock according to Profakowski
now?

DD> It won’t. I will cache the directory. Now I will
DD> cache everything - rulez! ;))))
:) Wow! We also need to make a fact about this - “Note to the Hostess”! :)

And the din is ready and passable... There are little things left like menus -
who would have written :))) There will be no demo version - castrating
completely is not good, and in general it’s all pampering...
Do it completely and immediately.

The steering wheel itself is on 256 (scorpio, profi, stump). on 128 there is also a steering wheel,
but not like that :)
True, I don’t leave the 8th bank to the scorpion - there is no room for
indulging in all this :)))

Well, should I throw screenshots?

[about Vitaly 465/204.23]

Why is he so famous that everyone recommends him? why is he not visible in the echo (not audible :)))?

Be healthy!
Renat Mamedov

RM> Isaev just said in a personal conversation that our din -
RM> [skip]... Hands give up... I want a couple of screenshots in the echo

RM> Strange! =) Zonov doesn’t want his standard to be supported by coders?..

yes, no one knows the CMOS ports in SMUC, Larchenko doesn’t bother...
and polling the clock via RST#8 takes about a quarter of the frame,
therefore it’s difficult to read the clock every time, and that leaves your favorite
INTERRUPT.

All the best.

Dmitry aka -=LD=- / X-TRADE GROUP.

-+- SMM version 1.08

RM> Uff. Already easier.

Yes nefiga. In ZXNEWS'e ports are written #58 and #D8.
And in *MAS*'a one bit differs!

KC> ^^^^^^^^^^
KC> Dpaivepny. ;)

And each program has 65535 drivers and 65536 files on disk. Keyboard layout, and all.

Still need BIOS and OS.

Wi7h be57 Wi5he5, FK0.

DD> It won’t. I will cache the directory. Now I will cache everything - rulez!
DD> ;))))

Crazy idea - make an installer. Install it
directly into the file that is the largest and then download everything at once
without jerking your head again.

├┤i Dmitry & Roman !

[...]

DL> yes, no one knows the CMOS ports in SMUC, Larchenko doesn’t bother...
DL> and polling the clock via RST#8 takes about a quarter of the frame,
DL> therefore, it’s difficult to read the clock every time, and your favorite one remains
DL> INTERRUPT.

Well, even if in ASCII, then only from 5 and 2 cans, and it’s still buggy.

RM> will load all drivers. BIOS is needed!
KC> ^^^^^^^^^^
KC> Driver. ;)

RM> What is “everything”? Two or three wires? The port itself needs to be attached
Well, roughly speaking, three, but this is just a snapshot, you need to climb according to the scheme.
RM> from above,
RM> yes. But don’t you think that it’s better for everyone, according to Profakovski
RM>, to now connect the clock?
I didn’t think, I don’t think and I won’t think! but the timekeeping standard can be used
Profinsky, although if you do everything through the driver then...

Hello, Kirill!
05 Jun 98 Kirill Chubenko was squeezing his fingers in the hope that Andrey Isaev would read about

AI>> It’s not about the graphics, your graphics aren’t bad, it’s all about the
AI>> plot.

DP> And our plot just worked and that’s all.

Nu-nu... :)

Come on. Throw it!

RM> And the din is ready and passable... There are little things left like menus -
RM> who would have written :))) There will be no demo version - castrating
RM> completely is not good, and in general it’s all pampering...
RM> To do it - so complete and right away.

The demo is for the clientele. They usually don’t buy it on the fly...

RM> The steering wheel is the 256 (scorpio, profi, stump). on 128 there is also a steering wheel,
RM> but not like that :)
RM> True, I don’t leave the 8th bank to the scorpion - there is no room for
RM> it’s all pampering :)))

I almost shouted about the off-topic, I realized it in time... :)
What about the very non-standard 256s? ;)
What is the difference between 128/256?

RM> Well, why not post screenshots?

Look higher, huh? :)

RM> [about Vitaly 465/204.23]

RM> why is he so famous that everyone recommends him? why is he not visible in the echo
RM> (not audible :)))?

But he sees everything! :) And what he is famous for - he will show you himself if he wants :)

2Vitalic: I would throw something for the soul... :)

I greet you from the bottom of my heart, Andrey!

Sat Jun 06 1998, Andrey Isaev squeezed the keyboard, hoping that the following words would reach Tim Kelly:

RM>> Isaev just said in a personal conversation that our din is

he wants, but, IMHO, he wants them to buy smuk and use RST 8,
which is described in the doc...
And the fact that it is _long_ is not important...

And if _I_ personally don’t need a screw on the spec for nothing,
(no, you can do it for nothing ;-), but you need a watch, then what?
buy smuk???

AM>> *MAS* is that kind of thing man...
RM> Well, now I recognize the alias of Alexander Mayorov. :)
Damn, it would be better if I looked in the “Authors” section....
otherwise I took it and got the last name wrong....

[ ]

RM> So, more or less normal standard 2 - Glitch and *MAS*.
^^^^^^^
this connection was not developed by me alone!!!
but together with Dmitry Lomov! (X-Trade)
therefore, it’s not worth calling this connection by me!

RM> Let Zonov think about SMUK, since he won’t admit it in a good way? :). It doesn’t work out...

Well, that’s all
*MAS* with a sledgehammer

-+- wild bastard...

KF> No big deal. In ZXNEWS the ports are written #58 and #D8.
KF> And *MAS* differs by one bit!

!@#$%^&*()
you don’t seem to realize that _SOFT_
address decoding is used, and the number of combinations is infinite!
I _specially_ set all possible bits to "1"
so that clearly avoid climbing “in the wrong place”!

And if we take your words, it turns out that on the Pentagon
memory port addressing as #7FFD and #FD are completely different
standards, completely incompatible?

And if I climb on a scorpion in #7FFD as in #703D,
and in #1FFD as in #35A5, will you also start talking about a NEW
standard? Like it's not compatible with the original...
Although _it_ will work! and without reworking the board!

Also soft decryption...

RM> you will have to download and uninstall :))))

Well, now you need to climb onto the server. :(
2TK: let's go to the echo too... At least the loader for ZED and the source of the time installer!

DL> beloved INTERRUPT.
...Yes, the policy of the Scorpion company, which is trying in every possible way to crush other
platforms, has begun to backfire on it! :)
Instead of establishing her standard, with her clumsy actions
she gave birth to another standard, perhaps more convenient.

PS. While you're here, tell me, is there a version of STORM older than the seventh format?

Hello, Dmitry!

How are things going with the new version of the subject? And finally, what is the last one?

AM> Damn, I’d better look at the “Authors” section....
AM> otherwise I took it and got the name wrong....

Majorov?!

I’m leaving and leaving. :)

With all kinds of regards and wishes.
Igor.

... Pedestals were invented by dwarfs.

Today it turned out that the Scorpio driver does not work.
I released an alpha version, so to speak, for testing - to distribute
to Scorpovites/professionals. The pro is alive, the scorpion is dying...
I already found the mistake.

TK> I almost shouted about the offtopic, but I caught myself in time...
TK> :)

As always, I didn’t understand which one? Well, it doesn’t matter, since it’s off-topic :).

TK> What about the very non-standard 256s? ;)

It would be a great honor to support all extensions - these seem to have become the standard. And on not very standard ones - it won’t see
the extra memory there, and that’s all...
An external driver for the game is insanity. Otherwise, all the options
will not be taken into account.

TK> What is the difference between 128/256?

128 kilos of twice compressed (under AU) numbers. Cool.
You won’t hear this on 128s :)

To be honest, I don’t quite understand it myself... :)
RM> why can’t you see it in the echo (can’t hear it :)))?
Probably not enough smart thoughts :(

PS Change the subject from time to time ;-)

Vitalic

TK> 2Vitalic: I would throw something for the soul... :)
So you have everything... ;)
And it’s a little scary - what if they stutter? :-))

Good luck!
Vitalic

AM> this connection was not developed by me alone!!!
AM> but together with Dmitry Lomov! (X-Trade)
AM> therefore, there is no point in calling this connection me!

And it wasn’t me who called it that! ...Think together with Dmitry and give a name to your
scheme.
Or better yet, remake it in Gluck’s style. ;)

Although a universal driver will not be much more complicated than a special one. You just need to decide how the program will determine the clock circuit. I would suggest looking into cell #11 when you first start (if I'm not mistaken). The glitch puts the number there
#AA.
You can keep #55 there, for example. And depending on this value, immediately
reconfigure the driver. And if there is #FF, be sure to display the inscription “Set the clock!” - this is very important! :)

IG> Majorov?!

and you, Brutus... ;-))))

the letter “j” in the middle of the word most likely reads like “Y”...
or am I wrong?

Why is it floundering from the bay?
It’s in the style of Paradise Lost and maybe better. (As a graphic designer will say)

RM>
RM> Right now someone will immediately start lying: they say we’ll sell it - don’t
RM> believe it...
And I won’t yell, I’ll say it in a whisper.

RM> Do it yourself I'm not going to spread it. I'd rather
RM> play it. Free :).
People probably also want to play this steering wheel?

I greet you from the bottom of my heart, Roman!

Mon Jun 08 1998, Roman Milukov squeezed the keyboard, hoping that the following words would reach Renat Mamedov
:

RM> Well, now you need to climb onto the server. :(
RM> 2TK: let's echo too... At least the loader for ZED and the source
RM> of the time setter!

Don't... Take it from the server.

I greet you from the bottom of my heart, Vitalic!

Tue Jun 09 1998, Vitalic Svetashov squeezed the keyboard, hoping that the following words would reach Renat
Mamedov:

RM>> why is he so famous that everyone recommends him?
VS> To be honest, I don’t quite understand myself... :)

In a minute everyone will understand... :)

Tue Jun 09 1998, Vitalic Svetashov squeezed the keyboard, hoping that the following words would reach Tim Kelly
TK>> 2Vitalic: I would throw something for the soul... :)
VS> So you have everything... ;)

The hint is taken! In the echo!

VS> Yes, and it’s a little scary - what if they stutter? :-))

Afraid of teeth... :)

RM> Right now the situation is such that all devices exist in
RM> several vatiants.

But not in hundreds? I understand if on the spec there was a situation like on the PC, with a bunch of video, sound, etc. And write 5 memory drivers, 3 keyboards, 4 clocks, etc. Difficult? You can generally provide information about the driver - whoever needs it will write it himself
or find someone who will write to him.

With that, Roman, let me say goodbye.
KIR.

AI> Hello, Kirill!
AI> 05 Jun 98 Kirill Chubenko was pinching in the hope that
AI> Andrey Isaev will read about
AI> again about cmos, I read it and decided to answer:

Once on June 9, 98 Roman Milukov sent a
letter to Aleksandr Majorov:

[ skip about the subject driver ]

RM> And if there is #FF - be sure
RM> to display the inscription “Set the clock!” - this is very important! :)

Yeah, "Please, insert CMOS chip and press any key" ;)

RM> I think we could stop there. As "page
RM> RAM" this is quite enough, imho. But you need to connect SIMM 4M
RM> through a separate port, like an electronic drive, and be sure to
RM> make it smarter. Can it be substituted by a page not
RM> with #C000, but with #0000?

By the way, there are no sims.
Or rather, about additional memory addressing ports.
there is an option to use all eight bits of the Profi expansion port
#DFFD (you don’t need to invent a separate port, and you can address
a decent amount of memory), or use a separate port
for memory expansion. if the second option, then I want to offer
a series of ports #AxF7 (16 or 32 ports, as you like :), while
the port address decoder is the same as for #eff7 and subject ports (mmma
ID7).

Well, and finally, does anyone have a ready-made one? Sims wiring diagram? with
regeneration, etc.?
We couldn’t find one in Kharkov, so a trial
version was developed that uses internal regeneration of
sims; contains <10 small microcircuitslogic, works together with the main
memory; or you can put simm 512k instead of RU7 ;). The scheme was developed by
Konstantin Kovernikov (Evil Genius).

If there is no ready-made scheme and ours will work, then
I will definitely post it here. Now we have the most “fundamental” problem - which
port should we allocate memory expansion to?

With best regards, Denis.

RM> PS. While you're here, tell me, is there a version of STORM older than the seventh
format?

no. the new one will be no earlier than September - for which two months are allocated, which could be used for the next demo. I decided that STORM is
more interesting to me than the demo...
there are so many new things planned in STORM 2.0 that it won’t
fit on a large sheet :) I closely followed the bazaars on the ASMA theme,
and along the way I thought and listened to my friends.

All the best.

Dmitry aka -=LD=- / X-TRADE GROUP.

RM> And it wasn’t me who called him that! ...Think with Dmitry and give a name
to your
RM> circuit.

"circuit" ;-))))

RM> Or better yet, remake it in Gluck's style. ;)

How many mikruh do you need to pick up according to his scheme?
And for a scorpion?

And according to our scheme, only one inverter is needed, and even that in a scorpion
is available free...

RM> Although a universal driver will not be much more complicated than a special one. You just need
RM> to decide how the program will determine the clock circuit. I would suggest that when you first start, look into cell #11 (if I'm not mistaken). The glitch puts there
number
RM> #AA.
RM> You can keep #55 there, for example. And depending on this value
immediately
RM> reconfigure the driver. And if there is #FF, be sure to display the inscription
"Set the clock
RM>!" - this is very important! :)

br...
I don’t understand
how the _contents_ of the _CMOS_ cell will help you determine
_the_connection_scheme_?

After all, in order to read data from the CMOS you need to know
its connection diagram, and if you know the circuit, then why
determine it (the circuit) by the contents of the CMOS?
(that’s what he said! ;-)

v driver for MMD 4.00 I used the simplest option:
I read the contents of all _hour_ registers, and if all data
(hours/min/sec/day/month/year) are _real_, then there is a clock!
If at least something is wrong (for example 66seconds) - no clock.

DD> By the way, there is no need for Sims.
DD> Or rather, about additional memory addressing ports.
DD> there is an option to use all eight bits of the expansion port
DD> Pros
DD> #DFFD (no need to invent a separate port, and you can
Forget about this option! #dffd this is pure It’s a pro-Finnish port and it’s not worth using it for anything other than its intended purpose. How do you think such a program will work on the Pro itself?
DD> address
DD> a decent amount of memory), or use a separate
DD> port
It’s much better!

DD> Well, and finally, does anyone have a ready-made circuit
DD> connecting sims? with regeneration, etc.?
Definitely not in 5026, although Ivan Mak once threw a circuit into ZX.SPECTRUM.

DD> If there is no ready-made circuit, and ours
DD> will work, then
DD> I will definitely throw it here.
And when will you install the cache circuit, the one with which you can replace the chips?

KC> Oops... I already forgot about this... Sorry. Kin
KC> for sure. ;)
It doesn’t seem necessary, this article was here.

RM> It will be a great honor to support all extensions - these, it seems,
RM> have become a standard. And on not very standard ones - he won’t see
RM> the noise there is extra memory, and that’s all...
RM> The external driver for the game is insanity. Otherwise, all the options
RM> cannot be taken into account.

I’m not talking about non-standard page switching, I’m talking about... offtopic :)

...
DD> for memory expansion. if the second option, then I want
DD> to offer
DD> a series of ports #AxF7 (16 or 32 ports, as you like
DD> :), while
DD> the port address decoder is the same as for #eff7
DD> and subject ports (mmm ID7).

The second option is preferable imho, because and in "Profiks" this memory will be
additional (there will be no unnecessary conflicts) and it will be more convenient to bridge to Pent.

AM> br...
AM> didn’t understand
AM> how the _contents_ of a _CMOS_ cell will help you determine
AM> _connection_scheme_?

AM> After all, in order to read data from a CMOS you need to know
AM> its connection diagram, and if you know the circuit, then why
AM> determine it (the circuit) by its contents kmosa?

Look. At the first start, the program reads cell #11 on the Glitch ports, if
there is no clock (#FF received), it tries on your ports.
Depending on the results, the driver is modified. Oh, yes, you can keep #AA there for both
schemes. :)
AM> in the driver for MMD 4.00 I used the simplest option:
AM> I read the contents of all _hour_ registers, and if
AM> all data
AM> (hours/min/sec/day/month/year) are _real_, then there is a clock!
AM> If at least something is wrong (for example, 66 seconds) - there is no clock.

You can also Well, I got laid, but I saved one slot. :)

KC> I can do this. Wait at speed. (maybe...) ;)
AI> Well, let's wait...
KC> Oops... I already forgot about this... Sorry. Kin
KC> for sure. ;)

Hello, Kirill!
18 Jun 98 Kirill Chubenko pressed his fingers in the hope that Andrey Isaev would read about

16-06-98 at 23:27:30 Renat Mamedov wrote for Roman Milukov....

RM> Aleksandr Majorov lied here for Roman Milukov, and I will teach you
RM> how to lie!

We are not lying! We either get it right or we make mistakes! ;-))))

AM>>> Pin 13 (/CE) - crystal selection. With on-
[ ]
RM> In the same Radio Yearbook to which
RM> Roman once referred, it is said that with inactive sampling, m/s has a significantly
RM> lower current consumption. I think this also applies to Dallas,

therefore, when the computer's power is turned off, the chip switches
to low-power mode, and if there is +5V, then an extra
milliampere will not make a difference...

RM> but what should you do with it when the battery runs out? But maybe
RM> I’m wrong...

“I’m tormented by vague doubts” (C) that in Dallas, not everything
is so simple...
The 13th leg on the pussy itself, from where the chips were torn out,
was attached to the ground!
And I once asked the people, so one time a car was
seen with a dead car battery...
IMHO there is a recharger...

[ ]
AM>> And on Scorpio there is no #EFF7 port, but under TR-DOS
AM>> there are free ports...

RM> and on Scorpio there are free ports in the typdos?

There are two ID7s, which have “free” ports.
One “stands” with TR-DOS, the second is “regular”
Ha"normal" there are the following free ports:

address 7 6 5 4 3 2 1 0
--------------------------
0 1 0 0
0 1 1 0
1 1 0 0

The remaining bits are not analyzed. Moreover, these addresses are simply
access to a port, without division into writing/reading.

And in TR-DOS ID7 there are such “ports”

address 7 6 5 4 3 2 1 0
--------------------------
0 0 write
1 0 write
0 0 read
1 0 read

So you don’t even need to “add” by OR
"SELECT ADDRESS" and "RECORD" / "READ"

As you can see, connecting the clock requires current
one inverter...
So this is the _only_ advantage of connecting
this clock for _scorpio_...

[ ]
AM>> *MAS* with a sledgehammer

RM> Somehow in Format I saw your initials under mmd driver.
RM> It also seemed to be written for Hayes... How did the process???

the process was interrupted because... the person who had haes at that time could not specifically explain how
it was buggy, “it’s just buggy and that’s all!”.

And then I got tired of it... And all the data was lost...
I’m somehow not interested in haes right now, I’m still too lazy to rip it out of my pussy, I don’t need it anyway tama...

RM> I threw out my own version of this scheme, did you see it?
RM> There is no difference between Penta and Scorpio.
RM> It is not tailored for a specific type of computer.

Whoa! but ours is sharpened, and therefore there is no need for mikruh...

RM> And then you can’t count the body directly here. There is ID7 - an address
decoder
RM> for several circuits at once, TM8 - actually port #EFF7 - also
universal...

sorry, port #EFF7 - what kind of universal is this?
I don’t have anything connected to it... ;-)))
Yes, we have this port finally no...
What's hanging on it?

[ ]
RM> Depending on the results, the driver is modified. Oh, yes, you can keep #AA there in
both
RM> schemes. :)

wow!

RM> And in Penta, initially, there was no such port either, until people began to install it!

And _what_ am I going to hang on it?
only one watch?

We don’t have those bells and whistles that you hang on this port...
and besides, we have a more accepted method of not soldering
microphones on a computer, but sticking a scarf into the connector...

[ ]

RM>> I think it would be interesting to use this output...
RM>> Add it to NMI...

AM>> yeah, don’t forget the interrupt manager ;-))))

RM> ?!! This is probably some kind of 40-legged boar? A? ;)

580ВH59, 28 legs

in a nutshell: there are 8 interrupt request legs,
and when an interrupt is requested, the chip issues an interrupt to the processor and
after which it can “push” a CALL command with the address to it...
But this is suitable for a regular interrupt, in IM1 mode...

And NMI simply jumps to #0066...

[ ]

AM>> where does int go from Hayes? ;-)))

RM> So I also have “magic” coming from the controller there! ;)

please! don’t be confused!
magic has its own “dispatcher”, it first turns on
TR-DOS ROM, and only then gives NMI, so the percentage jumps to #0066
in TR-DOS!

├┤i Aleksandr & Roman !

[...]

AM> and _what_ will I put on it?
AM> only one watch?

For example, I have one the extended screen hangs. And I’ll also “hang” a lot of things there
.

[...]

AM> and besides, we have adopted a more accepted method of not soldering
AM> mikruh on the computer, but of sticking a scarf into the connector...

However, there’s nothing to stick in. And there is no connector. You can’t stick yourself into something like that.

GS/XTR is not enough. The rest is explicit MD.

W!7h Be$7 W!$he$, FK0.

...
AM> And then I got tired of it... And all the data was lost...

It's a pity.

AM> I'm somehow not interested in the chaos right now, I'm even too lazy
AM> To rip it out of my pussy, there's no need for it anyway...

Can it be made FTN-compatible?

All the best.
Roman.

AM> wow! but with us it is imprisoned, and therefore there is no need for mikruh...
And this is a “+” in your opinion? ^^^^^^^ :) IMHO - "-"!
Well, it’s good that you don’t need any micro devices anymore.

AM> sorry, port #EFF7 - what kind of universal is this?
AM> I don’t have anything connected to it... ;-)))

So I said “universal”, not “standard”! Although many people have already made it, and you can consider it standard, but the fact that there is nothing on it in your
computer... you probably consider port #1FFD standard? And I have nothing on it! ;)

AM> Yes, we don’t have this port anymore...
AM> And what’s hanging on it?

It’s not “hanging”, but it’s working. :) I already wrote about 512*192.

AM> 580ВH59, 28 legs

Yeah. Or 1810. Let's also hook up VK37 (VT57) for DDP, VM89, etc... :)

AM> But this is suitable current for a regular interruption, in
AM> IM1 mode...

When everyone has a bunch of interrupt-generating devices, then we will
install VH59. In the meantime, well...

AM> And NMI just jumps to #0066...

So what? After all, from there a transition is made (if the byte in the “old” ROM is corrected!) to the address specified in #5CB0/B1! Wherever you want, send it there. The main thing is to know
in advance
where the interruption will come from - from haes or from the clock.

AM> yay! don't be confused!

Yes, I was joking! ;)

AM> "magic" has its own kind of "dispatcher", it first
AM> turns on
AM> TR-DOS ROM, and only then gives NMI, so the percent jumps to
AM> #0066 in TR-DOS!

TR-DOS is of no use to us here. :)

All the best.
Roman.

AM>
AM> “I’m tormented by vague doubts” (C) that not everything in Dallas
AM> is so simple...
AM> The 13th leg on the pussy itself, from where the chips were torn out,
AM> was attached to the ground!
AM> And I once asked the people, that’s how it happened once
AM> a car with a dead battery was spotted...
AM> IMHO there is a recharger...

Well, offtopic is not an indicator in terms of coolness. Maybe
they saved on the diode :) But if so, then it’s clear.

AM> there are two ID7s, which have “free” ports.
AM> One “stands” with TR-DOS, the second is “regular”

[well, I described the ports here, so what now? :).

Tue 23 Jun 1998 22:57, Renat Mamedov wrote to Aleksandr Majorov:

RM> Be healthy!

Will anyone ever come to our ZXNet sysopnik from Ivanovo?
Realshchikov - at least shoot ;)))))

Sincerely, Alexey Ivanov

KF> For example, I have an extended screen. And I’ll also “hang” a lot of things there
KF>.

_what_ and _when_?
and will others need it?

[...]

KF> However, there’s nothing to stick. And there is no connector. You can’t plug it into something like that.

well, that’s probably your problem?
I didn’t have a connector either, I needed it and it appeared!

There’s nothing to plug it in?
GS, XTR, SMUC, we plug in HDD, HAYES - not enough???

KF> GS/XTR is not enough. The rest is obvious MD.

and I can say that your load on this port
called “extended screen” is MD
and since it’s MD, then why do I need it?
It’s also logical?

and for some reason people plug in something else...
(list above) rather than collect what _you_ consider not MD.

For some reason people prefer to use editors under 64 characters,
rather than go into the computer and assemble some kind of expansion scheme,
for which there is also nothing...
(the situation is similar to the spring, see .general)