Installing LabVIEW DSC 8.6 Run Time on Windows XP Embedded flash memory

I'm trying to install LabVIEW DSC 8.6 Run Time on an embedded PC running Windows XP Embedded. This has a small local disk (c), so I would like to install DSC Run Time on a secondary flash memory drive (d). The installer tells me that I don't have enough free space on drive c, but I cannot browse to select drive d. What do I need to do to get this installed?
Thanks,
Josh

The DSC module can't easily be installed to external flash memory. You'll want to move any extra data onto the flash drive to free up space on the internal memory for installing the DSC module.
Mark E.
National Instruments
Schedule a Free 1-Hour online LabVIEW Tutorial with an NI Applications Engineer

Similar Messages

Run-Time Error window doesn't have Retry and Ignore options

Hi,
The run-Time Error window usually have 4 bullets at the bottom part. They all used to be enabled untill recently. Somehow, I only have the Run Cleanup and Abort immediately bullets enabled. Why are the Retry and Ignore disabled? Is there an option to turn it on and off?
Thanks
Rafi

Hi,
Its possible you have operator privileges. What's user type are you running as?
Regards
Ray Farmer
Regards
Ray Farmer

My macbook won't copying anything to any external hard disk drivers same time can copying to any flash memory

my macbook won't copying anything to any external hard disk drivers same time can copying to any flash memory
my macbook with ratina display the newest virsion

my macbook won't copying anything to any external hard disk drivers same time can copying to any flash memory
my macbook with ratina display the newest virsion

Install Labview DSC Run Time without SQL Express

Hi
I have an application of DSC run time that I tested successfully but now must be installed on a server and my client does not allow install an instance of SQL Server Express because he are already using the Enterprise version. What should I do to not install the SQL Server Express incorporated in the DSC Run Time and use the SQL Server Enterprise already installed on the server?

Hello Jdrendon
Did you try to install your application on a PC with an instance of the Enterprise version?
Maybe another instance of SQL will not be installed in this case, because you already have a later version installed.
The second possibility is just uncheck the option to install the SQL Server Express when you are installing your application.
Let me know if it is possible and if it solve your problem.
Plínio Costa
Application Engineer
National Instruments Brazil

Why does my LabVIEW 2010 Program ask for the LabVIEW 8.5.1 run-time engine every time it is launched after being installed?

It is a simple timer program that shows the elapsed time (see attached pics). I can't think of a single thing that should be causing this ... It started happening right after I selected scale objects with front panel resizes and recompiled, and re-installed the app. It was not happening before that when installed without the selection of resizing, but then I removed the selection and it still happens. Any Ideas would be appreciated.
Solved!
Go to Solution.
Attachments:
Timer Block Diagram.JPG ‏100 KB
Timer Front Panel.JPG ‏34 KB

A bit more info:
If I cancel through all of the dialog boxes (see attached) when trying to launch my little app, it runs normally. Looks like it really doesn't need the 8.5.1 engine after all.
Attachments:
Run-time Engine 8.5.1 dialog box.JPG ‏25 KB
Run-time Engine 8.5.1 dialog box - 1.JPG ‏15 KB

Can I run LabVIEW DSC on Fieldpoint real time processor?

I want to use the Fieldpoint real-time processor as an OPC server on the network. Can I run DSC runtime on the Fieldpoint processor?

There are two separate questions here. One, can a FieldPoint Real-Time Controller act as an OPC Server, and two, can the DSC Run-time engine be downloaded into the FP-20XX controller. The answer to both questions is no.
The FieldPoint RT modules are running a Real-Time OS, they are not running any version of Microsoft Windows. The OPC Specification is based upon Microsoft's DCOM model which is built into Microsoft Operating Systems. This does not exist in the built-in OS and thus the FieldPoint unit can not be an OPC Server. However, a host PC running Windows can have an OPC Server on it that in turn publishes all of the data from the FP-20XX module.
Can the DSC run-time be loaded into a FP-20XX? No, it was never designed for it and would not fit in the mod
ule.
Regards,
Aaron

DSC 8.0 Run-Time custom installation

