Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 21293

Summary:	Critical error when open cvs project
Product:	[Eclipse Project] Platform	Reporter:	philippe <alves_ph>
Component:	Resources	Assignee:	DJ Houghton <dj.houghton>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	blocker
Priority:	P5
Version:	2.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description philippe

2002-07-08 04:19:00 EDT

Just after install eclipse, i tried to open a cvs project and it appeared a 
general failed. My computer tried to show me what the memory contained but not 
succed doing it. I have a single BORLAND C++ project with 10 files and i just 
wanted to see it. But i can not.
The error is :
*** STOP : 0x000000D1
DRIVER_IRQL_NOT_LESS_OR_EQUAL
***Adress BFF15C2B base at BFF0C000, DateStamp 3a68bea9 - NDIS.sys
Empezando el volcado de memoria fisica.

Comment 1 philippe

2002-07-08 04:54:31 EDT

I have 8 other projects in the repositories and i can open everyone of them.
i just have problems with this project. I tried to open this project from a 
linux machine and it works so i don't understand.....

Comment 2 Darin Swanson

2002-07-08 08:58:41 EDT

I don't believe this is a debug report...moving to platform core.

Comment 3 John Arthorne

2002-07-08 10:24:03 EDT

Please provide as much detail as you can:

- eclipse build number
- java VM vendor and version
- CVS server OS (Linux or WinNT) and version
- English translation of the Spanish error message if possible

Comment 4 John Arthorne

2002-07-08 12:14:15 EDT

Email from contact:

        Build id: 200206271827,
        IBM Java 2 RunTime Environement SE V1.4.0_01
        linux CVS (client/server) V1.11.1p1

Translated message: Beginning the fisical memory upset

Thanks for the details.  In the future, please attach comments directly to the 
bug report instead of emailing them.

Comment 5 Michael Valenta

2002-07-10 16:34:49 EDT

I didn't know IBM had a 1.4 VM yet. Is this a beta release? Could you try a 
different VM (IBM 1.3.1 or Sun 1.4) and see if the problem reoccurs?

Comment 6 John Arthorne

2002-07-10 16:45:48 EDT


*** This bug has been marked as a duplicate of 21276 ***