Slow pictures context menu

VanguardLH on 04/01/2014 wrote:

WLM as of version 14 dropped proper quoting (prefixing the parent
content with "" the number of which represents the hierarchical level
of the quoted content).

Oops, looks like it was version 15 of WLM that dropped proper quoting in
reply posts.

Because of Microsoft's decision to screw up their NNTP client (WLM) that
was working before, I colorize via filter rule all posters using WLM
from version 15, and after. This is to alert me that such posters are
likely to be missing the proper quoting because OE/WLM users have
exhibited historical laziness in reviewing their posts before submitting
them, arranging quoted content in the same order as they use for their
reply, don't get rid of spaces between the "" characters that make for
overly long lines and reduce legibility by adding too much whitespace,
and generally are very lazy posts and just submit whatever their client
generates for them. Back for OE, there was a patch that let users alter
OE's behavior regarding top- versus bottom-posting and to place the
signature AFTER the quoted section rather than above it (when
top-posting -- since signatures ALWAYS belong at the end of a post
whether top- or bottom-posting) but rare few OE users bothered to do the
registry edit even when referred to the MS article telling them how.

You could, as suggested, trial other NNTP clients to find one that
follows better netiquette and meets your needs. Or you could continue
using WLM but then *you* will have to manually edit your posts BEFORE
you submit them to rearrange all quoted content to match your top- or
bottom-posting style along with *you* inserting all the quoting prefix
characters so each block of quoted content can be paired to the matching
attribution line. Go ahead and keep using WLM if you don't mind doing
more work to massage your replies before submitting them. It's doable.
You can stick with what you already know and do a bit more editing work
before clicking the Send button.

Migrante on 04/01/2014 wrote:

Do you know how to fix slow pictures right click menu on windows 8
desktop?

Back on topic, can you do a screen capture saved into an image file
(e.g., JPEG) and save it online to give a URL to it so the rest of us
can see what items have been added to the context menu?

Alternatively, use Nirsoft's Shell Extension Viewer to find what
registry entries were added as you installed software that might be
causing the slow response to display the context menu.

http://www.nirsoft.net/utils/shexview.html
Windows 8 is not mentioned as supported but this utility should still
work as it interrogates the 'shellex' entries in the registry to find
the shell extensions and what handlers (programs) are assigned to each.

I believe this utility (haven't gotten around to re-installing Nirsoft
stuff on my new computer setup) can save its listing into a file which
is probably a text file. YOu could then copy the content of the text
file and post the list here.

Or you could use Nirsoft ShellExView yourself and just *disable* (not
delete) each shell extension to see if and when the content menu
suddenly becomes much quicker to respond.

Notice on Nirsoft's product page (URL above) there is a link to
"Right-click is slow or weird behavior caused by context menu handlers".
This is what you've described as being your problem.

On 1/4/2014 5:55 PM, Gene E. Bloch wrote:
On 1/04/2014, Migrante posted:
Thank you all for helping. The more ideas the best. Later I'll try to
put it on practice. I supose it's better to listen opinion from others
than arguee with you all.

Yes :-)

Good luck with your problem.

FWIW, I understood the OP's question. Looks like Paul did too and gave
the OP a starting point. The OP wasn't talking about pictures on the
desktop, he/she was talking about icons and the context menu.

By the way, a slow context menu can also be due to you uninstalling some
software that left behind shellex handlers. Windows is trying to find
the handler defined by the shellex registry entry but eventually times
out because the handler isn't available anymore. Did you install
something lately afterwhich you noticed the lag for the context menu?
This is about the only time that I recommend a registry cleaner to the
less than expert user.

Normally the use of a registry cleaner affords no increase in registry
performance as claimed by many authors because the registry is read only
once from the disk to copy it into memory and thereafter all registry
access is against the memory copy, and memory is RAM (random access
memory) which means it takes as long to access one byte as another in
memory. Eliminating orphaned registry entries does nothing to affect
registry speed because those entries in memory aren't being looked up.
Often registry cleaners will suggest to delete something that really is
needed. The authors don't have the knowledge of the dependency of an
entry or the environment under which it will be used (i.e., it may look
like an orphan entry but a program or boot scenario may need it). Yet a
registry cleaner (well, a good one) may find orphaned shell extension
entries in the registry and delete them. After all, the handler to
which they point doesn't exist, isn't where the entry says it should be
found, or the handler is corrupt or non-functioning so it's loss from
the context menu is no loss since it isn't usable, anyway.

