CyclonePC and OS

[Nikita]

Project is live again! Wooo!

Cyclone is an operating system that runs primarily on zCPU. It is nearing version 1.

Here is a list of features, also a todo list:

Working features:
- number library
- string library
- printf, scanf
- memory allocation
- variadic functions
- basic shell
Currently working on:
- filesystem
To do before the release:
- iostream
- multitasing
- bootstrapping
Planned for future versions:
- window system
- interprocess communication
- sound support
- security features
- networking via Multi-Socket Radio

23 DECEMBER 2011

Below are some posts from an ancient era.

[Schilcote]

Sorry, but this is WAY over... (umm... forget the word, overblown?)... What you're trying to do is more that what BP's WireOS does, and BP is the smartest person here.

Sorry, it's just impractical. I suggest you start with something much, much simpler.

[Black Phoenix]

Doesn't mean you shouldn't even try, you might need to write two or three iterations of your OS before it will be able to do all said above. You might discover a lot of interesting stuff during your research and code writing, and there are people who will help you when you have specific questions.

[Tasuit]

I agree with BP, you should'nt say "Dont do this because BP is smarter then you!".
Besides, i find your post abit offensive, saying that BP is the smartest here, what gives you the right to say such thing?.

[Whodunnit]

its true until we prove otherwise :P

[Tasuit]

I dont have to prove anything, infact this isnt about who is smartest
- but would you like somebody telling you "hey, im smarter then you, and i cant do it, so dont even try"?

[Tasuit]

Sorry for double post, but any progress on this?

[Nikita]

CPU E2: 2500 instructions per second (you have to increase softquota by a thousand), encapsulated in a timer. Remove a few timers to get it working at normal rates... For some reason timers absolutely hate being inside conditional statements, or having variable time set.

Code: pastebin - collaborative debugging tool
It explains the current instruction set in the #comments.

I am currently trying to figure out how exactly do wirelinks work, if I want them modifiable from both ends. Wirelink seems to be the only way information can be transmitted between modules fast enough.

[Black Phoenix]

CPU E2: 2500 instructions per second (you have to increase softquota by a thousand), encapsulated in a timer. Remove a few timers to get it working at normal rates... For some reason timers absolutely hate being inside conditional statements, or having variable time set.

Code: pastebin - collaborative debugging tool
It explains the current instruction set in the #comments.

I am currently trying to figure out how exactly do wirelinks work, if I want them modifiable from both ends. Wirelink seems to be the only way information can be transmitted between modules fast enough.

You want to use shared RAM, and they are called "hispeed links" for a reason (wirelink is just E2 name for them, and few more things)

[Nikita]

Shared RAM? Not sure which one do you mean, tried normal memory gates, and they don't react to wirelinks. But dinamic memory does! And it's maximum size is for some reason around 2MB. Persistant means it gets stored on the hard disk?
Okay testing shouldn't be a problem now.

Edit: WOOHOO! I can't belive it! I wrote a 7 word program in machine codes and it executed them from first try with no mistakes!

(It's counting up ^^)Now for something more complicated.