Hi All,

Is there a way from te command line to show the run line
associated with a task.

The test task is
>raku -e "sleep 4"

>tasklist | grep -i raku
raku.exe 1540 Console 1 99,364 K

>PowerShell.exe Get-Process | grep -i raku
165 17 90052 98840 0.22 3388 1 raku

The reason is that I will sometimes have several raku (perl 6)
programs running a once. I need to tell them apart.

Many thanks,
-T

T <T@invalid.invalid> wrote:

> Hi All,
>
> Is there a way from te command line to show the run line
> associated with a task.
>
> The test task is
> >raku -e "sleep 4"
>
> >tasklist | grep -i raku
> raku.exe 1540 Console 1 99,364 K
>
> >PowerShell.exe Get-Process | grep -i raku
> 165 17 90052 98840 0.22 3388 1 raku
>
> The reason is that I will sometimes have several raku (perl 6)
> programs running a once. I need to tell them apart.
>
> Many thanks,
> -T

In Powershell, you could use:

$process = "raku.exe"
Get-WmiObject Win32_Process -Filter "name = '$process'" | Select-Object CommandLine

If you're using the same command line to run raku.exe (i.e., same args),
you won't tell the difference with multiple instances. You would need
to add something on the command line that was different for each
instance of raku.exe that you run.

The above is the PS example. The same can be done using wmic.exe, but
I'd have to search for the command line args.

On 2/8/24 13:47, VanguardLH wrote:
> T <T@invalid.invalid> wrote:
>
>> Hi All,
>>
>> Is there a way from te command line to show the run line
>> associated with a task.
>>
>> The test task is
>> >raku -e "sleep 4"
>>
>> >tasklist | grep -i raku
>> raku.exe 1540 Console 1 99,364 K
>>
>> >PowerShell.exe Get-Process | grep -i raku
>> 165 17 90052 98840 0.22 3388 1 raku
>>
>> The reason is that I will sometimes have several raku (perl 6)
>> programs running a once. I need to tell them apart.
>>
>> Many thanks,
>> -T
>
> In Powershell, you could use:
>
> $process = "raku.exe"
> Get-WmiObject Win32_Process -Filter "name = '$process'" | Select-Object CommandLine
>
> If you're using the same command line to run raku.exe (i.e., same args),
> you won't tell the difference with multiple instances. You would need
> to add something on the command line that was different for each
> instance of raku.exe that you run.
>
> The above is the PS example. The same can be done using wmic.exe, but
> I'd have to search for the command line args.

>PowerShell.exe Get-WmiObject Win32_Process -Filter "name = 'raku.exe'"
| Select-Object CommandLine
'Select-Object' is not recognized as an internal or external command,
operable program or batch file.

On 2/8/24 13:47, VanguardLH wrote:
> The same can be done using wmic.exe, but
> I'd have to search for the command line args

I do not mind wmic. I read the output into a sting
variable in Raku and have loads of fun with it.
Like 100 times more power than bash pipes.

Do you know the wmic command for this?

On Thu, 8 Feb 2024 15:47:57 -0600, VanguardLH <V@nguard.LH> wrote:

>T <T@invalid.invalid> wrote:
>
>> Hi All,
>>
>> Is there a way from te command line to show the run line
>> associated with a task.
>>
>> The test task is
>> >raku -e "sleep 4"
>>
>> >tasklist | grep -i raku
>> raku.exe 1540 Console 1 99,364 K
>>
>> >PowerShell.exe Get-Process | grep -i raku
>> 165 17 90052 98840 0.22 3388 1 raku
>>
>> The reason is that I will sometimes have several raku (perl 6)
>> programs running a once. I need to tell them apart.
>>
>> Many thanks,
>> -T
>
>In Powershell, you could use:
>
>$process = "raku.exe"
>Get-WmiObject Win32_Process -Filter "name = '$process'" | Select-Object CommandLine
>
>If you're using the same command line to run raku.exe (i.e., same args),
>you won't tell the difference with multiple instances. You would need
>to add something on the command line that was different for each
>instance of raku.exe that you run.
>
>The above is the PS example. The same can be done using wmic.exe, but
>I'd have to search for the command line args.

My understanding is that WMIC is on its last legs.

https://winaero.com/wmic-is-now-disabled-by-default-on-windows-11/

Microsoft has disabled by default the Windows Management Instrumentation (WMIC)
command-line tool. Currently, in Windows 11, WMIC is accessible as a feature on
demand (FOD) which is available out of the box, but it will be deactivated in
the next update.

In place of WMIC, Microsoft has introduced Windows PowerShell for WMI, asserting
that the removal of outdated features aids in reducing code complexity and
ensuring user safety and productivity.

