7.0 executable won't run on xp with new pci-gpib.

This executable ran on previous version of windows. Automation explorer talks to gpib and instruments ok. GPIB version 2.2 installed. Executable doesn't seem to try to talk to gpib, ie. doesn't hang up.

Hello,
If you can talk to your instrument from Measurement and Automation Explorer then it means that the driver and hardware are installed properly. So it has to do with the application itself.
Make sure that you are using the correct device name, because this new board might have gotten a different device number and also check the primary address.
If you have LabVIEW installed in the computer sometimes the problem is because it was installed after the driver, so you might want to reinstall the driver.
If you don�t have LabVIEW but only the .exe and the run time engine, then you can open NI-SPY and see if the application is trying to talk to the instrument at all.
You can find NI-SPY in Start»Programs»National Instruments. Enable the capture a
nd then open the LabVIEW application and run it. You should see some GPIB or VISA commands in the capture.
Hope this helps.
Ricardo Santa Olalla
National Instruments.

Similar Messages

How do you run Adobe Reader with New Lions

How do you run Adobe Reader with New Lions?

Lion has Preview, you may not need Adobe Reader.
Preview Help
View your images and PDF documents, touch them up, annotate them, and share your comments.
Regards,
Colin R.

Executable won't run

I have a main application calling a sub VI 'Sub Al getest2.VI" into a sub panel. When I include a 'display message to user' from the functions palette in de sub VI, the whole program runs fine in developer mode. After building an application, the sub VI opens in the main applications sub panel, but it won't run. The same if I add another custom VI to the "Sub Al getest2 VI" it also won't run after building the full application.
The fun part is: If I create a new project with the sub Al getest2.VI as the main program (and including embedded sub VI's) I can build an executable and it will run fine on it's own.
In the main application build I include all project files as 'Always included'.
Do you have a suggestion what could be wrong?
Attachments:
Sub Al getest2 runs not.vi ‏34 KB
Sub Al getest2 runs.vi ‏20 KB

Putting a VI in a subpanel is not the same thing as calling it. If you want the VI that you're going to put in the subpanel to start running after you open the reference to it, you have to tell it to run by using something like the Run VI method an asynchronous call node.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Oracle 9.2 setup.exe won't run on P3 with Win2K SP3

Hi, everyone:
We had difficulty in installing Oracle 9.2 onto our Dell P3 Latitude C800 laptop running Win2K Professional with SP3. As many of you already reported, after double clicking "setup.exe", it won't run and nothing happened. We tried to run "autorun.exe" but that didn't work either. We also changed the system Temp/Tmp environment variables but no help either. Since our laptop is P3, not P4, not sure whether changing the symcjit.dll name would help.
This seems to be a Java issue but not sure exactly what caused the problem. We had TrendMicro's OfficeScan AV s/w installed. Is that the problem? What other commonly used s/w are Java based and may cause conflict with Oracle installer? We only have MS Office, VisualBasic, UltraEdit, Acrobat, WinZip, and GetRight installed on the laptop.
Are there any other suggestions for us to try? Your feedback will be greatly appreciated.
Jason

disable getright and try again

Executable won't run on target PC

Hi
I have written an application to control a 'Data Translation' PCI data acquisition card (DT302) using LabVIEW (8.6.1). I have used Data Translations 'LVLink' VIs in the application. It works perfectly on the development PC as a VI and as an executable.
The problem arises when I try to run the executable on a target PC. The program fails to recognize the DT302 card. I believe I have the necessary extra files/software installed:
LabVIEW RTE (8.6.1)
DT Open Layers for .NET Class Library
LVLink2.dll
Driver for DT302 card
I know the card is installed correctly as it can be recognized by other (non Labview) programs. I think I may require an additional file or .dll but I'm not sure.
Any help would be greatly appreciated
Thanks
Stuart

Suspect this is due to a relative path call to the dlls being created by the calling VIs when you compile.
It may be due to a version difference in the files mentioned on your PC and the ones used on the "blank PC".
Recommend you make an installer which includes the dlls and re-installs them to the PC - it is possible that the NI calls to the dlls are modifying them or the registry.
James
Edit:
Compare the Path between your LabVIEW PC and your blank one
Also check the correct params are inserted in the path for any calls to functions external to LabVIEW, this could be causing breaks if %PATH% has not got the required files in it.
Message Edited by James W on 05-18-2010 04:31 PM

Matlab script in executable won't run

I'm having trouble with getting a VI with a MATLAB script to run reliably, specifically when built into an executable.
I'm using LV8.0, Matlab R2006a.
The VI (not executable) runs properly when I start the computer fresh (i.e. just after a reboot)
The MATLAB command window opens as soon as I open the VI.
If I build an executable and run it, it works, so long as I haven't closed LabVIEW and the VI.
If instead, I attempt to close out LabVIEW and run the executable alone, the MATLAB command window does not start, and the MATLAB functionality is ignored.
I have updated all of my dlls, and I have checked the box enabling the ActiveX server (though I don't know what to name the server). I have also read all the associated Knowledge Bases, and found their solutions did not apply.
I also have intermittent issues running the VI once I have tried running the executable.
If I make a change to my MATLAB script, I can get the VI to run again, but if it has failed once, the MATLAB command window no longer opens when the VI is opened.
I can solve this problem by rebooting too, but it seems like there should be a better way.
Any ideas?

Hi tblir,
Can you try to run and build into an
executable one of the shipping examples (i.e. MATLAB Script – Fractal.vi)? Let me know if this exemplifies the same behavior.
Ecleamus Ricks, Jr.
National Instruments
Applications Engineer

Vi outside executable won't run - Labview 8.0

Hello.
I have a main program including a set of vi:s. I then have modules that hook into the program using vi:s in the main program.
I call the module from the main program with a open vi reference + invoke node.
#1 Main <- #2 module
And it works great. I then build my main program to a executable and
when I launch the executable (main) there is a popup searching for vi:s
and then it dissapears. The module is not executed.
I logged the error output on the open vi reference in the main program and it states: "Error 1003, could not find subvi:s".
In application.ini i have:
[application]
viSearchPath="/path/path/application/*"
Even if i remove the viSearchPath line the main vi looks for the sub
vis, but Im not sure if its actually looking for the vi:s in my
executable. Is there a way to check that the application is actually
using the application.ini file? Am I doing something wrong? This is
possible right? =)
I'm running Labview 8.2, Linux version.
Any help is more then appreciated.

"Fox_Mccloud" <[email protected]> wrote in message news:[email protected]...
Hello.
I have a main program including a set of vi:s. I then have modules that hook into the program using vi:s in the main program.
I call the module from the main program with a open vi reference + invoke node.
#1 Main <- #2 module
And it works great. I then build my main program to a executable and
when I launch the executable (main) there is a popup searching for vi:s
and then it dissapears. The module is not executed.
I logged the error output on the open vi reference in the main program and it states: "Error 1003, could not find subvi:s".
In application.ini i have:
[application]
viSearchPath="/path/path/application/*"
Even if i remove the viSearchPath line the main vi looks for the sub
vis, but Im not sure if its actually looking for the vi:s in my
executable. Is there a way to check that the application is actually
using the application.ini file? Am I doing something wrong? This is
possible right? =)
I'm running Labview 8.2, Linux version.
Any help is more then appreciated.
Well, it's clear that the exe cannot find some subvi's used by the subvi. Some vi lib vi's are not included in the runtime (e.g. some of the picture control stuff). To be sure, you can save the sub vi as development llb, and include vi library vi's. That should include everything it needs.
Under windows, you can start a VI with the executable. When the exe is running, you can use the command prompt to start a vi in the exe (e.g. c:\test.exe "c:\vi with missing subvis.vi"). This does almost the same as starting a vi dyamically, from the exe. A big difference is that you get a list with all the vi's that are missing in a dialog. Don't know if this works with Linux, but usually this work better...
Another thing is when you use type defs. The exe, by default disconnects the type defs. The vi that is started doesn't. That will conflict. So untag the "disconnect from type defs and polymorphic vis" tag in the app builder (if it's in the linux builder).
Regards,
Wiebe.

