User forums > Nightly builds
The 25 June 2006 build is out.
killerbot:
--- Quote from: oz on June 26, 2006, 05:49:46 am ---when C::B is firstly running on a Win32 machine, there will be an error dialog box says failed to read a key from registration table regarding the Borland compiler. It is only happened on the last nightly build.
--- End quote ---
I changed some stuff for compiler detection, but not for the Borland compiler. Will look into it today.
[EDIT] : I think the problem might have entered at the nightly of 20th june, then some BCC settings have changed.
So are you 100% sure it was NOT present in the nightly from 2 days ago ??
[EDIT2} : I am 100% sure it is because ot he change of the 20th, because at that time the registry check was added. Will fit it today or tomorrow.
killerbot:
this problem is fixed (cause : the 20th june adaptation).
To prevent reg key pop up errors, like in this case, first check to see if the key exists, on then open it.
revision 2612
skirby:
Hello,
I don't know if I am the only one to have this problem but since few build I have a noticed some slow down in C::B
The problem has appeared since The 14 June 2006 build.
It is easy to reproduce.
Open any project file.
Select a big piece of code (about 200 lines)
Then, Copy these lines (Ctrl+C)
On my computer (P4 2.8 Ghz and 2 Go RAM) C::B takes 100% CPU during 5 seconds to copy my piece of code.
Now paste it and try to undo your modification.
C::B take again 100% CPU.
I believe that that problem appear with the ByoGames plugin but I am not sure.
Somebody can confirm my problem?
Thanks and have a nice day.
byo:
--- Quote from: skirby on June 26, 2006, 01:58:22 pm ---I believe that that problem appear with the ByoGames plugin but I am not sure.
--- End quote ---
Could you disable byogames plugin (in Plugins->Manage Plugins menu) and see what will change ?
byoGames trigers one time event per second and it shouldn't take 100% CPU :?
oz:
--- Quote from: killerbot on June 26, 2006, 01:01:14 pm ---this problem is fixed (cause : the 20th june adaptation).
To prevent reg key pop up errors, like in this case, first check to see if the key exists, on then open it.
revision 2612
--- End quote ---
I am late :?, but glad to hear that you already fixed it. I did not try the previous nightly builds on windows (for clear install), so I said *only*, really sorry for the inconvenience. I'll say more later :o
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version