• 0

How to build an operaing system ?


Question

Recommended Posts

  • 0

"ReactOS is an Open Source effort to develop a quality operating system that is compatible with Microsoft Windows® applications and drivers."

"The kernel has come a long way and is quite stable and many APIs are complete enough for higher level work to be done. Substantial work has been done on many libraries. Initial networking code is there, but unusable for the moment. A basic implementation of the Graphics Device Interface (GDI) and a VGA graphics driver is paving the way for a GUI. The amount of developers is steadly increasing."

its realy nice os, and you can use losts of windows software on it

they even have a live cd version

  • 0

1- Mostly x86 Assembly and pure C, C++ was not really a good choice at that time

2-Run it under an emulator, Vitual PC and Vmware works fine, use bochs if you need a free one

3- You absolutely need know to x86 Assembly to make the Master Boot Record and some parts of the kernel. Assembly is the lowest level language you can program with if you dont want to learn all the x86 OPcodes. They are numbers that means something to the processor like making an addition etc...

4- Windows 95/98/me all relied on a dos subsystem, in Me it was simply hidden, you can even get a patch to return to DOS from Me. They just had no choice or else no one would be using windows at that time, because customers needed perfect compatibility wth DOS programs to use old softwares that was popular at that time. Window NT/2000/XP was made with stability in mind, not compatiblity, they are able to run DOS programs but in a CONSOLE which is not DOS but only program which tries to emulates. That's why a lot people complained about certain DOS programs not functionning correctly or at all with XP, XP was the first microsoft attempt to bring an NT OS to "normal" users. WinXP is just Windows 2000 with a better user interface and better compatibility with games, just look at the build numbers of win2000 & XP, 2000 is windows NT5 and XP is 5.1 . Longhorn, the next windows, will be windows version 6.0 which should be a significant upgrade from XP.

So... You want to make an OS, learn some assembly, pure C or C++ ( which is not as bad for that than it was before it was standardized ) and have lots of patience. Start by reading how to make MBR and some x86 specific stuff like gate A20, gdt, ldt , interrupts and last but not least, protected mode. If you don't know C/C++ start learning it before thinking of doing anything. And don't even think of doing a user interface before a lot of things is implemented. You actually have to reinvent the wheel, you have to access hardware like the video card directly to write something on the screen.

If anything i said is not 100% correct, just tell me in a correct way.

Thank you

  • 0
I can tell you that Windows is written in C and C++, with small amounts of assembly in places. Linux, mostly C++ from what I understand. DOS, who knows (or cares) ;)

Linux is written in C, Linus torvolds the creator has said a million times that C++ is slow because it has extra overhead. Just so you know ;)

  • 0
Linux is written in C, Linus torvolds the creator has said a million times that C++ is slow because it has extra overhead. Just so you know ;)

585816262[/snapback]

Got it (Y)

But you didn't need to revive the thread just to tell me that. You could have sent a PM or something ;)

  • 0
Wow, for such a smart guy(Linus), that sure is an ignorant thing to say.

585816478[/snapback]

But Linus is right. For an OS, you want to spend as little time in kernel space as possible and that means you don't want to deal with the overhead of C++ (exceptions, RTTI). Also, C++ uses a lot of stack space. You only have a limited stack (8k or 4k) in the kernel. Another feature of C++ that gets in the way is name mangleing(sp?). When you have to mix languages, dealing with name mangleing is one more thing you have to worry about.

  • 0
Thanks for bumping the thread. The first three pages are ****ing comedy!

585817579[/snapback]

Yes, it's extremely funny. Until you realize that these people aren't trying to be funny.

Now it starts to lose it's charm.

It starts to become disturbing. You realize that these people actually exist and that they actually think, speak and react in this manner. It's frightening to think that these people believe that they are being clever.

This does not bode well for the future of mankind. I don't think there's any legal way to stop them from spreading there malformed genes into future generations. You can't just go around shooting the idiots and dumping them into a big hole. Although I have considered it in the past. I don't think we'll get that far with that method.

We must educate the poor losers. We must somehow convince them that they should not reproduce.

Well this is far too deep of an issue for the pages at Neowin.

  • 0
