Re: Lexmark 3150
gch_at_ggi.ca
Date: 04/20/04
- Next message: Cynthia: "runtime error"
- Previous message: Healey: "Re: Random BSOD's"
- In reply to: William Wang[MSFT]: "RE: Lexmark 3150"
- Next in thread: William Wang[MSFT]: "Re: Lexmark 3150"
- Reply: William Wang[MSFT]: "Re: Lexmark 3150"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 20 Apr 2004 11:06:33 -0400
as stated I put the msg here because this is one of the managed groups; I'll
continue the thread in print_fax
"William Wang[MSFT]" <v-rxwang@online.microsoft.com> wrote in message
news:UrSLcNqJEHA.3564@cpmsftngxa10.phx.gbl...
> The issue is possible caused by some corruption of
> the print job in memory on the computer, or
> corruption in the spool file. It is sometimes
> possible to clear the queue by restarting the Spooler
> service. If that does not correct the issue, then the
> computer should be rebooted to clear the memory
> segment being used to store the print job.
>
> To restart the Spooler service, follow these steps:
>
> 1. To stop the Spooler service, type the following
> command at the command prompt, and then press ENTER:
>
> "NET STOP SPOOLER" (without the quotation marks)
>
> 2. To start the Spooler service again, type the
> following command at the command prompt, and then
> press ENTER:
>
> "NET START SPOOLER" (without the quotation marks)
>
>
> I agree with Cari that we continue to work on this
> issue in the appropriate newsgroup -
> microsoft.public.windowsxp.print_fax. I've also
> noticed that Cari has already replied to your thread
> and that you are going to try the suggestions
> provided by Lexmark. If you would, let's focus on
> that thread so that we can concentrate fully on your
> issue.
>
> Sincerely,
>
> William Wang
> Microsoft Online Support Engineer
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> =====================================================
>
> This posting is provided "AS IS" with no warranties,
> and confers no rights.
> --------------------
> >From: <gch@ggi.ca>
> >Subject: Lexmark 3150
> >Date: Fri, 16 Apr 2004 11:02:31 -0400
> >Lines: 49
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express
> 6.00.2800.1409
> >X-MimeOLE: Produced By Microsoft MimeOLE
> V6.00.2800.1409
> >Message-ID: <#WX0YP8IEHA.3840@TK2MSFTNGP11.phx.gbl>
> >Newsgroups: microsoft.public.windowsxp.hardware
> >NNTP-Posting-Host: unnassigned-83-230.tht.net
> 216.126.83.230
> >Path:
> cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11
> phx.gbl
> >Xref: cpmsftngxa06.phx.gbl
> microsoft.public.windowsxp.hardware:201584
> >X-Tomcat-NG: microsoft.public.windowsxp.hardware
> >
> >posted this in xp print_fax but as this is a managed
> newsgroup I'll put it
> >here too
> >
> >Installed XP ProSP1 from the ground up on new
> hardware (Intel 865 chipset),
> >all post sp critical hotfixes installed. Then
> installed a Lexmark 3150 per
> >the Lexmark instructions (i.e. cancelled all the
> 'found new...' messages).
> >Everything went smoothly, no problems, printer
> prints, scans, faxes, does
> >OCR and all that wonderful stuff.
> >
> >However, when I print the job won't delete from the
> spool after printing is
> >complete, it just sits there with the status message
> 'deleting'. To get the
> >job to delete I have to cycle the printer (this
> works most of the time,
> >sometimes I have to stop the spooler, delete the spl
> files then boot).
> >
> >Needless to say I think this is a stupid solution
> (the Lexmark tech support
> >people appear to think this is a good solution as
> this is what they've
> >advised me to do - hard to believe that they'd see
> that as a solution but go
> >figure <hey, some people think the earth is flat so
> what can I say?>).
> >
> >I've reinstalled many times (even followed the
> instructions from the guy at
> >shaw.ca) and run into the same problem - I'm
> starting to get really p*&%$d
> >with it. In fact one of the reasons for installing
> on new hardware was the
> >thought that my old hardware was the source of the
> problem - silly me (at
> >least I ended up with a faster box).
> >
> >I note that in the advice tendered here we're told
> to not connect the
> >printer until told to do so by the installation
> program. This is not what
> >the Lexmark guides say (they say: connect printer,
> ignore detections,
> >install from supplied CD). In fact if you wait for
> the install to ask for
> >the printer to be connected you'll wait a long time
> because it never does -
> >in addition at one point it tries to install the fax
> software but that fails
> >because (you guessed it) it can't detect a printer;
> this kills the whole
> >install and you've really got a mess on your hands.
> >
> >I see similar kinds of problems (but not quite like
> this) reported in the
> >print_fax group but there appears to be a lack of
> solid solutions. Could
> >this be USB related (I've a satellite modem and
> mouse on usb as well as the
> >printer) or
> >has Lexmark sold me junky hardware and/or software?
> >
> >Perhaps the problem resides in the 'all-in-one'
> software from Lexmark (it
> >creates many services) so I'd like to try to just
> install the printer
> >drivers and the twain driver and leave the Lexmark
> stuff (s***t?) out but
> >it's not clear to me which files go where - any
> advice on how to do that
> >would be appreciated.
> >
> >ta!
> >
> >
> >
>
- Next message: Cynthia: "runtime error"
- Previous message: Healey: "Re: Random BSOD's"
- In reply to: William Wang[MSFT]: "RE: Lexmark 3150"
- Next in thread: William Wang[MSFT]: "Re: Lexmark 3150"
- Reply: William Wang[MSFT]: "Re: Lexmark 3150"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
