Mapped Network Printer to LPT1 hanging programs

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

We have several computers running Windows XP (Home and Pro) networked to a
file server running Windows 2000 Server. All critical updates have been
applied to the desktop computers since SP2.

We have some older programs (DOS and Windows 3x based) that rely on printing
to LPT1. All printers are networked. Up through this spring, this has been
working fine using

NET USE LPT1 \\servername\printername

In the past couple of months, some critical update has fouled up all efforts
to print to these printers. When you invoke printing to the mapped LPT1,
the program just hangs; if try to close, get the "Generic Host Process"
error upon exact every once in a while.

Has anyone else been running into this problem with recent critical updates?

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Not sure if you read my post or not. I've been mapping printers for almost
4 years in XP; some Critical Update in the last 4 months is causing the map
to not work anymore.

"Cari (MS-MVP)" <Newsgroups1@coribright.com> wrote in message
newsjJGkmWuFHA.3528@TK2MSFTNGP15.phx.gbl...
> See:
> http://members.shaw.ca/bsanders/printfromdos.htm
> --
> Cari (MS-MVP)
> Printing & Imaging
>
>
>
> "Michael Wyatt" <mwyatt@afcpensions.com> wrote in message
> news:2e6dnbmXc-9s2bXeRVn-gg@conversent.net...
>> We have several computers running Windows XP (Home and Pro) networked to
>> a file server running Windows 2000 Server. All critical updates have
>> been applied to the desktop computers since SP2.
>>
>> We have some older programs (DOS and Windows 3x based) that rely on
>> printing to LPT1. All printers are networked. Up through this spring,
>> this has been working fine using
>>
>> NET USE LPT1 \\servername\printername
>>
>> In the past couple of months, some critical update has fouled up all
>> efforts to print to these printers. When you invoke printing to the
>> mapped LPT1, the program just hangs; if try to close, get the "Generic
>> Host Process" error upon exact every once in a while.
>>
>> Has anyone else been running into this problem with recent critical
>> updates?
>>
>
>

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

See if the information in http://support.microsoft.com/?scid=kb;en-us;832219
helps.

See also http://support.microsoft.com/?scid=kb;en-us;891861 - updated
version of the Update Rollup 1 for 2000 SP4.

I suggest you contact Microsoft Product Support Services
http://support.microsoft.com/oas/d [...] &x=8&y=10.
Any issue with a security patch is a free call.

--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"Michael Wyatt" <mwyatt@afcpensions.com> wrote in message
news:YuGdnZ24m7RiFbXeRVn-pQ@conversent.net...
> Not sure if you read my post or not. I've been mapping printers for
> almost 4 years in XP; some Critical Update in the last 4 months is causing
> the map to not work anymore.
>
> "Cari (MS-MVP)" <Newsgroups1@coribright.com> wrote in message
> newsjJGkmWuFHA.3528@TK2MSFTNGP15.phx.gbl...
>> See:
>> http://members.shaw.ca/bsanders/printfromdos.htm
>> --
>> Cari (MS-MVP)
>> Printing & Imaging
>>
>>
>>
>> "Michael Wyatt" <mwyatt@afcpensions.com> wrote in message
>> news:2e6dnbmXc-9s2bXeRVn-gg@conversent.net...
>>> We have several computers running Windows XP (Home and Pro) networked to
>>> a file server running Windows 2000 Server. All critical updates have
>>> been applied to the desktop computers since SP2.
>>>
>>> We have some older programs (DOS and Windows 3x based) that rely on
>>> printing to LPT1. All printers are networked. Up through this spring,
>>> this has been working fine using
>>>
>>> NET USE LPT1 \\servername\printername
>>>
>>> In the past couple of months, some critical update has fouled up all
>>> efforts to print to these printers. When you invoke printing to the
>>> mapped LPT1, the program just hangs; if try to close, get the "Generic
>>> Host Process" error upon exact every once in a while.
>>>
>>> Has anyone else been running into this problem with recent critical
>>> updates?
>>>
>>
>>
>
>