Posts: 7,564
Threads: 643
Joined: Sep 2024
Reputation:
0
A have a permission that can't be repaired, a plist file for my fax program which resides in the root level Library folder; could this file possibly be causing my system to hang during bootup/login, even though that app is not a startup app?
Do all plist files get read during login?
I've trashed all the identified unrepairable files (as noted by DW fixing permissions) and currently am 1/2 way through 8,000 files being emptied from the trash at about 116 per minute (the tempo of the Colonel Bogie march for those who never needed to memorize tempi as part of their musical training).
Posts: 10,000
Threads: 626
Joined: Jul 2020
Reputation:
0
> could this file possibly be causing my system to
> hang during bootup/login, even though that app is
> not a startup app?
Potentially, if your fax software uses a kernel extension... but if so then it's a file-corruption issue and not a permissions issue.
> Do all plist files get read during login?
No. They are basically preference-files. If a program stores preferences in a plist file then when it runs it will read the file.
> I've trashed all the identified unrepairable files
I'm very grateful you're not doing my tech support.
Posts: 10,000
Threads: 626
Joined: Jul 2020
Reputation:
0
> I don't seem to have any way of weeding out or fixing corrupt files
Your drive seems to have serious problems.
Assuming that it's directory corruption and not a hardware malfunction, and assuming that you have a "healthy backup" that is a working clone, this is what you should do:
(First step) Back up recently-changed document files of any importance.
Erase the problem-drive.
Install the OS on the newly-erased drive and perform all necessary OS-updates.
Run the Migration Assistant to import your user-accounts, home folders, network settings and applications from your backup.
Copy back the files from the first step.
Is there any particular reason why you haven't done this?
Posts: 10,000
Threads: 626
Joined: Jul 2020
Reputation:
0
> Do you really think using Migration Assisstant is
> better than cloning from a backup that runs smoothly?
Whatever went wrong with your original, it could also be wrong with the clone, just waiting to make your life miserable again as soon as you start using it regularly.
Going the MA route, you have an almost-virgin System and Library and a spare admin account in case you need to troubleshoot. It also means that any troubleshooting that you have to do will almost certainly be restricted to stuff in your Home folder, thus making troubleshooting a heck of a lot easier.
> And, oh, any value to zeroing the internal rather
> than just erasing IYO?
Generally, no. Not unless the DU or DW is reporting bad sectors.
...You seem to be doing much more than just backing up a few user files and restoring from a good clone.
Why are you still using DiskWarrior, mucking about deleting files and digging through your /System and /Library folders?
Posts: 10,000
Threads: 626
Joined: Jul 2020
Reputation:
0
> Remember when macs were the ones that you could
> fix by replacing a few bad files, and PCs were the
> ones where every little problem meant reinstalling the OS?
That era ended in late 2001.
[Edit] Except for the bit about PCs.
