apache 2.2.21 and php 5.2.14 problem

[Massimo]

Hi all,

on a new installation i get this error:

bin\\httpd: Syntax error on line 112 of ./conf/httpd.conf: Cannot load D:/apache
/modules/modphp5.dll into server: SYS0002: The system cannot find the file speci
fied. (PHP5)

line 112:

LoadModule php5_module modules/modphp5.dll

of course i've checked all paths, files and dll, followed the instructions
but if i activate php i get this error and it's not a problem related to the path

any idea?
any help?

thanks
bye

massimo s.

[Paul Smedley]

Php5.dll is not in the lib path

Sent from my iPhone

> --
> You received this message because you are subscribed to the Google Groups "Apache for OS/2" group.
> To post to this group, send email to apa...@googlegroups.com.
> To unsubscribe from this group, send email to apache2+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/apache2?hl=en.
>

[Al Savage]

[from January 19, 2012]

> on a new installation i get this error:
>
> bin\\httpd: Syntax error on line 112 of ./conf/httpd.conf:

> Cannot load D:/apache/modules/modphp5.dll into server:
> SYS0002: The system cannot find the file specified. (PHP5)

>
> line 112:
>
> LoadModule php5_module modules/modphp5.dll

Thanks, Max, for asking this question a year ago. I just ran into the
same problem.

Paul, you might add a note about this in the README.OS2 for php.

--
Regards, Duvall, Wash.
Al S. http://nissandiesel.dyndns.org

[Al Savage]

For the search engines.

When I migrated my virtual hosts from my 1.3 setup to 2.2, I received
this error:

[F:\apache2\bin]httpd -t
[Mon Apr 29 15:19:58 2013] [warn] NameVirtualHost *:80 has no
VirtualHosts
Syntax OK

The usual advice is to avoid duplicate entries of

NameVirtualHost *:80

across all conf files in use, but I double-checked and I don't have
duplication.

I have not exhaustively researched, but my old vhosts began:
<VirtualHost *>

I changed them to:
<VirtualHost *:80>

and that has removed the warning on startup.

[Al Savage]

Does 2.2 still require the EMXOPTs that I'm using with 1.3?

From my 1.3 startup script:

/* The next SET EMXOPT needed for the Apache.
** EMX options "-h256 -!0x800" were added for
Apache/2 per http://silk.apana.org.au/apache/
** EMX options "-c -n -h1024" were added for PHP 4.0.3
** The "-!0x800" parameter is not documented in EMX docs.
** The "-!0x800" parameter causes a SYS1808 in TWM.exe
(X11 window manager).
*/
SET "EMXOPT=-c -n -h1024 -!0x800"

[Steven Levine]

In <55542.66.235.54.20....@www.ncplus.net>, on 04/29/13
at 02:54 PM, "Al Savage" <asa...@iname.com> said:

Hi Al,

>> bin\\httpd: Syntax error on line 112 of ./conf/httpd.conf:
>> Cannot load D:/apache/modules/modphp5.dll into server:
>> SYS0002: The system cannot find the file specified. (PHP5)
>> line 112:
>> LoadModule php5_module modules/modphp5.dll

>Paul, you might add a note about this in the README.OS2 for php.

A note about what? That php5.dll must be available in the LIBPATH? This
applied to any DLL required by any other DLL.

Steven

--
----------------------------------------------------------------------
"Steven Levine" <ste...@earthlink.net> eCS/Warp/DIY etc.
www.scoug.com www.ecomstation.com
----------------------------------------------------------------------

[Steven Levine]

In <55929.66.235.54.20....@www.ncplus.net>, on 04/29/13
at 03:26 PM, "Al Savage" <asa...@iname.com> said:

Hi,

>[F:\apache2\bin]httpd -t
>[Mon Apr 29 15:19:58 2013] [warn] NameVirtualHost *:80 has no
>VirtualHosts
>Syntax OK

>The usual advice is to avoid duplicate entries of

> NameVirtualHost *:80

>I have not exhaustively researched, but my old vhosts began:
> <VirtualHost *>

>I changed them to:
> <VirtualHost *:80>

>and that has removed the warning on startup.

This makes sense. * is not a wildcard in the strict sense, so I can
understand why the NameVirtualHost address spec needs to match the
VirtualHost address spec.

See

http://httpd.apache.org/docs/2.2/vhosts/name-based.html

