ZED1_02cache

Here, I’m throwing the subject into the echo, as I once promised :)
the whole package is in two zxzip archives (required), without help files (I can send
separately if you really need it)
(CMOS watches are not supported because I haven’t gotten around to it, maybe someone
will do it ;)

Due to the lack of various hardware in Kharkov, the following questions are of interest:

- Does the subject work on Scorpios, and does it see memory above
256k? and below 256k? ;)

- does the subject work normally on a Pro with a lot of memory and a non-linear
page arrangement?

- are there any other glitches besides those described in the ZeadMe.W file
and under what conditions do they manifest themselves?

Those who wish can add to the list ;)

Now a little nonsense about any rights to authorship.
when the subject was made for cache, we thought mainly about ease of use, not about rights. I am not attempting any authorship/co-authorship, but if anyone does not agree with my point of view,
they can erase the subject from all available drives and call me a malicious hacker, I will not be offended ;)

Well, I would like to take this opportunity to convey a huge thank you to Rick Murray
for -ZED- !!!

With best, Denis.

Sorry, the subject didn’t fit into two archives, so there are already three archives!

by the way, if anyone likes it, I set up the colors in the subject config...

With best regards, Denis.

DD> - does the subject work normally on a Pro with a lot of memory and
DD> non-linear arrangement pages?
NO! I have 576kb of memory and the subject defines 640kb in total and 576
for the RAM disk

And how will it cooperate with E. Miluna’s tosser?

Sincerely, Andrey.

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

DD> sorry, the subject didn’t fit into two archives, so there are already three archives!
Well, it’s okay, we weren’t offended :)

DD> by the way, if anyone likes it, I’ve set up the color subject in the config
DD>...
By chance you don’t have a B&W monitor? ;)

By the way, why not reconfigure them?! (sorry, my eyes are not friendly with your flowers) ;)

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

[skip]

DD> - does the subject work on Scorpios, and does
DD> see memory on them above
DD> 256k? and below 256k? ;)

It works, sees 176k.

DD> - are there any other glitches besides those described in the file
DD> ZeadMe.W
DD> and under what conditions do they manifest themselves?

Рpppppppppp!!!!!! (menacing growl).
Why is the “ytsuken” keyboard displayed in life?!?!?!
(the only thing I changed was zed.sets, zed.book, zed.areas, cio.sys, I installed my own
zed.kbd2)

DD> Those who wish can add to the list ;)

Again “ppppppppp” ;).

AI> Do you happen to have a B&W monitor? ;)

Yes, I didn’t like the colors either. IMHO the original ZED ones are better, I
only changed the color for the kludges from blue to purple and that’s it, I
like the rest.

And I tried to use the subject... With a 5.12F RAM disk, it seems to be more convenient. Maybe I
missed it?

All the best.
With respect, Roman Milukov.

A very unpleasant glitch - the keyboard does not switch, life is in the "ytsukeng".
It's not in order, I can't work in it.
From the files that were in the package I changed: .sets, .kbd2, cio.sys, & *.book's
Maybe because of .sets? Because given what it was, you can’t change the color...

[skip]

KC>
KC> A very unpleasant glitch - the keyboard does not switch, due to
KC> life in the "ytsukeng". It's not in order, I can't work in it
KC> I can't.
KC> From the files that were in the package I changed: .sets, .kbd2, cio.sys,
KC> & *.book's
KC> Maybe because of .sets? Because given what was there, it’s not
KC> to change the colors...

No... it’s because of cio.sys, here a new font flew by, tried to replace it, instead of
yaverty yatsuken =(

Sorry, they brought fresh beer...

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

[skip]

GK> No... it's because of cio.sys, here the new font flew by,
GK> tried to replace it, instead of
GK> yaverty yutsuken =(

Hmm... Why then in the old (not patched) with the new font - everything is ok? If
it was glitchy - I I wouldn’t throw it to Roman.

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

It's funny with this... If you put the old cio.sys in a mushy zed, then you have yaverts for life, if you put a new cio.sys (which I like better) in a mushy zed, you have yatsuken for life...

2DD: How do we understand this? ;)
I.e. the settings simply don’t affect anything...

KC> Fun with this... If you put an old one in a stuffed zed
KC> cio.sys, then we have yaverts for life, if we put a new
KC> cio.sys in the quilted zed (which I like more
KC>) - we have yatsuken for life...
Well, in this situation, you can go two ways: insert the 'yaverts' sign
manually, it is there right after lies as a font, or make a cached one from the standard file
'zed.C'.

KC> 2DD: How to understand this? ;)
KC> Ie. the settings simply don't affect anything...

As far as I understand, in cached ZED you can't change individual files without
altering them first. The modification is not complicated, I think Denis said something about this
but I forgot.

All the best.
Roman.

AI> Well, in this situation, you can go two ways: substitute
AI> the 'yaverty' sign
AI> manually, it is there right behind the font, or make a cached one from
AI> a standard file
AI> 'zed.C'.

To my deepest regret - I am not a coder, and I cannot do this myself I can...
That's why I'm asking/telling. If you do, I will say thank you.

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

RM> As far as I understand, in cached ZED you cannot change
RM> individual files without
RM> first altering them. The modification is not complicated, it seems,
RM> Denis said something about this
RM>, but I forgot.

I said, but we need to redo those overlays that work with the disk, and what
the screen has to do with it is not clear.

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

Hello, Kirill!

30 Jun 98 Kirill Chubenko, hoping that Roman Milukov would read, wrote:

KC> I said, but we need to redo those overlays that work
KC> with the disk, and what the screen has to do with it is unclear.

I don’t know.

