New OS

[DeletedAccount]

Anyways who cares ? Its not my concern

[Troy Martin]

Welcome back, SphinCorp!

How's the project doing? Have you written a simple video driver yet? Are you using Pmode?

[pcmattman]

It's good to see you didn't get overly discouraged by the negativity here and went on to keep learning and keep working at it.

You need to always be trying to learn how to do something better, or how to do something new, or how something works, in OSDev. That's half the fun, I've found .

[inflater]

The post that started this thread was *three months ago*, not one year...

That was the first thing that gave me a slap when reading this article, too...

I deserve a second chance to prove myself to you guys

You surely do, but "I moved have moved beyond the magical world of managed code, to pure c++, then the win32 api" doesn't sound very good. At first, you need to know the whole bootstrap and the low level "what who where why" that occurs "behind the scenes" in a simplest Helloworld OS kernel, before OSdev itself.

You won't get far trying to use Win32 api or trying to program in C++ as a kickstart for your OS. Keep that as a advice, not as a insult.

Good luck.

Regards
inflater

[Troy Martin]

I deserve a second chance to prove myself to you guys

You surely do, but "I moved have moved beyond the magical world of managed code, to pure c++, then the win32 api" doesn't sound very good. At first, you need to know the whole bootstrap and the low level "what who where why" that occurs "behind the scenes" in a simplest Helloworld OS kernel, before OSdev itself.

You won't get far trying to use Win32 api or trying to program in C++ as a kickstart for your OS.

Yeah, you're going to need to learn assembly first. When I started, I thought, "Hell, I'll just learn the basics and use others' code!" Bad plan. Since then, I've learned how to read and write assembly language (mostly just real mode.)

That's my definition of "deserving a second chance." And you know what? I think I got it.

Keep that as a advice, not as a insult.

Seconded.

[SphinCorp]

School has kept me VERY busy for a long while, unfortunately I have given up on making my own OS. It's just not worth it at this point.

[jal]

I have given up on making my own OS. It's just not worth it at this point.

Duh! Good luck with your school stuff though.


JAL

[imate900]

I hope you revive this project.

--The IDontCareCorp.
----Anonymous

[ScorchOS]

Ditto.

This poster remind me a lot of me when I first started out (grand plans of 3D desktops and making millions of pounds and becoming the next Linus Torvalds). I wasn't treated so kindly when I tried to make out ScorchOS was the next big thing, but I've stuck with it because I'm passionate about the idea of creating my own OS kernel.

You learn a lot from your mistakes, and I hope the poster comes back as, despite the practicalities halting his ideas, it would be interesting to see something of them being realised.

[mathematician]

I have never attempted anything like this before, so bear with me:

I want to design my own OS. It will be called Sphinx-WAP OS. I already built a replacement Command Parser for windows called Sphinx-WAP. I have many ideas for it, like:

Memory auto correction: 1/2 of all RAM will be reserved in part for a system recovery dump, which will be 1 second or so behind the actual running system. Apps should also have partial dumps, and the ability to go "dormant" by extending it's dump. If an error occurs, the memory address is found, and the equivalent dump address is taken, then the error is corrected using dump info, which would be from 1 second ago.

I will soon create a fake screenshot of what I think it should look like.

I REALLY need help on this one guys, so anyone interested PLEASE email me. I can offer you free email and FTP services, and a zone on my server to make your own site.

Thanks in advance,
Richard Carson
Sphinx Gaming Inc., C.E.O., Founder

Using half of memory for a dump doesn't sound like a good idea to me. But if you want to go ahead with it you could try and familiarise your self with huffman encoding, so at least you don't need half of memory.

Normally you try to minimise the amount of time the operating system has control of the computer, so as to free up resources for applications. Shifting huge amounts of memory around doesn't sound like a good way to do that.

[stealther]

Memory auto correction: 1/2 of all RAM will be reserved in part for a system recovery dump, which will be 1 second or so behind the actual running system. Apps should also have partial dumps, and the ability to go "dormant" by extending it's dump. If an error occurs, the memory address is found, and the equivalent dump address is taken, then the error is corrected using dump info, which would be from 1 second ago.

Well... then... every application that crashes will be reverted to some particular state _before_ the crash and it will most probably happen in approximately 1 second again
Or maybe I just didn't got the idea right.
Good luck.

[Coty]

I will soon create a fake screenshot of what I think it should look like.

what? have you even started the kernel? anyone can dream of what they want it to look like

[manonthemoon]

Geez, would somebody pay attention to the post dates? The OP completely gave up months ago, and the original post is over a year old. Just leave this alone already