[Steven Levine]

In <55939.66.235.54.20....@www.ncplus.net>, on 04/29/13

at 03:33 PM, "Al Savage" <asa...@iname.com> said:

Hi,

>Does 2.2 still require the EMXOPTs that I'm using with 1.3?

Nope. 2.2 is libc based, not emx based and will not even look for EMXOPT
in the environment.

[Al Savage]

>>Paul, you might add a note about this in the README.OS2 for php.
>
> A note about what? That php5.dll must be available in the LIBPATH?

Yes, that.

> This applied to any DLL required by any other DLL.

Paul's notes so far explain where to put modphp5.dll and the
loadmodule line to add to a conf. It's left to the user to figure out
where to put the long list of other dlls that are in the zip's modules
dir, and php.dll that's in the php dir, as well as where to place
php.exe and php.dll.

Not all users have the depth of background & experience to guess
correctly. Notes (that will sometimes actually be read) can cut down
the man-hours required to install this pkg considerably. It would
have in my case, surely.

More directly, my first thought when I saw php.dll was that it was
required for php.exe, and I'm not running php from the commandline nor
cgi. I thought that was a pretty good guess. Of course, I was wrong.

A single sentence in the readme would have saved both Max & I some
run-around time, and that's why I'm suggesting it. Hell, I'll even
volunteer to write the readme.

[Al Savage]

>>I have not exhaustively researched, but my old vhosts began:
>> <VirtualHost *>
>
>>I changed them to:
>> <VirtualHost *:80>
>

> This makes sense. * is not a wildcard in the strict sense, so I can
> understand why the NameVirtualHost address spec needs to match the
> VirtualHost address spec.

I've run 1.3 for over a decade with the wrong spec. I'm not surprised
that the syntax checking became more strict, and I think that's a Good
Thing. I am documenting an alternate reason that that particular
Apache warning can occur, because the first two pages of Google search
results do not list it as a cause. An undocumented cause, as it were.

[Al Savage]

>>Does 2.2 still require the EMXOPTs that I'm using with 1.3?
>
> Nope. 2.2 is libc based, not emx based and will not even look
> for EMXOPT in the environment.

The readme for Apache contains Thanks to Brian Havard for having done
the mojority of the work to make it run with EMX. To those of use who
do not work with the underpinnings, it's a reasonable question to ask:
are the EMXOPTs still needed. Thanks for confirming that they aren't.

[waldo kitty]

On 4/29/2013 18:33, Al Savage wrote:
> Does 2.2 still require the EMXOPTs that I'm using with 1.3?

i still use them because i have other apps that are compiled with EMX... as long
as i continue to have other EMX-based apps, i plan to keep those opt, too ;)

--
NOTE: No off-list assistance is given without prior approval.
Please keep mailing list traffic on the list unless
private contact is specifically requested and granted.

[waldo kitty]

On 4/29/2013 19:06, Steven Levine wrote:
> In<55542.66.235.54.20....@www.ncplus.net>, on 04/29/13
> at 02:54 PM, "Al Savage"<asa...@iname.com> said:
>
> Hi Al,
>
>>> bin\\httpd: Syntax error on line 112 of ./conf/httpd.conf:
>>> Cannot load D:/apache/modules/modphp5.dll into server:
>>> SYS0002: The system cannot find the file specified. (PHP5)
>>> line 112:
>>> LoadModule php5_module modules/modphp5.dll
>
>> Paul, you might add a note about this in the README.OS2 for php.
>
> A note about what? That php5.dll must be available in the LIBPATH? This
> applied to any DLL required by any other DLL.

in the LIBPATH or in the specified modules directory??

[waldo kitty]

i must be missing something but then i do not specify the port for my virtual
hosts in 1.3... the only port i specify is 80 and that in the general setup
section... my v1.3 virtual hosts section starts off as

NameVirtualHost *
<VirtualHost *>
ServerName virtual.domain1.here
DocumentRoot x:/foo/bar1
[...]
</VirtualHost>
<VirtualHost *>
ServerName virtual.domain2.here
DocumentRoot x:/foo/bar2
[...]
</VirtualHost>
<VirtualHost *>
ServerName virtual.domain3.here
DocumentRoot x:/foo/bar3
[...]
</VirtualHost>


on my linux installation, it is a little bit different but still pretty much the
same except that everything does use that *:80...

