My Vis Studio editor runs like a dog
-
I have a 600MHz PIII with 256M Ram running windows NT server . Generally apps go along nicely . But if I do a carrige return or a delete at the top of a 16KB source file it takes 5 seconds to respond , and the processor goes from 2% utilisation to 50% .(memory usage stays constatnt around 75MB) I am pulling what little hair I have out in big chunks . Any ideas ?
-
I have a 600MHz PIII with 256M Ram running windows NT server . Generally apps go along nicely . But if I do a carrige return or a delete at the top of a 16KB source file it takes 5 seconds to respond , and the processor goes from 2% utilisation to 50% .(memory usage stays constatnt around 75MB) I am pulling what little hair I have out in big chunks . Any ideas ?
-
I have a 600MHz PIII with 256M Ram running windows NT server . Generally apps go along nicely . But if I do a carrige return or a delete at the top of a 16KB source file it takes 5 seconds to respond , and the processor goes from 2% utilisation to 50% .(memory usage stays constatnt around 75MB) I am pulling what little hair I have out in big chunks . Any ideas ?
-
I have a 600MHz PIII with 256M Ram running windows NT server . Generally apps go along nicely . But if I do a carrige return or a delete at the top of a 16KB source file it takes 5 seconds to respond , and the processor goes from 2% utilisation to 50% .(memory usage stays constatnt around 75MB) I am pulling what little hair I have out in big chunks . Any ideas ?
This typically happens because of the .NCB file created by VC++. Close down your project and delete this file (in your project's folder). Let me know if it helps, Alvaro