Please, see attachments and talk two words about this project

HINT: You will get a lot more action using standard .zip format.

OK

Thank you very much maximYCH. I looked at two files in ROS. One was named bootsect.asm, and the other was SECBOOT.asm.

I think it would be useful, eventually, not necessarily today, mind you, but, eventually, to include a sentence or two explaining:

1. how ROS is organized, for example the purpose of each file.
2. WHY ROS was conceived, and implemented;
3. Which directions ROS will take, in the future;
4. Which particular characteristics of ROS make it "fast as a rabbit";
5. Which features of ROS distinguish it from other operating systems, for example, SOL, or Menuet, or DEXOS. In the alternative, one could simply describe the advantages of ROS, without mentioning any other OS.
6. Whether or not, a future version will access the hard disk, instead of, or in addition to, the current code based on FAT 12.

Thanks again for sharing your work with us....

Thanks
1. bootsect.asm - first boot sector; SECBOOT.asm - second boot loader; KERNEL32.asm - simple kernel.
2. Flexible alternative for MeOS/KOS, + some features of Windows and Linux.
3. Microkernel; multitasking; full modules structure.
4. My bad english ... I don`t know, what you talk me.
5. See up.
6. Yes. Future module structure -> all drivers (file systems, hardware, controllers, etc.) let load/unload its.

English forums: http://www.asm-teach.ru/forum/viewforum.php?f=6

Not to worry. In general, it is not the foreigner whose English is bad, it is the native speaker, who writes too much (verbose), and uses vocabulary which is too arcane.

Let me rephrase, numbers 4 and 5.

How about this:
You call your operating system, ROS, RABBIT operating system. The animal, rabbit, is able to run very fast. Therefore, we imagine that your operating system executes very quickly. The question is HOW does the design of ROS permit rapid execution? What is it, about the design of ROS, which confers upon your operating system, the property of fast execution? Does ROS employ preemptive multitasking, or cooperative multitasking, or neither?

Another way of asking this question, i.e. number 5 above, is to compare ROS with MeOS.

You have written, above, earlier today, in response to question #2, that ROS represents a "Flexible alternative for MeOS".
Why flexible? -- Is "flexibility" a useful trait for an operating system?
Do you mean to imply that ROS can be easily modified by individual programmers, to suit a particular environment? Alternatively, do you mean that it is appropriate for a wide range of computing tasks, such as individual desktop work station, factory automation, hospital data base, government record keeping, and so on....?

How is ROS flexible? --- what are the characteristics of ROS, compared with the same trait in MeOS? What is it about the design of ROS which confers the property of flexibility on it, when compared with other operating systems?

In other words, please explain, as best you can, what it is, about ROS, that makes it FAST and FLEXIBLE, especially since, at least in my mind, those two properties are generally antithetical (opposites).

Mmmm!!! I think about fork KolibriOS.

You mean MenuetOS? KolibriOS is itself a fork of MenuetOS.

> HINT: You will get a lot more action using standard .zip format.

7-ZIP is fine

> and talk two words about this project

Bootable "Hello"

> and talk more than two words about this project

1. Bootable "Hello world"

2. Be careful about "ROS" ROS-mess