Always backup the registry before you edit it or when you using a
registry cleaner. A registry cleaner is a tool to assist in automatic
and speedy cleanup that the user is expected to already understand. If
the user doesn't understand what changes the cleaner proposes to do in
the registry then don't use the tool. A scalpel in your hand doesn't
make you a surgeon but the surgeon can use the scalpel. You can export
the entire registry into a .reg file. Personally I prefer to do an
image backup (which will include the registry's disk files). That's
because if something gets royally screwed up in the registry then you
may not be able to boot into Windows and/or be able to run reg.exe or
regedit.exe to import back your registry backup. A backup is worthless
unless you have the environment available to restore it.

http://i.cubeupload.com/GFwUzX.jpg

"VanguardLH" escreveu na mensagem ...

Migrante on 04/01/2014 wrote:

Do you know how to fix slow pictures right click menu on windows 8
desktop?

Back on topic, can you do a screen capture saved into an image file
(e.g., JPEG) and save it online to give a URL to it so the rest of us
can see what items have been added to the context menu?

On Sat, 4 Jan 2014 20:33:59 -0600, VanguardLH wrote in


Prior to the avalanche, bottom-posting was the de facto standard style
so users could read a thread in the same way they read a book. It
provided the context for the following reply. It is also expected that
you trim the quoted content so it provides enough context for your reply
without becoming cumbersome by providing too much unnecessary content.

Well said.
--
A: Yes.
Q: Does that happen with short messages too?
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on Usenet and in e-mail?

On 1/5/2014 12:33 AM, Migrante wrote:


"VanguardLH" escreveu na mensagem ...
Migrante on 04/01/2014 wrote:

Do you know how to fix slow pictures right click menu on windows 8
desktop?

Back on topic, can you do a screen capture saved into an image file
(e.g., JPEG) and save it online to give a URL to it so the rest of us
can see what items have been added to the context menu?

http://i.cubeupload.com/GFwUzX.jpg

I'm having trouble matching that to any menu here.
Is that Windows 8, Windows 8.1, or WinXP ?

Paul

VanguardLH wrote, On 1/4/2014 9:33 PM:
Microsoft not only abandoned Usenet when they
shutdown their NNTP servers (their newsgroups continue to survive,
however) but then they chose to deliberately alter their WLM program to
remove its quoting function that it *did* have before. They stripped
out or nullified the quoting function in WLM as of verson 14. They will
not be repairing this stupidity.

The first part is mostly true. Usenet abandonment actually predates the
shutdown of the nntp servers in favor of the web forums. The latter were
in place well before the backend MSFT nntp servers were gradually
deprecated and finally complete in Oct 2010.

With respect to 'WLM quoting function'.
- during the beta of WLM 15 code changes to increase the robustness of
the HTML engine and integration with Photo email (composition and Live
Photo Gallery) and SkyDrive broke the plain text quoting 'insert '.
While aware of it, the updated code for better integration was a higher
priority.

That decision created a larger and readily apparent problem - how to
handle all the complaints that were certain to appear in the Windows
Live Solution Center forums (which pre-dated Live's migration to
Microsoft Answers).
- At that time to ensure a common and consistent answer provided by
paid (and controlled) Solution Center support personnel when the product
went RTM MSFT removed the code for choosing the '' option in the final
beta and subsequently released those bits as RTM Version 15 approx.
thirty days later....thereby allowing all support personnel when asked
about plain text quoting to provide a sole responseto reply 'Design
intent'.

The focus of the entire 15x beta was also integration with Hotmail type
accounts using DeltaSync (MSFT approach to IMAP as a replacement for
WebDAV), synchronization of contacts and calendar for the signed on
Live/Microsoft accounts, and the use of that signed on account's
SkyDrive for Photo email. Doing so (and by design) provided the seminal
telemetric (phone home) data on cloud usage and storage.

i.e. it was never really about Usenet (while impacted and a
drive-bystander) but the ability to collect usage data of web service
features (using the entire Live Platform of desktop and web
applications) for later 'cloud' integration into future products (e.g.
Windows, Office,etc.)...thus inevitably from 'day-one' making every
single Windows Live Essentials v12x-14x-15x/Windows Essentials 16x user
a 'cloud' beta tester!

Incidentally, if folks still wished 'plain text quoting' the feature
was retained in the Hotmail web UI - but to take advantage of that one
had to sign on to the guess what! - 'cloud'


Welcome to the machine.


--
...winston
msft mvp consumer apps

Paul wrote, On 1/5/2014 2:30 AM:
On 1/5/2014 12:33 AM, Migrante wrote:


"VanguardLH" escreveu na mensagem ...
Migrante on 04/01/2014 wrote:

Do you know how to fix slow pictures right click menu on windows 8
desktop?

Back on topic, can you do a screen capture saved into an image file
(e.g., JPEG) and save it online to give a URL to it so the rest of us
can see what items have been added to the context menu?

http://i.cubeupload.com/GFwUzX.jpg

I'm having trouble matching that to any menu here.
Is that Windows 8, Windows 8.1, or WinXP ?

Paul


Looks familiar - similar to the Windows Photo Gallery (a component in
Windows Essentials 2012) context menu after opening Photo Gallery,
opening a picture of editing, then rt. clicking on the picture.

The English version (WLPG 2012 QFE1-latest version) shows Rotate Right
and Rotate Left. The op's pic shows Rotate Clockwise and Rotate
Counterclockwise. Possibly his pic is unique to WLPG 2012 RTM (his
version) or inherent to a European specific installed language version.

If not WLPG, it is most likely the op's picture viewing software (not
the o/s)


--
...winston
msft mvp consumer apps

So, do you think the cause is Windows Photo Gallery?

.................................................. .................................................. ...............

"Looks familiar - similar to the Windows Photo Gallery (a component in
Windows Essentials 2012) context menu after opening Photo Gallery,
opening a picture of editing, then rt. clicking on the picture.

The English version (WLPG 2012 QFE1-latest version) shows Rotate Right
and Rotate Left. The op's pic shows Rotate Clockwise and Rotate
Counterclockwise. Possibly his pic is unique to WLPG 2012 RTM (his
version) or inherent to a European specific installed language version.

If not WLPG, it is most likely the op's picture viewing software (not
the o/s)"


--
...winston
msft mvp consumer apps

I've tried to verify if delay is related with windows photo gallery,
uninstalling wpg and movie maker from windows essentials 2012, but it isn't.
.................................................. .................................................. ...............

"Looks familiar - similar to the Windows Photo Gallery (a component in
Windows Essentials 2012) context menu after opening Photo Gallery,
opening a picture of editing, then rt. clicking on the picture.

The English version (WLPG 2012 QFE1-latest version) shows Rotate Right
and Rotate Left. The op's pic shows Rotate Clockwise and Rotate
Counterclockwise. Possibly his pic is unique to WLPG 2012 RTM (his
version) or inherent to a European specific installed language version.

If not WLPG, it is most likely the op's picture viewing software (not
the o/s)"


--
...winston
msft mvp consumer apps

The menu delay still persists and entries are the same.

"Migrante" escreveu na mensagem ...

I've tried to verify if delay is related with windows photo gallery,
uninstalling wpg and movie maker from windows essentials 2012, but it isn't.
.................................................. .................................................. ...............

"Looks familiar - similar to the Windows Photo Gallery (a component in
Windows Essentials 2012) context menu after opening Photo Gallery,
opening a picture of editing, then rt. clicking on the picture.

The English version (WLPG 2012 QFE1-latest version) shows Rotate Right
and Rotate Left. The op's pic shows Rotate Clockwise and Rotate
Counterclockwise. Possibly his pic is unique to WLPG 2012 RTM (his
version) or inherent to a European specific installed language version.

If not WLPG, it is most likely the op's picture viewing software (not
the o/s)"


--
...winston
msft mvp consumer apps

On Sat, 04 Jan 2014 16:45:40 -0800, Gene E. Bloch
wrote:

On 1/04/2014, Ken Blake, MVP posted:
On Sat, 04 Jan 2014 12:05:41 -0800, Gene E. Bloch
wrote:

On 1/04/2014, Ken Blake, MVP posted:
On Sat, 4 Jan 2014 16:22:06 -0000, "Migrante"
wrote:

I don't know why should I use an old newsreader or non microsoft
in a windows 8 forum.
If you can't help me I'll wait for something. I've tried searching
help in other places but couldn't find answer.


