472,973 Members | 2,429 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,973 software developers and data experts.

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

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
6 2664
"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
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
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
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
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
"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 thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

6
by: paul calvert | last post by:
I hope somewhere here has encountered and solved a similar problem in the past. 1) on a new Win2000 PC: installed Visual C++ 6.0 download & install single file Service Pack 5.0 2) try to...
1
by: Andrew Ward | last post by:
Had an internal compiler error if anyone at MS is interested. Line 7 was a forward declaration of a class, more specifically: class SchematicSpecID; The error went away when I moved the...
5
by: Michael Kennedy [UB] | last post by:
Hi, I would like to report some weird behavior which results in an internal compiler error in VS.NET 2003 (VC++). I have an ATL COM dll project which also uses MFC. This solution (workspace...
1
by: Irakli Lomidze | last post by:
Internal Compiler Error VS.NET 2003 Enterprise Architect Windowx XP SP1 RAM 1GB Free DiskSpacs 20GB
1
by: Irakli Lomidze | last post by:
Internal Compiler Error VS.NET 2003 Enterprise Architect Windowx XP SP1 RAM 1GB Free DiskSpacs 20GB
4
by: sebastien NO Maraux SPAM | last post by:
I am using Ghost Lib 4.0, which is SDK for Phantom haptic device. this lib does not compile under .net, seemingly because of a union of this type : union A { union A* aList; char b; };
10
by: PufferFish | last post by:
Hi folks, I hope that this is the correct group for these things, apologies if not. I've got a strange compiler error. It appears to be similar to the issue described in knowledgebase...
1
by: Marcus Kwok | last post by:
I am not sure if this is related to my previous thread ("NullReferenceException with value struct") so I am starting a new thread. I saw in...
6
by: pasalic.zaharije | last post by:
I write some project, and after few lines (ok, not few, after a lot of lines) i got internal compiler error. After few hours of looking trough my code, I find error: two same names in typedef and...
2
by: DJRhino | last post by:
Was curious if anyone else was having this same issue or not.... I was just Up/Down graded to windows 11 and now my access combo boxes are not acting right. With win 10 I could start typing...
2
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 4 Oct 2023 starting at 18:00 UK time (6PM UTC+1) and finishing at about 19:15 (7.15PM) The start time is equivalent to 19:00 (7PM) in Central...
0
by: Aliciasmith | last post by:
In an age dominated by smartphones, having a mobile app for your business is no longer an option; it's a necessity. Whether you're a startup or an established enterprise, finding the right mobile app...
3
NeoPa
by: NeoPa | last post by:
Introduction For this article I'll be using a very simple database which has Form (clsForm) & Report (clsReport) classes that simply handle making the calling Form invisible until the Form, or all...
1
by: Teri B | last post by:
Hi, I have created a sub-form Roles. In my course form the user selects the roles assigned to the course. 0ne-to-many. One course many roles. Then I created a report based on the Course form and...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 1 Nov 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM) Please note that the UK and Europe revert to winter time on...
3
by: nia12 | last post by:
Hi there, I am very new to Access so apologies if any of this is obvious/not clear. I am creating a data collection tool for health care employees to complete. It consists of a number of...
0
NeoPa
by: NeoPa | last post by:
Introduction For this article I'll be focusing on the Report (clsReport) class. This simply handles making the calling Form invisible until all of the Reports opened by it have been closed, when it...
0
isladogs
by: isladogs | last post by:
The next online meeting of the Access Europe User Group will be on Wednesday 6 Dec 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, Mike...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.