Upgrading PCDMIS - Safe way?

[Underspec]

Ok, I am getting a SMA renewal as mentioned. They say they will send me the latest version. Now, I don't want to install it and have things go screwing. I know some of you have done this in the past so here is my question.

What is the safest way to install the new version and still keep the old version? Just install into a different directory? What other precautions should I take?


Thanks all.

[Matthew D. Hoedeman]

1) COPY the current Pcdmis directory, give it a name to match the version (ie PCDV37MR3)
2) Install the new version into that directory.

[William Johnson]

Running 2 versions pcdmis

1. You will need to also copy over your comp.dat file to your new directory.
2. Also if you have a sharpe 32 controller you will need to copy over the downl.oad file.
3. Ver 3.7mr3 will not let you run an older version of pcdmis without some extra work on your part. If you have ver 3.5mr2 and ver3.7mr3 on the same computer 3.7 changes your set search path to the directory that you have designated. The problem comes into play when you open an older version of pcdmis. When you open lets say 3.5mr2 the set search paths are set to the ones 3.7mr3 had. This will corrupt your probe files and your program when you try to run a program in a older version. You will get some kind of error about end of program. So when you switch between versions you will need to change the set search paths every time. Another work around is this.
Set up 3.7mr3 the way you want it and then shut it down. Goto the registry and find where the paths are saved. export that branch "3.7mr3paths.reg"
Now run the old version, double click on the reg file that you assigned for that version and the paths will be restored for the session. Do this for each version that you have. I do have and run both versions and this works really well for me. I just update the registry for the version that I'm going to run before I open it.

[JamesMannes]

I would suggest vigorously to not load 4.0. Wait until at least PC-DMIS 4.1(new naming convention starting with 4.0). Too many bugs in 4.0 for my taste and I've always been a masochist when it comes to the new versions, but not anymore.

[Matthew D. Hoedeman]

WJ:

1&2) If you have the Sharpe32 controller, those files should be in the install directory of Pcdmis, making a copy of the entire directory copies those files as well, both DOWNL.OAD and COMP.DAT.

3) With the advent of the registration setup of Pcdmis, ALL versions since V3.5 no MR will use the same path names. Another way around it is to make probe files for the new version that match the probe files for the old version and only use the new version probes in the new version (names like 4x20V35 and 4x20V37). This eliminates the need to do the registry thingie. Unless you have some huge probe changer rack, this method is no big deal. Just remember, if you get a PROBE warning to update to the new version, TELL IT NO, then use the 'new' version of that probe build up. I am currently running both V3.5 no MR and V3.7 MR3 and have not lost a program yet.

[Underspec]

Wow, I didn't realize there are so many problems with upgrading and replacing upgrades. I am running 3.7 MR1 at this moment. I probably won't upgrade at this time then.

[JamesMannes]

Upgrade to 3.7MR3 it is a very good mr.

[William Johnson]

Matt I have 30 probe files and I would take me a long time to re build all of them with all of the angles that I need in them. We have over 50 different customers and a large variation in types of product. The update of the registry was the easiest for me to do. As far as the files go I always install new versions into their own directory, without copying over from the old to the new. Back when 3.5 came out I copied over like you said and I had troubles with my probe files. (maybe a 3.5 thing) After that I have been gun shy.
After I install the new version into its own directory, I just copy over all the files that I need and this has helped me keep my sanity. Do you remember when 3.5 came out and it did not look at you comp.dat file, and we had to go into the settings editor and turn it on.

[William Johnson]

Underspec I would go to ver 3.7mr3 as it is the most stable.

[BOB PARSONS]

SAFE UPGRADES

THERE IS A MUCH EASIER WAY TO RUN AN OLD VERSION PROGRAM
AFTER YOU RUN IT ON YOUR LATEST UPRGADE! VERSION 3.7 OR
HIGHER ALLOWS YOU TO SAVE A PROGRAM "BACK" TO AN OLDER REVISION
SUCH AS 3.5 OR 3.2. IF YOU DON'T DO THIS OR THE MUCH MORE COMPLICATED
REG. THING MENTIONED ABOVE YOU WILL GET A SERIALIZATION ERROR.
SIMPLY DO A "SAVE AS" AND AT THE VERY BOTTOM OF THE MENU SELECT
THE VERSION ( I.E. 3.2 ) YOU WANT TO SAVE IT AS. SO LONG AS THE SAVED OR LAST RUN VERSION IS THE SAME OR OLDER THEN THE VERSION YOR ARE TRYING TO EXECUTE, PC-DMIS WILL RUN AS NORMAL.

[Underspec]

I have 3.7MR1 right now, if I upgrade to 3.7MR3 but use a different directory. Will MR1 still work since they are both V3.7?

[Matthew D. Hoedeman]

YEP.

[Underspec]

Seems they don't work because MR3 is a new version supposedly so I cannot open MR3programs. Luckily I backup my programs and just copied over the old ones back.

[Matthew D. Hoedeman]

SORRY, I mis-understood your question. Both versions will work, but once a program is opened AND saved (closed) in a newer version, it will only work in that version OR a newer one. You can, however, save the back to the older version.

[BOB PARSONS]

UPGRADE SAFELY

UNDERSPEC SEE MY POST ABOVE #10. IT EXPLAINS ( I HOPE ) HOW YOU CAN
RUN YOUR PROGRAM IN MR1 AFTER YOU RUN AND SAVE IT IN MR3. ITS SIMPLE
AFTER YOU DO IT ONCE OR TWICE.