I am trying to uninstall a program called PictureProject which came with a
Nikon camera. This should not be a problem but i am getting a message asking
whether to delete/keep shared files. The message reads:

InstallShield is about to remove a file that was previously shared between
programs. You should only keep if you know another program needs it.

It then lists the shared file and location, but the rest of the text is
obscured and there is no option to expand window or scroll down.

I have the options YES, NO, and CANCEL and because i don't know the full
question am not sure which to hit. I am happy to keep any shared files
rather than run the risk of affecting another program.

Any help much appreciated

Mark

That is a pretty standard message which does confuse!

It is an application that you no longer wish to use, so you do not wish it
to be sharing with other files on your computer.

Computers work on logic.
If you delete the application, there is NO need for the shared file!

Delete it, along with the application.

Click YES.

"mynameismark" wrote:

I am trying to uninstall a program called PictureProject which came with a
Nikon camera. This should not be a problem but i am getting a message asking
whether to delete/keep shared files. The message reads:

InstallShield is about to remove a file that was previously shared between
programs. You should only keep if you know another program needs it.

It then lists the shared file and location, but the rest of the text is
obscured and there is no option to expand window or scroll down.

I have the options YES, NO, and CANCEL and because i don't know the full
question am not sure which to hit. I am happy to keep any shared files
rather than run the risk of affecting another program.

Any help much appreciated

Mark

It is always safer to keep the shared file if you don't know what the other
program might be and therefore can't be sure it will not be used later.

"mynameismark" wrote in message
...
I am trying to uninstall a program called PictureProject which came with a
Nikon camera. This should not be a problem but i am getting a message
asking
whether to delete/keep shared files. The message reads:

InstallShield is about to remove a file that was previously shared between
programs. You should only keep if you know another program needs it.

It then lists the shared file and location, but the rest of the text is
obscured and there is no option to expand window or scroll down.

I have the options YES, NO, and CANCEL and because i don't know the full
question am not sure which to hit. I am happy to keep any shared files
rather than run the risk of affecting another program.

Any help much appreciated

Mark

I realize this thread is almost two years old, and that you probably
already found the answer to your question, but I was having the same
problem and stumbled across your post as I looked for an answer. Now
that I have one I wanted to pass it along, just in case you were still
waiting.

Before I answer your question, however (and I'll be the first person in
this thread to actually do so), I need to speak to Mick...

Hey Mick, what is it about people like you who need to respond to
peoples questions when you clearly don't know what you're talking about.
You weren't even paying close enough attention to *know what the
question was*. Is it just some horribly powerful desire to appear to be
intelligent?

If I may paraphrase, Mark's question was "In the Installshield message
window, what's the final line say?"

Let's review your "answer":

Mick: "That is a pretty standard message which does confuse!"

The message doesn't confuse, the question that follows the message
being obscured does. And do I detect a little condescension?

Mick: "It is an application that you no longer wish to use..."

Yeah, no kidding. That's why he's uninstalling it.

Mick: "...so you do not wish it to be sharing with other files on your
computer."

Um...wow. This statement is moronic on so many levels. The application
will be removed, so it won't share with anything regardless of what
options are chosen. Also, if a non-existent application could somehow
share, it would share with other applications, not with other files. It
is the files that are being shared.

The files are shared. The applications are doing the sharing. Big
difference.

Mick: "Computers work on logic."

Mick does not.

Mick: "If you delete the application, there is NO need for the shared
file!"

Again, wow. You have a lot of problems with applications not working
correctly after you uninstall other applications, don't you Mick? In
order for a file to be considered "shared" it must be being used by two
or more applications. If you uninstall one of those applications, there
is still at least one more application that *needs* that file.

Here's an example, in case you still don't get it...

Let's say you have Windows Media Player and Windows Movie Maker
installed on your computer. Let's say that they both need a driver to
work with MPEGs, and let's say that the driver is named MPEGDRIVER.DLL.
Let's also say that in order to conserve space, the file was installed
into a "common" or "shared" folder, so that both applications could use
it, instead of having two copies of the exact same file on your
computer. This is done all of the time...

Now let's say that one day you decide to uninstall Windows Movie Maker.
As the uninstall process goes along and deletes all of the files listed
as belonging to Movie Maker, it will get to MPEGDRIVER.DLL and notice
that another program, Windows Media Player, might use that file. At this
point, it will ask you if you want to keep it or delete.

And your response would be?

Mick: "Delete it, along with the application."