Hello,
I have developed an application using DSC 8.0 features and it runs fine on my development computer. I have a couple of questions regarding deploying a buillt executable on customer computer.
1. Can application exe be located in a folder different as DSC RTS installation?
2. Can DSC Run-Time 8.0 be installed in location different as default? I started an installation process of DSC RTS 8.0, but the Browse... button to select custom destination is disabled.
Ideally, I would like to achieve that application executable ( and all folder hiearchy needed ) would be separate from DSC RTS ( as when building pure LV code). If this is not possible, than 2 options exists:
a: to install application structure to default DSC RTS location or
b: to install DSC RTS to a custom location of my application ( prefered )
Please, can you explain me what option do I have.
I can not find a document that would describe a complete procedure for deploying DSC application with all possiblle options that could happen, as we all know that DSC applications are usually preety complicated and consists of many parts deployment can be very frustrating. This is a request for NI folks to put together one complete document ( kind of " Deployment Bible" ) for version 8.0
Regards,
ROMP

Matt:
Please try the following and let me know what you find.
Open your project from the project explorer
Right-click on your application and select Properties
Click on Advanced in the Category list
Disable Enable Enhanced DSC Run-Time Support
I am curious to know what you find.
Regards,
Rudi N.

Test Stand LabView adapter 8.6 run time will not run 8.5 VIs

I’m trying to run a script I developed with a dev computer on
a regular PC set up with a Test Stand User Gui, and run times for Test Stand
and Labview.
With the Test Stand Labview adapter set to 8.6.1 all of my
ENA(Agilent Network Analyzer) calls fail for “VI Version is too early to
convert to the current LabVIEW version.” The ENA library is written in 8.5. If I set the adapter to 8.5.1 then all of the
VIs developed in 8.6 fail. In addition
it will not run any VIs that I save back to 8.5. I installed a demo Labview development
version (2010?) and everything ran fine with the adapter set to Development
System.
I am not sure what to try next to get it to run on the
regular PC, any hints.
Test Stand = 4.2
LabView = 8.6
Running in windows XP
Solved!
Go to Solution.

One of the many things I tried was saving the ENA library to 8.6, but I could not get it work.
This is the Original library I installed and was trying to Convert (8.0 upgrade agena.zip)
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=001CE83736F3674BE0440003BA7CCD...
I am about to try this one. (8.2.1 Upgrade)
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=74D1F1D4EB5268E8E04400144FB7D2...
I am pretty new to labview so I am not sure how to make the save to previous version workfor libraries, but I can easily do it with individual VIs. For libraries, it creates a new directory, and puts in all of the files and then asks me about saving the lib files as something else. This is where I think I get it wrong. I tried it again today and got the same results.
I greatly appreciate the Help
Brian

Getting LabVIEW load error code 59 using LabVIEW 2010 with a Run Time Engine.

I use a vi compiled with a run time engine to run separate vi’s in my application directory. Once a file association is made with this exe file any Vi in my application directory is available to be loaded as needed. This is a process that has been very successful for me over the years and would prefer to continue using this process. Most of my applications are running in LabVIEW 8.6 and have moved them to 2009. First indications are in 2009 this process is still working. However, I plan to go on to 2010 before upgrading my test stations.
In 2010 I get the error 59: “The source file’s compiled code has been separated, and this version of LabVIEW does not have access to separated compiled code.”
The same dialog box also presents, (Hex 0x626) “Cannot open a VI with separated compiled code in a Run Time Engine that has no access to the VIObjCache.”
What can I do in the build that will get around this error?
Thank you

Thank you for the solution. I am sure this works until the next vi in the vi library gets this option selected.
The bigger issue is I was doing something that National Instruments did not support. When I started in the days of LV 4.0 it was recommended to me that I use this method as virtually all my applications were for in house projects. This is still my preference because it gives the most versatility and allows modifications of single files rather than compiling the entire application.
The final solution I ended up with for those who may be having the same issues. My recommendation for what it is worth, is to compile the application as an executable. This is from what I can tell the only acceptable and supported method. Using this method the problem is solved.
I have accepted this as the solution. I still don't like it. I could list the reasons why but it is a mute point.
Thanks again for taking the time to respond to this issue and offer the solution you found.

Can I use labview 7.1 run time in windows 98?

I am going on update a too old test system. I use labview 7.1,but I find I can't install labview 7.1 runtime in windows 98.
so should I use labview 6.1 instead of it?
Sonic
Diffrent Strokes for Different Folks

Why cnt you update both ?!
- Partha
LabVIEW - Wires that catch bugs!

Will there be problems installing LabVIEW 7.1 if I upgrade to Windows XP?

We have a program in LabVIEW 7.1 running on Windows 2000. We plan to upgrade all of our computers to Windows XP. Will there be any problems installing LabVIEW 7.1 onto Windows XP?

