Only one program is missing and that is a Scan-Disk (written as 2 words) utility for Fat32. For what I kow, DOSFSCK is working and need only a small fixes in the read sector.
I strongly disagree.
:( see beloww
Our SCANDISK for FAT1x is completely defunct, so we have no SCANDISK in the meaning of "nice looking user interface to the CHKDSK and DOSFSCK engines" at all.
I agree :)
My DOSFSCK-2.8-FAT32 currently works okay, but a working 2.10 port would be much better.
IIRC ther is some bug in this version that is _not_ related to the dos port and it behaves strangely with some fat erros. Again IIRC this is ok in next version...
I hope Imre can find the time to add working lowlevel disk access drivers to 2.10 (does not work at all for me for FAT16 in FreeDOS). It would not be THAT hard.
That is what I said.
Have a look at my 2.8-FAT32 (can only read, only compiles okay in Turbo C, not in Borland C,
as dosfsck is a Linux program, it will probably work well only under DJGPP. For the Fat32 version this is ok as it need lots of memory anyway.
see recent absread discussion) and Imres 2.10, maybe YOU can help us and provide a working "can read and write all FAT types" 2.10 ...
I wish I could help. FWIK, you (Eric) have some knowledge about it and Andreas has too but he will be too busy in the next few months. I will have some free time next month, but I don't even know where to look at to start :(
I was just hoping that your previous work with lbacache would make it easyer for you ;-)
What else is missing?is is my particular and very BIASED opinion:
RAMDISK problems are a bit vague... Maybe even kernel related.XMSDSK is 100% functional and free _can_ be used
?? are these rally bad or are they related to uncommon file systems?FDISK - The newest 1.21 (?) version seems to be better than 1.20, but I think there are still important bugs on some systems. Updates planned?
But I am confident that something will come around soon ;-)FORMAT - With all feedback from "Fritz" and Johnson I still could not figure out why running FreeDOS FORMAT under Windows creates broken FAT32. All boot sector fields look okay for me but still the root directory is accessed at the wrong place by Windows.
MODE and KEY ...are underway thanks to Aitor
FreeCOM should at least fix the following bugs / problems:
Overwriting file by nonexisting file zaps file.I believe this is fixed
Context memory has a memory leak.?? looks bad
Renaming dir with trailing \ makes it disappear.?? looks bad
Most other problems I (personaly) don't see as show stoppers
Alain
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
