Reader02 Re:here, I cooked it up over the weekend...

RM>> Works under SPRINTER-1 & 2 firmware. Maybe on
RM>> others...

AG> I have a new firmware on Sprint, so it was not possible to evaluate
AG>. Ivan Makarchenko promised to make a software change to the contents of the ROM from the setup in the near future. Therefore
AG> IMHO it is advisable to indicate the release date of the firmware
AG> until they come up with the idea of ​​assigning names to them, which would be
AG> more convenient.

I guess the reason for this... The fact is that according to
the description of the BIOS functions, it is not recommended to use old ones -
and there is one there, #80 is called. It is used to open
different text modes... I don’t know why it is not recommended
for use - it is quite convenient...

And as for release dates - there is a BIOS function that reports
the current computer configuration and BIOS version in a string. But, unfortunately, on mine (due to the antiquity of the BIOS) it doesn’t work. That's why I didn't
do it...

And changing the firmware can be as easy as shelling pears - connect it to RAM...
and the BIOS too... but programmatic changing the contents of the ROM
is not provided for by their design :)...

RM>> After loading, a list of files falls out on the 64*24 screen

AG> Two files were displayed and blue-violet ones appeared along the border
AG> stripes.

These stripes are a debugging action. If the BIOS returns
with an error or error situations occur- these stripes
and there is an attempt to go to the very beginning - to
reread the catalog... It’s okay - the test version
is forgivable :).
But why they fall out is the question... Did you slip him a
tyrdos disk???

More details about the symptoms - you can use soap.

This is the version of the investigation. I said.