iviConfigurationstore.xsd missing

[LuI]

Hi,

I am a little desparate now.
I was a beta tester for LV7. When the final release came up I uninstalled my complete set of NI SW and installed the whole package new from my DevSuite TestEdn. This started three weeks ago and still I am having trouble with MAX an other components.

At the moment MAX can not 'deserialize' the viConfigurationStore.xml, because the XML schema file iviConfigurationstore.xsd is not found. It should reside in :\Programs\IVI\Data\iviConfigurationstore.xsd . The same problem is reported by the NIDMM driver front panel.
I have tried to repair my NI-DMM driver with no luck. I have searched for that file locally, on my CD set and on NIs homepage - with no luck either.
Can anyone of you send this file
to me?

In case it is important:
* The whole set of HW did operate with the beta SW, so there should be no HW problem.
* My system: W2k German, SP2 on PII/450 with 448MB of RAM
* Develloper Suite Test Edition as of May 2003, which is
- MAX 3.0.0.3014
- LV 7.0 PDS
- NI-DAQ 7.0.0f8
- NI-DMM 2.1.1
- IVI Engine 2.0.0
- IVI driver Toolset 1.5
- IVI Configuration server 1.3.1.0

Any help is apreciated!

[gagi1]

Installation or uninstallation of either the IVI Compliance package or the niDmm driver does not remove this file from your system. Most probably you have manually deleted the IVI folder from Program Files while you were trying to clean up your system from the beta components. That is the reason why the .xsd file did not get reinstalled when you tried to repair your niDmm driver.

Here are the steps you should try to do to fix the problem:

1. Download and run the IVI Cleanup Utility from the IVI Foundation website.
2. Download and install the IVI Shared Component installer from the IVI Foundation website.

The link is: http://www.ivifoundation.org/ApprovedSpecs/Default.htm (see the bottom of the page).

I hope this helps!

Vesna Jadric
Instrument Dri
vers/IVI

[LuI]

Vesna was right with this answer, allthough not complete. I had to repair the instruments drivers (in my case NI-DMM) to get it operating. Anyhow - I would not have been able to fix this alone - so thanx!