FP2000 Crashing HELP!

[Bill]

I've been getting this error message in FrontPage 2000, occasionally when editing,
usually whenever I try to save:

FRONTPG caused an invalid page fault in
module KERNEL32.DLL at 0167:bff9db61.

I did do a web search on this & came up with nothing useful. Detect & Repair on FP2000
did nothing. All other Office 2000 programs run fine.

When the error comes up, clicking "close" won't let it go away - the dialog always comes
back, and I have to ungracefully shut down the computer

The computer is a solid performer, Win98SE, IE6, 576M RAM, well maintained & absolutely
free of spyware and viruses.(thanks to Spybot & V-COM).

This silly error occurs so often, FP2000 is pretty much unusable - HELP!!!

 

[Guest]

There is a known issue with local cache file corruption in some versions of
FrontPage. Look for files with .web and delete them in your sites (using
Windows Explorer). Best to backup (copy and store elsewhere) just in case
this is not your issue.

Other possibilities include virii, spyware and other items that can affect
Kernel32. FrontPage, in these cases, is the catalyst, not the problem. Also,
are you up to date with the latest patches for Windows and Office?

http://windowsupdate.microsoft.com
http://office.microsoft.com/en-us/officeupdate/default.aspx


--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

 

[Bill]

I did as you suggested and deleted the .web file for one web that was crashing. I also
deleted the file cmdui.prf (recommended based on a web search I did).

Problem appears to be solved to far!

Are .web files cache files? If so, wouldn't it be safe to clear out my FP temporary
files and then manually delete all my .web files?

Thanks so much!

Bill.

 

[Thomas A. Rowe]

You delete them daily, if you want. Just make sure FP is closed.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================