How to run Matlab Standalone Application .exe file on Windows XP? - matlab

I have a computer at work, and it does have Windows XP 32-bit OS and no Matlab.
And I wrote a code on Matlab on different computer(Windows-10 64-bit OS), and made a standalone application using Matlab's Application Compiler.
I got an .exe file for my program. I tried to run .exe file on Windows XP computer, but it gave an "invalid machine" error( I don't know what that means.)
Is there any way I can run this standalone application .exe on Windows XP? Is it because of 32-bit situation, or because of Windows XP?
And one last question, if I can't run .exe on Windows XP, to which program language should I convert my code? So I can run program on Windows XP 32-bit, Windows XP 64-bit, or for example Vista,Ubuntu etc.
Actually, which program language is compatible with all OS platforms? Is python compatible?
Thank you for reading, hope I did not take your time. Thanks in advance.

Related

C + + Builder 10.4.1 compiler running error in XP

Link with Dynamic RTL=true
Compiler running under XP prompt error
Unable to locate the program input point acquiresrwlockshared on the dynamic link library kernel32.dll.
AcquireSRWLockShared() was introduced in Windows Vista. Clearly something in your project is static-linking to that function, so the error message makes sense when running your code on XP. Note also that you enabled the Dynamic RTL, but you did not also enable the Delphi Runtime Library, too. Typically, most C++Builder users disable these options to produce standalone executables, but you seem to want to enable them instead to utilize runtime BPLs (which will still fail to load on XP btw, even if your main EXE could run).
XP is no longer a supported platform. You can't run the IDE itself on XP, nor can you run programs compiled with 10.4 on XP. The IDE itself requires Windows 10 or later. Compiled programs require Windows 7 SP1 or later. See Operating System Requirements in 10.4's documentation.
The last version to officially support compiled programs running on XP was XE2. Support for XP was dropped in XE3.

Running 64-bit Windows and Linux in 32-bit mode

I need to test my C code for 32- and 64-bit versions of Windows (XP and 7) and Linux. But I have got access only to their 64-bit installations.
Question: Is it possible to use some boot-time settings or other hacks to run/emulate these OSes in 32-bit mode? If not, is there any other way to test the portability of my C code?
Note: The C code in question is not a full-fledged application but rather a .dll/.so file.
Neither Linux nor Windows 64Bit can run as 32Bit OS. Also, while you can run 32Bit executables on the 64Bit OS, it is not quite the same as running the same under a 32Bit OS. But it might work as a quick screening test. Besides, you certainly want that to work as well, right?
Your choices are full multi-boot setup, using VMs (might hide/expose bugs), being content with the emulation layer or running the other OS's on different hardware.
BTW: If you have Windows 64Bit, the license allows you to run 32Bit instead and vice versa. Anyway, you might want to check different language versions as well...

My app created on XP does not run on Windows 7

I am trying to run an app I created at work (I sent myself the .exe file) so that I could see how it looks on Windows 7.
My laptop (running 64-bit Windows 7) won't even open it, though. It opens some compatibility wizard to try to rectify whatever the problem is, but that doesn't work either.
Is there anything I need besides the .exe itself, that I should have copied over?
A team member using Windows 7 can run it (by checking it out of Subversion and running it in the VS IDE, anyway), but the display if "off" (The FlowLayoutPanel's controls are experiencing a kind of "wardrobe malfunction"). But I, as mentioned, can't even run it.
What might be the problem/solution?
If you are running the Professional edition of Windows 7 or higher then it will include the option to install the "Windows XP Virtual Machine". You can then run your app as normal under the virtual machine, quckest and easiest way to resolve these sort of issues in Windows 7.

How can I install, or run, a Mac-version of MATLAB on Parallels' virtual Windows platform?

Adam Lewis answered, "I have switched to running Matlab on Parallels Desktop on my 2008 Mac Book Pro and have Zero issues". I have been unable to get a Mac-version of MATLAB v.7x to either install, or to run as a Mac program within Windows, on Parallels v7 virtual Windows7Prof, on my 13" MacBook Air.
Does it require a PC-version of MATLAB for the virtual machine?
Yes, it requires a Windows version.
If you install any software on a Virtual Machine, that software needs to be compatible with the guest OS (Windows in this case).
A virtual machine is exactly what it says: a virtual machine. So for any software, it will seem as if it's running on a real machine with that configuration (OS, CPU, RAM, ...). It doesn't really matter what the host machine is: that could be a Windows, Mac or Linux host or even your toaster.
Yes, if you plan to run MATLAB on a Windows virtual machine, you need the Windows version of MATLAB.
... But consult a local expert for help. Installing the Mac version of MATLAB should be effortless.

Compiled perl executable fails to run on Windows 7 (64 bit)

I have created an executable (.exe) of a perl script on a 64-bit linux kernel. It executes correctly in this environment.
When the executable is run in 64-bit Windows 7, the following error message is displayed:
The version of this file is not compatible with the version of Windows
you're running. Check your computer's system information to see
whether you need x86 (32-bit) or x64 (64-bit) version of the program,
and then contact the software publisher.
Given that the source and destination OS's were both 64-bit, I'm not sure that the architecture of the build is the issue. Are there any special considerations to make a compiled perl program execute properly in Windows? Thank you.
Executable files are not compatible across platforms. They will run on the original platform only unless they are explicitly cross-compiled to a different target. That's actually the reason we use interpreted languages. What you want to do is not possible because the Windows and Linux APIs, libraries, and well just about everything are completely different.
This is why you need to download a different version of a program for linux/windows/mac.