That's cool. Now Media Player isn't working. I wonder why. Maybe
I'll post another question on a message board, get more bad advice, need
to ask more questions, get more bad advice, etc., and before you know it
my computer will burst into flames.

Mick: "Click YES."

Ah, Mick, you're so quick to pull that trigger. But there is a hidden
clue in your answer. It is the only useful information in your entire
post. Mark can assume that clicking "Yes" will delete the file.

But considering how staggeringly idiotic the rest of your response was,
should he trust that assumption? Can he safely assume that YES=DELETE
and that NO=SAVE? After explicitly stating that he is "happy to keep
any shared files rather than run the risk of affecting another program",
can he trust the guy who tells him to delete with reckless abandon?

I wouldn't.

As soon as Mark posted his question, it should have been clear as day
to you that he wants to keep any shared files, just in case. Otherwise
there'd be no reason to post the question. Your advice? Delete the
very files he's trying to save. Should he trust a clue given by someone
who doesn't understand computers, didn't understand his question, and
doesn't respect his desire to keep the files in question?

I wouldn't.

From now on, Mick, make sure of the following two things before
replying to a post:

1 - You understand the question, and
2 - You actually know the answer.

I know I sound crazy going off this severely over something pretty
trivial, but idiots like you need to understand something: when you have
a problem that you've spent time trying to fix, and then spent time
researching, and then finally spent time posting a question online
about, it really starts to weigh you down. You so badly want the
problem solved. Then the magical day comes when you find out that
there's a response to your question! You feel something you haven't
felt for quite some time: hope. You see the light at the end of the
tunnel. You allow yourself to smile a little, and you begin to feel
happiness creeping back into your life. By the time you've logged in to
read the response (or opened the e-mail), you're actually excited!

Then you read it. And your hopes are dashed. Because the person who
responded is an imbecile.

And this will happen over and over, and you'll get your hopes up every
time even though you know you shouldn't. If it isn't the dopey
"let-me-misinform-you-about-something-other-than-what-you-asked" type of
response (like yours), it's the attention starved
"3-paragraphs-to-essentially-say-'I-don't-know'" type of response, or
the lazy
"I-have-the-same-problem,-can-you-let-me-know-when-you-figure-it-out"
type of response. Eventually you start beating your head against the
wall.

It is incredibly rare to get a clear, concise, correct answer...

Like this one:

Hey, Mark! The last line in that window reads "Do you want
Installshield to remove this file?".

So, since you want to keep any shared files, not delete them, click
"NO".


--
wealthypoets

I realize this thread is almost two years old, and that you probably
already found the answer to your question, but I was having the same
problem and stumbled across your post as I looked for an answer. Now
that I have one I wanted to pass it along, just in case you were still
waiting.

Before I answer your question, however (and I'll be the first person in
this thread to actually do so), I need to speak to Mick...

Hey Mick, what is it about people like you who need to respond to
peoples questions when you clearly don't know what you're talking about.
You weren't even paying close enough attention to *know what the
question was*. Is it just some horribly powerful desire to appear to be
intelligent?

If I may paraphrase, Mark's question was "In the Installshield message
window, what's the final line say?"

Let's review your "answer":

Mick: "That is a pretty standard message which does confuse!"

The message doesn't confuse, the question that follows the message
being obscured does. And do I detect a little condescension?

Mick: "It is an application that you no longer wish to use..."

Yeah, no kidding. That's why he's uninstalling it.

Mick: "...so you do not wish it to be sharing with other files on your
computer."

Um...wow. This statement is moronic on so many levels. The application
will be removed, so it won't share with anything regardless of what
options are chosen. Also, if a non-existent application could somehow
share, it would share with other applications, not with other files. It
is the files that are being shared.

The files are shared. The applications are doing the sharing. Big
difference.

Mick: "Computers work on logic."

Mick does not.

Mick: "If you delete the application, there is NO need for the shared
file!"

Again, wow. You have a lot of problems with applications not working
correctly after you uninstall other applications, don't you Mick? In
order for a file to be considered "shared" it must be being used by two
or more applications. If you uninstall one of those applications, there
is still at least one more application that *needs* that file.

Here's an example, in case you still don't get it...

Let's say you have Windows Media Player and Windows Movie Maker
installed on your computer. Let's say that they both need a driver to
work with MPEGs, and let's say that the driver is named MPEGDRIVER.DLL.
Let's also say that in order to conserve space, the file was installed
into a "common" or "shared" folder, so that both applications could use
it, instead of having two copies of the exact same file on your
computer. This is done all of the time...

