hey jim.... installation of v10 is different , no doubt about that.... but prior versions are not completely dead, their still there and we still have the cd's..... we just need to figure out a simple way to return that does not involve equis tech support.... however , tech support is there ready and waiting.... and let's not overlook the possibility that the problem could have been on my end......

 kinda bet the number of customers returning  v10 will be almost nill.... and the number of users wanting to maintain older versions likely will be small.... i myself will no longer maintain separate versions once v10 esignal is available.....

failing drives and corrupted files shouldn't be a problem, other than the obvious.... the license is just a 15 digit number which can be reinput and we would still have the cd for drive failures....

 i might give pyradius's suggestions above ...... h

brief update.... while  reading roys newsletter last night i was overcome with jealously.... his meta versions don't conflict ... mine do.... or did.... but mine are realtime, his are eod, and there is a big difference in how the two work..... still his success was enough to get my mind workin on a solution that even a hayseed could use..... thanks roy....

and btw, a very big thanks to jennifer on equis  tech support for this pointer.... i previously uninstalled version 10 to reclaim my prior esignal version ....  last nite reading of roys success i tried to re-install  v10 again but no go....  kept gettin a 'temp msi' file error.... as it turns out uninstalling v10 does not uninstall the qc component.... we must use the add/remove new programs and  remove quotecenter , then reinstall the whole shootin match.....

after a full day of studyin high tech methods i'm embarassed to say a simple solution finally hit me.....  so here is where we stand as of now.... we can have both esignal pro 9 on and offline versions working with v10 for qc on and offline versions on the same computer on the same drive.......

everything works fine and more importantly switching back and forth is again easy... i did not try pyradius's suggestion swapping hkey_current_user>software  but i trust his judgement there.... will post the details later, its 4pm, the market is closed and the deer stand is callin.......h

 

hayseed:

will post the details later, its 4pm, the market is closed and the deer stand is callin.......h

A man's gotta have his priorities straight to live a happy life.

Good for you.

---

When you see that in order to produce, you need to obtain permission from men who produce nothing - when you see that money is flowing to those who deal, not in goods, but in favors - when you see that men get richer by graft and by pull than by work, and your laws don't protect you against them, but protect them against you - when you see corruption being rewarded and honesty becoming a self-sacrifice - you may know that your society is doomed. - Ayn Rand

Hi Hayseed

 

I’ve had no problems with several versions all installed at the same time in their own folders. The only time I’ve gotten into trouble in the past was when I uninstalled one version. For that reason I don’t even contemplate uninstalling now – I just install and use the new version as and when I want to, and leave older versions is place for when I want to use them.

 

The one issue that does annoy me a little is that smart charts are not backward compatible. This means that once I’ve opened a security in MS 10 I can’t open the same file in MS 9.1 until the smart chart has deleted. MS 10 is quite happy to accept an earlier version smart chart but not the other way around. Nothing new with that this time around.

 

Roy

MetaStock Tips & Tools

Hi Hayseed

 

You’re right about me only reporting on what happens with EOD versions. I have no idea of the difficulties that might crop up with multiple real-time versions installed.

 

Roy

MetaStock Tips & Tools

hey roy.... my experience with the prior versions is the same as yours.... my hike around the smart chart issue has been just to keep seperate metastock data folders which of course keeps the smart charts seperate....

v10 realtime version installs quite differently than the eod version.... its very likely pyradius's suggestion might work best as we don't have complete control over what gets installed where... and after install we can't just move componets to suit our needs without causing other problems...

my  method , which is by no means perfect, does work but has issues itself.... i have discovered at least one c++ runtine error that completely shuts down v10 .....

but of course all this just a interesting passtime till v10 for esignal is released... 

money is different in different parts of the world but for my money v10 is a real steal.... i would have gladly paid patrick far more than 200 bucks to write the new features in for me......

a better way to appreciate the price would be to advertise for bids...  such as, any programers out there want to submit bids to code in number 11 on the 2nd page wish list....

Ability to sort custom indicators into different folders. For example, the list displayed in the indicator builder would have different levels... a tree view; regardless of where the actual indicator is stored....

i'll glady pay 200 for that also....heck, i might even go to 225..... and speaking of well worth the price, always enjoy your msst news letter....thanks.....h

there is a compatibility patch out for v10.... of course most will know this, but some might not, might be a good idea to use the organizer and export everything prior to the new install.... also make a copy of your charts folder, C:\Program Files\equis\MetaStock\Charts , that holds your layouts, templates and such....

if for some reason you get the error of a missing msi file like i did, remember jennifers suggestion posted above....

 the rmo deal has a training video, you might have better luck with broadband..... h

i'll reinstall v10 to make sure the problem is not on my end..... can't seem to find any documention reguarding the inability to use  a filter for column k and/or column l, but it appears to void the exploration when used with other columns being filtered also..... all securities are rejected....

however, when only colk or coll is filtered,  meta shuts down.....  can somebody verify they can filter column k and/or coll with no problems..... either the v10 pro or eod versions.....  you don't have to fill all columns, you can just put rsi(14) in  k and put colk in the filter section ....

  and again, the problem could be on my end.....h

 

 

hayseed:

i'll reinstall v10 to make sure the problem is not on my end..... can't seem to find any documention reguarding the inability to use  a filter for column k and/or column l, but it appears to void the exploration when used with other columns being filtered also..... all securities are rejected....

however, when only colk or coll is filtered,  meta shuts down.....  can somebody verify they can filter column k and/or coll with no problems..... either the v10 pro or eod versions.....  you don't have to fill all columns, you can just put rsi(14) in  k and put colk in the filter section ....

  and again, the problem could be on my end.....h

