Frequently upon boot-up AOL (loading of aol.exe) produces an error and says
that it must close down. A huge error report is produced, a text file of
about 230K. A typical file name would be "fofd_appcompat.txt". The report
means little to me as I am not a programmer. Since AOL will not help, do I
have any options for getting help? Sending the error report to Microsoft,
as suggested in the error message, has never resulted in any feedback.

More info on problem. Using "Event Viewer" I have found that the faulting
application is aolsoftware.exe and the faulting module is usually one of the
following: bfts.dll, xprt6.dll or msvcrt.dll. Any clue here?

"PSRumbagh" wrote:

> Frequently upon boot-up AOL (loading of aol.exe) produces an error and says
> that it must close down. A huge error report is produced, a text file of
> about 230K. A typical file name would be "fofd_appcompat.txt". The report
> means little to me as I am not a programmer. Since AOL will not help, do I
> have any options for getting help? Sending the error report to Microsoft,
> as suggested in the error message, has never resulted in any feedback.

PSRumbagh wrote:
> More info on problem. Using "Event Viewer" I have found that the faulting
> application is aolsoftware.exe and the faulting module is usually one of the
> following: bfts.dll, xprt6.dll or msvcrt.dll. Any clue here?
>
> "PSRumbagh" wrote:
>
>> Frequently upon boot-up AOL (loading of aol.exe) produces an error and says
>> that it must close down. A huge error report is produced, a text file of
>> about 230K. A typical file name would be "fofd_appcompat.txt". The report
>> means little to me as I am not a programmer. Since AOL will not help, do I
>> have any options for getting help? Sending the error report to Microsoft,
>> as suggested in the error message, has never resulted in any feedback.


I'm afraid you'll need to contact AOL's tech support for resolution of
problems with -- or caused by -- their product; Microsoft has no control
over AOL's product quality, or lack thereof. You best course of action
would be to remove it.

Sadly, the only practical way I've ever found to completely remove
AOL from an operating system is to format the hard drive and perform a
clean installation. I absolutely loathe having to resort to a hard
drive format to fix what should be a relatively minor issue, but it
takes a lot less time than manually removing/replacing all of the
Windows system files that AOL replaces with their own versions and the
hundreds of unnecessary registry entries.

(AOL's historical inability and unwillingness to support its own
product has become something of a legend, nowadays. I can honestly say
that I've never met any AOL customer who has ever had anything good to
say about them.)


--

Bruce Chambers

Help us help you:
http://www.catb.org/~esr/faqs/smart-questions.html

http://support.microsoft.com/default.aspx/kb/555375

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin

Many people would rather die than think; in fact, most do. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot

Do a search on remove and reinstall aol software on the net

"PSRumbagh" wrote:

> More info on problem. Using "Event Viewer" I have found that the faulting
> application is aolsoftware.exe and the faulting module is usually one of the
> following: bfts.dll, xprt6.dll or msvcrt.dll. Any clue here?
>
> "PSRumbagh" wrote:
>
> > Frequently upon boot-up AOL (loading of aol.exe) produces an error and says
> > that it must close down. A huge error report is produced, a text file of
> > about 230K. A typical file name would be "fofd_appcompat.txt". The report
> > means little to me as I am not a programmer. Since AOL will not help, do I
> > have any options for getting help? Sending the error report to Microsoft,
> > as suggested in the error message, has never resulted in any feedback.

PSRumbagh wrote:
> More info on problem. Using "Event Viewer" I have found that the faulting
> application is aolsoftware.exe and the faulting module is usually one of the
> following: bfts.dll, xprt6.dll or msvcrt.dll. Any clue here?
>
> "PSRumbagh" wrote:
>
>> Frequently upon boot-up AOL (loading of aol.exe) produces an error and says
>> that it must close down. A huge error report is produced, a text file of
>> about 230K. A typical file name would be "fofd_appcompat.txt". The report
>> means little to me as I am not a programmer. Since AOL will not help, do I
>> have any options for getting help? Sending the error report to Microsoft,
>> as suggested in the error message, has never resulted in any feedback.

There is a generic help page here.

http://help.channels.aol.com/kjump.adp?articleId=223707

Paul

PSRumbagh wrote:
> Frequently upon boot-up AOL (loading of aol.exe) produces an error and says
> that it must close down. A huge error report is produced, a text file of
> about 230K. A typical file name would be "fofd_appcompat.txt". The report
> means little to me as I am not a programmer. Since AOL will not help, do I
> have any options for getting help? Sending the error report to Microsoft,
> as suggested in the error message, has never resulted in any feedback.

Do yourself a favor and format your hard drive, reinstall XP and DON'T
reinstall AOL.

--
C

Can't get individual technical help from AOL because I am no longer a paying
customer. Received lifetime "FREE" AOL limited service as an inducement to
go with Charter Cable internet service back in October 2006. In May 2007 AOL
said no more custom help for non-payers.

Amen to your comment about AOL's lousy service and software. AOL needs a
lawsuit to force them to produce a complete and thorough un-install program
that removes all vestiges of AOL including Registry entries.

"Bruce Chambers" wrote:

> PSRumbagh wrote:
> > More info on problem. Using "Event Viewer" I have found that the faulting
> > application is aolsoftware.exe and the faulting module is usually one of the
> > following: bfts.dll, xprt6.dll or msvcrt.dll. Any clue here?
> >
> > "PSRumbagh" wrote:
> >
> >> Frequently upon boot-up AOL (loading of aol.exe) produces an error and says
> >> that it must close down. A huge error report is produced, a text file of
> >> about 230K. A typical file name would be "fofd_appcompat.txt". The report
> >> means little to me as I am not a programmer. Since AOL will not help, do I
> >> have any options for getting help? Sending the error report to Microsoft,
> >> as suggested in the error message, has never resulted in any feedback.
>
>
> I'm afraid you'll need to contact AOL's tech support for resolution of
> problems with -- or caused by -- their product; Microsoft has no control
> over AOL's product quality, or lack thereof. You best course of action
> would be to remove it.
>
> Sadly, the only practical way I've ever found to completely remove
> AOL from an operating system is to format the hard drive and perform a
> clean installation. I absolutely loathe having to resort to a hard
> drive format to fix what should be a relatively minor issue, but it
> takes a lot less time than manually removing/replacing all of the
> Windows system files that AOL replaces with their own versions and the
> hundreds of unnecessary registry entries.
>
> (AOL's historical inability and unwillingness to support its own
> product has become something of a legend, nowadays. I can honestly say
> that I've never met any AOL customer who has ever had anything good to
> say about them.)
>
>
> --
>
> Bruce Chambers
>
> Help us help you:
> http://www.catb.org/~esr/faqs/smart-questions.html
>
> http://support.microsoft.com/default.aspx/kb/555375
>
> They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety. ~Benjamin Franklin
>
> Many people would rather die than think; in fact, most do. ~Bertrand Russell
>
> The philosopher has never killed any priests, whereas the priest has
> killed a great many philosophers.
> ~ Denis Diderot
> .
>