Hi Aengus
Thanks for that - but I'm afraid I'm still not getting very far!
I have all the necessary files (analog.exe, analog.cfg and lang/uk.lng) in
the cgi-bin directory of my web site. Everyone has FULL CONTROL on this
directory and execute is enabled on this directory.
I still get the following error:
Warning F: Failed to open configuration file
=E:\Inetpub\wwwroot\Paradisii\cgi-bin\analog.cfg:
It is trying to open the correct file as the path is correct - but for some
reason I am getting this error still
Any further suggestions would be much appreciated!
Regards
Paul Gower
Paradisii Limited
Tel: (01273) 470006
Fax: (01273) 470007
Mobile (0973) 172650
[EMAIL PROTECTED]
http://www.paradisii.co.uk
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Aengus Lawlor
Sent: 11 January 2000 19:22
To: [EMAIL PROTECTED]
Subject: Re: [analog-help] Running Analog on NT
(By the way, did anyone make a 4.01 version of anlgform.exe?)
Paul Gower wrote:
>I am using it on an ASP based NT platform and am using ASPEXEC to call it.
>
>I always get back the following messages:
>
>e:\inetpub\wwwroot\paradisii\cgi-bin\analog.exe: Warning F: Failed to open
>configuration file analog.cfg: ignoring it (For help on all errors and
>warnings, see docs/errors.html)
>e:\inetpub\wwwroot\paradisii\cgi-bin\analog.exe: Warning F: Failed to open
>language file lang/uk.lng: ignoring it
>e:\inetpub\wwwroot\paradisii\cgi-bin\analog.exe: Fatal error: Can't read
>language file lang/uk.lng: exiting
I haven't tried to call Analog from ASPEXEC, but using the supported
perl web form, I found that when anlgform.pl calls Analog, all relative
paths are relative to the anlgform.pl directory, not the analog
directory. So analog looks in the script directory for ANALOG.CFG, and
for LANG\UK.LNG. Analog requires a Language file, so it will fail if it
doesn't find one.
You can either put the LANG folder in the scripts directory, or you can
add a LANGFILE entry to your CFG file - use a fully qualified path,
because a relative path will still be relative to the Script directory,
not the Analog directory. Eg:
LANGFILE "C:\Program Files\Analog 4.01\lang\uk.lng"
(Note the quotes are only necessary for paths with spaces).
But you also need to help Analog find this CFG file. Again, Analog will
look for it in the scripts directory first, so you either put analog.cfg
in the scripts directory, or you tell Analog where to find the CFG fle
by specifying it as a commandline parameter
Analog -G +g"C:\Program Files\Analog 4.01\analog.cfg"
>Do you have any idea what could be causing this? I have tried putting all
>the necessary files in the same directory (and several others as well!)
>but I cant seem to get it to read either .cfg file or the lang file
>
>Paul Gower
Aengus
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
