XPost: alt.windows7.general
From: V@nguard.LH
"R.Wieser" wrote:
> 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.
>>
>> Syntax: wordpad [/p]
>>
>> That's it. Get over your desire for Wordpad to have more args.
>
> You seem to have a problem with your chronology.
>
> I did not ask you if you *now* can come up with something, I asked you
> where you did *before* chewing me out over it.
>
> ... or did you hope I would not notice what you did ? :-)
See Message-ID where I mentioned filespec
and /p arguments, and only those. I said that 3 days ago. That was my
first response.
> 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.
>> You're going to leave Wordpad windows open indefinitely until
>> sometime later when you shutdown Windows?
>
>: -) You're fishing for reasons to why you can claim I'm wrong, and
>: than retroactivily put that onto the current case, aren't you ?
And you divert via lambaste by not saying why you need to keep Wordpad
open between separate runs on your program. To have you clarify, you
run your program, open Wordpad, and then immediately run your program
again? How often do you run the "program"?
>> I suggest *YOU* run at the command line:
>>
>> taskkill /?
>>
>> Specifying the PID is one way. Specifying the image name is another,
>> but takes out all processes with the same image name.
>
> I suggest you do that again yourself, and now /actually read/ what it says.
>
> Hint : the "/FI" argument.
Which can also specify image name or PID. Window title can also be
specified, but all instances of Wordpad you open to the same file will
have " - WordPad" as their title, so no different than
using "/im wordpad". Well, I didn't think about you having other
instances of Wordpad open to edit other files since the topic herein was
about you using Wordpad on the same file created by your "program". If
you have other instances of Wordpad open at the time, and they loaded
different files, then /im wordpad would nail more than those just for
the program's output file.
>> Really that hard for you to read the syntax description to see
>> PID is one way to specify what process to kill?
>
> I noticed, yes. The problem is that you said, in relation to what *I*
> was doing, "No having to find the PID of the prior instance of
> Wordpad.".
>
> No, I didn't need a PID, so its anybodies guess (although I have a suspicion
> or two) to why you mentioned it.
Have you yet disclosed just how you are running taskkill? With which
args? Your "program" remains a mystery, and so does how you use
taskkill. I'm not wasting time discussing every permutation of args and
their values to cover every way taskkill can be used. Stop hiding.
>> Apparently you profess that you don't use /pid or /im,
>
> You /realy/ have a reading problem, don't you ? I challenge you to quote
> where I said that I dodn't use /im. I'll even go further : quote where I
> mentioned /any/ of taskkill's arguments - *before* you tried to make claims
> to how I did it wrong ofcourse.
Exactly. You deliberately leave obtuse just how you use taskkill, so
others have to guess how you use it. Stop hiding.
>> so how ELSE do you use taskkill?
>
> Kid, your "you're wrong!" only exists because you, on purpose or
> otherwise, change what /has/ being said into something that better
> serves your own goals.
And you're still hiding. Instead of answering on how you use taskkill,
you obfuscate again.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
