LabVIEW program use administrator rights

[Wiebe@CARYA]

H,


Why are you using CreateProcessWithLogonW? Why not CreateProcessWithLogonA. You can put the LabVIEW strings directly in them. You can skip the ascii to unicode conversion.


Don't know if it will work, but it usually does.


Regards,


Wiebe.
"Dynamik" <x@no.email> wrote in message news:1144082432286-346719@exchange.ni.com...
Attaching [tested] Launcher2_1.vi -&nbsp;with much egg-on-face.
2_1. actually uses the Command-line parameter.
Excuse: This VI went through many revs before&nbsp;Launcher2.vi went&nbsp;into production app.&nbsp; A nice, general-purpose version that accommodates empty-string arguments&nbsp;seems to complicate matters, as&nbsp;arguments passed to CLF change.
Non-empty strings require array-inputs, and empty strings require U32 inputs set to zero&nbsp;(null pointer.)(?)
&nbsp;
Apologies, Conseils!
&nbsp;
Message Edited by Dynamik on 04-02-2006 05:12 PMMessage Edited by Dynamik on 04-02-2006 05:13 PM



Launcher2_1.vi:
http://forums.ni.com/attachments/ni/170/177256/1/Launcher2_1.vi

[rolfk]

---

@Dynamik wrote:

Hi Jim, Conseils,

      Please consider using the attached Launcher2.vi  It closes thread and process handles associated with call, allowing Launcher2.vi to be calleded multiple times without incurring a memory leak.

Cheers.

---

I see you have gotten a very proficient Windows API/Call Library Node programmer. 😉

The only comment I have is that your way of ASCII->Unicode translation is rather brute force. It will only work for US american code pages without real problems. Already some European code pages and the according special chracters used in the strings will create invalid Unicode characters.

As Wiebe has pointed out using the ANSI function may simplify the code a bit. Otherwise you really should consider using the MultiByteStringToWideChar API to do the translation properly.

Rolf Kalbermatter

Message Edited by rolfk on 04-05-2006 10:25 AM

[Conseils]

Thanks for pointing out the code page handling concerns; as I am certain to come accross this in the inteded application. All those funny little dots and accents sat on the top of letters...... always cause me problems, when I am coding for something as well. I have some time in hand yet before implementation, but I know it's coming hence I am so pleased that someone offered a solution and just as pleased that it's being peer reviewed. For any code to withstand the scrutiny of a peer review like this is pretty daunting but I am really pleased that the code is there. I would probably have had very many frustrating hours bashing my head against a brick wall on this one.

Handling a code page is, I hope , well within my scope.... messing about within API's is also within my scope; I place it at the same pain level as having my wisdom teeth removed without anasthetic, possibly necessary, eventually beneficial but better to regularly visit a good Dentist first. Much less trouble in the long run.....(read Dentits as Dynamik and yourselves here for contributing). Thanks.

[Dynamik]

Hi Guys,

      Thank you for the "proficient" plug, Rolf!    ... though I'm not sure that "knowing enough to be dangerous" qualifies me as "proficient".

re: "brute force" - have to admit that All Unicode is Greek to me. 

re: CreateProcessWithLogonA - what API DLL would I find that in?

Cheers. 

---

@rolfk wrote:

---

@Dynamik wrote:

Hi Jim, Conseils,

      Please consider using the attached Launcher2.vi  It closes thread and process handles associated with call, allowing Launcher2.vi to be calleded multiple times without incurring a memory leak.

Cheers.

---

I see you have gotten a very proficient Windows API/Call Library Node programmer. 😉

The only comment I have is that your way of ASCII->Unicode translation is rather brute force. It will only work for US american code pages without real problems. Already some European code pages and the according special chracters used in the strings will create invalid Unicode characters.

As Wiebe has pointed out using the ANSI function may simplify the code a bit. Otherwise you really should consider using the MultiByteStringToWideChar API to do the translation properly.

Rolf Kalbermatter

Message Edited by rolfk on 04-05-2006 10:25 AM

---

Message Edited by Dynamik on 04-13-2006 07:53 PM

[rolfk]

---

@Dynamik wrote:

re: "brute force" - have to admit that All Unicode is Greek to me. 

re: CreateProcessWithLogonA - what API DLL would I find that in?

---

Hmm, you don't have to understand Unicode to use it . Just get familiar with WideCharToMultiByte and MultiByteToWideChar and you are completely fine

CreateProcessWithLogonA: Mmmh, when writing this I was wondering if this might be one of those APIs introduced with W2K or later and therefore without ANSII counterpart, but I was to lazy to check and usually Microsoft does not name those functions with a W ending. But it seems this one is such a beast. Sorry about that.

Rolf Kalbermatter

PS: There is a post here on the boards with a VI library attachment that does the Unicode <-> ANSII translation using above mentioned functions (thus Windows only).

Message Edited by rolfk on 04-14-2006 11:28 AM

[Garyeh]

Hello,

Do you guys know how to programmatically get the User Privileges from the OS at Runtime.

Thanks and Best Regards,

Gary

[Ankita]

HI,

See this KB for more information on checking user privileges.

Ankita

[PaulieG]

Please allow me to ask this seemingly dumb question :).

Why does one need Admin rights to run LabVIEW Runtime anyways? prior to 2020, we didnt need this. 

we have multiple users who are using LabVIEW RTE for years, and our company policy has always been NOT to allow elevated rights to regular users.

With the change in LabVIEW 2020, we're having to jump through hoops to get it working on a regular account. Not ideal at all.

Wish this would be reversed again to regular accounts being able to run LabVIEW RTE again..

[rolfk]

The LabVIEW runtime does not need administrative rights as far as I can tell here. It must be something your programs try to do that requires this.

What doesn't work for you without administrative rights?

[PaulieG]

Hi Rolf, 

after installing Labview Runtime 2020, when i start the application under a regular user account, it prompts me to provide Admin credentials. we've tried using iCACLS to setup specific access to the program folder and subfolders, but to no avail.

are we doing something wrong in the installation process you think?