I am new to Unity and from my PC (MAC) i have created 3 builds of my project (1-MAC, 2-Windows x86_64, 3-WebGL)
I state that my version of Unity Hub is 2.4.2 and my Unity version is 2019.4.18f1
When i start my game on mac everything works fine (obviously starting the build for mac), later I put the x86_64 windows build in a compressed folder and then transferred it into a USB, to try the game from another pc (win 10 PRO). In this PC the same version of unity was already present.
So far, so good.
The problem starts when I take the same USB with the same files, which, as previously said on win10 pro work, I put them on a win10 home (32 bit) and when I try to start the .exe it gives me this error "This app can't run on your PC. To find a version for your PC, check with the software publisher "
Looking on the internet I tried to get around the problem they change the local settings policy, but the result is the same :(
These are the files inside my compressed folder
And these are my build settings
I thank whoever will be able to help me and I apologize for my bad English
You say your other PC is 32 bit!
That's your issue!
You are building for the Architecture
x86_64 => 64-bit CPU
It does not mean 32 or 64 bit.
To run it on a 32 bit system you have to build for x86 instead.
See Unity Manual - PC, Mac & Linux Standalone build settings
Related
I've build aosp_x86_64-eng target on Linux and now I can start it using emulator command. However, I'm looking for a way to "deploy" the .img files and whatever is necessary to Windows, so I could run the same emulator on Windows.
My main problem is that in out directory (out/target/product/generic_x86_64) there are a lot of things and I'm not sure which to choose and how to glue them with .ini and .prop files. I also didn't find any working tutorial or example on that topic. On the other hand I'm sure it's possible, since Google provides working emulators for Windows and they had to be build on Linux or Mac OS.
I have just started looking at Capacitor as a possible solution to package my hybrid apps in an electron shell. This is the first time I have used Electron, so really know very little about it's details.
I ran through the following steps..
1. Create new Ionic app
2. install capacitor as per doco
3. run npx add electron
4. cd electron
5. npm i electron-packager -g
6. electron-packager . --platform=win32
I ended up with a subfolder electron\capacitor-app-win32-x64that contained an executable, which ran fine on both my dev machine (Windows 10 x64), and another Windows (Windows Server 2008 R2 Standard x64).
My ultimate target device is a specialised small ruggedised tablet, that runs Windows 7 Embedded 32 bit.
It does not run on this, I get The version of this file is not compatible with the version of Windows you're running. I am not even sure if the build app is managed or unmanaged (assuming unmanaged?)
So, I would like to know what is not compatible about the Windows machine. Initial questions are
How do I Know what "bitness" the Electron app is (ie 32 bit, 64 bit, or is it .net to is like "any cpu"). I can't see where to find out this information (dotpeek won't open the exe, and opening the exe in Visual Studio, I don't see much information)
Could it be it is not build for the correct CPU?
Is there some other dependency that perhaps the embedded Windows 7 has not got
Any help is how to figure this out would be great!
[UPDATE1]
Following some advice as given here, it appears it is a 64 bit application, which is strange as the command electron-packager . --platform=win32 appear to indicate we want a 32 bit. So that may be my problem.
Does anyone know how to make it build to 32bit?
Found the problem. Just need to add a --arch=ia32 to get 32 bit.
So my complete build command was
electron-packager . --platform=win32 --arch=ia32
and it is now 32 bit and runs on the 32 bit machine.
I've browsed through many topic and answers related to the emulator crashing issue. Yet, I still have no clue how to resolve this issue.
My setup:
Windows 10 x64 laptop - 16GB RAM - Intel Core i7-6820HQ CPU # 2.7Ghz
Android Studio 2.3.3
Java JDK jdk-8u141-windows-x64
HAXM installed and activated
When I open Android Studio, I can start the emulator without any issues.
(see picture here)
But when I try the same from the commandline, the emulator does not startup properly and stops. (see picture here)
I've tried:
HAXM 6.0.6 and HAMX 6.1.3
Graphics: Software GLES 2.0 (instead of auto)
RAM: lowered to 512 (instead of the default 1536) as mentioned in many posts
Try a emulator with lower resulution (like Galaxy S 800x600) as also mentioned in many posts
Use arm image to trigger arm emulator
Add MB behind certain values in the ini file
Set the width/height value to 0 in the ini file
Turn off the camera (front and back) emulation
Disable multi-core CPU (since it mentioned behind it that it's experimantal)
I tried the emulator in the tools folder and the emulator folder
What am I doing wrong here?
What else can I try?
Did I forget a combination of the above mentioned items?
My end goal:
I want to make this emulator part of my CI cycle and for that I need to run a command line (or powershell) script on a Hyper-V machine (in Azure), to start this emulator, so I can hook it up to my selenium-grid (via Appium).
I had the same problem, I fix it by updating my windows (windows 10) to the latest version (windows 10 version 1903 build 18362) and take the optional update (KB4512508)
in the windows update setting..
I'm using:
- Windows 10 Enterprise.
- AMD A10-4600M APU withe Radeon HD graphics.
- ram 512.
Try this solution it worked for me.
I am following the instructions given HERE
I can install it to the vmware hard disk fine and get it running, but then it says to open a terminal and execute su
The terminal says that it cannot make me a root and nothing else
I am not able to go any further after this and so the internet isn't working in the virtual machine
Moreover, the internet works if I was just using the live CD version, without me having to do anything else
How do I get root permissions in android x86 on VMware?
--- EDIT---
After playing around some more with this I have noticed another problem: when I try to start the virtual machine, most of the times it reaches the Chrome coloured android startup logo, the logo animates continuously but the screen is sort of stuck at that phase. And if I loose focus to the vmware window and come back, I see that the window is blank and I am not sure if the virtual machine is even further loading or not. How do I properly get Android x86 to work on vmware (with full install on it's virtual hard disk and not just the live CD version? Should I try other virtual machines? I have not been able to get others such as qemu and bochs to work in the past and see that vmware is the easiest and most stable option, so I would like to run this in vmware if possible.
check here www.bitdirect.nl/?p=128
I followed this with a few little tweaks here and there and it worked perfectly.
only downside is transferring data outside of the android os is a pain.
I am running my build on Windows 8 O.S. , 64 bit machine. I have JavaFx2.0 and Java 1.7.0_09 installed on my system. I am able to build a 64 bit window executable that launches my JavaFx application as a self-contained Javafx application.
Now I want to deliver native app bundles on Windows, Linux and Mac without build my project on all three platforms i.e I would like to achieve these set of bundles in a single build that I suppose to run on by Windows 8 O.S. 64 bit machine.
I am also okay if I can do it by distributing a single Application JAR file as .zip for MAC and Linux. But what I want is that JAR should work on there respective platform.
When I used to run a single application Jar on MAC using command
java -jar application.jar
It always shows a dialog "The application require a newer version of Java Run-time" with download link. Even I have downloaded and successfully installed it on my MAC machine but it still shows me the same window.
I don't want the users to experience such difficulties while running my JavaFX application on MAC and Linux.
What I need to ship more with the Application JAR so the users can run my JavaFx application on MAC and Linux without any hassle?
I guess you are making the JavaFX Solution in a 64bit machine and on the other hand you must be having all the SDK and runtime for 64bit version. The problem is that the application made using 64bit version of SKD would required 64 bit OS to render itself. So the bottom line is, is yout mac and linux PC have 64bit version of OS and JavaFX Runtime as well as Java7.X all 64 bit? If not then you must update your runtime to 64bit version or make your application in a 32bit version of SDK. One quick suggestion. If your mac or linux is 64bit(I dont have much idea about mac) then just install a browser i.e. 64bit version and runtimes and try out. I was having the same problem and that got fixed. Let me know if my answer caused any confusion.