Glenn,
You have the idea, but it's not yet in the ballpark.
On Sun, 08 Apr 2001 18:36:39 -0400, Glenn McCorkle wrote:
>> What we both forgot/overlooked is that core.exe underwent a MAJOR change
>> in the area of built-in DGIs between 1.66 & 1.70 ... Core.exe from 1.66
>> simply cannot function under the conditions where 1.70 can. It can't
>> find certain things and simply locks up.
> Yes, some changes were made.
> However, both 1.66 and 1.70;r3 still handle .mes files in the same manner.
Not necessarily. Both call upon InSight to read the message; the
problem occurs *before* that point. The problem is that Arachne cannot
find the *.mes file and "forward" it on to InSight for processing.
> ---from mime.cfg v1.66 ---
> file/*.mes >HTM|[130]$einsight.exe -i $1 -cache=$t>$2
> __________________________
> ---from mime.cfg v1.70;r3 ---
> file/*.mes >HTM|[130]$einsight.exe -i $1 -cache=$t>$2
> __________________________
> Now that I look at the line...... It just dawned on me what the problem
> might be.
> Try this... remove the [130] from that line and try it again.
I didn't think it would make a difference, since I never get this far.
<G> For that line to have any effect Arachne must have found the file
12345678.mes ... it doesn't. So changing minimum memory requirements
[which I met anyway] didn't change the software's response.
> I have a sneaking suspicion that this is the problem.
I wish it were that easy... :<
l.d.
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