But Linus is right.  For an OS, you want to spend as little time in kernel space as possible and that means you don't want to deal with the overhead of C++ (exceptions, RTTI).  Also, C++ uses a lot of stack space.  You only have a limited stack (8k or 4k) in the kernel.  Another feature of C++ that gets in the way is name mangleing(sp?).  When you have to mix languages, dealing with name mangleing is one more thing you have to worry about.

585817508[/snapback]

That's assuming you use RTTI, and program in an OO way. C++ doesn't force you to do either. Concerning mangling, extern "C" fixes that. Linus implies that you have to use all the features of C++, if he truly said what was posted. And if that is the case, that is why I think it was ignorant. I'd be surprised if Linus didn't have more to say about programming style instead of the language. You can program in an OO way in C, too.

  • 0

if your gonna make an OS.. make a good one for starters LOL

or even an OS, at your expierence level, i'd be surprized.

but lemme give you some advice...

an OS takes years and years to profect.. and you need to know ins and outs of computers

an OS is millions of lines of code. and... if you can get passed 10,000, i'll personally shake your hand.

im not trying to put you down, but look at how many employees work for microsoft. i bet more then 60% of them work in creating / improving, or in some sorta way, have their hand in the creation of an OS.

  • 0

Thanx a lot for people who posted links to learn from it, and no thanks for people who is trying to depress me. Just tell me what you know or stop posting.

Do i said that i want to make OS like windows :blink: , i just want to make an OS for my self, happy now !

*Thread redownloaded for summer holiday*

and please can some one help me in this thread :

https://www.neowin.net/forum/index.php?showtopic=311820

I think I will find my solution from Neowin.net after 10 useless posts :rolleyes:

  • 0
Not necessarily - Unix was created using C. So was Linux for that matter.

585819807[/snapback]

Correct me if i'm wrong, but isn't Assembly necessary at times, to interface with hardware? Like wouldn't Assembly be required to write some of the fundamental aspects which then a higher-level language can use off, i.e. C, C++.

Btw why the hell isn't this thread locked already?

  • 0
Correct me if i'm wrong, but isn't Assembly necessary at times, to interface with hardware? Like wouldn't Assembly be required to write some of the fundamental aspects which then a higher-level language can use off, i.e. C, C++.

Btw why the hell isn't this thread locked already?

585820040[/snapback]

The thread remains open because it is a valuable learning resource. It also demonstrates the complexity and sheer size of an operating system.

And assembly is necessary, at least for the kernel and some hardware interface. Unix was not created entirely with C code.

  • 0

first pages of this threads are jokes. but i guess he is learning. but i agree with something posted in here before: you should just do the shell for windows which will do all you want. now that would be useful and realistic. and i think it is the more important part of you final idea. and if you get your ai interface think to work nicely - that you can think of writing underluying ssytem. not before.

  • 0
The thread remains open because it is a valuable learning resource. It also demonstrates the complexity and sheer size of an operating system.

And assembly is necessary, at least for the kernel and some hardware interface. Unix was not created entirely with C code.

585820982[/snapback]

In that case perhaps you should strip away the non-informative bits of the thread if possible.

  • 0
Btw why the hell isn't this thread locked already?

.....

John:

The thread remains open because it is a valuable learning resource. It also demonstrates the complexity and sheer size of an operating system.

.....

In that case perhaps you should strip away the non-informative bits of the thread if possible.

585821443[/snapback]

:yes: :yes: :yes:

I tend to agree with Winston, this thread should be closed. maybe create a new sticky thread on building an OS?

I think we pick on Elagizy way too much in this thread to allow people to bring it to life again.

  • 0
WinXP has a command prompt, not DOS.

Just because it looks like DOS doesn't mean it is DOS.

585829659[/snapback]

correct.

earlier windows used DOS.. and i believe since windows NT, they changed to Command Prompt.

  • 0

The only DOS in Windows XP is the DOS virtual machine used for running legacy apps. This is not unlike what happens when you load Virtual PC. The DOS virtual machine thinks that it is DOS and thinks that it had direct access to the system, but really it's running in a "sandbox." When it makes a call to the hardware, Windows XP's compatability layer says "Oh, the DOS VM wants to access the hardware directly. That's not allowed any more, so I'll just give it the answer it wants and only pretend that it actually accessed the hardware."

Any non-blank autoexec files you find on your system are either:

A) Leftovers from a previous DOS/Windows 9x installation, or

B) Used to set environment variables (like the PATH statements posted before) so that programs running in the VM can find things they need.