Hi,
No, you won't experience any problems with that upgrade. LabVIEW 7.1 is fully compatible on Windows XP, just as it is on Windows 2000.
Peter
Peter L.
Applications Engineer
National Instruments
www.ni.com/support/

I want to install a learn software that runs normally in windows?

I am trying to instal a lern software for my kid on a mac that runs only on windows. is there a possibilty to download it and make it run?

Have your cake and eat it too! With the Intel Macs, you can run windows in a virtual machine. You will need our own copy of Windows.
Don't miss the free VirtualBox.
"VirtualBox is a general-purpose full virtualizer for x86 hardware. " Runs Windows on Mac OS.
http://www.virtualbox.org/
Parallels:
http://www.parallels.com/en/products/desktop/
& some catalog order places sell Parallels for 9.99 when you buy a mac.
With VMware Fusion, run the most demanding Mac and Windows applications side-by-side at maximum speeds without rebooting
http://www.vmware.com/products/fusion/
Wine emulates the windows api's on an intel Mac.
"Wine lets you run Windows software on other operating systems. With Wine, you can install and run these applications just like you would in Windows."
http://www.winehq.org/
Robert

How do you create a program in Labview that can be run as a Windows Service?

I would like to create a Labview program that can be run as a Windows service. I have read the following Knowlegebase articles and have done what they say.
Creating a Windows NT Service Using LabVIEW http://www.ni.com/white-paper/3185/en
Running a LabVIEW Application as a Windows NT/2000/XP/Server 2008/7 User-Defined Service http://digital.ni.com/public.nsf/allkb/21BA0F671A63A60386256CB4004DF99B
When trying to start the service I get an error that says the program didn't respond to the start in a timely manner. I also set the "run when opened" parameter in the VI. I am programming in Labivew 2010, proffesional version. The server is running Windows Server 2008. Can anyone help? Is the ini file important in Windows Server 2008?

I haven't looked through all those links. But I have created Windows Services from LabVIEW executables way back when WinXP came on the market.
The problem with services is that they have no UI. So you can't really see what is going on. Your EXE might be failing or hanging due to some kind of error (most liklely a security/permissions error), but you can't see the error. So my advice is to either:
1. Have your EXE write lots of info to a log file. Write info that log every step in the application. If an error ocurrs, have it write the error info to the log file. That is a very useful debugging tool.
2. Use VI Server functions to monitor the service to see what is going on.

Renew; installing OSX on a PRO running only on Windows XP

Back to the drawing board with my older post (see title). I re-formatted the HDD on another PRO and installed a fresh version of OSX on the drive. It boots without issues on that PRO hence no HDD issues. After putting this HDD in my PRO same problem occurs, it runs perfect on Windows XP (including all features) but wont boot past the Apple logo after boot up on the installed OSX (same with newly installed OSX on external drive and disc). Can it be a hardware issue? If yes how can i check this when the PRO only runs on XP?

On the optical disk(s) that came with your Mac, there is a program called Apple Hardware Test. It is accessed by booting this optical disk while holding the D key (instructions are on the disk).
bd

Crystal Reports ClickOnce install fails after upgrade to run time 13.0.2

I realize this is very similar to two other posts but the ClickOnce failure was not addresses in the two threads I found.
Visual Studio 2010 V 10.0.40219.1 SP1Rel
.NET Framework V 4.0.30319 SP1Rel
Crystal Reports for .NET Framework 4.0 BuildVersion=13.0.2.469.Cortez_CR4VS (from ProductId.txt in the download folder)
Application was original developed using CR BuildVersion=13.0.1.220.Cortez_CR4VS
So since I upgraded this week, if a user clicks the Launch link on the deployment web page the application loads the appl;ication update and starts. Does not even check with Crystal Reports but everything seems to work.
The new version of the Crystal Reports runtime tries to install for users I have that enjoy clicking the run button. The install fails and points at a log file, the key part of which is
Installing using command 'C:\WINDOWS\system32\msiexec.exe' and parameters ' -I "C:\DOCUME1\clyle\LOCALS1\Temp\VSDC8.tmp\Crystal Reports for .NET Framework 4.0\CRRuntime_32bit_13_0_2.msi" -q '
Process exited with code 1603
Status of package 'SAP Crystal Reports Runtime Engine for .NET Framework 4.0' after install is 'InstallFailed'
Uninstalling the previous version manually alleviates the failure as does manually running the msi on the target machine. But that kind of defeats the purpose of ClickOnce. Looking at product.xml that accompanies the runtime download I see it tests for the 13.0.2 version and bypasses the install if it finds it but it does not check for earlier versions.
Another thread I read indicated changing the switches in the install command would work but I am not clear on how to do that from ClickOnce, I cannot locate where the command is being given. Is there a way to get it to test for previous versions and delete them or force an overwrite using the ClickOnce?

