Moving Labview app from an Old PC to a new one

[as1564]

Hi all!

I am moving a Labview app (I do not have the source code just the executable file and its folders) which runs in LabView Run Time 7.1 to a new PC with windows 10. I have attached a photo of the NI MAX configuration of the OLD PC which shows the software installed. I downloded the same version for most of the software, but I had to upgrade to NI MAX 2024 and VISA 2024 because I was having some issues with them which now are fixed.
Now when I run the labview app it starts the test as normally but after a few seconds I am getting Error - 1073807343. As per the following link (https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9IASA0&l=en-US) I believe the issue is arising because in the Old PC the ports name were COM1 and LPT1 but now in the new PC the port names are COM1 and, if I am not mistaken, LPT1 is splitted in COM2 and COM5 because I am using a 2-port Universal PCI board (https://www.moxa.com/en/products/industrial-edge-connectivity/multiport-serial-boards/pcie-upci-pci-... which was not necessary in the old PC.

Is it possible to rename COM2 and COM5 as LPT1 in order for the VISA to recognize it as in the old PC? Or what else could be done to fix this issue?

Also, do you believe there might be some additional issues that may be causing the error?

I appreciate any help you can give! Thanks!

[as1564]

I will add the referenced links here because there is a problem with them in the OP:

Error - 1073807343: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9IASA0&l=en-US

2-port Universal PCI board: https://www.moxa.com/en/products/industrial-edge-connectivity/multiport-serial-boards/pcie-upci-pci-...

[ZYOng]

Running Executables or Installers on Different Windows Versions

Installers and executables are only guaranteed to work on the operating system they are built on.  For example, a Windows 10 installer or executable may not work as expected on a different Windows version (e.g. Windows XP, Windows 8, or Windows 7).

I would recommend you reach out the developer for the source code or ask them to rebuilt the exe.

[mcduff]

Are you sure its LabVIEW or is it LabWindows/CVI?

You don't have the 7.1 LabVIEW Runtime in the new computer; I have no idea how the program would even load without it. But you seem to have LabWindows/CVI on both computers.

[UliB]

---

@mcduff wrote:

Are you sure its LabVIEW or is it LabWindows/CVI?

You don't have the 7.1 LabVIEW Runtime in the new computer; I have no idea how the program would even load without it. But you seem to have LabWindows/CVI on both computers.

---

The icon of the error dialog is a LabVIEW icon.

I believe in the days of LabVIEW 7 it was possible to place some .dll files from the runtime-engine next to the executable (without installing the runtime-engine in the system) and it worked. But I'm not really sure about that.

[LLindenbauer]

---

@as1564 wrote:

[...]

I believe the issue is arising because in the Old PC the ports name were COM1 and LPT1 but now in the new PC the port names are COM1 and, if I am not mistaken, LPT1 is splitted in COM2 and COM5 because I am using a 2-port Universal PCI board ... which was not necessary in the old PC.

That sounds like a serious issue. Can you get into more detail on what devices were connected to each other, in which way? Splitting a parallel port into two serial ports sounds like some serious custom-built equipment was used.

Is it possible to rename COM2 and COM5 as LPT1 in order for the VISA to recognize it as in the old PC? Or what else could be done to fix this issue?

Also, do you believe there might be some additional issues that may be causing the error?

---

I would not be optimistic at all to such a thing being possible. Even if it were, your program would need to understand how it should handle the split.

If you did not use custom hardware and signal mangling, the solution might be something very simple.

If you did, it might be easier to rewrite the code.

[as1564]

I still have LabVIEW Runtime 7.1 installed, but when I upgraded NI MAX to the latest version, LabVIEW 2024 was also installed. For some reason, the old version of LabVIEW no longer appears in the list of software but I still have it

[as1564 · Accepted solution]

Thanks everybody for your replies. The issue is already resolved. I needed to match not just the aliases but also the resource names. With that done, the app runs with no problems.