Re: WP34S V3: Question about wp34s_asm.exe Message #30 Posted by Neil Hamilton (Ottawa) on 1 Jan 2012, 2:04 p.m., in response to message #24 by fhub
I think what is happening is that, for some reason, your executable is coming back with capital ".EXE" and not lower case ".exe". Why this would be different from my setup, I don't know -- unless its because I don't use the bare program name but tend to type "wp34s_asm.exe" instead of "wp34s_asm".
Unfortunately, my script is case specific and it is looking for lower case ".exe". The capitals are befuddling it. This is easily fixed by changing line 348 of the ASM from:
if( $script_name =~ /\.exe$/ ) {
to:
if( $script_name =~ /\.exe$/i ) {
and line 351 from:
$preproc =~ s/\.pl$/\.exe/;
to:
$preproc =~ s/\.pl$/\.exe/i;
This makes the search and replacement case insensitive. If you can try this at your end and let me know the result, I will make the official change in my source.
(This is deduced because the second invocation is still trying to run the Perl version of PP and not an EXE version. Therefore the search. and thus the replace as well, failed.)
The other thing this log is telling me is that you don't have the MS-DOS file associations setup correctly. (See the Assembler documentation, section 7.2.2, footnote 28.) This is why you are still required to use "perl" in front of your Perl commands. Fixing the file associations will solve this. As noted in the documentation, some packages set these up for you (all should!!) and some don't.
Question: If you have Indigo up and running, why not just use it with the native Perl scripts rather than go to the trouble of the EXE? If you get the file associations setup correctly, it should "just work".
|