XPost: alt.windows7.general   
   From: V@nguard.LH   
      
   "R.Wieser"  wrote:   
      
   > Vanguard,   
   >   
   >> Couldn't you use a batch script as a wrapper to your program?   
   >   
   > Yes, I could.   
   >   
   > But all of those try to circumvent the problem itself (which will still rear   
   > its ugly head in other circumstances where the origional files contents   
   > change) as well as having their own side effects.   
   >   
   > I think that taskkill (which I mentioned in my initial post) is one of the   
   > few "solutions" (hacks) which seems to have no side effects - even though   
   > its usage seems to be limited to where a script launches the changed   
   > document.   
   >   
   > Regards,   
   > Rudy Wieser   
      
   The problem is that you refuse to acknowledge that Wordpad won't do what   
   you want, and keep expecting someone to come up with a solution where   
   Wordpad has command-line arguments other than filespec and /p (for   
   printing).  There are no other command-line args to Wordpad, including   
   no arg for forcing a flush of its buffer nor an arg to force a close of   
   the current doc to get a new copy loaded in its buffer.   
      
   Either you're stuck with how Wordpad functions, or you use a different   
   editor that does do what you want.  For some unknown reason, you are are   
   averse to using anything other than Wordpad.  There are far better   
   editors that can read RTF files.  You refuse the obvious in renaming the   
   output file.  Wordpad got bundled into Windows over 28 years ago.   
      
   The only advantage Wordpad has over Notepad is Wordpad supports RTF   
   (bold, italics, fonts, etc).  Although touched on before, you've yet to   
   disclose if the program's output is RTF at all, or just plain text   
   dumped into a .rtf file.   
      
   If you insist on using Wordpad, there is no good solution for you.   
   Using taskkill is no more a better a solution than others offered.  In   
   fact, some suggestions require less effort than you using taskkill.   
   Well, if that's your preference then go with it.  You asked how to solve   
   the problem besides using taskkill, but you're adamant on using Wordpad   
   and taskkill.  You started with that solution, and are determined to   
   continue using it.  If it's how you want, go for it.   
      
   I don't see how taskkill is a solution.  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?  No having to find the PID of the prior   
   instance of Wordpad.  No having to open a command shell to run "taskkill   
   /i wordpad.exe /f" (which would take out both the old and new instances   
   of Wordpad unless you wait until after taskkill to open the new   
   instance).  No having to dig into Task Manager to kill the old instance.   
   Just click on the "X" titlebar icon in the old instance before you load   
   the new instance of Wordpad.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)