-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 32bit not supported #24
Comments
Yeah, sorry. There's only 64 bit executables in the release download. I can add some 32 bit executables later. |
At least 32-Bit Windows executables should be easy enough to add. Could make some quick builds. |
Yeah, 32-bit builds for both makerom and ctrtool would be much appreciated. |
Meh, this issue is old. Anyway, you can install MinGW-W64 (the name sounds like it's 64 bit only but there are 32 bit versions too). It is better than the regular MinGW anyway (imho). It should build fine with it. |
Well, it's better to rise an issue from the dead rather than creating a new one |
Does this still only work on 64-bit??? I really need it for Windows 10 32-bit. |
It does work as 32 bit build but you quickly reach the 4 GB RAM limit with it. I can make 32 bit builds but would not recommend them because of this. Games around 2 GB make it run out of mem already. Besides that there is currently a RomFS verify problem which makes it hang/loop forever. I was too lazy to look into it yet. I thought maybe @jakcron jwould have noticed it already. Well, then i must fix it. |
For those of you that need a 32-bit version in order to even use the tools, there you go: |
CTRTool is now released with 32-bit Windows builds. https://github.com/3DSGuy/Project_CTR/releases/tag/ctrtool-v1.0.0 |
I downloaded the program and I get the following error:
This version of C:\Users*****\Desktop\Windows_x86_64\ctrtool.exe is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher.
I'm using Windows 10 32 bit
The text was updated successfully, but these errors were encountered: