By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,119 Members | 2,064 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,119 IT Pros & Developers. It's quick & easy.

Internal Compiler Error in Windows headers, using .NET 2003 / VC7.1

P: n/a
Hi,

I recently installed a 60-day trial of .NET 2003 on my development system.

I made tests with previous personal projects (which compiled ok with VC6)
and some open source files, and keep facing the same problem with many
of them:
I keep getting errors such as:
....\WinUser.h(8028): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
....\UrlMon.h(4459): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
....\WinUser.h(3353): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
NB: the file and line of the error seems to vary...

These errors typically occur by #include-ing <windows.h> !
Several, even large, programs that rely only on the standard library
compile without problems.

I use VC6, gcc, metrowerks, and several other tools without problem
on my system, but .NET 2003 seems to have a serious issue that I
cannot explain, making it unusable for C++ & Windows development.

Any idea of why this is happening ? suggestion for a workaround ?
The system is an Athlon 3.0+ running Windows 2000.
Thanks in advance for any support,
Ivan
Nov 16 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
"David Lack" (i.A. Ivan) <so*****************@privacy.com> wrote
in message news:eL**************@tk2msftngp13.phx.gbl...
I recently installed a 60-day trial of .NET 2003 on my development system.

I made tests with previous personal projects (which compiled ok with VC6)
and some open source files, and keep facing the same problem with many
of them:
I keep getting errors such as:
...\WinUser.h(8028): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
...\UrlMon.h(4459): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
...\WinUser.h(3353): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
NB: the file and line of the error seems to vary...

These errors typically occur by #include-ing <windows.h> !
Several, even large, programs that rely only on the standard library
compile without problems.

I use VC6, gcc, metrowerks, and several other tools without problem
on my system, but .NET 2003 seems to have a serious issue that I
cannot explain, making it unusable for C++ & Windows development.

Any idea of why this is happening ? suggestion for a workaround ?
Ironic: we installed Intel's 7.1 C++ compiler, which seamlessly
integrates in the VS.NET interface.
The internal compiler errors disappeared, and all projects
now compile without problem.
The system is an Athlon 3.0+ running Windows 2000.


Isn't this ironic? Intel's compiler seems to support my AMD
platform better than Microsoft's product.

So, should we get a cheap version of MS's IDE, and buy intel's
compiler, instead of a full-blown version of .NET ?

Any advice on how to get Microsoft's C++ compiler to work ?
I previously had the same problem when trying the
first C++ .Net compiler...

Thanks,
David
Nov 16 '05 #2

P: n/a
David Lack wrote:
Hi,

I recently installed a 60-day trial of .NET 2003 on my development
system.

I made tests with previous personal projects (which compiled ok with
VC6) and some open source files, and keep facing the same problem
with many
of them:
I keep getting errors such as:
...\WinUser.h(8028): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
...\UrlMon.h(4459): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
...\WinUser.h(3353): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
NB: the file and line of the error seems to vary...

These errors typically occur by #include-ing <windows.h> !
Several, even large, programs that rely only on the standard library
compile without problems.

I use VC6, gcc, metrowerks, and several other tools without problem
on my system, but .NET 2003 seems to have a serious issue that I
cannot explain, making it unusable for C++ & Windows development.

Any idea of why this is happening ? suggestion for a workaround ?
The system is an Athlon 3.0+ running Windows 2000.


No ideas off hand. I've got VC6, VC7, VC7.1 all installed on one of my
machines and can build projects easily with any of them.

What's your include path look like? Are you using the Platform SDK headers
that shipped with VS.NET, or have you installed a later platform SDK?

If you create a simple wizard-app (e.g. MFC) in VS.NET, can you build it?

-cd
Nov 16 '05 #3

P: n/a
I use VC6, had VS.NET 2002 (uninstalled now), have VS.NET 2003 and next
Whidbey alpha. All on same system. No problem whatsoever between them.

"David Lack" <so*****************@privacy.com> wrote in message
news:eL**************@tk2msftngp13.phx.gbl...
Hi,

I recently installed a 60-day trial of .NET 2003 on my development system.

I made tests with previous personal projects (which compiled ok with VC6)
and some open source files, and keep facing the same problem with many
of them:
I keep getting errors such as:
...\WinUser.h(8028): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
...\UrlMon.h(4459): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
...\WinUser.h(3353): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
NB: the file and line of the error seems to vary...

These errors typically occur by #include-ing <windows.h> !
Several, even large, programs that rely only on the standard library
compile without problems.

I use VC6, gcc, metrowerks, and several other tools without problem
on my system, but .NET 2003 seems to have a serious issue that I
cannot explain, making it unusable for C++ & Windows development.

Any idea of why this is happening ? suggestion for a workaround ?
The system is an Athlon 3.0+ running Windows 2000.
Thanks in advance for any support,
Ivan

Nov 16 '05 #4

P: n/a
btw, try clean and then full rebuild

"David Lack" <so*****************@privacy.com> wrote in message
news:eL**************@tk2msftngp13.phx.gbl...
Hi,

I recently installed a 60-day trial of .NET 2003 on my development system.

I made tests with previous personal projects (which compiled ok with VC6)
and some open source files, and keep facing the same problem with many
of them:
I keep getting errors such as:
...\WinUser.h(8028): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
...\UrlMon.h(4459): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
...\WinUser.h(3353): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
NB: the file and line of the error seems to vary...

These errors typically occur by #include-ing <windows.h> !
Several, even large, programs that rely only on the standard library
compile without problems.

I use VC6, gcc, metrowerks, and several other tools without problem
on my system, but .NET 2003 seems to have a serious issue that I
cannot explain, making it unusable for C++ & Windows development.

Any idea of why this is happening ? suggestion for a workaround ?
The system is an Athlon 3.0+ running Windows 2000.
Thanks in advance for any support,
Ivan

Nov 16 '05 #5

P: n/a
I met your problem once. And when I cleaned some virus on my machince, it
goes. It might sounds absurd, but I still suggest you to check your disk for
viruses.
"David Lack" <so*****************@privacy.com> дʼ
news:%2******************@tk2msftngp13.phx.gbl...
"David Lack" (i.A. Ivan) <so*****************@privacy.com> wrote
in message news:eL**************@tk2msftngp13.phx.gbl...
I recently installed a 60-day trial of .NET 2003 on my development system.
I made tests with previous personal projects (which compiled ok with VC6) and some open source files, and keep facing the same problem with many
of them:
I keep getting errors such as:
...\WinUser.h(8028): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
...\UrlMon.h(4459): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
...\WinUser.h(3353): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
NB: the file and line of the error seems to vary...

These errors typically occur by #include-ing <windows.h> !
Several, even large, programs that rely only on the standard library
compile without problems.

I use VC6, gcc, metrowerks, and several other tools without problem
on my system, but .NET 2003 seems to have a serious issue that I
cannot explain, making it unusable for C++ & Windows development.

Any idea of why this is happening ? suggestion for a workaround ?


Ironic: we installed Intel's 7.1 C++ compiler, which seamlessly
integrates in the VS.NET interface.
The internal compiler errors disappeared, and all projects
now compile without problem.
The system is an Athlon 3.0+ running Windows 2000.


Isn't this ironic? Intel's compiler seems to support my AMD
platform better than Microsoft's product.

So, should we get a cheap version of MS's IDE, and buy intel's
compiler, instead of a full-blown version of .NET ?

Any advice on how to get Microsoft's C++ compiler to work ?
I previously had the same problem when trying the
first C++ .Net compiler...

Thanks,
David

Nov 16 '05 #6

P: n/a
"Carl Daniel [VC++ MVP]" <cp*****************************@mvps.org.nospam >
wrote in message news:uv**************@TK2MSFTNGP11.phx.gbl...
I recently installed a 60-day trial of .NET 2003 on my development
system.

I made tests with previous personal projects (which compiled ok with
VC6) and some open source files, and keep facing the same problem
with many of them:
I keep getting errors such as:
...\WinUser.h(8028): fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701) [....] Any idea of why this is happening ? suggestion for a workaround ?
The system is an Athlon 3.0+ running Windows 2000.

No ideas off hand. I've got VC6, VC7, VC7.1 all installed on one of my
machines and can build projects easily with any of them.


VC6 (and other compilers) work flawlessly on the system.
But both VC7 (tried once earlier) and VC7.1 seem to trigger a similar issue.
The machine is not a brand system, but has always been stable. It is used
for some data and image processing etc - has always worked ok.
Latest patches installed, virus scan (w/ updated defs) done recently.
But we tried VC7.1 on another (P4) system here, and it hasn't presented
this issue.
What's your include path look like? Are you using the Platform SDK headers that shipped with VS.NET, or have you installed a later platform SDK?
The headers are all clean installs from the installation DVD.
If you create a simple wizard-app (e.g. MFC) in VS.NET, can you build it?


Good point. Creating a new Win32 project, and it did compile... at first.
But then, I removed the "#define WIN32_LEAN_AND_MEAN" from "stdafx.h",
and now the compilation fails with the same error:
c:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\PlatformSDK\Include\OAIdl.h(848):
fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 2701)
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more
information

This is the usual behavior we observe: somehow the "complexity" of the
windows.h
header seems to trigger the problem -- and disabling parts of it (e.g. with
WIN32_LEAN_AND_MEAN or VC_EXTRALEAN) makes the issue less likely to occur.
Note that the ICE is always the same (compiler file 'msc1.cpp', line 2701),
but the source line triggering the issue seems somewhat random (typically
a simple #define or enum item).

I'd be curions what this famous line (compiler file 'msc1.cpp', line 2701)
is !

Thank to everyone for your help,
Ivan
Nov 16 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.