LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

OT: transfering driver

This is a cross posting of a question I posted on the LAVA forum found here.
 
 
FIrst lets get this out of the way.

"BEN, you did not write it down? You idiot!"

I have been using a driver that that was developed using by one of NI's internal consulting group using the "VISA Driver Development Wizard".

When I first installed it following the supplied instructions, it did not work.

I then called the NI Developer that did the development and followed his directions to get it working.

Now this is where the "did not write it down" part comes in.

I was so excited I proceeded to test and develop and did not write down whatever it was I did to get it going.

My memory says that I had to type something at a command prompt, I suspect it was registration realted.

So a year latter the customer now wants me to develop a duplicate of my original system.

Well it turns out the NI developer has quit and finding a resource to fill in the blanks is not happening real fast.

Has anyone here figured out what it takes to transfer the "driver" to another machine?

I will supply more details if that would help but I will save the bandwidth unless requested.

Ben

Message Edited by Ben on 07-12-2006 03:19 PM

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 1 of 4
(2,822 Views)

Ben,

The instrument driver wizard creates an .inf file that get's stuck into a hidden windows folder called 'inf' appropriately enough. When we we debugging some of our custom usb and pci cards, I remember having to right click on the .inf file and select 'Install' occasionally. This should create the compiled .pnf file. Since the initial debug, I've only had to put the inf and pnf files onto new systems. I'll see if someone here with a better meory can think of anything else.

Dennis

Message 2 of 4
(2,813 Views)

Dennis wrote:

"I remember having to right click on the .inf file and select 'Install' occasionally."

That is good feedback Dennis.

I did try that and I saw the pnf file but since I had the board in the machine before doing that, it may not have worked correctly.

I'll try restoring a "pre-Ben" backup WITHOUT the borad in the machine and try that agin.

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 3 of 4
(2,803 Views)

Thanks again Dennis for those confirming words.

I managed to get it working and I now have a 31 step proceedure for executing this game. I'll spare you the details but here are some notes that may help others.

1) Make sure the board is not in the machine when you do the "Install" Dennis mentioned.

2) After doing the above "Install" and installing the inteface, just get through the New Hardware Wizard as fast as possible.

3) Under the Windows device manager there is a "Scan for Hardware Changes" option that will kick-off the New Hardware Wizard after you have deleted the bogus install at boot-up.

4) Make Image backups before you start this stuff. I ended up having IT restore the PC about 8 times before I had the procedure figured and the PC did not hang any more.

Again,

THANK YOU DENNIS!

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 4 of 4
(2,783 Views)