OSDev.org

Okey so first of all i hate MS lets just get that out there no offense to any of those Hardcore Gates fans but anyways....

I want/already am starting a project in (how ironic) Visual Basic to create a form application to hopefully make it a little simpler to build a simple working OS

Any Input would be nice...also if anyone spent the time to learn VB in depth your help would be greatly appreciated

the form isnt to create an os all the way but more or less a basic outline to add in extra stuff later...if that made any sense...sry im very uuuuum tired.....


The Project is going to be called the AesycOS Builder (names not important really) based of of my own OS name AESYCOS....


meaning An Easy Simple Yet Complete Operating System (funny thing is the complete part kinda contradicts it in a way)
<>anyways feed back would be nice if you have anything to say just email me at [email protected].
~~ Peaz and Tanks!!! ~~~

If this uses your OS as a base, why not just create a customizable build service for it that allows you to set options?

-JL

i think he/she means that they're making a program that will construct the code for a basic OS based on a set of choices, rather than using his/her OS as a base

Ugh. That is all.

I agree with James, what we do here, coding at the level that we do, is an art form, something that requires a lot of work and skill...
It isn't something that should be prostituted to the likes of a auto make wizard, where all you have to do is click boxes to add IRQ's another for ISR and yet another to add a floppy driver...
Any way creating this would just in crease the flow of idiots who've read a hoax website and believe that it's their ticket to riches and being famous..., that was an insult to everything we do here..., the worst being when people who obviously know nothing about what we do, start telling us we don't know about this and that...
It really isn't a good idea to open OSdev to just anyone in my honest opinion, they first have to prove themselves by climbing the mountain to get here, not downloading a wizard...
If you do go through with this, this is what will happen...
Also, I do not believe that an OS coded by somebody who used a wizard would ever get anywhere, because they just wouldn't know enough about it and the workings of an OS to take it that distance...
Sorry for being so direct, but that just what I think...

Jules

P.S. Hate is a strong word, dislike is probably closer to the truth...

On one side I agree with suthers, but on other it can be useful to have a clicable wizard. It can be used in education. You can "click" base for your system and add or rewrite something in it.

I started working on a click-to-make bootloader with some customized functionality specified by the user. It is my first project using Ruby. I'm not looking to downplay the work put into os development, but using this as a tool to pump out a bootloader as a base framework to build upon later.

I am still a newbie at os dev, and im currently writting my first os. I may not be the worlds best assembler or pascal coder but i am getting through the tough task ok. I agree with james and everyone else who thinks this is a bad idea. I have spent so much time learning to program asm and reading up on theory and i would find it some what insulting for a newbie to just use a click interface and say they coded an os.

I think being able to provide a mechanism for a new OS developer to enter appropriate variables such as stack locations, floppy sector load locations, gdt descriptors and entries, and other things would be a good way for them to be able to get a conceptual understanding before being thrown into the fires of assembly in a bootloader.

I have made a program that allows new os developers to see their conceptual understanding get put into a practical implementation (bootloader) without having to jumble learning assembly and learning how to use it to perform bootloading tasks. This is a good thing because once it has been generated, it is just a .asm file that can be opened, examined, learned from, and modified later once the new developer has a better grasp on things. Also, seeing a working impelementation with their input is a great moral booster and will hopefully have them decide to not give up on it just from the daunting task of bootloading.

Also, it makes my life alot easier as I can just put in a few positional variables and out pops a bootloader suited for whatever I needed it for. It's not meant to replace coding your own bootloader, but it should be used as a learning tool.

I understand what you're saying, but you should be aware that this has been discussed several times before no useful tool emerging from the discussions. (I really hope someone doesn't make an application that has a built in "GUI and App Designer", with options such as "Select the scheduler algorithm to use:" "Select the drivers to include inside the kernel:", and if you buy the Pro version for $99 you can edit the C code.)

What you're describing sounds like it would be better suited being in the form of macros for a common IDE, or a template that someone can use as a starting ground.

There are several excellent tutorials on the Internet that can get your kernel to a somewhat usable level, while fully explaining the process as you go, which in my opinion I believe will help a beginner far more than a template with a few comments.

hey guys thanx for the input and honesty the one thing im most glad for about the people at this site is that you guys, at least seem to be fully honest and direct with your opinions god is it frustrating when people skip around with what they mean....anyways....

ummm....to explain a little more on what the project was to be was not like "here people, put w/e the f*ck you want into these boxes, check some boxes over here, choose this or that, but abide by these limitations" the project was merely going to be a compilation and compromise of tutorials and resources into 'a wizard' that follows the same procedures that these 'walkthroughs' already on sites like http://www.osdever.net/ follow and set the basis, like some said, for a beginning shell to an operating system that developers can use to start off with or study to help with learning os design concepts and implementation. This is supposed to me more of a learning aid as opposed to be some f*cked up os builder so people can put their names on sh*t they didnt do and show off like some a$$hole...i've met a few like that...

What this project would do is put chosen parameters into a more practical form to aid in the process of learning osdev...

i wouldnt want to give people the answers to a problem if they havn't even tried to work it out on their own i would only give hints...(not that i have all the answers anyways)

and i agree with you guys some one should not have the cheating availability to just skip to the finish line and get awarded the gold if that makes any sense...
(((NOTE: sorry i put guys out there alot if there are any females that are offended you are included in that general statement of 'guys')))

You may have a point or explanation in there somewhere, but it usually skip lines that contain profanities, therefore I may have missed it. No one should be spoon-fed anything, they should have the conceptual knowledge of something before diving into the subject, but that doesn't make everyone an instant assembly/C programmer that can turn that conceptual know-how into source code.