Fix is out

grahams — Wed, 05 Mar 2008 14:24:16 -0800

Release 7.1 has shipped with this bug fix.

It is a bug

JanD — Tue, 04 Dec 2007 18:17:32 -0800

This is a bug in the --dyndll code that only happens on Vista. It will be fixed in PDK 7.0.1.

possibly a dyndll bug

grahams — Tue, 04 Dec 2007 09:20:25 -0800

I'm looking into this on the ticket you raised through support@activestate.com

Major problem with the--dyndll option under Vista

jw — Tue, 04 Dec 2007 02:11:47 -0800

All,

The following script when turned into an exe fails (with no error message) under vista:

#!perl -w
use strict;
use warnings;
use Win32::GUI();

Win32::GUI::GetOpenFileName (-title    => "Open File", 
                             -explorer => 1, 
                             -multisel => 1, 
                             );

Built using:

perlapp --norunlib --dyndll --exe GetOpenFileName.exe GetOpenFileName.pl

I've tried various versions of Perl (5.8.7 813 and 5.8.8 822) and PerlApp (6.0.2 and 7.0.0) but I always get the same result. I also tried the Win32::GUI 1.5 PPM from sourceforge and have built my own Win32::GUI - all fail. The exe runs fine under XP.

It comes down to the --dyndll - remove it and the exe runs fine.

In my main application I am also getting a full blown crash, again only when --dyndll is on.

I really need to use --dyndll as start-up times are really slow without it. When not using this option there are also issues with the application finding dll's and removing them once the application exits.

What's the best way to escalate this issue? Formally raise a bug report? I'm currently using 6.0.2 and would happy upgrade to 7.0.x once the issue is resolved.

Cheers,

jez.

ActiveState Community Site - Major problem with the--dyndll option under Vista - Comments

Fix is out

It is a bug

possibly a dyndll bug

Major problem with the--dyndll option under Vista