Codeblocks api ms win crt string l1 1 0 dll

Topic: Installing Code::Blocks Windows XP SP3  (Read 16088 times)

Hello, I'm using Win XP 32bit, SP3.
I tried to install codeblocks-20.03mingw-32bit-setup.exe
Installation completed successfully, but on launch of codeblocks.exe there was an error:

The application has failed to start because api-ms-win-crt-string-l1-1-0.dll was not found.

Quick googling shows that Visual C++ Redistributable should be installed
I have installed vcredist_x86.exe from microsoft site, and get another error:

The procedure entry point _o__configure_narrow_argv could not be located.

I even performed complete reinstall my Win XP. After clean installation the error is the same.
Does that mean that Code::Blocks no longer support Win XP?
Could you help me, please?

C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

You must use svn11196, not svn12091 !

@developpers
To avoid this recurring problem, could you modify the corresponding version in the repository ?

« Last Edit: May 24, 2020, 04:45:37 pm by LETARTARE »

CB-13071, plugins-sdk-2.23.0 : Collector-1.7.7, AddOnForQt-3.4.9
1-Win7 Business Pack1 64bits : wx-3.2.1, gcc-8.1.0,
2-OpenSuse::Leap-15.4-64bits : wx-3.2.1;gtk3, gcc-8.2.1,
=> !! The messages are translated by Deepl

Dear LETARTARE,

It works, thank you!

For those, who experience similar problems.
Go to https://sourceforge.net/p/codeblocks/code/11196/tree/trunk/src/exchndl/win32/bin/
Download all 6 files. Place to Codebloks directory (overwrite will be required).
So, it still works with XP, such a relief!

Thank you for putting the link and instruction in your post!    I have codeblocks up and running on my old XP laptop now.

Hello,

I'm using Win XP x64, SP2.

I can install codeblocks-20.03mingw-32bit-setup.exe  and add the files from

https://sourceforge.net/p/codeblocks/code/11196/tree/trunk/src/exchndl/win32/bin/

Then codeblocks works with "Win XP x64, SP2" and "Win XP 32bit, SP3"

If I install "codeblocks-20.03mingw-setup.exe" on "Win XP x64, SP2"  I get the usual error message:-

The application has failed to start because api-ms-win-crt-string-l1-1-0.dll was not found.

If I then add the files from:-  https://sourceforge.net/p/codeblocks/code/11196/tree/trunk/src/exchndl/win32/bin/

I get a new error message:- The application has failed to start because exchndl.dll was not found.

Because I am happy to use the 32bit version of codeblocks on my XP x64 I am not looking for a fix, but just
thought it would be useful to other users to have this behavior documented.

Thank you for the continued development of CodeBlocks.

Tim

Looks like you installed a 64bit Code::Blocks and fed it a 32bit exchndl. Please try the win64/bin/ folder right next to it.

Thanks for pointing that out, I'm amazed I didn't notice that myself, I should be grateful that I can still feed myself!

However, when I tried the 64bit files today, I received a new error message:-

"The procedure entry point Wow64GetThreadContext could not be located in the dynamic link library KERNEL32.dll"

Tim

"The procedure entry point Wow64GetThreadContext could not be located in the dynamic link library KERNEL32.dll"

Sadly this is a limitation of Win XP for 64 bit applications. This kernel API was introduced in Vista.

The Wow64GetThreadContext is in the dbgcore.dll file. The dbgcore.dll  is refefnced in the dbghelp.dll.

Looks like you may have used the latest files. They the x64 files from:
    https://sourceforge.net/p/codeblocks/code/11196/tree/trunk/src/exchndl/win64/bin/

The dbghelp.dll. in the directory above does not reference the dbgcore.dll  and as such does not require it and therefore the Wow64GetThreadContext error should not occur.

Can you please post if this is okay as if it does work then I will see if I can do something in the installers I have been working on to address this if it is even possible.

@AndrewCot

I've just tried the files at:-  https://sourceforge.net/p/codeblocks/code/11196/tree/trunk/src/exchndl/win64/bin/

Unfortunately Code::blocks started up with the same error of:-

"The procedure entry point Wow64GetThreadContext could not be located in the dynamic link library KERNEL32.dll"

Please don't try too hard on my account, I'm fine using the 32bit version, That said I will continue to test any fixes you suggest. I don't want to wear out my welcome, as I have some more pressing questions to ask in the near future, as soon as I have educated myself enough to ask a sensible question and understand the answer.

Regards... Tim

@tim. I have grabbed the Windows XP 32 and 64 bit ISO files from https://archive.org . I then copied a script I use to do an unattended Virtualbox guest install of Linux and modified it to install  Windows XP 32 and 64 bit OS's as it's a lot faster and I do not need to do anything apart from run the batch file as it's fully automated and I end up with a working Windows guest.

I have successfully installed the NSIS 32 bit installer on XP x86 and x64 and was able to run C::B without and errors popping up.

I did not get the x64 C::B build to run on Windows XP x64 SP2. I get a "The procedure entry point _wassert could not be located in the dynamic link library msvcrt.dll." pop up error. The msvcrt.dll is 7.0.3790 and I cannot find an update for XP x64. I traced the change in MinGW-64 to 2013 when the _wassert was added, so it's not like you can go back a few years to a compiler that does not include it and build C::B.

Looks like the work around is to use the C::B 32 bit version, unless you can find a later msvcrt.dll that works and there are no more issues.

What is API MS Win CRT string i1 1 0 dll?

Where to put API MS Win CRT Convert l1 1 0 dll?

What is API MS Win core Winrt l1 1 0 dll?