<a name="l8"></a>* ZealOS does not figure-out </span><span class=cF2>FAT32</span><span class=cF0> short name alias numbers. </span><a href="https://tomawezome.github.io/ZealOS/Kernel/BlkDev/FileSysFAT.html#l646"><span class=cF4>FAT32DirNew</span></a><span class=cF0>(). It can cause hard drive corruption, so it might
<a name="l10"></a>make us ruin the beautiful shiny-new ZealOS with that!" </span><span class=cF2>FAT32</span><span class=cF0> is also unappealing because it is in patent limbo. </span><span class=cF2>FAT32</span><span class=cF0> might
<a name="l11"></a>get removed from ZealOS. There is the </span><a href="https://tomawezome.github.io/ZealOS/Doc/RedSea.html#l1"><span class=cF4>RedSea</span></a><span class=cF0> 64-bit file system that works perfectly well. </span><span class=cF2>FAT32</span><span class=cF0> is useful, however, because
<a name="l14"></a>* The </span><a href="https://tomawezome.github.io/ZealOS/Compiler/OpCodes.html#l1"><span class=cF4>asm opcodes</span></a><span class=cF0> names were changed to remove the ambiguity between insts with different numbers of arguments, making the </span><span class=cF4>
<a name="l15"></a></span><a href="https://tomawezome.github.io/ZealOS/Compiler/Asm.html#l1"><span class=cF4>assembler</span></a><span class=cF0> simpler and minimal 16-bit asm support was done, since 64-bit is what you should be using, unless you're doing a </span><span class=cF4>
<a name="l29"></a>* </span><a href="https://tomawezome.github.io/ZealOS/System/Gr/GrPrimatives.html#l1018"><span class=cF4>GrEllipse3</span></a><span class=cF0>() is broken on transformations.