Re^3: Windows 10 and Win32::Process

... the last two times that I used Win32 to do something both functions were not working properly. ... Functions that did not work for me [were] ...

Just to be clear, do I understand correctly that we're talking about some functions in the Win32::Process module?

Give a man a fish: <%-{-{-{-<

Comment on Re^3: Windows 10 and Win32::Process Download Code

Replies are listed 'Best First'.

Re^4: Windows 10 and Win32::Process
by Veltro (Hermit) on Jun 27, 2018 at 14:57 UTC

No. It was just a general concern regards Win32 (and it's sub modules). I can't exactly remember anymore how I tried to kill the process. I used some method to pull the PID out of the system (edit: by name). But that was the method that failed. I looked in the core module and found out that a system command was used and that looks for some information that newer operating systems don't seem to display anymore. The sleep function that I was talking about is: Win32::Sleep

edit: I did some further digging and I found one example:

use strict ;
use warnings ;
use Win32::Process::Memory ;
my $proc = Win32::Process::Memory->new({ name => 'notepad.exe' });
printf "Commited Memory = %X Bytes\n", $proc->get_memtotal ;
__END__
Use of uninitialized value in lc at C:/Perl64/site/lib/Win32/Process/M
+emory.pm line 38.
...
Use of uninitialized value in lc at C:/Perl64/site/lib/Win32/Process/M
+emory.pm line 38.
Use of uninitialized value in subroutine entry at C:/Perl64/site/lib/W
+in32/Process/Memory.pm line 59.
Commited Memory = 0 Bytes
[download]

[reply]
[d/l]


Perl-Sensitive Sunglasses
	PerlMonks