Why do they need to be different processes?
Have a look at Win32::Process, it creates processes using the Windows API. A quick test shows that each explorer window shows up as its own process. It also includes a kill method that kills a given process ID.
I'm not sure that Win32::Process ships with ActiveState perl, but ppm shows a couple of versions available.
A quick proof-of-concept follows...
use strict;
use warnings;
use Win32::Process;
use Win32;
sub ErrorReport{
print Win32::FormatMessage( Win32::GetLastError())
}
my @processes;
for (0, 1) {
my $tmpPO;
Win32::Process::Create($tmpPO,
"F:\\Program Files\\Internet Explorer\\IEXPLORE.EXE",
"",
0,
CREATE_NEW_PROCESS_GROUP,
"." )|| die ErrorReport();
push @processes, $tmpPO;
print "Process $_ created: Process ID is ",
$processes[$_]->GetProcessID, ".\n";
}
print "Press enter to kill current processes:"; <STDIN>;
$processes[$_]->Kill(0) for (0, 1);
-
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.