Bernie,
*YOUR* argument just PROVES my point.
The file never gets to InSight in the first place. I thought I'd made
the clear time and time again. The file I can't get Arachne to open is
not the cached file; if it were, the URL for the cached file would be on
the URL line of the error message. It is *NOT* !! Didn't you bother to
look at the screen shot I put up for download?
When I say that Arachne cannot find
t:\arachne\mail\members.hip\12345678.mes
that is what I mean.
And it appears I've found the 'switch' that turns this bug off & on; I'm
waiting for verification from Glenn to see if he can duplicate it now.
l.d.
====
On Fri, 13 Apr 2001 11:30:41 +0200, Bernie <[EMAIL PROTECTED]> wrote:
> L.D wrote:
>> If the problem were with InSight ... big word *IF* ... it should not
>> matter which version of core.exe were used to run Arachne.
> (snip)
>> Make sense?
> Not really, since this is what happens:
> 1. You tell core.exe to open t:\arachne\mail\whate.ver\12345678.mes
> 2. core.exe looks for file/.mes in mime.cfg
> 3. core.exe "launches" (not really since it's adding it to a BATch file)
> insight.exe with all the things needed. <- Risk for error here if the line
> gets too long.
> 4. insght.exe opens the file t:\arachne\mail\whate.ver\12345678.mes and
> processes it. Output is redirected to a file in the cache. <- Problem with
> InSight would result in error here
> 5. Control "returns" to core.exe which opens the cached file for display <-
> This is the file you can't get Arachne to open.
> There are four places where this can go wrong. Point 4 could also go wrong
> if you have no space left but I assume you've already checked that. Point 2
> could also go wrong, but it probably don't in this case since you would get
> another screen in that case.
> Could you do like this:
> 1. Clear cache
> 2. Open one of those mails (do this with a version that doesn't work of
> course).
> 3. Exit Arachne
> 4. Was the file created in the cache?
> And are you sure that *all* paths are the same between the two versions of
> Arachne that you use? The only diffrence I can think of is if Arachne
> suddenly had a lower limit for that string than it used to, but I find it
> unlikely.
> You could also try this mail directory, just move a message to it (in DOS
> of course):
> t:\mail.let\
> And see if that helps it, if so the length of the string was reduced. And
> apart from making the length larger for the next version the sollution is
> to use shorter paths (this is essentially a DOS limitation not an Arachne
> problem).
> //Bernie
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
