Send To

Topic

New Reply

Does anyone have any experience with the

Reply | Quote

Replies

I can’t solve your problem (no delay on my set up), but you may like to look at File Targets which is a free download from Moon Software. It works in a similar way to send to but is more advanced and fully configurable.

Reply | Quote

Thanks. I downloaded File Target but haven

Reply | Quote

Tony,

I did install File Target and it works very well and fast as the send to should. Again, thanks.

Reply | Quote

Anyone experiencing this “send to” delay yet and is there a remedy?

FileTargets works fine but I haven’t found a way to put a “mail recipient” shortcut in it so I still have to use

Reply | Quote

This any use?

How to Add Items to the “Send To” Menu in Windows XP (Q310270)

Reply | Quote

Leif,

The article about adding or removing shortcuts to the

Reply | Quote

You could try a) moving the SendTo folder, and using a tool like TweakUI to point the shell at its new location, or pruning some of the entries in there that you don’t use anyway. Both of these are troubleshooting methods only, of course – if you’re happy with File Target, it’s a moot point. I prefer not to run additional shell software to avoid weird problems.

Additionally, if the SendTo menu refers to a resource such as a CD-RW drive and it contains a disc, Windows feels the need to spin up the disc to read its contents (this also affects operations in file dialogs system wide and can be quite a nuisance).

Reply | Quote

Tweak UI – one of the MS Power Toys lets you adjust the speed menus appear at.
But if it is something specific to the Send To menu, there may be a problem accessing the contents of the SendTo folder. Have you tried moving any unwanted “targets” out of it?

Edited to add:
I’m SURE I started replying before Mark did

Reply | Quote

Mark and Lief,

Thanks but there are only 8 entries in the

Reply | Quote

Oh boy! I’m sure glad you found that point, my friend. Even though on my machine, the window opens in a flash, I’ve been lookin’ all over the web trying to see if there is a registry “fix” for any problem like that. Now that you’ve discovered what you did, it sounds a lot like an occasional problem with “drive mapping.” (That has slowed down many-a-computer since Windows tries to “talk to” mapped drives). Anyways, good you found what ya did!

Reply | Quote

Big Al,

Thanks for your searching. I had looked all over MS’s site many, many times to no avail.

In this case I believe,

Reply | Quote

Ah – but you DO have shortcuts pointing to network locations. Even if they are static drive mappings, I’d bet that it could cause problems. The PC has to resolve the system’s names via network cable, and if there are Win9x systems attached (I seem to recall that you had one of those) then Windows XP also checks for scheduled tasks on the remote system. Try removing them and see if it changes the response time back to normal. If it does, you can assign static IP addresses to your PCs (although it might not be the best idea) and/or disable the Scheduled Tasks check.

Reply | Quote

Tell ME more about that scheduled tasks statement, would you Mark. One of my in-home machines runs Win98SE and it has a scheduled task or two running on it. Is this fact somewhere to be found in the XP Pro HELP system? I’m gonna go look now, but if you can…..

Reply | Quote

Certainly, I can! I don’t believe it’s in XP’s help, but here’s all you ever wanted to know about it.

The default of a normal Windows 2000/XP setup scans shared files for Scheduled Tasks. Sadly, this can result in a delay as long as 30 seconds when you try to view shared files across a network. It occurs because Windows 2000 is using the extra time to search the remote computer for any Scheduled Tasks. Though the fix is intended for only those affected, Windows 2000 & XP users will experience a noticeable increase in browsing speed of both the Windows Explorer and Internet Explorer.

Open up the Registry and go to :

HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/Current Version/Explorer/RemoteComputer/NameSpace

Under that branch, select the key :

{D6277990-4C6A-11CF-8D87-00AA0060F5BF}

right click it and select “Delete”. The change is effective immediately, no reboot required. You may want to export the registry branch so that you can restore the key if necessary. Note! This key also exists in Windows 98, but I haven’t tested whether or not it works. I’d be leery of deleting it from there, because this problem wasn’t widely reported in Win98, but if anyone wants to zap it, the same logic applies.

Off to the races….so to speak.

Reply | Quote

Mark,

I removed those shortcuts from the XP computer to the Network locations on the other machines (your memory is excellent, they are Win 98 SE computers) and

Reply | Quote