PFS and the PFSDoctor - does it work ?

[Torti-the-Smurf]

Hi Folks.

Some of you know for sure if the PFSDoctor 1.6 will work with PFS3 All in One (Tony Wilen & Co )
https://aminet.net/package/disk/misc/pfs3aio

PFSDoctor 1.6 sees it as a PFS-II 19.2 Is that normal ?

You see;
Today i got an error message while booting the WB that a certain Font and a Prefs setting would be missing.
But those files where present. Very Odd.

So i tried PFSDoctor but it did report Zero Errors.

I have a recent backup of this HardDiskFile (using it on the FPGA MIST)
and that was quickly resolved, but now i am wondering.

Does the PFSDoctor 1.6 not work with the newest PFS ?

I think i have heard something about that, but any info or a link to a working PFSDoctor would be Mega Sweet.

The last thing i want is corrupt files

Thank you very much

[Toni Wilen]

Old pfsdoctor works, at least if drive is less than 4G, not all >4G modes are supported by old pfsdoctor. (But in that case you would get huge amount of errors from pfsdoctor..)

Usual case for disappearing file (if program does delete first and then writes file from scratch) or file not having latest updates is not waiting for buffer flush (few seconds) before reseting the system. This is by design.

[Torti-the-Smurf]

Thank you Toni

Its a HardDiskFile thats about 4,6 GB; Divided in 4 patitions (about 1GB each).

[Torti-the-Smurf]

I did also tried the "experimental pfsdoctor" (the CLI only) but it always say

DEVICE dh0: not found
EXITING ...

Why ? I used the command like this: Pfsdoctor check dh0:

Any ideas ?

[Turran]

No colon on the device if I remember correctly.
pfsdoctor check dh0

[Torti-the-Smurf]

Funny; i use AMIGA´s sice 1987 and would never had come to the conclusion to NOT make a "colon" after a Drives Name

Thank you so much Turran it worked

(but where does it reports the Errors ?
Could not see any; well i have zero errors on every drive with the "old/normal PFSDoctor",
so .... maybe thats why , but a point that says "zero errors" would be neat )

Thanks again Turran, very appreciated

[PoulpSquad]

I was tinkering the other days with an older versions of PFSDoctor with mixed results.

Checking a small partition of a few MB (about 55MB) went ok, but checking a bigger partition (rest of the virtual drive, 4095-55 MB) resulted in thousands of errors, and PFSDoctor "choking" to death after a few seconds.

Increasing the number of stacks to about 5M did the trick and PFSD could complete the test (errors were still found, 4000+ of them).

Long story short, the drive was fine, PFSDoctor Experimental never raised any issues with it, and repairing the 4000+ imaginary errors with the older version of PFSD messed up the the file system badly.

On the other hand, after letting old PFSD butcher the disk, I could see how PFSD Experimental warns of an error. As long as the drive is OK PFSDE will do its thing and exit without any warnings. If there are errors, it will warn you in clear terms (sorry, I didn't think about taking a screenshot!).

Hope this helps... Be super careful when you're using older, mismatched versions of tools like PFSD, make backups of your drive(s)!

[Mr. Toast]

Originally Posted by Torti-the-Smurf

Funny; i use AMIGA´s sice 1987 and would never had come to the conclusion to NOT make a "colon" after a Drives Name

Googling for answers brought me to this thread! I was scratching my head to figure out why I couldn't get PFSdoctor to scan a volume and incredibly grateful to find out why. Face palm moment.

[Torti-the-Smurf]

Thanks PoulpSquad for that useful Info

@ Mr.Toast; who could blame us;?...there is usually always a Colon after the Volume name