|
PureBytes Links
Trading Reference Links
|
Yngvi:
I noticed that, too. Version 7 doesn't allow >60min and <Daily charts
anymore. That was an important feature that should be returned immediately.
The problem with upgrading the indicators seems to be related to those that
call variables (FmlVar) or entire custom indicators (Fml). Below is a
description and workaround from Bill Forman, Equis's customer support
manager:
> "The two [identified upgrade problem] circumstances are:
>
> 1) You have FMLVar() calls in formulas and they are calling formulas below
> the formula they exist in. This will cause a crash. Any formulas called
> in the list above the formula with Fmlvar() will not have a problem.
>
> 2) You have formulas that have more than 1000 characters AND leading
> spaces in the formula. This will cause corruption of the specific
> formula.
>
> The work around is:
>
> Using 6.5x, export all formulas that do NOT contain FMLvar() calls to a
> new folder. Import them into 7.0 and upgrade the formula file by open
> 7.0. Export the formulas containing FMLvar() calls from 6.5x and then
> import them into 7.0 and the file will successfully upgrade.
>
> If you have leading spaces in your formulas, they need to be removed
> before the upgrade.
>
> The fixed CD will handle both of these instances by doing two loops
> through the formula file and upgrading all formulas that DO NOT have
> Fmlvar()calls and removing the leading spaces. It will then go back
> through the file and upgrade the formulas with Fmlvar() calls. In this
> way, the formulas needed by the Fmlvar() calls will already be upgraded.
>
> So, you may want to wait for the new CD or you can use this convoluted
> workaround. I don't know how long it will take to get the new CD."
Like you, I also had some layouts irreparably damaged, but I restored these
from backup and they worked. These layouts contained Fml functions, so I
just assume it was all part of the same problem.
I also experienced for several days the instability you mentioned. On
loading a layout, indicators would not update quickly and then the system
would hang. The problems seem to have corrected (self-healing software?)
and things seem stable again. Perhaps it was all related.
Unlike you, I also had problems reading my intraday data files after the
upgrade and I discovered that the master and emaster files had been deleted
during the upgrade. I restored these with Norton Utilities and it worked.
I won't get into the problems I had, and my gripes with, DataOnDemand, but
I've set that aside for now as an interesting but largely useless (for me)
feature. With some enhancements that could be a very powerful tool.
The good news is that Tech Support jumped all over these problems and was
genuinely interested in solving them. They have good people there.
Good luck.
----- Original Message -----
From: Yngvi Hardarson <hardy@xxxxxxxxxxxxx>
To: Metastock list <metastock@xxxxxxxxxxxxx>
Cc: Equis Support <support@xxxxxxxxx>
Sent: October 27, 1999 01:22
Subject: Realtime Intraday Interval and MS 7.0 problems
> All!
>
> Does anybody know how to create realtime MetaStock securities for a
> higher
> interval than 60 minutes? I am interested in 3 hours (180 mins), 4 hours
> (240 mins) and 12 hours (720 mins) as well as a daily (1440 mins) update
> where I can have long history with todays bar active.
>
> Also- It seems some people have been having trouble with their 7.0 pro
> upgrade (including myself). My problems have centered on getting the
> custom
> indicators translated. I have managed to do some via piecemal imports from
> 6.52 having that version installed on a second computer. However not all
> indicators come across. Furthermore those of my SmartCharts and Layouts
> that
> employ custom indicators have become screwed up and there are hundreds of
> them. It seems MS is replacing some of my indicators with other ones. Any
> solutions out there?
>
> Also it seems MS 7.0 is unstable especially when the Organizer and custom
> indicators are involved.
>
> I am running MS on a Windows 98 Pentium II/266 MHz with 128 Mb internal
> memory.
>
> Thanks,
> Yngvi Hardarson
> hardy@xxxxxxxxxxxxx
|