As neither Steven nor anyone else seemed to have an answer to my problem
(appearing below), I delved deeper. After splitting up the log files into
several files all below 5 Meg and running analog on different combinations
of them, I realised it wasn't anything in the logfiles that was causing the
crash. So I turned on the debugging and found that the crash was at the
point where analog opened the output file. That and the fact that the
windows crash message also referred to a stack dump led me to think that it
was some sort of memory problem. Sure enough, FILELOWMEM 1 cured the problem
and we are now back on track. Perhaps I should have looked at the section in
the manual on low memory a bit sooner!.
Rob Elliott
Jerusalem
[EMAIL PROTECTED]
http://www.britishconsulate.org
****************************
Travel Advice for Israel and the Occupied Territories is
available on the web sites of the British Consulate-General
Jerusalem (www.britishconsulate.org), the British Embassy
Tel Aviv (www.britemb.org.il) and the Foreign & Commonwealth
Office London (www.fco.gov.uk).
****************************
----- Original Message -----
From: British Consulate Jerusalem <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: 25 November 1999 09:34
Subject: [analog-help] Analog 4.0 Crashes
> A curious problem. Analog 3.32 (on Win98) has been running fine but I
> decided to upgrade to 4.0. The program crashes after analysing the two log
> files (one of 11 Mb, one of 19Mb) and gives the following message
>
> This program has performed an illegal operation:
> ANALOG caused an invalid page fault in
> module ANALOG.EXE at 023f:0041a0d0.
>
> But it only does this when analysing *both* log files in the same
operation.
> If I analyse the first one on its own there is no problem, and the same
with
> the second one.
>
> The entries in the analog.cfg file that I think are relevant are as
follows:
>
> ############################
> # Following commands needed to read the two formats contained
> # in our log files. Do not remove.
> LOGFORMAT COMMON
> LOGFORMAT COMBINED
>
> # log files below named access_log1, access_log2 etc are older log files
> # the log file without a number is the current log file
>
> LOGFILE britan.palnet.com_access_log1
> LOGFILE britan.palnet.com_access_log
>
> ############################
>
> The cfg file was the same as I used on version 3.32 only modified to
reflect
> new file locations.
>
> I tried reinstalling but the problem persists. I'd be grateful for any
> suggestions.
>
>
> Rob Elliott
> Jerusalem
> [EMAIL PROTECTED]
> http://www.britishconsulate.org
>
> ------------------------------------------------------------------------
> 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]/
------------------------------------------------------------------------
