I guess that the original "actual problem" was in the part that got clipped
below the sig indicator line.
I didn't get the answer that I originally looked for, but some replies gave me
a few hints, and I did find a solution that worked for me in most cases.
Sorry about mentioning the "top posting" stuff at all (please ignore this
mention, too).
I could perhaps start another flurry by mentioning the sheer stupidity of
allowing filenames to contain spaces in the first place (which is the root
cause of my "original problem"). At least they could have not allowed spaces
to be both in filenames and used as delimiters, too!
Why not have allowed people to type in spaces when creating a filename, but
then replace them all with something like an underscore - it would have looked
about the same, but not have caused such grief. Most of the time people who
put spaces in names never type them again, anyway - they just click on them in
some GUI.
|I suppose we can chat about the theory of this for a long time. But what =
|is your actual problem.
|
|--=20
|----------------------------------------------------------
|
http://www.uscricket.com
||> Now I see a reason why some don't like top posting (I don't care =
|myself):
|> the "-- " at the beginning of one's sig makes all the stuff below that =
|from=20
|> earlier posts disappear. Oh well, on with the top post:
|>=20
|>=20
|> I looked at the suggestion below, and the idea that some had of =
|putting in a=20
|> command that could not be found by explorer - to trick it into =
|thinking that=20
|> it may be a non-longfilename aware command, and so pass the short =
|filename.
|> It turned out to be hard to find an easy way to specify a command that =
|
|> explorer could not find, but CreateProcess could. And then, it didn't =
|help=20
|> anyway, as the long filename got passed in any case.
|>=20
|> I did find that if I used a command that was an old DOS .COM file, it =
|did pass=20
|> the short filename. So, by renaming the .EXE that I was trying to run =
|to=20
|> COM, I got Explorer to pass the short filename. When the .COM file is =
|
|> executed, it is found to have an EXE header inside, so it still runs=20
|> correctly.
|>=20
|>=20
|> In the suggestion below, it says that %1 passes short filenames - my =
|problem=20
|> is that it does not. If I put in anything like the following shell =
|command:
|> cmd.exe /k echo %1
|> I get the long filename under WinXP, and the short filename in other =
|Windows=20
|> versions.
|>=20
|> In article <
[email protected]>, "Wesley Vogel"=20
|> |[[The posted tweak uses %1 as a parameter which passes short =
|filenames to
|> |cmd.exe. Changing the %1 to %l (lowercase L) passes the long filename
|> |instead. ]]
|> |
|> |Command prompt here with long filename (WXP-Pro)
|> |
http://tinyurl.com/3qazt
|> |
|> |