Small update in BIOS

Now, if anyone remembers, I was going to leave a call to the drivers directly
at the address. Problem solved! It is now possible to call the driver by number.
The problem was solved by changing the method of calling functions. Now functions
not by setting the function code in the C register, but by setting the function code
after the restart command (just like errors were made in BASIC). Thus, I took the last free restart to call drivers. The
function code is the driver number (0-127), and the driver function code is C. That's all!
Programmers should obviously feel better after this. Yes, by the way, how do people
look at being even more perverted and writing driver function code after a restart? Something like this:
rst #28
db 1 ; driver number
db 2 ; driver function number

This is sometimes more useful, and sometimes not. For example, this method saves registers and memory, but takes a little more time.

With respect, Roman aka Megus of Brainwave Association.

[Team ZX-Spectrum] [Team Agatha Christie] [Team Metallica] [Team Iron Maiden]

Hello, Roman!

29 Jun 98 Roman Petrov, hoping that everyone would read it, wrote:

RP> drivers too
RP> after the restart should I write? Something like this:
RP> rst #28
RP> db 1 ; driver number
RP> db 2 ; driver function number

RP> This is sometimes more useful, and sometimes not. For example
RP> this method saves
RP> registers, memory, but takes a little more time.

I think it is very important to save _time_! IMHO.

All the best.
Roman.

RM> I think it's very important to save _time_! IMHO.
It seems so to me too, because at the moment the function number is
transmitted to the driver in register C. So, calling functions, and calling the
driver itself are quite cunning procedures, and also quite
slow. But no matter, no one will ever forbid you to call the driver
directly by address (there are all the means for this), as well as
any BIOS function, the address of which is also no less easy to obtain.