Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug under WinNT for both CPAN and ActivePerl distributions #148

Closed
p5pRT opened this issue Jul 2, 1999 · 6 comments
Closed

bug under WinNT for both CPAN and ActivePerl distributions #148

p5pRT opened this issue Jul 2, 1999 · 6 comments

Comments

@p5pRT
Copy link

p5pRT commented Jul 2, 1999

Migrated from rt.perl.org#953 (status was 'resolved')

Searchable as RT953$

@p5pRT
Copy link
Author

p5pRT commented Jul 2, 1999

From JohnLopez@vandorndemag.com

[note - I have modified the text from its original format to fit your screen]

Dear Sirs,

I am executing a Perl program
under the CPAN distribution for Win95,
release 5.00502. The program executes well,
calling certain external services that I need
including a Win32 version of RCP and RSH, as
well as a command line call to a CAD file
converter. All is functional and works appropriately.

I downloaded ActivePerl on a WinNT box,
configured it, and run the program. Again, it
executes without error, however it seems to blow
past the system(); function without execution.
I created a small test program that simply does​:

  $cmd=sprintf("dir > test.txt");
  system($cmd);

It is apparent that the system() command is
not functioning at all. Since I have some code
that read from redirection of command output from
a Unix server that I am RSHing to, obviously the
files are not created on the WinNT machine, and
the program die()s on the attempted open() to the file.

Further, to hedge against an ActivePerl issue,
I downloaded DOSPERL from CPAN and configured
it on the same NT box. It does the same thing.
System() does not function.

The only discernable difference that I can
think of is that I configure dcom95.exe on
the Win95 box. But to my understanding that
is not needed on WinNT 4.0 or >, and from the
associated documentation I understood that it
should not be implemented on the above, only for
Win95. Aside from this, to my knowledge, the Perl
environments are the same.

I understand that you surely are inundated
with mail from around the world, but please
consider this email. I have a mission critical
application that must be deployed soon on the
WinNT configuration to execute both interactively
with the character based interface that I have
provided for this beta run, and in CGI mode for
later implementations.

You assistance is greatly appreciated. Thank you.

Best Regards,

John Lopez
contract programmer
Van Dorn Demag Corporation

@p5pRT
Copy link
Author

p5pRT commented Jul 2, 1999

From [Unknown Contact. See original ticket]

subject​:system(); bug under WinNT
for both CPAN and ActivePerl distributions

[note - I have modified the text from its original format to fit your screen]

Dear Sirs,

I am executing a Perl program
under the CPAN distribution for Win95,
release 5.00502. The program executes well,
calling certain external services that I need
including a Win32 version of RCP and RSH, as
well as a command line call to a CAD file
converter. All is functional and works appropriately.

I downloaded ActivePerl on a WinNT box,
configured it, and run the program. Again, it
executes without error, however it seems to blow
past the system(); function without execution.
I created a small test program that simply does​:

  $cmd=sprintf("dir > test.txt");
  system($cmd);

It is apparent that the system() command is
not functioning at all. Since I have some code
that read from redirection of command output from
a Unix server that I am RSHing to, obviously the
files are not created on the WinNT machine, and
the program die()s on the attempted open() to the file.

Further, to hedge against an ActivePerl issue,
I downloaded DOSPERL from CPAN and configured
it on the same NT box. It does the same thing.
System() does not function.

The only discernable difference that I can
think of is that I configure dcom95.exe on
the Win95 box. But to my understanding that
is not needed on WinNT 4.0 or >, and from the
associated documentation I understood that it
should not be implemented on the above, only for
Win95. Aside from this, to my knowledge, the Perl
environments are the same.

I understand that you surely are inundated
with mail from around the world, but please
consider this email. I have a mission critical
application that must be deployed soon on the
WinNT configuration to execute both interactively
with the character based interface that I have
provided for this beta run, and in CGI mode for
later implementations.

You assistance is greatly appreciated. Thank you.

Best Regards,

John Lopez
contract programmer
Van Dorn Demag Corporation

@p5pRT
Copy link
Author

p5pRT commented Jul 2, 1999

From [Unknown Contact. See original ticket]

Your e-mail has been received by the Perl Bug Squashing Team.

