msgserve.dll

[Patrik_K]

I am working on reconstructing a few VI that got corrupted in an update, and I wondered if anyone have worked with either the old VIs named SussRegisterProberApp.vi and SussDoProberCmd.vi or the msgserve.dll library (and more specificly the DoProberCommand and RegisterProberApp in it).

As it is I am using the SussUnregisterProberApp.vi, that survived the upgrade, as an template for how the other VI should look. Unfortunatly I have not been able top find any information on the VI or the msgserve.dll library.

Any insight would be appriciated.

[Davidek]

Hi Patrik

Sorry to say I've never worked with any of the VIs or the dll and I don't have them on my machine either. If you can tell me which versions you were upgrading to/from I'll see what I can dig up. Would also be good to know if they are LabVIEW native and in that case if they are part of any specific library or toolkit? I did a quick google search and came up with a company called SUSS MicroTec that work with Wafers and MEMS testing. Could the VIs be drivers provided by them?

Best Regards

David

NISW

[Patrik_K]

Sorry for late reply, but I have been on vacation. Yes it is SUSS MicroTec that made the VI originally and it seem that only solution they had was buy the production package for the newer LabVIEW. Problem is of course that all I was interested in was 3 VIs, and the price for the full package makes those 3 VI expensive. Oh well, probably will have to buy the program package after all.

[Davidek]

Hi Patrik

Hope you had a nice vacation. Before you go and buy yourself new VIs there might be some things you can try, but that depends on the following:

1. Do you still have the original VIs?

2. Are the VIs locked?

3. What version of LabVIEW were the VIs for?

4. What version of LabVIEW are you upgrading to?

5. What error(s) are you seing after the upgrade?

Best Regards

David

[Patrik_K]

1. Yes, we do have the original VIs

2. Unfortunatly they are locked and can't open at all.

3. The VI was originally for LabVIEW 6.0.

4. I was trying to get things to work in LabVIEW 8.20.

5. Error message is:

LabVIEW: VI is not loadable.

In a built application, this error might occur because VI being loaded was last compiled for a different OS, in which case you must save the VI on current platform. This error also might occur if the VI is a polymorphic VI, which cannot be loaded in the LabVIEW Run-Time Engine. You must load an instance of the polymorphic VI instead of the polymorphic VI itself.

An error occurred loading VI 'SussDoProberCmd.vi'. LabVIEW load error code 11: VI version (6.0) cannot be converted to the current LabVIEW (8.2) because it has no block diagram.

The VI was originally used on an old Windows (NT) computer, from what information I gathered from those that worked here at the time.

Thanks for taking the time for this problem.

[Davidek]

Hi Patrik

Ok, that clarifies things, but I'm sorry to say that it's not going to help you. The error message you get indicates that the VIs were saved without the block diagram. That was possible in earlier versions of LabVIEW as a means of protecting sensative code. LV needs the blockdiagram to update the VI to a later version, so even though you normally should be able to open a 6.0 VI in 8.2 (Version Upgrade Table) you will not be able to do so with your VIs. They will only run on the version of LV they were created in. So it looks like your only option is to get the upgraded VIs from SUSS, sorry.

Best Regards

David

Message Edited by DavidEk on 07-28-2009 03:20 AM

[Davidek · Accepted solution]

or keep running LabVIEW 6.0 obviously...

[Patrik_K]

Thanks for the explanation of why the VI had missing blockdiagram. I did manage to find an old LabVIEW 6.0 and test  the VI. It seem it is possible to open them in an older LabVIEW. Probably will try to use that one to run things.

[Davidek]

Happy to help, hope it works out for you

/David