Sound on Spec. Re: GMX controller

Hello, Eugene!

12 Mar 98 Eugene Safronov, hoping that Roman Milukov will read,
wrote:

ES> If this board interests people, then I think
ES> it will not be difficult to arrange its serial production.
Figure it out yourself. How many CVs have you sold? This is approximately how much you can realistically sell GS. Imho.

ES> The device consists of 3 functional blocks:
ES> DMA controller, interrupt controller, DAC unit.
...
Judging by this information, the device is quite serious. The scheme is probably big.
That means riveting it yourself is not realistic for everyone. Although if we mass-produce a certain number of blank boards... It may very well be possible. What kind of stones are needed and
how many? I should have written about this right away.

ES> If anyone is interested in this development -
ES> write, I’ll throw some more materials into the echo on this
ES> occasion.
Come on, come on! A. Savichev sounddrive is going to sew up PLM for the accelerator, so maybe this scheme can be done right away?

All the best.
With respect, Roman Milukov.

TK> The DMA controller is exactly what you need for high-quality music,
TK> they wrote and write a lot about this in ZX.SPECTRUM. In addition, it can
TK> be used not for music...
I quote from the author:
1) It is possible to connect up to four input/output devices. These can be ADCs,
digitizers, multicards, video processors and much more. The main advantage
is that the processor is completely unloaded from I/O operations and waiting for results.
So, a hard drive connected via a PC multicard will send data
direct access and can be programmed using its own interrupt.
2) It is possible to cascade connect another DMA controller - plus 3
chips.
3) It is possible to transfer memory - memory.

RM>> Judging by this information, the device is quite serious. The scheme
RM>> is probably large. This means that riveting yourself is not realistic for everyone.
RM>> Although if you mass-produce a certain number of blank boards...
RM>> It may very well be. What kind of stones are needed and how many? It was necessary
RM>> to write about this right away.
In the next letter.

TK> In a minute there will be info - it’s a bummer for me, wait for Evgeniy Safronov :)
It’s not only a bummer for him - he just doesn’t have documents - I have almost all of it
:)

RM> ...
RM> Judging by this information, the device is quite serious. The scheme is probably
RM> big. This means that riveting yourself is not realistic for everyone. Although if
RM> mass-produces a certain number of blank boards... It may very well
RM> be possible. What kind of stones are needed and how many? I should have written about this right away
RM>.

Well, now I’ll correct my mistake. Here are extracts from the document:

[bit-bit-bit]

If you don’t have a turbo mode, then feel free to install 580VI53. In principle, they hold
3.5 MHz CLK (I checked 4 of them, they all held), but at the same time they heat up like
an electric stove. Yes, there is also such a thing as 1810VI54. They say it's the same at 5 MHz. I don’t know, I saw such a m/s once and then in someone else’s AON.

[bite-bite-bite]

Unfortunately, I don’t have a complete board diagram right now, so I’ll write another
microphone that I remembered - K1810BT37. I don’t know what this is, I’ll have it on hand
I’ll write out the diagram in more detail.

Hello, Eugene!

21 Mar 98 Eugene Safronov hoping that Roman Milukov will read,
wrote:

ES> If you don’t have a turbo mode, then feel free to install 580VI53.
ES> In principle, they keep 3.5 MHz CLK (I checked 4 of them,
ES> they all held), but at This heats up like an electric stove. Yes,
ES> there is also such a thing as 1810VI54. They say it's the same
ES> at 5 MHz. I don’t know, I saw such a m/s once and then in
ES> someone else’s AON.
I put this in AON, I know. This is not a complete analogue of VI53, if
VI53 is used for its entire architecture, then it cannot be replaced with VI54. Yes, in my opinion, VI53 will not go anywhere even in turbo. It's true that they get warm.

ES> Unfortunately, I don't have a complete circuit diagram of the board right now,
ES> so I'll write another little gadget that I remembered -
ES> K1810BT37. I don’t know what this is - I’ll have a diagram on hand
ES> I’ll write it down in more detail.
Uuu. This is more serious. This is the traffic controller. Very interesting. Yes, here another piece of information has come to light. My opinion is that this is what is needed. Make boards with a slot for a
PC multicard!

Hello, Eugene

21 Mar 98 Eugene Safronov was beeping in the hope that Tim Kelly would read about
Sound on Speck. Re:GMX controller, I read this and decided to answer:

ES> Well, CV also went to other cities... In general, so -
ES> whoever is interested in this board - write so that there is at least some information
ES>, how many people need this development at all.
Of course it is necessary, otherwise all sorts of kovoks are already sick of them, and GS is too expensive.
TK> I listened to the sound from

I just got the schematic for this audio device. I list all the stones used in it:

