Hi Enrico, > In principle, I would like FFS to be able to handle > pathnames longer than 67 and possibly read Unicode filenames.
But then it would not be compatible to FAT. If you want to have long unicode file names, then you have to implement exactly that - LFN. Look at doslfn. But watch out, some aspects of LFN are still patented by Microsoft. If you just say "infinite number of subdirectories", then you still get FAT at first glance, but many operating systems will get confused by deep nesting sooner or later. Among them of course DOS. Some DOS APIs use fixed size data structures. Having UTF8 is a similar problem - if you use 8.3 names for UTF8 data, you get like 5.1 names ;-). Of course you can already get quite far in the western world with Latin1 file names or some similar DOS codepage / font for the names. > Do you think I'll be to produce > a port that doesn't depend on "struct dhdr"? Basically the main purpose of the table of device headers is to know which function to call for sector read/write on which drive letter, so it should be quite easy to short- circuit around that. You could stop at dskxfer or maybe (w/o BUFFERS) even at rwblock, but you will need your own code to handle partitions if you drop all the "execrh / blockio / LBA_Transfer / fl_* part in the chain below: > APP - int 21.3f - DosRead - DosRWSft - rwblock - dskxfer - execrh - > block device driver - blockio - LBA_Transfer - fl_* - int 13 - BIOS. 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 Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
