Re: Problems with long file paths (embedded spaces) after installi

Tech-Archive recommends: Fix windows errors by optimizing your registry

Check the value of the EXEFILE open command in the registry:

HKEY_CLASSES_ROOT\exefile\shell\open\command

It should be: "%1" %*

"dlaub" <dlaub@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E99E64F9-4D8B-4E20-8949-993979660179@xxxxxxxxxxxxxxxx
You'll note I said i have no problems when i run these executables from a
DOS
prompt - the issue is clicking on an executable in Windows Explorer where
the
path is assumed.

Yes, I want to solve this

Thanks

David

"NewScience" wrote:

So what's your question? Do you want to solve this?

The solution is to enclose the path in quotes.

"dlaub" <dlaub@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AE9565C6-A571-4FEE-B975-A9E4E3B20864@xxxxxxxxxxxxxxxx
The problem symptoms are:

When an executable program is started from Windows Explorer (versus DOS
prompt), the spaces (if any) in the file path to the executable are
misinterpreted as (invalid) command line arguments/file names to open:

e.g. C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\devenv.exe will WORK, but complains about not being
able
to
open files named:
a) Files\Microsoft
b) Visual
c) Studio
d) .net
e) 2003\Common7\IDE\devenv.exe

similar problems occurs with MS Office products, e.g. Outlook, Excel,
PowerPoint, as well as non Microsoft products, e.g. Adobe Reader, XML
SPY

e.g.

a) Excel complains: "Files\Microsoft.xls could not be found"
b) PowerPoint complains: "the path or file name for C:\Program is
invalid"
c) Outlook complains: "The command line argument is not valid"
d) XMLSpy complains: "Files\Altova\XMLSpy2005\XMLSpy.exe could not be
opened"

Note as stated above that this problem does NOT occur if starting the
executable from a DOS prompt, or invoking a file of the file type
associated
with that executable

Note also that copying the executable to a path with no embedded spaces
also
solves the problem, e.g. C:\

Note for Visual Studio specifically, invoking devenv.com instead of
devenv.exe also solves the problem

Note also that some executables (e.g. sql server enterprise manager)
have
no
problems, perhaps because they don't expect/support command line
arguments

? Related ? IE does NOT start with my home page: it tries to open:
http://files/Internet%20Explorer/iexplore.exe

Unistalling SP2 makes all these problems disappear
ReInstalling SP2 causes all these problems to re-appear
Un-Unistalling SP2 makes all these problems disappear again







.

Relevant Pages