RTE LV17 64bit on Windows10 Home 64bit don't work:

[Marinica]

I built an application and an installer in LV2017 (64bit) on a PC with Windows 7 Pro 64bit.
I installed the application on a Windows10 Home tablet (64bit).
When I try to launch the application I get an error window:

"MyHOMEalarm.exe- Entry Pointing Not Found
The procedure entry point BaseReleaseProcessExePath culd not be
Located in the dynamic link library C: \ ProgramFiles \ BETA \ Alarm \ data \ kernel32.dll. "

After clicking OK, the front panel with the broken arrow appears and a new window with the message:

"Missing external function kernel32.dll: GetSystemPowerStatusC in VI Alarma.vi"

What can I do?

[Bob_Schor]

---

@Marinica wrote:

What can I do?

---

Attach your VI(s) and let us take a look to find the flaw.

Bob Schor

[Marinica]

Attached is all the compressed project.

It was developed on Windows10 Professional 64bit machine and under LV2017 64bit.

I need to run the application on a 64-bit Windows10 machine

[Marinica]

Into the same project are two others simple applications build that work very well on target machine:

CheckCOM

DefaultDirectory

The main application is Alarma.vi but it works using two additional hardware device:

-BMS1040 - is an acquisition and programmable controller 16inputs, 4outputs. It communicate using RS485 and ModbusRTU protocol.

-USR-GPRS-410 is an GPRS server able to send SMS to a mobile phone

[dkfire]

---

@Marinica wrote:

I built an application and an installer in LV2017 (64bit) on a PC with Windows 7 Pro 64bit.
I installed the application on a Windows10 Home tablet (64bit).
When I try to launch the application I get an error window:

"MyHOMEalarm.exe- Entry Pointing Not Found
The procedure entry point BaseReleaseProcessExePath culd not be
Located in the dynamic link library C: \ ProgramFiles \ BETA \ Alarm \ data \ kernel32.dll. "

After clicking OK, the front panel with the broken arrow appears and a new window with the message:

"Missing external function kernel32.dll: GetSystemPowerStatusC in VI Alarma.vi"

What can I do?

---

Are you trying to run your exe on a tablet? 

If yes, what processor has this tablet? 

[Marinica]

The tablet is ASUS T101HA,

Processor: Intel Atom x5-Z8350 CPU @ 1.44GHz

RAM: 2GB (1.83GB usable)

[Marinica]

On the other hand, I installed and run another two applications, of which one also used the RS485 communication.
The tablet does not have a native serial port, but I used an USB-RS485 adapter cable from FTDI. The drivers have been installed very well and the small test application communicates excellently with my hardware device.

[dkfire]

Are the two application that you have run on the tablet also LabVIEW builds ?

[altenbach]

Does the application work correctly if you run in on a windows machine that is not a tablet?

(I assume things would work correctly if you disable that loop where you call the dll).

Why are you including kernel32.dll with the installation?

Have you tried using LabVIEW 32bit instead? (LabVIEW 64bit is an unusual choice for something like this. What was the reason for the decision?)

[Marinica]

Sorry for the delay.
I was on vacation.

I used LV64b because the laptop I developed was 64b (W7-64b) and I installed LV64b. The target machine runs W10-64b, so I did not get tired of trying 32b.

But now I will, let's see what happens