Subject: From: Date:

Re: ECST v4 status? David Mccoll Fri, 29 Jan 1999 16:21:07 -0800

---

Wayne,
I have tried the latest ECST 4.0 updates, but they did not help the problems
that I mentioned earlier. The HD is still being accessed when running from a
ramdisk and the cursor bleeds through the screen saver rendering the screen
save useless. Version 3.3 is stable and does not suffer from these problems.
I have no idea about 3.4 as I skipped it. I want to upgrade as there are
some new features in 4.0 that I could use but I can't have these bugs that
come with it.

I wonder about the Win version and if it also suffers from the hard-coded
references to C:.  I ran it a couple of times and found copies of some ECS
files in the Windows and Win\System directories ! They shouldn't be there.

So if ECST has hard coded references to the C:drive, then running Win ECS
4.0 off of a ramdrive is a waste of resources.

How can I impress upon Mark the speed advantages of running all of ECS off
of a Ramdisk. Everything runs so much faster and smoother with whole program
and SF loaded on it.

DAvid M.

-----Original Message-----
From: Wayne Wittenberg <waynew@magicnet.net>
To: herronf@us.ibm.com <herronf@us.ibm.com>
Cc: dmccoll@intergate.bc.ca <dmccoll@intergate.bc.ca>
Date: Sunday, January 24, 1999 7:48 AM
Subject: ECST v4 status?


>Have either of you had any luck resolving your problems with ECST v4?  I am
>about to give up on v4 due to Marks attitude and the quality of the
product.
>
>I reported to Mark one way that I had found to induce the lseek error that
>had been a constant problem.  I told him that I didn't think this was the
>only way the lseek error would appear, as I don't use F9 on message screen
>very often.
>His reply:
>>I don't have time to find the real problem,
>>but i "fixed" it via a brute force approach
>>(re-reading/processing the log file after F9).

---