Hi Imre!

> > SCANDISK - this should be implemented as an user interface to DOSFSCK
> Yes, for this you should strip down dosfsck (throw out delayed writing and

I disagree: Delayed writing is perfectly useful because you can use the code
to create an UNDO LOG before actually changing the disk, very similar to the
"MS" SCANDISK feature of creating an undo floppy.

> the undelete feature). Then you should make it compile with turbo c++
> [Imre suggests a 16bit version...]

Disagree again: DOSFSCK can check FAT32 and uses lots of memory. There is
no real need for an 8086 compatible SCANDISK, and a 15 year old 386 already
has enough features to run a DJGPP/386 SCANDISK.

> After you can get this to run you could change all the input/output from
> the user to show up in dialogs, this should not be to difficult (might be
> a lot of work though?).

Yes, that is mainly what creating SCANDISK from DOSFSCK would mean. I think
code from Joes user interface for the old proof of concept SCANDISK can be
re-used for this.


This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
Freedos-user mailing list

Reply via email to