RE: Problems Printing After XP Upgrade from 98SE

Ken,
I've done the net use /persistent=yes, and I can get everything to print.
The real problem is that after printing perfectly for a while, it seems like
until a power down possibly, then jobs enter the que, but don't print.

In addition to not printing, the jobs multiply. For example if you delete
all of the jobs from the queue and print a test page from XP, from either the
workstation that is directly connected to the printer, or one that is using
it accross the network, as soon as the test page enters the queue and goes to
the printing state, another one enters the queue in the spooling state.

Eventually the queue fills with hundreds of jobs that do not print.

I resolved the problem yesterday by: clearing the queue, deleting the queue,
removing the driver from the server, re-starting the workstation and let it
discover the printer and load the software on it's own.

This morning I was called and told that it has the same error! I talked the
staff through the above steps and it works fine again.

Manually installing the printer failed to fix the problem yesterday. It had
to be installed automatically to work. Also the new driver on HP's site did
not work.

Once again, the problem isn't that I can't ever get it to print, but rather
it works for a while and then goes nuts.

I hope this clarifies exactly what's happening.

Thanks

--
JE


"Ken Zhao [MSFT]" wrote:

> Hi Jeff,
>
> Thank you for using newsgroup!
>
> First, I want to appreciate all valuable input above. Thanks!
>
> For your issue, based on my research, by default, most MS-DOS-based
> programs print directly to either the LPT1 port or to the LPT2 port.
> However, the output is not automatically routed across a redirector to a
> print share unless you use one of the following methods.
>
> Method 1 (Ortega has mentioned)
> ===============
> Use the net.exe command to establish a persistent connection. To do this,
> use the following syntax at a command prompt
> net use lptx \\printserver\sharename /persistent:yes
> where x is the number of the printer port that you want to map, where
> printserver is the print server that is sharing the printer, and where
> sharename is the name of the printer share.
>
> For example, to map LPT1 to a printer shared as Laser1 on a print server
> that is named Pserver, follow these steps:
> 1. Click Start, and then click Run.
> 2. In the Open box, type cmd, and then click OK.
> 3. Type net use lpt1 \\pserver\laser1 /persistent:yes, and then press
> ENTER.
> 4. To quit the command prompt, type exit, and then press ENTER.
> Note: In Windows XP, non-administrative users cannot map an LPT port to a
> network printer path when the LPT port exists on the computer as a physical
> parallel port.
> 313644: Non-administrators cannot remap an LPT port to a network printer
> http://support.microsoft.com/kb/313644/
>
> Method 2
> ===============
> Print directly to the printer share by using the following syntax at a
> command prompt
> print /d:\\printserver\sharenamedrive:\path\filename
> where printserver is the print server sharing the printer, where sharename
> is the name of the printer share, and where drive:, path, and filename make
> up the complete path of the document that you want to print.
>
> For example, to print a document that is named letter.doc from the root
> directory of drive C to a printer shared as Laser1 on a print server that
> is named Pserver, follow these steps:
> 1. Click Start, and then click Run.
> 2. In the Open box, type cmd, and then click OK.
> 3. Type print /d:\\pserver\laser1 c:\letter.doc, and then press ENTER.
>
> The following command-line message appears:
> C:\letter.doc is currently being printed
> 4. To quit the command prompt, type exit, and then press ENTER.
> Because Novell NetWare's CAPTURE command is not supported in Windows XP,
> use the following command to map the LPT port to a Novell NetWare print
> queue:
> net use lptx \\server\queue
> If the LPT port is redirected successfully, you receive the following
> message:
> The command completed successfully.
> To disconnect persistent LPTx connections, use the following syntax:
> net use lptx /delete
>
> More detailed information, please refer to the article:
> 314499: How to print to a network printer from an MS-DOS-based program in
> Windows XP
> http://support.microsoft.com/default.aspx?scid=kb;en-us;314499
>
> I hope the information helps!
>
> Best regards,
>
> Ken Zhao
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
>
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
>
> If you are outside the United States, please visit our International
> Support page: http://support.microsoft.com/common/international.aspx.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> --------------------
> | Thread-Topic: Problems Printing After XP Upgrade from 98SE
> | thread-index: AcWGS7h9Il7DmvqiS5G4a34xQlAKZg==
> | X-WBNR-Posting-Host: 24.207.207.56
> | From: =?Utf-8?B?amU3Mzgz?= <Jeff7383@xxxxxxxxxxxxxx>
> | References: <D2B400BD-7307-4578-9608-36346E5ADF8F@xxxxxxxxxxxxx>
> <8AC2EB48-1B7C-48E9-9BC4-1E6FF5570505@xxxxxxxxxxxxx>
> | Subject: RE: Problems Printing After XP Upgrade from 98SE
> | Date: Mon, 11 Jul 2005 12:07:02 -0700
> | Lines: 39
> | Message-ID: <EFE10F95-D0EA-42A8-A5CD-F5867A92193D@xxxxxxxxxxxxx>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.windowsxp.help_and_support
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.windowsxp.help_and_support:160947
> | X-Tomcat-NG: microsoft.public.windowsxp.help_and_support
> |
> | Thanks, but it's a printer connected to LPT1: of the host machine.
> | --
> | JE
> |
> |
> | "Byte" wrote:
> |
> | > May find some help here.
> | > Print From DOS with WindowsXP
> | > http://members.shaw.ca/bsanders/printfromdos.htm
> | > --
> | > Some days you're the windshield,
> | > some days you're the bug.
> | >
> | >
> | > "je7383" wrote:
> | >
> | > > I have a client whom I recently upgraded to XP from 98SE. Their
> primary
> | > > application is a DOS application, and their primary printer is a
> shared
> | > > Laserjet 6p. They are on a peer to peer network.
> | > >
> | > > After the upgrade, at first, test pages printed from all workstations
> as
> | > > expected. Upon attempting to print from the DOS application (Foxpro
> 2.5 I
> | > > believe), A print job would show up in the queue, then disappear
> without
> | > > printing, then more jobs would be added continuously. Hundreds of
> jobs would
> | > > stack up very quickly.
> | > >
> | > > I resolved the problem by deleting the print queue and the drivers
> from the
> | > > server then re-installing. This solved the problem for about one
> week, then
> | > > the problem re-appeared.
> | > >
> | > > I then tried using the newest driver on the HP web site. The same
> problem
> | > > occurred. Next I deleted the queue and drivers again and re-added
> using the
> | > > XP driver again. This solved the problem but I don't know for how
> long or
> | > > what causes it to re-appear.
> | > >
> | > > Any thoughts would be greatly appreciated.
> | > > --
> | > > JE
> |
>
>
.

