How to make niconfig.daq active?

Question

I have a system using Win 95, Run Time Engine 5.1.1, Ni-Daq 6.1, and an executable application which worked previously until the customer uninstalled everything.  Everything has been re-installed and all error messages eliminated.  No particular order was used to re-install all the above software.  Niconfig.daq was configured after all the above was intalled at C:\Windows\niconfig.daq, for two AT-MIO-16E-2 boards.  Both the Configuration Utility and DAQ Channel Wizard where used to assign and configure the AO, AI's, and DIO's.  Save at the bottom of the Channel Wizard was clicked and all windows closed.  When the Configuration Utility is clicked on later and from the pull down "Run Channel Wizard" of the Configuration Utility the niconfig.daq as set up is still present.  When the application .exe is clicked, the main control panel of the application appears.  According to the operating procedures provided with the application the first thing to do is click the top button which is "Check Out".  This runs a pre-operational test of the application.  The pre-operational test/check out occurs and a number of items not associated with the MIO boards operate correctly, BUT one of the DIO's, an input, informs me the Amplifier has a switch in the Inhibit position.  It is not in the inhibit position, OK is clicked on this message, the checkout continues and we are informed a second time the switch is in the Inhibit position.  Finally, the Check Out completes informing us the test has failed.  None of these messages is a LabView error message, just part of the applications checkout.  I have inverted the DIO signal with the Channel Wizard, no change, it still does not recognize that the switch is in the enable position.  I have used both the Configuration Utility's "Test Panels" and the Channel Wizard's "Test" to check the AO, AI's, and DIO's all of which operate properly using both "Test Panel" and "Test".  I am assuming that the C:\Windows\niconfig.daq is somehow not being seen by the application.  How can I make the application see the niconfig.daq?  I have a great deal more information about what files and folders are present in C:Windows, C:\Program Files\National Instruments\Shared\Labview Run-Time\5.1, C:\Ni-Daq\Chanwiz, and finally the application itself C:\WQM8\bin (in which all of the files are clearly of National Instruments in origin).      

Answer 1

Yes, it is a built executable.  No, I don't have access to the source VI's.  I have a copy of Labview Development Suite 7.1, which may not really be helpful.  The executable worked for years until the customer played with it, and the customer has no tools to open the executable with, what they did was just play with the whole thing.  I am thinking that, yes, the config was in some file within the executable, which somehow got corrupted.  Or more likely the config was in a separate file external to the executable using a pathname that was called from within the executable.  Is this possible?  In other words, no matter which it is, we have to find someway to can opener the executable to either repair a corrupted config inside it, or discover the assigned pathname of the config?  If there is a way to open a built executable with Labview, I would certainly be willing to try it.
The app directory (C:\WQM8\bin) contains the following files:
1.  analyses autostart.exe (works)
2. autostart.exe (works)
3. autostart.ini (oddly empty, but not our problem child)
4. autostart_wqm8.exe (works)
5. daqdrv
6. iw_en.lrm
7. Lvdevice.dll
8. serpdrv
9. wqm8.exe (The Problem, the app executable)
10. wqm8.ini (contains: PostscriptLevel2=False, thats all there is in the .ini of our problem child)
11. wqm8_analysis.exe (works)
Could there have been a config.daq or some other config file in this directory that the app called and all we are missing is the pathname the wqm8.exe is looking for?  Or would the config have been internal to the .exe?  Is there any point in putting Labview 7.1 on here with Win 95 and trying to use the daqchutil.dll to force the config.daq on the app/executable?  Remember, this all worked for years, with basically what we've got here.  The things listed above which do work are useless without the wqm8.exe working.