The WMI command-line (WMIC) utility is deprecated as of Windows 10, version
21H1, and as of the 21H1 semi-annual channel release of Windows Server. This
utility is superseded by Windows PowerShell for WMI. This deprecation applies
only to the WMI command-line (WMIC) utility; Windows Management Instrumentation
(WMI) itself is not affected.

In a post on the TechCommunity forum, Microsoft states that they will disable
WMIC starting from January 29, 2024, beginning with preview builds of Windows
11. Eventually, Microsoft intends to remove WMIC from future Windows releases.

On 2/8/24 14:33, T wrote:
> On 2/8/24 13:47, VanguardLH wrote:
>>   The same can be done using wmic.exe, but
>> I'd have to search for the command line args
>
> I do not mind wmic.  I read the output into a sting
> variable in Raku and have loads of fun with it.
> Like 100 times more power than bash pipes.
>
> Do you know the wmic command for this?

>raku -e "sleep 14"

>wmic process where "name='raku.exe'" get ProcessID,SessionID,CommandLine
CommandLine ProcessId SessionId
raku -e "sleep 14" 5020 1

Yippee!

Thank you!

T <T@invalid.invalid> wrote:

> On 2/8/24 13:47, VanguardLH wrote:
>> T <T@invalid.invalid> wrote:
>>
>>> Hi All,
>>>
>>> Is there a way from te command line to show the run line
>>> associated with a task.
>>>
>>> The test task is
>>> >raku -e "sleep 4"
>>>
>>> >tasklist | grep -i raku
>>> raku.exe 1540 Console 1 99,364 K
>>>
>>> >PowerShell.exe Get-Process | grep -i raku
>>> 165 17 90052 98840 0.22 3388 1 raku
>>>
>>> The reason is that I will sometimes have several raku (perl 6)
>>> programs running a once. I need to tell them apart.
>>>
>>> Many thanks,
>>> -T
>>
>> In Powershell, you could use:
>>
>> $process = "raku.exe"
>> Get-WmiObject Win32_Process -Filter "name = '$process'" | Select-Object CommandLine
>>
>> If you're using the same command line to run raku.exe (i.e., same args),
>> you won't tell the difference with multiple instances. You would need
>> to add something on the command line that was different for each
>> instance of raku.exe that you run.
>>
>> The above is the PS example. The same can be done using wmic.exe, but
>> I'd have to search for the command line args.
>
> >PowerShell.exe Get-WmiObject Win32_Process -Filter "name = 'raku.exe'"
>| Select-Object CommandLine
>
> 'Select-Object' is not recognized as an internal or external command,
> operable program or batch file.

That was part of 1 line. Maybe your client sliced the long line into
two lines as part of its word wrap. I didn't try to put the directives
on the same line as the one that loads powershell.exe. I loaded
Powershell, and THEN entered the 2 command lines. When you tried to run
powershell.exe with the command as an argument, well, "|" is a pipe on a
DOS command line. The parsing would be incorrect how you did it.

Char Jackson <none@none.invalid> wrote:

> On Thu, 8 Feb 2024 15:47:57 -0600, VanguardLH <V@nguard.LH> wrote:
>
>>T <T@invalid.invalid> wrote:
>>
>>> Hi All,
>>>
>>> Is there a way from te command line to show the run line
>>> associated with a task.
>>>
>>> The test task is
>>> >raku -e "sleep 4"
>>>
>>> >tasklist | grep -i raku
>>> raku.exe 1540 Console 1 99,364 K
>>>
>>> >PowerShell.exe Get-Process | grep -i raku
>>> 165 17 90052 98840 0.22 3388 1 raku
>>>
>>> The reason is that I will sometimes have several raku (perl 6)
>>> programs running a once. I need to tell them apart.
>>>
>>> Many thanks,
>>> -T
>>
>>In Powershell, you could use:
>>
>>$process = "raku.exe"
>>Get-WmiObject Win32_Process -Filter "name = '$process'" | Select-Object CommandLine
>>
>>If you're using the same command line to run raku.exe (i.e., same args),
>>you won't tell the difference with multiple instances. You would need
>>to add something on the command line that was different for each
>>instance of raku.exe that you run.
>>
>>The above is the PS example. The same can be done using wmic.exe, but
>>I'd have to search for the command line args.
>
> My understanding is that WMIC is on its last legs.

It has been deprecated, and Microsoft wants users to move to PowerShell.
They need something to convince users to start using PowerShell. That's
why I showed how to use PowerShell to get a process' attributes, like
the command line to load the process.