Microcircuit | quantity
========================
555ID7 | 2
555LP8 | 1
555LI1 | 1
555ЛH1 | 1
1810VT37 | 1
555AP4 | 1
555LA3 | 1
555ИР16 | 1
580VI53 | 2
555LL1 | 2
555ИР22 | 1
555TP2 | 2
555TM2 | 1
555ИР23 | 4
555TM8 | 1
555LA2 | 1
555TM9 | 3
572PA1 | 7
KR140UD20 | 4
========================
37 mikrukh in total. Impressive, isn't it?

By the way, about the boards. If anyone is interested - write, you need to know
how many boards are needed.

have a package, Roman, a package!

[Team Alos MUST DIE!]

RM> Ugh. This is more serious. This is the traffic controller. Very interesting. And then
RM> another piece of information came to light. My opinion is that this is what is needed. Make boards
RM> with a slot for a PC multicard!

What info? Where did it come from? Why did she influence your opinion so much? Kolos!
And the fact that the card has DMA, we said earlier, this is DDP.
Tell us, why is there a slot for a PC multicard? Perhaps we should contact the author
we need to reset the slot?
By the way, he connected the screw according to his original circuit a couple of days ago.
Now the software is writing, let's see what happens?..

Hasta la vista.
Tim Kelly

Hello, Eugene!

24 Mar 98 Eugene Safronov, hoping that Roman Milukov will read,
wrote:

ES> ======================================
ES> 37 mikrukh in total. Impressive, isn't it
ES>?
Sooo!

ES> By the way, about the boards. If anyone is interested -
ES> write, you need to know how many boards are needed.
I'm interested! But! I'm unlikely to make such a big board just because of the sound. We need to think about what to put in it at once. The screw is just a
necessity. But here, too, it is necessary to somehow take into account existing standards. Now
DISMASTER is collecting all sorts of schematics for the screw, you need to wait, look at them and
choose the most acceptable option. By the way, the spark-software controller, like in
50**, became a standard. Or maybe not, I don’t know.
What else?

Hello, Tim!

25 Mar 98 Tim Kelly hoping that Roman Milukov would read,
wrote:

RM> replace. Yes, in my opinion, VI53 will not go anywhere even in turbo.
RM> They really get warm.
TK> Do you have a reference book or what kind of documentation do you have? To see exactly
TK>? We'll soon draw the card circuit, just draw it
I just have it written that the clock frequency arriving at the CLC inputs is up to 2 MHz.
How much is that? I think less.
TK> Tell us why there is a slot for a PC multicard? Perhaps we need to contact
TK> the author, how to add a slot?
TK> By the way, he connected the screw according to his original
TK> circuit, a couple of days ago.
The screw is stuck into the multicard PC. I already wrote about this. This
originality scares me.

TK> Now the software is writing, let's see what happens?..
Damn! He should talk to DISMASTER first. Maybe they could cooperate, he also wanted to write software for the screw, and it was a very cool idea. Now he
is trying to get his bearings so that it will be more standard.

RM> I'm interested! But! I’m unlikely to make such a great board just because of the sound
RM>. We need to think about what to put in it at once.
RM> The screw is simply a necessity. But here, too, it is necessary to somehow take into account the existing
RM> standards. Now DISMASTER is collecting all sorts of circuits for the screw,
RM> you need to wait, look at them and choose the most acceptable
RM> option. By the way, the spark-software controller seems to have become a standard in 50**. Or maybe not, I don’t know. What else?

Oooh! I'll finish the diagram one of these days and post it here. Whoever wants, add whatever you want, I’ll just take charge of setting up the payment. It will be possible to insert the slot - I'll put both two and three on the board. As soon as someone makes the diagram and checks it. You're broke!

RM> Damn! He should talk to DISMASTER first. Maybe we could cooperate
RM>, he also wanted to write software for the screw, and the idea was very
RM> cool. Now he is trying to get his bearings so that it will be more standard.

What is DISMASTER's postal address/telephone number? Let them contact you.
2Zheka Safronov: put here the address of the developer of the sound system, pls.

RM> This originality scares me.
TK> In a couple of years, cartoons will disappear from sale. And here
TK> is an original solution.
Yeah, and DISMASTER doesn’t like connecting via multitasking. He is leaning more towards the ATM
scheme.

TK> What is DISMASTER's postal address/telephone number? Let
I’ll let you know with soap.

TK> Woohoo! I'll finish the diagram one of these days and post it here. Whoever wants
TK> do whatever they want, I’ll just take charge
TK> of installing it. It will be possible to plug in the slot - I’ll put both
TK> two and three on the board. As soon as someone makes the diagram and checks it.
Okay, you can forget about the slots imho. But the screw connection diagram needs to be
drawn up.

RM> Okay, you can forget about slots imho. But the connection diagram for the screw
RM> needs to be
RM> wired.

