Hi Enrico, > What I need to know to proceed, is how you guys configure FreeDOS at > compile time. In particular, I need to assign an initial value to > variables like: "f_nodes_cnt", or structures like "buffers" list...
That is not a compile time thing. Most of those variables are in kernel.asm and the List of Lists, where they either have hardcoded initial values (f_nodes_cnt is 0) or are initialized by zeroing out memory areas or by calculating values during kernel init. You cannot use filenames / pathnames longer than 67 (but the LFN mapped to them with drivers like DOSLFN can be longer). You cannot use UNICODE filenames either (the filename charset depends on your codepage / dos font, and it is recommended to use plain ASCII). Again, DOSLFN can help, it supports some subsets of UNICODE for the long file names. To mount partitions, they are added to some array or linked list of drive properties. Also used for ramdisks and networked/nonfat drives. Read the initdisk.c code starting at dsk_init() / ReadAllPartitionTables() and the things which call it, such as init_kernel() and FreeDOSmain(). Then you will also know what FreeDOS does between "boot sector" and "read config sys". The latter is done in config.c and is probably interesting for you to read IF you plan to use BUFFERS. Maybe you do, as it makes porting easier. Make sure you do not implement too much of init_kernel(), or you may end up adding the whole FreeDOS kernel to FFS ;-). In particular, the kernel can relocate itself to HMA memory, and there are various device drivers. Eric ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