I’ve been cruel here several times already Broke off with ZED+ramdisk. :( I was thinking about switching to a cached one, I carefully read the accompanying text from Denis and abandoned
this idea. I switched to a regular ZED and a regular disk. Brake - where can I go! :(
The fact is that lately we have started playing around with electricity -
turning it off at the most inopportune moment. :( Just imagine: I wrote a bunch of letters (I pored over for a long time), then bam! The light went out - all the work was down the drain...

It is necessary that ZED immediately writes down every written letter to a disk (magnetic) (on the
host).

All the best.
Roman.

KC> To my deepest regret, I’m not a coder, and I can’t do this myself
KC>... That’s why I’m asking/telling. If
KC> you do it, I’ll say thank you.
I’ve already done it!
2All: can I post it here?

AI> Already done!
AI> 2All: can we get him here?

Babe!!! Come on!
However... I don't use it - I described the reason recently. :(
Can you help me?..

All the best.
Regards Roman.

KC>
KC> Hmm... Why then is everything ok in the old (not covered) with the new
KC> font? If
KC> it had been glitchy, I wouldn’t have given it to Roman.

Hmm, I had this glitch with the new cio.sys with a non-cached
subject (the Ytsuken layout was not disabled). Perhaps my original ZED1.02b itself was buggy?

With best regards, Denis.

RM> separate files without first altering them.
RM> The alteration is not difficult, it seems Denis said something about it,
RM> but I forgot.
In executable files (with start address 25200, in dos.sys)
change CALL #3d13 to CALL #6000.
With the zed.C file it’s a little more complicated, I don’t remember myself.
But: glitches with layouts did not appear from caching, it’s just
I had the original ZED with these glitches (by the way, how can this
be? After all, ZED1.02b is the one you once sent me, but cio.sys
doesn't work with him...)

With the best, Denis.

DD> Hmm, I also had this glitch with the new cio.sys with
DD> a non-cached
DD> subject (the Ytsuken layout was not disabled). Perhaps
DD> me
DD> the original ZED1.02b itself was buggy?

Maybe everything is ok with me. (in the old one)

KC> It works, sees 176K.

DD> :-?
DD> Do you have exactly 176K? or is this a glitch?

Hmm... I have 256, but probably you don’t count all sorts of system pages (like 5,
8, etc.)? If you think so, it’s a glitch.

KC> Рpppppppppp!!!!!! (menacing growl).
KC> Why is the “ytsuken” keyboard set in life?!?!?!
KC> (the only thing I changed was zed.sets, zed.book, zed.areas,
KC> cio.sys, installed my zed.kbd2)

DD> ^^^^^^^
DD> it’s because of this file glitch with the layout. I didn’t delve into this
DD> issue, but there were corrected versions of cio.sys
DD> (the one that flew in the echo, just with this glitch).

We’ve already sorted that out.

DD> In any case, in the subject package there is my configuration,
DD> which "yaverts".

Yeah, and with the old cio.sys.

Thursday July 02 1998 00:39, Denis Dmitriev ─── Andrey Isaev:

AI>> How can I start the tosser E Miluna? or will we now have
AI>> a mountain of standards for zed overlays? Is hardware chaos
AI>> not enough for you?
DD> Unfortunately, I haven’t seen this tosser, so I can’t say anything
DD>.
This is, IMHO, about the fact that my tosser works with #3D13 and uses the entire 128th
memory. It is absolutely “transparent” for ZED, i.e. as if it is an upgrade.

Good luck! Evgeny.

■ The night is shorter than the day... The day will kill me... The world of illusions burns down in it. (C) Aria.

DD> I can’t say
DD>.
???!!! So they threw it three times in zx.spectrum and after that you say that you read all the mail ;) And the tosser, by the way, is steering, imho if you cut off the use of 128th memory in the cached zed, then it will work.

DD> Clearly, that means the subject failed.
DD> Well, then I apologize to everyone for whom it caused a bunch of
DD> glitches...
The subject was a real success! Now we just need to remove some glitches and everything will be ok.

5 Jul 98 Denis Dmitriev, hoping that Roman Milukov would read, wrote:

DD> In executable files (with start address 25200, in
DD> dos.sys)
DD> change CALL #3d13 to CALL #6000.
DD> With the zed.C file it’s a little more complicated, I don’t remember anymore.
DD> But: glitches with layouts did not appear from caching,
DD> just
DD> I had the original ZED with these glitches (by the way, how
DD> is this
DD> maybe? After all, ZED1.02b is the one you gave me once
DD> sent it, but cio.sys doesn’t work with it...)

Ah-ah!.. Everything is clear! After that (it was a long time ago) Rick admitted that the file
zed.C was buggy and threw a fixed version into ZX.SPECTRUM!
When I replaced this file (and not cio.sys.C!) everything was OK!
And you, apparently, always used the corrected (probably Z-MAN) cio.sys.C! So
there is a discrepancy!
Catch the parcel with soap.

DD> was the original ZED1.02b buggy?

Denis! Did you even change your zed.C file when Rick (quite a long time ago) threw it into
zx.spectrum? Or did you just have a tricky cio.sys.C and the situation with it
was normal?

2 Jul 98 Denis Dmitriev, hoping that Roman Milukov would read, wrote:

RM> And I tried to use the subject... With a 5.12F RAM disk, it seems
RM> it’s more convenient. Maybe I missed it?
DD> That's right, it will be faster with a ramdisk.
DD> It’s convenient to sit on the subject when there is no ramdisk, and even then,
DD> helps
DD> except for wear-out floppy disks ;)

It is necessary that a freshly written letter be recorded on a magnetic disk! And then when
the light happens to be turned off - such a bummer!.. :(

DD> was the original ZED1.02b itself buggy?
Most likely, a long time ago Roman told me about this, that they say there was such a glitch in zed, but then Rick fixed it and threw the corrected zed.c file into the echo. Or am I confusing something?