again about cmos

Despite the warm beer, Hello, Tim!
There are a few questions that need to be clarified...

RM> Few people have already assembled the scheme, there are none in Donetsk yet
RM> not a single one, _yet_!

As I have repeatedly stated, I work for myself, so
this is not an indicator for me.

RM> The spec does not have as much memory as more
RM> sophisticated cars! Autoconfig should be done once and
RM> no longer take up space! Extra drivers are thrown away!
RM> If you want, save the installation.

Not relevant, but since we're talking - the driver takes about 1 hour - I don't think it's worth saving on this, but if necessary, you can erase the unnecessary driver.


RM> Why support new ones if the old ones are ALREADY SUPPORTED????
RM>
RM> Ah-ah! Where? What if someone wants to have both
RM> and so that there are no conflicts? You are the author - rewrite
RM> the diagram in a way that is more convenient for the people, they don’t mind!

You apparently don’t imagine the process - if you want to have
both - set #eff7 (extended screen) to selection
signal from the megascreen - if the clock is on - there is no access to
control of the extended screen - NO CONFLICTS!!!

RM> Due to the fact that Zonov is not compliant, and there are troubles, isn’t there?
RM> you have a direct connection with the user, take into account his interest!

Zonov pursues the correct policy - ifdone, there can be no reverse
way, besides, it has mass production (in relation
to this situation).

RM> Because you don’t want the scheme to be changed
RM> by someone else! Take off the fur coat from your master's shoulder :), perhaps
RM> give us what is interesting and necessary for us!

For God's sake! If the decision is successful, I myself will someday redo it myself. In the meantime, I'm not going to do this
and I'll make a new version of the ROM for my watch, and the main
emphasis will be placed on the widespread use of the hardware
excesses of my computer.

RM> and on P.. and a... they are not there???
RM> Aren't they a glitch, with a bunch of patches and bloated memory for
RM> this?

No, everything is clear, but what exactly...

RM> Apparently, nothing will change my opinion...
RM> It seems like I have nothing to do with it ;)
RM>
RM> Hello! :) And who then - “what”, the moderator?
RM> :)

This topic is being discussed by all and sundry - starting with Isaev,
who will NEVER set a watch for himself (he
has one in his profession) and ending with me :) - by the time
my inclusion in the conversation I got the impression that
I don’t seem to and.

RM> Yes, since I’m here, I learned that I’m writing a game
RM> “Zhirinovsky” and I’m having troubles with the muse, and dear TK
RM> can help me - is this true???

At the moment the project is hanging in the air...

RM> P.S. Has any of the reals done the layout in the evil grandfather
RM> or is everyone still struggling???
RM>
RM> What's not to your liking?

The yaverts here are VERY bad... punctuation marks on combinations
... delusional....

And my specialty was meant - I graduated from the IEK in
specialty Automation of production processes in the energy sector,
formerly Relay protection and automation of power systems, now
working in rotten office electrician (I turn out light bulbs :))

Now about the rules... Cool point about firmware...
I'm not going to do that. I don’t think that I will give a new version to anyone - in light of the latest regulations - I don’t like it when they get into my code and steal my thoughts...
I heard that somewhere they write their own firmware :)) God bless them!!!
If I work for free, I should get at least some
pleasure from the work???

In general, I am for healthy competition... Deadline for completing the work?:)
By the way, I sewed for everyone for a reasonable fee - 20p, and Isaev
even refused to supply beer... Is this kind of work worth
a bottle of beer? That's right Mednonogov Slava put his money on everything.
Here the people love freebies; and when Isaev and I parted ways
on the line of the PZ - this is when he said that the work of sewing
more than the work of my head...

Sincerely, Renat.

P.S I think the topicзакpыта???

RM>
RM> This topic is discussed by all and sundry - starting from
Not all and sundry, but those who need it and are interested.