Let's see. Now, if only I could build a sensible operating system, with nested
directories and segmented files... But with this crap it’s just pain...
you can’t even make text configuration files :(

RM> the screw connections need to be separated.

TK> Let's see. Now, if you could build a sensible operating system,
It is necessary, but...
TK> with nested directories and segmented files...
TK> But with this crap it’s a pain...
TK> you can’t even make text configuration files :(
... just don’t blindly copy MS-DOS. Although some people like IS-DOS. :-/

TK>> with nested directories and segmented files...
TK>> And this shit is a pain...
TK>> you can’t even make text configuration files :(

Over the course of a year of using MS-Dos, I have not found any unpleasant moments in it.
Shortcomings - yes, but not glitches. Of course, you don’t need to blindly copy, you just need to
grasp the basis of the file structure.

RM> is-dos like it. :-/

VS> I would say not to blindly copy CP/M - it is much closer
VS> to ZX.
TR-DOS is much closer to ZX. :)

RM> TR-DOS is much closer to ZX. :). I consider the built-in commander to be stupid.

In general, the axis should be loaded from disk. And only BIOS sits in the ROM.

TK> Well... TR-DOS is not an axis, but less than half :(
Well, almost a “semi-axis”, as someone put it. :)

TK> So tell me how to change it so that it is convenient to work with the
TK> screw, with program configuration files, etc.?
I won’t say, let those who know This fumbles more than me.

TK> In general, the axis should be loaded from the disk. And in the ROM
TK> there is only BIOS.
Probably.

And IS-DOS is also very close to ZX (although I somewhat
dislike it as a system - it’s inconvenient and slow).

TK> program files, etc.? Is-Dos is quite a powerful message :), but there
TK> there are a lot of excesses, shortcomings, etc. I think the built-in commander
TK> is stupid.
And the built-in commander is not so stupid, but when it comes to
the fact that the command line interpreter is loaded from the disk, then this is
really terrible stupidity.

TK> In general, the axis should be loaded from the disk. And in the ROM there is only
TK> BIOS.
This is of course true, but due to the fact that Speckie is primarily a disk drive machine, not everyone has screws (for example, I don’t either), then it would be nice to place the shell (at least a la Norton, in general
commander of some kind) in the ROM.