Relevant Pages

  • [SLE] N-up printing in KDE with Cups, OpenOffice, etc (was Re: [SLE] pdf booklet)
    ... > to buy adobe acrobat? ... CUPS N-Up printing, or specifically 4-up printing selected from the ... Click the "Add filter" button - it looks like a funnel. ... Command"), and then click the "Edit Command" button on the "Command edit ...
    (SuSE)
  • RE: Problems Printing After XP Upgrade from 98SE
    ... Use the net.exe command to establish a persistent connection. ... network printer path when the LPT port exists on the computer as a physical ... Because Novell NetWare's CAPTURE command is not supported in Windows XP, ... Microsoft Online Partner Support ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Get RAW Bitmap Data from a file
    ... Posiflex uses the Epson command set). ... I am using code from this MS Knowledgebase that allows printing RAW ... the Epson command to turn on Define Graphic Download). ... Any other format, even DONTCARE fails with ...
    (microsoft.public.dotnet.languages.vb)
  • Re: scheduled printing of a text file using batch files
    ... this would be a scheduled task question rather than a printing question. ... have never used the schtasks command. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Printing on a thermal printer
    ... I use a lot of Thermal Printers for labelling applications and have had the ... spooler API's and allows me to send command directly to the printer in its ... Simply set the printer name to the name of any installed windows ... actually control the printing of pages as the driver is being bypassed, ...
    (microsoft.public.dotnet.framework)