Windows XP build is currently incomplete

RetroArch Windows devices
#1

The current builds of Retroarch for XP-32 are incomplete. Tested the stable and nightly binaries of Retroarch with the Windows XP specific runtimes, but there is an error about missing _itoa_s function in msvcrt.dll. This function is a security enhanced function of itoa (or _itoa) and is not present in the msvcrt.dll in XP; however, this security enhanced function, in addition to others, are present in Windows Vista and later.

It is possible there are other errors, but this is the first one encountered in XP. Suggest to include an updated XP specific package which excludes the enhanced function set and has the Retroarch executable built by mingw or by Visual Studio version with XP compatibility.

#3

Verified that the Windows 32-bit build of Retroarch v1.3.4 (stable version) has no reference to _itoa_s (or itoa). As the author indicated, the stable builds are designed for XP. The nightly 32-bit Windows builds would require Vista or higher. Thank you.

#5

Thanks. As an aside, I previously tested a recent 32-bit Windows Retroarch against an older Intel chipset (Atom series). I recall that it was necessary to use the rgui client instead of xmb; threaded video off; and d3d offered the best overall compatibility even though it was not compatible with (the tested) shaders. Tested in non-windowed fullscreen mode. However, I recall that the non-windowed fullscreen gl mode would not operate at the 60 fps rate, but instead would run at a lower rate leading to slow emulation speed; but this effect did not occur in the windowed modes. This was on a LCD TV and would have to be verified again, but I don’t think this is an issue since this particular video chipset does not offer modern gl capability (and speed), so the d3d should be preferred. SDL2 audio and gamepad options were working best, too.

Note that, in this specific case above, that the windowed d3d modes work with VNC but the non-windowed fullscreen d3d mode does not.

The configuration file may have changes where experimenting with shader options, so this would cause the d3d mode to fail as noted above in this specific case; if this happens, it is simplest to revert to the default retroarch configuration file and then update the settings again, instead of attempting to find the modified lines of the configuration file.

#6

This is my first post so sorry it tags onto this thread, but I just wanted to confirm that the latest nightlies of retroarch are not working on Windows XP. I have Windows XP Professional x64 edition, and neither the 32 bit version, or 64 bit version works, and it’s giving me the _itoa_s error mentioned above. Further, the stable 1136 version is giving me the same error. Is there any correction for this? I would like to use retroarch for some of my emulated systems, but for other reasons, I want to stick with Windows XP for now for my arcade machine.

Is there anyone who has had any success with retroarch on the latest windows xp? Thanks.

#7

http://s000.tinyupload.com/index.php?file_id=30450993869128730431

Not mine but this tool fixes xp builds (official + nightlies). A few hex byte edits.

#8

Bingopud, do you have any more information about that? If we knew what that fix did, we could incorporate it properly into the code base. RetroArch is not a proprietary project that should need binary patches.

#9

[QUOTE=Lex;46793]Bingopud, do you have any more information about that? If we knew what that fix did, we could incorporate it properly into the code base. RetroArch is not a proprietary project that should need binary patches.[/QUOTE]Scans exe and replaces msvcrt import table strings: itoa_s ==> itoa, vsnprintf_s ==> vsnprintf

#10

It is not working here either (both stable and nightly).

I get an error: The instruction at “0x0ab619cf” referenced memory at “0x00000008”. The memory could not be “read”.

I, also, would be interested in an XP-working build in the future.

#11

I am terribly sorry for the carelessness and the error and unfair semi-wailing it engendered: all appears to be working as it should, after all.

(The cause was that I was trying to run it under virtualization software, with the hope of fetching the Windows cores to use on my offline chine.)

#12

No worries. I’m glad to hear it’s working!

#13

What is the name of the tool you used? The tinyupload link expired.

I keep getting the _itoa_s error even though I have installed: -Visual C++ redist 2010 SP1 -Visual C++ redist 2012 -Visual C++ redist 2013 -Visual C++ redist 2015-2019

Windows XP SP3

Edit: Seems that the Win32 1.9.0 stable build is looking for dll files which are only available in Windows 7 32 bit (BCRYPT.DLL, DWMAPI.DLL). I thought I saw somewhere that the stable 32 bit builds were supposed to work in XP. Is that true? If not, can someone tell me the most recent build/version which does work in XP?

#14

In case anyone else lands here searching for the _itoa_s error, the MSVC2010 build (RetroArch-msvc2010-x86-setup.exe as of today) is the version that works in Windows XP and NOT RetroArch-x86-setup.exe, which works in Win7 32-bit. Researched this extensively yesterday until a nice Reddit user finally clued me in.