CS preference settings changing

wrote:

Out of the blues, the preference settings in PS CS (winXP) are all reset to defaults, and the browser and palettes locations, etc. are all screwed up. Now I have to change them. This happened once before. What is happening and how can this be prevented? Thanks.

When you do change them to what you want, save the changes. They’ll then be available to reload when your OS blows away your PS Prefs. file again.

—
John McWilliams

On Wed, 13 Jul 2005 12:39:02 -0700, John McWilliams
wrote:

wrote:

Out of the blues, the preference settings in PS CS (winXP) are all reset to defaults, and the browser and palettes locations, etc. are all screwed up. Now I have to change them. This happened once before. What is happening and how can this be prevented? Thanks.

When you do change them to what you want, save the changes. They’ll then be available to reload when your OS blows away your PS Prefs. file again.

This happens so frequently, on both OSs, that I think it’s a PS problem, not an OS problem. I don’t know of any other software where this happens with the frequency it does with PS, or even at all for most software.

—

Hecate – The Real One

Fashion: Buying things you don’t need, with money
you don’t have, to impress people you don’t like…

Hecate wrote:

On Wed, 13 Jul 2005 12:39:02 -0700, John McWilliams
wrote:

wrote:

Out of the blues, the preference settings in PS CS (winXP) are all reset to defaults, and the browser and palettes locations, etc. are all screwed up. Now I have to change them. This happened once before. What is happening and how can this be prevented? Thanks.

When you do change them to what you want, save the changes. They’ll then be available to reload when your OS blows away your PS Prefs. file again.

This happens so frequently, on both OSs, that I think it’s a PS problem, not an OS problem. I don’t know of any other software where this happens with the frequency it does with PS, or even at all for most software.

— you lack a space after –.

Have you a source other than anecdotal?

—
John McWilliams

I almost had a psychic girlfriend but she left me before we met.
[Stephen Wright]

John McWilliams wrote:

Hecate wrote:

This happens so frequently, on both OSs, that I think it’s a PS problem, not an OS problem. I don’t know of any other software where this happens with the frequency it does with PS, or even at all for most software.

— you lack a space after –.

Have you a source other than anecdotal?

The experience may be anecdotal only, but I concur. Photoshop preferences become corrupted so often that they’ve created a keyboard shortcut to delete and rebuild them rather than the old way of doing it manually. I have never had any file of any type on a system that became corrupted with such regularity.
——————
Tom

Unsolicited advertisements cheerfully ignored.

"Tom Thomas" wrote in message

John McWilliams wrote:

Hecate wrote:

This happens so frequently, on both OSs, that I think it’s a PS problem, not an OS problem. I don’t know of any other software where this happens with the frequency it does with PS, or even at all for most software.

— you lack a space after –.

Have you a source other than anecdotal?

The experience may be anecdotal only, but I concur. Photoshop preferences become corrupted so often that they’ve created a keyboard shortcut to delete and rebuild them rather than the old way of doing it manually. I have never had any file of any type on a system that became corrupted with such regularity.
——————
Tom

Unsolicited advertisements cheerfully ignored.

well I have only been reading this NG for a few months and it seems to be the NUMBER ONE problem we have all encountered. The only other most popular question is the CAPS LOCK/lost my brush cursor thing.

I had not seen that happen before and I used PS since 1996, but it happened to me this past weekend. Because I had read about it here I knew what to do or I would’ve reinstalled and driven myself crazy.
I renamed some files.
I think PS gets confused when it tries to crank up on ‘recently used files" that are no longer there.

On Wed, 13 Jul 2005 15:01:48 -0700, John McWilliams
wrote:

When you do change them to what you want, save the changes. They’ll then be available to reload when your OS blows away your PS Prefs. file again.

This happens so frequently, on both OSs, that I think it’s a PS problem, not an OS problem. I don’t know of any other software where this happens with the frequency it does with PS, or even at all for most software.

— you lack a space after –.

Have you a source other than anecdotal?

Not other than the large number of peoples on this and the comp.graphics.apps ng who find that their problems are cured by trashing prefs. There are so many different problems occurring all of which have the same solution, occur on multiple OSs and with such frequency that there is almost always at least one post on these ngs with that as the solution. Empirically, the fact that it happens on more than one OS and happens with such frequency leads to the conclusion it’s the software – along with the fact that I don’t see nay other posts on other newsgroups where the same, ort equivalent advice, turns up for other apps.

Now, do you have any source for your assertion other than your stated comment?

—

Hecate – The Real One

Fashion: Buying things you don’t need, with money
you don’t have, to impress people you don’t like…

Hecate wrote:

On Wed, 13 Jul 2005 15:01:48 -0700, John McWilliams
wrote:

— you lack a space after –.

Have you a source other than anecdotal?

Not other than the large number of peoples on this and the comp.graphics.apps ng who find that their problems are cured by trashing prefs. There are so many different problems occurring all of which have the same solution, occur on multiple OSs and with such frequency that there is almost always at least one post on these ngs with that as the solution. Empirically, the fact that it happens on more than one OS and happens with such frequency leads to the conclusion it’s the software – along with the fact that I don’t see nay other posts on other newsgroups where the same, ort equivalent advice, turns up for other apps.