Server Version: Apache/2.2.14 (Ubuntu)
Server Built: Mar 8 2013 16:42:47

each domain is defined in its own conf file...

[snip domain1.conf]
#domain1.conf
<VirtualHost *:80>
ServerName virtual.domain1.here
DocumentRoot x:/foo/bar1
[...]
</VirtualHost>
[/snip]

[snip domain2.conf]
#domain2.conf
<VirtualHost *:80>
ServerName virtual.domain2.here
DocumentRoot x:/foo/bar2
[...]
</VirtualHost>
[/snip]

[snip domain3.conf]
#domain3.conf
<VirtualHost *:80>
ServerName virtual.domain3.here
DocumentRoot x:/foo/bar3
[...]
</VirtualHost>
[/snip]


and in ports.conf there is this...

[snip ports.conf]
NameVirtualHost *:80
Listen 80

<IfModule mod_ssl.c>
# If you add NameVirtualHost *:443 here, you will also have to change
# the VirtualHost statement in /etc/apache2/sites-available/default-ssl
# to <VirtualHost *:443>
# Server Name Indication for SSL named virtual hosts is currently not
# supported by MSIE on Windows XP.
Listen 443
</IfModule>

<IfModule mod_gnutls.c>
Listen 443
</IfModule>
[/snip]


so i'm not sure i'm understanding the problem unless the OS2 version is highly
different than the linux version...

[Al Savage]

>>>> <VirtualHost *>
>>>
>>>> I changed them to:
>>>> <VirtualHost *:80>

> i must be missing something but then i do not specify the
> port for my virtual hosts in 1.3... the only port i specify
> is 80 and that in the general setup section... my
> v1.3 virtual hosts section starts off as
>
> NameVirtualHost *
> <VirtualHost *>

[ . . . ]

> on my linux installation, it is a little bit different but
> still pretty much the same except that everything does
> use that *:80...
>

> [snip domain1.conf]
> #domain1.conf
> <VirtualHost *:80>

[ . . . ]

> and in ports.conf there is this...
>
> [snip ports.conf]
> NameVirtualHost *:80
> Listen 80

> so i'm not sure i'm understanding the problem unless
> the OS2 version is highly different than the linux
> version...

Yours & my 1.3 <VirtualHost *> are the same.

My OS/2 2.2 and your linux 2.2 <VirtualHost *:80> are the same.

It appears that v2.2 requires the port specified at the vhost level,
as v1.3 didn't. But I haven't gone back and actually read the 1.3
vhost docs, as I don't really care.

My takeaway is that when migrating a vhost conf v1.3->v2.2, one must
edit the VirtualHost sections and add port specifiers. I don't have
an issue with that. However, I'd like to make it easier to know about
that, which is point of my first post.

Heck, I was just editing my old Apache startup script (migrating) and
found a note to myself about the EMXOPTs not being needed anymore for
Apache 2.x . So I knew about that years ago, I just forgot. I write
myself notes everywhere, and the internet is an everywhere.

[Steven Levine]

In <517F089D...@windstream.net>, on 04/29/13
at 07:56 PM, waldo kitty <wkit...@windstream.net> said:

Hi,

>> A note about what? That php5.dll must be available in the LIBPATH? This
>> applied to any DLL required by any other DLL.

>in the LIBPATH or in the specified modules directory??

FWIW, putting php5.dll in the modules directory will probably not work.
Apache does not use the LIBPATH to load modules from the modules
directory, so there's no need for the modules directory to be in the
LIBPATH.

I've seen setups that add the modules directory to the LIBPATH, but it is
neither needed or used.

My preferred location for misc DLLs used only by apache is in the same
directory as httpd.dll. This happens to be apache22/bin in my case.
Httpd.dll is loaded via LIBPATH so to my way of thinking that's where the
misc DLLs should be too.

[Steven Levine]

In <3518.66.235.54.20....@www.ncplus.net>, on 04/29/13

at 04:46 PM, "Al Savage" <asa...@iname.com> said:

Hi Al,

>I've run 1.3 for over a decade with the wrong spec.

It's not really wrong for 1.3. See

http://httpd.apache.org/docs/1.3/vhosts/name-based.html

and it's not really wrong for 2.x. It just may be wrong in both cases to
as you say it's a good thing that the warning exists.

The port spec has always been and still is optional.

