Help me making a o.s. in FAT32 and with a better tutorial
-
nuno_silva_pt
Help me making a o.s. in FAT32 and with a better tutorial
Help me making a o.s. in FAT32 and with a better tutorial
-
Pype.Clicker
- Member
- Posts: 5964
- Joined: Wed Oct 18, 2006 2:31 am
- Location: In a galaxy, far, far away
- Contact:
Re:Help me making a o.s. in FAT32 and with a better tutorial
$> syntax error ... please redo from start.
what do you mean ?
what do you mean ?
-
distantvoices
- Member
- Posts: 1600
- Joined: Wed Oct 18, 2006 11:59 am
- Location: Vienna/Austria
- Contact:
Re:Help me making a o.s. in FAT32 and with a better tutorial
I think he has asked this before.
What kind of programming language should that be .. fat32?
I use to think of it as filesystem, but this brings an other light to it ... it's really a shame that i cannot help.
What kind of programming language should that be .. fat32?
I use to think of it as filesystem, but this brings an other light to it ... it's really a shame that i cannot help.
... the osdever formerly known as beyond infinity ...
BlueillusionOS iso image
BlueillusionOS iso image
-
Mr_Spam
Re:Help me making a o.s. in FAT32 and with a better tutorial
a small OS written in assembly that uses FAT32 is menuet. take a look at it and it can help you implement FAT32.
-
Therx
Re:Help me making a o.s. in FAT32 and with a better tutorial
Just to clairfy I think what he said before was that he can't use a seperate partition so it must run on the windows partition. I can't see this being a problem. Install a multiboot loaded set up an option and one for your own OS (some kernel file on the windows partition) Or does GRUB etc. not support FAT32?
-
Pype.Clicker
- Member
- Posts: 5964
- Joined: Wed Oct 18, 2006 2:31 am
- Location: In a galaxy, far, far away
- Contact:
Re:Help me making a o.s. in FAT32 and with a better tutorial
okay, so, nuno_sliva_pt, here are your options (from the safest to the most risky)
1. install a pc emulator such as bochs. Your filesystem will be on a standard file that you will pass to bochs and bochs will present this to your OS as if it was a real disk
2. If you have pure MS-DOS under Windows, write a small .EXE program that will replace the normal booting sequence. This is what my own SOS.EXE does.
That EXE program will load your "own filesystem" out of a regular file and put it in memory (just like a RAMDISK). It is limitated but it will allow you to wait for a crash machine.
3. focus on the floppy disk for now. Have your OS booting and file access from the floppy only. You will have to support FAT12 instead of FAT32.
However, i suggest you use already-existing tools to create that floppy (GRUB, PARTCOPY, RAWRITE, etc): i had once the unpleasant experience of mixing "IDE0" and "FLOPPY0" drive numbers in a small tool i wrote for a multi-boot program... and i screwed up my partition table
4. create your filesystem within a legacy file (c:\myos.fs) and consider it as a partition in your OS. I suggest you only do this when you're sure your IO routines works fine (using thechnique 1, for instance)... HAve that C:\MYOS.FS file a SYSTEM file so that windows can't move it.
5. try to find a second (small) HDD from someone upgrading his and install it in your father's tower. Be sure your driver will not get the wrong drive ID, though ...
Hope this addresses your question. If it doesn't, please rephrase.
1. install a pc emulator such as bochs. Your filesystem will be on a standard file that you will pass to bochs and bochs will present this to your OS as if it was a real disk
2. If you have pure MS-DOS under Windows, write a small .EXE program that will replace the normal booting sequence. This is what my own SOS.EXE does.
That EXE program will load your "own filesystem" out of a regular file and put it in memory (just like a RAMDISK). It is limitated but it will allow you to wait for a crash machine.
3. focus on the floppy disk for now. Have your OS booting and file access from the floppy only. You will have to support FAT12 instead of FAT32.
However, i suggest you use already-existing tools to create that floppy (GRUB, PARTCOPY, RAWRITE, etc): i had once the unpleasant experience of mixing "IDE0" and "FLOPPY0" drive numbers in a small tool i wrote for a multi-boot program... and i screwed up my partition table
4. create your filesystem within a legacy file (c:\myos.fs) and consider it as a partition in your OS. I suggest you only do this when you're sure your IO routines works fine (using thechnique 1, for instance)... HAve that C:\MYOS.FS file a SYSTEM file so that windows can't move it.
5. try to find a second (small) HDD from someone upgrading his and install it in your father's tower. Be sure your driver will not get the wrong drive ID, though ...
Hope this addresses your question. If it doesn't, please rephrase.