Creating Folder stucture Application Builder
Dear Friends,
I was intending to populate a specific folder structure inside the BUILD folder as shown in figure. But after a lots of combination unable to find what I was looking for.
Please refer the figure and do suggest me if, there is any methods / tricks to achieve my goal.
Assumptions:
All Vis Should be Always Included into the Build Specification.
All Vis contains SubVIs and Vilib Vis.
Thanks
Sri
I don't understand what you are trying to do. I think you are trying to build an Executable from a LabVIEW Project that is organized as a set of Folders inside a Top Level Folder.
If that is correct, then you should not try to replicate your folder structure in the Build! The structure of a Build is a single folder that holds the Application (the .exe file that results from compiling and linking together all of the LabVIEW VIs and support VIs referenced by your Project) and giving you a single file (My Application.exe). It also provides a few Configuration files (My Application.ini and My Application.aliases) in the same Folder, and might have a Data sub-folder where files that "need to be available", but might not be directly linked by the Builder, are located. Most of my Executables just have the three .exe, .ini, and .aliases files present.
When you build the executable on your own PC, it links to the LabVIEW library routines whose locations it already knows (they're usually in Program Files\National Instrument\LabVIEW 20xx or similarly-named folders). If you want to run this code on another PC that does not have the LabVIEW Run Time Library installed, you can create an "Installer" that will package up the additional files and create something that, when you run it, will "install" the Run Time Libraries and the Application.
I've only rarely done this (and, I confess, not recently) -- it can be a little messy. I'm not delivering to Customers, but rather providing routines to Students, so it's a little more "hands on". What I've done is to provide the Build (meaning the folder containing My Application and its supporting files), which they can copy to their PCs or just run directly from a Share, and also pointed them to an Executable that will install the appropriate LabVIEW Run Time Engine on their PC. We've "standardized" on LabVIEW 2014 (for now), so everyone has the RTE installed, and only needs to pick up the latest Executable.
Hmm, are you trying to do a Source Distribution? If I've gone off on an irrelevant tangent here, I apologize. Yes, if you are trying to distribute the Source, then you may want to keep track of the existing file structure. [How embarrassing if I've been ranting away on the wrong issue ... I'll go away, now ...]
Bob Schor
Similar Messages
-
Inifile created by the application builder
Why is an almost empty ini file (with the same name as the executable)
always created in the installation folder when installing a labview
program created with the application builder?
I want to distrubute my own inifile with the installer but it seams
that it is overwritten. I have one other file copied into the
installation folder by the installer and it is installed just fine. Any
suggestions? Do I have to change my inifile name (don´t want that)?
/ RoineHello!
Here you have some more information that you might find helpful when it comes to *.ini files and executables created in LabVIEW:
Setting LabVIEW Preferences For a Windows Executable
http://digital.ni.com/public.nsf/websearch/65f76f247012df68862562c70073be06?OpenDocument
How Do I Prevent Automatic Creation of an INI File in Windows Start Directory when I Run a LabVIEW Executable from the Same Directory?
http://digital.ni.com/public.nsf/websearch/40E442486D81582E86256D16004D5D07?OpenDocument
Will My Application's .ini File Be Overwritten When I Run My LabVIEW Stand Alone Executable?
http://digital.ni.com/public.nsf/websearch/680ADAAD4A2E97F586256DC80074B471?OpenDocument
Regards,
Jimmie A.
Applications Engineer, National Instruments
Regards,
Jimmie Adolph
Systems Engineer Manager, National Instruments Northern Region
Bring Me The Horizon - Sempiternal -
To create folder in Application server
hi,
How to create folder in application server from presentation server??
how is the program it??
reply me soon...
thx,
s.suresh.hi Suresh
Hope u r having nice day
here i am sending a sample report which can upload the file to Application Server which inturn automatically create folder .
REPORT ZSHR_UPLOAD_TO_APPLICATION .
DATA : BEGIN OF IT_MAT OCCURS 0,
MBRSH LIKE MARA-MBRSH,
MTART LIKE MARA-MTART,
MAKTX LIKE MAKT-MAKTX,
MEINS LIKE MARA-MEINS,
END OF IT_MAT.
DATA : W_DIR(40).
MOVE 'D:\usr\sap\DEV\DVEBMGS00\work\SHR' TO W_DIR.
"SHR" IS A FOLDER NAME TO BE CREATED
START-OF-SELECTION.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = 'C:\MAT.TXT'
FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = 'X'
TABLES
DATA_TAB = IT_MAT
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17.
OPEN DATASET W_DIR FOR OUTPUT IN TEXT MODE ENCODING UTF-8.
IF SY-SUBRC EQ 0.
LOOP AT IT_MAT.
TRANSFER IT_MAT TO W_DIR.
ENDLOOP.
ENDIF.
CLOSE DATASET W_DIR.
IF USEFUL AWARD POINTS.
REGARDS
HEMASEKHARA REDDY S -
After installing an application that was created using the Application Builder
After installing an application that I created using the Application Builder I get this error if I try to run " ANY " LabVIEW App's that I have built. "Executable Version 7.1.1 doesn't match Resource File 7.1. Check your configuration."
The way that I tried to fix this is to reload LabVIEW 7.1 and DAQmx 8.0. I am using two NI-6528 switch cards.
After I reload LabVIEW and DAQmx I can run my applications but as soon as I install one on this development machine the error begins again.
The executable that I built works fine on the development machine and any other machine that I try it on but it appears that the Run-Time engine 7.1 becomes corrupt after I run setup.exe for the newly created application.
I have built numerous Installers, setup.exe's in the past without this error. Just this latest one caused this problem to start.
I can NOT upgrade to 7.1.1. I am doing work for many different sections of this factory and I can not force them to upgrade. I've asked. Others supply code for the same machines using LabVIEW 7.1.
I am stuck creating executables and manualing moving the correct files to the target machines.
What can be done?No. The KB article was talking about a machine with 7.1.1 installed. I have LabVIEW 7.1 installed.
The machine that I am having trouble with is my development machine. LabVIEW 7.1, DAQmx 8.0.
If I build the executable all is fine. I can still run old executables including the one I just built.
If I create the installer all is fine. I can still run old executables including the one I just built.
When I install the app on my development machine the corruption occurs. I can " NOT " run old executables including the one I just built. The subject error pops up.
I have not moved any executables to the other machines yet. I don't want to corrupt others. -
Folder of application builder(*.exe) with run-time DLL
My application consists of main.vi, subvi folder, and example folder.
In addition, I have to add the run-time libraries for add-on tool kit (advanced signal processing, lvwa.dll) which should be located in the root folder.
(For exe application, can I set the location of DLLs to not the root folder but "DLL folder"?)
In my several trials, I can't maintain the hierachy of "example folder".
Instead of my intension, the NI application builder copied the files in the folder to the support directory.
Can I locate the "example folder" to the root folder by using NI application builder?
In summary, I want to get the folder structure by application builder.
main.exe, DLL folder, Example Folder.
메시지가 08-08-2008 01:30 AM에 labmaster에 의해 편집되었음Hey Labmaster,
What version of LabVIEW are you using?
I am not too clear as to what you are trying to do. You can create folders and add anything from your project when creating an installer under the Source Files section in its properties.
It might be easier if you'd attach a screen shot of what you are doing or trying to do.
Aashish M
Applications Engineer
National Instruments
http://www.ni.com/support/ -
I need to include a procedure in a dll that is non-blocking, i.e. it should return immediately after the procedure has been called, and not return after its processes are completed.
The procedure is a LabView 7.0 VI, and the dll is being created using the Application Builder. Currently the procedure completes its desired task and then returns, but I would like the function to return immediately. Thanks for your help!Rischaard,
I don't know if that will work in a dll, however as an idea:
use the vi-server functions:
Your dll-procedure opens a OwnTreat.vi(wich will do the work) with vi-server, and run it without waiting for completion.
First thing OwnTreat.vi should do is opening (with vi-server) a reference to itself (So your caller dll can close without stopping the OwnTreat.vi)
Then OwnTreat.vi con do what YOU want. When finished close the self-reference
Maybe you need a short wait or a feedback to make sure that OwnTreat has opened his own reverence before your dll stops.
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ' -
What are the options in the application builder application.ini file
What are the options that I can add in the application.ini file that is created by the application builder.
They are about the same as LabVIEW.ini. Scott Hannahs has a list of ini settings for several versions of LabVIEW that can be found here.
-
Application builder distribution rights
Hi,
Could someone please clarify the rights we have with regard to distribution
of executables created with the application builder. I bought the
application builder because its sales pitch was "you can freely create
executables and distribute them". Upon receiving the software, (app
builder) i read the software license agreement and found that you are free
to distribute the executables except when you are using it for: data
acquisition, analysis, a user interface (strip charts, gauges, meters etc)
and a host of other restrictions.
I can not actually think of any application that does not use at least one,
if not all of the above.
This seems ridiculous, since I have bought $1700 worth of software that does
exac
tly what I want, technically, but prevents me from ever using it
legally. (at least as I have understood the software agreement)
Just what is the go?
EasilyConfusedJohn-
I've had the same questions lately and the feedback that I got from a
NI salesperson was that you can distribute the executibles and labview
runtime to any machine that you wish. To do the data acqusition, you
have to install NI-DAQ, but that license will come with the DAQ card
that you will have to purchase from the machine.
Hope this helps...
In article ,
"John Cronin" wrote:
> Hi,
>
> Could someone please clarify the rights we have with regard to
distribution
> of executables created with the application builder. I bought the
> application builder because its sales pitch was "you can freely create
> executables and distribute them". Upon receiving the software
, (app
> builder) i read the software license agreement and found that you are
free
> to distribute the executables except when you are using it for: data
> acquisition, analysis, a user interface (strip charts, gauges, meters
etc)
> and a host of other restrictions.
> I can not actually think of any application that does not use at
least one,
> if not all of the above.
> This seems ridiculous, since I have bought $1700 worth of software
that does
> exactly what I want, technically, but prevents me from ever using it
> legally. (at least as I have understood the software agreement)
>
> Just what is the go?
>
> EasilyConfused
>
>
Sent via Deja.com http://www.deja.com/
Before you buy. -
I am having an issue with an installer which I created with the Application Builder. I have a project that I have successfully deployed. Subsequently I created another project (and vi) which is based on a copy of the originals, both with new file names. In the renamed project file, I changed all file names, paths, and all resources, to reflect the new names. I also changed the installer’s destination and install folders, of course. I reset the executable’s version number (in the Build Specification properties) to 1.0 (the original was 1.3). I then successfully built an executable and the application installer. However, when I run the installer (setup.exe), it gives a dialog (after the license screen) that it “Cannot install” because a “higher version already installed”.
I’ve done exactly the same thing with other vi’s and projects of mine, and never had this issue. The installer correctly installs the newly created (and renamed) version where it is told to in the project file. Also, I’ve never had a problem deploying (installing) on my development PC either.
I have carefully checked and rechecked to make sure there is no reference to the original executable or paths. What could be causing this behavior? I want to keep the two projects completely separate, so simply changing the version to higher than 1.3 is not an acceptable solution.
Thanks to anyone in advance for any help and suggestions.
EdYes, LV 8.5 does NOT give me control over the GUID. In the project file there are three such strings:
"App_applicationGUID"
"App_INI_aliasGUID"
"App_INI_GUID"
They all have different numbers and none of them match the GUID or PackageGUID in setup.ini. I don't know if they are related or not, but usually it's not a good idea to mess with (manually edit) files like these (project, ini, etc.) unless you know what you are doing. (For example, I do edit the setup.ini file to change some of the [Dialogs] parameters, but that is based on direction from NI support.)
Anyway, like I said, I've made copies of projects before and never ran into this problem. At least I have a solution, however laborious, in creating a new project file from scratch.
Let me know if anyone has more thoughts on this.
Ed -
DeploymentException: Unable to create folder
Hello,
i'm developing some enterprise service on a NetWeaver CE SP1 plattform and sometimes while deploying i encounter a DeploymentException: Unable to create folder. Whats the reason for this exception?
I can only resolve it with restarting the server and deploy the projects again...
regards,
Matthias
1. Exception has been returned while the '<application>_start_ccbpmear' was starting. Warning/Exception :
Error occurred while starting application <application>_start_ccbpmear and wait.
Reason: Clusterwide exception: server ID 14616650:com.sap.engine.services.deploy.container.DeploymentException: Unable to create folder <root>\<application>_start_ccbpmear\EJBContainer\applicationjars
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:880)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.makeStartInitially(ContainerInterfaceImpl.java:758)
at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:181)
at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:143)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:393)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:428)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:416)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:170)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:393)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:418)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:318)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:533)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:230)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:374)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2955)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2885)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2861)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:646)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:637)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:488)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:209)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:154)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:61)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:36)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:882)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:52)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:287)
Caused by: com.sap.engine.services.ejb3.container.ActionException: Unable to create folder <root>\<application>_start_ccbpmear\EJBContainer\applicationjars
at com.sap.engine.services.ejb3.container.FSMakeFolder.perform(FSMakeFolder.java:48)
at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:874)
... 37 moreHi,
This usually happens when the undeployment is not done properly. Alternatively, you can undeploy the application through SDM and then deploy it again to solve this problem.
Thanks,
S-B -
Can I include raw files into the installer folder with LV application builder?
Hello,
I have created a batch file that will run at the end of the installer, which will copy over some raw configuration files into the source destination so that the configuration files can be customized for each end user without rebuilding the installer with application builder. I also have an autorun.inf so the installer will automatically run when the user installs the CD.
However I would like to have some default configuration files and an autorun.inf file that will be automatically added to the installer "volume" folder using the application builder.
However I don't see a way to include raw files in the "volume" folder. It appears all source files in the application builder are embedded into the binary files.
Please let me know if this is possible with the current application builder.
Regards,
Russell
Engineering Team Leader
G Systems, www.gsystems.com
Certified LabVIEW Architect
Certified Professional InstructorRussel,
i think this link might give you some good hints....
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it. -
LV8 Application Builder Folder Structure
I have a folder structure in my development environment.
When I build an application, using the application builder, I want to get the same folder structure.
Example:
I have folders ..Application\Drivers\DMM\Agilent 34401 and ..Application\Drivers\DMM\Fluke 45.
There are subfolders containing VI:s in each folder (..Application\Drivers\DMM\Agilent 34401\Subs\sub.vi)
In the application builder I add ..Application\Drivers to "Dynamic VIs and Support Files".
I create a new "Destination".
Now all vi:s from ..Application\Drivers goes to this folder, not to subfolders.
Is it possible to get a folder structure?
Staffan Ekstrom
Sony Ericsson Mobile Communications AB
Lund, SwedenHi Staffan,
When you build an application all of the VI:s will be integrated in an .exe file. The reason for this is that the user of your program not shall be able to do changes in the source code.
When adding files to the "Dynamic VIs and Support Files" these files are for example help files that you want the program to find no matter where you install your program on the computer. Before adding files to this you need to build the relative path in the program using strip path.vi and build path.vi.
Dynamic VI:s are not the same as sub VI:s.
The short answer to your question is no, there is not possible to get a file and folder structure when building an application.
Regards,
Andreas E
Applications Engineer
National Instruments -
Creating a folder in application server in background.
Hi experts,
Is it possible to Creating a folder in application server in background.?
My requirement is like this , every time a PO is created it has to be saved locally.
When atlast i manged to do this, i get stuck again by this CR ,
The PO has to be saved in a folder with the same name as PO number,
I do not know if it is possible.
So as always I am looking for inputs/suggestions or knowledge if you had come across scenario like this one.
Thanks and Regards,
KHi,
You could create a system command in SM69 to create a directory and then use the function module SXPG_CALL_SYSTEM to invoke the command and pass in the directory name as a parameter at run time.
Darren -
Is it possible to embed DAQmx in Installer(created by Application Builder)?
The good thing of Installer (created by application Builder) is that it also integrates LabView Runtime Engine along with supports like Serial port support, Port I/O support etc. Due to which one can install the application developed by Labview on any system wheather that contains Labview or not, as the engine required by that application also gets installed.
But problem with my application is that it uses DAQmx related stuff, so I have to install DAQmx 8.0 prior to running my application installer on any system. Is it possible that the DAQmx related stuff required by my application also gets install through same installer as it installs LabView Runtime Engine, so that the distribution of my application donot require the complete installation of DAQmx.You need to use LV 8.0. You can add NIDAQ to your installer in LV 8.0. In previous versions I do not think it is possible.
see: http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
Matt
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison -
I'm looking for a solution of the following problem.
The DLL created by the "sum1.vi" source works properly, while the DLL create by "sum2.vi" always gives a zero result.
The "sum2.vi" source contains an additional "Hanning Window" VI (not wired), that seems to be the cause of the problem.
If I delete the Hanning VI and re-build the DLL, the same works fine
Is there a solution or is it not possible to make Labview DLLs when containing analysis VIs as filters, windows, FFTs, and so on?
Thank you for your answers.
N. Roberto
Attachments:
sum1.vi 12 KB
sum2.vi 14 KBRoberto N. wrote:
Thank you Jordan, I'm using Labview 7.1.
Anyway I've resolved the problem by adding the "lvanlys.dll" file (present in "..\Labview 7.1\resource\lvanlys.dll" path) as support file in the building process. Now the DLL containing the analysis functions works correctly.
Natalino Roberto
Ok, you probably got lucky since the lvanlys.dll seems to implement that function directly. However most Advanced Analysis functions are just redirected by lvanlys.dll to the Intel Math Kerneal Library that gets installed with LabVIEW 7.1 and higher. The only way to get that properly installed with your LabVIEW executable or DLL is to create a LabVIEW installer in your Application Builder and make sure to select under "Installer Settings->Advanced" the "LabVIEW Run-Time Engine" and the "Analyze VIs Support". Then use that installer to install your DLL on another computer.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions
Maybe you are looking for
-
How can i pass a value in array into .setText()?
i want to display a value in an array into a JTextField. May i know how to do it? eg: JTextField UserName; UserName.setText(s); but it doesn't display the value into the JTextfield.
-
I just updated to FireFox v3.6.8, after using v3.5 successfully for many months. With the new version I keep getting error messages that a script "may have stopped responding", The script in question is "contentAreaUtils.js". My OS is Win2k SP4, with
-
Problems with a certain program for existing users
Hello, We have problems with a third party software application. We have installed this software program on a terminal server (server 2003 32bit) and when we open this software with a existing user account the application crashes with the following e
-
Is there any way to enable SSH via Terminal in the OSX Installer utility list?
Hi guys, I've messed up my install a little on my internal HDD.. I can't boot into OSX as I keep getting kernel panics on boot. I was just wondering if there's any way I can SSH into my Mac Pro via the Terminal on the OSX Installer Utilities list.. I
-
Re: Bluetooth connection to Desktop Version 6.....
Hi, Any update on your problem ? I am also facing the same and suprise no post since 2010.