Ticket ID '[ID 19990702.004]' has been assigned. Please include this ticket ID in the
subject line of any followup messages related to this issue.

This is an automatic confirmation message.
--
Perl Bug Squashing Team
perlbug@​perl.org
 

@p5pRT
Copy link
Author

p5pRT commented Jul 2, 1999

From [Unknown Contact. See original ticket]

subject​:system(); bug under WinNT
for both CPAN and ActivePerl distributions

[note - I have modified the text from its original format to fit your screen]

Dear Sirs,

I am executing a Perl program
under the CPAN distribution for Win95,
release 5.00502. The program executes well,
calling certain external services that I need
including a Win32 version of RCP and RSH, as
well as a command line call to a CAD file
converter. All is functional and works appropriately.

I downloaded ActivePerl on a WinNT box,
configured it, and run the program. Again, it
executes without error, however it seems to blow
past the system(); function without execution.
I created a small test program that simply does​:

  $cmd=sprintf("dir > test.txt");
  system($cmd);

It is apparent that the system() command is
not functioning at all. Since I have some code
that read from redirection of command output from
a Unix server that I am RSHing to, obviously the
files are not created on the WinNT machine, and
the program die()s on the attempted open() to the file.

Further, to hedge against an ActivePerl issue,
I downloaded DOSPERL from CPAN and configured
it on the same NT box. It does the same thing.
System() does not function.

The only discernable difference that I can
think of is that I configure dcom95.exe on
the Win95 box. But to my understanding that
is not needed on WinNT 4.0 or >, and from the
associated documentation I understood that it
should not be implemented on the above, only for
Win95. Aside from this, to my knowledge, the Perl
environments are the same.

I understand that you surely are inundated
with mail from around the world, but please
consider this email. I have a mission critical
application that must be deployed soon on the
WinNT configuration to execute both interactively
with the character based interface that I have
provided for this beta run, and in CGI mode for
later implementations.

You assistance is greatly appreciated. Thank you.

Best Regards,

John Lopez
contract programmer
Van Dorn Demag Corporation

1 similar comment
@p5pRT
Copy link
Author

p5pRT commented Jul 2, 1999

From [Unknown Contact. See original ticket]

subject​:system(); bug under WinNT
for both CPAN and ActivePerl distributions

[note - I have modified the text from its original format to fit your screen]

Dear Sirs,

I am executing a Perl program
under the CPAN distribution for Win95,
release 5.00502. The program executes well,
calling certain external services that I need
including a Win32 version of RCP and RSH, as
well as a command line call to a CAD file
converter. All is functional and works appropriately.

I downloaded ActivePerl on a WinNT box,
configured it, and run the program. Again, it
executes without error, however it seems to blow
past the system(); function without execution.
I created a small test program that simply does​:

  $cmd=sprintf("dir > test.txt");
  system($cmd);

It is apparent that the system() command is
not functioning at all. Since I have some code
that read from redirection of command output from
a Unix server that I am RSHing to, obviously the
files are not created on the WinNT machine, and
the program die()s on the attempted open() to the file.

Further, to hedge against an ActivePerl issue,
I downloaded DOSPERL from CPAN and configured
it on the same NT box. It does the same thing.
System() does not function.

The only discernable difference that I can
think of is that I configure dcom95.exe on
the Win95 box. But to my understanding that
is not needed on WinNT 4.0 or >, and from the
associated documentation I understood that it
should not be implemented on the above, only for
Win95. Aside from this, to my knowledge, the Perl
environments are the same.

I understand that you surely are inundated
with mail from around the world, but please
consider this email. I have a mission critical
application that must be deployed soon on the
WinNT configuration to execute both interactively
with the character based interface that I have
provided for this beta run, and in CGI mode for
later implementations.

You assistance is greatly appreciated. Thank you.

Best Regards,

John Lopez
contract programmer
Van Dorn Demag Corporation

@p5pRT
Copy link
Author

p5pRT commented Jul 2, 1999

From [Unknown Contact. See original ticket]

Your e-mail has been received by the Perl Bug Squashing Team.

Ticket ID '[ID 19990702.004]' has been assigned. Please include this ticket ID in the
subject line of any followup messages related to this issue.

This is an automatic confirmation message.
--
Perl Bug Squashing Team
perlbug@​perl.org
 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant