BrokenThorn Entertainment

Any update on the next chapters?

Hoozim

Which line is causing it to crash?

The error could be caused by the fact that the loader loads the kernel into 16bit space. That means that the extra 512 bytes (1 sector) could be written into a vital data structure. This would cause a crash. For example, the kernel could expand into the page tables. When memory is next accessed, it ...

Any update on the next chapter?

What about graphics 2? Is there an ETA on that?

Ok, great. I can't wait.

When will the next series chapter be released? What about the next graphics chapter? The other chapters are excellant and I am looking forward to the next chapters.

It is fragmented. That is the point of the FAT table. To find the fragments.

Remember that if Windows is using unicode, you need to use an L before the quotes (L"\\\\.\\A:"). I don't know if this works with fstreams. Include "Windows.h" and use the CreateFile function (with the FileExisting bit set). Then read and write with ReadFile() and WriteFile() functions. These functi...

To put on all of the other files, just copy it like any other file. Then use a filesystem minidriver to find the file and load it.

Make your own application to do this with WIN32. That is what I did. It is really easy. Just simply open the device like a file ("\\\\.\\A:"). Then write to it.

A 'real' filesystem is needed for debugging. One major problem with a 'homemade' filesystem is the fact that you need to get files onto the media to test it. That means implementing the write function first. After getting the standard filesystems fully implemented, do try making your own filesystem....

You probably won't be able to find a practical implementation but it isn't that different. The closest I will be able to give you is the series which uses FAT12. Find the differences between FAT12 and FAT32 and it shouldn't be too difficult from there. Try implementing FAT16 since it is the easiest....

Yes, it is legal. Otherwise how would a MAC file work on Windows :wink: . Here is a little mini tutorial: The first 512bytes contain information on the media (the BPB section) and how it is formatted. Right after that are reserved sectors (you choose how many in the BPB). Then there is the FAT table...

Why not go with a standard file system like the FAT filesystems? Then your OS will be able to read Windows and Linux files. When implementing any file system, focus on code organization since there could be a lot. Use a virtual file system for user appeal. Seperate the file loading steps into sepera...