ZED under 512!

A straightforward question: is there a ZED for 512kb??? And preferably higher than 1.02beta, otherwise it is very buggy and slow. What I mean is that today in Rostov we have the first
person on the Spectrum in fido. Will soon appear in the echo, but only ZED needs
more normal, help plz!!!

Wiz zE BeSt WisHeZ 2 U!
-=JoCkeR/OmEga HaCkErS Grp/1998year=-

AH> A straightforward question: is there a ZED under 512kb??? And preferably higher than
AH> 1.02beta, otherwise it is very buggy and slow. This
Alas, no :(
AH> I mean, today in Rostov we have the first person on
AH> Spectrum in fido. He will soon appear in the echo, that's all
Does he have an RKT corrector for Zedov's letters? And that is, there is a possibility that
he won't succeed without it.
AH> ZED is needed more normal, help plz!!!
With joy, but there’s nothing :(

Sincerely, Andrey.

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

AI> Does he have an RKT corrector for Zedov’s letters? and that is, there is a probability
AI> that he won’t be able to do anything without it.
He doesn’t have such a corctor, if it’s not difficult, throw some soap
to me.

AH> So, no one is going to write anything cooler?
Not in the near future :( soon there will be a tosser for the zed, a little faster than the current one,
but in general, if the zed is launched from the RAM disk, then it (the zed) just flies.
AH> * Origin: I saw the secret maps, I know where we
AH> are sailing... (2:5061/33.32)
And where?

AI> And where?

Question for filling :)

AI> Sincerely, Andrey.
AI>
AI> ... The hedgehog is a proud bird: if you kick it, it won’t fly!
AI> --- Zloy dED1.02b---
AI> * Origin: To the world - Peace, To the student - Beer! (2:5026/18.42)

Sorry, they brought fresh beer...

__KLIM/Omega Hackers Group/MFA'98__

GK> ^^^^^^^^^
GK> And if in more detail...
There is a version of tyrdos in which a RAM disk is implemented, its volume is 1536 sectors,
works only on stumps with 512kb available as disk "D", everything that works through
#3d13 will work with ramdisk.

Sincerely, Andrey.

AI> Not in the near future :( soon there will be a tosser for the zed,
AI> a little faster than the current one, but in general, if the zed is started with

AI> There is a version of tyrdos in which a RAM disk is implemented, its
AI> has a volume of 1536 sectors, works only on stumps with 512kb
AI> is available as disk "D", everything that works through #3d13 will
AI> work with a RAM disk.

It would be wonderful to have such a bottle.
Get it for me plz..(with a detailed description)

Sorry, they brought fresh beer...

/ musicmaker \
__KLIM/Omega Hackers Group/MFA'98__

...Illiteracy is sister ignorance!

I recently came across some good beer... and with it a crazy idea
that might work - convert dos.sys into ZED-e in such a way that it
uses disk caching (obviously, all functions of Dydos will have to be emulated) in
128K memory.
Caching - Track-by-track, not sector-by-sector, because ZED constantly
reads/writes no more than one sector per disk revolution, otherwise
it will have to whistle.
You can make a cache for 512k (with auto-detection, of course).
The most pleasant thing is that only two files from the entire package will be replaced - DOS and
loader :)

Well, so what, nada? or who will do a good deed himself? (otherwise I need to go far for descriptions of the functions of the idiot).

With the best, Denis.

AI> Not in the near future :( soon there will be a tosser for the zed,
AI> a little faster than the current one, but in general, if the zed is started with
RM> No, much faster!

AI> volume 1536 sectors, works only on stumps with 512kb
AI> is available as disk "D", everything that works through #3d13 will
AI> work with ramdisk.

DD> So, it worked for me :)
And depending on your luck, Rick also succeeds, and therefore he doesn’t recognize this glitch :(
DD> (by the way, have you finished it already?)
Does that mean you’ve finished it? If the one that you have is packing letters into two packages and displays all
info on the screen, then he didn’t finish it :) and if not, then finished it.

DD> I recently came across some good beer... and with it a crazy
DD> idea
DD> that might work - convert dos.sys into ZED-e
[...]
DD> The best part is that only two
DD> files from the entire package will be replaced - DOS and loader :)
And the bootloader has already been redone, I inserted a program here that copies the current
time from cmos directly to zed, otherwise it’s somehow not good to have a cmos clock to enter everything by hand every time.

DD> Well, how about it, nada? or who will do a good deed himself? (ato
Of course, but it won’t be me.
DD> I need to go far for
DD> descriptions of the functions of the idiot).
Well, probably not to Moscow :)