RM> By the way, I sewed for everyone for a reasonable fee - 20p, and Isaev
RM> even refused to supply beer... Such work is worth
We have already discussed everything about beer (remember XAS).
RM> bottles of beer? That's right Mednonogov Slava put his money on everything.
RM> Here people love freebies; and when Isaev and I parted ways
RM> along the line of work - this is when he said that the work of stitching
RM> is more than the work of my head...
^^^^ and that’s exactly the same as yours? Apart from you, no one else took part in its writing?
Maybe you won’t raise this topic again, we seem to have already discussed everything
related to this issue and everyone has their own
opinion.

Sincerely, Andrey.

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

RM> Isaeva,
RM> who will NEVER set a watch for himself (he
RM> has them in his professional life) and ending with me :) - by the time
RM> of my inclusion in the conversation, I got the impression
RM> that
RM> I had nothing to do with it.
So, I don’t understand yours offense. We are talking, if you don’t understand, about
developing by joint efforts the most convenient
CMOS port numbers for ANY computer.
So that they don’t conflict with existing hardware! And, as far as possible, with
the newly created
DISMASTER was invited (or he himself decided after seeing the diagram - it doesn’t matter)
to support the clock in Melon. Moreover, this has long been requested in the mailer! Support
only Skoppovsky’s smook? What about other computers? There were no clocks at the Pentagon yet.
And so, in order for the Pentagon to immediately include clock support in the mailer (first
installing them for itself, obviously) DISMASTER and asked the people in this echo FIRST to discuss
the new addresses they proposed. Can anyone suggest something useful?

RM> Now about the rules... Cool point about
RM> firmware...
RM> I'm not going to do that. I don’t think that
RM> I will give a new version to anyone - in light of the latest regulations - I don’t
RM> I like it when they get into my code and steal my thoughts...
And who stole what from you?!!

RM> I heard that somewhere they write their own firmware :)) God bless them!!!
Thank you. That's why they write,that no one will break or remake yours. And the idea of ​​placing a useful program on the zero page has long been in the air, and there have been some works in this direction. Another thing is that YOUR firmware pushed coders to write their own firmware (not only for themselves :). Well, you categorically refused to change anything there. What is incomprehensible here?

RM> If I work for free, I should get at least some
RM> pleasure from work???
An interesting idea, very fresh! :) So, did you specially make _such_ letters
green and bright blue in your bottle?! Do you enjoy it when others have difficulty reading them? Very fresh! :))

RM> In general, I am for healthy competition... Deadline for
RM> works?:)
We'll see.

RM> The yaverts here are VERY bad... punctuation marks on combinations
RM> ... crazy....

Connect the PC keyboard, fortunately there are a lot of circuits... And go to the main one, except
spek, standard.

RM> And my specialty was meant - I graduated from IEC in
RM> specialty Automation of production processes in the energy sector,
RM> former Relay protection and automation of power systems, now
RM> I work in a rotten office as an electrician (light bulbs I'm turning it inside out :))

Wow! And here we are indulging in buns... :) (C) Carlson

Well, I’m a regulator of REA and instruments at a dying military plant...
I don’t go beyond wiring boards and adjusting various little things in everyday life, at
there’s enough of this at work, it’s already dazzled in the eyes. At home I'm drawn to the computer :)
I remembered the old joke about "machines, machines, machines..."

RM> Now about the rules... Cool point about firmware...

Don't touch the rules! This is sacred :) I will upvote and swear with soap!

AI> ^^^^ and what exactly is yours? Apart from you, no one else took part in its writing?
AI> Maybe you won’t raise this topic again, we seem to have already discussed everything that
AI> concerns this issue and everyone remained with their own
AI> opinion.

Guys! No hassles or misunderstandings, pls.

RM> Now everything is clear! Yours - so yours.

As I already stated - if I redo the circuit, the software will be
rewritten, or I’ll do it right away with autoconfig - so that I
don’t have to change it later.

RM> So, I don’t understand your grievances. We are talking, if you don't
RM> understand, about working together to develop the most
RM> CMOS port numbers convenient for ANY computer. So that
RM> do not conflict with existing hardware! And, as far as
RM> this is possible, with the newly created one.

