XPost: alt.windows7.general   
   From: address@is.invalid   
      
   Vanguard,   
      
   > The problem is that you refuse to acknowledge that Wordpad won't   
   > do what you want,   
      
   Do tell me where you have posted that you think that that wordpad can't do   
   it.   
      
   *Thats* the problem.   
      
   For all I know none of you have got a clue, therefore ignore it and continue   
   with suggesting, possibly quite unneeded, work-arounds.  And yes, that has   
   happend to me before.   
      
   > If you insist on using Wordpad, there is no good solution for you.   
      
   I think that the others here will thank you for that assessment. :-)   
      
   Ofcourse, with the definition to your "good solution" being up for grabs it   
   doesn't mean too much.   
      
   > Using taskkill is no more a better a solution than others offered.   
      
   I beg to differ.  But as you have not brought forward any "and this is why"   
   to it there is nothing we could discuss in that direction ...   
      
   > You open Wordpad with a file, you want to open another instance of   
   > Wordpad to the same but since-changed file, but you involve taskkill   
   > to eliminate the earlier instance of Wordpad.  Why can't you just   
   > exit the earlier instance before you load the next one?   
      
   I can, and currently have to.   
      
   But I thought I made it rather clear why I wanted to eliminate that manual   
   middle step (and why!).   If not I suggest you re-read the thread, I've   
   mentioned it multiple times.   
      
   > No having to find the PID of the prior instance of Wordpad.   
      
   :-)  And with that you show that you have no clue how that taskkill works.   
      
   Suggestion : Open a command prompt, type "taskkill /?" and read.  You might   
   learn something.   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)