Rob,
Thanks for the sugestion. Doesn't work in our case though...
Willem van Asperen
Program Director
We zijn verhuisd:
MasterNet Communications bv
Rendementsweg 20-B3
Postbus 171, 3640 AD, Mijdrecht
Tel. 0297 230340 Fax 0297 230341
http://www.masternet.nl/ <http://www.masternet.nl/>
Trend Micro - Your Internet VirusWall !!
-----Original Message-----
From: British Consulate Jerusalem [mailto:[EMAIL PROTECTED]]
Sent: maandag 24 januari 2000 13:55
To: [EMAIL PROTECTED]
Subject: Re: [analog-help] analog 4.01 Win32 crash generating report on
large logfile
Willem,
I had a similar problem with Win98 after upgrading to Analog 4.0. Analog
crashed every time just as it was about to write the output file. I
eventually resolved it by putting FILELOWMEM 1 in the analog.cfg file. Since
then I have had no crashes.
I hope this helps.
Rob Elliott
Jerusalem
*************************************
Travel Advice for Israel and the Occupied Territories is
available on the web sites of the British Consulate-General
Jerusalem ( www.britishconsulate.org <http://www.britishconsulate.org> ),
the British Embassy
Tel Aviv ( www.britemb.org.il <http://www.britemb.org.il> ) and the Foreign
& Commonwealth
Office London ( www.fco.gov.uk <http://www.fco.gov.uk> ).
*************************************
----- Original Message -----
From: Willem van Asperen < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> >
To: < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
Sent: 24 January 2000 13:54
Subject: [analog-help] analog 4.01 Win32 crash generating report on large
logfile
> Hello List,
>
> I just downloaded analog 4.01 and tried it on a logfile in Microsoft
> Extended Logformat, 11,597 bytes in size. I turned debugging on and this
> tells me that inputting the file works fine. Then it records "Opening
> <filename> as output file" (<filename> being the report file) and crashes
> with a access violation.
>
> There is an output file generated and it is 0 byte in size.
>
> Yes - we have write permission for the file
> Yes - there is enough disk space
> Yes - it recognizes the correct log format
> Yes - this is the case when no language has been set in the .cfg file
> Yes - it crashes too when a language file is set
> Yes - this is a log file of only one day
> Yes - same thing happens using wildcards and reading multiple files (all
> about the same size)
>
> Trying it with smaller log files it works fine.
>
> I tried in on a P II, 120 Mhz with 64Mb RAM, running Windows 98 and on a P
> II, 400 MHz with 256 Mb RAM, running Windows NT Workstation 4.0.
>
> Same thing happens on both machines. Anybody has a record on this? Anybody
> for a sollution?
>
> Thanks a lot for taking the time to read this -- even more thanks for any
> clues.
>
> Willem van Asperen
>
> ------------------------------------------------------------------------
> This is the analog-help mailing list. To unsubscribe from this
> mailing list, send mail to [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
> List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
<http://www.mail-archive.com/analog-help@lists.isite.net/>
> ------------------------------------------------------------------------
>
>
------------------------------------------------------------------------
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/analog-help@lists.isite.net/
------------------------------------------------------------------------
