|
PureBytes Links
Trading Reference Links
|
Hi,
I saw a few posts about Elwave 5.0 last week. I bought the new Target
Clusters, and downloaded 5.0. I can't get the Target Clusters to "enable"
with the new License Key (It's ironic that these protection schemes inhibit
paying customers, but someone who obtains a cracked copy can use it without
inconvenience). The program seems to work fine, otherwise. Has anyone else
had problems making it work? I sent two messages to Prognosis, but they
haven't been able to help me.
Thanks,
Dan
w4tq@xxxxxxxxxx
-----Original Message-----
From: A.J. Maas <anthmaas@xxxxxx>
To: info@xxxxxxxxxxxx <info@xxxxxxxxxxxx>
Cc: Jan van Diessen <diessen@xxxxxxxxxxxxxx>; derksenf
<derksenf@xxxxxxxxxxxxxx>; Jan Diederik Haas de <jddehaas@xxxxxxx>; KLPD,
Jan <klpdmozo@xxxxxx>; LuudMaas2 <nlcou936@xxxxxxxxxxxxxxxx>; Onno Goedknegt
<goedkneg@xxxxxx>; Rene Dennesen <dennesen@xxxxxxxxxxxxxx>; rijt, wil v.d.
<wil.rijt@xxxxxx>; Metastock-List <metastock@xxxxxxxxxxxxx>; Arnoldi, Mike
<marnoldi@xxxxxxxxxxxxx>; Campbell, Kevin <Kevin243@xxxxxxx>
Date: Friday, February 05, 1999 4:32 PM
Subject: Re: I downloaded Elwave 5.0 [Fwd: Re: I downloaded Elwave 5.0]
From: "A.J. Maas" <anthmaas@xxxxxx>
>Thank you very much, Arjan.
>This is very informative info, and "no", I did not know about all of this.
>
>I have made a brieve summing-up of things to be considered:
>1.-Upgrading always pays off in the end, so an upgrade to ELWAVE v 5.x
> should always be considered by all questioneers. This will then enable
them
> to get rid of all of the F*DOP files present in any Metastock Data
Files-folder.
> The only thing left to do then, is to make New Scenarios, deleting the
older.
> This can be bad news to those users, relying strongly on their old
Scenario's, eg
> as they will have to do a re-build. (Not very handy).
>2.-Non upgrading to v5.x users, should strongly be aware, that not
upgrading to this
> MSFL651.dll file supporting version of ELWAVE and then also not making
up any
> New Scenarios supporting this latest MSDownloader 6.51 Data File
format, can
> always expect to receive errors at any time, eg sometimes when on
Opening
> (Importing) any of the currently excisting -but now old- Scenarios.
>3.-My version of the MSFL651.dll library file is the correct " 6, 5, 1, 3 "
and it is by
> Equis as manufacturer standard dated as Dec.15, 1998.
> 4.-I miss a brief explanation as to why other users requests for support
will not get
> answered by Prognosis, whilst, from my honoust opinion, the answers are
very well
> printed and explained in your excellent mail reply to my request.
> Is Prognosis too busy developing the next generation -again for the
better- version(s)?
>5.-I also miss out on the regular update mails, eg also users' questions
and reply mails,
> on how they experience working with and solve any arisen problems
working with
> and in the ELWAVE program. Hope that the email-support-list for all
users worldwide
> is still being considered by Prognosis.
>
>I hope you will forget my above in no.4(in the last line) -sort of-
sinical note, but also hope
>you will realise how much important this very well back(ed)-up support is
to your users
>worldwide, and as such that you will also consider to reply to
heir -sometimes very-
>urgent calls in the future, as much as you have also done so in this -very
well- mail to me.
>Again, Arjan, thank you very much for taking out your time, and if I can be
of any assistance
>to you on this matter(s) in any way in the future, do not hesitate to ask.
>
>Best Regards,
>Ton Maas
>ms-irb@xxxxxx
>
>
>
>----- Original Message -----
>From: Arjan van Gog <info@xxxxxxxxxxxx>
>To: A.J. Maas <anthmaas@xxxxxx>
>Cc: Jan van Diessen <diessen@xxxxxxxxxxxxxx>; derksenf
<derksenf@xxxxxxxxxxxxxx>; Jan Diederik Haas de
><jddehaas@xxxxxxx>; KLPD, Jan <klpdmozo@xxxxxx>; LuudMaas2
<nlcou936@xxxxxxxxxxxxxxxx>; Onno Goedknegt
><goedkneg@xxxxxx>; Rene Dennesen <dennesen@xxxxxxxxxxxxxx>; rijt, wil v.d.
<wil.rijt@xxxxxx>
>Sent: vrijdag 5 februari 1999 11:25
>Subject: Re: [Fwd: Re: I downloaded Elwave 5.0] From: "A.J. Maas"
<anthmaas@xxxxxx>
>
>
>>Dear Mr. Maas,
>>
>>Here's some general information on how ELWAVE works with MetaStock files
>>that may be helpful, although you probably already know most of it. You
>>are free to pass on this information to others if you think it will be
>>of any help to them.
>>
>>The first versions of ELWAVE supported only MetaStock 3.51 format and
>>required the presence of a MASTER file and one .DAT/.DOP combo for each
>>entry in the MASTER file. The .DOP file specifies which columns
>>(date,time,open,high,low,close,volume,oi) are present in the .DAT file.
>>
>>MetaStock itself was limited to 32766 records per datafile, but the 16
>>bit record count actually allows for 65534 records if you use it as an
>>unsigned integer. We decided to interpret the record count as unsigned,
>>which means that old MetaStock versions can only read .DAT files created
>>by ELWAVE that have less than 32766 records.
>>
>>Later versions of ELWAVE no longer needed the .DOP files to be present,
>>because the same information is present in the MASTER file. However, if
>>the .DOP file that corresponds to the .DAT file is present, the
>>information in the .DOP file is used by ELWAVE instead of the specs in
>>the MASTER file. If for some reason the .DOP is incorrect (and we know
>>from experience it sometimes is), ELWAVE cannot read the .DAT file. If
>>you try to read such a file, you will get 'out of order date' or similar
>>errors because ELWAVE is trying to interpret something as a date while
>>it is actually a time,open or high etc. Another problem was caused by
>>some versions of MetaStock, which would write "IO" instead of "OI" in
>>the .DOP file for open interest. This was fixed by having ELWAVE
>>recognize both as meaning open interest.
>>
>>In the latest version of ELWAVE we have added support for MetaStock 6.51
>>files. We have also kept the 3.51 import code in place for compatibility
>>reasons. As it turns out, the msfl651.dll that was shipped to us is
>>already outdated, causing an error code #007 while installing ELWAVE.
>>This error simply means that a file is being copied to your computer
>>that is older than the file already there. The newer file on your system
>>will NOT be overwritten by the ELWAVE Setup Wizard, so you can safely
>>ignore this warning. Obviously the error message should have been more
>>specific.
>>
>>I have included a reply we received from Equis on this matter:
>>
>>> The MSFL 6.51 is the latest version. MetaStock 6.52 uses the
>>> MSFL 6.51.
>>> The latest release of the MSFL 6.51 is 24 November 1998. You
>>> can verify you have the latest version by looking at the date of the
>>> files on the setup disk or by checking the version of the DLL using
>>> the Windows Explorer. The DLL version should be 6, 5, 1, 3.
>>>
>>> You are right, the MSFL does write to the master files. However, the
>>> files should remain backward compatible as long as the following rules
>>> are followed.
>>>
>>> 1. There must always be 255 or less securities per folder.
>>> 2. There can be no intraday securities in the folder.
>>> 3. The price records for every security must not exceed
>> 32,766.
>>> 4. The price data must not contain dates outside the 1900's.
>>>
>>> If the rules are followed, the data should remain compatible.
>>> However, since the MetaStock 3.0 format does not support dates
>>> outside the 1900's, it would be wise to have your customers upgrade
>>> all their software to support the newest MetaStock format.
>>
>>One thing to note is that the MetaStock library actually writes to the
>>MASTER file if you open a directory, even if you don't actually write
>>any data. This may cause problems if you have an old ELWAVE scenario
>>file that references a 3.51 format MetaStock file. If this happens, you
>>should create a new scenario and use the MetaStock 6.51 import to read
>>the data.
>>
>>We have requested the latest version of the MSFL651.DLL from Equis. When
>>we receive this we will see if there is a need to release an updated
>>version of ELWAVE to solve any problems you and other customers are
>>experiencing.
>>
>>I hope that with this information you will better be able to find the
>>cause of and solve any problems you may have when reading MetaStock
>>files using ELWAVE. If we can be of further assistance, please let us
>>know.
>>
>>Kind regards,
>>Arjan van Gog
>>
>>--
>>Prognosis Software Development
>>Phone: +31.15.2123543 Fax: +31.15.2132558
>>email: info@xxxxxxxxxxxx
>>World Wide Web: http://www.prognosis.nl
>
>
|