On 2/8/24 16:41, VanguardLH wrote:
> T <T@invalid.invalid> wrote:
>
>> On 2/8/24 13:47, VanguardLH wrote:
>>> T <T@invalid.invalid> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Is there a way from te command line to show the run line
>>>> associated with a task.
>>>>
>>>> The test task is
>>>> >raku -e "sleep 4"
>>>>
>>>> >tasklist | grep -i raku
>>>> raku.exe 1540 Console 1 99,364 K
>>>>
>>>> >PowerShell.exe Get-Process | grep -i raku
>>>> 165 17 90052 98840 0.22 3388 1 raku
>>>>
>>>> The reason is that I will sometimes have several raku (perl 6)
>>>> programs running a once. I need to tell them apart.
>>>>
>>>> Many thanks,
>>>> -T
>>>
>>> In Powershell, you could use:
>>>
>>> $process = "raku.exe"
>>> Get-WmiObject Win32_Process -Filter "name = '$process'" | Select-Object CommandLine
>>>
>>> If you're using the same command line to run raku.exe (i.e., same args),
>>> you won't tell the difference with multiple instances. You would need
>>> to add something on the command line that was different for each
>>> instance of raku.exe that you run.
>>>
>>> The above is the PS example. The same can be done using wmic.exe, but
>>> I'd have to search for the command line args.
>>
>> >PowerShell.exe Get-WmiObject Win32_Process -Filter "name = 'raku.exe'"
>> | Select-Object CommandLine
>>
>> 'Select-Object' is not recognized as an internal or external command,
>> operable program or batch file.
>
> That was part of 1 line. Maybe your client sliced the long line into
> two lines as part of its word wrap. I didn't try to put the directives
> on the same line as the one that loads powershell.exe. I loaded
> Powershell, and THEN entered the 2 command lines. When you tried to run
> powershell.exe with the command as an argument, well, "|" is a pipe on a
> DOS command line. The parsing would be incorrect how you did it.
>

Since I am calling the command a a system call from a running
program, I have to call "powershell.exe". So that is the way
I test it too. And I think I goofed up the quotes.

Running from a powershell, the command works but does not find raku.exe

PS C:\> PowerShell.exe Get-WmiObject Win32_Process -Filter "name =
'raku.exe'" | Select-Object CommandLine

CommandLine
-----------
<nothing>

On 2/8/24 16:43, VanguardLH wrote:

> It has been deprecated, and Microsoft wants users to move to PowerShell.
> They need something to convince users to start using PowerShell. That's
> why I showed how to use PowerShell to get a process' attributes, like
> the command line to load the process.

What would be the equivalent powershell of

wmic process where "name='raku.exe'" get ProcessID,SessionID,CommandLine

?

On 2/8/2024 8:24 PM, T wrote:
> On 2/8/24 16:41, VanguardLH wrote:
>> T <T@invalid.invalid> wrote:
>>
>>> On 2/8/24 13:47, VanguardLH wrote:
>>>> T <T@invalid.invalid> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> Is there a way from te command line to show the run line
>>>>> associated with a task.
>>>>>
>>>>> The test task is
>>>>>       >raku -e "sleep 4"
>>>>>
>>>>>    >tasklist | grep -i raku
>>>>> raku.exe        1540 Console   1     99,364 K
>>>>>
>>>>>    >PowerShell.exe Get-Process | grep -i raku
>>>>>        165      17    90052      98840       0.22   3388   1 raku
>>>>>
>>>>> The reason is that I will sometimes have several raku (perl 6)
>>>>> programs running a once.  I need to tell them apart.
>>>>>
>>>>> Many thanks,
>>>>> -T
>>>>
>>>> In Powershell, you could use:
>>>>
>>>> $process = "raku.exe"
>>>> Get-WmiObject Win32_Process -Filter "name = '$process'" | Select-Object CommandLine
>>>>
>>>> If you're using the same command line to run raku.exe (i.e., same args),
>>>> you won't tell the difference with multiple instances.  You would need
>>>> to add something on the command line that was different for each
>>>> instance of raku.exe that you run.
>>>>
>>>> The above is the PS example.  The same can be done using wmic.exe, but
>>>> I'd have to search for the command line args.
>>>
>>>   >PowerShell.exe Get-WmiObject Win32_Process -Filter "name = 'raku.exe'"
>>> | Select-Object CommandLine
>>>
>>> 'Select-Object' is not recognized as an internal or external command,
>>> operable program or batch file.
>>
>> That was part of 1 line.  Maybe your client sliced the long line into
>> two lines as part of its word wrap.  I didn't try to put the directives
>> on the same line as the one that loads powershell.exe.  I loaded
>> Powershell, and THEN entered the 2 command lines.  When you tried to run
>> powershell.exe with the command as an argument, well, "|" is a pipe on a
>> DOS command line.  The parsing would be incorrect how you did it.
>>
>
>
> Since I am calling the command a a system call from a running
> program, I have to call "powershell.exe".  So that is the way
> I test it too.  And I think I goofed  up the quotes.
>
> Running from a powershell, the command works but does not find raku.exe
>
> PS C:\> PowerShell.exe Get-WmiObject Win32_Process -Filter "name = 'raku.exe'"  | Select-Object CommandLine
>
> CommandLine
> -----------
> <nothing>

