From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0632_01C30273.5A28E530
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   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_0632_01C30273.5A28E530
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable









   OCA applies = to system=20
crashes not app crashes so a buggy driver is likely.  That = Microsoft=20
acknowledged it as a Microsoft bug is suspicious.  I've not seen =
a\language=20
like that but I've rarely seen OCA use because I'm conservative =
drivers. =20
My guess is that it is an identified problem but that it is likely a = third party=20
driver for which the third party hasn=92t provided an update.  I'd
= expect the=20
crash and/or OCA to identify the specific driver.
 
   A corrupt or=20 invalid font
is also interesting suggestion but that would presume = that you=20
have changed the default font settings.
 
Rich
 

  "Robert Comer" <bobcomer{at}mindspring.com>">mailto:bobcomer{at}mindspring.com">bobcomer{at}mindspring.com>
= wrote in=20
  message news:3e9989c7$1{at}w3.nls.net...Looks=20
  about the same as mine. (except the last 4 of OE is .1106, not =
.106I=20
  really suspect a corrupt font on yours.> When
I looked at =
the OCA=20
  message, MSFT acknowledged that this is
theirbug,> so I'll =
leave it=20
  at that.Interesting -- it doesn't always happen that way on =
all PC's=20
  obviously.  Isuppose it could be a driver
problem.- =
Bob Comer=20
  <just toggled it over 10 times and added this and then =
i'lltoggle it=20
  one more 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 at=20
  the OCA message, MSFT acknowledged that this is
theirbug,> =
so I'll=20
  leave it at that.>> "Robert
Comer" <bobcomer{at}mindspring.com>">mailto:bobcomer{at}mindspring.com">bobcomer{at}mindspring.com>
= wrote in=20
  message> news:3e99778f{at}w3.nls.net...>=
 >=20
  Which version of OE and OS btw.>
>> > - Bob =
Comer>=20
  >> >> >
"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.>=20
  > >> > >
Boom.> > >> >
> =
"Geo."=20
  <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 can=20
  crashOE> > > > >
with impunity just by toggling =
between=20
  plain-text and HTML when> > > >
> sending a new=20
  message.> > > >
>> > > > > No =
fix as of=20
  yet.> > > >>
> > >> > =
>>=20
  > >> >>=20
>>>

------=_NextPart_000_0632_01C30273.5A28E530--

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