#EFF7
ZXNet echo conference «real.speccy»
From Kirill Frolov → To All 15 August 1998
about #EFF7 and I decided to intervene.
├┤i Roman & All !
[...]
RP> Will All tell me the information about which devices are hanging on the Subj port?
RP> Which bits are responsible for what. I would be very grateful.
There is such an idea here - to make it possible to read what is written down.
There is a lot of hanging and the program can change without knowing what...
And what about what hangs - it seems like this: 0-multicolor, 1-512pix, 2-forgot
3-??? 4-gigascreen 5-??? 6-??? 7-hour blocking
3,5,6 - can be used for additional use. ROM and STAT.RAM, but
when installing them, it is absolutely necessary to read what is written
into the port, change it, write it back and nothing else! After all, there is
the opportunity to connect another ROM/RAM...
W!7h Be$7 W!$he$, FK0.
From Roman Milukov → To All 18 August 1998
KF> There is an idea here - to make it possible to read
KF> what is written down.
KF> It hangs a lot and the program can change itself without knowing
KF> what...
You're right. But this is only true for control bits of additional ROM/Stat.RAM. And for
the rest of the bits - the program knows what to change.
KF> And what about what hangs - it seems like this: 0-multicolor,
KF> 1-512pix, 2-forgot
KF> 3-??? 4-gigascreen 5-??? 6-??? 7-hour blocking
~~~~~~~~~~
7 - access permission!!! If there is "0" - the clock is not visible!
KF> 3,5,6 - can be used for additional use. ROM and STAT.RAM,
KF> but when installing them, it is absolutely necessary to read
KF> written
KF> to the port, change it, write it back and nothing else! After all
KF> it is possible to connect another ROM/RAM...
Or maybe this could still be transferred to another port? - Grab one more bit of the address.
(as if everything was just decided by a toggle switch!)
All the best.
Roman.