RM> Okay. But tell me, is it possible to remove requests for selecting
RM> turbo-non-turbo and repeating formatting for drive “D”?
It’s possible, but it was simpler this way, and there’s less to change in TypDos, and every extra
changed byte adds incompatibility.

DD> So, it worked out for me :) (by the way, have you finished it yet?)
And it worked out for me, but I still process the written letters with PKT_corr before
sending them. For packing in two bags. Now, if only they could process ZED’s jujuks...

Hello, Andrey!

14 May 98 Andrey Isaev, hoping that Denis Dmitriev would read it,
wrote:

DD> (by the way, have you finished it yet?)
AI> Does that mean you finished it? if the one that you have is loading letters into
AI> two packages and displaying all the information on the screen, then it’s not finished :) and
AI> if not, then it’s finished.
:) Continue finishing it so that it also processes packages with yuyuks. And
make a small setup - enter the name of the program that he will launch after
his work (so that Melon will immediately launch,
for example).

AI> And the bootloader has already been redone, I inserted the program here
Well, then you have “here”, but we don’t have here. But for now there is no CMOS either. :) But this is temporary.

AI> which copies the current time from cmos directly to zed, otherwise
AI> it’s somehow not good to have a cmos watch and have to enter everything
AI> manually every time.

AI> It’s possible, but it was simpler this way, and there’s less to change in typdos
AI>, and every extra byte changed adds
AI> incompatibility.
And this way you can’t automatically create a ramdisk.

AI> And the bootloader has already been redone, I inserted a program here that
AI> copies the current time from cmos directly to zed, otherwise it’s not good
AI> having a cmos clock, you have to enter everything manually every time.

In the echo! IN ECHO! But only in a separate file!

Hasta la vista.
Tim Kelly

Thu May 14 1998, Andrey Isaev squeezed the keyboard, hoping that the following words would reach Roman Milukov
: Russian, Ukrainian, English. Try not to complicate the lives of others, write more clearly, if possible competently, correct the mistakes of others correctly and, if possible, by netmail.

[Skipped]
=== Cut ===

DD> used disk caching (obviously, all functions of TypDos
DD> will have to be emulated) in
DD> 128K memory.

[skip]

Will this caching use standard Typ-Dos points? (all sorts of #3d13)
If not... For me, with the screw, this won’t help.

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

TK> In the echo! IN ECHO! But only in a separate file!
What the hell to you all :) say thank you to Gluck, I have a watch first of all in the ports,
secondly the time is stored there for a friend, Gluck didn’t want to maintain this
'standard', and I'm not going to change it, because that's how it's done in CP/M'e.

RM> I received the soap today. He’s finishing the tosser, he’ll throw it in the echo soon
RM>, he says.
Oh, I’ll have it “soon” :)

RM> Well, you also have “tuta”, but we don’t have tutta. But so far there is no CMOS,
RM>. :) But this is temporary.
Well, then, no one has realized how much shouting there was until now :(

AI> Never mind you all :) say thank you to Gluck, I have a watch
AI> first of all, the ports are not sweaty, secondly, the time is stored there
AI> friend, Gluck did not want to maintain this 'standard', and
AI> I am not going to change it, because that is how it is done in CP/M'e.
Well, thank you. Why then was there a need to shout in response to a valuable offer from Denis, that everything was already there? Was it you who answered him at first?

