Author Topic: Mossy 2.0 - NO BITMAPS FOR YOU  (Read 2599 times)

mossy sounds like some kind of old school adventure game.

Good morning everyone
Today after i fix time i'n going to start commands!

Ok, the following is a reminder for me
unsigned long getTime() return time_tick;
Yarrr

So like, this is an actual operating system? It actually monitors and handles the hardware? It can be booted by itself with nothing else? Its not just some stuff script based on a pre-made console OS?

So like, this is an actual operating system? It actually monitors and handles the hardware? It can be booted by itself with nothing else? Its not just some stuff script based on a pre-made console OS?
Yes, yes, yes, yes

Interested? http://forum.blockland.us/index.php?topic=193074.0
I updated the largest font to have 446 characters. If you can make a basic OS I'm sure you can read bitmap fonts.

That'd require so much work D:
I'd have to rewrite parts od the graphics stuff ;-;


That'd require so much work D:
I'd have to rewrite parts od the graphics stuff ;-;
Why rewrite? Can't you simply write a separate font reader on top of your existing graphics things?

Make a partition function too.

forget it, I'll run it on a CD

Why rewrite? Can't you simply write a separate font reader on top of your existing graphics things?

Because displaying bitmaps is much harder than rendering predefined BIOS fonts.

Why rewrite? Can't you simply write a separate font reader on top of your existing graphics things?
Rendering the text is handled by the graphics adapter. Right now all he has to do is tell the CPU what text to write. If he were to write a bitmap font renderer, he would have to switch to graphics mode and completely rewrite the whole console I/O.


Needs another column of periods because there's a blank line on the left side, but not on the right.