Previous replies here that solved the "dll initialization routine failed" problem for others aren't working for me.

Question

Hello everyone,
I place the DLL, LVLIB and all the VI files from a VXIPnP LabVIEW instrument driver folder-tree under the "instr.lib" folder under the LabVIEW 8.2 installation folder, like I've always done before with no issues.
But because this particular Windows XP lab-PC has a strong level of file-system lock-down, only the administrator is able to drop driver-function icons from that driver VI set into a LV 8.2 block diagram without "dll initialization routine failed" pop-ups, which is what always happens for all "domain users" who log on this system.
If I go to another XP PC (my laptop) with the same LV8.2 and driver-folder configuration under instr.lib, there is no problem with attaching to this driver DLL at all when building VI's with those driver functions. That system allows "everyone" permission to all file and folder write operations, all the way down the NI folder tree (scary, I know, but the same IT guy set it up that way, perhaps because this is a laptop).
I see there are two other threads in this forum giving possible solutions to this by setting the permissions on the \Program files\National Instruments\ folder (only) to allow all domain users write-permission on that folder (even though no files are apparently written to that folder). But this isn't working for me, or perhaps I'm doing it wrong. My IT guy will not allow me to open up all the permissions under the NI installation folder for domain users or everyone (like the laptop has), so I don't know if this would solve it, or if certain branches of the NI folder tree are the specific ones that need this done to them instead of others.
Does anyone out there have a solution for this? Is there something specific in this NI folder-tree that has to have specific permissions opened up in order to make this work?
I am burning way too many hours trying to solve this...
(I wonder if this would get worse once Vista is prevalent)
JB
To whom it may concern: My alias is also my nickname, I've had it since I was a (very) skinny basketball-playing teen. OK, so I've got a 38 inch waist now, but my hometown friends haven't shaken that appellation for me. I trust that you will someday be OK with that alias, as I have been with that nickname.

Answer 1

No, just tried that, didn't fix it, thanks for the advice though. I though it might have been DEP (Data Execution Prevention) which was turned on for this machine. But it wasn't.
I did discover that some drivers do it, and some don't. It must have something to do with the way the DLL is linked into the LVLIB file.
Is there a white paper or a location in the help file that explains how the DLL shared libraries should ideally be arranged in the *.lib folders in order to work properly?
JB
To whom it may concern: My alias is also my nickname, I've had it since I was a (very) skinny basketball-playing teen. OK, so I've got a 38 inch waist now, but my hometown friends haven't shaken that appellation for me. I trust that you will someday be OK with that alias, as I have been with that nickname.