In general, I am leading to to the fact that our group (or rather me ;-) has begun the development of a new BIOS for the Spectrum. Installing it on a computer does not require any hardware tweaks to the computer. Everything is done by simply replacing the ROM. The new BIOS is sewn in place of 128 Basic (no one really needs it anyway, except for some rare enthusiasts), which is why there are no modifications. After installing the ROM, you have
two systems: TR-DOS and NeOS. NeOS may be multi-system
(that is, it won't care which disk you gave it - TR-DOS or
NeOS). Yes, formatNeOS disks are completely identical to 640k IS-DOS disks.
So nothing new, everything is familiar. Just don’t think that if IS-DOS discs are readable, then programs will run from them. The system is completely different.
Now a little about what NeOS gives to programmers. Hurray, no more problems with memory above 128k - a corresponding ROM will be made for each Specky model. A standard function is used to switch pages. ROM functions will be accessed through restarts (RST #0 - RST #38). The function number is supplied to the restart input in register
C (and in this it is similar to IS-DOS, although IS-DOS
has only one restart - RST #10). Restarts are divided by type of
function: System manager, Error manager, Screen manager,
File manager, Memory manager. Based on NeOS, you can organize a pseudo-multitasking system: programs do not work in parallel, but there are several programs in memory, between which you can switch, and the programs (with the right approach) cannot harm each other. Accessing ROM functions by address is not recommended, since procedure addresses may change in different versions. If you
are not satisfied with the fact that functions are called for quite a long time (I don’t remember how many
this is in clock cycles), then it is possible to determine
the address of any function. How to do this, I will not - because at the moment it ismakes no sense, because NeOS has not yet been completed. Yes, by the way,
you can call NeOS functions without even being in it, since
NeOS saves Basic system variables, placing its own in place
of the printer buffer (we don’t touch TR-DOS!). This will greatly facilitate the development of programs for NeOS at the initial stage of its development, until an assembler for NeOS appears.

NeOS readiness stage at the moment:
Memory manager - 100% (everything I came up with was implemented)
Screen manager - 60%
System manager - 3%
Error manager - 0%
File manager - 1%

Advice and suggestions within reasonable limits are welcome. All kinds of
questions are also welcome (according to the capabilities of NeOS).

With respect, Roman aka Megus of BrainWave association.

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

TK>> only BIOS.
RP> This is of course true, but due to the fact that Specky is predominantly
RP> a disk drive machine, not everyone has screws (for example, I don’t have either
RP>), it would be nice to place the shell (at least a la Norton, in general
RP> some kind of command) in ROM.

Well... Booting the OS from the system floppy once a day is not a problem, IMHO. And the programs must return control to it upon completion of work.

RP> In general, I mean that our group (or rather me ;-) has begun
RP> the development of a new BIOS for the Spectrum. Installing it on a computer does not
RP> require any hardware tweaks to the computer. Everything is done
RP> by simply replacing the ROM. The new BIOS is sewn in place of 128 Basic (it
RP> is not needed by anyone anyway, except for some rare enthusiasts),
RP> that is why there are no modifications. After installing the ROM, you have
RP> two systems: TR-DOS and NeOS. NeOS, it is possible to be multi-system

So, are you still developing Bios or OS? These are two different concepts!

RP> (that is, she won’t give a damn which disk you gave her - TR-DOS or
RP> NeOS). Yes, the format of NeOS disks is completely identical to 640k IS-DOS disks.

Why not 800k? Normal operation has been verified, there is more space.

RP> printer buffer (don’t touch TR-DOS!). It's strongwill facilitate
RP> the development of programs for NeOS at the initial stage of its development, until
RP> an assembler for NeOS appears.

RP> NeOS readiness stage at the moment:
RP> Memory manager - 100% (everything that was invented - implemented)
RP> Screen manager - 60%
RP> System manager - 3%
RP> Error manager - 0%
RP> File manager - 1%

RP> Advice and suggestions within reasonable limits are welcome. All kinds of
RP> questions are also welcome (according to the capabilities of NeOS).

Firstly, you need to make a more _operating_ than _disk_ system.
Flash into a BIOS ROM, which will know the formats, write/read
sectors/tracks/files, etc. And the OS should be able to put this information where it needs to be launched, interpreted... For example, put programs into those pages that _it_ sees as free, etc. Only in this way will it be possible
to fully utilize the extended memory. This way you can have several running
programs in memory, switch between them, exit to the OS and
return to programs, and much more.

this is great, we need to make sure that the next PF doesn’t come out.

RP> The new BIOS is being flashed in place of 128 Basic (it’s
It’s high time to demolish it!
RP> Yes, the format of NeOS disks is completely identical to 640k
RP> IS-DOS disks.
Not enough will be!
RP> Now a little about what NeOS gives to programmers.
RP> Hurray, no
RP> no more problems with memory above 128k - for each model
RP> Specky
RP> a corresponding ROM will be made for switching
And it’s not easier to make a universal one. driver?
RP> pages used
RP> standard function.
RP> All kinds

RP> development of a new BIOS for the Spectrum. Installing it on
I read about this online some time ago, it seems. When do you plan to finish it?
I liked this idea even then, and I’ve been waiting for it ever since. :)

RP> neither), then it would be nice to put the shell (at least a la
RP> Norton, in general some command) in ROM.

TK> Exactly!

And who is stopping you from loading the resident interpreter?

[skipped]

Have a nice connection.
Roman.

April 23, 1998, already 23:39

RP> for example
RP> neither), then it would be nice to put the shell (at least a la
RP> Norton, in general some kind of command) in the ROM.
RM> It is possible.

RP> Now a little about what NeOS gives to programmers.
RP> Hurray, no
RP> more problems with memory above 128k - for each model
RP> Specky
RP> a corresponding ROM will be made. To switch

At 20:23, Tuesday April 21, 1998 there was such a thing that
Tim Kelly dashed off a letter from Roman Petrov:

TK> Well... Once a day, boot the OS from the system floppy disk, IMHO, not
TK> a problem. And programs should return control to her upon completion of
TK> work.
This is natural, programs will return control to her anyway, but
what to do with glitches? ;-) After all, the Spectrum is also not 100% protected from them

TK> So, after all, are you developing a Bios or an OS? These are two different
TK> concepts!
Is MS-DOS DOS? This is approximately the same thing I am developing, that is, a command interpreter will be added to
BIOS.

RP>> or NeOS). Yes, the format of NeOS disks is completely identical to 640k IS-DOS
RP>> disks.
TK> Why not 800k? Normal operation has been verified, there is more space.
But in principle I don’t care what driver I connect, that’s what it will be. It will be
possible to connect your own disk device drivers => what's stopping
from writing a driver for 800k disks, or for MS-DOS disks in general? After all,
driver functions will be standardized, there are no problems with compatibility
drivers (work with the disk is carried out not at the level of sectors and tracks, but
files).

TK> Firstly, you need to do more _operating_ than _disk_
So that’s the way it is.
TK> where to go, run, interpret...Let's say, lay out
TK> programs in those pages that _she_ sees as free, etc. Only
Is it OS or BIOS? In my case, this is already done by the BIOS (protection of
applications at the BIOS level).
TK> in this way it will be possible
TK> to use the expanded memory to the fullest. So you can have
TK> running
TK> programs in memory several at a time, switch between them,
TK> exit to the OS and return to programs, and much more.
All this was immediately in the plans. Now we need to make NeOS for now (BIOS +
command interpreter), and then it will be possible to write a
pseudo-multitasking OS.

