title: Paths and CreateProcess
body: <p>I have a question regarding a symptom of my misuse of CreateProcess. I'm using the lpcommandline parameter to feed the path to my executable and parameters.  My misuse is that I have not surrounded the path to the exe with quotes.  </p>
  
  <p>My question is, why does the CreateProcess work just fine on most computers and not others? I know that the path will have a space in most of the time, yet on 90% of XP machines it works.  I of course found out my issue on those 10% where it did not.  But I'm wondering what is different on the machines where it does not work?  Is there a setting or a policy that any of you folks know about.  And yes, I am going to fix the quote issue. Just curious about why something like this would not have just failed off the bat.  </p>
  
  <p>So the code would look something like below and the szCommandLine Parameter would be something like below. Notice no quotes around the path to the exe.</p>
  
  <p>"C:\Program Files\My Company\doit.exe  parameter1 parameter2"</p>
  
  <pre><code>CreateProcess(
      NULL,           
      szCommandLine,  
      NULL,           
      NULL,           
      FALSE,          
      NULL, 
      NULL,  
      NULL,           
      &amp;si,            
      &amp;pi )       
  </code></pre>