Now let's say that one day you decide to uninstall Windows Movie Maker.
As the uninstall process goes along and deletes all of the files listed
as belonging to Movie Maker, it will get to MPEGDRIVER.DLL and notice
that another program, Windows Media Player, might use that file. At this
point, it will ask you if you want to keep it or delete.

And your response would be?

Mick: "Delete it, along with the application."

That's cool. Now Media Player isn't working. I wonder why. Maybe
I'll post another question on a message board, get more bad advice, need
to ask more questions, get more bad advice, etc., and before you know it
my computer will burst into flames.

Mick: "Click YES."

Ah, Mick, you're so quick to pull that trigger. But there is a hidden
clue in your answer. It is the only useful information in your entire
post. Mark can assume that clicking "Yes" will delete the file.

But considering how staggeringly idiotic the rest of your response was,
should he trust that assumption? Can he safely assume that YES=DELETE
and that NO=SAVE? After explicitly stating that he is "happy to keep
any shared files rather than run the risk of affecting another program",
can he trust the guy who tells him to delete with reckless abandon?

I wouldn't.

As soon as Mark posted his question, it should have been clear as day
to you that he wants to keep any shared files, just in case. Otherwise
there'd be no reason to post the question. Your advice? Delete the
very files he's trying to save. Should he trust a clue given by someone
who doesn't understand computers, didn't understand his question, and
doesn't respect his desire to keep the files in question?

I wouldn't.

From now on, Mick, make sure of the following two things before
replying to a post:

1 - You understand the question, and
2 - You actually know the answer.

I know I sound crazy going off this severely over something pretty
trivial, but idiots like you need to understand something: when you have
a problem that you've spent time trying to fix, and then spent time
researching, and then finally spent time posting a question online
about, it really starts to weigh you down. You so badly want the
problem solved. Then the magical day comes when you find out that
there's a response to your question! You feel something you haven't
felt for quite some time: hope. You see the light at the end of the
tunnel. You allow yourself to smile a little, and you begin to feel
happiness creeping back into your life. By the time you've logged in to
read the response (or opened the e-mail), you're actually excited!

Then you read it. And your hopes are dashed. Because the person who
responded is an imbecile.

And this will happen over and over, and you'll get your hopes up every
time even though you know you shouldn't. If it isn't the dopey
"let-me-misinform-you-about-something-other-than-what-you-asked" type of
response (like yours), it's the attention starved
"3-paragraphs-to-essentially-say-'I-don't-know'" type of response, or
the lazy
"I-have-the-same-problem,-can-you-let-me-know-when-you-figure-it-out"
type of response. Eventually you start beating your head against the
wall.

It is incredibly rare to get a clear, concise, correct answer...

Like this one:

Hey, Mark! The last line in that window reads "Do you want
Installshield to remove this file?".

So, since you want to keep any shared files, not delete them, click
"NO".


--
wealthypoets

trrew vcbxbxzbzbbzbb vcbxbxcbxbbxcvjcjcx
--
swewbbncncn nbnvncncncnvncn nbnncc
rrtreob bnvnvcnvnvncn nbvnncnvncmvncn n bnnvnvncxnc
srrree vbcbcb b ububuvuvuvncnvnxnvnxcnvn vbxbvbxbcv
cvcc



"wealthypoets" wrote:


I realize this thread is almost two years old, and that you probably
already found the answer to your question, but I was having the same
problem and stumbled across your post as I looked for an answer. Now
that I have one I wanted to pass it along, just in case you were still
waiting.

Before I answer your question, however (and I'll be the first person in
this thread to actually do so), I need to speak to Mick...

Hey Mick, what is it about people like you who need to respond to
peoples questions when you clearly don't know what you're talking about.
You weren't even paying close enough attention to *know what the
question was*. Is it just some horribly powerful desire to appear to be
intelligent?

If I may paraphrase, Mark's question was "In the Installshield message
window, what's the final line say?"

Let's review your "answer":

Mick: "That is a pretty standard message which does confuse!"

The message doesn't confuse, the question that follows the message
being obscured does. And do I detect a little condescension?

Mick: "It is an application that you no longer wish to use..."

Yeah, no kidding. That's why he's uninstalling it.

Mick: "...so you do not wish it to be sharing with other files on your
computer."

Um...wow. This statement is moronic on so many levels. The application
will be removed, so it won't share with anything regardless of what
options are chosen. Also, if a non-existent application could somehow
share, it would share with other applications, not with other files. It
is the files that are being shared.

The files are shared. The applications are doing the sharing. Big
difference.

