Hi
I made a virtualbox VM with a 12gb hard drive and a base install with
source.
Running dosfsck -a -v took around 90 seconds approximately. My host
system is an i5/sata/windows 10.
Running on 86Box was different. I'm sure part of it is because 86box
intends to be cycle accurate.
Here's my notes from that:
16mb:
"Reading file allocation table." (took approx 2 min)
"Checking files and directories" (took 7 minutes)
"Reclaiming unconnected clusters. (took 1 minute)
64mb:
"Reading file allocation table." (took approx 1 min)
"Checking files and directories" (took 8 minutes)
"Reclaiming unconnected clusters. (took a few seconds)
86Box/build 2533/[i430TX] ADLink NuPRO-592
...another difference is that I had open watcom and other compilers and
packages unpacked in 86Box. I'm not sure that makes a lot of difference
though.
On 8/16/2020 10:52 AM, Eric Auer wrote:
Hi!
As you use an emulator, can you try with 32 or 64 MB RAM?
You can also tell dosfsck to be more verbose, which might
help to know at which phase things are taking too long.
Regards, Eric
It was dosfsck 2.11 DOS3, 8 Aug 2007; the version from FreeDOS RC3. I
was using it on a 12gb hard drive.
But this was in 86Box (emulating a Pentium 133 with 16mb of ram), so the
problem may have been with the emulator and not with the program.
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