Labview 8.5 executable won't run on Runtime Machines

Created an .exe from my Labview Project TS_playback.lvproj. I am running Labview 8.5. Target computers have Runtime Engine 8.5. Windows XP mostly (and 2000). When I run the .exe I either get a quick flash of the loading vi box , or nothing at all. If I have task manager open, I do see the exe open briefly before disappearing.
When creating the exe, I use my main vi as the startup vi.
I don't use any other files in 'Always included'
All subvi's and dependencies are 'Included if referenced'
Custom vi properties of startup vi are basically default, except - turn off run when open, turn off allow debugging.
Note - the vi has locked subvi's associated with LockinPLL and LockinDemodulator.
The code itself is a torn down version of a much more complicated real-time version. This version is simply to post-process data, mainly for a client to fiddle with, so it is meant to function and not be pretty. Sadly, now it only functions on our office machine.
Any help would be great.
Thanks
Attachments:
TS_Playback.zip ‏3064 KB

Lokis wrote:
Target computers have Runtime Engine 8.5.
There are two flavors of the runtime engine and you need the 97MB one. Could it be that you installed only the 24MB web browser version
See this page for details.
LabVIEW Champion . Do more with less code and in less time .

ITunes won't run - detected problem with audio configuration

I just installed iTunes 7 (I had iTunes 6) and now it won't work. An error message comes up that says "iTunes cannot run because it has detected a problem with your audio configuration". iTunes worked just fine before I downloaded the new version. I tried doing a system restore to go back to version 6 but it wouldn't work. Please help! Thanks!

