XPost: alt.windows7.general   
   From: address@is.invalid   
      
   Vanguard,   
      
   >> show me where you mentioned /selecting a different printer from   
   >> from wordpads commandline/.   
   >   
   > Again, "Yep, mentioned the /p arg back in my first response, too."   
      
   Ah yes, the "/p which is somehow used for printing" there does explain how   
   to select a different printer adequatily ofcourse.  As does your   
   once-or-twice posted "wordpad [/p] ".   I see, my bad. /s   
      
   Kid, you really suck at your game.  Maybe honesty will serve you better.   
      
   > If /p doesn't work, try /pt.   
      
   You can ofcourse quote where you (or anyone else) said that ?  No ?  Why am   
   I not surprised ...   
      
   > Oh, we're supposed to come up with a solution to a vague scenario.   
      
   Lol.   
      
   If you think my scenario as described in my initial post is vague than you   
   no doubt will see blurry on even the clearest days.   There are no specs   
   that will be able to correct it.   
      
   > I gave specifics on how to use taskkill.  You kept it a secret.   
      
   Huh? If you gave the specifics than where/what can the secret be ?  You   
   already know everything. /s   
      
   And I distinctly remember having clued you in on the existence of the /FI   
   argument.  So no, you didn't.   
      
   Now if you would have been a nice kid and /asked/ for it I /could/ have   
   decided to provide that information.  But now ?  Fat chance.   
      
   >> 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 .   
      
   You're right, there is absolutily no reason to do that.  I give you that.   
      
   ... The only problem is that I never said that that was what you needed to   
   do to fix your problem.   
      
   So yes, you definitily made a mistake.  Multiple even.  The biggest one that   
   you stopped looking for something that /would/ have a reason to be used.   
   And yes, thats another hint.   
      
   > Because if you had identified the program, or noted it was a   
   > script, others might've helped you with configuring the program   
      
   I didn't ask for that.  I also was quite clear in stating that I wanted a   
   generic solution, not one that would be specific to my thanwhile situation.   
      
   You wish to refuse to acknowledge and work with that ?  Well, thats not my   
   problem, is it ?   
      
   Besides, when I posted my question I indicated that I already had a working   
   solution.  So, your offered help was quite unneeded.   
      
   > 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.   
      
   Who said I wanted to fix wordpad itself ?   I just wanted a generic solution   
   applicable to what wordpad does - or rather, /doesn't/ do - when   
   double-clicking a document file.   
      
   > Your use of taskkill is just another workaround.   
      
   "Just ?  I seem to remember to having said to you that its the one with the   
   least ammount of side-effects.   Shucks, I can't remember you ever having   
   responded to that.  I wonder why ...   
      
   But you ofcourse have a better solution ?    No, I didn't think so.  Ah yes,   
   that might be the above "why" .... :-)   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)