hayseed -

I have v10 EOD (build date Sep 28 2006).  I ran an exploration with RSI(14) in colk.  I filtered for colk>70.0 and loaded the SP500.  The exploration completed normally (no crash) but all 500 securities were rejected.  Under the "Rejects" tab of the report it indicated the following for all 500 stocks: "Results of formula not defined on calculation date".

  

hey net.... thanks.... was kinda hoping it was trouble only on my end but apparently not.... when its convienent, could you run the exploration again but this time just put in colk  in the filter section ..... that might immeadiately shut down meta but no harm will be done..... so obviously  don't do it during market hours if your trading.....

this is something we might have forward to pyradius ......

apppears we can still use both columns k and l, however they must stand alone, ie no filter of any kind referencing to them.... h

OK, hayseed.  Tried it again with just colk in the filter.  System self-destructed.  I want my money back! 

Has anyone heard anything from Equis on this problem, or is it a feature?

hey vaughn.... sorry,  my error , thought i had posted ..... pyradius looked into it that very day and said he would write  up a memo for the r&d dept.... he had no idea of a time frame on a fix....

until then,  filters referencing to k and l should not be used, as they void the exploration.... and expect meta to shut down if a filter is used in only column k or l.... those columns can still be used in normal non filtered situations.....

a guess, and just a guess, would be bugs that shut down meta might be handled at a fast as reasonably possible pace.....h

 

Not a problem, I was just wondering. It is a small thing anyway, but it will be good to see how they deal with it.

Cheers

vaughn:

Not a problem, I was just wondering. It is a small thing anyway, but it will be good to see how they deal with it.

Cheers

On the contrary, I see this as a major problem with one of the few new features in their latest s/w upgrade cycle.  This type of problem should have been captured during the normal course of regression tests by the Equis developers.

They have already quickly addressed a problem (or problems) with v10 and various plug-ins.  Let's hope they are just as quick with issuing a patch for this problem.  We should not have to be forced to create "work-arounds" to utilize this new expanded functionality.

I agree, it will be good to see how they deal with it.  

Oops, that came out wrong. I meant that the loss of ability to filter 3 out of 12 columns is not that big of deal, to me at least since I am still learning. The additional columns was the main reason I upgraded. The fact that something like that made it through internal testing, Beta & RC testing is definitely a problem.

I checked their updates and patchs page - the only thing there was for metastock 8.

vm

VM -- Where is that page?  I'd like to see if the Channels bug(s) have been fixed in 10.

---

--Johnathan

hey vaughn.... i understood and agree....   they might have beta testers, they once did.... i beta tested quotecenter for quite some time before official its release.... 

of course their business is their buisness, but it would seem wise to have beta testers...  and those testers should be  intense  meta users ,  all day every day, with real money on the line....

similar to ford and gm benefiting from  nascar drivers.....  if something is gonna break, that guy driving 200 mph will see it first......h

Hi,

It is better to wait then.

Asish

hayseed:

i'll reinstall v10 to make sure the problem is not on my end..... can't seem to find any documention reguarding the inability to use  a filter for column k and/or column l, but it appears to void the exploration when used with other columns being filtered also..... all securities are rejected....

however, when only colk or coll is filtered,  meta shuts down.....  can somebody verify they can filter column k and/or coll with no problems..... either the v10 pro or eod versions.....  you don't have to fill all columns, you can just put rsi(14) in  k and put colk in the filter section ....

Happy New Year hayseed!

Was wondering about the status of the version 10.0 column k/l filter problem with Equis.  Do you think they will address this in the new year or will we have to wait for v11?  JMHO, but I think this problem warrants a software patch.     

hey net...... happy new years..... nope, haven't heard anything..... pyradius had written it up for us and likely issuses, such as this,  that shut down meta will be on the front burner of r & d's agenda.....

meta has taken a back seat with me, lately been spendin most of my time in the forex market ..... a slightly faster way to loose money  but the autotrading ea aspect of it is none the less appealing.....h

Hi all,

I did write this up as a bug.  I am hoping this should be resolved in 10.1 but at this time I cannot say for certain what will be in this release or the release date.  Crash issues are definitely a top priority when it comes to what will be fixed in a maintenance update.

As a side note, unless you are trying to reject securities by referencing 11-12 columns in the Filter tab, you should not experience this issue.  You can still use column K and column L for reporting values in the Report.

hayseed:

meta has taken a back seat with me, lately been spendin most of my time in the forex market ..... a slightly faster way to loose money  but the autotrading ea aspect of it is none the less appealing.....h

I prefer to lose my money the old fashioned way.  Call me a dinosaur.

Pyradius:

I did write this up as a bug.  I am hoping this should be resolved in 10.1 but at this time I cannot say for certain what will be in this release or the release date.  Crash issues are definitely a top priority when it comes to what will be fixed in a maintenance update.

As a side note, unless you are trying to reject securities by referencing 11-12 columns in the Filter tab, you should not experience this issue.  You can still use column K and column L for reporting values in the Report.

Pyradius (and hayseed) -

Thanks for the update on the filter problem.

As I have said before, the extension of the filter fields is one of the few improvements added to MS in V10.0.  We shouldn't have to rely on a work-around (i.e. not referencing certain columns) just to assure that the system does not crash.  I do hope that they fix this sooner rather than later.

they say  patience is a virtue ....... for all of us patiently awaiting  v10 for esignal , our day in the sun  has come.... appears mine is in the mail..... 

thank you   equis  guys and gals......h