Mick: "Computers work on logic."

Mick does not.

Mick: "If you delete the application, there is NO need for the shared
file!"

Again, wow. You have a lot of problems with applications not working
correctly after you uninstall other applications, don't you Mick? In
order for a file to be considered "shared" it must be being used by two
or more applications. If you uninstall one of those applications, there
is still at least one more application that *needs* that file.

Here's an example, in case you still don't get it...

Let's say you have Windows Media Player and Windows Movie Maker
installed on your computer. Let's say that they both need a driver to
work with MPEGs, and let's say that the driver is named MPEGDRIVER.DLL.
Let's also say that in order to conserve space, the file was installed
into a "common" or "shared" folder, so that both applications could use
it, instead of having two copies of the exact same file on your
computer. This is done all of the time...

Now let's say that one day you decide to uninstall Windows Movie Maker.
As the uninstall process goes along and deletes all of the files listed
as belonging to Movie Maker, it will get to MPEGDRIVER.DLL and notice
that another program, Windows Media Player, might use that file. At this
point, it will ask you if you want to keep it or delete.

And your response would be?

Mick: "Delete it, along with the application."

That's cool. Now Media Player isn't working. I wonder why. Maybe
I'll post another question on a message board, get more bad advice, need
to ask more questions, get more bad advice, etc., and before you know it
my computer will burst into flames.

Mick: "Click YES."

Ah, Mick, you're so quick to pull that trigger. But there is a hidden
clue in your answer. It is the only useful information in your entire
post. Mark can assume that clicking "Yes" will delete the file.

But considering how staggeringly idiotic the rest of your response was,
should he trust that assumption? Can he safely assume that YES=DELETE
and that NO=SAVE? After explicitly stating that he is "happy to keep
any shared files rather than run the risk of affecting another program",
can he trust the guy who tells him to delete with reckless abandon?

I wouldn't.

As soon as Mark posted his question, it should have been clear as day
to you that he wants to keep any shared files, just in case. Otherwise
there'd be no reason to post the question. Your advice? Delete the
very files he's trying to save. Should he trust a clue given by someone
who doesn't understand computers, didn't understand his question, and
doesn't respect his desire to keep the files in question?

I wouldn't.

From now on, Mick, make sure of the following two things before
replying to a post:

1 - You understand the question, and
2 - You actually know the answer.

I know I sound crazy going off this severely over something pretty
trivial, but idiots like you need to understand something: when you have
a problem that you've spent time trying to fix, and then spent time
researching, and then finally spent time posting a question online
about, it really starts to weigh you down. You so badly want the
problem solved. Then the magical day comes when you find out that
there's a response to your question! You feel something you haven't
felt for quite some time: hope. You see the light at the end of the
tunnel. You allow yourself to smile a little, and you begin to feel
happiness creeping back into your life. By the time you've logged in to
read the response (or opened the e-mail), you're actually excited!

Then you read it. And your hopes are dashed. Because the person who
responded is an imbecile.

And this will happen over and over, and you'll get your hopes up every
time even though you know you shouldn't. If it isn't the dopey
"let-me-misinform-you-about-something-other-than-what-you-asked" type of
response (like yours), it's the attention starved
"3-paragraphs-to-essentially-say-'I-don't-know'" type of response, or
the lazy
"I-have-the-same-problem,-can-you-let-me-know-when-you-figure-it-out"
type of response. Eventually you start beating your head against the
wall.

It is incredibly rare to get a clear, concise, correct answer...

Like this one:

Hey, Mark! The last line in that window reads "Do you want
Installshield to remove this file?".

So, since you want to keep any shared files, not delete them, click
"NO".


--
wealthypoets
.

trrew vcbxbxzbzbbzbb vcbxbxcbxbbxcvjcjcx
--
swewbbncncn nbnvncncncnvncn nbnncc
rrtreob bnvnvcnvnvncn nbvnncnvncmvncn n bnnvnvncxnc
srrree vbcbcb b ububuvuvuvncnvnxnvnxcnvn vbxbvbxbcv
cvcc



"wealthypoets" wrote:


I realize this thread is almost two years old, and that you probably
already found the answer to your question, but I was having the same
problem and stumbled across your post as I looked for an answer. Now
that I have one I wanted to pass it along, just in case you were still
waiting.

Before I answer your question, however (and I'll be the first person in
this thread to actually do so), I need to speak to Mick...

