[edwardh1]

I reposted this to make it clearer that I just get the "finder unexpectedly quit" prompt/error message that my finder has quit.
But there is nothing wrong with the finder. Click OK and move on.
9.2.2 on a beige G3
desktop pattern comes up, then the hard drive icon come on the screen with the few aliases I have on the desktop, and then about one or so seconds later the prompt comes on: "finder has unexpectedly quit, save....."
I click Ok and move on.
I changed extension sets last week to add CD function and I loaded some tax table updates, then reset the extension set to where it had been. Have trashed finder preferences
now it does this. was OK before
Related to extensions loading since it happens after the desktop comes up could the extensions order do it/ how do you change that?
where does this prompt/message come from?

[WebFusion]

Lots of clues to what is happening -- the change of extension sets is possibly cause of extension conflict. If you want to change the order of loading, change the name of some extensions you suspect (add an extra space or two before the name, or other symbols ~ * ^ or even Option-8, The Big Black Dot). That works in the apple menu also, to change the order of things in there.
1. re-bless the system folder (open the System folder, drag the System Suitcase to desktop, close the System F. -- drag the suitcase over the Sytem F icon and release)
2. Rebuild the desktop
3. If the finder unexpectedly quits again after all that, come back and let us know.

[edwardh1]

Thanks - finder has not quit i just get the error message.
Someone in another forum suggested trashing the
1. finder preferences --I have done that no change
2. system preferences- what will change in the operation of the machine and need resetting if I trash these???
3. Mac OS preferences- same question what will change and where are these? - i looked in APplication folder and in system folder.

[WebFusion]

You continue to insist: "I only get the error message that my finder has quit.
But there is nothing wrong with the finder" - if it says it quit, then it really has, and you are only assuming it is fine because you get the finder (desktop) to appear after dismissing the message.
Go ahead and do the steps outlined in my post, starting with the extension conflict resolutions and the System reblessing. Go ahead and trash System prefs and Find File prefs, they'll only reset to default anyway. By the way, in my experience, a corrupted font suitcase will bring down the finder in the way you describe, allowing you to continue to the desktop as if nothing had actually happened (although it did, behind the scenes).
Removing the Fonts folder from the HD:System Folder is an easy way to eliminate a corrupt font --- the System will create a fresh empty folder on reboot and you can copy fresh fonts from the system CD as needed Drag them onto the closed System Folder, NOT into the Font Folder itself. The mac will put them neatly away.

[edwardh1]

thanks- in the above post reply you said:
assuming it is fine because you get the finder (desktop) to appear after dismissing the message.
the desktop appears first and stays on , then the hard disc icon loads then the finder quit prompt appears. the desktop is always there.
make any difference??

[WebFusion]

Are you still getting the error after doing some troubleshooting and reconfiguring? Strongly suspect fonts. I remember the advice first offered in the original 'Macs for Dummies' (Thank you, David Pogue, wherever you are)
He suggested that the fonts could be a problem sufficient to bring up a System Bomb! Only once did I have a bomb, and sure enough, a corrupted font was the culprit. You are not at that stage, so it's still relatively simple to verify what is causing the error (and yes, if you get to the desktop first, and then receive the error while the mac is trying to display the main HD icon, that does indeed sound like the finder itself crashing, and then recovering).

[edwardh1]

Thanks you said:
"then receive the error while the mac is trying to display the main HD icon,"
nope, I get desktop background , then hard disc icon comes on the scren , then the two aliases I have, then wait 1 sec and you get the error prompt.
Its not "trying to display the HD icon" - the icon IS displayed, then the error message
make any difference or help in diagnosis?????

Maybe related? Above problem is at the office - machine works so I am hesitant to fool with it too much.
At home I also have a 9.2.2 G3 with a G4 processor. Today I cut off two extensions
Open transport, and OT ALSM.
when I restarted, I got the same type finder quit as i get at the office. I changed back the extension set to add those two back in and on restart did NOT get the finder quit.
Office machine per my records DOES have the two extensions enabled, tho I will check.
what about OT and OT aslm being absent would cause this?????????? what do they do?

[WebFusion]

No, the diagnosis is the same -- your finder is crashing!
Open your system folder in the Office mac. In the Extension folder, rename the OT (open transport) extension with a space before the name. Then do OT ALSM with Option-Shift-8 before the name (makes a bullet). That will change the order they load, nothing else. If that works, go about your day and keep smiling.
(BTW, why did you decide to focus on the OT extensions?)

[edwardh1]

thanks
maybe solved- it went away based on two (2) cold starts not giving the prompt after I added all at once:
control panel - location manager
extensions:
DNS plug in
draw sproket lib
find by content
location manager
xtnd power something
any idea why these did it (thois was written in the paper puter records as having fixed it 2 years ago. Any idee?????????

[WebFusion]

Dude, for someone who was afraid to "mess with" the computer at the office, you certainly did some serious messing! Anyway, to answer the question you asked - yes, by adding new ones, you changed the loading order of the extensions, and that achieved the same result as my original suggestion to just rename a few extensions with extra spaces and ~ * symbols to change their load order.
Happy to see you are good to go. /forums/ubbthreads/images/graemlins/grin.gif

[edwardh1]

your suggestion on the loading was a good one, as when the screen came up the ext seem to keep loading for a few seconds in time when error (used to) comes up