I searched on google and found my answer. I redownloaded quicktime and now it works.

Forte for Java CE won't run files created with J2SDK

I'm very new to Java. When I try to run packages, classes written with Java 2 SDK, I get the following error:
java.lang.NoClassDefFoundError: TextComponentPrintWriter (wrong name: utilities/TextComponentPrintWriter)
I have mounted the root directory and the JAR files- or I think I have- but I'm still getting an error when I run the programs form the IDE of Forte v. 3. By the way, they all compile okay. Please help!

Try downloading a newer SDK and getting
c:\j2sdk1~1.1_0\jre\bin
out of the path

KT4 won't run at 133MHz with Athlon XP2400+

I have recently built a new PC with:
MSI KT4V-L Motherboard
Athlon XP 2400+ CPU
Arctic Cooling Copper Silent CPU cooler rated for Athlon XP up to 2800+
Samsung 256Mb DDR400 RAM
Matrox 80Gb HD
Sparkle GeForce 2 MX400 Graphics card with 32Mb
Running Windows XP Pro
On initial instillation, the processor is reported as Athlon XP 1800+ by
BIOS. Is this correct?
By default the FSB frequency is set in the BIOS to 100MHz, and Memory speed is Auto.
I've managed to push the FSB up to 120, which leads to PCAlert4 reporting a
CPU speed of 1808MHz (15 x 240.5) and a CPU voltage of 1.60v. CPU temp is
measuring 54 degrees C.
However when I try to push speed up to 133, I can't get windows to start.
It gets through POST, but then reboots before starting windows.
What's wrong?
I've read the MSI FAQ section, but nothing is even close to my problem. I've
read the mobo manual cover to cover and several forums (including this one) and articles on the web.
They do indicate that there are compatibility issues with DDR400 memory,
which is why I went for one of the recommended brands that is known to work
with this motherboard. In retrospect, I should have plumped for DDR333
memory since it gives me more options for increasing memory later, and would
have been more likely to work with the Athlon XP 2400+.
I've already cointacted my reseller and he just indicated that I need to
change settings in the BIOS. I've read all about these BIOS settings and
tried dozens of combinations beyond the most obvious.
I'm considering now:
a) borrow some DDR333 to test if its the memory.
b) ask my reseller to test the mobo/cpu and ram, but this will cost me more than £30 per hour.
c) accept that I'll only run at 1.8GHz, which is a significant improvement to my previous Celeron 466.
Is there anything else I can try?
Dave

