Robolab corrupts LabVIEW installation.

[pdo_75]

I am running LabVIEW 6.1 and Robolab 2.5.2 on a PC running Windows XP. Each time I run the Robolab application, it appears to corrupt the LabVIEW installation. In particular, LabVIEW crashed when I tried to insert ActiveX objects into an ActiveX container. I searched the knowledge base and found a solution (document 2IHGJAB5) involving repairing the labView installation. This is impractical to do each time Robolab is run. Is there an alternate solution?

[BrandonS]

I have verified the same situation on a Windows 2000 system. Unfortunately I am not aware of any way to work around this problem. I know that Robolab is built on the same kernal as LabVIEW. I assume that this is where the problem lies. I will email the company that currently develops Robolab and make sure they are aware of this situation.

[uncleop]

Have you heard of any resolution to this? Pitsco LEGO/Dacta is still shipping RoboLab 2.5.2, which only appears to include LabView 6.0.3, which in turn is not a version recognized on this site's support forms. (They go from 6.0.2 to 6.1...)

Also note that my install on Win2K didn't allow a "repair", just a "remove". I'll go back to 2.5.1 for now; any idea what was "fixed" or added in 2.5.2?