*:80 is the same as * if you are only listening to port 80.

[Steven Levine]

In <517F0F83...@windstream.net>, on 04/29/13
at 08:25 PM, waldo kitty <wkit...@windstream.net> said:

Hi Waldo,

>NameVirtualHost *
><VirtualHost *>
> ServerName virtual.domain1.here
> DocumentRoot x:/foo/bar1
> [...]
></VirtualHost>
><VirtualHost *>
> ServerName virtual.domain2.here
> DocumentRoot x:/foo/bar2
> [...]
></VirtualHost>
><VirtualHost *>
> ServerName virtual.domain3.here
> DocumentRoot x:/foo/bar3
> [...]
></VirtualHost>

This is straight out of the docs. See

http://httpd.apache.org/docs/1.3/vhosts/name-based.html

>it is a little bit different but still pretty
>much the same except that everything does use that *:80...

>Server Version: Apache/2.2.14 (Ubuntu)
>Server Built: Mar 8 2013 16:42:47

>each domain is defined in its own conf file...

>[snip domain1.conf]
>#domain1.conf
><VirtualHost *:80>
> ServerName virtual.domain1.here
> DocumentRoot x:/foo/bar1
> [...]
></VirtualHost>
>[/snip]

>[snip domain2.conf]
>#domain2.conf
><VirtualHost *:80>
> ServerName virtual.domain2.here
> DocumentRoot x:/foo/bar2
> [...]
></VirtualHost>
>[/snip]

This too is straight out of the docs

http://httpd.apache.org/docs/2.2/vhosts/name-based.html

>so i'm not sure i'm understanding the problem unless the OS2 version is
>highly different than the linux version...

The preferred style changed between 1.x and 2.x which means if you only
update so of the addr:port references, you will get a warning because they
don't match exactly. It's just a warning so I have to assume that in the
vast majority of cases, apache will guess correctly what you meant.

[Al Savage]

>>> A note about what? That php5.dll must be available in the LIBPATH?

>>> This applied to any DLL required by any other DLL.
>
>>in the LIBPATH or in the specified modules directory??
>

> My preferred location for misc DLLs used only by apache is in the same
> directory as httpd.dll. This happens to be apache22/bin in my case.

I have both httpd.exe & httpd.dll in F:\Apache2\bin; I put php.dll
there and it worked. But . . .

> Httpd.dll is loaded via LIBPATH so to my way of thinking that's
> where the misc DLLs should be too.

. . . nothing on F: is in the LIBPATH, and I don't use a BEGINLIBPATH
when starting Apache.

[Steven Levine]

In <2097.66.235.54.20....@www.ncplus.net>, on 04/29/13

at 08:10 PM, "Al Savage" <asa...@iname.com> said:

Hi Al,

>> Httpd.dll is loaded via LIBPATH so to my way of thinking that's
>> where the misc DLLs should be too.

>. . . nothing on F: is in the LIBPATH, and I don't use a BEGINLIBPATH
>when starting Apache.

Sure it is. You have a . in LIBPATH and you are startd apache with the
current directory set to f:\Apache2\bin.

[Dan Napier]

And I would be glad to help, If I understand it-- any idiot could understand. I have spent countless hours over the DLL locations. Finally putting everything in c:\os2\dll-- Yes Steve I know that is a really bad idea, but the other options are at best a WAG for me. --

Add me to the editor list and I will gladly do whatever is helpful.
Dan Napier

Wag = Wild Ass Guess
For WAG support questions call 800-123-4567

--
You received this message because you are subscribed to the Google Groups "Apache for OS/2" group.

To unsubscribe from this group and stop receiving emails from it, send an email to apache2+u...@googlegroups.com.

To post to this group, send email to apa...@googlegroups.com.

Visit this group at http://groups.google.com/group/apache2?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.

[voy...@sbt.net.au]

Not sure how relevant my comment is,
but, i usually place non-op-sys dlls in something like  f:/dll, and, have that on libpath

Not sure how relevant...

Dan Napier <d...@cihcsp.com> wrote:

And I would be glad to help, If I understand it-- any idiot could understand.  I have spent countless hours over the DLL locations.  Finally putting everything in c:\os2\dll-- Yes Steve I know that is a really bad idea, but the other options are at best a WAG for me. --

Add me to the editor list and I will gladly do whatever is helpful.
Dan Napier

