I've just been wrestling with the OSKit, which the Flux Group cannot be bothered to document properly. *Sigh*
Anyway, I managed to get the multiboot "hello, world" kernel compiled and linked, but has a dump of many hundreds if not thousands of lines of errors that flew by so fast I couldn't possibly see what they were about. When it finally stopped, mid-way through printing something (run out of video memory? Whatever...) it said something about a "bad trap."
Anyone know what this is and why it happened?
Damn it... the OSKit would be a dream come true, if only it was properly and completely documented...
Anyone use OSKit?
Re:Anyone use OSKit?
I evaluated and dismissed OSKit before it even hit the compiler, for lack of documentation, structure, and ease of use.
Every good solution is obvious once you've found it.
Re:Anyone use OSKit?
I have to say, you're wiser than I am. OSKit sucks heavily for the reasons you've given and I've wasted so much time, I'm almost ready to send them a bill.Solar wrote: I evaluated and dismissed OSKit before it even hit the compiler, for lack of documentation, structure, and ease of use.
Re:Anyone use OSKit?
Actually, it was mostly the UNIX-like structure and the COM-like component interfacing that did set me off, since my OS project aimed at a "from scratch" approach to things - think things over before you do them just like everybody else.
So you're not to blame. OsKIT *does* look good at first glance.
So you're not to blame. OsKIT *does* look good at first glance.
Every good solution is obvious once you've found it.