tradtional nidaq 6.9.3 problems

[vandenberg greg]

 I keep getting this error message when I run MAX (version 2.2):

"Unable to open a connection to the server. The configuration file, config.mxs, or the entire installation may be corrupted."

I tried fixing the registry settings like the document  "Config.mxs Error when Opening MAX under Windows" suggests but no success.

I tried reinstalling traditional nidaq 6.9.3 but no success, also, now my visual C++ application now won't run but gets the error window popup:

"The application failed to start becuase NIPALU.dll was not found"

Can anybody help me?

[Matthew_W]

 hi vandenberg greg,

 This sounds like the NI-PAL software has gotten corrupted, I would try the following steps:

  1. Install NI-VISA v4.2
    This will re-install the latest version of NI-PAL to your system.
    After completing the NI-VISA installation, attempt to run MAX.
 
  2. The next thing to try all of the steps in this KnowledgeBase article. Please note that this KB asks you step sequentially through the steps.


 Please post back here if this does not fix your problem and include the following information:
   1. Any error numbers that may be generated.
   2. Has this application worked in the past?
   3. What changed?
   4. What operating system are you using?
   5. What DAQ hardware are yo uusing?

  Have a great morning,

  MatthewW
  Applications Engineer
  National Instruments



 

   


    


Message Edited by Matthew W on 11-20-2007 10:23 AM

[vandenberg greg]

Installing NI-VISA worked! Thanks! Now the problem is I'm adding a DAQPad-1200 using the Add Hardware Wizard, and appears to install, but then at the last step, "Completing the Add Hardward Wizard" a message pops up: "This device cannot start (code 10)", and when I run my application, it doesn't see the DAQdpad.

How can I fix this?

[Matthew_W]

 hi vandenberg greg,

 This sounds like maybe interrupts are disabled for the parallel ports. Here's a knowledgebase article that covers how to fix this.

  If that does not work then take a look at this forum posting for other tips.

  If still experiencing issues, then reply back with what operating system you are using and any error codes generated.

 Thanks!

 MatthewW
 Applications Engineer
 National Instruments





Message Edited by Matthew W on 11-21-2007 01:14 PM

[vandenberg greg]

The parallel ports were enabled.

I looked at the forum posting you suggested and installed the ni-cdu1610.exe patch. Still no luck.

I installed the patch ni-cdu1121.exe as described in the knowledge -base article "Why do my National Instruments PCI Devices Receive Error Code 10 in the Windows Device Manager?", but no luck

When I check the Device Manager I see a yellow exclamation point over the DAQPad-1200 icon, and then when I right right-click to get Properties I in the Device status window I get the message:

   "This device cannot start. (Code 10)"

  "Click Troubleshoot to start the troubleshooter for this device"

If I click on Troubleshoot I get a window that advises me to remove then reinstall the device. This doesn't work either.

If I click on Next it advises me to reinstall the driver. Are there any other drivers or is there anything else I need to do?

Thanks

[vandenberg greg]

Also, I forgot, this is on a Sony Vaio laptop running Windows-XP.

[Speedy_Badger]

Hello vandenberg greg,

"This device cannot start (code 10)" is a Windows error which usually describes a conflict between devices for a given resource. You mentioned there being a yellow exclamation point next to the DAQpad-1200 in device manager. Is it possible that there are already LPT devices installed on your Sony laptop that access the same port? An example device would be a printer.

If you have any other device drivers installed which use parallel ports for communication I would try disabling them or changing the port number. There are several "ghost" parallel ports that you can choose from to assign your other devices to. This will free up your primary parallel port for access by the DAQpad-1200.

If the above suggestion does not improve the situation, I would suggest re-installing the NI-DAQ drivers once more. If 6.9.3 continues to be problematic, try rolling back your driver to NI-DAQ 6.9.2.

Regards,