|
PureBytes Links
Trading Reference Links
|
> Install your 7.0x in a new directory, not over the old one. That way you
> can go back and use 6.52 until you're sure everything is OK.
That is not ever advisable.
1. What makes you think that you will be running your "old 6.52" ?
At most it will be a 6.52-skinned 7.02 version. A clone.
2. Installing to a separate folder will store there some of the new 7.02 files.
But system related files will not be stored there, they will be put in the
Windows|System folder, overwriting and thus replacing the old 6.52 files
+ possibly also adding additional new 7.02 files.
3. Windows Registry will now have 2 seperate entries, one for the old 6.52 and
one for the 7.02, where 7.02 will now most of the time overule any 6.52 settings.
Then a quick calculation made will imply that the 6.52 version has deceased.
Perhaps still present on disk, but as lame as a blind bat. Without the vital 7.02 files
it will not function. The cover might look as 6.52 but the base will be 7.02, with all
the possible consquences too(errors,malfunctioning), to follow or for a 6.52
program to function properly.
4. Later uninstalling the "perhaps" not needed 6.52, will unnessecary have
irrepairable consquences too, it will have files getting uninstalled + registry
entries being deleted. Files+entries that can still belong to the new 7.02
program.
5. To find out the other terrible consequences involved, f.e. when later upgrading
to new patches, let alone upgrades, see the Equis website on the previous
6.51 --> 6.52 and 6.52a patches. Two different versions of the same Patch
were at that time created and users that had installed to separate folders, were
advised to also use the special other instructions, other then the "plain" 6.5 users.
6. Then later on in program life, when upgrades to 7.03 or higher versions will be
installed, what then will be deleted when you uninstall 6.52 ?
7. Even not uninstalling, you're still stuck with 2 seperate programs, of which the
oldest will never be used and only takes up disk- & registry space and can also
only lead to confusion, and once unistalled........................see above.
Thus theoreticaly maybe an advice, but the BLOOPER of the year would be
a more appropiate description.
Therefore practicaly, not ever recommended !!.
Regards,
Ton Maas
ms-irb@xxxxxxxxxxxxxxxx
Dismiss the ".nospam" bit (including the dot) when replying.
Homepage http://home.planet.nl/~anthmaas
----- Original Message -----
From: "Chuck Engstrom" <engstrom@xxxxxxxxxxxxx>
To: <metastock@xxxxxxxxxxxxx>
Cc: <stocks@xxxxxxxxxx>
Sent: zaterdag 5 augustus 2000 3:26
Subject: Re: defect in V7.02
> At 03:44 PM 08/04/2000 -0500, you wrote:
> >I just installed V 7.02. Notwithstanding the assurances of the sales
> >department that almost all of the bugs in V7.01 had been fixed, I find that
> >it is indeed buggy.
> >
> >Non of my personally created indicators, systems , and wizards were
> >transferred by the "organizer". Most if not all of them are simple (no
> >convoluted mathematical operations). For example one indicator is as simple
> >as OBV, another is a price oscillator. The personal wizards had all been
> >posted to this listserver and worked quite well with V 6.52.
> >
> >It will be a tedious chore to copy them manually into V 7.02.
> >
> >1. is there a fix for this?
> >
> >2. should I return V 7.02 for refund until this problem is fixed?
> >
> >If something as simple as transferring and converting files is beyond the
> >scope of V7.02, how many more difficulties am I faced with. I have neither
> >the time nor the patience to spend much time or effort on this.
> >
> >Intuit and Microsoft seem to be able to manage file conversions. The
> >program should have been checked more thoroughly before shipping.
> >
> >
> >Lionel Issen
> >lissen@xxxxxxxxx
> >
> >
> Lionel, Claude, Paula, others upgrading --
>
> Ron Stockstill posted an excellent checklist for upgrading about two weeks
> ago. Unfortunately, I no longer have it, but perhaps he could post it
> again. I followed it pretty carefully and don't seem to have had the
> problems some have had with upgrading of formulas, etc.
>
> I would add these comments to his:
>
> When you check your formulas, explorations, etc, do so by both running them
> and by opening them with their respective EDIT functions. I found that some
> of my 6.52 items would in fact run -- or maybe I should say, appear to run
> -- even though they were not properly constructed. But if you open a
> defective formula, etc in EDIT and then click OK, you'll get some sort of
> warning about its defect. That's your chance to correct or delete it. If
> you click CANCEL after the warning, the defect will be retained.
>
> Install your 7.0x in a new directory, not over the old one. That way you
> can go back and use 6.52 until you're sure everything is OK. But be aware
> that opening a security in 7 makes it no longer usable in 6.5 -- so you
> might also want to make a duplicate set of 6.52 data files, which I failed
> to think of.
>
> I didn't let 7.0x convert my stuff en masse during installation. I just
> said no to its offer, and let the installation go to completion. Then I
> opened 6.52 and exported some formulas to an empty directory. Next, I
> closed 6.52, opened 7.02, and imported them. I've now done this several
> times, a few items at a time, and so far, so good, but I still have a lot
> of stuff not yet done. This is undeniably a lot slower than mass import
> during installation but on the other hand, a lot faster than retyping one
> by one. And it helps you to clean house since you'll want to import your
> best stuff first.
>
> Good luck!!
>
> Chuck Engstrom
>
|