hello, i'm experiencing the same issue as Elrainia. I'm running MacOS 10.15.3 and PathFinder 9.0.5. Please can someone from the Cocoatech team acknowledge that they have seen this thread and will act on it.
I've wrestled with the NFS/Catalina/PathFinder issues at various times over the last 3 months and although this isn't a solution that's going to be acceptable to most. This is what I've done:
1) Migrated away from NFS to SMB. I don't have any faith that Apple are going to support NFS going forward.
2) Changed my workflows so as not to need auto mounting (as much). I've switched from some code I wrote back in 2001 (used to backup various systems using rsync over NFS) to TimeMachine backing up to a NAS over SMB.
3) Sadly, I've almost ditched PathFinder for ForkLift 3. I've been with PF for the best part of 15 years, but the level of support (or lack of it) has lead me to look elsewhere. ForkLift is missing a few features that I love in PF, but it's speed, simplicity and the way it handles network drives has pushed me to the point where PF is no longer my default file manager.
I hope everyone wrestling with similar NFS issue finds their way through the mire sooner rather than later...
I have also been a paying customer for a long time. I see this NFS problem has been known about for multiple years and i see closed discussions without resolution. I guess if you need to use NFS go elsewhere.... I was kinda getting annoyed with the version nags anyway.
I’m sorry, but I posted this issue on Dec 7th last year and didn’t get any response. I struggled on until the new year, but we finally gave up and deleted PathFinder from 7 machines and installed ForkLift3 which has worked flawlessly for us since then. It was a tough decision as I’ve been an advocate of PF since v4.5 (which is well over 10 years) but the lack of support has ultimately driven me away. I had a question about licensing from last year too, and to date, no reply to that either.
I wish you all well in these troubling times and beyond,