MOS Release 2.0
MOS Release 2.0
Hi guys....
first time my os site is out.... I'v lot of plans ahead but now MOS Version 1.0 can be seen at
http://www.themosland.110mb.com
This is in a trivial state.... but have some good plans for enhancement in future...
Please have a look and give feedback here OR
mail me at [email protected]
first time my os site is out.... I'v lot of plans ahead but now MOS Version 1.0 can be seen at
http://www.themosland.110mb.com
This is in a trivial state.... but have some good plans for enhancement in future...
Please have a look and give feedback here OR
mail me at [email protected]
Last edited by prajwal on Wed Jul 22, 2009 11:57 pm, edited 2 times in total.
Hi...
Nice work... Although your OS has still to achieve a lot, its simple & sweet...
Great to see a chap from India working on this (like me ).. All the very best... I would like to see the updates on your project...
Some weird questions:
1. In which language you are coding MOS?
2. Your floppy driver seems to shut the motor too offen, Is it doing so? If so then I suggest to keep a timer which shut it off after say 30 sec of motor off command.
Comments are welcome on my OS too.. I guess you had download the image of TAJ.. Hows it?
Nice work... Although your OS has still to achieve a lot, its simple & sweet...
Great to see a chap from India working on this (like me ).. All the very best... I would like to see the updates on your project...
Some weird questions:
1. In which language you are coding MOS?
2. Your floppy driver seems to shut the motor too offen, Is it doing so? If so then I suggest to keep a timer which shut it off after say 30 sec of motor off command.
Comments are welcome on my OS too.. I guess you had download the image of TAJ.. Hows it?
hi Viral... Yes I did download your OS the day before I launched the site...
I ran it under Qemu Emulator....
Sorry I couldn't login... I have posted this question in ur site asking for user/pass
U have replied it.... I'll try it today night....
Regarding ur Qs
1. I have developed it in C (with asm at some places)
2. Yes the floppy driver is playing with motor on/off... thanks for the suggestion.... i'll correct it...
I ran it under Qemu Emulator....
Sorry I couldn't login... I have posted this question in ur site asking for user/pass
U have replied it.... I'll try it today night....
Regarding ur Qs
1. I have developed it in C (with asm at some places)
2. Yes the floppy driver is playing with motor on/off... thanks for the suggestion.... i'll correct it...
MOS Release V2.0
After a long gap I finally made it to MOS Version 2.0
This time I did put a bit of effort in building a website eating away my time which I could have dedicated for MOS development.
Friends!! please have a look and give your valuable feedback.
http://www.themosland.110mb.com/
Thanks,
- MosMan
This time I did put a bit of effort in building a website eating away my time which I could have dedicated for MOS development.
Friends!! please have a look and give your valuable feedback.
http://www.themosland.110mb.com/
Thanks,
- MosMan
- Combuster
- Member
- Posts: 9301
- Joined: Wed Oct 18, 2006 3:45 am
- Libera.chat IRC: [com]buster
- Location: On the balcony, where I can actually keep 1½m distance
- Contact:
Nice work. It runs smoothly under QEMU
However, I tried it on a real box and got the following messages:
Floppy initialisation [ FAILED ]
IDE initialisation [ FAILED ] (there is no IDE controller - only SCSI)
and no login prompt
On Microsoft VirtualPC it refuses to switch to a console. The kernel output seems ccorrect though
Bochs floods error messages about unsupported vga writes, invalid DMA commands, and writing to read-only registers. I can switch consoles, but once again there is no login prompt
However, I tried it on a real box and got the following messages:
Floppy initialisation [ FAILED ]
IDE initialisation [ FAILED ] (there is no IDE controller - only SCSI)
and no login prompt
On Microsoft VirtualPC it refuses to switch to a console. The kernel output seems ccorrect though
Bochs floods error messages about unsupported vga writes, invalid DMA commands, and writing to read-only registers. I can switch consoles, but once again there is no login prompt
Hi all,
Just wanted to update Project Status...
Accomplished
1. stdio portion of libc ported successfully with minor customizations.
2. nasm, ndisasm ported successfully
Working On
Bug Fix:
1. Already implemented edit (text editor) chrashing. Bug narrowed down to sprintf() call. Working on it with high priority.
2. Files created in "msh" shell are not reflected in subsiquent "ls" command till user umount/mount filesystem or logs in and logs out of shell.
UpComing
1. Port ld and other related binutils and try to build exes on MOS using nasm
2. Implement simple Signal Handling System or in general a Messsage Handling System.
Release Plan
MOS Version 2.5:- After completing UpComing - 1
MOS Version 3.0:- After completing UpComing - 2
Thanks,
- MosMan
Just wanted to update Project Status...
Accomplished
1. stdio portion of libc ported successfully with minor customizations.
2. nasm, ndisasm ported successfully
Working On
Bug Fix:
1. Already implemented edit (text editor) chrashing. Bug narrowed down to sprintf() call. Working on it with high priority.
2. Files created in "msh" shell are not reflected in subsiquent "ls" command till user umount/mount filesystem or logs in and logs out of shell.
UpComing
1. Port ld and other related binutils and try to build exes on MOS using nasm
2. Implement simple Signal Handling System or in general a Messsage Handling System.
Release Plan
MOS Version 2.5:- After completing UpComing - 1
MOS Version 3.0:- After completing UpComing - 2
Thanks,
- MosMan
Re: MOS Release 2.0
Though slow but I have made some decent progress with this project...
Accomplished
I have ported following into MOS
1. binutils/gas
2. binutils/ld
3. cc (old version - do not remember at this point )
How did it go !!
Did a test with a simple hello world c program
1. which I wrote on MOS using edit (mos editor),
2. compiled to .s using cc,
3. assembled to .o using as and
4. finally linked with -lc and generated .exe using ld and ran it successfully....
By the time I got the above work completed, I came across many bugs and limitations imposed by mos design. I fixed most of the bugs.
I have some key issues open with FileSystem caching and File Write. Asof now, I only know the problem and don't know why and where ! Will work on this coming weekend. Basically - FS Table geting corrupted on copying large file and also system becomes dead slow while copying large files and eventually hangs
Upcoming:
1. Fix these critical issues with FileSystem caching, File Write
2. Implement File Locking (atleast internal -> not allowing 2 processes to open file in write mode)
3. Implement a simple Process Signal/Message handling system -- Mostly I will resort to a Message Handling thing which also supports Singnal Handling Feature (- Signal Handler Call Back ) not sure yet !
Accomplished
I have ported following into MOS
1. binutils/gas
2. binutils/ld
3. cc (old version - do not remember at this point )
How did it go !!
Did a test with a simple hello world c program
1. which I wrote on MOS using edit (mos editor),
2. compiled to .s using cc,
3. assembled to .o using as and
4. finally linked with -lc and generated .exe using ld and ran it successfully....
By the time I got the above work completed, I came across many bugs and limitations imposed by mos design. I fixed most of the bugs.
I have some key issues open with FileSystem caching and File Write. Asof now, I only know the problem and don't know why and where ! Will work on this coming weekend. Basically - FS Table geting corrupted on copying large file and also system becomes dead slow while copying large files and eventually hangs
Upcoming:
1. Fix these critical issues with FileSystem caching, File Write
2. Implement File Locking (atleast internal -> not allowing 2 processes to open file in write mode)
3. Implement a simple Process Signal/Message handling system -- Mostly I will resort to a Message Handling thing which also supports Singnal Handling Feature (- Signal Handler Call Back ) not sure yet !
complexity is the core of simplicity