Rank: Advanced Member
Groups: Registered, Registered Users Joined: 3/19/2005(UTC) Posts: 2,995
Was thanked: 14 time(s) in 10 post(s)
|
Starting with v7.0 the version number is stored as a folder under this key. What exactly are all of the possible version numbers between 7.0 and 9.1?
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 11/28/2005(UTC) Posts: 276 Location: Salt Lake City, UT
|
I'd imagine it would be all the versions that have been available:
7.0, 7.2, 7.3, 8.0, 9.0, 9.1.
I am not sure how minor upgrades such as 7.02, 7.03, etc fit in.
They may show up just like that or they may have used the 7.0, etc.
Have to check with someone that has one of those versions installed.
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 3/19/2005(UTC) Posts: 2,995
Was thanked: 14 time(s) in 10 post(s)
|
Thanks Branden! That's what I was looking for, though you do raise a good question about the minor versions. Surely, they are listed under big brother...
Anybody care to confirm??
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users, Subscribers Joined: 3/7/2005(UTC) Posts: 1,346
|
hey g.... not sure whats on your mind with that, but checking mine both 9 and 9.1 are in the same folder with my hexi-decimal password to reuters being different for each....h
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 3/19/2005(UTC) Posts: 2,995
Was thanked: 14 time(s) in 10 post(s)
|
HKEY_CURRENT_USER\\Software\\Equis\\Common is the root path to the MS executable files. If different versions are installed into differenct paths, they will be recorded here.
e.g.,
HKEY_CURRENT_USER\\Software\\Equis\\Common\\9.1\\File Paths\\ {ProgramPath}
HKEY_CURRENT_USER\\Software\\Equis\\Common\\8.0\\File Paths\\ {ProgramPath}
I'm trying to find the path to the MS executable files regardless of the version installed.
|
|
|
|
Rank: Member
Groups: Registered, Registered Users Joined: 4/27/2005(UTC) Posts: 13 Location: Salt Lake City, UT
|
To my knowledge, file paths in the registry will always be listed under a specific version number. There isn't a global value across versions.
Is there a reason you require a static value sans versioning?
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 3/19/2005(UTC) Posts: 2,995
Was thanked: 14 time(s) in 10 post(s)
|
Hey KC-
I'm not looking for a static value... I know the file name. I'm just trying to find out where the file is located for each version of MS that is installed. In order to do that, I am looping through the registry, using HKEY_CURRENT_USER\\Software\\Equis\\Common as a root. If key exist in 9.1 directory, get location; if exist in 8.0 directory, get location; etc. It's a super easy routine, but I'm just trying to hard code all of the potential places to look rather than search blindly for all occurrences... just to make my rountine as fast as possible. Hence, needing to know what possible registry values might exist.
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 11/28/2005(UTC) Posts: 276 Location: Salt Lake City, UT
|
g_stockman wrote:Hey KC-
I'm not looking for a static value... I know the file name. I'm just trying to find out where the file is located for each version of MS that is installed. In order to do that, I am looping through the registry, using HKEY_CURRENT_USER\\Software\\Equis\\Common as a root. If key exist in 9.1 directory, get location; if exist in 8.0 directory, get location; etc. It's a super easy routine, but I'm just trying to hard code all of the potential places to look rather than search blindly for all occurrences... just to make my rountine as fast as possible. Hence, needing to know what possible registry values might exist.
I am not sure if it is possible with registry keys, but you might want to look at a way of getting the Common key and see what folders are under it (giving you the version).
That way you aren't hard coding values that may (will) change when a new version is released.
Another problem is that if the user has more than one version installed, there will be more than one version key listed in there.
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 3/19/2005(UTC) Posts: 2,995
Was thanked: 14 time(s) in 10 post(s)
|
Quote:Another problem is that if the user has more than one version installed, there will be more than one version key listed in there.
I'm being unclear... sorry. :oops
i.e., what I am wanting to do is be able to determine how many MS installations are on the computer and determine what version they are. I can do this already... I'm just trying to speed up the process.
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 11/28/2005(UTC) Posts: 276 Location: Salt Lake City, UT
|
g_stockman wrote:Quote:Another problem is that if the user has more than one version installed, there will be more than one version key listed in there.
I'm being unclear... sorry. :oops
i.e., what I am wanting to do is be able to determine how many MS installations are on the computer and determine what version they are. I can do this already... I'm just trying to speed up the process.
I didn't mean so much a problem as something to keep in mind.
Sounds like you were intending to though.
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 3/19/2005(UTC) Posts: 2,995
Was thanked: 14 time(s) in 10 post(s)
|
This is a small routine to return the path of all the MS versions installed on a computer. I'm using it as part of a larger project. I've tested it on a couple of computers and it works OK on them, but I especially need people with multiple MS versions installed to test it for accuracy. Will someone be brave enough to volunteer? LOL!
It should run fine on any computer, except for Win98... I think.
Thanks!
<update>
<dysfunctional beta attachment removed>
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users, Subscribers Joined: 9/8/2004(UTC) Posts: 2,266
Was thanked: 1 time(s) in 1 post(s)
|
Psst .... It did not recognize that version 7.22 was installed ... :P
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 3/19/2005(UTC) Posts: 2,995
Was thanked: 14 time(s) in 10 post(s)
|
Thanks. That answers the earlier question regarding minor updates. I'm going to have to know all of the minor updats or just blindly go searching for anything in the root key. I'm thinking that might not be the best way... but, revision coming.
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 3/19/2005(UTC) Posts: 2,995
Was thanked: 14 time(s) in 10 post(s)
|
Did it report anything at all on the 7.2 line?
Are you saying that 7.2 and 7.22 could be installed in different directories?
Questions... questions... this was supposed to be a given.
<addendum>
I've got this one nailed. I'll repost it tomorrow sometime. Then I re-challenge you... :P
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users, Subscribers Joined: 9/8/2004(UTC) Posts: 2,266
Was thanked: 1 time(s) in 1 post(s)
|
g_stockman wrote:Did it report anything at all on the 7.2 line?
Nope :(
g_stockman wrote:Are you saying that 7.2 and 7.22 could be installed in different directories?
Nope
g_stockman wrote:
<addendum>
I've got this one nailed. I'll repost it tomorrow sometime. Then I re-challenge you... :P
Bring it :D
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 3/19/2005(UTC) Posts: 2,995
Was thanked: 14 time(s) in 10 post(s)
|
Ok... run this one through the grinder for a while. See if it breaks.
Requires .NET framework and Win2000 or better.
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users, Subscribers Joined: 9/8/2004(UTC) Posts: 2,266
Was thanked: 1 time(s) in 1 post(s)
|
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 6/6/2005(UTC) Posts: 424 Location: connecticut,USA
|
Hey G. what the Equis utilities file is about and for what version?
PS: Key for version 9.0 as Hayseed mention is diffrent from 9.1
also for futher refrence can I load(instal) just a 9.1 version without setup 9.0?
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users Joined: 3/19/2005(UTC) Posts: 2,995
Was thanked: 14 time(s) in 10 post(s)
|
The purpose of this [so far] sole utility is to identify the location of all MetaStock installations on the local computer... whatever they are. It should work with any version of MS starting with 7.0. Maybe before that, I'm not sure. The data provider doesn't matter.
It doesn't really DO anything... it is just a routine that I'm working with as part of a larger project. I wanted to test it out on different computers and setups so I posted it here.
I am especially interested in the way it will function on computers with:
1. Multiple MS installations
2. Networked installations
3. Older versions of MS (prior to 7.0)
Please... everone test it out and let me know.
Thanks.
|
|
|
|
Users browsing this topic |
Guest (Hidden)
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.