[This is the third time I've written this. Time before hit some unknown
key combo and lost all my work; last time I hit CTRL-W to save to
textarea.txt and my system went to black screen freeze.]
People, please try to "listen" more carefully this time. It's
absolutely necessary if this mess is going to get fixed.
CORE.EXE had some *drastic* changes made in it for v1.70.r3 ... and
some of them had *nothing* to do with css. We lost the way that
TEXTAREA.TXT is written/saved; same goes for TEXTAREA.TMP. The way DGIs
are accessed were changed for some of the DGIs.
Bernie, I'll try to address your issues:
1. The problem is not with InSight. PERIOD.
2. There is no problem creating the index.
3. InSight doesn't *find* the mail; it *processes* the files which
CORE.EXE sends to it. If this were *not* the case, InSight wouldn't
be called into effect when you access messages from the desktop
"list all files" type directory. If this were *not* the case,
InSight wouldn't be able to handle files that aren't 'local' to the
mail installation.
If this were *not* the case, there would be no need to put
instructions in MIME.CFG as to how CORE.EXE will handle *.mes files!
4. I don't know what you mean by "fixed directory entries." However,
it is *NOT* a problem because of directory paths exceeding the
allowable length of a DOS string.
It is not the *length* of the path in DOS at all.
1.70 needs to follow \mail\members.hip\12345678.mes
1.66 needs to follow t:\arachne\mail\members.hip\12345678.mes
> Arachne (I assume we are talking about core.exe) never reads that file,
> InSight does. However when you read/write/send/fetch mail you do it in
> Arachne (core.exe).
Bernie, that is precisely what I've been trying to make clear to Glenn
and it hasn't been sinking in!!
If InSight were the culprit [which it isn't] then the same version of
InSight wouldn't work with core.exe 1.66 and *not* with core.exe 1.70
... and InSight [the same version, copied over from my 1.70 install] has
no problem reading the message in my 1.66 installation.
If it were a matter of running out of environment space, then the 1.66
installation should have the same problem. I would *guess* that I have
plenty of space for environment since even shelled out [to the
restricted 512] I have 220 still available and everything is still in
envrionment where it belongs.
The problem lies within CORE.EXE ...
Those who want to take a look at the index produced by InSight can
download http://www.b-for.org/downloads/index.zbm
The error message, showing the correct file path, is downloadable at
http://www.b-for.org/downloads/errormsg.zbm
l.d.
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
