Rgui.exe crashes on startup (PR#2057)

[zhenliu66@hotmail.com]

By the way, I have found the offending application: it is a virtual screen
manager called JSP2. As soon as deinstalled it, R works just fine.

Hopefully this will help other people may have similar problems.

Thanks again for your help,

Zhen


----- Original Message -----
From: "Duncan Murdoch" <murdoch@stats.uwo.ca>
To: "Zhen Liu" <zhenliu66@hotmail.com>
Sent: Tuesday, September 24, 2002 2:07 PM
Subject: Re: Rgui.exe crashes on startup (PR#2057)


> On Tue, 24 Sep 2002 12:49:19 -0400, you wrote in message
> <OE59szTvHP0J3lTTJNJ0000205d@hotmail.com>:
>
> >Thanks a lot for your help, the Rgui.exe start working again!!!
> >
> >Here is the result when I run test87:
> >
> >
> >
> >Press test button to see effect of changing the control word.  If the
> >report comes without pressing the button, some driver is buggy.
> >
> >Try resizing this window, running other programs, etc, to see if the bug
> >shows up.
> >
> >In R, the floating point control word should always be 037F.
> >12:45:13 PM:  Control word changed to 027F
> >12:45:26 PM:  Control word changed to 0040
> >12:46:13 PM:  Control word changed to 0040
> >12:47:25 PM:  Control word changed to 027F
> >
> >Looks like something is changing the control word to 027F, but I can't
> >really figure out which program is doing that. Is there anyway to have
> >Rgui.exe peg the floating point control word to what it likes?
>
> The difference between 37F and 27F is that 27F only gives 53 bit
> precision, while 37F gives 64 bit precision.  (You can see the meaning
> of the bits on this web page which Google found for me:
>
>  <http://www.compaq.com/fortran/docs/vf-html/pg/pg1contw.htm>)
>
>  I don't think this change would cause a crash; I would have expected
> to see only subtle changes in numerical results.  My guess would be
> that the change to 27F isn't what's causing the crash, though it might
> be another symptom of the same bug.
>
> The difficulty in trying to fix this is that it can happen almost any
> time. Whenever R makes a call to the system (e.g. to display a message
> or to process a keystroke), the buggy driver might mess up the control
> word.
>
> I'd like to try to move some code around to try to fix this, but I'm
> going out of town tomorrow, and the release of 1.6.0 is imminent.
> Here's what I'd suggest:
>
> You should try to find updates to the video drivers your system uses.
> Go to the Control Panel, System, Device Manager, Display Adapters.
> You probably only have one display adapter; click on it, and select
> properties.  I think most versions of Windows have an option to search
> online for an updated driver.  Try that if you can; if it can't find
> an update, try the manufacturer's web site.
>
> After 1.6.0 is released, if you haven't been able to find a fix that
> works for you, let me know and I'll play around with some changes that
> might help.
>
> Duncan Murdoch
>

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._