Glenn,
Me again.
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.
Now, I have access to the core.exe from intervening versions, but I
don't know at what point the change was made ...
I do know that CORE.EXE from 1.68 can't find the inbox DGI, because I
just tried it. I never installed 1.69 because so many people reportes
so many problems with it ... I don't exactly feel like "installing" it
just to get to core.exe to try the experiment.
Now, just which files exactly did you think might be causing problems in
the arachne main directory? I don't have, AFAIK, *any* APMs installed
with this version. So what does that leave?
If you can think of files that Arachne can run without, I'll try moving
them out of the main directory and see what happens. I'm even willing
to change MIME.CFG to what you might suggest ... but I can tell you mine
is "cleaner" than your version because I don't have a lot of things
enabled.
I'm willing to work on this, but ...
l.d.
====
On Fri, 06 Apr 2001 19:16:25 -0500, Glenn McCorkle wrote:
> OK, try this.
> In your Arachne_main_dir (v1.70;r3)...
> ren core.exe core.exb
> then copy-over to that dir the core.exe from v1.66
> Now try 1.66 but in the dir where 1.70;r3 used to be.
> If it still does not work, the problem is with one or more of the fikles
> in the v1.70;r3 directory. (not with v1.70;r3 itself)
> If we can track-down the exact cause of this, maybe we have a chance of
> fixing it.