Thanks for the response.
Ok, I'll try to answer all questions:
1) Did you try to download the new firmware?
No, my Live update says I've got AMIBIOS v1.80 and didn't suggest an upgrade
2) Set the FSB to 133 and the memory at 266Mhz (try not to use 333mhz DDR modules)
Done this already, but no joy.
3) After you set the options in the BIOS, it would be better if you make a fresh install of WinXP or whatever OS you have.
I'm not prepared to re-install WinXP PRO unless I see evidence that it will run successfully at FSB 133.
1. Power Supply not up to spec. Post the specs on the 3.3v, 5v, 12v rails. The Amps output for those voltage lines.
Dragon Technologies 350W Power supply model LC-B350ATX.
+3.3V 28A
+5V 35A
+12V 16A
-12V 0.8A
-5V 0.3A
+5VSB 2A
+5V & +3.3V combined load 200W
+5V & +3.3V & +12V combined load 330W
2. CPU cooler not mounted properly. 54 degrees is pretty for an underclocked CPU, double check to make sure the heatsink/fan is mounted fine. Remount to ensure that it is done properly.
Cooler mounted ok, but I thought sticky copper block on underside of cooler was a "thermal pad", so I followed instructions and did not put any thermal paste on. I intend to rectify this, although slightly worried I'll trash die when lifting heat sink. Anyhow, when machine first turned on, CPU temp is 40 so surely it could at least boot up Windows if only to fail 5-10mins later as temp rises to 55?
3. Memory settings too agressive, set the CAS latency to 2.5, try to set them to the higher value, just for stability testing.
Tried this, but still hangs before starting windows.
Will sort out heatsink next.
So you don't think its my DDR400 mem then?
BIOS reports CPU as 1800 when FSB set to 100 or 120. Is this normal?
Dave

Retail version of 10.5 won't run on AGP with an OWC mercury G4 1.4 Ghz processor, 1 Gb ram, 32 mb vid card; was running 10.4 no problem

i have no idea what's happening, the machine ran fine with 10.4, after i installed 10.5 over the 10.4 on a 60 gb hdd it wouldn't run, I start the machine up, get the chime then the Apple logo and then the machine abruptly shut off after 35 seconds. installed a new hdd, an 80 gb, formatted it using the 10.4 install disk and partioned it into 2 40gb sections and then installed OS 10.5 onto the 1st partion, get the same result. the OS seemed to install OK, but as before the machince was shut off when I returned, and behaves exactly the same way, 35 seconds and shuts off. the Leopard 10.5 is a retail version, have NO idea what is happening. i read what the requirements for this OS and think I have met them. shutting down so soon into the startup makes me think its a hardware problem. do have a Logitech marble mouse and a non-Apple usb key board, but as noted had no problems with OS 10.4

i did a clean install of the 10.5 OS on a virgin hdd, that i partioned using the 10.4 install #1 cd.
Try it with the 10.5 Install Disc... what is the 2z691-****-A number on the 10.5 Disc?
1. Insert the Mac OS X 10.5 Install disc, then restart the computer while holding the C key.
   2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at the top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
      *Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
   3. Click the Erase tab.
   4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
   5. Select your Mac OS X volume.
   6. Highlight the drive, select Partition Tab, then Format type... MacOS Extended Journalled, select the Security Options button, choose Zero Out Data, Erase, one pass... after completion hopefully you'll be able to get a good install.
Oh, does it run forever whilst booted from the Install Disc?

K8t Neo2 won't run dual channel with Opteron 165