In my opinion, the whole problem is in one element ll1, which they STRONGLY
don’t want to include in the #eff7 scheme - I’m already tired of shouting
(I’ll go lie down :)) that there will be no conflicts.
Perhaps the point is that it is not known how it works (or
will work :)) clock driver - if the clock is not found,
there will be no calls to it (this is already done in the ROM).

Yes, I haven’t forgotten yet. Even in the Pentagon there is no #fd port. the address
#fd implies decoding one a1 at a time - no one has ever done or will do this. Even in the stump,
a1 and a15 are decrypted, but using out (#fd), the a byte will be written
to port #7ffd if the 7th bit is reset in a. If you didn’t know -
command out (#xx), a puts the contents of a on the high half
of the address bus and throws out a at the received address.
And so that the program does not crash on Scorp and the like, where
there is a port addressed by a14 and they ask you to set the 6th bit
inand before being released into the port #fd - here are the programs that breed, which
do not want to work on computers with more than 128 memory on the port
#7ffd.

RM> DISMASTER was suggested (or he himself decided to see
RM> the diagram - it doesn’t matter) to support the clock in Melon. Moreover, this
RM> has been asking for a mailer for a long time! Support only smuk
RM> Skoppovsky? What about other computers? At the Pentagon for now

What about ATM, where the clock is made on a single crystal?

RM> there were no clocks. And so, in order for the Pentagon to immediately include clock support in
RM> mailer (by first installing it for themselves, obviously)
RM> DISMASTER and asked the people in this echo FIRST to discuss
RM> the new addresses proposed by them. Can anyone suggest something useful
RM>?

It’s completely unclear (or the skis don’t work...) If you are supposed to work with two schemes (I hope no one seriously entertains
the idea of Scorpov’s clock on a stump?), then why not make
a third, in the form of a driver (outdated) or autoconfig?

RM> I don’t like it when they get into my code and steal my thoughts...
RM> And who stole what from you?!!

Not yet. But I didn’t see...

TK>
TK> Therefore, every ram climbs into a branded car and
TK> cripples it by inserting switches and other crap... But not

I hope this does not apply to me :)))

TK> it’s easier to foresee everything yourself, so as not to spoil the idea, eh?

I confess, I missed it then, but I don’t feel like catching up right now.

TK> Exactly... When the real thing... For yourself... And you’re the author,
TK> Aren’t you sorry that they’ll redo it? If they remake it successfully - all the glory
TK> is on their side, if unsuccessfully - everyone will say that the
TK> scheme is obviously wrong, that's why the programs are buggy!

It's a pity, but we have democracy - whoever wants to go where he wants.

Now about the matter. We'll have to hold onto the palm of the championship :)
address register (/as on the clock) - #bff7 - on the sample
a14 (previously a12)
data register - no changes #dff7 - a14
m/s sample - it was #fffc (damn! what's bad? :)) - #eff7 -
on the sample a12, a3, /iorq, - fed to the /c trigger -
from there to the sample 512vi1 /se, and to the signals /as, /ds
strobe through the addresses (see above). I lost the diagram :),
maybe I mixed up the addresses - I need to check. WHO IS DISSATISFIED?
Yes, oh #eff7. Due to the removal of #fffc as a class, its
functions are switched to #eff7.
d0 - perversion with the screen
d1 - blocking large memory
d5 - control /dos
d6 - locking ROM (rom disk)
d7 - clock

RM> 1. There is absolutely no time with this feed

You’ll get used to it :)

RM> 2. The script is not ready

This does not mean that the project is hanging, is it not being developed?

RM> 3. There are not enough graphics

I have to draw...

RM> 4. There is no music at all.

Who to contact, I told you here.

RM> But in general the game is written - even the internal language is written, which
RM> will control it. There is a primitive scenario - you can already
RM> play - but there is still not enough action.
RM> In connection with the latest antics of V.V. I'm thinking of radically
RM> changing the plot - Homer Simpson in Russia.

Well, it hangs - hangs :)

Yes, I see. I'm like that myself. But it’s necessary!

