From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0678_01C302D5.AB990E10
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Interesting.  User mode exceptions sent to OCA are rare.  Someone was =
just telling me of this connection last week and I don't remember how he =
described the small set of executables for which OCA is invoked.  I =
didn't know OE is in that set as I have not seen it.

   In any case, the text does not say the problem is Microsoft's only =
that it occurs when running what is likely a Microsoft app (in this case =
of OE it is) and that Microsoft is aware of it or in other words, that =
this specific crash is one which has been reported before but not that =
the cause is the fault of Microsoft or even in a Microsoft authored or =
even Microsoft provided component.

Rich


  "Randy H"  wrote in message =
news:3e9b78b9{at}w3.nls.net...
  When OE Crashed I received this dialog box, to which i clicked 'Send =
Error Report':
  After the report was sent, I received the following box:



  Which, when I clicked on the 'More Infromation' link, yielded the =
following:


  So it appears that OCA supports system crashes and application crashes =
as well--and, in this case, has stated a Microsoft application is more =
than likely the cause of the problem.=20


    "Rich"  wrote in message news:3e9af2e9{at}w3.nls.net...
       OCA applies to system crashes not app crashes so a buggy driver =
is likely.  That Microsoft acknowledged it as a Microsoft bug is =
suspicious.  I've not seen a\language like that but I've rarely seen OCA =
use because I'm conservative drivers.  My guess is that it is an =
identified problem but that it is likely a third party driver for which =
the third party hasn't provided an update.  I'd expect the crash and/or =
OCA to identify the specific driver.



       A corrupt or invalid font is also interesting suggestion but that =
would presume that you have changed the default font settings.



    Rich



      "Robert Comer"  wrote in message =
