Hi Eric, thanks for your detailed and clear answer.
What I'm doing is "borrowing" (with respect to the license) the filesystem and producing a, freestanding (i.e. NO OS dependancies), run-to-completion (no semaphores, no critical sections...), self-consistent, pure ANSI C filesystem for embedded platforms. On top of this layer of code, I'll put the C standard library (*) which calls the following set of functions: open ( ), close ( ), creat ( ), read ( ), write ( ), lseek ( ), unlink ( ) (*) I borrowed from MINIX 4 years ago and fully tested. Floating points are handled by the assembly library of the specific platform. > In short: When a DOS app wants to read a file in FreeDOS, we get: > APP - int 21.3f - DosRead - DosRWSft - rwblock - dskxfer - execrh - > block device driver - blockio - LBA_Transfer - fl_... - int 13 - BIOS. > The BIOS is what finally talks to the hardware to fetch the data. Please, correct me if I'm wrong: The starting point of my port should be the following set of functions: "DosOpen()", "DosClose(), "DosRead", "DosWrite",... And not the following set: "dos_open()", "dos_close(), "dos_read", "dos_write",... > I hope readers of the mailing list archive will enjoy this > walkthrough or at least the summary, too ;-). > Sure did! Enrico ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-modeĀ di Wind http://i-mode.wind.it/ ------------------------------------------------------------------------- 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
