Desktop OS
Desktop OS
Hello everyone. This is an operating system I've worked here and there since 2003. It's a 32-bit operating system with multitasking/multithreading, dynamically loadable libraries and drivers, and some other things. Devices can point to dynamically created driver stacks for easy filtering and other cool tricks. For instance, I have a very simple cache driver that filters on top of the floppy device.
Devices can also provide a query interface to extend the object namespace, and this is how the filesystem drivers work. For instance, the floppy is typically mounted at /Boot Disk. If a request is made to open /Boot Disk/Desktop/Libraries/StandardC, the Boot Disk device (which in this case is provided by the Fat driver) is passed the remaining part of the path.
There is another component of the namespace, which starts at /System, and is case sensitive. This contains objects which are the actual processes, threads, drivers, etc. in the system. Running the info utility on any of these can provide more info. The processes also act as directories, which contain thread objects.
It will definitely run in VMWare, and should also run in Bochs, Virtual PC, and on a real computer. It's been a while since running it in anything other than VMWare though, so I can't vouch for that. A Pentium or greater is required. Check out the /Desktop/Utilities on the floppy disk to see what can be run.
Booting from CD-ROM and hard disk is also possible, it's just a matter of creating the image, installing GRUB, and tweaking the /boot/grub/menu.lst file.
Here's a link. On that page, you will find a download link to a recent floppy image.
Thanks for reading!
Devices can also provide a query interface to extend the object namespace, and this is how the filesystem drivers work. For instance, the floppy is typically mounted at /Boot Disk. If a request is made to open /Boot Disk/Desktop/Libraries/StandardC, the Boot Disk device (which in this case is provided by the Fat driver) is passed the remaining part of the path.
There is another component of the namespace, which starts at /System, and is case sensitive. This contains objects which are the actual processes, threads, drivers, etc. in the system. Running the info utility on any of these can provide more info. The processes also act as directories, which contain thread objects.
It will definitely run in VMWare, and should also run in Bochs, Virtual PC, and on a real computer. It's been a while since running it in anything other than VMWare though, so I can't vouch for that. A Pentium or greater is required. Check out the /Desktop/Utilities on the floppy disk to see what can be run.
Booting from CD-ROM and hard disk is also possible, it's just a matter of creating the image, installing GRUB, and tweaking the /boot/grub/menu.lst file.
Here's a link. On that page, you will find a download link to a recent floppy image.
Thanks for reading!
- piranha
- Member
- Posts: 1391
- Joined: Thu Dec 21, 2006 7:42 pm
- Location: Unknown. Momentum is pretty certain, however.
- Contact:
Hmm......I like....
Do you have the source available, or is it closed-source?
-JL
Do you have the source available, or is it closed-source?
-JL
SeaOS: Adding VT-x, networking, and ARM support
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io
- crazygray1
- Member
- Posts: 168
- Joined: Thu Nov 22, 2007 7:18 pm
- Location: USA,Hawaii,Honolulu(Seriously)
- crazygray1
- Member
- Posts: 168
- Joined: Thu Nov 22, 2007 7:18 pm
- Location: USA,Hawaii,Honolulu(Seriously)
OK, I've got it working again under Bochs. New image is here. I have not noticed any slowness with input under Bochs or VMWare.
Currently it's closed source, although I haven't ruled out releasing the code.
Currently it's closed source, although I haven't ruled out releasing the code.
- Brynet-Inc
- Member
- Posts: 2426
- Joined: Tue Oct 17, 2006 9:29 pm
- Libera.chat IRC: brynet
- Location: Canada
- Contact:
Amazing
I tried it out in bochs and it worked wonderfully but there seemed to be a big lag when I was examining the directories. Great job though, can't wait to see more.
NULL
I have a debugging option enabled in this build which outputs information to the serial port; the FAT driver uses it quite a bit, so this could be part of the slowness. I'll try to remember to disable that in the next image I post. The FAT driver is also not well optimized, especially in the directory listing code, so that is probably the other problem.
Directory listings done within /System should be fast at least.
Also, to note, the path separator is a forward slash, not a backslash, so that's why 512dev's initial cd command did not work.
Directory listings done within /System should be fast at least.
Also, to note, the path separator is a forward slash, not a backslash, so that's why 512dev's initial cd command did not work.