Tomorow - Reveals information about planned projects.

byJIb|sdc

bios

   There was a lot of discussion in the news about wasps. Me too
when I was still a mom, I firmly believed that it was simple
it is necessary to make a speck axis. I was a fool. Having learned
Dehu Kodu I realized that not everything is as plastic as
it seems. Z80 is far from 3GHz percent, the drive is far from HDD,
128Kb is far from 1GB, and AU is not SB8.2. I'm not talking about robopm
Count.  Folks, think the fuck over! at this stage it’s
developmentm!, its axis because its use will lead to
loss of prog speed and dulling of coders(!). Even
opehtupobatb it under 1m, 7MHz, HDD it will not give results.
   The most surprising thing is that some people simply
they write boot extensions, but they believe that they are screwed
rulnum axis. People who are really doing something serious
slow down (no offense), ChaOS, DoorS, BeeOS. Honestly
Not one of them impressed me, but only confused me
its ckopoctbm.Yes, multitasking is not bad, but
only if it is acceptable in terms of speed than the z80
basically cannot allow it (output z80H2OMHz).
   I'm not against the OS, I just think it's necessary
first I started to hit the iron on the steering wheels, and only then think about the OS
   Having realized all this, I had one idea, namely
play with the spec BIOS. Yes, the speck doesn’t have a billion VU, but
nevertheless, this will make it easier to hang all sorts of rules on the Speck and
will make it easier to write an OS for steeringspeck.
   Its main concept is to make it
open to any device based on zilog codes. And
Naturally, if the axis is written for it, then on
will become absolutely open.
...[description]........................................
   In reality, this BIOS is a program for
installations, driver settings. The driver system is based
as follows: there are two types of dravaks:
1. Basic (keyboard, ram, VZU) through which he works
BIOS, and all programs can interfere.
2. Resident dravaks lined up in a chain and executed
every INT.
 Basic drivers cannot be deleted, only replaced.
   Resident dravaks can
install, remove, turn off, start setting up. Setting up
is carried out as follows: if at the beginning of the code
#ff is read, then the offset will be read
indicating the dravak settings program, that is, the program
the settings are written by the author of dravak himself using
BIOS functions are included in a small GUI.  Prog
event processing and the chain of dravaks will be initially
sit on some rst echo. In the future it is planned
make an interrupt controller for NMI (after all, it
don’t care), and hang it all on him. It’s also planned
add-on for emulating some devices based on others in
in the form of a buffer of ports from 0 to 65535 (on SRAM-21000).
   Thisthe program will be in a version only for a cache volume
at least 1bKb. The program will absolutely not use
undocumented z80 commands.
   At the moment, the test version has already been released, but sooner
In total, it will be rewritten in order to optimize
time and volume, especially since it is present in the test version
program for saving trdos tasks (up to 7) in heimem,
which I will remove (due to uselessness(?)).
   Wait for the release! And worry about it!