XPost: alt.windows7.general   
   From: V@nguard.LH   
      
   "R.Wieser"  wrote:   
      
   > Vanguard,   
   >   
   >> R.Wieser wrote:   
   >>   
   >>> And by the way, I seem to have found information where you can,   
   >>> from the commandline, select a different printer.   
   >>   
   >> Yep, mentioned the /p arg back in my first response, too.   
   >   
   > show me where you mentioned /selecting a different printer from   
   > wordpads commandline/.   
      
   Again, "Yep, mentioned the /p arg back in my first response, too."   
      
   If /p doesn't work, try /pt.  You "discovered" what was already told to   
   you before.   
      
   > As for /why/ I do it ?  Thats as little your concern as the program I   
   > generate the document with was to J. P. .  And yes, you're /still/ fishing   
   > for something you can complain about.   
      
   Oh, we're supposed to come up with a solution to a vague scenario.  Your   
   request was answered days ago: Wordpad has no other arguments than   
   filespec and /p.  Others, and I, tried to provide workarounds.  You   
   chose to stick with your taskkill workaround.   
      
   >>> Hint : the "/FI" argument.   
   >>   
   >> Which can also specify image name or PID.   
   >   
   > Ah yes, trying to divert attention away from you having made a   
   > mistake.   
      
   I made no mistake.  No reason to use /FI with a condition testing on PID   
   or image name versus just using /pid  or /im .  Go ahead   
   and make it harder if you want.   
      
   The only feature /fi adds is testing on window title, but you still have   
   not disclosed how you use taskkill to know if that's how you kill, plus   
   it won't work any better than /im if you keep reopening the same file.   
      
   >> Have you yet disclosed just how you are running taskkill?   
   >> With which args?   
   >   
   > Why would I need to do disclose that ?   
      
   I gave specifics on how to use taskkill.  You kept it a secret.   
      
   >> Your "program" remains a mystery,   
   >   
   > Good. That way you could not be sidetracked by it either.   
      
   Because if you had identified the program, or noted it was a script,   
   others might've helped you with configuring the program or modifying it   
   to version by timestamp its output file allowing to both keep a history   
   of those files, if you chose, along with eliminating the problem with   
   Wordpad upon which you are fixated.   
      
   Wordpad can't be fixed unless you get its code to create NewWordpad with   
   MDI support, or add a buffer flush command-line arg, or however you wish   
   it to function.  It doesn't have the feature or command-line arguments   
   you would like it to have.  The program might be changed to timestamp   
   version its output file to eliminate the same-file problem with Wordpad,   
   but you don't want to look there.  Workarounds allow for renaming the   
   output file, but you don't want those, either.  Your use of taskkill is   
   just another workaround.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)