KC> This kyshirovaniye will use standard points
KC> Tyr-Dosa? (all sorts of #3d13) If not... For me, with a propeller, this
KC> will not help.
Well, IMHO, a zed with a propeller should fly anyway.

RM> Okay. But tell me, is it possible to remove the selection requests
[...]
AI> incompatibility.
RM> And so it is impossible to create a ramdisk automatically.

AI> Well, well, how much shouting there was and still is, no one can imagine
AI> did not put it :(
Everyone has different difficulties imho. And the shouting was useful. It’s better to shout before people have time to weigh themselves down with them, than later.

AI> What the hell to you all :) say thank you to Gluck, my watch is not sweating in the first place
AI> ports, secondly the time is stored there for a friend, Gluck did not want
AI> to maintain this 'standard', and I am not going to change it, because that is how it is done in
AI> CP/M'e.
Well, here's another standard :( Maybe you can do it like Gluck - after all, he was the first to start :) , huh? Otherwise, there will be a bunch of incompatibilities again, again
'universal' CMOS drivers will have to be written :(

Well, packaged, Andrey, packaged!
[Team thief Alos MUST DIE!]

AI> What the hell to you all :) say thank you to Gluck, my watch is not sweating in the first place
AI> ports, secondly the time is stored there for a friend, Gluck did not want
AI> to maintain this 'standard', and I am not going to change it, because that is how it is done in
AI> CP/M'e.

ES> Well, here's another standard :(
Well, let's say this should be said about Renat's watch.
ES> Maybe you can do it like
ES> with Gluck - after all, he was the first to start :), huh? And then again
ES> there will be a bunch of incompatibilities, again 'universal'
ES> CMOS drivers will have to be written :(
Ha! It was not he who started it first, but the company that produced Profi, and I have just such
a copy, I had a watch even before Gluck started making his own, and
it was
he who did everything in my own way, not me.

ES>> y Gluck - after all, he was the first to start :), eh? And then again
ES>> there will be a bunch of incompatibilities, again 'universal'
ES>> CMOS drivers will have to be written :(
AI> Ha! The first one was started not by him, but by the company that produced Profi, and I have the name
AI> of such a copy, I had a watch even before Gluck AI began to make his own, and it was he who did everything his own way, not me.
But he was the first to write the firmware for CMOS (Glitch).

RM> Everyone has different difficulties imho. And the scream was useful. It’s better
RM> to shout before people have time to weigh themselves down with them, than
RM> later.
Well, who’s hung themselves up with them (will weigh themselves down)? Until now, no one has found any errors or omissions in the description, and from this it follows that either no one has read it (the description), or no one really needs it (cmos), damn it.

RM> And so you can’t create a ramdisk automatically.
AI> Automatically how?
RM> From a BASIC loader, at least... :) You have to press the button two more
RM> times.
He who doesn’t work, doesn’t eat!!! :)

AI> I’m not going to change it, because that’s how it’s done in CP/M.
RM> Well, thank you. Why then shout in response to the valuable
RM> proposal from Denis, that everything is already there?
But it really exists, and I expected that Renat would make a version for his
cmos.
RM> Was it you
RM> who answered him at first?
Well, I.

Hello, Eugene!
19 May 98 Eugene Safronov was pinching in the hope that Andrey Isaev would read about cmos again, I read it and decided to answer:

ES> CMOS drivers will have to be written :(
AI> Ha! It was not he who started the first, but the company that produced Profi, and
AI> I have such a copy, I had a watch even before
AI> before Gluck started making his own, and it was he who did everything
AI> in his own way, not me.
You yourself said: in Profi, the clock ports conflict with the K-mouse ports! Or do you not have a mouse - there is no problem :)
If they were implemented there in a normal way - it would be a different matter, then there would be no point
the whole market is about them!

AI> which copies the current time from cmos directly to zed, otherwise
AI> it’s somehow not good to have a cmos watch and enter everything
AI> manually every time.
Oh! Fill it up, pls! so that it was all together at once.

AI> Well, IMHO, a zed with a propeller should fly anyway.

One born to crawl cannot fly...
With tears in my eyes, I look at the propeller as it “compacts” after “killing”
the read packets. I just feel sorry for him (screw).

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

RM> And so you can’t automatically create a ramdisk.
AI> Automatically how?
RM> From the BASIC loader, at least... :) You have to poke the button two more
RM> times.

AI> And the bootloader has already been redone, I inserted a program here
AI> that copies the current time from cmos directly to zed, otherwise
AI> it’s somehow not good to have a cmos watch every time you enter everything
AI> manually.

RM> You said it yourself: in Profi, the clock ports conflict with
RM> ports
RM> K-mouse! Or do you have no mouse - no problem? :)
I have a mouse and, accordingly, there was also a problem (there was one), but I have nothing against Gluck
ports, but how it stores time in a watch does not suit me
specifically.
RM> If they had been implemented there in a normal way - it would be a different matter,
RM> then there would be no point there was a whole market here about them!
Even if the watch were implemented normally, the glitch would still make it
in its own way, you just don’t know him well ;)

