You're printing a document from Firefox? Please give more details. Is the printer set up as the default printer for this PC? If not, you need to establish a physically connection for the printer (to the PC, to the router, or is it wireless?) and then click on Start, Devices and Printers to establish the setup and have the printer recognized as the default device. You may need to reboot your PC, or restart whatever program you're printing from.

with zone alarm you usually have the option to un check any of the add ons prior to the install. But it has been added to the hall of shame for now having a pre selected item in the install procedure. Installers Hall of Shame (Unwanted add-on) always a good place to check

Hi Zep, Here's the information from the Whocrashed report. System Information (local) -------------------------------------------------------------------------------- computer name: LYNNDELL windows version: Windows XP Service Pack 3, 5.1, build: 2600 windows dir: C:\WINDOWS Hardware: Inspiron 530, Dell Inc., 0FM586 CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 2950799360 total VM: 2147352576, free: 2022486016 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Tue 6/10/2014 9:46:41 PM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini061014-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x5FC9E) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF85FC9E, 0xFFFFFFFFADB9BAE4, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- One crash dump has been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. ------------------------------------------------------------ I'll try reinstalling Firefox, but I'm doubtful because during the course of today - after my initial Firefox difficulties, I did update from Firefox 29 to Firefox 29.0.1. So I can re-install 29.0.1, but installing it this afternoon did not fix the problem. I'll check back later. And now I'll reinstall. Thank you. Lynn.

The difference between success and failure could still be the browsers. IE is more intensive on resources than FF. If you feel like experimenting do a C-A-D and end everything but Explorer and System Tray. Then try IE and shutdown. What brand is the system? HP at one time had a sound driver/Win98 conflict with shutdown. You might want to try the Windows 98 Help search word "troubleshoot" (sans quotes). Without going out to the garage to verify, my recollection is there is a Startup and Shutdown troubleshooter in Win98. Also, my recollection is SFC will identify changed and corrupt files, but unless you can find the specific file in the Windows .inf folder you will need a Win98 disk to extract it from to repair. All over the map here, just trying to come up with an answer. DA