OE 6 Hangs when opened

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Kathy (kdrusso_at_hotmail.com)
Date: 04/17/04


Date: Sat, 17 Apr 2004 12:49:07 -0700

Every once in awhile I have a problem with OE opening. In
the past after much trial and error, I ended up re-
installing IE 6 and everything was fine. I chalked it up
to a corrupt or missing file. Well, this time that fix and
other attempts are not working at all.

When I click to open OE it starts to open, shows the name
of the account with the message board, but the hourglass
just hangs and doesn't actually open the program all the
way. Any ideas??? I have Windows 98 SE.

Thanks for any help.
Kathy



Relevant Pages

  • RE: ASP.net version mismatch after installing vstudio 2005
    ... you're getting some problems opening a ASP.NET ... > VS.NET 2003 need some certain setting and services in IIS (such as front ... > Microsoft Online Support ... ASP.net version mismatch after installing vstudio 2005 ...
    (microsoft.public.vsnet.general)
  • Re: Making Linux Easy for Newbies
    ... At least GNU/Linux is stable and not easily forthcoming with the BSODs ... wipe out Mepis and play with it for awhile. ... as far as installing new software, but it'll be fun to plat with something ... the only real problem I have with Linux is that if a program I ...
    (alt.os.linux)
  • rpm segmentation fault (kernel 2.6.6-1.398)
    ... opening db environment /var/lib/rpm/Packages joinenv ... but got another segmentation fault. ... problems after installing arjanv's 2.6.6-1.406. ... The rpm install of the ...
    (Fedora)
  • Re: debian bsdgames emacs packages conflict
    ... usually means that dpkg or another apt tool is already installing ... Opening in read-only mode; any changes you make to the states ... of packages will NOT be preserved! ...
    (Debian-User)
  • Re: accessing my website through frontpage
    ... Are you opening your FP site using File Open Site ... Before opening a page to edit in FP? ... Before re installing front page, I always had to log on ...
    (microsoft.public.frontpage.client)