MotoBIOS & MotOS: The personal computer

[Drunkie]

Not really, they're scripted shells with wanna-bee functions. They give all this "fancy info" about their stuff etc... Fake load times, no kernel or API or whatever a real OS has which is actually functional it just makes them feel proud. But who am I to take away their happiness? They can do as they want if it really makes them proud.
WireOS - AlcyOS are pretty much the only "real" OS's to date.

Go hate on someone else. He's doing it in assembly so he should be proud of that alone. All these other OS's in E2 with Console Screen and writeString() are the ones you need to go hate on.

On Topic: I'd like to see this get finished, sounds promising.

[neos300]

This *will* be finished, the question is how long it will take. At the moment I am still working on making the BIOS and the filesystem(i have no idea were to start, ughh)

[Bull]

So you don't have anything yet?

[Xandaros]

I know the problem with the "where to start".
I started with the BIOS and a basic API. Mostly used by the BIOS, so the so-called API was in reality a part of the BIOS... lol

Xan

[Matte]

This *will* be finished, the question is how long it will take. At the moment I am still working on making the BIOS and the filesystem(i have no idea were to start, ughh)

You know how FAT works, right?

[Drunkie]

You know how FAT works, right?

Yeah it usually starts from mcdonalds and other fast food restaurants.

[Dav1d]

Yeah it usually starts from mcdonalds and other fast food restaurants.

+1 rep'd

[N00bDud3]

Cell 0 outputs how many keys are being pressed at once. Up to 30 I believeCell 1 outputs the ASCII key codes per keys pressed (If cell 0 = 2, then two keys are pressed, which would be cell 1 & cell 2)Usually, though, you only need to access cell 0 to see if a key is pressed, then cell 1 to retrieve the ASCII code. Then you simply write 0 back to cell 1 and wait for the next key press

According to the hi-speed documentation, the first 32 cells are supposed to be a keybuffer, as the rest of the cells afterwards are an array of all held keys.

Keyboard
Hi-Speed outputs: Memory/Key

Keyboard! You push keys, and it reacts! By default it outputs last pressed key to its only output, BUT the only output also serves as hi-speed link..!
Virtual memory area thing of wired keyboard is divided into 2 areas: 1 is the key buffer, and other one is array of pressed keys.

Key buffer is situated at first 32 bytes of keyboard, and it has following structure:
Zeroth byte shows how much keys there are in the buffer. New keys are appended on start.
Writing value to ANY of these 32 bytes except first will clear value you wrote from key buffer. I.e. if our buffer looks like:
4,2,3,4,5
it means that there are 4 variables. If we write "3" to it, it will become:
3,2,4,5
Writing removes most recent entry of key.
Ideally you'd read a key, trigger your event, and write back this code to same position you read it from.

Writing value to first value clears ENTIRE buffer.

There is also other area, which is situated from 32 bytes and up. It is ASCII-mapped array, where for each byte it's value shows if key is pressed or no.
I.e. if we wanna know if key #48 is pressed (thats "0") we look what is at address 32+48. If theres 1, we're off! Else meh, bad luck, key isn't pressed yet.

[neos300]

@Matte
Absouletely not. BUT I WILL LEARN!

And I am still in the design phase. I mainly wrote crap for alycone os to learn and use zasm, because I could never get the console screen to display anything for some reason. And it still isn't working for me. :\ I think something is wrong with my wire. I followed all the advice people have given me and foxes code but it still won't work.... BRB gonna see if regular wire stuff works with it.

Regular wire works but the console screen doesnt appear to be working.

[Schilcote]

I read a thingy a long time ago that might help you, let me find it again...

EDIT:

Found it.
http://www.superfrink.net/athenaeum/OS-FAQ/os-faq.html

There's information about file systems in there, although the document is mainly about real life PCs a lot of it should still apply to what you're doing...