hsdio vi broken

[Kyle_A.]

• Can you give me screenshots of the errors you are seeing? 
• You say it works with LV 8.6, but not the other two, has this always been the case or did this just begin with the installation of 1.7.5?
• What was the previous version of NI-HSDIO you were working with?  Did it work with 8.6, 2009, and 2010 just fine?
• When you installed/uninstalled, were there any errors? I find it suspicious you found other versions of the dll in other places.
• What other places housed the .dll file it was looking for?  There could have been a bad install/uninstall that left the file in a different location, and now it won't install into the proper location.
• Does it still say missing .dll's?  After the repair, did the missing .dll's reappear in their proper location?
• Do the .dll files appear elsewhere on the machine?  If you copied/pasted to their appropriate locations do you get different results?
• OPTIONAL FOR NOW: After all of these steps, can you attempt to uninstall the HSDIO driver, and download 1.7.5 off the internet onto your local machine, and then install that package to eliminate any probability it is the media causing the issue?
• Are there any other drivers on the machine that exhibit the same issue?

This is a pretty extensive list, but it would be helpful to spend some time looking through them all first and providing what you can, as it will help diagnose the issue effectively.  The alternate route is to start fresh on the machine, but due to your large amount of software I would see that as undesirable.  Let me know what you come up with, thank you for the information and patience.

[Jeff_Giacone]

Ok,

I'll try to do things you suggest after I get home.

if I were to manually link to the dll, should I link to the HSDIO.dll in the RT Images folder?

When I do this I get the "The application failed to start becasue ETSAPI.dll was not found" error

What is the ETSAPI.dll used for, why is labview looking for it.

Is something in the registry that I should be looking at.

The ETSAPI.dll shows up in the LMU for the HSDIO section of the registry on my machine at home.

[Jeff_Giacone]

The error I get is shown in "error 1.bmp" attachment

the library path  is niHSDIO**.* for the call library function

HSdio does not work in any version of labview now

I only looked at labview version 8.6 after 2010 and 2011 stopped working.

I'm not sure when 2011 hsdio stopped working. I thought it worked just after i installed 2011, but then stopped woring at some point, not sure what was upded or changed inbween it working and not.

I got no errors when I installed labview 2011 or reinstalling 1.7.5

I'm not sure where hsdio should be installed..in only 1 location or multiple? Let me know where it should be located. PS I did delete it from the RT images/hsdio folder and after I reinstalled it through the repair process, it re appeared.

the only location is "C:\Program Files\National Instruments\RT Images\NI-HSDIO\niHSDIO.dll"

no other problems tat I have found

here's the current registry dump for CMRU

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Search Assistant\ACMru\5603]
"000"="hsdio.dll"
"001"="auto*.exe"
"003"=""
"004"="niSync.dll"
"005"="tools*.*"
"006"="nidevmon.exe"
"007"="loa.exe"
"008"="niHSDIO*.dll"
"009"="niHSDIO**.*"
"010"="nihsdio.dll"
"011"="njhsdio.dll"
"012"="*.lvproj"
"013"="A0*.sys"
"014"="*.sys"
"015"="*.*"

dump from 5604

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Search Assistant\ACMru\5604]
"000"="*hsdio*"
"001"="nihsdio*"
"002"="emblabview.exe"
"003"="google"
"004"="NiFpgaDmaReadResholder.vhd"
"005"="http://rexnavarette.com/search.php"
"006"="http://vcstore.com/search.php"
"007"="ing"
"008"="ee500"
"009"="mediswebsite"
"010"="administrator"
"011"="Spyware Doctor"
"012"="ing direct"
"013"="in direct"

I'll let you know what happen after I try the optional for now approach

[Kyle_A.]

Do you happen to have a spare machine at your home that you can attempt a clean installation with just LabVIEW 2011 and HSDIO 1.7.5 on it?  Doesn't matter the Win OS used, just something to verify that you either get a similar result or a successful installation.  If not, we can look at your registry, because it does sound like there is some deep corruption.  Let me know if you have a spare computer.

[Jeff_Giacone]

No I don't have a spare computer at home.

It does matter what O/S is used Labview 2011 and all of it's components don't install correctly on a windows XP64 machine according to tech support..

I think I have some deep curruption as you suggest.

The question is how do I fix it what itmes in the registry should I take a look at?

Does HSdio use the ESTAPI.dll? this is the error when I try to link to the DLL manually.

There is no such ESTAPI.dll installed on my computer that I can find...I tried doing a file search and a registry search...and the only trace that I can find of this DLL was in the MRU

I deleted at item from the list and no luck...even after I tried to fix and reinstall the HSdio.dll

[Kyle_A.]

Yes, only a few of our drivers at NI support WinXP 64-bit, but the vast majority do not, I apologize for the misleading comment, I meant any supported WinOS should be fine for testing.

Just so you know it is actually ETSAPI.dll and not ESTAPI.dll, so if you search for the first naming convention I would imagine something would pop up on your machine.  ETS is related to the Real Time OS, which I'm very unsure why that dll is being called in the first place.

Will doing a clean wipe of NI software on your system and building it back up be an acceptable step for you?  It will take a very long time to search through your registry and clean that up manually, so based on the time that would take it would be quicker to start fresh and see if that eliminates the issue. 

[Jeff_Giacone]

I am not opposed to uninstalling all version of NI software. I am unsure how to clean out the registry, but I am not opposed to doing that if it will solve my problem. I have never cleaned the registry manually...how do I do that?

[Kyle_A.]

I had one of our Applications Engineers send you a message with the removal instructions.  I wanted to check and see if you were able to perform that procedure.  Let me know if you need any further assistance.

[Jeff_Giacone]

Kyle,

I did mot receive a message on how to clean my computer, but i think i found reference on how to do it on another post here on the forum.

I still have issues. It does not look like the niHSdio.dll is being installed correctly. I see it on my c drive , but it is not listed in the registery. I'll see abot posting a little more information from my home computer later thsi evening

[Jonathan_S1]

You should have received those instructions now.

Thanks,

Jon S