Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: podoroges on May 24, 2020, 01:14:14 pm

Title: Installing Code::Blocks Windows XP SP3
Post by: podoroges on May 24, 2020, 01:14:14 pm
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?
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: stahta01 on May 24, 2020, 02:42:32 pm
You need to copy some DLL files from the prior CB release.

See http://forums.codeblocks.org/index.php/topic,23770.msg162098.html#msg162098 (http://forums.codeblocks.org/index.php/topic,23770.msg162098.html#msg162098)

Tim S.
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: podoroges on May 24, 2020, 03:32:08 pm
Dear Tim,

Thank you for your answer. I followed your advice, downloaded 7 files from
http://svn.code.sf.net/p/codeblocks/code/trunk/src/exchndl/win32/bin/
to codeblocks directory (5 of them were overwrited).

However, the error is the same, and codeblocks will not start.
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: LETARTARE on May 24, 2020, 04:42:04 pm
You must use svn11196, not svn12091 !

@developpers
To avoid this recurring problem, could you modify the corresponding version in the repository ?
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: podoroges on May 24, 2020, 05:24:28 pm
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!
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: phoenixlpd on January 26, 2021, 03:50:16 pm
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.
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: Tim on August 03, 2021, 05:55:59 pm
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
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: Commaster on August 03, 2021, 07:52:55 pm
If I install "codeblocks-20.03mingw-setup.exe" on "Win XP x64, SP2"
-snip-
If I then add the files from:-  https://sourceforge.net/p/codeblocks/code/11196/tree/trunk/src/exchndl/win32/bin/
Looks like you installed a 64bit Code::Blocks and fed it a 32bit exchndl. Please try the win64/bin/ folder right next to it.
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: Tim on August 05, 2021, 11:19:59 am
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

 
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: Commaster on August 06, 2021, 04:09:44 am
"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.
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: AndrewCot on August 06, 2021, 07:04:10 am
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.
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: AndrewCot on August 06, 2021, 08:51:58 am
@Commaster. I have updated my unofficial x64 NSIS only installer that you can read up about on the following thread https://forums.codeblocks.org/index.php/topic,24592.0.html to include changes specifically for for Win XP that should if it works as programmed will install the correct files for x64 XP that I downloaded from the https://sourceforge.net/p/codeblocks/code/11196/tree/trunk/src/exchndl/win64/bin/ directory.

If you do try the x64 NSIS installer and it works or not could you post in the https://forums.codeblocks.org/index.php/topic,24592.0.html how it went.
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: Commaster on August 06, 2021, 09:42:06 am
@Commaster. I have updated my unofficial x64 NSIS only installer that you can read up about on the following thread https://forums.codeblocks.org/index.php/topic,24592.0.html to include changes specifically for for Win XP that should if it works as programmed will install the correct files for x64 XP that I downloaded from the https://sourceforge.net/p/codeblocks/code/11196/tree/trunk/src/exchndl/win64/bin/ directory.

If you do try the x64 NSIS installer and it works or not could you post in the https://forums.codeblocks.org/index.php/topic,24592.0.html how it went.
I think you mean @Tim, cause I don't have a Win XP x64, just using google  :)
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: Tim on August 06, 2021, 04:26:01 pm
@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
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: AndrewCot on August 07, 2021, 06:57:16 am
@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.
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: Tim on August 08, 2021, 10:03:53 am
Hi Andrew,

I appreciate you taking the time looking into this issue. I looked at my msvcrt.dll ver and it's
the same version, not surprising really as I also got my latest XP iso's from archive.org.

There's a certain "Karma" going on for me over the "XP x64" issue. I use XP "just because",
but I have only been using the x64 version for 6 months because I appear to have picked up
some sort of 'malware' (Eating up cpu cycles)  in one of my app's which I have not been able
to get to the bottom of. So I switched to x64 in the hope the 'malware' would not be able to
run under x64 and luckily it doesn't. If and when I feel the urge I will try and find out which
apps the 'malware' resides in and kill it off, and go back to XP-32bit.
So "XP x64" limitations have saved my bacon over the malware issue, so to complain about
those same limitations would be very churlish of me. I think I picked up the infection while
searching for cpld & fpga software license keys on some Russian & Chinese sites.

"Virtualbox" I've only tried it once but failed due to windows versions not being specified prior to
downloading the software. After waiting an hour for a download only to be told I need to
"upgrade my OS" I lost interest. That said, I partition my drives with multiple primaries,
and at present use "bootus" in the mbr for system selection. I use win2K permanently on one
partition for OS management. (format & copy systems to and from different partitions) It takes
2-3 minutes to format and copy a new XP system on to a partition. I've been doing this sort of
thing since 1997 but then used IBM's OS2 bootloader for system selection.

A year ago I tried Codeblocks with a Win32 GUI project and after I had found out about
ResEdit, I was amazed how easy it all seemed, especially since I haven't really done any
windows programming since 2005 when I was using MSVC6. This unexpectedly pleasant
experience has been in the back of my mind when I've been using Eclipse for playing
around with STM32 programming. I'm sure you can imagine that using Eclipse on my Intel
socket 775 Q6700 running XP is like going for a walk with bags of sand tied to my feet.
With this in mind I decided it was time I found out why I've not seen any STM32 development
going on with Codeblocks.

Now after 3 days of reading posts, gnu and JLink pdf's I think I'm starting to understand the
reasons for the lack of open source STM32 development. It seems to me that the skill-set
needed is soo wide that anyone having the full set will probably be considered by polite
society to be "Mad as a Hatter". That said if I think I have anything useful to say on the
subject I'll start a new topic thread.

One thing I can say is that if I had read "UM08001_JLink.pdf" first, I would have saved
me a lot of time as it gave me a very lucid overview of the real world debug procedure,
which put the gnu tools and forum posts into context.

Tim
Title: Re: Installing Code::Blocks Windows XP SP3
Post by: AndrewCot on August 08, 2021, 11:09:59 am
Tim,

Embedded systems development is easy if things work, but are f***ing hard as h**l if something does not want to play ball. I know all about it, I have done embedded systems on 8051, I80960 (a risc based CPU from intel 25 yrs ago), I386EX (16 bit) and AMD Elan 410 (486 32 bit) and lately Linux. Luckily the latest Linux was using SLD2 so I migrated the code base onto a real Linux OS and also MS VS2017 and C:B using MSYS2 after writing peripheral simulators.

If you can move the STm32 app onto Linux where you simulate the hardware it will make your life so much easier. For NVRAM malloc it and load/save it to a file on startup or shutdown or when you request it.

A for upgrading your PC check out the AMD 5 5600G or AND 7 5700G that was released last Thursday. I ordered on Friday a new PC with the 5700G in it that I should get in the middle of the week from a local computer store. I find VirtualBox acceptable if you give it say 4 or 8GM and 4 CPU's when running Linux or Windows. I have used it with 1Gb and 1 CPU and it was way too slow....

Some pages that may help you with C::B and STM32:
    https://www.codeproject.com/Tips/601093/Creating-STM-Microcontroller-Project-in-Code-Blo
   https://github.com/i25ffz/stm32f4-codeblocks-dev
   https://imagecraft.com/?catid=0&id=10
   https://sourceforge.net/projects/codeblockeps-ni/

So it looks like other people have enhanced their C:B version for STM32 usage, but as far as I can see none of it has made it into the C::B mainline source tree.