If there is room, I will combine the command interpreter with the shell (i.e.
it will not be like in IS-DOS - the interpreter is loaded from the disk, everything will be
combined, like in Norton Comander)

RM> I read about this online some time ago, it seems. And
RM> when do you plan to finish?
RM> I liked this idea even then, and I’ve been waiting for it ever since. :)
It was not me who wrote online, but Pasha Fedin from Moscow. Yes, he and I really wanted to collaborate in writing the BIOS, but then everything somehow fizzled out, although both Pasha and I still had some of the work. And now I
decided to revive this bright undertaking, taking as a basis the idea itself -
placing the BIOS in ROM, and then everything is mine.

AI> this is great, we need to make sure that another PF doesn’t come out.
Pink Floyd or what? I don’t know, if what I once saw is a complete
PF, then I categorically did not like it, besides, the whole thing (including the BIOS)
is loaded from disk => this is a system of a different class and is not a competitor to us yet.

RP>> Yes, the format of NeOS disks is completely identical to 640k
RP>> IS-DOS disks.
AI> It won’t be enough!
Who’s stopping you from picking up another driver (and the driver may be
immediately in ROM).

RP> Is it OS or BIOS? In my case, this is already done by the BIOS (protection
RP> of applications at the BIOS level).

This is great, but the question is - if someone doesn’t like the way it
does it, should they change the ROM? Or write bypassing the procedure, as in TR-Dos?
IMHO in the BIOS there should be those functions that obviously no one
will need to change (File structure, for example, why change? Bypassing the protection
and so will be).
That's why they separate the OS and BIOS. Read some books based on already established
standards, see why it was done this way and not otherwise.

TK> I would have said so, but it sounded like a tough installation.
Perhaps drivers for MS-DOS, IS-DOS (640/800)
and TR-DOS will be immediately flashed into the ROM. One of the functions of a disk device driver is the function of determining disk ownership. When changing a disk, the BIOS will
call this function in turn for all drivers connected to this
device (drive). This way it will determine the ownership of the disk and then,
until the next disk change, it will work with exactly the driver that
recognized the disk as its own.

TK>>> put the programs into those pages that _she_ sees free
TK> This is great, but this is a question - if someone doesn’t like it like it
TK> does this do what, flash the ROM? Or write bypassing the procedure, as in
Actually, yes, you would have to modify the ROM. OK, I’m adding one more function
switching pages without taking into account their protection.

RM> Is it so that you load it from a floppy disk every time, and take up space in RAM?
RM> There are heaps of such drivers written, take a ready-made one...
Why load it from disk? It’s not easier to flash it into ROM and, when the computer starts, determine its type and then switch pages accordingly. Only
in this situation, page switching will slow down a little more (well,
by 10-20 cycles).

TK> I'll like how she does it, what, should I flash the ROM? Or write
TK> to bypass the procedure, as in TR-Dos?
TK> IMHO in the BIOS there should be those functions that
TK> obviously no one will need to change (File
TK> structure, for example, why change? Bypassing the protection
TK> will be the case anyway).
Yes. But still, as many of these functions as possible need to be isolated and stuffed into ROM.

TK> That’s why they separate the OS and BIOS. Read some
TK> books according to already established standards, see why
TK> is done this way and not otherwise.
Yeah. Let him read it. But it just may turn out that it is impossible to do exactly _this_ for
Spek, but it is necessary _otherwise_, because Speck is “rigidly” built not at all like a
PC. Books are all written about the PC. Well, they cover some and other platforms, but only briefly. And Speck is very “special”.
Or historical, about the ancient SR/M?

Hello, Roman!

25 Apr 98 Roman Petrov, hoping that Roman Milukov will read, wrote:

RP> If there is room, I will combine the command interpreter with the
RP> shell (i.e.
RP> it will not be like in IS-DOS - the interpreter is from the disk
RP> is loaded, everything will be
RP> combined, like in Norton Comander)
Correct. That’s why many people spit on is-dos, because it constantly gets into the disk for no reason or no reason.

RP> It was not me who wrote online, but Pasha Fedin from Moscow. Yes,
RP> and I really
RP> wanted to collaborate in writing the BIOS, but then everything somehow
RP> fizzled out, although
But in vain. You must not throw the muzzle. Maybe on its basis now some powerful thread would be used by everyone.

RP> both Pasha and I still have some of the work. And
RP> now I
RP> decided to revive this bright undertaking, taking as a basis
RP> the very idea -
RP> placing the BIOS in ROM, and then everything is mine.
Well, that’s right. Let's do it. While Pasha still says in ZX.SPECTRUM "if
someone needed this..." :)

