Launching an application question
what they can't even let you do double quotation marks without a hiccup, you
expect them to handle spaces. :-)
the crazy thing is that microsoft deploys many of their software with spaces
also (even things as simple as "Program Files") and then like you said, you
get in trouble for having it that way.
and maybe if you can explain that you can explain why Microsoft had to mess
with me with Windows XP. I had all these great little scripts to my office
documents, but for some reason Microsoft decided lets not call it program
files\office\ etc anymore lets call it program files\office10\ etc. So now
I have to have a script look in the registry files for the location of the
office program to remap my desktop icons and worse, I have to run it in my
logon script because our office has w2k and xp workstations. So if I script
it one way and then I go to another operating system, then the link changes
to the new location. THat makes much more sense then just keeping their
products at the same location.
Sorry, I am allowed one tyrate a week against Microsoft aren't I? Or will
the MPD (Microsoft Police Department) ban me, spam me, and bug me????
Have a good day,
Robert
--
need to e-mail me off list just get rid of "your fears" and
drop me a line.
Quote:
> On Thu, 12 Jun 2003 14:17:08 -0400, "\"Crash\" Dummy"
> >The problem is the space in the pathname. You need to enclose it in
quotes:
> >WSHShell.Run ("""D:\Program Files\EndItAll\enditall.exe""
/K:cliponboots")
> >I have never forgiven Microsoft for allowing spaces in file/folder names.
That
> >was one of their dumber moves.
> That did it!!!! many thanks.
> Actually I've always "enjoyed" the spaces (or the ability to use them)
> but haven't really appreciated the problem they can cause until now. I
> would have thought that the MS programmers would have already allowed
> for this behavior .. apparently we have the right hand - left hand
> syndrome.
> Again, thanks.
> Don
