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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|