There really isn't much more to it than that.

The Windows NT kernel bears no relation to DOS in any conceivable way. It most closely follows the design of OpenVMS (whose creators developed NT for Microsoft). In many ways it is comparable to the Mach kernel that Apple's OS X runs on top of. NT relies more heavily on threading, which makes it more scalable in multi-processor situations. However, both NT and Mach are built to be simple, versatile kernels on which you can run pretty much on any platform and support pretty much any user-space system (just like Apple runs FreeBSD on top of Mach, and Microsoft runs various "subsystems" on top of NT - including Win32, POSIX, OS/2, etc).

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Glow 26.10 by Razvan Serea Glow provides detailed reporting on every hardware component in your computer, saving you valuable time typically spent searching for CPU, motherboard, RAM, graphics card, and other stats. With Glow, all the information is conveniently presented in one clean interface, allowing you to easily access and review the comprehensive hardware details of your system. Glow provides detailed information on various system aspects, including OS, motherboard, processor, memory, graphics card, storage, network, battery, drivers, and services. The well-organized format ensures easy access to the required information. You can export all the gathered data to a plain text file, facilitating sharing with others for troubleshooting purposes. No installation needed. Just decompress the archive, launch the executable, and access computer-related information. Glow runs on Windows 11 and Windows 10 64-bit versions. Glow 26.10 changelog: New Features The bootstrapping algorithm has been completely redesigned. The software can now launch directly without requiring TS Preloader. As part of this change, the startup splash screen displayed during initialization has been removed. In addition, spikes in CPU usage have been eliminated, resulting in a more stable architecture with significantly lower memory consumption. The Microsoft Office detection infrastructure within the Operating System section has been enhanced. Additional detection support has been added for Office C2R (Click-to-Run) installations. Furthermore, the license status evaluation system has been improved, and the priority order has been revised as follows: Licensed > Grace Period > Other (NOTIFICATIONS, EVALUATION, etc.). Glow now includes preliminary support for Wi-Fi 8 technology, allowing more detailed information to be displayed for Wi-Fi 8-compatible network adapters. Glow now provides full support for Bluetooth 6.2. Adapters supporting Bluetooth 6.2 can be analyzed in greater detail and with improved accuracy. The disk distribution view in the Disk section has been modernized, replacing the traditional table layout with a new 2×2 card-based design. The TS Custom Controls module has been updated to v26.7. Thanks to the new custom controls, all Türkaysoft applications now offer a more modern and consistent user interface aligned with Windows 11 design standards. Bug Fixes Potential line-ending handling issues in the Office detection code within the Operating System section have been resolved. Additionally, the output format has been standardized to UTF-8 to prevent character encoding issues and ensure consistent data processing. Several stability and file management issues within the Debugging infrastructure have been addressed. Problems that prevented new log files from being created after Debugging was disabled, as well as issues causing debug records to be lost, have been fixed. File deletion and reaccess issues that occurred after file locks were released have also been resolved. In addition, a bug that caused newly recreated log files to remain locked after deletion has been eliminated. Unnecessary blank lines within debug logs and the extra empty line that could appear at the end of log files have also been corrected. A shortcut key conflict caused by assigning identical hotkeys to both the DNS Test Tool and the Donation page has been fixed. The DNS Test Tool can now be accessed using CTRL + Shift + D, while the Donation page is available via CTRL + Alt + D. Changes The service responsible for providing the Public IP Address and Internet Service Provider information in the Network section has been updated to use the ipinfo.io infrastructure. This change improves the accuracy and consistency of the displayed data. (No external requests are made while Hiding Mode is enabled.) Some terms in the Dutch and Korean language files have been updated to make them clearer and more user-friendly. [TS Updater] Before the update process begins, users are now prompted to choose whether they would like to view the release notes. Note: Always unzip the program before using it. Otherwise you may get an error. Download: Glow 26.10 | 1.8 MB (Open Source) Links: Glow Homepage | Screenshot | Github Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Maradona if hydration breaks had existed in Mexico 86.
    • The quantum search for Time's origin had an equally mind-boggling conclusion by Sayan Sen Image by Steve Johnson via Pexels A theoretical study from researchers at the University of Surrey suggested that the direction of time may not be fundamentally fixed in certain quantum systems. The work, published in Scientific Reports, examined how the “arrow of time” could emerge from microscopic physics and found that time-reversal symmetry can remain intact even in models used to describe processes such as energy loss and thermalisation. The arrow of time refers to the observed one-way direction from past to future in everyday life. In macroscopic processes, this is easy to see. Spilled milk spreads across a table and does not gather back into a glass, and heat flows from hotter objects to colder ones. These processes shape the common sense idea that time moves in a single direction. However, at the level of fundamental physics, many equations do not prefer a direction of time. Time-reversal symmetry means that the same physical laws can describe a system whether time moves forward or backward. This has made it difficult to explain why irreversible behaviour appears in the large-scale world even when the underlying rules do not require it. Dr Andrea Rocco, Associate Professor in Physics and Mathematical Biology at the University of Surrey, described this contrast: "One way to explain this is when you look at a process like spilt milk spreading across a table, it's clear that time is moving forward. But if you were to play that in reverse, like a movie, you'd immediately know something was wrong – it would be hard to believe milk could just gather back into a glass. However, there are processes, such as the motion of a pendulum, that look just as believable in reverse. The puzzle is that, at the most fundamental level, the laws of physics resemble the pendulum; they do not account for irreversible processes. Our findings suggest that while our common experience tells us that time only moves one way, we are just unaware that the opposite direction would have been equally possible." The study focused on open quantum systems, which are quantum systems that interact with a surrounding environment. This environment, often described as a heat bath, can exchange energy and information with the system. The researchers used this framework to study how a direction of time might appear even when the underlying physics does not enforce one. A key part of the analysis involved the Markov approximation. This is a simplification used in many models where the system is assumed not to retain memory of its past states. The idea is that changes depend only on the current state, not on earlier history. This is commonly used when studying thermalisation, which is the process where a system settles into equilibrium with its environment. The study also used concepts such as master equations, including the Lindblad and Pauli equations, which describe how probabilities of different quantum states change over time. Another related model discussed was quantum Brownian motion, which describes the random-like movement of a quantum particle interacting continuously with its environment. In these descriptions, a “memory kernel” can appear, which is a mathematical term that accounts for how past states influence current behaviour. The researchers found that applying the Markov approximation did not break time-reversal symmetry. Even when the system interacted with an effectively infinite heat bath, the resulting equations of motion remained symmetric in time. This meant that the same mathematical description could, in principle, run forward or backward in time without contradiction. The study further showed that standard frameworks used in open quantum systems, including quantum Brownian motion and master equations like the Lindblad and Pauli forms, could be written in a time-symmetric way. These equations are typically used to describe processes that look irreversible, such as dissipation and thermalisation, but the results suggested they can also be interpreted as allowing evolution in both time directions. Thomas Guff, Research Fellow in Quantum Thermodynamics, said: "The surprising part of this project was that even after making the standard simplifying assumption to our equations describing open quantum systems, the equations still behaved the same way whether the system was moving forwards or backwards in time. When we carefully worked through the maths, we found that this behaviour had to be the case because a key part of the equation, the "memory kernel," is symmetrical in time. We also found a small but important detail which is usually overlooked – a time discontinuous factor emerged that kept the time-symmetry property intact. It’s unusual to see such a mathematical mechanism in a physics equation because it's not continuous, and it was very surprising to see it appear so naturally." The researchers also noted that deriving a one-way arrow of time from time-reversal symmetric microscopic dynamics remains an open problem across fields such as thermodynamics, statistical mechanics, particle physics, and cosmology. Their results suggested that some standard descriptions of irreversible behaviour in open quantum systems may be better understood using a time-symmetric formulation of Markovianity. According to the study, processes such as thermalisation, which are usually treated as irreversible, could in theory be described in a way that allows evolution in either time direction under the same rules. This does not imply that time reversal occurs in everyday life, but rather that the underlying equations do not strictly enforce a single direction. Overall, the findings suggested that the perceived direction of time may emerge from how physical systems are modelled and approximated, rather than from a fundamental asymmetry in the laws themselves. The researchers noted that this perspective could have implications for ongoing work in quantum mechanics, thermodynamics, and cosmology on the origin of time’s arrow. Source: University of Surrey, Nature This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing
    • A bit premature... 100% Marketing. Bizarre.
  • Recent Achievements

    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      581
    2. 2
      +Edouard
      182
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      73
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!