Mon Apr 27 1998, Roman Milukov squeezed the keyboard, hoping that the following words would reach Tim Kelly:

RM> Yeah. Let him read it. But it just may turn out that it is impossible to do exactly
RM> _this_ for Speck, but it is necessary _otherwise_, because Speck "iron"
RM> is not built at all like a PC. Books are all written about the PC. Well, they cover some
RM> and other platforms, but only briefly. And Speck is very “special”.
RM> Or historical, about the ancient SR/M?

It’s true, many books about PC have been written, but they were written by smart people...
You can read pre-PC literature, BIOS and OS have been used since time immemorial. :)

RP>>> it comes to the point that the command line interpreter from the disk
RP>>> is loaded, then this is really terrible stupidity.
TK>> Exactly!
RA> And who is stopping you from loading the resident interpreter?
Of course no one is stopping you, but it’s an infection, memory eats, and in IS-DOS there is very little of it, if not very little. IS-DOS is now, IMHO, outdated.
Now it needs a good replacement. This is the kind of replacement I am trying to create.

RP> return, but
RP> what to do with glitches? ;-) After all, the Spectrum is also not protected from them
RP> is 100% protected
Almost every system program and some games have
"output to DOS" (JP #0000 in trdos).
If it is used correctly...

AI> Isn’t it easier to make a universal driver?
RM> This is to load it from a floppy disk every time, and place it in RAM

RP> Yes, of course, just in addition to switching pages for
RP> different computers there are
RP> some more specific functions. Moreover, if you support
RP> all of them, then
RP> they can take up a decent amount of space, so for now
Well, you only need to support memory management functions, and this is not so
much (see ZXF5).
RP> there is
RP> the option of different firmware for different computers.
imho this is too hectic.

DD> Almost every system program and some games have
DD> “exit to DOS” (JP #0000 in trdos).
DD> If you use it correctly...
Yeah, it’s already been used ;-) The function is universal - both reset and exit the
program. The difference is this: if at the input A=1 - output, otherwise - reset (Hint:
when the Reset button is pressed, the memory is not reset, only
registers => A=0 are reset).

RP>> it comes to
RP>> that the command line interpreter from the disk
RP>> is loaded, then this
RP>> is really terrible stupidity.

TK> Exactly!

RM> This is so that you can load it from a floppy disk every time, and take up space in RAM
RM>?

RP> Why load it from disk? It’s not easier to flash it into ROM and when
RP> starts the computer
RP>, determine its type and then switch the pages
RP> accordingly. Only
Of course it’s easier. But I think it’s not difficult to release an installer program that
generates a firmware file for one or another unique computer.
Otherwise...

RP> in this situation, switching pages will slow down a little more
RP> (well, so
RP> clock cycles 10-20).
And besides, the universal driver is much longer than the normal one.

And then, this approach (firmware settings for a specific computer) will indicate
standards for the location of drivers in the firmware. Let everyone do what they want, but
in
designated places.

RM> And besides, the universal driver is much longer than the normal one.
That's it.

RM> And then, this approach (firmware settings for a specific computer)
RM> will indicate the standards for the location of drivers in the firmware. Let everyone
RM> do what he wants, but in designated places.
I understand you that drivers should have strictly fixed
addresses? Under no circumstances! I don’t want to repeat TR-DOS mistakes. Everything will be
standardized to the limit: standard restarts (RST 8 - RST 38) and
no addresses (well, maybe one small useful procedure at address #40, which will always sit there and all restarts will
use it). By the way, if someone is not satisfied with the speed of accessing a function via restart, then he can get the address of any function in a very simple way. The method will be described in the BIOS documentation.

RP> Of course, no one interferes, but he, an infection, eats up memory, and in IS-DOS there is very little of it, if not very little. IS-DOS is now, IMHO,
RP> outdated. Now he needs a good replacement. This is the kind of replacement I am trying to create
RP>.

Good luck. Here we have conferred with the SpbZxNet coders and come
to the conclusion that it will not be possible to write decent FTN-compatible software for our network without a
normal OS....

[skipped]

Have a nice connection.
Roman.

April 29, 1998, already 23:11

With respect, Roman aka Megus of BrainWave association.

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

AI> Well, it needs to be done right away.
Most likely the ROM will immediately contain drivers for TR-DOS, iS-DOS 640k,
iS-DOS 800k and MS-DOS 360/720k. There won't be any screw drivers yet due to our lack of any. But anyone can write a driver for their screw, connect it with a standard function, and then their screw will work completely without problems. By the way, you can organize the RAM-Disk
this way (maybe we’ll even do it ourselves and sew it into ROM).

AI> Well, you only need to support memory management functions, and this
AI> is not that much (see ZXF5).
But that’s the point, it’s not only that. In addition, as I already wrote, the time
working with such a universal driver will increase somewhat (switching
pages will take a little longer)

RM> unique company. Otherwise...

RP> By the way, a good idea, but I was going to release several
RP> firmware for
RP> different computers, since in addition to memory on different machines
RP>, for example, screws are connected in different ways (on Scorpa - SMUC, on Pro -
RP> something yours,
RP> to the Pentagon - in general, whoever wants).
Here! That is why the installer program is preferable. How will the screw be supported in your ROM for
Penta?
Or if, for example, someone on their Pro decided to connect the screw according to the
ZX-Next scheme (its advantages were clearly explained to us here)? Imho it’s better if
the consumer himself can create the firmware for his own hardware.

...

RM> Here! That is why the installer program is preferable. How will the screw be supported in your
RM> ROM for Penta? Or if, for example, someone on
RM> their Pro decided to connect the screw according to the ZX-Next scheme (its advantages were clearly explained to us here
RM>)? Imho it’s better if the consumer himself can
RM> create the firmware for his own hardware.
As for the installer - thank you, by the way, I liked the idea. Probably
it will be structured like this: several firmwares, with different memory drivers.
A bunch of drivers for all kinds of devices (hard drive,
disk systems, mouse, keyboard, etc.) will be attached. And in the installer you can
select those drivers to which you will need the fastest
access. These drivers are inserted into the free space of the firmware, configured
to the specified address and included in the table of built-in drivers.
Also in the installer you can set a bunch of other small settings.

RM> Create! urgently, only while there is a catastrophic lack of time -
study. Maximum 2 hours of work a day on the BIOS :( Never mind, summer is coming - so I’ll have a blast. Maybe even (if I try REALLY hard and work hard)
at least I’ll get the beta version ready for FunTop, but due to the fact that we’re also going to write a demo for it... In general, early in the fall not worth the wait.

PSGive us more tips and suggestions! Already now your letters reveal
some holes in the BIOS.

RP> I would not say, since the firmware from each other will
RP> differ minimally
RP> and will be delivered on one disk all together
RP> (standard
RP> it is planned to support: ZX-128, Scorpion 256k, Profi
RP> (512/1024),
^^^^^^^^but this is wrong, memory pros can have
not only 512/1024, I personally have come across computers with
memories of 3xx/576/768 and even 512 in which the pages are not in a row, that’s exactly why it’s needed universal driver

And finally, everything described above should be stored on the screw and in the ROM
only the initial boot.
And then everything will go from the screw.

Sincerely, Dmitry (SchemeMan) coder, artist and iron worker.
╔══════════════════╗
· DARK SOULS GROUP ·
╚══════════════════ў

RM> How will the screw be supported in your ROM for Penta?
Is there a screw there?
RM> Or if, for example, someone on their Profi decided
RM> to connect the screw according to the ZX-Next scheme (they clearly explained its advantages to us here
RM>)?
And we did the same with the scheme itself we haven’t seen and probably won’t see anymore :(

AI> From the 128th pzushka it is very hectic and slow to climb into the tyrdos, and therefore
AI> you can make a switch for the tyrdos ports for access from everywhere, in the port
AI> #eff7 there is a bit for this.
#EFF7 - is this on Pro? Only disk device drivers will access TR-DOS ports. Therefore, what's stopping you from making a version of these very drivers specifically for Pros? Should I install them in the installer instead of the standard ones? The entire system is as open as possible for modifications.

AI> But you can write your own, which will not glitch.
And I won’t even write it ;-) Everyone will create their own firmware
in their own way. Whichever driver you like, it will install (although the installer
will have a definition of the type of computer, but with the ability to change).

RP> Have you read about the idea of ​​an installer? Did you understand its essence? So it’s solved
Well, I read...
RP> the problem
RP> with a bunch of firmware - everyone will configure the system for themselves.
Okay, I’ve convinced you :)

AI> you won’t have to modify it on another computer.
You don’t have to sacrifice speed for dubious versatility. All the same
there will be a computer for which it will be necessary to modify it. And I think some people will immediately start replacing such universal drivers with fast ones. :)

RP>>exists

Hello, Dmitry!

2 May 98 Dmitry Pugachev, hoping that Roman Petrov would read, wrote:

DP> And finally, everything described above should be stored on a screw and in the ROM
DP> only the initial loading.
DP> And then everything will go from the screw.
Who doesn’t have a screw? That's the majority! I don’t think that in the near
future everything will be hung with screws.

AI> not only 512/1024 I personally have come across computers with
AI> memory 3xx/576/768 and even 512 whose pages are not
AI> in a row, that’s exactly why a universal driver is needed.

RM> that in the near future everyone will hang themselves with screws.
And me!
And me!
And I have the same opinion.:-)

