Hmm,
That's all a bit strange.

just to check again

you have
C:\Dwimperl\perl\bin\checkperl.exe

and

C:\Dwimperl\perl\bin\updateexec.pl

so the following commands should set everything up and run the script OK

set 
PATH=C:\Dwimperl\perl\site\bin;C:\Dwimperl\perl\vendor\bin;C:\Dwimperl\perl\bin;%PATH%

cd C:\Dwimperl\perl\bin

checkperl.exe updateexec.pl





On 16/11/2012 21:55, Brad Hodge wrote:
> So I just took a stab, and put it in C:\Dwimperl\perl\bin.  Upon running
> the below (as you typed it), I got *syntax error at (eval 12) line 1, near
> "<  >"
>
> *If that is not what I was supposed to do, just let me know.
>
> Thanks,
> Brad
> __________________________
>
> On Fri, Nov 16, 2012 at 2:59 PM, Brad Hodge<brad.h.ho...@gmail.com>  wrote:
>
>> Sorry to be slow, but which directory do I put the attached file?  Also...
>> did you say run it by C:\Dwimperl\perl\bin\checkperl.exe updateexec.pl(with 
>> a space between exe and update)?
>>
>> Thanks
>> Brad
>>
>> On Fri, Nov 16, 2012 at 2:47 PM, Mark Dootson<mark.doot...@znix.com>wrote:
>>
>>> Hi,
>>>
>>> The attached script should fix things for your particular case. If it
>>> does not, change line 8 to
>>>
>>> my $makemanifest = 0;
>>>
>>> which will remove the manifests altogether.
>>>
>>> As you have checkperl.exe as a working Perl executable, you can run the
>>> script with
>>>
>>> C:\Dwimperl\perl\bin\**checkperl.exe updateexec.pl
>>>
>>> I am thinking perhaps your issue is some version of MS XML libraries
>>> which choke on the spaces / comments etc in the original manifests (as the
>>> app loader tries to read them).
>>>
>>> If you still get 'application is not a valid executable' errors, there
>>> will be further info in the event log, but I'm guessing the above will fix
>>> it.
>>>
>>> Cheers
>>>
>>> Mark
>>>
>>>
>>> On 16/11/2012 18:01, Brad Hodge wrote:
>>>
>>>> That worked.  I got version information.
>>>>
>>>> Brad
>>>> ______________________
>>>>
>>>> On Fri, Nov 16, 2012 at 10:48 AM, Mark Dootson<mark.doot...@znix.com>**
>>>> wrote:
>>>>
>>>>   Oops! I meant for the last command
>>>>>
>>>>> C:\Dwimperl\perl\bin\**checkperl.exe -MWin32 -V
>>>>>
>>>>> On 16/11/2012 16:45, Mark Dootson wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Just to eliminate the possibility of your problem being some manifest
>>>>>> loading issue, I have uploaded a zip file
>>>>>>
>>>>>> http://www.wxperl.co.uk/**checkperl.zip<http://www.wxperl.co.uk/checkperl.zip>
>>>>>>
>>>>>> This contains a single executable 'checkperl.exe' that is really just
>>>>>> the perl.exe from Dwimperl with the manifest ripped out.
>>>>>>
>>>>>> So, if you extract this to C:\Dwimperl\perl\bin and the following
>>>>>> works,
>>>>>> the problem is in the manifests
>>>>>>
>>>>>> set PATH=C:\Dwimperl\perl\site\**bin;C:\Dwimperl\perl\bin;%**PATH%
>>>>>>
>>>>>> then
>>>>>>
>>>>>> C:\Dwimperl\perl\site\bin\**checkperl.exe -MWin32 -V
>>>>>>
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>> Mark
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 16/11/2012 16:10, Brad Hodge wrote:
>>>>>>
>>>>>>> Received no errors on either of those, but the second one ran without
>>>>>>> opening Padre. :(
>>>>>>> ______________________
>>>>>>>
>>>>>>> On Fri, Nov 16, 2012 at 10:06 AM, Mark Dootson<mark.doot...@znix.com
>>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>   Hi,
>>>>>>>>
>>>>>>>> OK. Next thing to test is if the Padre standalone executable works.
>>>>>>>>
>>>>>>> This
>>>>>
>>>>>> is at C:\Dwimperl\perl\site\bin\**padre.exe and has a manifest that
>>>>>>>> looks
>>>>>>>> correct to me but before it is run we must be sure that our PATH is
>>>>>>>> set
>>>>>>>> correctly so in a command prompt:
>>>>>>>>
>>>>>>>> set PATH=C:\Dwimperl\perl\site\**bin;C:\Dwimperl\perl\bin;%**PATH%
>>>>>>>>
>>>>>>>> then
>>>>>>>>
>>>>>>>> C:\Dwimperl\perl\site\bin\**padre.exe
>>>>>>>>
>>>>>>>>
>>>>>>>> does that work or does it fail too?
>>>>>>>>
>>>>>>>> Cheers
>>>>>>>>
>>>>>>>> Mark
>>>>>>>>
>>>>>>>> On 16/11/2012 16:00, Brad Hodge wrote:
>>>>>>>>
>>>>>>>>> Good thoughts Mark.
>>>>>>>>>
>>>>>>>>> I am running SP 3, so that shouldn't be an issue.
>>>>>>>>>
>>>>>>>>> I did try C:\Dwimperl\perl\bin\perl -MWin32 -V, and got the
>>>>>>>>> C:\Dwimperl\perl\bin\perl.exe is not a valid Win32 application
>>>>>>>>>
>>>>>>>> message.
>>>>>
>>>>>>
>>>>>>>>> Brad
>>>>>>>>> ____________________
>>>>>>>>>
>>>>>>>>> On Fri, Nov 16, 2012 at 9:48 AM, Mark Dootson<mark.doot...@znix.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>      wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>   Hi,
>>>>>>>>>>
>>>>>>>>>> This is probably not helpful but I had few problems installing and
>>>>>>>>>> running Dwimperl on 32bit Windows XP. I've tested installation and
>>>>>>>>>>
>>>>>>>>> use
>>>>>
>>>>>>   as both a privileged and a limited user.
>>>>>>>>>>
>>>>>>>>>> The only issue I found is that if installed whilst logged in as a
>>>>>>>>>> non
>>>>>>>>>> privileged user ( by using 'Run As' on the installer ) updates to
>>>>>>>>>> the
>>>>>>>>>> system such as the path etc. are not updated until I log out and
>>>>>>>>>> log
>>>>>>>>>> back in again. But this isn't surprising as the Dwimperl installer
>>>>>>>>>>
>>>>>>>>> does
>>>>>
>>>>>>   not attempt any system notifications etc.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> One thing I would check is that you are running latest Service Pack
>>>>>>>>>>
>>>>>>>>> ( 3
>>>>>
>>>>>>   ) with all updates applied.
>>>>>>>>>>
>>>>>>>>>> I seem to recall that the initial release of XP ( and maybe Service
>>>>>>>>>>
>>>>>>>>> Pack
>>>>>
>>>>>>   1 ) would choke on some features of an embedded manifest. The
>>>>>>>>>>
>>>>>>>>> embedded
>>>>>
>>>>>>   manifest in Perl 5.14.2 is technically incorrect as it refers to the
>>>>>>>>>> 'type' as 'Win32'. According to specification this is wrong and
>>>>>>>>>>
>>>>>>>>> should
>>>>>
>>>>>>   be 'win32' ( lowercase ) - but many Windows versisons seem to parse
>>>>>>>>>>
>>>>>>>>> this
>>>>>
>>>>>>   OK.
>>>>>>>>>>
>>>>>>>>>> If your XP is at Service Pack 1 ( or no service pack at all ) it
>>>>>>>>>>
>>>>>>>>> would
>>>>>
>>>>>>   be good if you could do a test so that the possible manifest problem
>>>>>>>>>>
>>>>>>>>> can
>>>>>
>>>>>>   be eliminated. I'll fix up a 'perl.exe' with no manifest and you
>>>>>>>>>>
>>>>>>>>> could
>>>>>
>>>>>>   test if that one works. But there is really no point doing this if
>>>>>>>>>>
>>>>>>>>> you
>>>>>
>>>>>>   have Service Pack 2 or above.
>>>>>>>>>>
>>>>>>>>>> Initially you could test the following:
>>>>>>>>>>
>>>>>>>>>> C:\Dwimperl\perl\bin\perl -MWin32 -V
>>>>>>>>>>
>>>>>>>>>> (note uppercase -V )
>>>>>>>>>>
>>>>>>>>>> and make sure it gives output.
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>>
>>>>>>>>>> Mark
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 16/11/2012 14:48, Brad Hodge wrote:
>>>>>>>>>>
>>>>>>>>>>> Mark,
>>>>>>>>>>>
>>>>>>>>>>> It's 32 bit XP.
>>>>>>>>>>>
>>>>>>>>>>> Brad
>>>>>>>>>>> ___________________
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Nov 16, 2012 at 8:46 AM, Mark Dootson<
>>>>>>>>>>> mark.doot...@znix.com
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>        wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>   Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> Brad, is your system 32 bit Windows XP or 64 bit Windows XP?
>>>>>>>>>>>>
>>>>>>>>>>>> I'll test out Dwinperl myself so I'm just checking that I get the
>>>>>>>>>>>>
>>>>>>>>>>> same
>>>>>
>>>>>>   environment as you.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards
>>>>>>>>>>>>
>>>>>>>>>>>> Mark
>>>>>>>>>>>>
>>>>>>>>>>>> On 16/11/2012 14:25, Brad Hodge wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> With regards to you your version email... I was successful
>>>>>>>>>>>>> running
>>>>>>>>>>>>>
>>>>>>>>>>>> perl -
>>>>>>>>>>
>>>>>>>>>>> v, and got all of the version information (v5.14.2).
>>>>>>>>>>>>>
>>>>>>>>>>>>> When I try to run c:\dwimperl\perl\bin\perl.exe
>>>>>>>>>>>>> c:\Dwimperl\perl\site\bin\**padre, I get a Windows error box
>>>>>>>>>>>>> stating
>>>>>>>>>>>>>
>>>>>>>>>>>> that
>>>>>>>>
>>>>>>>>>   c:\dwimperl\perl\bin\perl.exe is not a valid Win32 application.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Brad
>>>>>>>>>>>>> ____________________
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Nov 16, 2012 at 8:21 AM, Gabor Szabo<ga...@szabgab.com>
>>>>>>>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>   On Fri, Nov 16, 2012 at 4:19 PM, Brad Hodge<
>>>>>>>>>>>>>>
>>>>>>>>>>>>> brad.h.ho...@gmail.com>
>>>>>
>>>>>>   wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I did try both of the ones below.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> C:\Dwimperl\perl\site\bin\**padre got me the same results as
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> regular
>>>>>>>>>>
>>>>>>>>>>>   attempt.
>>>>>>>>>>>>>>> C:\Dwimperl\perl\site\bin>c:\**dwimperl\perl\bin\perl.exe
>>>>>>>>>>>>>>> gives me
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> the
>>>>>>>>
>>>>>>>>>   mesage
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 'dwimperl\perl\site\bin' is not recognized as an internal or
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> external
>>>>>>>>
>>>>>>>>>   command, operable program or batch file.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> sorry that was a wrong copy-paste on my part. I hope this is
>>>>>>>>>>>>>>
>>>>>>>>>>>>> better:
>>>>>
>>>>>>
>>>>>>>>>>>>>> c:\dwimperl\perl\bin\perl.exe c:\Dwimperl\perl\site\bin\**
>>>>>>>>>>>>>> padre
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Gabor
>>>>>>>>>>>>>> ______________________________**_________________
>>>>>>>>>>>>>> Padre-dev mailing list
>>>>>>>>>>>>>> Padre-dev@perlide.org
>>>>>>>>>>>>>> http://mail.perlide.org/**mailman/listinfo/padre-dev<http://mail.perlide.org/mailman/listinfo/padre-dev>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ______________________________**_________________
>>>>>>>>>>>>> Padre-dev mailing list
>>>>>>>>>>>>> Padre-dev@perlide.org
>>>>>>>>>>>>> http://mail.perlide.org/**mailman/listinfo/padre-dev<http://mail.perlide.org/mailman/listinfo/padre-dev>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ______________________________**_________________
>>>>>>>>>>>> Padre-dev mailing list
>>>>>>>>>>>> Padre-dev@perlide.org
>>>>>>>>>>>> http://mail.perlide.org/**mailman/listinfo/padre-dev<http://mail.perlide.org/mailman/listinfo/padre-dev>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ______________________________**_________________
>>>>>>>>>>> Padre-dev mailing list
>>>>>>>>>>> Padre-dev@perlide.org
>>>>>>>>>>> http://mail.perlide.org/**mailman/listinfo/padre-dev<http://mail.perlide.org/mailman/listinfo/padre-dev>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ______________________________**_________________
>>>>>>>>>> Padre-dev mailing list
>>>>>>>>>> Padre-dev@perlide.org
>>>>>>>>>> http://mail.perlide.org/**mailman/listinfo/padre-dev<http://mail.perlide.org/mailman/listinfo/padre-dev>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ______________________________**_________________
>>>>>>>>> Padre-dev mailing list
>>>>>>>>> Padre-dev@perlide.org
>>>>>>>>> http://mail.perlide.org/**mailman/listinfo/padre-dev<http://mail.perlide.org/mailman/listinfo/padre-dev>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ______________________________**_________________
>>>>>>>> Padre-dev mailing list
>>>>>>>> Padre-dev@perlide.org
>>>>>>>> http://mail.perlide.org/**mailman/listinfo/padre-dev<http://mail.perlide.org/mailman/listinfo/padre-dev>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ______________________________**_________________
>>>>>>> Padre-dev mailing list
>>>>>>> Padre-dev@perlide.org
>>>>>>> http://mail.perlide.org/**mailman/listinfo/padre-dev<http://mail.perlide.org/mailman/listinfo/padre-dev>
>>>>>>>
>>>>>>
>>>>>> ______________________________**_________________
>>>>>> Padre-dev mailing list
>>>>>> Padre-dev@perlide.org
>>>>>> http://mail.perlide.org/**mailman/listinfo/padre-dev<http://mail.perlide.org/mailman/listinfo/padre-dev>
>>>>>>
>>>>>
>>>>> ______________________________**_________________
>>>>> Padre-dev mailing list
>>>>> Padre-dev@perlide.org
>>>>> http://mail.perlide.org/**mailman/listinfo/padre-dev<http://mail.perlide.org/mailman/listinfo/padre-dev>
>>>>>
>>>>>
>>>>
>>>>
>>>> ______________________________**_________________
>>>> Padre-dev mailing list
>>>> Padre-dev@perlide.org
>>>> http://mail.perlide.org/**mailman/listinfo/padre-dev<http://mail.perlide.org/mailman/listinfo/padre-dev>
>>>>
>>>
>>> _______________________________________________
>>> Padre-dev mailing list
>>> Padre-dev@perlide.org
>>> http://mail.perlide.org/mailman/listinfo/padre-dev
>>>
>>>
>>
>
>
>
> _______________________________________________
> Padre-dev mailing list
> Padre-dev@perlide.org
> http://mail.perlide.org/mailman/listinfo/padre-dev

_______________________________________________
Padre-dev mailing list
Padre-dev@perlide.org
http://mail.perlide.org/mailman/listinfo/padre-dev

Reply via email to