So, you couldn’t tell me earlier? While the diagram for the ports was being redone.
No, I can’t do that - and how can I support the clock now - click in the config with the subject interface?

Personally, I am for the standards that have already been established and embodied in
circuits/boards, that is, for the Pros. But there is no diagram, and it is unlikely that this
option will not conflict with the Pentagon ports.
What are we going to decide, how to work with the subject in a more normal way?

s: since everything is not so with Pro, maybe you can give a description of how to pester the clock?

With the best, Denis.

KC> Born to crawl, he cannot fly...
:) Exactly!

KC> With tears in my eyes, I look at the screw while “compacting”
KC> after “killing”
KC> read packets. I just feel sorry for him (the screw).
The ZED sits on the ramdisk for a surprisingly long time!

AI> Well, who has weighed themselves down with them (will weigh themselves down)? so far no one
AI> has found errors or omissions in the description, and from this it follows
AI> that either no one has read it (the description) or it (cmos)
AI> is no longer needed by anyone, damn it.

There are errors/omissions - I compared both versions of the diagrams (before and after
altering the ports), it turned out that in the second diagram The address and
data strobes signals have swapped places. Who knows which option was correct,
so I’m trying to find the document for that little watch.

With the best, Denis.

KC> With tears in my eyes I look at the screw while “compacting”
KC> after “killing”
KC> read packets. I just feel sorry for him (screw).

AI> I have a mouse and, accordingly, I also have 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.
Yes, I understand! You already have a clock in your CPU/Me. But
as far as I understand, the data is stored there inconveniently - they need to be re-encoded every time. You've already changed your ports. Redesign the data storage format. Get yourself a program that will convert data in hours from CPU/M to Glitch and back. It's not difficult for you. Or can you prove that the Profako standard is
more convenient?

Hello, Denis!

21 May 98 Denis Dmitriev, hoping that Andrey Isaev would read, wrote:

DD> No, I can’t do that - and how can I support the clock now -
DD> in the config, click the subject interface?
That’s it, guys, stop arguing. There is already a FAQ about this watch on ZX_Serwer.

DD> Looking for errors/inconsistencies - I compared both versions of the circuits (before and
DD> after
DD> port modifications), it turned out that in the second circuit the signals
DD> address and data strobes swapped places. Fuck
DD> knows which of the options was correct, so I
DD> am trying to find the document for that little watch.
You don’t have to look, the second version of the scheme is correct, we checked it together with Gluck
and independently of each other. But there are omissions in the description:(

Well, if you really want to find a document on the chip, then I’ll give you a hint: Radio magazine number
12 for 1995 there is a description there, but it’s incomplete.

RM> Yes, I see! You already have a clock in your CPU/Me. But
RM> as far as I understand, the data is stored there inconveniently - they
RM> need to be re-encoded every time.
Yes, it’s necessary, but it’s not as complicated as Gluck described it.

RM> You’ve already changed the ports for yourself.
Well, you’ve changed it, and even then only incompletely

RM> Change and
RM> the data storage format. Get yourself a program that will convert data in hours from CPU/M to Glitch and back.
So what? Should I run it every time as soon as I want to get into CP/m or
back? Isn’t it easier to initially store time the way it’s done in Pro?
RM> It’s not
RM> difficult for you. Or can you prove that the Profakovsky standard
RM> is more convenient?
Maybe it’s more convenient, at least I don’t see any difficulties in using the
Profikovsky standard.

Well, in general, you do as you want, I’m already used to editing everything on my own watch, so
what if the program for me If you like it, she will definitely go under the knife.

DD> config with the subject interface click?
I don’t even know :(
DD> Personally, I am for the standards that have already been established and embodied in the
DD> circuit/board, that is, for the Pros. But there is no circuit diagram, and it is unlikely
DD> this
DD> option will not be with Pentagon ports conflict.
DD> What are we going to decide, how to work with the subject in a more normal way?
The only request is to store the time in the clock not in binary decimal form as
Gluck suggested, but simply in binary, and then making it work for
Pros will be a matter of minutes, it will be necessary to change the port addresses, and
the time setter for the zed can be used. (c),a
ld b,#df
ld a,#20
out (c),a

After this, port #00ff is an address register, and port #00df is a data register.

DD> So, it worked out for me :) (by the way, have you finished it yet?)
RM> And it worked out for me, but I still process the written letters with PKT_corr
RM> before sending them. For packing in two
RM> bags. Now, if only they could process ZED’s jujuks
RM>...

I can congratulate you. Uses via standard #3d13, on Scorpio
the 8th bank is not touched, i.e. It should work for you without problems. The only
thing is that I don’t know whether the memory test
works on Scorpios (there’s nowhere to test), but it seems to be written correctly.

I’m sitting in it, in the subject, and it’s really nice! And you don’t need to search for all sorts of suspicious questions, everything is already in the memory ;)

