Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
It might be worth adding that recovery software, depending on the method used, doesn't always work too well with text files (such as software source code). If it recovers the files using left-over structures in the filesystem, it will know where the file is supposed to be and how long it is, but as most modern filesystems overwrite these structures for security reasons modern recovery software tends to depend more on the structure of the file to determine where it starts and ends (this only works if the file isn't fragmented, of course). This doesn't work with text files because, unlike common office and media file formats (for example), they don't have standard headers/footers/blocks/size fields that can be used as a "signature" to locate the file and obtain information about it.
When you start writing an OS you do the minimum possible to get the x86 processor in a usable state, then you try to get as far away from it as possible.
onlyonemac wrote:It might be worth adding that recovery software, depending on the method used, doesn't always work too well with text files (such as software source code). If it recovers the files using left-over structures in the filesystem, it will know where the file is supposed to be and how long it is, but as most modern filesystems overwrite these structures for security reasons modern recovery software tends to depend more on the structure of the file to determine where it starts and ends (this only works if the file isn't fragmented, of course). This doesn't work with text files because, unlike common office and media file formats (for example), they don't have standard headers/footers/blocks/size fields that can be used as a "signature" to locate the file and obtain information about it.
Not *quite* true for source code; C files, for example, will have a bunch of "#include" near the beginning most of the time.
mariuszp wrote:Not *quite* true for source code; C files, for example, will have a bunch of "#include" near the beginning most of the time.
Although that's still somewhat "fuzzier" than locating a true header and using the structure of the file to determine its size.
When you start writing an OS you do the minimum possible to get the x86 processor in a usable state, then you try to get as far away from it as possible.
Basic OS Update:
1.Finally finally finally managed to finish the backspace, was having an awful bug.
2.Finished command framework, added help lists and descriptors.
3.Finished scrolling, I decided to clear the entire screen.
4.Implemented couple of commands.
5.As you can see my PIT and uptime counter both work.
6.Conclusion: terminal framework is finally "finished" and ready to be called stable.
Attachments
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
octacone wrote:Basic OS Update:
1.Finally finally finally managed to finish the backspace, was having an awful bug.
2.Finished command framework, added help lists and descriptors.
3.Finished scrolling, I decided to clear the entire screen.
4.Implemented couple of commands.
5.As you can see my PIT and uptime counter both work.
6.Conclusion: terminal framework is finally "finished" and ready to be called stable.
Finally, someone has given his OS the same name as I have , but it was centuries ago.
octacone wrote:Basic OS Update:
1.Finally finally finally managed to finish the backspace, was having an awful bug.
2.Finished command framework, added help lists and descriptors.
3.Finished scrolling, I decided to clear the entire screen.
4.Implemented couple of commands.
5.As you can see my PIT and uptime counter both work.
6.Conclusion: terminal framework is finally "finished" and ready to be called stable.
Finally, someone has given his OS the same name as I have , but it was centuries ago.
Techel wrote:Well, calling it Basic OS is very original
xD
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
Here is Obsidian OS with a new window design. I have also removed almost all graphical applications, for the moment.
I'm focusing now on OS stability and I'm also trying to make the OS much simpler. GUI apps will be re-added later.
Obsidian OS - Command Processor
"Open source seems to embrace the dark side of human nature." - Ville Turjanmaa
f2 wrote:Here is Obsidian OS with a new window design. I have also removed almost all graphical applications, for the moment.
I'm focusing now on OS stability and I'm also trying to make the OS much simpler. GUI apps will be re-added later.
[attachment=0]-snip-
I like this one better. Stick with it.
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
f2 wrote:Here is Obsidian OS with a new window design. I have also removed almost all graphical applications, for the moment.
I'm focusing now on OS stability and I'm also trying to make the OS much simpler. GUI apps will be re-added later.
[attachment=0]-snip-
I like this one better. Stick with it.
Yeah, me too. It remind me twm, an old window manager on Unix/Linux:
"Open source seems to embrace the dark side of human nature." - Ville Turjanmaa