Hi,
I have a K8t Neo 2, and was running a Newcastle 3500+ on it, with 2x1GB PC3200 memory sticks (Buffalo memory) in dual channel mode (ie DIMM 1 and DIMM 3 populated) without any problems. I replaced the 3500+ with a new Opteron 165, and the system would not post. One of the red lights on the D-bracket was red, the rest were out.
To troubleshoot, I removed one of the memory sticks, and the system booted fine. I then put the 2nd memory stick in a non-dual channel setup (DIMM 1 and DIMM 2 populated), and it booted fine. If I try booting the system with the RAM in any dual channel enabled configuration, it will not post. I verified that it isn't a RAM issue, because I have 2 sticks of 512 MB ShikaXRam, which has always worked fine, and I got the same behavior as I got with the Buffalo RAM. I have tried changing the RAM clocking in the BIOS, and that also doesn't help, because it seems it reads the speed automatically no matter what you set the DRAM clocking page to.
Does anyone have any suggestions? Is this board not Opteron 165 compatible with dual channel memory?

Alright, I tried all of the steps mentioned, setting optimized defaults, even tried changing all memory timings to the most conservative available. The only way the system will boot with 2 DIMMs installed is if they are in the two slots furthest from the CPU. It will also post with 3 DIMMs installed in any configuration.
I also have a generic 500 w PSU that is rated 32a on the 12v rail that I tried quickly plugging in (just plugged the 2 PSU connectors to the motherboard without hooking any of the IDE devices to it) It still exhibits the same behaviour. With no hard drives, optical drives, etc plugged in, wouldn't that pretty much eliminate the PSU as an issue?
I don't want to just spend $100 on a new PSU if it's highly unlikely to be the issue. Does this sound like something I'd need to replace the motherboard to fix? Is the performance difference between dual channel and single channel enough to even warrant buying a new board? The reason I want to avoid replacing the board right now is because I still have an AGP card, and don't want to replace it right now as well as the board, and getting another AGP based board seems to be stupid. Also, AGP boards are really hard to find now, and most of them available locally run on the ULi chipset

HP OfficeJet 6310 All-In-One printer won't print in color with new cartridge

HP OfficeJet 6310 All-In-One printer on a iMAC OSX version 10.9.5 system
Hello,
As I don't print in color much but had need to I discovered my printer not printing in color. I trouble shooted and even replaced with an new HP95 new from Office Depot ( I never buy refilled). The printer still won't print color but it advances the paper as if it was printing - just no ink on paper. I have cleaned thoroughly the ink jet heads, cartridge area, and run all the alignment and printer utilities. The test page print does not show color either. I have no error messages. Don't know what else to do.
thanks
DH

Hi there @dhengr!
Thanks for contacting the HP Forums!
I can see your having a print quality issue with your HP OfficeJet 6310. I should be able to provide documentation that will help locate a resolution. You mentioned you have already tried another HP95 tri-color cartridge with no resolution. I also noticed you said that the quality report from the printer also has no color ink.
If a stand alone test report is performed from the front of the printer such a printhead cleaning or print quality report and there is no color on the page then you are likely looking at a hardware issue within the printer. I have provided a document regarding Missing, Faded, or Dull Colors on the HP Officejet 6310 All-in-One Printer. If you follow the document from start to finish and still have the same issue then I would recommend contacting our HP tech support via phone. They deal with hardware warranty and replacement options.
Please call our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region. http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
Have a great weekend and thank you again for posting on the HP Forums!
Cbert
I work on behalf of HP.
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" at the bottom of this post to say “Thanks” for helping!

Won't print black ink with new cartridge

I have read all advise. Black stopped printing. New genuine HP cartridges. Did partial and whole resets. Cleaned printhead. Removed all cartridges and case and cleaned well. Very gunky. Still won't print HELP ME! Have read thru all the posts and did everything

The post here may help resolve black not printing on your Offcieejt 6500, go through all the troubleshooting steps in the document referenced there and if that does not resolve the issue then try soaking the printhead.
If this does not resolve the issue you may need to replace the printhead.
Bob Headrick, HP Expert
I am not an employee of HP, I am a volunteer posting here on my own time.
If your problem is solved please click the "Accept as Solution" button ------------V
If my answer was helpful please click the "Thumbs Up" to say "Thank You"--V

7.0 executable won't run on xp with new pci-gpib.

Similar Messages

Maybe you are looking for