If putting quotes around that pipe-equipped single line is too hard,
put it into a .ps1 script file.

powershell.exe myproject.ps1

Then myproject.ps1 can contain the hard-to-quote thing.

If you want a single source file, you can even have your master script
create the .ps1 file on the fly, so the master script controls what is in
it, and the myproject.ps1 is a "temporary" file of sorts.

While in Terminal, if you type "select" then hit tab key a few times,
you can see that, indeed, Select-Object is something powershell has internally.

Paul

On 2/8/2024 8:25 PM, T wrote:
> On 2/8/24 16:43, VanguardLH wrote:
>
>> It has been deprecated, and Microsoft wants users to move to PowerShell.
>> They need something to convince users to start using PowerShell.  That's
>> why I showed how to use PowerShell to get a process' attributes, like
>> the command line to load the process.
>
> What would be the equivalent powershell of
>
> wmic process where "name='raku.exe'" get ProcessID,SessionID,CommandLine
>
> ?

Google says:

You can try this cmdlet to get all available info of a process:

Get-Process -Name <process name> | Format-List *

then you can try this cmdlet to see the state of that process,
if it's True means it's running, if false means it's not running

Get-Process -Name <process name> | select Responding

While in Powershell, I did this, and it dumped a long (useless) stanza.
That represents the terminal I was working in.

Get-Process -name powershell | format-list *

Paul

On 2/9/24 09:34, Paul wrote:

> If putting quotes around that pipe-equipped single line is too hard,
> put it into a .ps1 script file.
>
> powershell.exe myproject.ps1
>
> Then myproject.ps1 can contain the hard-to-quote thing.
>
> If you want a single source file, you can even have your master script
> create the .ps1 file on the fly, so the master script controls what is in
> it, and the myproject.ps1 is a "temporary" file of sorts.
>
> While in Terminal, if you type "select" then hit tab key a few times,
> you can see that, indeed, Select-Object is something powershell has internally.
>
> Paul
>
>

What is the escape character in power shell?