Ludek,
Did this issue above every get resolved?
Here is what I have:
ClickOnce, Windows form app that uses Crystal. I upgraded to VS 2012 and Crystal right along
with it.
I only want the 32bit version to install, even on 64bit
machines. I have modified the
product.xml file to allow for this. Also
have some machines with version 13.0.0 and 13.0.1 of the Crystal ClickOnce msi
file. Would like to get everyone up to
13.0.6.
I am doing ALL this testing on clean VMWare installs.
Windows 7 x64 and Windows XP x86.
I force the 32bit install in the product file. (This I believe
is working correctly) And I do a version check, this is where the problem comes
in… Below, from the product file:
<InstallChecks>
    <RegistryCheck
Property="CRRuntime32Version" Key="HKLM\SOFTWARE\SAP
BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports"
Value="CRRuntime32Version" />
</InstallChecks>
Note to path in the registry. This path which is installed
by CR is different for Win7 vs WinXP, not sure why? In Win7 the path is:
HKLM\SOFTWARE\Wow6432Node\SAP
BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports
Also if you have version 13.0.0 installed there is no entry
in the registry for the version number at all!
The log file also show that it can’t find the version if 13.0.0 is
installed.
Admittedly the error log shows that it is somehow finding
the version if it is 13.0.1 (nothing for 13.0.0)? But even though I have it set
to skip the 13.0.6 install if the version check is 13.0.1 or higher Crystal
attempts to install anyway, and it fails in the process, halting the entire
ClickOnce install.
In summary. I need to
be able to check the version currently installed and update it to 13.0.6. This fails and seems to be a bug?   Hopefully there is a work around.
Thanks,
Jim
The product.xml file I have modified is below for review.
<?xml version="1.0" encoding="utf-8" ?>
<Product
xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper"
ProductCode="SAP.CrystalReports14.NET.2.0"
>

<PackageFiles>
    <PackageFile Name="CRRuntime_32bit_13_0_6.msi"
      HomeSite="http://downloads.businessobjects.com/akdlm/crnetruntime/clickonce/CRRuntime_32bit_13_0_6.msi"
      PublicKey="30818902818100cbc8f3d8b4bc4db86f150116f4ad7f2fd2d91d29ae6f752c2aa6489cbda10670a0b97b8840d03dd8d082bfb985882b1278504bdd15a1f2a00b629cd70bf26d94b3933a9647a12c819ca67acd1c32ac942e1b824aad4fd8e8a989c45cf4a13770fe2b233f598ea06b62081174be6b7701f347612c126d42c2f9b759ff00164eb30203010001"/>
</PackageFiles>
<RelatedProducts>
    <DependsOnProduct Code="Microsoft.Net.Framework.2.0" />
    <DependsOnProduct Code="Microsoft.Data.Access.Components.2.8" />
</RelatedProducts>
<InstallChecks>
    <RegistryCheck Property="CRRuntime32Version" Key="HKLM\SOFTWARE\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports" Value="CRRuntime32Version" />
</InstallChecks>
<Commands Reboot="Defer">
    <Command PackageFile="CRRuntime_32bit_13_0_6.msi"
      Arguments=''
      EstimatedInstalledBytes="50000000"
      EstimatedInstallSeconds="220">
      
      <InstallConditions>
        
        
        
        
        <BypassIf Property="CRRuntime32Version" Compare="VersionGreaterThanOrEqualTo" Value="13.0.1"/>
        
        <FailIf Property="AdminUser" Compare="ValueEqualTo" Value="false" String="AdminRequired"/>
        
        <FailIf Property="Version9x" Compare="VersionLessThan" Value="4.10" String="InvalidPlatformWin9x"/>
        
        <FailIf Property="VersionNT" Compare="VersionLessThan" Value="5.00" String="InvalidPlatformWinNT"/>
      </InstallConditions>
      <ExitCodes>
        <ExitCode Value="0" Result="Success"/>
        <ExitCode Value="1641" Result="SuccessReboot"/>
        <ExitCode Value="3010" Result="SuccessReboot"/>
        <DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
      </ExitCodes>
    </Command>
</Commands>
</Product>

Installing LabVIEW DSC 8.6 Run Time on Windows XP Embedded flash memory

Similar Messages

Maybe you are looking for