06-15-2010 04:04 AM
Hello Labview Community,
I get the following message when trying to start a LabVIEW based software:
Details:
Executable and Installer are created with LabVIEW 8.5.1 Development System
The software is installed multiple times from the same source (CD-Roms are burned from a kind of image-file) without problems.
The Installer was created from the LabVIEW Project-Explorer
Only additional Installer (besides the 8.5.1 runtime) is "NI Datasocket 4.7.2"
Our customers intall the hardware and software on their own (worldwide!).
This is the first time the software doesn't start.
The only difference to the other installations I can see is the arabic language support of the operating system (Win XP english)
Any hints are appreciated.
Best Regards,
Rainer Balzerowski
06-15-2010 04:38 AM
06-15-2010 05:01 AM - edited 06-15-2010 05:02 AM
Nope!
200A340 != 2002200
(additional Installer included here)
The problem may be the same, but who knows.
06-15-2010 08:55 AM
Balze wrote:Nope!
200A340 != 2002200
(additional Installer included here)
The problem may be the same, but who knows.
It's the same issue, even if you have a separate error code. The better approach would have been to add a message to your original thread indicating the different error code.
For all: comments should be posted in the other thread to keep the discussion in one place.
06-15-2010 09:44 AM
It's the same issue?
Are we going to collect all error codes in one thread?
Sorry I don't agree with you.
If there's a solution to one of these problems and this solution fits to the other problem I will for sure link the solution thread to the other one.
For all: If you've got any information regarding error code 200A340 please post it here. The other thread regarding an error code based on arabic language support is linked to this thread now aswell.
06-24-2010 03:27 AM
Hi Balze,
is it possible for you to give us a simple example, so we can reproduce this on a machine using arabic language support. maybe this would be a good way to understand what's going and to figure out if both problems are the same or not 🙂
thanks CMW
07-19-2010 05:10 AM - edited 07-19-2010 05:14 AM
CMW,
thank you for your reply. Sorry for my late respone. (Somehow I managed to diasable the email notification 😞 )
Sad but true it seems to be not that easy. I'm in contact with a customer in Qatar.
This guy is willing and smart enough to help us finding our problem.
He installed several testapplications, but is off for vacation now.
Before he left for vacation we had a littel success. His issue seems to be a problem with vi filenames.
As I'm german we sometimes have special characters in our filenames. (Like ä,ö,ü,ß)
We tried to avoid using them, but obviously it didn't work perfekt.
When he's back from vacation, we will test further on. When I'm sure this is the reason I will post this here !
The other error code may be caused by filenames too. I'll check this later.
It's not that easy because there is nearly NO support from our customer.
He wasn't able to tell me which OS is used till now (No feedback -> It seems the customer is very happy with our software 🙂 damned, no he can't)
Best regards, Rainer
11-15-2010 08:46 AM - edited 11-15-2010 08:50 AM
I have installed two different versions of LabVIEW on my Laptop, LV 2009 - 32 bit and LV 2010 - 32 bit (as evalution - for testing) and the OS is Win7 - 64 bit
I have a problem with LV2010. In LV2010 when I choose secound keyboard language by pressing left Alt+Shift (Arabic) and type in string boxes such String Controls, Labels, Captions, VI's Run-Time name (Windows title) and so on, LabVIEW has show all characters illegaly. Specially when using Application Font or System Font or Dialog Font. While Windows titles, Case Structure's name and so on using these fonts as default. Take a look at pictures. There is not such problem in LV2009. It seems that is because of installing two versions on a computer. Is there any way to fix it?
11-17-2010 12:44 AM
Any suggestions ??
07-14-2011 04:05 AM
The solution can be found here:
Best regards,
Balze
P.S.:
@smercurio_fc and muks : You were right, shame on me