Results 1 to 3 of 3
  1. #1
    2 Star Lounger
    Join Date
    May 2002
    Location
    Londonderry, Ireland, Northern
    Posts
    159
    Thanks
    9
    Thanked 0 Times in 0 Posts

    spool32.exe trouble

    W98 SE I went to bed leaving a four-page job printing. This morning only the first page had printed. Now every print job I load results in an error message to the effect that Spool32 has attempted an illegal operation and will be closed down. That includes the printer utility to clean print heads. The one exception is an MSDOS command [copy con prn ^M ^L^Z ^M] which is quietly ignored, presumably because it's outside Windows and so it can't call a Windows error message.

    In my attempts at troubleshooting I have checked the cable ends are firmly engaged, re-installed the printer (Epson Stylus Color 460) after it ran its performance check OK when isolated from the computer. I have Extracted spool32 from the CD-Rom file WIN98 WIN98-46.CAB to the right place in the WindowsSystem directory, overwriting the troublesome one in case of corruption on the hard disk . All with the same results as before.
    All help gratefully received!

  2. #2
    Uranium Lounger
    Join Date
    Dec 2000
    Location
    Los Angeles Area, California, USA
    Posts
    7,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: spool32.exe trouble

    You might try the steps listed in http://support.microsoft.com/default.aspx?...b;EN-US;Q191949 for troubleshooting Spool32 error messages. You might also try booting to DOS (not a DOS window) & typing:
    smartdrv.exe<enter>
    scanreg /fix /opt

    & see if that helps. When the screen finishes, you'll have to type "exit" (no quotes) to reboot.

  3. #3
    2 Star Lounger
    Join Date
    May 2002
    Location
    Londonderry, Ireland, Northern
    Posts
    159
    Thanks
    9
    Thanked 0 Times in 0 Posts

    Re: spool32.exe trouble

    Thank you Phil.
    I tried both tacks. It seems there was some repair work need at the Registry, but unrelated to the printer problem.
    With the Clean Boot, we eliminated the page fault attribution to spool32.exe, but the printer still wasn't responding to the computer at all. Perhaps spool32 was taking the blame for a hardware problem. I'm about to test another cable.
    All help gratefully received!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •