▄████████████ ██████████████████████████▄
███████▒▓░ dEaD of IdeA ░▓▒███████
▀▀▀███████████████████████████ ██████████████████████████████
▄ ▄██▀
▀▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄███
▄▀ █ Bul(dez)er'StyDezCrew █
▄▀ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
In this article I want to part with
those ideas that he defended throughout
NI 12 numbers, namely - OS creation
for Speccy. Yes, when this canoe was conceived -
valac, I had little idea about coding
g, namely, that Z80 is not so powerful in
in terms of working with memory and that often
in order to win in speed you
complete the program, it needs to be greatly expanded
blow" (for example, I wrote the Flame effect:
the code itself took approximately 250 bytes, and the buffer
1bKb and all because it’s faster to click
lines by inc h, than somehow differently,
you save even on [call ret], you bet
[jp jp], it is clear that in large cycles). A
there is also OS, whichneed to inform about
each step and the dispatcher on NMI,which
eats up a mountain of bars. After all, the frequency of the trace is
niya NMI according to the principle described by me in
ZXT#12, may be much shorter
INT'a. It is clear that writing toys and
no one will have hemorrhages like this, but
In general, they are not written anyway...
Except for systems, and even then - why
multitasking for them? It will be honey
slowly and Speccy is not necessary, except for
2-3 prog (I was convinced from my own experience that
that parallel work is needed), but
they are underTR-DOS and accordingly in the new
AXES must die. The authors of many systems are
bent over, and shovel the code yourself and transfer
I consider running under OS complete insanity. And
why a new DISK SYSTEM for systems?
For example, all the systems that I use
fit on one disk + disk c
BGE3.05 and others for full operation
cgraphics. Taking into account all these
facts, we can say that OS for SPECCY
is not needed at all, and if it is done
Lana, then it will bend without even developing.
Now I'm inclined to believe that SPECCY
you need something like BIOS, since
The spec is done and a lot of bells and whistles have been done
and few people support them in their pro-
gah. And with the help ofBIOSthey can be configured
rypupobatb. That is,BIOS in my understanding -
will have to perform such operations
tions:
1.Full driver support for any
HARD. At the same time, the components of BIOS also
will work through drivers, standard
structures of which are almost developed.
2. Software emulation (substitution) is not
which bells and whistles based on others.
For example, y you AU-mouse, and the program is under-
Only the Kempston mouse holds it. You write
dravak, connect to BIOS, click
BIOS (with built-in STS (445 bb,
packed with RIP)), dig in the program and
you replace the dravak in the program withRET. Fit-
nav cells or something else in your own - and on
BIOS ring. BIOS, as planned, will be
use the same NMI on which they will hang
dravaks and polling for pressing the desired combination -
key functions: for example, B+I+O+S by which
we fall into BIOS. And the state
the program is completely saved and you can
fall back.
3.Memory management. Exiting to BIOS
can be cleared, forwarded, connected
any page from any address.
4.Full emulation of working with a screw and
RAMDISKat the launch level from themTR-
DOS programs that even use direct access to
VG. Difficult as point 2, but possible, not
pisishniks after all.
5. Uploading to state memory and
the program itself with the ability to
ment to start from the interrupted place. Work
melt c HRW1.03, and sit in memoryW.WORD,
SCR>TXT - click BIOS and we can continue
live work with the above according to your
Bor.
6.Manager of external drives with support
support of the catalog system (on wood,
of course). For example, on a floppy disk you can
leave 0 track as is, and 1 track
use to create subdirectories and files
structure >128, for screws, etc.
I think Chkb you can donate. At the same time
compatibility is not lost.
Regarding point 2. Software intervention
This can be minimized, namely:
set bChkb of static RAM and on OE
serve IORQ - and that's it! Can be tracked
all entries to ports and using the driver,
emulate some devices based on
others!
Maybe my ideas are similar to shadow
SCORPbut I haven’t seen it or used it.
If there is anything else you want to see in
BIOS'e, then send your wishes by re-
stock addresses.
- - -
Comments from DWT:
--------------------- My beliefs regarding OS and security
Deniya Bul(dez)er'a (who didn’t guess -
this ex. Killeram) is always seriously different
foxed However, at two points we always
were in solidarity:
1. A new OS is undoubtedly needed;
2. The OS will be complete.
But one day Kolya stunned me with a new
Tew that he completely rethought all his
ideas and made a radical reassessment
their views. What did it lead to - you
see in the above article.
To be honest, I didn’t even try
speakBul(dez)er'from his ideas, so
how useless it is... But I’ll move on to the cri-
tique.
Not OS insanity, butBIOS, described
fight.You say that the OS will not be supported
rye. But to use your BIOS
improvement is needed, which is definitely
no one will do it. I wonder what
will be most likely supported by: OS implementing
conflict-free support for everything that exists
the computer is initially configured
tion, or BIOS,implemented as a certain
shadow and even with hardware upgrades
who? Isn't this going to be another one?
Casher on some perverted hardware
level?
Plus, to ensure compatibility
ctumoctu with the operation of devices through this
brilliantBIOSrequired by programs
climb with STS... What they were leaving from - to that -
and they came... Isn’t it easier with the same
the most STSget into the program and proceed
then replace the necessary drivers? Strength and
this will require the same amount of energy.
Moreover, this kind of "replacement
box" (in yourunderstandingBIOS) with its
work clearly will not miss the opportunity c
to “conflict” with something, which is inevitable
be careful, because he will be “boorishly” “overwhelming”
"into software processes, disrupting
in this case both the stack and the registers.
In general, as it seemed to me, this
BIOS another "lift" for older OSs.
That is, a kind of plastic surgery,
not hiding, but slightly smoothing
flaws. A side effect is scarring.
behind the ears and changing the location of the bro-
vey:)))... Oh! Sorry - a lot of glitches and
inevitable conflict.
Well, finish these chaotic kommeh-
Taria still wants to be optimistic
note. I hope that in my attempts I will
to lize the new OS on the Spectrum, our
the horns will still meet... In the meantime, we find-
Dimcya in very different positions practically
ski on all questions...
- - -
Share your thoughts about the article