User forums > Using Code::Blocks
Code::Blocks does not save settings not even 1 year later
Brute:
After 30 failed attempts to pass the captha on registration I'm finally IN!! Jesus...
Hi,
I stopped using codeblocks 1 year ago just because my compiler setting didn't get saved.... yesterday I decided to install CB again and I've set up my toolchain settings, includes and all the stuff...
and guess what happened today when I started CB??
THIS!!
Please tell me WHAT DO I NEED TO DO IN ORDER TO HAVE MY SETTINGS SAVED?
ollydbg:
I have meet the same issue, but this issue can be solved very easily.
You can just press the "Reset defaults" button on your screen, and then every will be OK.
thomas:
Also, be sure not to have Code::Blocks in the Programs folder and at the same time running it in "portable" mode (that is, with a config file in the same folder).
You can have it in the Programs folder just fine, or you can use it in "portable" mode, only just not both at the same time.
Both at the same time will not work because Windows is so super intelligent and silently denies the process to write its config when it's inside a folder inside %WINDIR%/Programs. Because, you know, security is greatly increased if some file operations don't work as expected and fail without error in some more or less arbitrary locations.
Brute:
Thank you guys for solution, I will apply you suggestion if this problem comes back.
raynebc:
--- Quote from: thomas on January 19, 2015, 04:54:49 pm ---Also, be sure not to have Code::Blocks in the Programs folder and at the same time running it in "portable" mode (that is, with a config file in the same folder).
You can have it in the Programs folder just fine, or you can use it in "portable" mode, only just not both at the same time.
Both at the same time will not work because Windows is so super intelligent and silently denies the process to write its config when it's inside a folder inside %WINDIR%/Programs. Because, you know, security is greatly increased if some file operations don't work as expected and fail without error in some more or less arbitrary locations.
--- End quote ---
User Account Control was Microsoft's solution for most people always logging in with an Administrator level account. Honestly I doubt there was a better way to improve peoples' security, and programs built with Windows Vista and newer in mind can properly request administrator level permission from the user whenever necessary. The workaround for allowing non UAC-aware programs to function as they were designed is to run the program as administrator. You can do this by right clicking on the application and selecting "Run as administrator", or you can go to the properties>compatibility for the program and set it to always run as administrator.
Navigation
[0] Message Index
[#] Next page
Go to full version