news:3e9989c7$1{at}w3.nls.net...
      Looks about the same as mine. (except the last 4 of OE is .1106, =
not .106

      I really suspect a corrupt font on yours.

      > When I looked at the OCA message, MSFT acknowledged that this is =
their
      bug,
      > so I'll leave it at that.

      Interesting -- it doesn't always happen that way on all PC's =
obviously.  I
      suppose it could be a driver problem.

      - Bob Comer 


      "Randy H"  wrote in message
      news:3e99858f$1{at}w3.nls.net...
      > OE6 is 6.00.2800.106
      >
      > XP+SP1.
      >
      > When I looked at the OCA message, MSFT acknowledged that this is =
their
      bug,
      > so I'll leave it at that.
      >
      > "Robert Comer"  wrote in message
      > news:3e99778f{at}w3.nls.net...
      > > Which version of OE and OS btw.
      > >
      > > - Bob Comer
      > >
      > >
      > > "Randy H" 
wrote in message
      > > news:3e99714f{at}w3.nls.net...
      > > > Toggle it back and forth twice, then go in and make some =
changes.
      > > >
      > > > Boom.
      > > >
      > > > "Geo."  wrote in message
      news:3e99615a$1{at}w3.nls.net...
      > > > > I do that all the time without problem.
      > > > >
      > > > > Geo.
      > > > >
      > > > > "Randy H"
 wrote in message
      > > > > news:3e98fad1$1{at}w3.nls.net...
      > > > > > It may be able to view source without
imploding, but I =
can crash
      OE
      > > > > > with impunity just by toggling between
plain-text and =
HTML when
      > > > > > sending a new message.
      > > > > >
      > > > > > No fix as of yet.
      > > > >
      > > > >
      > > >
      > > >
      > >
      > >
      >
      >


------=_NextPart_000_0678_01C302D5.AB990E10
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








  
Interesting.  User =
mode=20
exceptions sent to OCA are rare.  Someone was just telling me of = this=20
connection last week and I don't remember how he described the small set = of=20
executables for which OCA is invoked.  I didn't know OE is in that
= set as I=20
have not seen it.
 
   In any
case, the text does =
not say the=20
problem is Microsoft's only that it occurs when running what=20
is likely a Microsoft app (in this case of OE it is) and
that=20 Microsoft is aware of it or in other words, that this specific
crash is = one=20
which has been reported before but not that the cause is the fault = of=20
Microsoft or even in a Microsoft authored or even Microsoft provided=20
component.
 
Rich
 
 

  "Randy H" <randy_holcomb{at}attglobal.netmailto:randy_holcomb{at}attglobal.net">randy_holcomb{at}attglobal.net
A>>=20
  wrote in message news:3e9b78b9{at}w3.nls.net...
  When OE Crashed I received this dialog box, to =
which i=20
  clicked 'Send Error Report':
  After the report was sent, I received the =
following=20
  box:
   
   
   
  Which, when I clicked on the 'More Infromation' =
link,=20
  yielded the following:
   
  
   
  So it appears that OCA supports system =
crashes=20
  and application crashes as well--and, in this=20
  case, has stated a Microsoft =
application is more=20
  than likely the cause of the problem. 
   
   
  

    "Rich" <{at}> wrote in message news:3e9af2e9{at}w3.nls.net...
    
       OCA =
applies to=20
    system crashes not app crashes so a buggy driver is likely.  =
That=20
    Microsoft acknowledged it as a Microsoft bug is suspicious.  =
I've not=20
    seen a\language like that but I've rarely seen OCA use because I'm=20
    conservative drivers.  My guess is that it is an identified =
problem but=20
    that it is likely a third party driver for which the third party =
hasn=92t=20
    provided an update.  I'd expect the crash and/or OCA to =
identify the=20
    specific driver.
     
       A corrupt =
or=20
    invalid font is also interesting suggestion but that would =
presume that=20
    you have changed the default font settings.
     
    Rich
     
    
      "Robert Comer" <bobcomer{at}mindspring.com>=20">mailto:bobcomer{at}mindspring.com">bobcomer{at}mindspring.com>=20
      wrote in message news:3e9989c7$1{at}w3.nls.net...Looks=20
      about the same as mine. (except the last 4 of OE is .1106, not=20
      .106I really suspect a corrupt font on
yours.> =
When I=20
      looked at the OCA message, MSFT acknowledged that this is=20
      theirbug,> so I'll leave it at
that.Interesting =
-- it=20
      doesn't always happen that way on all PC's obviously.  =
Isuppose=20
      it could be a driver problem.- Bob Comer
<just toggled =
it over=20
      10 times and added this and then i'lltoggle it one more=20
      time...>"Randy H"
<randy_holcomb{at}attglobal.netmailto:randy_holcomb{at}attglobal.net">randy_holcomb{at}attglobal.net
A>>=20
      wrote in messagenews:3e99858f$1{at}w3.nls.net...=
>=20
      OE6 is 6.00.2800.106>>
XP+SP1.>> When =
I looked=20
      at the OCA message, MSFT acknowledged that this is =
theirbug,>=20
      so I'll leave it at that.>>
"Robert Comer" <bobcomer{at}mindspring.com>=20">mailto:bobcomer{at}mindspring.com">bobcomer{at}mindspring.com>=20
      wrote in message> news:3e99778f{at}w3.nls.net...>=
=20
      > Which version of OE and OS btw.>
>> > - =
Bob=20
      Comer> >>
>> > "Randy H" <randy_holcomb{at}attglobal.netmailto:randy_holcomb{at}attglobal.net">randy_holcomb{at}attglobal.net
A>>=20
      wrote in message> > news:3e99714f{at}w3.nls.net...>=
=20
      > > Toggle it back and forth twice, then go in and make some =

      changes.> > >>
> > Boom.> >=20
      >> > > "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote in=20
      messagenews:3e99615a$1{at}w3.nls.net...=
>=20
      > > > I do that all the time without
problem.> =
> >=20
      >> > > >
Geo.> > > >> =
> >=20
      > "Randy H" <randy_holcomb{at}attglobal.netmailto:randy_holcomb{at}attglobal.net">randy_holcomb{at}attglobal.net
A>>=20
      wrote in message> > > > news:3e98fad1$1{at}w3.nls.net...=
>=20
      > > > > It may be able to view source without =
imploding, but I=20
      can crashOE> > > >
> with impunity just by =
toggling=20
      between plain-text and HTML when> > >
> > =
sending a new=20
      message.> > > >
>> > > > > =
No fix as=20
      of yet.> > >
>> > > >>
> =

      >> > >>
>>=20
    =
>>>

------=_NextPart_000_0678_01C302D5.AB990E10--

--- BBBS/NT v4.01 Flag-4