Wag =  Wild Ass  Guess
For  WAG support questions call 800-123-4567

-----Original Message-----
From: apa...@googlegroups.com [mailto:apa...@googlegroups.com] On Behalf Of Al Savage
Sent: Monday, April 29, 2013 4:43 PM
To: apa...@googlegroups.com
Subject: Re: [Apache/2] apache 2.2.21 and php 5.2.14 problem


 Paul,
you might add a note about this in the README.OS2 for php.

A note about what?  That php5.dll must be available in the LIBPATH?

Yes, that.

This applied to any DLL required by any other DLL.

Paul's notes so far explain where to put modphp5.dll and the loadmodule line to add to a conf.  It's left to the user to figure out where to put the long list of other dlls that are in the zip's modules dir, and php.dll that's in the php dir, as well as where to place php.exe and php.dll.

Not all users have the depth of background & experience to guess correctly.  Notes (that will sometimes actually be read) can cut down the man-hours required to install this pkg considerably.  It would have in my case, surely.

More directly, my first thought when I saw php.dll was that it was required
  for
php.exe, and I'm not running php from the commandline nor cgi.  I thought that was a pretty good guess.  Of course, I was wrong.

A single sentence in the readme would have saved both Max & I some run-around time, and that's why I'm suggesting it.  Hell, I'll even volunteer to write the readme.

--

Sent from Kaiten Mail. Please excuse my brevity.

[Massimo]

yes, sure :)

often i can't neither understand emails from Paul, Steven or Peter Moylan
since they are too much complicated for me

it seems to read an O'reilly book ;)

massimo

[Massimo]

i had also problems since eCS put in libpath some old gcc-libc dlls (under ecs\dll)
and those ones come "before" my ones that were updated


massimo

[voy...@sbt.net.au]

ahh, I see what you mean...

[Steven Levine]

In <51803DF5...@ecomstation.it>, on 04/30/13
at 11:56 PM, Massimo <m...@ecomstation.it> said:

Hi,

>it seems to read an O'reilly book ;)

Hmm. The O'Reilly books have a reputation of being extremely readable and
useful for non-technical, entry level users.

I don't find them all that useful for my needs because they omit a lot of
technical details that are typically on my need to know list.

[waldo kitty]

On 4/30/2013 17:44, Dan Napier wrote:
> And I would be glad to help, If I understand it-- any idiot could understand.
> I have spent countless hours over the DLL locations. Finally putting
> everything in c:\os2\dll-- Yes Steve I know that is a really bad idea, but
> the other options are at best a WAG for me. --

i generally create an 3rd_dlls directory which i include in my libpath and put
all of my 3rd party dlls in there... every path that i add to libpath and path
is all placed at the front of the line so that they come before anything else
that may already be on the system...

> Wag = Wild Ass Guess For WAG support questions call 800-123-4567

hehehe... eWAG is an educated WAG... and then there's also sWAG for stupid or
silly WAGs :P ;)

[waldo kitty]

On 4/30/2013 18:02, Massimo wrote:
> i had also problems since eCS put in libpath some old gcc-libc dlls (under ecs\dll)
> and those ones come "before" my ones that were updated

you should add your modifications to the path and libpath to the beginning of
those lines instead of at the end of them... that way your stuff takes
precedence over the system default stuff ;)

[Dan Napier]

Well I guess Massimo is another candidate for the Read Me by "OH Reallly" I think I have been getting caught by the ecs\dll problem, Thanks Massimio, I did not look there!
So Far the editors of "Oh Really" for OS2 Apache are Al, Dan and I hope Massimio!

Beh credo che Massimo è un altro candidato per il "Read Me" di "OH Reallly" Penso che sono stato farsi prendere dal ecs \ dll problema, Grazie Massimio, non mi guardo lì!
Finora i redattori di "Oh, davvero" per OS2 Apache sono Al, Dan e spero Massimio!

Perhaps the Book "Oh Davvero" would be the best titile!


Dan Napier
Noli spurios te contundere

[Al Savage]

Hello, Dan:

> And I would be glad to help, If I understand it-- any idiot could
> understand. I have spent countless hours over the DLL locations.
> Finally putting everything in c:\os2\dll-- Yes Steve I know that is a
> really bad idea, but the other options are at best a WAG for me. --
>
> Add me to the editor list and I will gladly do whatever is helpful.
> Dan Napier

