Scans in 4.0

[dbusch]

Howdy, folks! Haven't posted in quite a while.
I have just now installed 4.0, and tried it on a few old programs. It does not run the scans in those programs. The DCC scanning module is installed, and the scans are not unmarked. It runs everything else in the programs.
I am still using 3.5 MR2, because there have been problems with subsequent versions. Is this a 4.0 problem, or am I overlooking something? Is 4.0 not meant to run old programs? Of course, I've only glanced at 4.0 so far, so I could easily be missing something Thanks for any guidance.

Doug

[Matthew D. Hoedeman]

Go to WILCOX and download V4.1, other than that, I don't know what to tell you other than there have always been problems of one sort or another with migrating programs from one version to another, no matter which direction you go (up or down). This is the reason I have 5 different, usable versions installed on my PC, I run programs in the 'native' version in which they were written.

[JamesMannes]

You may have to save the program as a 4.0 program and answer"yes" to updating your probe to the current version in order for some stuff to work. I don't know if that is your problem but it is a possibility.

Also, if you can load 4.0 I am assuming that you can load 4.1? If so, do it, I ran 4.0 for about 20 minutes before I uninstalled it and waited for 4.1. 4.0 is not a useable software in my opinion.

[kpayne]

I too tried 4.0 on our offline version and found a lot of issues and was afraid to load it on the online version.

I loaded 4.1 about a month ago and everything seems to be OK.

Kevin

[dbusch]

Same thing with 4.1. Since it's just testing the waters, i save a copy of the program and open it with 4.1. I then create a new probe file, same config as the old one. When running, scans are skipped over, but move points, etc. run okay. If I run a program with no scans, it runs to the end but the software locks up. The execution window stays on the screen-can't be cancelled. It tells me "executebarstate.dat" can't be found. I have to close pcdmis. I guess it's back to 3.5.

[JamesMannes]

I'll say it once more, have you saved these programs as a 4.0/4.1 program? You will know for sure if you go to the "save as" menu, and look at the pull down menu immediately below the "save as type" pull down menu. If you have saved the program "up" to 4.0/4.1 and you still have a problem with scans, then delete your executebarstate.dat file from your screen name folder, see if that does anything(PC-DMIS will create a new one for you).

[dbusch]

Company lost internet for about a day - man, that sucks!

Anyway - yes, the program was saved as 4.0, and I had renamed the file to executebarstate.old. No luck. However, after creating a NEW scan in a program, that scan will run. I would hate to think that new PCDMIS versions are designed mainly for the first-time buyers of systems, and not necessarily for folks with programs that were written with 3.2 or 3.5... I'm still waiting to hear from the help desk, however, so I shouldn't whine just yet.

I'm certainly not going to re-write the scans in our hundreds of old programs. I don't think my bosses would want me to spend time doing something like that! I get paid by the hour, though, so it would be okay with me.

Even if saving the programs as 4.0 was a fix, it still seems like a sloppy way of doing things. Anybody else experiencing this?

[Matthew D. Hoedeman]

Company lost internet for about a day - man, that sucks!

Anyway - yes, the program was saved as 4.0, and I had renamed the file to executebarstate.old. No luck. However, after creating a NEW scan in a program, that scan will run. I would hate to think that new PCDMIS versions are designed mainly for the first-time buyers of systems, and not necessarily for folks with programs that were written with 3.2 or 3.5... I'm still waiting to hear from the help desk, however, so I shouldn't whine just yet.

I'm certainly not going to re-write the scans in our hundreds of old programs. I don't think my bosses would want me to spend time doing something like that! I get paid by the hour, though, so it would be okay with me.

Even if saving the programs as 4.0 was a fix, it still seems like a sloppy way of doing things. Anybody else experiencing this?

As long as I can remember, there have been issues with migrating programs, either UP or DOWN versions. Why is anybody's guess, it has just always been there.

Here is something to try, in a program with a scan, simply put the cursor on the scan, hit F9 and bring up the 'spec' window for the scan. Then, simply click OK and see if it will then run. The way they 'add' things to different features, this may fix the problem by updating the scan feature with all the 'new' functionality of the scan.

[hammer]

when we updated to 4.1 I had the same problem with executebarstate.dat and we found that some of the file settings had to be chaned by IT to allow for writing to them not read only

[dbusch]

hammer, are you saying that you had a scanning problem with 4.1 because of that file?

[dbusch]

By the way MDH (Matt), re-clicking the button doesn't work. I'm still waiting to hear from BS - they seem to be very busy there at the help desk these days.

Also, MDH - I live in Lansing and work in Chelsea (helluva drive!) - can I inquire as to which company you work at? We were just acquired a few weeks ago by Orchid Orthopedic Solutions. Just curious...

[dbusch]

Heard back from BS. He replicated the problem. Online, that is - with offline it ran the scans in the virtual sense (shouldn't online and offline be more similar?) He is reporting the problem to Wilcox, although they must certainly have known about it before now. Is anyone using 4.0 or 4.1 to run scan programs created with 3.5? Successfully??