Problem

When working with earlier versions of Windows, IE: Win Srv 2003 and XP, this is not an issue. When using build forge to run a PERL scripts that outputs data to another location and or into a form. The data never arrives and is not being outputted or inputed into a form correctly. Example Command: "myperlscript.pl" This should work in earlier versions of Windows, but not in newer versions (Win 2008 and Win 7) When testing without the "perl" command, PL files (.pl) were configured to automatically run under the ActivePerl Perl Command Line Interpreter. The bfagent captures stdout and stderr from executed processes from the windows shell. When executing the script through the windows shell, perl is passing the output to the windows shell which then handles the funneling of stderr and stdout to different filehandles. That is how it works in 2003. he windows 2008 shell (powershell if it's different) seems to direct that output through non-posix-standard filehandles. posix has four perl classes it uses to handle the three standard outputs stdin stdout stederr. Well in windows 2003 and earlier versions windows funneled the stream data to standard ones, where as now it uses none standard. So while executing the script using perl as the shell, perl passes those outputs (stdout and sdterr) through the expected filehandles and it is properly captured. When running "perl foo.pl" perl handles the IO that's "normal" IO. Where as the windows 2008 shell would direct this data differently. pl2bat creates batch files that allow you to run perl scripts. This method requires you clarify perl in the command like mentioned earlier. You can now see how Micorosft has changed the way their shell works. By changing the file handlers on the shell and re-routing those. This change is Technically a way perl interacts with the data. So perl needs to capture the new streams etc. BF would then be able to utilize the functionality. So because MS changed, Perl has not and BF has not. Does this make sense? Thanks!