From: "Robert Comer" 

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.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

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