Application builder (activate activex)
Hello together,
you know that a VI can be compiled into an EXE-File with the Labview Application Builder.
Did somebody recognize the possibility to activate the ActiveX server within this EXE and made use of it?
Here you can find general information concerning this topic.
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/activating_lv_activex_srv/
There is an example shipping with LabView that shows how this works:
Refer to the VBToLV.frm, VBToLV.vbp, and VBToLV.vbw files in labview\examples\comm for an example of calling LabVIEW as an ActiveX server from Microsoft Visual Basic.
Similar Messages
-
How to build an ActiveX bridge for jasper viewer
Hi,
i want to build an ActiveX bridge for Jasper viewer.Does anyone knows How to build an Active X bridge for a component.I am very new to this concept.Please someone help mehi,
can u please give some url's which is helpful to create Activex Bridge? -
How is application builder to be installed with V8.21?
I have just installed my new V8.21. Where is Application Builder? Should I have received another disc? Should I install from the V8.20 disc? I never installed V8.20.
Thanks,
ChrisHello Chris,
Have you tried looking at the NI License Manager? Depending on which version of LabVIEW you have, you may or may not need to activate your application builder. If you have professional, it should come with it - but all others will need to be activated. You can activate application builder, by selecting it in the tree (as pictured below) and then clicking the Activate button at the top of the screen.
Have a great day!
Janell R | Applications Engineer
Message Edited by NIJanell on 05-10-2007 03:53 PM
Attachments:
t.jpg 42 KB -
Report Generation Toolkit and Application Builder
I am going insane trying to work this out.
I am trying to build an EXE program using Application Builder. The program uses the Office Report Generation Toolkit.
I have tried including the dynamic VIs into the project, both from the Development machine and from the CD. I still have the same problem : the application does not start Excel. It is like the commands go into a black hole. There isn't even an error message.
I have attached my report VI for you to peruse. Any help is appreciated.
Brian Rose
Solved!
Go to Solution.
Attachments:
TestReport.vi 122 KBYes, Labview 8.2
Office Toolkit = 1.1.1
I have tried many combinations of what files are included, from just the top level VI, to every VI in the heirarchy tree (a major pain). I am now trying to rebuild the project from scratch and see if that does anything.
Brian Rose -
Error message in application builder in Build Application.vi
Hello,
I'm trying to make an executable file but I recive the following error message:
Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi->Dist Build LLB Image.vi->Dist Build App Image.vi->Build Application.vi
Possible reason(s):
LabVIEW: The VI is not executable.
Does anyboy know the reason for this message?
Thanks.
Javier de PablosHello Jaime,
I've tried to compile a very simple VI (there is only a while loop that executes nothing and counter is wired to an indicator.
I've attached you.) and I've got the same error. So the code or any dynamic VIs are not the problem.
I've repaired the Application Builder within Control Panel > Add and Remove programs but I haven't resolved the problem.
Javier de Pablos
Attachments:
Untitled.vi 13 KB
gg.bld 1 KB -
Since Labview ver 8.0 and later, I am not very happy with the new way the project installer is managing the additional drivers such as Serial.
With LV 7.11 the serial components was included in the cab file and was installed on the target computer in a specific directory. The size of the distribution was pretty small and well suited for compact distribution.
My LV application use only the serial object and with LV 8.21, if I include the serial 3.2 component, I get an enormus file including max, visa ... and a lot of fucky component I do not need.
To distribute my application, I just need, the runtime engine and the serial driver as it was with the version 7.XX
Looking for clever advises from you gentlemen!Thanks Dennis for you input
My problem is in fact very simple. 3 years ago, I developped a software suite for X ray generator; My company is selling such generator all over the world and our control panel software and DLL (for OEM integrator) is based on Labview professionnal development plateform.
To drive our generator, we just need to transfer ascii data using the strandard RS232 port still present on most of equipments used in the industrial area.
Until LV version 7.11, there was no problem to include serial component in my distribution with a very reasonable size and transparency for the end user.
with LV 8.xx (preparing a new release), I'm very disapointed to see, my distribution is increased of about for 10 Mo to 180 Mo just because I increase the serial component.
May I mix a previous version of the serial component with LV 8.21?
Should I change my source to Visa instruction only and merge visa runtime only to my distribution?
is there any simple serial example based on visa and distributed with th application builder?
I will appreciate your help in order to optimize my distribution
Pascal -
LV 8.6 application builder creates an empty installer
LV seems to create the installer O.K. At least there are no error messages. However, after I run the installer, the directory where the executable is supposed to be does not exist. There are no error messages when running the installer.
Nisar F wrote:
Hi earl,
I hope you are doing fine. Here is the link that tells you how to build an installer. Particularly pay attention to step 3 -5 to see if you have set up the correct settings for source file to include in installer. Hope this helps
Best regards,
And step 6 shows you how to build a shortcut.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be! -
Error 7 application builder invoke node
I get this error when I tried to build an application. "Error 7 occured at Invoke Node in Dist read linkage.vi-> Dist Cmp Settings to Disk Hier.vi-> Dist Build App Image.vi-> Build Application.vi Possible reason, LabView: File not found.....and then NI-488 Non Existent board." Anyone knows why? I was able to build application just fine last night. But then when I tried to build it this morning, that's the error that I got. Thanks.
Check the info in this link:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=50650000000800000016730000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0&USEARCHCONTEXT_QUESTION_0=Error+7&USEARCHCONTEXT_QUESTION_S=0 -
Application builder error coder 21
I get this error code when trying to build an application and include the visa runtime install files
What can i do to fix this error
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Validating...
Copying files...
Scanning files...
Updating files...
Build complete successfully.
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'LabVIEW 2009, Media 1' from: \\dtads2\it_software$\Labview 2009\DVD 1 of 2\Distributions\LabVIEW\LabVIEW2009\ to: C:\Documents and Settings\brockmaa\Desktop\11164 Carnivore\builds\FVT1_4 test\My Installer\
Copying distribution 'National Instruments Device Drivers - February 2010' from: C:\National Instruments Downloads\NI Device Drivers\Feb10\ to: C:\Documents and Settings\brockmaa\Desktop\11164 Carnivore\builds\FVT1_4 test\My Installer\
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
*** Error: An internal tool or library returned an error. (Error code -21)
Error Messages
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper32.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-ORB' not found for part 'niorbi.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-ORB {F2D3406A-0A97-4EB9-9A09-F20A874C16F9}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-ORB' not found for part 'niorbi64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-ORB {F2D3406A-0A97-4EB9-9A09-F20A874C16F9}.xml'.
*** Error Details:
Error in MDF API function: _MDFBuildDist_Build
Error List
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper32.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
While validating input parts.
and so onHi brockmaa,
It seems that the files it needs to include the VISA runtime are not being found on your system. Try re-installing the correct version of VISA you need from:
http://www.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:du,n8:3.25.123.1640,ssna...
and try to build the installer again and it should be able to find the correct files.
DylanC -
Application builder error 1041
Dear All,
I have a problem to build a application in Labview 8.5.
It's the first time that I try to build this application in fact it's the first application every I try to build.
I found the following problem.
Authentication: "Error Code Database.vi is password-protected. Enter the password to acces the block diagram."
I do not know the password for this file.
The building errors details I get are:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1041 occurred at Invoke Node in AB_Source_VI.lvclass:Apply_VI_Properties.vi->AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Incorrect password.
Method Name: Lock Stateet
When I start looking for the file that causes the problems I find that it is "Get File Type.vi" it's protected.
This is an NI file and I do not know the password and I do not know why it is locked.
The VI general properties of the file are:
C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\lvfile.llb\Get File Type.vi
File revision is 78
I tried to solve the problem as discribed in tread
http://forums.ni.com/ni/board/message?board.id=170&message.id=297099&requireLogin=False
But that did not work for me. A build with a new file also gives the same error.
So I tried something else in the Build specification there is a menu "source file settings". There is a selection about passwords
You can choose 3 settings 1) No passord change 2) Remove password 3) Apply new password. I changed this setting from 2 to 1.
And I can build the project now. So I change back from 1 to 2 and I should get the error back again. And I did not. How can this happen?
What is going on?
Thanks in advanceMike, you can't change the password if you don't know the old one. Why do you want to change the password? I do't wanna change the password. The application builder is asking for it and I do not have it. The same problem occured at thread http://forums.ni.com/ni/board/message?board.id=170&message.id=297099&requireLogin=FalseIt looks almost the same but the solutions there did not work. The problem kept occuring. So I tried someting else:
In the Build specifications there is a menu "source file settings" for your project files. I only have 1 main.vi project file
There is a selection about passwords for your source file settings. See attachment 3. You can choose 3 settings
1) No passord change
2) Remove password
3) Apply new password.
I changed this setting from 2 to 1.And I can build the project now. So problem solved.
Then I changed back from 1 to 2 and I should get the error back again. And it did not.
I do not understand why it works and I would like to.
What is going on?
Attachments:
Authentication.JPG 13 KB
VIPropertiesProtection.JPG 131 KB
SourceFileSettings.JPG 52 KB -
Application Builder: error in building DLL from a VI
I have a VI which I have been compiling into a DLL for use with Labwindows. Suddenly yesterday the build would no longer compile. Instead the error message (see attached picture) persisted all day no matter what I changed in the VI. Before the error message appeared, the Labview project window went blank for a moment, then showed some "C" code from somewhere, and then back to the project window. It's almost like something blew up in the compile process.
I've tried all suggestions in the error message. Checked data types and names. I believed the VI is wired back to where it was. There is not much to the VI but it does reference some .NET assemblies.
Thanks for any comment or help,
Doug Wendelboe
Attachments:
VI-DLL-Pictures.zip 21 KBHi Eriquito:
Thanks for your response. I've included some snapshots of appropriate Ap Builder setup pages. My DLL is named "CVIMESQueryTray.dll". I had this compiling quite well up until a few days ago, so Ap Bldr didn't object then.
See if you can spot something in my ApBuilder setup that I might be doing wrong.
Thanks for your help.
Doug Wendelboe
(Hmmm.. I guess I can't attach more than three items, so I ZIPped them into one file).
Attachments:
ApBuilderPics.zip 154 KB
ProjectFile.JPG 60 KB
ApBuilderPage1.JPG 31 KB -
Error when loading customer's application build script
I'm updating a program for a customer to include a module that we have developed. We're required to use an application builder script because of the way the VIs work.
Anyways, when I attempt to load the build script for the LabView 6.1 application, eventually an error box comes up with the following message:
Error 1 occured at Program Files:\National Instruments\LabVIEW 6.1\vi.lib\addons\_office\_wordsub.llb\_Word Dynamic VIs.vi - invalid path.
Possible Reasons:
LabVIEW: An input parameter is invalid.
or
NI-488: Command requires GPIB Controller to be Controller in Charge.
I'm confused about the Program Files:\ syntax. Is this a valid reference? I can only assume so, as I believe they used this build script in the past. I'm currently working on Win2k, and I do not know what the customer's machine is running.
Is there a particular Windows or LabView setting that would let this build script work? If not, is there an application build script editor that I can use to change the file reference?Yes it's a valid path, see attached screen cap of the exact path on my computer (except version 8.2).
It looks like the target computer is just missing the MS Office toolkit, or the installation was not Typical. Tell the user to install the toolkit in the proper directory and it should compile.
Message Edited by Broken Arrow on 06-04-2008 09:08 AM
Richard
Attachments:
forum path pic.JPG 70 KB -
My VI calls SubVIs (all with the same connections) in a loop with one 'call by reference'. It works great in the VI but when I build an Application I receive Error 1003. After that I read in the KnowledgeBase when I build the Application I must add dynamically all the SubVIs I call by reference. Works fine at the moment but the amount of the SubVIs is rising steadily (approximately 10 per week) and there are many users all over the world of this application. So it is practically impossible and very uncomfortable to build a new application everytime the amount of SubVIs rises. There must be another solution maybe some kind of initialization, adding
the paths of the dynamic called SubVIs programmatically???You do not have to include all the dynamically called subVIs in your build. If you look at the shipping example called Plug In Example, the dynamically called VsubIs are in a subfolder called plugins. In this example, the paths to the subVIs are created based on what files are present and which have the correct type specifier. The high level VI can be built into an executable. The plugins folder could also be included with one or two subVIs but once installed, new subVIs can be distributed separately and just put into the folder. The only trick is to make sure that the path to the plugins folder is correctly obtained whether the VI is run in development mode or as an exe.
-
Application builder error creating
After install Labview 9.0f2, no longer is possible to build application
Solved!
Go to Solution.Would you like us to continue guessing, or would you be capable of providing some details?
Such as what the error is?
What was the version of LabVIEW you were using?
What toolkits you are using?
Anything else you can think of?
Remember, we don't have one of those nice troubleshooting scripts that call centers have. -
Application builder default control value
I have a VI the reads a data file. When I build an application and transfer the application to another computer the default directory is no longer valid. Is there anyway to allow the user to establish a default directory for the file read on his computer or does he always have to go through multiple levels to find the file every time he restarts the application?
There is an initialization file (projectname.ini) that is created with your application (build for the application). You can define your default locations there. Note, you will need to configure the builder to use your file.
Maybe you are looking for
-
OWB 11gR2 - Internal ERROR: Can not find the ACL containter
OWB 11gR2 - Internal ERROR: Can not find the ACL containter ======================================= I am using OWB 11gR2 (11.2.0.1) on Win XP 32 bit. I have 3.23 GB RAM. OWB design center is ver slow on my desktop. We have our OWB repository is on Un
-
Using small CD-ROM's with Mac Mini
Can I insert a small or mini CD_ROM into the Mac Mini slot? I bought a USB turntable and the software for it is on a mini CD-ROM. I am worried about inserting it. Anyone know? Thanks
-
How can i get plug ins to work
hi can any body help i have a set of plug ins and i loaded them on to my lap top using windows xp and they work fine how ever if i try using them on my other lap top using vista it crashes my program of photoshop cs2 any sugestions thanks
-
How to transfer PDF files from PC to ipad2
How to transfer PDF files to iPad and view
-
I'm trying to put firefox on my ipad and I need an account number.