Now, do you have any source for your assertion other than your stated comment?

What assertion? I doubt you are referring to the statement about your broken sig. delimiter, and I made no other in this thread.

It’s still rogered.

—
John McWilliams

Hecate wrote:

On Wed, 13 Jul 2005 12:39:02 -0700, John McWilliams
wrote:

wrote:

Out of the blues, the preference settings in PS CS (winXP) are all reset to defaults, and the browser and palettes locations, etc. are all screwed up. Now I have to change them. This happened once before. What is happening and how can this be prevented? Thanks.

When you do change them to what you want, save the changes. They’ll then be available to reload when your OS blows away your PS Prefs. file again.

This happens so frequently, on both OSs, that I think it’s a PS problem, not an OS problem. I don’t know of any other software where this happens with the frequency it does with PS, or even at all for most software.

That makes me feel better already: at least I’m not the lone sufferer. I ran out of scratch disk space during an edit and had to clean up the disk to save the file. After that, the Prefs were corrupted after PS was restarted. Not sure if PS has a problem with shuffling the disk space, but I’ll pay closer attention in the future.

Where is Chris Cox when we need him?

On Thu, 14 Jul 2005 15:55:05 -0700, John McWilliams
wrote:

Hecate wrote:

On Wed, 13 Jul 2005 15:01:48 -0700, John McWilliams
wrote:

— you lack a space after –.

Have you a source other than anecdotal?

Not other than the large number of peoples on this and the comp.graphics.apps ng who find that their problems are cured by trashing prefs. There are so many different problems occurring all of which have the same solution, occur on multiple OSs and with such frequency that there is almost always at least one post on these ngs with that as the solution. Empirically, the fact that it happens on more than one OS and happens with such frequency leads to the conclusion it’s the software – along with the fact that I don’t see nay other posts on other newsgroups where the same, ort equivalent advice, turns up for other apps.

Now, do you have any source for your assertion other than your stated comment?

What assertion? I doubt you are referring to the statement about your broken sig. delimiter, and I made no other in this thread.
It’s still rogered.

The one where you said "when your OS blows away your PS Prefs". That’s a claim as well unless you have documentary evidence. Otherwise, your comment is speculative and flies in the face of the evidence.

—

Hecate – The Real One

Fashion: Buying things you don’t need, with money
you don’t have, to impress people you don’t like….

wrote in message

Hecate wrote:

SNIP

This happens so frequently, on both OSs, that I think it’s a PS problem, not an OS problem. I don’t know of any other software where this happens with the frequency it does with PS, or even at all for most software.

For the record, I still have to experience the first corruption of the prefs, after some 11 years of regular Photoshop use on both Mac and Windows platforms (yes, you can call me a relative newbie).

That makes me feel better already: at least I’m not the lone sufferer. I
ran out of scratch disk space during an edit and had to clean up the disk to save the file. After that, the Prefs were corrupted after PS was
restarted. Not sure if PS has a problem with shuffling the disk space,
but I’ll pay closer attention in the future.

Where is Chris Cox when we need him?

Optimizing code I presume? Given the regular reports of the need (?) to thrash the Prefs, there may be a reason. I just don’t know what the reason is.

Bart

Hecate wrote:

On Thu, 14 Jul 2005 15:55:05 -0700, John McWilliams
wrote:

Hecate wrote:

On Wed, 13 Jul 2005 15:01:48 -0700, John McWilliams
wrote:

— you lack a space after –.

turns up for other apps.

Now, do you have any source for your assertion other than your stated comment?

What assertion? I doubt you are referring to the statement about your broken sig. delimiter, and I made no other in this thread.

The one where you said "when your OS blows away your PS Prefs". That’s a claim as well unless you have documentary evidence. Otherwise, your comment is speculative and flies in the face of the evidence.

There’s but scant claim, if any, in the quote you just brought back in.

When the OS blows away the Prefs. is a justifiable presumption as evidenced by several Windows users who’ve just posted to that effect. I don’t have the sense that it happens much on Mac.

—
John McWilliams

On Fri, 15 Jul 2005 17:42:39 -0700, John McWilliams
wrote:

When the OS blows away the Prefs. is a justifiable presumption as evidenced by several Windows users who’ve just posted to that effect. I don’t have the sense that it happens much on Mac.

It’s only a justifiable presumption if the problem doesn’t constantly recur with a single program or programs form a single manufacturer, which appears to be the case here.

—

Hecate – The Real One

Fashion: Buying things you don’t need, with money
you don’t have, to impress people you don’t like…

Bart van der Wolf wrote:

wrote in message

Hecate wrote:

SNIP

This happens so frequently, on both OSs, that I think it’s a PS problem, not an OS problem. I don’t know of any other software where this happens with the frequency it does with PS, or even at all for most software.

For the record, I still have to experience the first corruption of the prefs, after some 11 years of regular Photoshop use on both Mac and Windows platforms (yes, you can call me a relative newbie).

For a complicated piece of sw like PS, a more subtle bug typically occurs under a certain operating condition and/or operator use. The fact that not all users encounter that bug does not mean the bug does not exist. On the contrary, it only take a small number of users who report a bug to suggest its possible existence.

You may not be a newbie, but your experience in this case proves nothing. Just count yourself lucky.