maybe I should change my mind and, with the permission of the Moderator, throw the subject into the echo? there will probably be 60 kilos in one zip...

The only thing that sucks is that the files from the old ZEDs will not work - they
need to be improved a little.
Actually, the improvement is that in all files
of the package CALL #3d13 is replaced by CALL #6000.
If everyone can create it, then all I have to do is throw it only
2Kb of the cache file itself...

With the best, Denis.

Hello, Denis!

25 May 98 Andrey Isaev, hoping that Denis Dmitriev will read, wrote:

AI> Well, if you really want to find a document on the chip, then I give
AI> a hint: Radio magazine number 12 for 1995 there is
AI> a description, but incomplete.

A very complete description in Radio Yearbook 1989.

Tue May 26, 1998, Denis Dmitriev squeezed the keyboard, hoping that the following words would reach Roman Milukov
:

DD> There’s also ZxPower3 to finish, one of these days it’s coming out, damn it.

It’s crazy! :) What days?

Tue May 26, 1998, Denis Dmitriev squeezed the keyboard, hoping that the following words would reach Kirill
Chubenko:

DD> maybe I should change my mind, and with the permission of the Moderator, throw the subject into the echo
DD>? there will probably be 60 kilos in one zip...

Ok. I allow it. Be sure to indicate that this is an update to ZED 1.02b (the author must be
honored!)

Of course, you should definitely change your mind, otherwise why bother teasing everyone?

DD> If everyone can create it, then all I have to do is throw
DD> only
DD> 2Kb of the file itself for working with the cache...
Well, personally, this will suit me quite well.

DD> I can congratulate you. Uses via standard #3d13, on
DD> Scorpio
DD> 8th bank is not touched, i.e. It should work for you without
DD> problems. The only thing
DD> is that I don’t know whether the memory test
DD> works on Scorpios (there’s nowhere to test), but it seems to be written
DD> correctly.

Throw it in, I’ll check it, both for memory and for working with the screw.

DD> I’m sitting in it, in the subject, right now nice! And you don’t need to flash any
DD> suspicious dossier
DD>, everything is already in the memory ;)

Congratulations.

AI> Well, I threw it to you.
sorry, I probably missed it. I've been having troubles with netmail for the last week
:(

Best regards, Denis.

DD> sorry, I guess I got it. I've been having troubles with netmail
DD> for the last week :(

Denis, why do you need zed.uude? Imho, no one uses it anyway! Personally
I use your 0.0000002, first ripping out the sections with ZED and arranging them in order. Sometimes is the right one.
Take yours, better finish it! Make it “two-pass.” Let it first scan the mail database, remembering the location of the sections and display a list of files in the folders, and then unlink the file to which you show it - almost like in ZED. You can
sharpen it from ZED. started.

RM> Take yours and finish it! Make it “two-pass”.
RM> Let it first scan the mail database, remembering
RM> the location of the sections and display a list of files in the folders, and
RM> then unlink the file you show - almost
RM> like in ZED. You can sharpen it so that it can be launched from ZED.
And be sure to check the checksum.

Once on June 9, 98 Roman Milukov sent a
letter to Denis Dmitriev:

RM> Denis, why do you need zed.uude? Imho, no one uses it anyway
RM>! Personally, I use your 0.0000002,
RM> by first ripping out the sections with ZED and arranging them in
RM> order. Sometimes it’s true.

[skip]
RM> sharpen it so that it can be launched from ZED.

Maybe it’s better to finish Melon first? IMHO a more necessary weight.

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

Hello, Denis!

12 Jun 98 Denis Dmitriev, hoping that Roman Milukov would read, wrote: