>
> Hi,
> Well some progress has been made so I thought I would update this post
> in case anyone else experiences similar problems.
>
> Onenote screen clipping is now working for me!
>
> I experienced a BSOD after which all my firefox profile settings were
> screwed. I then discovered that when I tried to customise my toolbars,
> as soon as I clicked on 'customise', the customisation pop-up appeared
> for about 2-3 seconds and then FF crashed.
> I decided to completely reinstall FF. I uninstalled then installed the
> latest version downloaded from Mozilla. No joy. Still getting crashes
> when attempting to customise the toolbar. A bit of searching turned up
> this on 'Basic Troubleshooting'
> (
http://support.mozilla.com/en-US/kb/Basic+Troubleshooting)> "Some malware programs may target the Firefox application file. The
> following instructions may help diagnose such a problem:
>
> - From the menu at the top of the Firefox windowbar, select
> FileFirefox and then select the ExitQuit FirefoxQuit menu item.
> - Open the Firefox application folder - by default, it is:
> C:\Program Files\Mozilla Firefox.
> - Rename firefox.exe to firefox1.exe.
> - Double-click firefox1.exe to launch Firefox.
> - If Firefox runs without problems, some malicious code may be
> targeting Firefox (firefox.exe). Scan your computer for malicious
> code using the links above or your own antivirus or antispyware
> program."
>
> So I tried renaming to firefox1.exe as suggested and bingo! No crashes
> when customising the toolbar. So I ran Spybot S&D and Adaware (I fairly
> regularly run S&D but had not run Adaware for some time). Nothing
> untoward showed up with S&D but Adaware showed an infection by
> Win32.backdoor.bifrose which I then removed. Still no joy. FF still
> crashes when I try to customise the toolbar when running as
> firefox1.exe but not when running as firefox.exe.
>
> It was then that I tried Onenote screen clipping again and found that
> now it works. So I don't know whether it was the removal of bifrose or
> the reinstall of FF that cured it, but cured it seems to be. But I now
> have a different problem which I will post separately.
>
>
> --
> pridout