Hey Mick, what is it about people like you who need to respond to
peoples questions when you clearly don't know what you're talking about.
You weren't even paying close enough attention to *know what the
question was*. Is it just some horribly powerful desire to appear to be
intelligent?

If I may paraphrase, Mark's question was "In the Installshield message
window, what's the final line say?"

Let's review your "answer":

Mick: "That is a pretty standard message which does confuse!"

The message doesn't confuse, the question that follows the message
being obscured does. And do I detect a little condescension?

Mick: "It is an application that you no longer wish to use..."

Yeah, no kidding. That's why he's uninstalling it.

Mick: "...so you do not wish it to be sharing with other files on your
computer."

Um...wow. This statement is moronic on so many levels. The application
will be removed, so it won't share with anything regardless of what
options are chosen. Also, if a non-existent application could somehow
share, it would share with other applications, not with other files. It
is the files that are being shared.

The files are shared. The applications are doing the sharing. Big
difference.

Mick: "Computers work on logic."

Mick does not.

Mick: "If you delete the application, there is NO need for the shared
file!"

Again, wow. You have a lot of problems with applications not working
correctly after you uninstall other applications, don't you Mick? In
order for a file to be considered "shared" it must be being used by two
or more applications. If you uninstall one of those applications, there
is still at least one more application that *needs* that file.

Here's an example, in case you still don't get it...

Let's say you have Windows Media Player and Windows Movie Maker
installed on your computer. Let's say that they both need a driver to
work with MPEGs, and let's say that the driver is named MPEGDRIVER.DLL.
Let's also say that in order to conserve space, the file was installed
into a "common" or "shared" folder, so that both applications could use
it, instead of having two copies of the exact same file on your
computer. This is done all of the time...

Now let's say that one day you decide to uninstall Windows Movie Maker.
As the uninstall process goes along and deletes all of the files listed
as belonging to Movie Maker, it will get to MPEGDRIVER.DLL and notice
that another program, Windows Media Player, might use that file. At this
point, it will ask you if you want to keep it or delete.

And your response would be?

Mick: "Delete it, along with the application."

That's cool. Now Media Player isn't working. I wonder why. Maybe
I'll post another question on a message board, get more bad advice, need
to ask more questions, get more bad advice, etc., and before you know it
my computer will burst into flames.

Mick: "Click YES."

Ah, Mick, you're so quick to pull that trigger. But there is a hidden
clue in your answer. It is the only useful information in your entire
post. Mark can assume that clicking "Yes" will delete the file.

But considering how staggeringly idiotic the rest of your response was,
should he trust that assumption? Can he safely assume that YES=DELETE
and that NO=SAVE? After explicitly stating that he is "happy to keep
any shared files rather than run the risk of affecting another program",
can he trust the guy who tells him to delete with reckless abandon?

I wouldn't.

As soon as Mark posted his question, it should have been clear as day
to you that he wants to keep any shared files, just in case. Otherwise
there'd be no reason to post the question. Your advice? Delete the
very files he's trying to save. Should he trust a clue given by someone
who doesn't understand computers, didn't understand his question, and
doesn't respect his desire to keep the files in question?

I wouldn't.

From now on, Mick, make sure of the following two things before
replying to a post:

1 - You understand the question, and
2 - You actually know the answer.

I know I sound crazy going off this severely over something pretty
trivial, but idiots like you need to understand something: when you have
a problem that you've spent time trying to fix, and then spent time
researching, and then finally spent time posting a question online
about, it really starts to weigh you down. You so badly want the
problem solved. Then the magical day comes when you find out that
there's a response to your question! You feel something you haven't
felt for quite some time: hope. You see the light at the end of the
tunnel. You allow yourself to smile a little, and you begin to feel
happiness creeping back into your life. By the time you've logged in to
read the response (or opened the e-mail), you're actually excited!

Then you read it. And your hopes are dashed. Because the person who
responded is an imbecile.

And this will happen over and over, and you'll get your hopes up every
time even though you know you shouldn't. If it isn't the dopey
"let-me-misinform-you-about-something-other-than-what-you-asked" type of
response (like yours), it's the attention starved
"3-paragraphs-to-essentially-say-'I-don't-know'" type of response, or
the lazy
"I-have-the-same-problem,-can-you-let-me-know-when-you-figure-it-out"
type of response. Eventually you start beating your head against the
wall.

It is incredibly rare to get a clear, concise, correct answer...

Like this one:

Hey, Mark! The last line in that window reads "Do you want
Installshield to remove this file?".

So, since you want to keep any shared files, not delete them, click
"NO".


--
wealthypoets
.