i am developing a simple file system in assembly rn wich is based of FAT but with a FAT size of 256 limiting the total file system to 256kb(with 512 byte clusters) wich should be way more then enough. but to save computation and memory a path has to be of the following form "/WINTOWS1.DIR/SOMEDIR.DIR/EXECUTABLE.EXE", and if this doesnt save anough bytes it can also be turned into a flat filesystem wich would save a lot of memory since you have to do way less string parsing
trcmkr: well i do dev soon after this planing and then acctuly make a ms dos thing and then i can do it well i know dos but idl yet how to do stuff on the r3
is there a r2/r3 version already being developed or is this just planning? either way, sick! +1
yeah i only need to use 5-30% dpending how much i need from the RAM as Virtual Memory
you would also want a port that can take in small storage devices, the purpose i had in mind being making installing programs easier. and higher level languages for making the creation of programs easier
i may reccomend the R3 for speed preferably with alotta cores and definetly with pixel plotting mode on the terminal (terminal mode definetly will work for DOS though, but pixel plotting mode will allow for a GUI and... basic graphics, really) i like the idea +1
but a single tasking kernel should totaly be doable, and maybe some cooperative multitasking but you would need position independend code for that(wich i dont know if the r3 suports)
very cool idea but currently i dont think there is a storage device that interfaces with the r3 so that would have to be made first. then to make a usable os you would have to write a basic single tasking kernel with a file system, for the file system i reconmend a FAT16 like fs as it is simple and has all of the features that you need. and a GUI is way too resource intencive since you have to draw fonts on the cpu wich is extremely resource intensive.
That's very ambitious, executables might be limited without features like virtual memory
i dont care if it gets many views nor votes i only want if i can get help or smth
i am developing a simple file system in assembly rn wich is based of FAT but with a FAT size of 256 limiting the total file system to 256kb(with 512 byte clusters) wich should be way more then enough. but to save computation and memory a path has to be of the following form "/WINTOWS1.DIR/SOMEDIR.DIR/EXECUTABLE.EXE", and if this doesnt save anough bytes it can also be turned into a flat filesystem wich would save a lot of memory since you have to do way less string parsing
trcmkr: well i do dev soon after this planing and then acctuly make a ms dos thing and then i can do it well i know dos but idl yet how to do stuff on the r3
is there a r2/r3 version already being developed or is this just planning? either way, sick! +1
you would also want a port that can take in small storage devices, the purpose i had in mind being making installing programs easier. and higher level languages for making the creation of programs easier
That's very ambitious, executables might be limited without features like virtual memory