MotoBIOS & MotOS: The personal computer

[neos300]

So after looking at Alycone and BP's stuff, I decided that I would try to make my own BIOS & os.
This is going to be a personal computer, which means that it will have a GUI, and be centered around playing music and stuff like that.

Specs(Working):
RAM: 64kb onboard RAM, with additional extension for another 64kb
Output: Console Screen, soundcard
Input: Keyboard, maybe laser pointer input if I can figure it out.
Sound: Soundcard, not working on it yet
BIOS: MotoBIOS
Cartridge/Floppy disk: Will support cpu cartrideges and programs stuck on a bit of RAM
HDD: 256kb EEPROM (maybe more if my music format gets bloated)
DjFi: Computer to router to interwebz system
MaxHtml: Possible html parser.
OS: MotOS for regular things, MotoConsole for testing
Filesystem: FAT
DjAPI: A small assembly based API for creating 'apps'

no, it won't have multithreading.

This will take a very, very long time, as I don't know much about ZCPU yet :P

My notes:
Color scheme for sockets:
Dark Green: Extra Ram Slot
Red: Cartridge Slot
Blue: Screen

[WhiteWolf]

This is an awesome idea. PM me if you ever need some help.
Steamname: Sodaguzzler



Edit: Also, first reply. Fistpump.

[neos300]

I probably will, as this project will probably one of the most complicated projects (excluding BP's stuff)
Ill keep updating this thread as I go along.

[Schilcote]

Seems like everyone has an OS but me .

[N00bDud3]

I tried to do something like this in CPU once, but the keyboard's buffer is screwed up. Cell 1 returns current key press, and the other 31 buffer cells do nothing. Cell 0 doesn't hold the number of keys in the buffer, and no other buffer cells fill up. This may have been fixed already though, IDK. If it is fixed, I'll have to start learning CPU again.

[robertark]

I tried to do something like this in CPU once, but the keyboard's buffer is screwed up. Cell 1 returns current key press, and the other 31 buffer cells do nothing. Cell 0 doesn't hold the number of keys in the buffer, and no other buffer cells fill up. This may have been fixed already though, IDK. If it is fixed, I'll have to start learning CPU again.

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

[Nikita]

Seems like everyone has an OS but me .

My thoughts exactly.

[Nicolai1]

Seems like everyone has an OS but me .

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.

[Xandaros]

That's quite true...

But if you read the specs of this one, it could end up in a real OS.
It has the possibility of reading cartridges, FAT file system and it will be broke into BIOS and OS.

Now the only Question will be: Will this ever be finished?

I once (halfheartedly) tried to make my own Computer. I didn't even finish the BIOS. The Input didn't really work well and the Output was useless without a proper OS.

Xan

[Schilcote]

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.

BulkOS is pretty "real" too. It's more of a microcontroller BIOS than an operating system though.