RM> Now about the matter. We'll have to hold onto the palm of the championship :)
RM> address register (/as on the clock) - #bff7 - on the sample
RM> a14 (formerly a12)
RM> data register - no changes #dff7 - a14
a13, probably? ^^^
RM> m/s sample - there was #fffc (damn! what's wrong? :)) - #eff7 -
RM> on the sample a12, a3, /iorq, - fed to the /s trigger -
RM> from there to the 512vi1 /se sample, and to the signals /as, /ds
RM> with a strobe via addresses (see above). I lost the diagram :),
RM> maybe I mixed up the addresses - I need to check. WHO IS DISSATISFIED?
Me again! :) One bit!

RM> Yes, oh #eff7. Due to the removal of #fffc as a class, its
RM> functions move to #eff7.
RM> d0 - a perversion with the screen
It’s clear here, this is a “per byte attribute” for V.M.G.

RM> d1 - blocking large memory
But here it’s not! Here is the control of the “512 points per line” mode!
Please, change the blocking to another bit!

RM> d5 - control /dos
Can you write about this in more detail? Isn't it a secret?

RM> d6 - locking ROM (rom disk)
And about that?

RM> d7 - clock

RM> I said - do as you want. I suggested my own option
RM>(s)
RM>.
Thanks! I will forward this letter to DISMASTER and let him support me. Lock bit
"large memory",I hope you will transplant? Maybe on d4?

Hello, Renat!

28 Mar 98 Renat Mamedov, hoping that Roman Milukov would read it,
wrote:

RM> then there was no need to change it.
But the very idea of ​​keeping software in ROM already implies frequent changes!
Software is being improved! (there is already a perfect 1.7) So autoconfig is
superfluous, it just takes up space.

RM> Perhaps the fact is that it is not known how the clock driver works (or
RM> will work :)) - if the clock is not found,
RM> there will be no calls to it (this is already done in the ROM).
Well... Very It’s unpleasant when the device is there, but the software doesn’t see it!

RM> to port #7ffd, if the 7th bit is reset. If you didn't know -
Knew! But “soft makers” sometimes really like to save money. :(

RM> What about ATM, where the watch is made on a single crystal?
It is, of course, difficult to support everything. Especially such perversions as ATM!
Scorpio is not far behind it in this sense imho, but it is very widely produced
(and is still, unlike ATM!).

RM> working with two circuits (I hope no one seriously
RM> admits
RM> thoughts about Scorpov's clock on a tree stump?), then why not
And I hope :)

RM> to make
RM> a third one, in the form of a driver (outdated) or autoconfig?
Extra. problems...

TK> We sell ready-made boards - awesome! With two
TK> layouts, which can be changed if desired (RF2) and
TK> a bunch of bells and whistles. Zheka Safronov will tell you better. But the price
TK> is biting - 40 hryvnia - 120 rubles, rude.

This is very, very interesting - the amount will not stop me.
More interesting are the technical parameters and how I can
get it from free Ukraine to free Russia.

1. It understands _any_ at-clave / Kovalevsy I wrote somewhere that not everything fits the Scorpov controller - does it not suffer from this?

2. How does it work / without /wait, /nmi - or does it still slow down?

3. A stupid question, but still there was no answer - #fe emulates?

Sincerely, Renat.

RM> This is very, very interesting - the amount will not stop me.
RM> More interesting are the technical parameters and how can I get it
RM> from free Ukraine to free Russia.

RM> 1. It understands _any_ at-clave /Kovalevsy wrote somewhere,
RM> that not everything fits the Skoropov controller - does not
RM> suffer from this?

There is a PC keyboard controller on the board, in theory it can eat anything.

RM> 2. How does it work / without /wait, /nmi - or whatever is it slowing down?

Question for Safronov.

RM> 3. Stupid question, but still there was no answer - #fe emulates?

Same there.

Hello, Roman!

30 Mar 98 Roman Milukov slammed his fingers in the hope that Renat Mamedov would read about

The controller that I have #fe emulates perfectly, without glitches. Absolutely _all_ AT keyboards are suitable (they use a PC microcontroller).

Come on, Renat, come on!
[Team thief Alos MUST DIE!]