Like you would for GRUB, you would say uses the multiboot bootloader "GRUB".
The reason for "MOP" is people keep reinventing the wheel, if you start a OS project and start making bits of a OS and you give up after a while, you end up were 95% of OS projects end up.
But if you used "MOP" and instead of making what has already bean made, you add new stuff like USB or a driver for a common sound card, we will build up a large collection of ASM code for the development of OS.

By mixing and matching these MOP modules you would end up with total differant OS's.
What you do not want is loads of downloads and more downloads and more downloads
but no new modules for "MOP" .

Maybe instead of MOP as a collection of modules, i may release it as a 32bit pmode BIOS, as in all the functions of the BIOS, but for uses from pmode.
Not as in a v86, but as in eg: a pmode floppy driver, that emulats int 13h.

\\\\||////
(@@)
ASHLEY4.

ASHLEY4,

You have gotten us to the point! While distributing sources it's very difficult to controller who is using it and not giving the credit. I think it's well known fact that if you put something into internet some people start using them regardless of licences etc.

regards
Mac2004

ASHLEY4,

You have gotten us to the point! While distributing sources it's very difficult to controll who are using the sources and not giving the credit. I think it's well known fact that if you put something into internet some people start using them regardless of licences etc.

regards
Mac2004

Normal code for such things, are usually so integrated, in to other bits of code that it is a lot harder to just rip it off, but because these are in separate modules they are very easy to rip.
We need a way for them to be used, as a module called "MOP".
\\\\||////
(@@)
ASHLEY4.

I just noticed that some of my messages are 'doubling' for some reason eg. my previous message. Anybody else having similar problems??

Mac2004

I have not, had a doubling of messages so far.

\\\\||////
(@@)
ASHLEY4.

ASHLEY4 remember me? In the DOS topic of timer, if you can help me,
i posted an example of the code... Tankyou!

If have an people can helpme with the timer and the int8 please helpme!
Iam creating an MultiTask OS, (CrossOver OS) and I have the
graphics loader, booter, but I have problems to create the code to the
timer and the vector table of int...

Tankyou for all...
If an people need help with booting and graphics in text mode,
i can help...

However there're some points here:

1) some would like to use only one TSS for V86, tasks etc. and some would like to use hardware TSS switching and several TSS.

2) what about memory managers? ( local heap, locally resided but reference list for blocks, page table managers etc. )

3) PIT

4) PIC

also a basic kernel RTL would be nice - linked lists support, strings formatting, TSS dump etc.

All these module are being built in to a OS to replace v2os (code named v3os) and a release will be available soon for testing, .
See here for details: http://www.v2os.cx/

\\\\||////
(@@)
ASHLEY4.

Batteries not included, Some assembly required.

I was just wondering, how is it going with the MOS project, If that module is available, where can I get it?

It was called MOB.
And I don't know if there is still intrest for it? Dex4u (former ASHLEY4), is currently developing his own OS (http://dex.7.forumer.com/), so I don't know if he has any time to spend on this anymore.

Bubach is right, all the module are now part of a new OS called "Dex4u" details on the above forum or you can get the demo from Dex4u web site
http://falconrybells.co.uk/
At the moment it has full suport for loading and run programs from floppy and CD, it as a full set of functions, including vesa support.

PS: Code will be released, has soon as the first release is ready.