Find attached my first pass at an attempt to add to the README.OS2

[Al Savage]

(sorry: I think I fumbled on the Send button early by accident)

Hello, Dan:

> And I would be glad to help, If I understand it-- any idiot could
> understand. I have spent countless hours over the DLL locations.
> Finally putting everything in c:\os2\dll-- Yes Steve I know that is a
> really bad idea, but the other options are at best a WAG for me. --
>
> Add me to the editor list and I will gladly do whatever is helpful.
> Dan Napier

Find attached my first pass at an attempt to add to the README.OS2 for
php for OS/2. Make any additions/corrections you feel necessary.

[Steven Levine]

In <4319.66.235.54.20....@www.ncplus.net>, on 05/01/13
at 07:24 AM, "Al Savage" <asa...@iname.com> said:

Hi guys,

>Find attached my first pass at an attempt to add to the README.OS2 for
>php for OS/2. Make any additions/corrections you feel necessary.

Looks OK. I recommend you wrap the lines at 72 columns or so.

[waldo kitty]

On 5/1/2013 10:24, Al Savage wrote:
> Find attached my first pass at an attempt to add to the README.OS2 for
> php for OS/2. Make any additions/corrections you feel necessary.

* Extract /php.dll to a dir on LIBPATH . If using with Apache, you can
generally put it where httpd.dll resides (/Apache2, etc.)

this line seems to be in error as there is no php.dll but there is a php5.dll...

* Extract modphp5.map to ???
* Extract php5.map to ???

my understanding from discussions on the weasel, ftpser and/or this apache2
lists is the following

modphp5.map would go in the same directory as modphp5.dll
php5.map would go in the same directory as php5.exe

however, there is a problem with the php5.map file because there are two
php5.exe files... one for normal command line usage and one for cgi usage...
there does not appear to be any indication of which exe this map file is for...

perhaps the build script needs to be modified a bit to place the map files in
the same directory as the dll or exe they go with... it is possible that there
are really two php5.map files generated but the second one overwrites the first
because they are output to the same directory...

FWIW: the way i would likely install php5 is to extract the archive to x:\php5
and then add x:\php5 to my libpath (for the php5.dll)... then i would either
copy modphp5.dll to my apache2's modules directory OR i would use the
x:\php5\modules\modphp5.dll in my apache2.conf file... most likely i would start
with the latter instead of the former so as to maintain complete separation of
the two apps for update purposes... then the only file that would need to be
placed outside of x:\php5 would be the php.ini file which has to go in %etc
TTBOMK...

NOTE: the above FWIW is based on my years ago install of
php 4.3.10 (cli) (built Dec 18 2004 13:54:52)
[according to php --version]...

[Al Savage]

Steven said:
>>Find attached my first pass at an attempt to add to the
>>README.OS2> for php for OS/2. Make any additions/corrections
>>you feel necessary.
>
> Looks OK. I recommend you wrap the lines at 72 columns or so.

I generally do not wrap text, and let the client's viewer do the
formatting. The exception is webmail, where I do try to stay under 70
chars on replies.

Waldo said:
> * Extract /php.dll to a dir on LIBPATH . If using with
> Apache, you can generally put it where httpd.dll resides
> (/Apache2, etc.)
>
> this line seems to be in error as there is no php.dll but there is a
> php5.dll...

Good catch, fixed.

> * Extract modphp5.map to ???
> * Extract php5.map to ???
>
> my understanding from discussions on the weasel, ftpser and/or
> this apache2 lists is the following
>
> modphp5.map would go in the same directory as modphp5.dll
> php5.map would go in the same directory as php5.exe
>
> however, there is a problem with the php5.map file because
> there are two php5.exe files... one for normal command line
> usage and one for cgi usage...
> there does not appear to be any indication of which exe this
> map file is for...
>
> perhaps the build script needs to be modified a bit to place
> the map files in the same directory as the dll or exe they go
> with... it is possible that there are really two php5.map
> files generated but the second one overwrites the first
> because they are output to the same directory...

Good points. As Paul hasn't weighed in on this, I may email him
directly.

[Al Savage]

>> Dan Napier <d...@cihcsp.com> wrote:
>>
>> And I would be glad to help, If I understand

http://mantis.smedley.id.au/view.php?id=573

Any further suggestions should go there.