Labview app wont run on fresh reboot unless MAX is started.

Question

I am a Labview NOOB. I am the only IT here and started about a year ago and basically got thrown into the "labview" with 0 labview experience.I had to take an xp machine and turn it into a win 7 machine.
Here's some specs: labview 8.2 32bit running on windows 7 32 bit with IO libraries 16. Driving a gpip to usb 34970A data aquisition unit and a temperature compensation oven. Heres the situation. When i restart the PC my "temp_comp.exe"(application that labview consultant wrote) will not run. I get a few errors One as soon as i start the app: "oven Communication Fault" and one when i try to run the oven with shortened testing times and temp:
error 107387202 occurred at visa close in HP34970A close.vi-
34970A_read.vi>measure oven temp.vi->wait for oven to reach temp vi-
a comp loop.vi - a test loop sequence.vi>main temp comp.vi
Possible reasons VISA: hex 0xbfff009e a code library required by VISA could not be located or loaded.
I have reformatted a machine with xp and was able to get this running fine.
So here's the kicker. If i open up MAX and expand the devices and interfaces tree the program works fine and dandy. no errors. I have ran 3 batches in the oven over night with no problems. I figured i would just do an easy work around and have the max program start during startup but i have to manually expand the devices and interfaces tree before it will work.
Any ideas will be super helpfull Cheers!
Solved!
Go to Solution.

Answer 1

It never ceases to amaze me what managers think is possible.  It would be difficult for even an experienced LabVIEW programmer to port a LabVIEW app from XP to Windows 7 using a version of LabVIEW not supported on the operating system.  Tell them you'll see them in a few months.
I ran into an issue once where a vendor's Win7 dll had different default settings than the priginal and we couldn't figure out why we couldn't communicate with the I/O card.  Seems that they inverted the address bits as default.  Of course, there was no documantation on the change - unless you count the source code itself.
It was an intentional change which would make sense if you were someone who bought a new card and never used the old dll before.  But guess what?  The card was already obsolte/unsupported, so there AREN'T GOING TO BE ANY NEW USERS!
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.