DP> And me!
DP> And me!
DP> And I have the same opinion.:-)

Why are you yelling “everything is screwed”, if you admit that
everyone will never install it?

DP> Sincerely, Dmitry (SchemeMan) coder, artist and
DP> ironworker.

And why have you cheated and added iron? I saw art.
And where is all this?

DP> ╔══════════════════╗
DP> · DARK SOULS GROUP ·
DP> ╚══════════════════ў

There is no such group!!! And the frame resembles a grave.
And there was a “dark souls corporation”. Was... And no :)))

Sincerely, Renat.

The night is shorter than the day, but there will be no murder.

RM>
RM> Don't do this!!!! it will drive him crazy with joy:)))
Be sure to do it.

RM> But you won’t collect anyway, but you won’t get any screams
RM> you’ll end up with it:)))
And I’ll collect it, and there won’t be any screams.

RM> And what have you screwed up and screwed up? I saw art.
RM> And where is all this?
I saved so much that you couldn’t even dream of it.
For example, I screwed up the megascreen port.
And finally, you bastard, what port does your watch hang on.
Isn’t it really on mine.

DP> Maybe someone can make a diagram or throw it in the echo, I will be very grateful
DP> I will be grateful.
RM> Don’t do this!!!! it will drive him crazy with joy :)))

