Clarence,
Do you use a pure 1.70 installation? Or are you still back at < 1.70?
Used to be almost all the DGIs for internal tasks were batch files or
separate; in the latest version the majority of the DGIs have been
included as part of the CORE.EXE code. How? I have *no* idea...
And *IF* it were a matter of the files supposed to be in the
./system/dgi directory and not being there, then 1.70r3 wouldn't be able
to do any of the stuff ... and the problem is only with the readmail.dgi
and only when it involves a 8+3 subdirectory in the ./mail directory [at
least that's the only problem I've found.
l.d.
====
On Wed, 11 Apr 2001 18:03:25 -0500, Clarence Verge wrote:
> L.D. Best wrote:
>> I haven't done, and don't have time to do, a file by file comparison
>> between 1.66 and 1.70r3 ... I *do* know that simply inserting core.exe
>> v 1.66 into the 1.70r3 installation results in Arachne being unable to
>> find:
>> inbox.dgi
>> outbox.dgi
>> sentmail.dgi
>> readmail.dgi
>> trashfolder.dgi
>> emptytrash.dgi
>> That would seem, to me, to be a clear indication that CORE.EXE in
>> v1.70r3 handles DGI files for mail in a different manner than 1.66
>> The likely source of the problem I have might be the "readmail.dgi"
>> module in the 1.70r3 core.exe.
> Hi LD;
> *I* know that YOU know that .DGIs are pretty much just one line .BAT files
> found in mime.cfg.
> If A1.66 core can't find those .DGIs then maybe they aren't there.
> Try copying your 1.66 mime.cfg over to your 1.70 install temporarily.
> If it fixes the mail problem, your 1.70 mime.cfg must be trashed.
> If it doesn't, then the paths in A.cfg may be trashed.
> - Clarence Verge
> --
> - Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
> - The internet is infected - Windows is a VIRUS !!
> --
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
