When vc6.0 was recently used and file-> open was used, "Microsoft (r) Developer studio needs to be closed when it encounters a problem. We are sorry for the inconvenience" In additionProgramWhen you click the compile button or link button, the system does not respond. You must turn the VC off and re-open it in the task manager. However, no matter how the current VC gets it, you can only compile it, no response from a single link, depressing! Do you know? Thank you. Best Answer
Sometimes there are some problems with VC compilation. It is much better to install the SP6 patch. I installed the SP6 patch, and there was no problem with compilation.
Chinese version of vc6.0 SP6 patch:Http://download.microsoft.com/download/e/c/9/ec94a5d4-d0cf-4484-8b7a-21802f497309/Vs6sp6.exe
English version of vc6.0 SP6 patch:
Http://www.microsoft.com/downloads/info.aspx? Bytes
After Visual Studio 6.0 is installed, it is found that the "open" function in vc6.0 is unavailable. An error occurs after you click "open. exe-application error "0x73d311c7" command references the "0x00000004" memory, which cannot be "read ". I have seen a similar problem on the internet, saying it is in conflict with office2007. I uninstalled office2007 and found that the problem was eliminated. There is another problem with the installation of office2007.
The user said that it would be enough to pack the vc6.0sp6 patch. I installed it, but I still cannot.
After the patch is opened, select the installation directory of vc6.0. After the patch is installed, there is a text that seems to be news in the installation directory. Check its properties and check the modification time to see if it has been installed.
If the program compilation is normal, but "..." appears during running, you must disable it if you encounter any problems. We are sorry for the inconvenience caused. "I think a large part of the reason is because of your program problems, and most of them are memory usage errors. Pay attention to your usage of pointers and arrays, check whether cross-border orOthersError!