You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current romgen.exe is 64-bit, and hence only works on 64-bit Windows laptops, but the laptop I use is an old Windows XP 32-bit, and so I cannot run romgen.exe.
It would be very convenient to convert roms using a 32-bit program rather than a 64-bit program, because 32-bit programs provide better availability to all users of Win32.
It is possible to use the online conversion website, but I prefer the command line application, because it is annoying to have to keep on connecting the Ethernet cord, and I don't prefer for the laptop to be connected to the Internet anyway.
No additional context.
The text was updated successfully, but these errors were encountered:
So the executable I bundled actually was 32-bit, but Visual Studio dropped support for Windows XP in recent versions. I reverted to the VS2017 toolset to try and make XP builds for the tools (statically linked because I couldn't find a good standalone installer for the Universal C Runtime). Let me know if these work on your system: tiboyce-winxp.zip
Thank you for your detailed explanation, calc84maniac. adriweb, I tried to download the web page but it didn't work, probably because it used too new a version of something.
The current romgen.exe is 64-bit, and hence only works on 64-bit Windows laptops, but the laptop I use is an old Windows XP 32-bit, and so I cannot run romgen.exe.
It would be very convenient to convert roms using a 32-bit program rather than a 64-bit program, because 32-bit programs provide better availability to all users of Win32.
It is possible to use the online conversion website, but I prefer the command line application, because it is annoying to have to keep on connecting the Ethernet cord, and I don't prefer for the laptop to be connected to the Internet anyway.
No additional context.
The text was updated successfully, but these errors were encountered: