|
PureBytes Links
Trading Reference Links
|
I am running 32megs on one machine, 64 on another. 6.52 will crash if I am
running only MetaStock. On my office machine I am running NAQ's RealTime
Trader. I will add that I never had a crash with ver 5.11. My machines
are for trading and I do not keep non-trading programs open during the day.
The crashes come when attempting to cycle thru securities with the arrow
buttons and when accessing a chart from the small window on the lower right
side of the screen. Believe me, Equis knows of this problem, they simlpy
will not address it, just like the printing problems.
I might add that I never had a printing problem until I responded to a post
discussing printing problems. Now I have them regularly. Hope your
response does not bring you crashes.
Al Taglavore
----------
> From: Jeff Haferman <haferman@xxxxxxxxxxxxx>
> To: metastock@xxxxxxxxxxxxx
> Subject: Re: 6.52 (and 7.01 EOD!!!) crashes very often on Windows 2000
> Date: Thursday, April 06, 2000 11:41 AM
>
>
> I'm running 6.52 on Windows '98, and haven't *ever* had Metastock crash.
> I've had this configuration for a year.
>
> For those of you who are crashing, how much RAM do you have, and
> how many other applications do you have open?
>
>
> >
> >Friends,
> >I thought that it was my old computer (& WIN95) that was causing the
crash
> >problems.
> >Perhaps we should go back to our old DOS versions of MS, until Equis can
remove
> >the bugs.....?
> >Larry
> >
> >
> >
> >At 05:15 PM 04/05/2000 -0400, you wrote:
> >>Lynn,
> >>
> >>I have completely removed 6.52 & register keys. Did a fresh
> >>installation of 7.01 EOD on Windows 2000. I only use local
> >>hard disk data. Unfortunately, Metastock still crashes.
> >>
> >>6.52 crashes very often, about once every 20 securities.
> >>MS 7.01 is slightly better, about one crash every 50-100
> >>securities. It crashes when I scroll through securities
> >>using the arrow buttons at the lower right-hand corner.
> >>I've used Windows 2000 since Beta 3 (April, 1999).
> >>MS 6.5 is so stable, I don't even recall any crash.
> >>The problem starts with MS 6.52. And now it seems
> >>MS 7.01 still has the same problem.
> >>Any suggestion is appreciated.
> >>
> >>Thank you very much.
> >>R. I.
> >
|