From: Graeme P. <gf...@pa...> - 2002-12-26 11:10:20
|
Hi I am looking into trying out Jedit on both windows and Linux. Does installing the Sun's Java 1.4 VM cause any problems on XP - is = this a common thing to do? Will it cause me any problems with Internet = Explorer or Windows i.e. does XP like to have the MS version of the Java VM. Does the console plugin work on Windows and capture all the output of a compiler. Can I run a "command line" batch file with a single keystroke = or toolbar button from within Jedit. I noticed the message about some Graphics drivers having problems on = Windows with Java 1.4.1 - has anyone successfully used an Intel 845G CPU board = with onboard graphics and Java 1.4.0 or 1.4.1. Graeme |
From: Randall R S. <rrs...@cr...> - 2002-12-26 15:52:19
|
Graeme, My, you're the apprehensive one, aren't you? There should be no problem. Always keep your drivers up to date. The problems triggered by (but not lying within) jEdit and the 1.4 releases of the Sun JVM were, I belive, limited to those with ATI video cards. Updating drivers resolved the problem. I'm unaware of any untoward interactions between the Sun JVM and the Microsoft one (such as it is). I don't think there's a way to map a keyboard event to a batch file invocation in the Console plug-in directly. I think you could write a BeanShell macro to do so, however, but it's not something I know a lot about. Go for it. Randall Schulz At 03:09 2002-12-26, Graeme Prentice wrote: >Hi > >I am looking into trying out jEdit on both windows and Linux. > >Does installing the Sun's Java 1.4 VM cause any problems on XP - is this >a common thing to do? Will it cause me any problems with Internet >Explorer or Windows i.e. does XP like to have the MS version of the Java VM. > >Does the console plug-in work on Windows and capture all the output of a >compiler. Can I run a "command line" batch file with a single keystroke >or toolbar button from within jEdit. > >I noticed the message about some Graphics drivers having problems on >Windows with Java 1.4.1 - has anyone successfully used an Intel 845G CPU >board with onboard graphics and Java 1.4.0 or 1.4.1. > >Graeme |
From: Doug <um...@my...> - 2002-12-30 15:31:43
|
Randall R Schulz wrote: > Graeme, > > My, you're the apprehensive one, aren't you? > > There should be no problem. Always keep your drivers up to date. The > problems triggered by (but not lying within) jEdit and the 1.4 releases > of the Sun JVM were, I belive, limited to those with ATI video cards. > Updating drivers resolved the problem. Not true in my case. I had the latest ATI drivers and was still hanging when exiting jEdit. <snip> > > Randall Schulz |
From: Andrew K. <aw...@cb...> - 2002-12-30 16:58:52
|
I have the latest ATI drivers (from compaq) on a Win2k notebook and when I exit JEdit (under JDK1.4.1) the OS completely locks. I am running under jdk 1.4.0 and not experiencing the problem. Because I am running a notebook I can't get drivers from ATI, I have to get them from the notebook manufacturer. (see the ATI web site) Not sure what I am going to do long term. -Andy. > Randall R Schulz wrote: >> Graeme, >> >> My, you're the apprehensive one, aren't you? >> >> There should be no problem. Always keep your drivers up to date. The >> problems triggered by (but not lying within) jEdit and the 1.4 >> releases of the Sun JVM were, I belive, limited to those with ATI >> video cards. Updating drivers resolved the problem. > > Not true in my case. I had the latest ATI drivers and was still hanging > when exiting jEdit. > > <snip> >> >> Randall Schulz > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > -- > ----------------------------------------------- > jEdit Users' List > jEd...@li... > https://lists.sourceforge.net/lists/listinfo/jedit-users |
From: <ll...@li...> - 2002-12-31 01:44:59
|
I had that problem too. Since I use jEdit 8+ hours a day I got very frustrated and looked up at the bugparade to see if there was a workaround. I found this: http://developer.java.sun.com/developer/bugParade/bugs/4756720.html Workaround (cut from link above) For users running standalone apps, try running without d3d: java -Dsun.java2d.d3d=false For WebStart users, see the workaround in bug 4749817. If you are using the windows jEdit launcher application you will need to go in and change it there. jedinit.exe IFAIR. I hade trouble with other applications too, so I ended up setting it as a system environment variable in Control Panel > System > Advanced > Environment Variables (note that you should not add the -D part there) I am running a winXP infested dell 1200mzh laptop with 512mb ram, and I have had no crashes since. Hope that helps /Lasse Andrew Kelso wrote: >I have the latest ATI drivers (from compaq) on a Win2k notebook and when I >exit JEdit (under JDK1.4.1) the OS completely locks. I am running under >jdk 1.4.0 and not experiencing the problem. Because I am running a >notebook I can't get drivers from ATI, I have to get them from the >notebook manufacturer. (see the ATI web site) > >Not sure what I am going to do long term. > >-Andy. > > > > >>Randall R Schulz wrote: >> >> >>>Graeme, >>> >>>My, you're the apprehensive one, aren't you? >>> >>>There should be no problem. Always keep your drivers up to date. The >>>problems triggered by (but not lying within) jEdit and the 1.4 >>>releases of the Sun JVM were, I belive, limited to those with ATI >>>video cards. Updating drivers resolved the problem. >>> >>> >>Not true in my case. I had the latest ATI drivers and was still hanging >> when exiting jEdit. >> >><snip> >> >> >>>Randall Schulz >>> >>> >> >>------------------------------------------------------- >>This sf.net email is sponsored by:ThinkGeek >>Welcome to geek heaven. >>http://thinkgeek.com/sf >>-- >>----------------------------------------------- >>jEdit Users' List >>jEd...@li... >>https://lists.sourceforge.net/lists/listinfo/jedit-users >> >> > > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf > > |
From: <ll...@li...> - 2002-12-31 01:55:42
|
And as a special service for those of you who are curious, but can't be bothered to get a login at the bugparade here is what one of Suns engineers has to say about the problem: Apparently the problem is that we create too many d3d devices. Currently, whenever we want d3d capabilities on a ddraw surface, we create a d3d device for that surface. The DirectX docs suggest that having one d3d device per ddraw object (not per ddraw surface) is a better way to go for performance reasons; the context switching inherent in multiple d3d devices is too expensive. They do not happen to mention that having too many devices can also hang the system (this is presumably a driver bug that we just happened to bump into on these ATI boards). Although the real fix for the crash lies with ATI (I don't think the OS should crash because of what we are doing), we can and should fix the problem in our code by moving to a system of sharing a single d3d device, as suggested by the DirectX documention. There are issues with this approach, such as: - we need to do a SetRenderTarget whenever we are rendering into a new ddraw surface since the single d3d device may currently be set to a different render target. - in addition to changing the rendering target, we also need to update the viewport if the dimensions of the new surface differ from the previous one. - we need to lock around accesses to this shared device since we have potential multi-threaded rendering issues when rendering to different surfaces. http://developer.java.sun.com/developer/bugParade/bugs/4713003.html Lets hope that Sun will clean up their mess and ship a jdk 1.4.1_02 Real Soon Now /Lasse Lasse Lindgård wrote: > > I had that problem too. > > Since I use jEdit 8+ hours a day I got very frustrated and looked up > at the bugparade to see if there was a workaround. > > I found this: > http://developer.java.sun.com/developer/bugParade/bugs/4756720.html > > Workaround (cut from link above) > > For users running standalone apps, try running without d3d: > java -Dsun.java2d.d3d=false > For WebStart users, see the workaround in bug 4749817. > > If you are using the windows jEdit launcher application you will need to > go in and change it there. jedinit.exe IFAIR. > > I hade trouble with other applications too, so I ended up setting it as a > system environment variable in Control Panel > System > Advanced > > Environment Variables > (note that you should not add the -D part there) > > I am running a winXP infested dell 1200mzh laptop with 512mb ram, > and I have had no crashes since. > > Hope that helps > /Lasse > > > > Andrew Kelso wrote: > >> I have the latest ATI drivers (from compaq) on a Win2k notebook and >> when I >> exit JEdit (under JDK1.4.1) the OS completely locks. I am running under >> jdk 1.4.0 and not experiencing the problem. Because I am running a >> notebook I can't get drivers from ATI, I have to get them from the >> notebook manufacturer. (see the ATI web site) >> >> Not sure what I am going to do long term. >> >> -Andy. >> >> >> >> >>> Randall R Schulz wrote: >>> >>> >>>> Graeme, >>>> >>>> My, you're the apprehensive one, aren't you? >>>> >>>> There should be no problem. Always keep your drivers up to date. The >>>> problems triggered by (but not lying within) jEdit and the 1.4 >>>> releases of the Sun JVM were, I belive, limited to those with ATI >>>> video cards. Updating drivers resolved the problem. >>>> >>> >>> Not true in my case. I had the latest ATI drivers and was still >>> hanging >>> when exiting jEdit. >>> >>> <snip> >>> >>> >>>> Randall Schulz >>>> >>> >>> >>> ------------------------------------------------------- >>> This sf.net email is sponsored by:ThinkGeek >>> Welcome to geek heaven. >>> http://thinkgeek.com/sf >>> -- >>> ----------------------------------------------- >>> jEdit Users' List >>> jEd...@li... >>> https://lists.sourceforge.net/lists/listinfo/jedit-users >>> >> >> >> >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> >> > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf |
From: Slava P. <sl...@je...> - 2002-12-31 02:01:10
|
On Mon, 2002-12-30 at 20:58, Lasse Lindgård wrote: > Lets hope that Sun will clean up their mess and ship a jdk 1.4.1_02 Real Soon Now I hope Sun doesn't make any changes which sacrifice performance. It is not Sun's fault that the OS and drivers were optimized for running Kaazaa and playing games instead of doing real work. -- Slava Pestov <sl...@je...> |