Why my Visual C can not compile?
Jeffery Lu
My Visual C++(6.0) can not compile recently. When I compile a project,
it
displays "copy contents file...", then stops there forever.
I already reinstalled Visual C, but get the same results.
Could any one tell me what happened? How to solve it?
Thanks a lot!
Jeff
Karl Medcalf
wrote:
My office had the same problem, and it seems that there is a problem
with Norton AnitVirus and Visual C++. It seems to exhibit itself as
hanging the Visual C++ during compile of the help file.
The simplest solution is to disable Norton when compiling.
Karl Medcalf - WK5M
PP-ASEL (N43CS)
<kmed...@pdq.net>
James H. Steiger
wrote:
>Hi,
>
>My Visual C++(6.0) can not compile recently. When I compile a project,
>it
>displays "copy contents file...", then stops there forever.
>I already reinstalled Visual C, but get the same results.
>
>Could any one tell me what happened? How to solve it?
>
>Thanks a lot!
>
>Jeff
Jeff, I have the same problem, the identical problem. However, I
uninstalled my antivirus software and I *still* have the problem (so
far). After 15 hours of troubleshooting, here is what I found on my
machine.
1. Reinstalling VS does not help.
2. Reinstalling VS to a shorter path (say, C:\MSDEV) does not help.
3. If I run Windows in Safe Mode, the identical project compiles fine.
4. But it is not a graphics adaptor problem. Installing VGA.DRV does
not cure the problem.2
Under certain conditions, you can discover that VS is hanging while
trying to execute vcspawn.exe. If you do CTRL ALT DELETE and kill
WinOldApp (you will have to wait about 30 seconds for the program
to respone), the project MAY resume compiling, or it may not,
depending on what processes are running at the time.
Fortunately, (ahem) there is a "workaround" (funny how desperate
one frequently becomes for "workarounds" when one works with MS
software). It is described in MS Knowledgebase article Q250670,
although it fails to properly describe all that you need to do.
Here is what I suggest.
If you are running Norton Anti Virus or McAfee Anti Virus, disable and
try again. If that solves your problem, rejoice. If not, then do the
following.
a. The problem should arise only in projects where you are using
Context Sensitive Help.
b. For such projects, disable custom builds for 3 files, called
<YourProjectName>.hpj, resource.h, <YourProjectName>.cnt. To do this,
go into FileView, right click each file, call up Settings-->General,
and (1) unclick "Always Use Custom build step" and click the "Exclude
file from build" step.
c. To compile your help file, you will have to click on makehelp.bat,
a file that has been constructed for you. However, it will not work
unless your path contains the TOOLS directory for MS Visual Studio.
If the Visual Studio directory is "C:\Program Files\Microsoft
Developer Studio", you will need to add the
"C:\Program Files\Microsoft Developer Studio\Common\Tools"
to your path. It will, of course, look something like
"C:\Progra~1\Micros~5\Common\Tools"
in your autoexec.bat file, but you will have to experiment to get the
path right. because the "5" in the above example will change depending
on whether you have other paths that start with "Micros".
The workaround allows you to compile and test your code. Once you have
the path correct, you can just doubleclick on Makehelp.bat to compile
the help file.
I apologize if any of this is unclear. The Knowledge Base article
reinforces much of this.
If ANYONE gets more details on the precise nature of this, would you
PLEASE post to the newsgroup. I have seen about 10 people complaining
of this problem in various newsgroups. I suspect that the actual
culprit is some device driver or environment setting. But so far,
nobody seems to have the problem nailed down. Needless to say, I'd
like to completely eliminate it before "It" (whatever it is) surfaces
in some other form when I can least afford another 16 hour delay.