Sort of like bash:
echo "\"\"\"\""
""""

On 2024-02-09 01:11, T wrote:
> On 2/8/24 14:33, T wrote:
>> On 2/8/24 13:47, VanguardLH wrote:
>>>   The same can be done using wmic.exe, but
>>> I'd have to search for the command line args
>>
>> I do not mind wmic.  I read the output into a sting
>> variable in Raku and have loads of fun with it.
>> Like 100 times more power than bash pipes.
>>
>> Do you know the wmic command for this?
>
>
> >raku -e "sleep 14"
>
> >wmic process where "name='raku.exe'" get ProcessID,SessionID,CommandLine
> CommandLine          ProcessId  SessionId
> raku  -e "sleep 14"  5020       1
>
> Yippee!
>
> Thank you!

I was going to say, from long memory, that the function call to start a
program returns the PID of that process.

--
Cheers, Carlos.

On 2/9/2024 5:28 PM, Carlos E.R. wrote:
> On 2024-02-09 01:11, T wrote:
>> On 2/8/24 14:33, T wrote:
>>> On 2/8/24 13:47, VanguardLH wrote:
>>>>   The same can be done using wmic.exe, but
>>>> I'd have to search for the command line args
>>>
>>> I do not mind wmic.  I read the output into a sting
>>> variable in Raku and have loads of fun with it.
>>> Like 100 times more power than bash pipes.
>>>
>>> Do you know the wmic command for this?
>>
>>
>>  >raku -e "sleep 14"
>>
>>  >wmic process where "name='raku.exe'" get ProcessID,SessionID,CommandLine
>> CommandLine          ProcessId  SessionId
>> raku  -e "sleep 14"  5020       1
>>
>> Yippee!
>>
>> Thank you!
>
> I was going to say, from long memory, that the function call to start a program returns the PID of that process.
>

These are part of the fork/exec part of UNIX/Linux.

Windows doesn't work quite the same way. It's like
eating at a fancy restaurant and the waiter forgot
your fork and spoon. Some utensils are missing.

The code for Firefox, would likely contain an example
of a workaround, whether it's a POSIX library or something
else, I do not know. I'm not a programmer of that caliber.
I'm a copy/paste programmer, and all I know is what I copy :-)

The original Quantum code for Firefox, was pretty clunky.
I expect the staff received "feedback" from people who
knew how to do that properly. It almost feels like
it is "fork/exec" quality code now. Originally, it
could take 20 seconds for Firefox to shut down. That kind
of clunky.

As it is, these multi-process programs, shutdown works
best if you kill the parent (the PPID). Process Explorer
from Sysinternals, makes this easy for you. Task Manager ? Not so much.

Paul

On 2024-02-10 06:59, Paul wrote:
> On 2/9/2024 5:28 PM, Carlos E.R. wrote:
>> On 2024-02-09 01:11, T wrote:
>>> On 2/8/24 14:33, T wrote:
>>>> On 2/8/24 13:47, VanguardLH wrote:
>>>>>   The same can be done using wmic.exe, but
>>>>> I'd have to search for the command line args
>>>>
>>>> I do not mind wmic.  I read the output into a sting
>>>> variable in Raku and have loads of fun with it.
>>>> Like 100 times more power than bash pipes.
>>>>
>>>> Do you know the wmic command for this?
>>>
>>>
>>>  >raku -e "sleep 14"
>>>
>>>  >wmic process where "name='raku.exe'" get ProcessID,SessionID,CommandLine
>>> CommandLine          ProcessId  SessionId
>>> raku  -e "sleep 14"  5020       1
>>>
>>> Yippee!
>>>
>>> Thank you!
>>
>> I was going to say, from long memory, that the function call to start a program returns the PID of that process.
>>
>
> These are part of the fork/exec part of UNIX/Linux.
>
> Windows doesn't work quite the same way. It's like
> eating at a fancy restaurant and the waiter forgot
> your fork and spoon. Some utensils are missing.

I was a Windows programmer in the 90's, and I know I had this problem. I
don't remember the details, what I did back then.

However, a google search suggests (the first paragraph is a single line):

powershell -executionPolicy bypass -command "& {$process = start-process
$args[0] -passthru -argumentlist $args[1..($args.length-1)]; exit
$process.id}" notepad test.txt

echo Process ID of new process: %errorlevel%

I can not test this at the moment.

--
Cheers, Carlos.

On 2/10/24 02:33, Carlos E.R. wrote:
> On 2024-02-10 06:59, Paul wrote:
>> On 2/9/2024 5:28 PM, Carlos E.R. wrote:
>>> On 2024-02-09 01:11, T wrote:
>>>> On 2/8/24 14:33, T wrote:
>>>>> On 2/8/24 13:47, VanguardLH wrote:
>>>>>>    The same can be done using wmic.exe, but
>>>>>> I'd have to search for the command line args
>>>>>
>>>>> I do not mind wmic.  I read the output into a sting
>>>>> variable in Raku and have loads of fun with it.
>>>>> Like 100 times more power than bash pipes.
>>>>>
>>>>> Do you know the wmic command for this?
>>>>
>>>>
>>>>   >raku -e "sleep 14"
>>>>
>>>>   >wmic process where "name='raku.exe'" get
>>>> ProcessID,SessionID,CommandLine
>>>> CommandLine          ProcessId  SessionId
>>>> raku  -e "sleep 14"  5020       1
>>>>
>>>> Yippee!
>>>>
>>>> Thank you!
>>>
>>> I was going to say, from long memory, that the function call to start
>>> a program returns the PID of that process.
>>>
>>
>> These are part of the fork/exec part of UNIX/Linux.
>>
>> Windows doesn't work quite the same way. It's like
>> eating at a fancy restaurant and the waiter forgot
>> your fork and spoon. Some utensils are missing.
>
> I was a Windows programmer in the 90's, and I know I had this problem. I
> don't remember the details, what I did back then.
>
> However, a google search suggests (the first paragraph is a single line):
>
> powershell -executionPolicy bypass -command "& {$process = start-process
> $args[0] -passthru -argumentlist $args[1..($args.length-1)]; exit
> $process.id}" notepad test.txt
>
> echo Process ID of new process: %errorlevel%
>
>
>
> I can not test this at the moment.
>
>

I tried. It is a mess of errors.

On 2024-02-11 22:24, T wrote:
> On 2/10/24 02:33, Carlos E.R. wrote:
>> On 2024-02-10 06:59, Paul wrote:
>>> On 2/9/2024 5:28 PM, Carlos E.R. wrote:
>>>> On 2024-02-09 01:11, T wrote:
>>>>> On 2/8/24 14:33, T wrote:
>>>>>> On 2/8/24 13:47, VanguardLH wrote:

....

>>> These are part of the fork/exec part of UNIX/Linux.
>>>
>>> Windows doesn't work quite the same way. It's like
>>> eating at a fancy restaurant and the waiter forgot
>>> your fork and spoon. Some utensils are missing.
>>
>> I was a Windows programmer in the 90's, and I know I had this problem.
>> I don't remember the details, what I did back then.
>>
>> However, a google search suggests (the first paragraph is a single line):
>>
>> powershell -executionPolicy bypass -command "& {$process = start-process $args[0] -passthru -argumentlist $args[1..($args.length-1)]; exit $process.id}" notepad test.txt
>>
>> echo Process ID of new process: %errorlevel%
>>
>>
>>
>> I can not test this at the moment.
>>
>>
>
> I tried.  It is a mess of errors.

Post them here for us to see and guess :-)

--
Cheers,
Carlos E.R.

In article <uq3g1f$24med$1@dont-email.me>, T wrote...
>
> Hi All,
>
> Is there a way from te command line to show the run line
> associated with a task.
>
> The test task is
> >raku -e "sleep 4"
>
>
> >tasklist | grep -i raku
> raku.exe 1540 Console 1 99,364 K
>
> >PowerShell.exe Get-Process | grep -i raku
> 165 17 90052 98840 0.22 3388 1 raku
>
> The reason is that I will sometimes have several raku (perl 6)
> programs running a once. I need to tell them apart.
>
> Many thanks,
> -T

I can't help with PowerShell, as I've never found time to invest the time to
learn it (sadly), but if you want to see the command line of a process easily,
download Process Explorer from systinternals.com (aka Microsoft) and it'll tell
you.

https://learn.microsoft.com/en-gb/sysinternals/downloads/process-explorer

--

Phil, London

On 2/12/24 06:28, Philip Herlihy wrote:
> In article <uq3g1f$24med$1@dont-email.me>, T wrote...
>>
>> Hi All,
>>
>> Is there a way from te command line to show the run line
>> associated with a task.
>>
>> The test task is
>> >raku -e "sleep 4"
>>
>>
>> >tasklist | grep -i raku
>> raku.exe 1540 Console 1 99,364 K
>>
>> >PowerShell.exe Get-Process | grep -i raku
>> 165 17 90052 98840 0.22 3388 1 raku
>>
>> The reason is that I will sometimes have several raku (perl 6)
>> programs running a once. I need to tell them apart.
>>
>> Many thanks,
>> -T
>
> I can't help with PowerShell, as I've never found time to invest the time to
> learn it (sadly), but if you want to see the command line of a process easily,
> download Process Explorer from systinternals.com (aka Microsoft) and it'll tell
> you.
>
> https://learn.microsoft.com/en-gb/sysinternals/downloads/process-explorer
>

I need to get it from the comm,and line. I use Process Explorer
all the time when I don't need the command line.

On 2/11/24 13:49, Carlos E. R. wrote:
> On 2024-02-11 22:24, T wrote:
>> On 2/10/24 02:33, Carlos E.R. wrote:
>>> On 2024-02-10 06:59, Paul wrote:
>>>> On 2/9/2024 5:28 PM, Carlos E.R. wrote:
>>>>> On 2024-02-09 01:11, T wrote:
>>>>>> On 2/8/24 14:33, T wrote:
>>>>>>> On 2/8/24 13:47, VanguardLH wrote:
>
> ...
>
>>>> These are part of the fork/exec part of UNIX/Linux.
>>>>
>>>> Windows doesn't work quite the same way. It's like
>>>> eating at a fancy restaurant and the waiter forgot
>>>> your fork and spoon. Some utensils are missing.
>>>
>>> I was a Windows programmer in the 90's, and I know I had this
>>> problem. I don't remember the details, what I did back then.
>>>
>>> However, a google search suggests (the first paragraph is a single
>>> line):
>>>
>>> powershell -executionPolicy bypass -command "& {$process =
>>> start-process $args[0] -passthru -argumentlist
>>> $args[1..($args.length-1)]; exit $process.id}" notepad test.txt
>>>
>>> echo Process ID of new process: %errorlevel%
>>>
>>>
>>>
>>> I can not test this at the moment.
>>>
>>>
>>
>> I tried.  It is a mess of errors.
>
> Post them here for us to see and guess :-)
>

>powershell -executionPolicy bypass -command "& {$process =
start-process $args[0] -passthru -argumentlist $args[1..($args.length-1)]

Missing closing '}' in statement block or type definition.
+ CategoryInfo : ParserError: (:) [],
ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingEndCurlyBrace

On 2024-02-12 22:07, T wrote:
> On 2/11/24 13:49, Carlos E. R. wrote:
>> On 2024-02-11 22:24, T wrote:
>>> On 2/10/24 02:33, Carlos E.R. wrote:
>>>> On 2024-02-10 06:59, Paul wrote:
>>>>> On 2/9/2024 5:28 PM, Carlos E.R. wrote:
>>>>>> On 2024-02-09 01:11, T wrote:
>>>>>>> On 2/8/24 14:33, T wrote:
>>>>>>>> On 2/8/24 13:47, VanguardLH wrote:
>>
>> ...
>>
>>>>> These are part of the fork/exec part of UNIX/Linux.
>>>>>
>>>>> Windows doesn't work quite the same way. It's like
>>>>> eating at a fancy restaurant and the waiter forgot
>>>>> your fork and spoon. Some utensils are missing.
>>>>
>>>> I was a Windows programmer in the 90's, and I know I had this
>>>> problem. I don't remember the details, what I did back then.
>>>>
>>>> However, a google search suggests (the first paragraph is a single
>>>> line):
>>>>
>>>> powershell -executionPolicy bypass -command "& {$process =
>>>> start-process $args[0] -passthru -argumentlist
>>>> $args[1..($args.length-1)]; exit $process.id}" notepad test.txt
>>>>
>>>> echo Process ID of new process: %errorlevel%
>>>>
>>>>
>>>>
>>>> I can not test this at the moment.
>>>>
>>>>
>>>
>>> I tried.  It is a mess of errors.
>>
>> Post them here for us to see and guess :-)
>>
>
> >powershell -executionPolicy bypass -command "& {$process =
> start-process $args[0] -passthru -argumentlist $args[1..($args.length-1)]
>
> Missing closing '}' in statement block or type definition.
>     + CategoryInfo          : ParserError: (:) [],
> ParentContainsErrorRecordException
>     + FullyQualifiedErrorId : MissingEndCurlyBrace
>

You did not enter the complete command.

Again, it is the next single line:

powershell -executionPolicy bypass -command "& {$process = start-process
$args[0] -passthru -argumentlist $args[1..($args.length-1)]; exit
$process.id}" notepad test.txt

All that in one single line. The next line in the script is:

echo Process ID of new process: %errorlevel%

--
Cheers, Carlos.

On 2/12/24 13:44, Carlos E.R. wrote:
> On 2024-02-12 22:07, T wrote:
>> On 2/11/24 13:49, Carlos E. R. wrote:
>>> On 2024-02-11 22:24, T wrote:
>>>> On 2/10/24 02:33, Carlos E.R. wrote:
>>>>> On 2024-02-10 06:59, Paul wrote:
>>>>>> On 2/9/2024 5:28 PM, Carlos E.R. wrote:
>>>>>>> On 2024-02-09 01:11, T wrote:
>>>>>>>> On 2/8/24 14:33, T wrote:
>>>>>>>>> On 2/8/24 13:47, VanguardLH wrote:
>>>
>>> ...
>>>
>>>>>> These are part of the fork/exec part of UNIX/Linux.
>>>>>>
>>>>>> Windows doesn't work quite the same way. It's like
>>>>>> eating at a fancy restaurant and the waiter forgot
>>>>>> your fork and spoon. Some utensils are missing.
>>>>>
>>>>> I was a Windows programmer in the 90's, and I know I had this
>>>>> problem. I don't remember the details, what I did back then.
>>>>>
>>>>> However, a google search suggests (the first paragraph is a single
>>>>> line):
>>>>>
>>>>> powershell -executionPolicy bypass -command "& {$process =
>>>>> start-process $args[0] -passthru -argumentlist
>>>>> $args[1..($args.length-1)]; exit $process.id}" notepad test.txt
>>>>>
>>>>> echo Process ID of new process: %errorlevel%
>>>>>
>>>>>
>>>>>
>>>>> I can not test this at the moment.
>>>>>
>>>>>
>>>>
>>>> I tried.  It is a mess of errors.
>>>
>>> Post them here for us to see and guess :-)
>>>
>>
>>  >powershell -executionPolicy bypass -command "& {$process =
>> start-process $args[0] -passthru -argumentlist $args[1..($args.length-1)]
>>
>> Missing closing '}' in statement block or type definition.
>>      + CategoryInfo          : ParserError: (:) [],
>> ParentContainsErrorRecordException
>>      + FullyQualifiedErrorId : MissingEndCurlyBrace
>>
>
>
> You did not enter the complete command.
>
> Again, it is the next single line:
>
> powershell -executionPolicy bypass -command "& {$process = start-process
> $args[0] -passthru -argumentlist $args[1..($args.length-1)]; exit
> $process.id}" notepad test.txt
>
>
> All that in one single line. The next line in the script is:
>
> echo Process ID of new process: %errorlevel%
>
>

All that does is open up an empty notepad.

I purposely left that part off so I could see what
the command was doing. It was crashing.

On 2/12/24 14:22, T wrote:
> On 2/12/24 13:44, Carlos E.R. wrote:
>> On 2024-02-12 22:07, T wrote:
>>> On 2/11/24 13:49, Carlos E. R. wrote:
>>>> On 2024-02-11 22:24, T wrote:
>>>>> On 2/10/24 02:33, Carlos E.R. wrote:
>>>>>> On 2024-02-10 06:59, Paul wrote:
>>>>>>> On 2/9/2024 5:28 PM, Carlos E.R. wrote:
>>>>>>>> On 2024-02-09 01:11, T wrote:
>>>>>>>>> On 2/8/24 14:33, T wrote:
>>>>>>>>>> On 2/8/24 13:47, VanguardLH wrote:
>>>>
>>>> ...
>>>>
>>>>>>> These are part of the fork/exec part of UNIX/Linux.
>>>>>>>
>>>>>>> Windows doesn't work quite the same way. It's like
>>>>>>> eating at a fancy restaurant and the waiter forgot
>>>>>>> your fork and spoon. Some utensils are missing.
>>>>>>
>>>>>> I was a Windows programmer in the 90's, and I know I had this
>>>>>> problem. I don't remember the details, what I did back then.
>>>>>>
>>>>>> However, a google search suggests (the first paragraph is a single
>>>>>> line):
>>>>>>
>>>>>> powershell -executionPolicy bypass -command "& {$process =
>>>>>> start-process $args[0] -passthru -argumentlist
>>>>>> $args[1..($args.length-1)]; exit $process.id}" notepad test.txt
>>>>>>
>>>>>> echo Process ID of new process: %errorlevel%
>>>>>>
>>>>>>
>>>>>>
>>>>>> I can not test this at the moment.
>>>>>>
>>>>>>
>>>>>
>>>>> I tried.  It is a mess of errors.
>>>>
>>>> Post them here for us to see and guess :-)
>>>>
>>>
>>>  >powershell -executionPolicy bypass -command "& {$process =
>>> start-process $args[0] -passthru -argumentlist
>>> $args[1..($args.length-1)]
>>>
>>> Missing closing '}' in statement block or type definition.
>>>      + CategoryInfo          : ParserError: (:) [],
>>> ParentContainsErrorRecordException
>>>      + FullyQualifiedErrorId : MissingEndCurlyBrace
>>>
>>
>>
>> You did not enter the complete command.
>>
>> Again, it is the next single line:
>>
>> powershell -executionPolicy bypass -command "& {$process =
>> start-process $args[0] -passthru -argumentlist
>> $args[1..($args.length-1)]; exit $process.id}" notepad test.txt
>>
>>
>> All that in one single line. The next line in the script is:
>>
>> echo Process ID of new process: %errorlevel%
>>
>>
>
>
> All that does is open up an empty notepad.
>
> I purposely left that part off so I could see what
> the command was doing.  It was crashing.
>

What was the web site you got that from?

On 2024-02-12 23:23, T wrote:
> On 2/12/24 14:22, T wrote:
>> On 2/12/24 13:44, Carlos E.R. wrote:
>>> On 2024-02-12 22:07, T wrote:
>>>> On 2/11/24 13:49, Carlos E. R. wrote:
>>>>> On 2024-02-11 22:24, T wrote:

>>> You did not enter the complete command.
>>>
>>> Again, it is the next single line:
>>>
>>> powershell -executionPolicy bypass -command "& {$process =
>>> start-process $args[0] -passthru -argumentlist
>>> $args[1..($args.length-1)]; exit $process.id}" notepad test.txt
>>>
>>>
>>> All that in one single line. The next line in the script is:
>>>
>>> echo Process ID of new process: %errorlevel%
>>>
>>>
>>
>>
>> All that does is open up an empty notepad.

Did you run that from the script?
It is two lines, the second line prints the PID, supposedly. It is not
that complicated to test.

The notepad is just a dummy process to run and find its PID, I assume.

>>
>> I purposely left that part off so I could see what
>> the command was doing.  It was crashing.
>>
>
> What was the web site you got that from?

I don't remember, but you can google it easily and find it again:

<https://stackoverflow.com/questions/9486960/how-to-get-pid-of-process-just-started-from-within-a-batch-file>

--
Cheers, Carlos.