On Mon, Feb 21, 2022 at 11:33 AM Prime Seal <sealpri...@gmail.com> wrote:
>
> Dear Sir[Jim Hall]
>
> I like FreeDOS but I have noticed the shortage of documentation of different 
> formats e.g downloadable PDF. There is also a lack of documentation of kernel 
> customizations for compilation.
> making it unfriendly for forking. I once commented on you YouTube channel 
> about UPX giving errors. I have also noticed that FreeDOS does not have python
>


If you start at the "Source Code" page on the FreeDOS website
<https://www.freedos.org/source/> and click on "Kernel Source Code"
you'll end up at Jeremy's GitHub: <https://github.com/FDOS/kernel>

And if you click on the "docs" directory, you'll find a bunch of
documentation about the kernel, including "build.txt" about how to
build the kernel. This file says, in part:

> To build the operating system a batch file (BUILD.BAT) is included
> to make life easier.  This file is in the FDKERNEL directory of the
> distribution.  In addition, there is a corresponding batch file
> (CLEAN.BAT) to clean up the source directories.
>
> There is a CONFIG.B file that specifies all the paths and names of
> the compiler, assembler, etc. that you want to use.  You MUST copy
> it to CONFIG.BAT first, then edit it to reflect your setup.


and:

> The recommended compiler and assembler at the time of writing (2009/05/19)
> are OpenWatcom 1.8 and NASM 2.05.01.


and:

> Optionally, the kernel can be compressed using UPX. You can find
> UPX at http://upx.sourceforge.net. Simply adjust config.bat to
> enable it.


Other documentation files you'll find here:

bugs.txt build.txt config.txt contrib.txt history.txt index.md
intfns.txt lfnapi.txt memdisk.txt mkboot.txt nls.txt readme.cvs
readme.txt sys.txt


Why is PDF format needed? The kernel documentation is in plain text,
which is readable everywhere on every system.


_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to