DP> ╔══════════════════╗
DP> · DARK SOULS GROUP ·
DP> ╚══════════════════╝
RM>
RM> There is no such group!!! And the frame resembles a grave.
DP> And I tell you there is, even if I am alone.

DP> And then everything will go from the screw.
RM> Who doesn’t have a screw? That's the majority! I don’t think so
DP> And those who don’t have it, like me, should install it.:-(

^^ Renat...
DP> I wanted to give you an idea.
This is how you install the screw for yourself, then he will... maybe then he will like your idea
like it. ;)

DP> And I’ll put on the icons.
We’ll see about that later.

At 14:34, Monday May 04 1998 there was such a thing that
Denis Dmitriev wrote a letter to Roman Petrov:

DD> Not a bad idea.
Yeah, I even liked it myself ;-)

DD> Although there are comments - condition A=1 will not be found in many programs
DD> is executed, but by Reset it falls NOT in trdos, but in 128basic
Yeah, tnx for the advice - I completely forgot that TR-DOS
programs will also function, which sometimes have a habit of being reset by turning on 128 ROM,
and then - JP #0. In this case, yes, it is not always fulfilled. In the case of
BIOS, the program should exit, and not be reset!

[ Someone was hungry... ]

Thank you for the idea - I’ll check for the environment from which the exit occurs.

PS One of these days I’ll send you an incomplete document on BIOS functions

Hello, Viktor!

04 May 98 Viktor Kuzmin hoping that Roman Alexandrov will read,
wrote:

VK> New DOS = a perversion for the Spectrum, but the commander in ROM =
VK> is a pretty cool thing (convenient).
You shouldn’t be doing that. Spec needs a new DOS. And if we’re going to throw out
BASIC128, then not just for the sake of the commander...
_Just_commander_ can be made for the cache.

VK> Here we will soon (1-2 weeks) have a completely finished
VK> product
VK> E-mage Work Station by RUM of E-mage, which will be
VK> intended for firmware
VK> in ROM instead of 128 BASIC, a pretty cool teamp
VK> (convenient and fast), if
Any new product is interesting, we’ll take a look.

VK> throw the information on the broom, then you can make support for
VK> the broom (you can also
VK> throw the broom yourself ;) ), you can also throw the information on Cmos.
The “broom” itself is unlikely, :) I can give you some information if
you didn’t catch what was flying here.

RM> This is how you install the screw for yourself, then he will... maybe then
RM> he will like your idea. ;)

I’m not planning a screw for myself. That's it, there will be no system!!! :)))
Let Dima yell whatever he wants, but you can’t create something global
alone... and there’s no need.

it was me... Renat

At 18:27, Monday May 04 1998 there was such a thing that
Viktor Kuzmin wrote a letter to Roman Alexandrov:

VK> New DOS = pervert for the Spectrum, but the command in ROM = quite
I don’t think that DOS is a pervert. For those who do not write complex system software, the new DOS is not needed in principle, but it can be useful for them too).
VK> cool thing (convenient). Here we will soon (1-2 weeks) be completely
I would like to know more about this very team of yours.

Sat May 09, 1998, Dmitry Pugachev squeezed the keyboard, hoping that the following words would reach Roman Milukov
:

DP> And finally, bastard, what port does your watch hang on.

If this is said as a joke, put a smiley face. If not, a star will find you ;)

Hasta la vista.
Tim Kelly