You should use whatever you want. Far be it from me to tell you
what to do.

My point is a simple one: if you make it hard for us to read your
messages, many of us will killfile you, as I am about to do.
Goodbye.

I don't killfile for mere etiquette violations or bad attitudes
(OTOH, pron or racism or insanity are other issues).


Nor I.


However, when someone's attitude is negative or when their reader
software makes it hard to figure out where their reponse is - and
especially when both are true - I sure won't put in a lot of effort
for the poster.


Exactly! And that's why I killfiled him.

ISTM that in your first remark you agreed with my stated approach to
killfiling and in your second remark you disagreed with it.

I'm puzzled.


In my first remark I said I agreed that I didn't killfile for
"etiquette violations or bad attitudes" (although there have been some
exceptions).


In my second remark, I said that I killfiled someone whose quoting
technique made their messages very hard to understand. Two different
things, as far as I'm concerned.


So, as examples, I don't killfile someone who violates netiquette by
top-posting (although there's occasionally someone whose top-posted
messages are very hard to understand, and I come close to kill-filing
them). But I do kill-file someone like the person to whom I responded
who refuses to either change to a newsreader that quotes properly or
put the signs in himself, and whose messages are therefore very hard
to read; I just don't have the time to try to figure out what they are
trying to say.

On Sat, 4 Jan 2014 20:33:59 -0600, VanguardLH wrote:


There has been a long-running debate over top- versus bottom-posting in
reply posts.


That's for sure!

Here's my view, which is different from most people's:

I want to know what a reply is to, before I read the reply itself.
That means that the answer is best when it follows the question. But
that doesn't exactly mean that everything should be bottom-posted. If
a reply is to multiple questions or multiple assertions, the answer to
each should be after the particular question or assertion. That means
I'm in favor of interspersed posting, not posting everything at either
the top or bottom. And I feel the same way about both newsgroup
messages and e-mail

There are those who say that top-posting is better than bottom-posting
because they don't want to have to scroll down to the bottom to read
the message. My view is exactly the opposite: if you top-post in reply
to a long message, I have to scroll *twice*--once down to read the
question, then again back up to read the answer.

There are of course those who don't have to scroll twice, because they
remember what the question is. But the only people who don't have to
scroll twice are those who remember what the thread was about; they
either have excellent memories, or more likely get very few messages,
so remembering them is easy.

And one more point: if you are not overly wordy and do a good job of
trimming the material you are quoting, it doesn't matter a whole lot
whether you top-post or bottom-post: both the question and the reply
can be seen in the window without scrolling. So I think that trimming
is more important than the question of top-posting vs. bottom-posting.

On 1/5/2014 7:31 AM, Migrante wrote:
The menu delay still persists and entries are the same.

"Migrante" escreveu na mensagem ...

I've tried to verify if delay is related with windows photo gallery,
uninstalling wpg and movie maker from windows essentials 2012, but it isn't.
.................................................. .................................................. ..............

"Looks familiar - similar to the Windows Photo Gallery (a component in
Windows Essentials 2012) context menu after opening Photo Gallery,
opening a picture of editing, then rt. clicking on the picture.

The English version (WLPG 2012 QFE1-latest version) shows Rotate Right
and Rotate Left. The op's pic shows Rotate Clockwise and Rotate
Counterclockwise. Possibly his pic is unique to WLPG 2012 RTM (his
version) or inherent to a European specific installed language version.

If not WLPG, it is most likely the op's picture viewing software (not
the o/s)"



This thread, covers Photo Gallery being slow to display pictures.
The solution is to remove a display profile that has been "calibrated".

http://www.sevenforums.com/music-pic...nely-slow.html

Someone here, the Context Menu was slowed as a side effect of mapped drives.

http://social.technet.microsoft.com/...um=w7itproperf

"I had the same problem, it was taking any where from 1 to 5 minutes for
the context menu to show up after doing a right click.

I solved the issue by removing all of the mapped drives from my
send to folder. This was causing the problem because some of the
mapped drives I had were taking a lot of time just verifying that
they existed."

And a guy here, used Process Monitor to find a hint as to
what might be slowing his computer. The Process Monitor showed
some network activity, and he traced it to the Bluetooth Stack.

http://community.futuremark.com/foru...ce-manager-etc

Paul