Discussion:
VBDOS program doesn't print from DOS window in XP
(too old to reply)
Stan Hilliard
2005-09-14 21:25:21 UTC
Permalink
I have a legacy program written in VBDOS that runs in a DOS window.
One of my customers using Windows XP can't print. The attempt to print
just hangs the DOS window.

The internal code is like
OPEN "O", #1, "PRN"
PRINT #1, etc.

It has printed from windows 98 and 2000. Could it be windows XP
related?

It is not practical to change the program. (The program seems to work
well in XP otherwise.)

What could be the problem?

Help will be appreciated.
Ken Halter
2005-09-14 21:47:44 UTC
Permalink
Post by Stan Hilliard
I have a legacy program written in VBDOS that runs in a DOS window.
One of my customers using Windows XP can't print. The attempt to print
just hangs the DOS window.
The internal code is like
OPEN "O", #1, "PRN"
PRINT #1, etc.
It has printed from windows 98 and 2000. Could it be windows XP
related?
It is not practical to change the program. (The program seems to work
well in XP otherwise.)
What could be the problem?
Help will be appreciated.
Is it a networked printer?... or maybe a USB printer? According to "Dir
Help", you can use the following command to send a directory listing to a
printer....

dir > prn

All printers connected here are networked. That command just causes the dos
window to sit and spin since there's nothing connected to LPT1. It doesn't
cause it to hang though.... depending on what your definition of "hangs the
DOS window" is, I suppose <g>

So.... you might try asking that customer to open a dos window and type the
Dir > PRN command to see if anything shows up on the printer.
--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
Please keep all discussions in the groups..
Ralph
2005-09-14 22:35:09 UTC
Permalink
Post by Stan Hilliard
I have a legacy program written in VBDOS that runs in a DOS window.
One of my customers using Windows XP can't print. The attempt to print
just hangs the DOS window.
The internal code is like
OPEN "O", #1, "PRN"
PRINT #1, etc.
It has printed from windows 98 and 2000. Could it be windows XP
related?
It is not practical to change the program. (The program seems to work
well in XP otherwise.)
What could be the problem?
Help will be appreciated.
You need to set up a "DOS Printer" or LPT1:
For networked printers use...
net use LPT1:\\My_Server\Printer
There are various administrative setups that deny certain ports or config
ability.
Get more information from the XP help (Startup->Help).

hth
-ralph
MikeD
2005-09-14 22:58:23 UTC
Permalink
Post by Stan Hilliard
I have a legacy program written in VBDOS that runs in a DOS window.
One of my customers using Windows XP can't print. The attempt to print
just hangs the DOS window.
The internal code is like
OPEN "O", #1, "PRN"
PRINT #1, etc.
It has printed from windows 98 and 2000. Could it be windows XP
related?
It is not practical to change the program. (The program seems to work
well in XP otherwise.)
What could be the problem?
With every new version of Windows, you can expect less and less support for
16 bit apps. You're talking about a DOS app (which WinXP probably suppports
even less than a 16 bit Windows app). It wouldn't surprise me at all that a
DOS app can't print, let alone "see" some printers, particularly newer
printers that use USB. You say it has printed from Win98 and Win2000. On
these systems, what kind of printer is installed? Is this a network printer
and are these Win98 and Win2000 systems on the same network and using the
same printer as the WinXP system that won't print?

IMO, there's no reason to expect a DOS program to work 100% under WinXP. You
might be able to work-around things, but it's probably trial and error and
hacks at best.
--
Mike
Microsoft MVP Visual Basic
Ralph
2005-09-15 12:13:27 UTC
Permalink
Post by MikeD
Post by Stan Hilliard
I have a legacy program written in VBDOS that runs in a DOS window.
One of my customers using Windows XP can't print. The attempt to print
just hangs the DOS window.
The internal code is like
OPEN "O", #1, "PRN"
PRINT #1, etc.
It has printed from windows 98 and 2000. Could it be windows XP
related?
It is not practical to change the program. (The program seems to work
well in XP otherwise.)
What could be the problem?
With every new version of Windows, you can expect less and less support for
16 bit apps. You're talking about a DOS app (which WinXP probably suppports
even less than a 16 bit Windows app). It wouldn't surprise me at all that a
DOS app can't print, let alone "see" some printers, particularly newer
printers that use USB. You say it has printed from Win98 and Win2000. On
these systems, what kind of printer is installed? Is this a network printer
and are these Win98 and Win2000 systems on the same network and using the
same printer as the WinXP system that won't print?
IMO, there's no reason to expect a DOS program to work 100% under WinXP. You
might be able to work-around things, but it's probably trial and error and
hacks at best.
--
Mike
Microsoft MVP Visual Basic
To amplify "DOS" command line commands are not even supported on 64-bit
Windows. I don't know if this is just part of the 'prototype' or if it is a
sign of things to come.

-ralph
H-Man
2005-09-15 21:37:32 UTC
Permalink
Post by MikeD
Post by MikeD
Post by Stan Hilliard
I have a legacy program written in VBDOS that runs in a DOS window.
One of my customers using Windows XP can't print. The attempt to print
just hangs the DOS window.
The internal code is like
OPEN "O", #1, "PRN"
PRINT #1, etc.
It has printed from windows 98 and 2000. Could it be windows XP
related?
It is not practical to change the program. (The program seems to work
well in XP otherwise.)
What could be the problem?
With every new version of Windows, you can expect less and less support
for
Post by MikeD
16 bit apps. You're talking about a DOS app (which WinXP probably
suppports
Post by MikeD
even less than a 16 bit Windows app). It wouldn't surprise me at all that
a
Post by MikeD
DOS app can't print, let alone "see" some printers, particularly newer
printers that use USB. You say it has printed from Win98 and Win2000. On
these systems, what kind of printer is installed? Is this a network
printer
Post by MikeD
and are these Win98 and Win2000 systems on the same network and using the
same printer as the WinXP system that won't print?
IMO, there's no reason to expect a DOS program to work 100% under WinXP.
You
Post by MikeD
might be able to work-around things, but it's probably trial and error and
hacks at best.
--
Mike
Microsoft MVP Visual Basic
To amplify "DOS" command line commands are not even supported on 64-bit
Windows. I don't know if this is just part of the 'prototype' or if it is a
sign of things to come.
-ralph
Currently XP (32bit) emmulates DOS, XP64 does not. I strongly suspect that
this will not change. Solutions abound however with virtualization. Some
time ago MS bought VirtualPC. I would not be at all surprised to find that
in the future, DOS support will come through this scenario. It may require
an additional purchase, or MS might just bundle a very lite version for
legacy support.
--
HK
Ken Halter
2005-09-15 22:01:06 UTC
Permalink
Post by H-Man
Currently XP (32bit) emmulates DOS, XP64 does not. I strongly suspect that
this will not change. Solutions abound however with virtualization. Some
time ago MS bought VirtualPC. I would not be at all surprised to find that
in the future, DOS support will come through this scenario. It may require
an additional purchase, or MS might just bundle a very lite version for
legacy support.
--
HK
VirtualPC 2004's extremely cool. I use it for mostly for testing
InstallShield packages and seeing how my apps work on "other" OSs (running
XP/SP2 with Win2k and/or Win2003 Server and/or NT4 running in VPC windows)
It would be very easy (I assume) to set up a pure DOS VPC.... or, at least a
Win95 VPC.
--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
Please keep all discussions in the groups..
A. David Garza Marín
2005-10-10 00:35:38 UTC
Permalink
Post by Ken Halter
VirtualPC 2004's extremely cool. I use it for mostly for testing
InstallShield packages and seeing how my apps work on "other" OSs (running
XP/SP2 with Win2k and/or Win2003 Server and/or NT4 running in VPC windows)
It would be very easy (I assume) to set up a pure DOS VPC.... or, at least
a Win95 VPC.
Under 64 bits, no 16 bit application will work.
--
A. David Garza Marin
Field Application Engineer
AMD Latin America, LTD
A. David Garza Marín
2005-10-10 00:34:17 UTC
Permalink
Post by Ralph
To amplify "DOS" command line commands are not even supported on 64-bit
Windows. I don't know if this is just part of the 'prototype' or if it is a
sign of things to come.
Err... There is a Console mode in the x64 version of Windows. What cannot
work are 16 bit applications under such an environment.

That is more because the way the processor works under 64 bit mode, and not
because Windows at all.
--
A. David Garza Marin
Field Application Engineer
AMD Latin America, LTD
Ralph
2005-10-10 00:59:32 UTC
Permalink
Post by A. David Garza Marín
Post by Ralph
To amplify "DOS" command line commands are not even supported on 64-bit
Windows. I don't know if this is just part of the 'prototype' or if it
is
Post by A. David Garza Marín
Post by Ralph
a
sign of things to come.
Err... There is a Console mode in the x64 version of Windows. What cannot
work are 16 bit applications under such an environment.
That is more because the way the processor works under 64 bit mode, and not
because Windows at all.
--
A. David Garza Marin
Field Application Engineer
AMD Latin America, LTD
I wondered about that. In the 64-bit 'version' I got to play with basic
commands didn't work or rather there was no obvious way to get to a command
line. The 'help' file said "DOS Commands were no longer supported". It
didn't sound like a good idea. But, Hey, what do I know. <g>

-ralph
Stephen Howe
2005-10-12 02:36:27 UTC
Permalink
Post by Ralph
I wondered about that. In the 64-bit 'version' I got to play with basic
commands didn't work or rather there was no obvious way to get to a command
line. The 'help' file said "DOS Commands were no longer supported". It
didn't sound like a good idea. But, Hey, what do I know. <g>
But what will happen?

Seems to me in the year 2400...

Microsoft will announce Windows Solid Matter 4D version 27.0, runs all
devices you use in real life and full integration with brain with new
emotional sensations, alternative bodies is now standard, virtual sex has
been enhanced with optional male/female aliens, matter teleportation is
fixed this version and no longer kills people at random on use, and, and...
we have withdrawn legacy archive support for "DOS" apps, some obscure
software we wrote 424 years ago.

And there will howls of rage at the withdrawal of DOS support for 424 years
ago.

Stephen Howe
Ralph
2005-10-12 18:16:03 UTC
Permalink
Post by Stephen Howe
Post by Ralph
I wondered about that. In the 64-bit 'version' I got to play with basic
commands didn't work or rather there was no obvious way to get to a command
line. The 'help' file said "DOS Commands were no longer supported". It
didn't sound like a good idea. But, Hey, what do I know. <g>
But what will happen?
Seems to me in the year 2400...
Microsoft will announce Windows Solid Matter 4D version 27.0, runs all
devices you use in real life and full integration with brain with new
emotional sensations, alternative bodies is now standard, virtual sex has
been enhanced with optional male/female aliens, matter teleportation is
fixed this version and no longer kills people at random on use, and, and...
we have withdrawn legacy archive support for "DOS" apps, some obscure
software we wrote 424 years ago.
And there will howls of rage at the withdrawal of DOS support for 424 years
ago.
Stephen Howe
LOL

Probably true. You never saw Spock with some d**n mouse. Sometimes you just
want to type or scribble. <g>

-ralph

H-Man
2005-09-15 20:33:29 UTC
Permalink
Post by Stan Hilliard
I have a legacy program written in VBDOS that runs in a DOS window.
One of my customers using Windows XP can't print. The attempt to print
just hangs the DOS window.
The internal code is like
OPEN "O", #1, "PRN"
PRINT #1, etc.
It has printed from windows 98 and 2000. Could it be windows XP
related?
It is not practical to change the program. (The program seems to work
well in XP otherwise.)
What could be the problem?
Help will be appreciated.
It works for me, XP Home SP2, HPLJ1100 on network print server mapped as
LPT1

I'd be interested in exactly what printer this is going to. Perhaps it's
more of a printer issue than an OS issue.
--
HK
Stan Hilliard
2005-09-16 04:09:28 UTC
Permalink
Post by H-Man
Post by Stan Hilliard
I have a legacy program written in VBDOS that runs in a DOS window.
One of my customers using Windows XP can't print. The attempt to print
just hangs the DOS window.
The internal code is like
OPEN "O", #1, "PRN"
PRINT #1, etc.
It has printed from windows 98 and 2000. Could it be windows XP
related?
It is not practical to change the program. (The program seems to work
well in XP otherwise.)
What could be the problem?
Help will be appreciated.
It works for me, XP Home SP2, HPLJ1100 on network print server mapped as
LPT1
I'd be interested in exactly what printer this is going to. Perhaps it's
more of a printer issue than an OS issue.
My customer has XP on a stand alone computer with a printer connected
USB. I don't know what brand. No network.

I have a Win98SE and an XP home. Neither is networked. I found the
following on the PC Magazine site for the XPs. I have not tried it
yet:

==== From Old App to USB Printer
http://www.pcworld.com/howto/article/0,aid,120357,00.asp

I have an old DOS-based database program that will print only to the
LPT1 or LPT2 ports on my PC. My new printer is strictly USB. How do I
print to it from my database application?

Walter Mueller, Regina, Saskatchewan

I'm becoming more and more convinced that you simply should not buy a
printer that doesn't include a parallel port. USB printers have too
many limitations (see "How Do I Share a Printer on My Small Network?"
for another example). Fortunately, there's a workaround for this
problem in Windows XP and 2000 that involves printer pooling, which is
meant to allow one logical printer to print to two actual devices.

First, you'll need to open the Printers applet in Control Panel: In
Windows XP, select Start, Control Panel, Printers and Other Hardware
(if you are using XP's Categories view), Printers and Faxes. If you
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
printer pooling near the bottom of the dialog box; then select LPT1:
at the top of the port list, and click OK (see FIGURE 1).

Windows 98 and Me have what appears to be a built-in remedy--an option
named Capture Printer Port on the Details tab of each printer's
Properties dialog box. Unfortunately, this function works only for
printers on a network, not for those connected directly to your
computer.
====

I will try that with my XP laptop and USB printer soon. I sort of
expect it to work.

My win98 machine is another matter. It has two parallel ports
connected plus one USB printer. (three altogether, no network) I get
an error message from trying to address the USB:

==== (in DOS window)
Microsoft(R) Windows 98
(C)Copyright Microsoft Corp 1981-1999.

C:\WINDOWS>net use prn: \\tower\HP1012

Error 2106: This operation cannot be performed to your own computer;
it can be performed only on a server. For more information, contact
your network administrator.

C:\WINDOWS>
====

This might mean that it needs a "Microsoft Loopback Adapter" software
which tricks the computer into using its networking features even if
it is not actually on a network. However it is part of win2k and XP
but not 98.
http://www.columbia.edu/~em36/wpdos/winprint.html
H-Man
2005-09-16 17:07:37 UTC
Permalink
Post by Stan Hilliard
Post by H-Man
Post by Stan Hilliard
I have a legacy program written in VBDOS that runs in a DOS window.
One of my customers using Windows XP can't print. The attempt to print
just hangs the DOS window.
The internal code is like
OPEN "O", #1, "PRN"
PRINT #1, etc.
It has printed from windows 98 and 2000. Could it be windows XP
related?
It is not practical to change the program. (The program seems to work
well in XP otherwise.)
What could be the problem?
Help will be appreciated.
It works for me, XP Home SP2, HPLJ1100 on network print server mapped as
LPT1
I'd be interested in exactly what printer this is going to. Perhaps it's
more of a printer issue than an OS issue.
My customer has XP on a stand alone computer with a printer connected
USB. I don't know what brand. No network.
I have a Win98SE and an XP home. Neither is networked. I found the
following on the PC Magazine site for the XPs. I have not tried it
==== From Old App to USB Printer
http://www.pcworld.com/howto/article/0,aid,120357,00.asp
I have an old DOS-based database program that will print only to the
LPT1 or LPT2 ports on my PC. My new printer is strictly USB. How do I
print to it from my database application?
Walter Mueller, Regina, Saskatchewan
I'm becoming more and more convinced that you simply should not buy a
printer that doesn't include a parallel port. USB printers have too
many limitations (see "How Do I Share a Printer on My Small Network?"
for another example). Fortunately, there's a workaround for this
problem in Windows XP and 2000 that involves printer pooling, which is
meant to allow one logical printer to print to two actual devices.
First, you'll need to open the Printers applet in Control Panel: In
Windows XP, select Start, Control Panel, Printers and Other Hardware
(if you are using XP's Categories view), Printers and Faxes. If you
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
at the top of the port list, and click OK (see FIGURE 1).
Windows 98 and Me have what appears to be a built-in remedy--an option
named Capture Printer Port on the Details tab of each printer's
Properties dialog box. Unfortunately, this function works only for
printers on a network, not for those connected directly to your
computer.
====
I will try that with my XP laptop and USB printer soon. I sort of
expect it to work.
My win98 machine is another matter. It has two parallel ports
connected plus one USB printer. (three altogether, no network) I get
==== (in DOS window)
Microsoft(R) Windows 98
(C)Copyright Microsoft Corp 1981-1999.
C:\WINDOWS>net use prn: \\tower\HP1012
Error 2106: This operation cannot be performed to your own computer;
it can be performed only on a server. For more information, contact
your network administrator.
C:\WINDOWS>
====
This might mean that it needs a "Microsoft Loopback Adapter" software
which tricks the computer into using its networking features even if
it is not actually on a network. However it is part of win2k and XP
but not 98.
http://www.columbia.edu/~em36/wpdos/winprint.html
I don't know of a single USB only printer that has the capability to be
printed to from DOS. The primary difference is that DOS sends ASCII strings
to the printer and the printer responds appropriately. So when DOS tells it
to print the letter "A" the printer performs all of the lookups internally
to find out how to go about printing the letter commanded of it. In windows
with USB and "Windows only" or "Windows GDI" printers, when your
application tells the printer to print the letter "A" the character or
rather the entire page is first rasterized, that is converted into an
image. Then the printer is instructed as to where to put the dots and what
colors and so on. The difference then is that for a DOS compatible printer
it will take and ACII string and represent it correctly, directly. For a
"Windows GDI" printer, it requires the interaction of a driver to make it
work. Simple redirection won't work to accomplish this, you'll need to use
a Windows spooling program for this. In effect, print from DOS to a file,
and let Windows print the file to the printer. Look at

http://www.guolo.com/printfil/english.htm?en-us

This will provide the option for you to print to a Windows GDI Printer from
DOS .
--
HK
J French
2005-09-17 09:40:48 UTC
Permalink
On Fri, 16 Sep 2005 11:07:37 -0600, H-Man <I-***@Spam.sucks> wrote:

<snip>
Post by H-Man
I don't know of a single USB only printer that has the capability to be
printed to from DOS. The primary difference is that DOS sends ASCII strings
to the printer and the printer responds appropriately. So when DOS tells it
to print the letter "A" the printer performs all of the lookups internally
to find out how to go about printing the letter commanded of it. In windows
with USB and "Windows only" or "Windows GDI" printers, when your
application tells the printer to print the letter "A" the character or
rather the entire page is first rasterized, that is converted into an
image. Then the printer is instructed as to where to put the dots and what
colors and so on. The difference then is that for a DOS compatible printer
it will take and ACII string and represent it correctly, directly. For a
"Windows GDI" printer, it requires the interaction of a driver to make it
work. Simple redirection won't work to accomplish this, you'll need to use
a Windows spooling program for this. In effect, print from DOS to a file,
and let Windows print the file to the printer.
That is not really true

Consider the case of the WritePrinter API that pumps data directly
into the Spooler bypassing the Printer's Canvas
H-Man
2005-09-22 17:47:44 UTC
Permalink
Post by J French
<snip>
Post by H-Man
I don't know of a single USB only printer that has the capability to be
printed to from DOS. The primary difference is that DOS sends ASCII strings
to the printer and the printer responds appropriately. So when DOS tells it
to print the letter "A" the printer performs all of the lookups internally
to find out how to go about printing the letter commanded of it. In windows
with USB and "Windows only" or "Windows GDI" printers, when your
application tells the printer to print the letter "A" the character or
rather the entire page is first rasterized, that is converted into an
image. Then the printer is instructed as to where to put the dots and what
colors and so on. The difference then is that for a DOS compatible printer
it will take and ACII string and represent it correctly, directly. For a
"Windows GDI" printer, it requires the interaction of a driver to make it
work. Simple redirection won't work to accomplish this, you'll need to use
a Windows spooling program for this. In effect, print from DOS to a file,
and let Windows print the file to the printer.
That is not really true
Consider the case of the WritePrinter API that pumps data directly
into the Spooler bypassing the Printer's Canvas
Of course you're right, I should have made clear that I was speaking in
general terms, not absolute. Although it is possible to bypass the printers
canvas, doing so would require specific knowledge of what the printer needs
to see for the desired output. In general terms this is not related to
printing from a DOS program to a Windows GDI pinter, unless the Windows
spooling program uses this call. The only time I've ever seen this used is
with printers known to be PCL compatible.
--
HK
Ralph
2005-09-17 14:53:08 UTC
Permalink
Post by H-Man
Post by Stan Hilliard
Post by H-Man
Post by Stan Hilliard
I have a legacy program written in VBDOS that runs in a DOS window.
One of my customers using Windows XP can't print. The attempt to print
just hangs the DOS window.
The internal code is like
OPEN "O", #1, "PRN"
PRINT #1, etc.
It has printed from windows 98 and 2000. Could it be windows XP
related?
It is not practical to change the program. (The program seems to work
well in XP otherwise.)
What could be the problem?
Help will be appreciated.
It works for me, XP Home SP2, HPLJ1100 on network print server mapped as
LPT1
I'd be interested in exactly what printer this is going to. Perhaps it's
more of a printer issue than an OS issue.
My customer has XP on a stand alone computer with a printer connected
USB. I don't know what brand. No network.
I have a Win98SE and an XP home. Neither is networked. I found the
following on the PC Magazine site for the XPs. I have not tried it
==== From Old App to USB Printer
http://www.pcworld.com/howto/article/0,aid,120357,00.asp
I have an old DOS-based database program that will print only to the
LPT1 or LPT2 ports on my PC. My new printer is strictly USB. How do I
print to it from my database application?
Walter Mueller, Regina, Saskatchewan
I'm becoming more and more convinced that you simply should not buy a
printer that doesn't include a parallel port. USB printers have too
many limitations (see "How Do I Share a Printer on My Small Network?"
for another example). Fortunately, there's a workaround for this
problem in Windows XP and 2000 that involves printer pooling, which is
meant to allow one logical printer to print to two actual devices.
First, you'll need to open the Printers applet in Control Panel: In
Windows XP, select Start, Control Panel, Printers and Other Hardware
(if you are using XP's Categories view), Printers and Faxes. If you
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
at the top of the port list, and click OK (see FIGURE 1).
Windows 98 and Me have what appears to be a built-in remedy--an option
named Capture Printer Port on the Details tab of each printer's
Properties dialog box. Unfortunately, this function works only for
printers on a network, not for those connected directly to your
computer.
====
I will try that with my XP laptop and USB printer soon. I sort of
expect it to work.
My win98 machine is another matter. It has two parallel ports
connected plus one USB printer. (three altogether, no network) I get
==== (in DOS window)
Microsoft(R) Windows 98
(C)Copyright Microsoft Corp 1981-1999.
C:\WINDOWS>net use prn: \\tower\HP1012
Error 2106: This operation cannot be performed to your own computer;
it can be performed only on a server. For more information, contact
your network administrator.
C:\WINDOWS>
====
This might mean that it needs a "Microsoft Loopback Adapter" software
which tricks the computer into using its networking features even if
it is not actually on a network. However it is part of win2k and XP
but not 98.
http://www.columbia.edu/~em36/wpdos/winprint.html
I don't know of a single USB only printer that has the capability to be
printed to from DOS. The primary difference is that DOS sends ASCII strings
to the printer and the printer responds appropriately. So when DOS tells it
to print the letter "A" the printer performs all of the lookups internally
to find out how to go about printing the letter commanded of it. In windows
with USB and "Windows only" or "Windows GDI" printers, when your
application tells the printer to print the letter "A" the character or
rather the entire page is first rasterized, that is converted into an
image. Then the printer is instructed as to where to put the dots and what
colors and so on. The difference then is that for a DOS compatible printer
it will take and ACII string and represent it correctly, directly. For a
"Windows GDI" printer, it requires the interaction of a driver to make it
work. Simple redirection won't work to accomplish this, you'll need to use
a Windows spooling program for this. In effect, print from DOS to a file,
and let Windows print the file to the printer. Look at
http://www.guolo.com/printfil/english.htm?en-us
This will provide the option for you to print to a Windows GDI Printer from
DOS .
--
HK
Could you clarify what you mean by a "DOS" or "Window-Only" printer?

Perhaps I am living in a fool's paradise, (no comments, gentlemen, please.
<g>)but I have yet to run into a situation in which a USB printer could not
be configured to receive output from a "DOS Prompt" or Console application
by a simple configuration, either thru the Printer Applet, Net commands, or
'mode' settings.

Have I just been lucky? Is there some logo or spec to look for when buying a
USB printer? Is this only true for Win2k and up? (Never had an occasion to
attach a USB printer to a Win95/98 system.)

-ralph
Mike Williams
2005-09-17 15:39:02 UTC
Permalink
Post by Ralph
Could you clarify what you mean by a "DOS" or "Window-Only" printer?
Some printers, even printers that connect through a standard parallel port,
(many of the HP Deskjet range, for example) will only work properly when
addressed through their own printer drivers, which by and large means that
they are effectively "page printers" that need the appropriate Windows (or
other) printer driver to produce an output. There is nothing you can do to
them (hardware wise) to get them to accept simple "old fashioned" Ascii
codes and control codes to print text in the old fashioned way.

Mike
Mike Williams
2005-09-17 15:41:25 UTC
Permalink
"Mike Williams" <***@WhiskyAndCoke.com> wrote in message news:dghdbm$46e$***@newsg4.svr.pol.co.uk...

. . . sorry about the multiple postings. Bit of a hiccup this end :-(

Mike
Ralph
2005-09-17 16:49:35 UTC
Permalink
Post by Mike Williams
Post by Ralph
Could you clarify what you mean by a "DOS" or "Window-Only" printer?
Some printers, even printers that connect through a standard parallel port,
(many of the HP Deskjet range, for example) will only work properly when
addressed through their own printer drivers, which by and large means that
they are effectively "page printers" that need the appropriate Windows (or
other) printer driver to produce an output. There is nothing you can do to
them (hardware wise) to get them to accept simple "old fashioned" Ascii
codes and control codes to print text in the old fashioned way.
Mike
OK. You mean USB Printers will have difficultiy in supporting some kinds of
'direct' printing. But as the console inherently supports "Windows printing"
this should ever be a problem in normal practice.

thanks,
-ralph
Mike Williams
2005-09-17 15:39:37 UTC
Permalink
Post by Ralph
Could you clarify what you mean by a "DOS" or "Window-Only" printer?
Some printers, even printers that connect through a standard parallel port,
(many of the HP Deskjet range, for example) will only work properly when
addressed through their own printer drivers, which by and large means that
they are effectively "page printers" that need the appropriate Windows (or
other) printer driver to produce an output. There is nothing you can do to
them (hardware wise) to get them to accept simple "old fashioned" Ascii
codes and control codes to print text in the old fashioned way.

Mike
Mike Williams
2005-09-17 15:39:44 UTC
Permalink
Post by Ralph
Could you clarify what you mean by a "DOS" or "Window-Only" printer?
Some printers, even printers that connect through a standard parallel port,
(many of the HP Deskjet range, for example) will only work properly when
addressed through their own printer drivers, which by and large means that
they are effectively "page printers" that need the appropriate Windows (or
other) printer driver to produce an output. There is nothing you can do to
them (hardware wise) to get them to accept simple "old fashioned" Ascii
codes and control codes to print text in the old fashioned way.

Mike
Mike Williams
2005-09-17 15:39:51 UTC
Permalink
Post by Ralph
Could you clarify what you mean by a "DOS" or "Window-Only" printer?
Some printers, even printers that connect through a standard parallel port,
(many of the HP Deskjet range, for example) will only work properly when
addressed through their own printer drivers, which by and large means that
they are effectively "page printers" that need the appropriate Windows (or
other) printer driver to produce an output. There is nothing you can do to
them (hardware wise) to get them to accept simple "old fashioned" Ascii
codes and control codes to print text in the old fashioned way.

Mike
H-Man
2005-09-22 18:01:27 UTC
Permalink
Post by H-Man
Post by H-Man
Post by Stan Hilliard
Post by H-Man
Post by Stan Hilliard
I have a legacy program written in VBDOS that runs in a DOS window.
One of my customers using Windows XP can't print. The attempt to print
just hangs the DOS window.
The internal code is like
OPEN "O", #1, "PRN"
PRINT #1, etc.
It has printed from windows 98 and 2000. Could it be windows XP
related?
It is not practical to change the program. (The program seems to work
well in XP otherwise.)
What could be the problem?
Help will be appreciated.
It works for me, XP Home SP2, HPLJ1100 on network print server mapped as
LPT1
I'd be interested in exactly what printer this is going to. Perhaps it's
more of a printer issue than an OS issue.
My customer has XP on a stand alone computer with a printer connected
USB. I don't know what brand. No network.
I have a Win98SE and an XP home. Neither is networked. I found the
following on the PC Magazine site for the XPs. I have not tried it
==== From Old App to USB Printer
http://www.pcworld.com/howto/article/0,aid,120357,00.asp
I have an old DOS-based database program that will print only to the
LPT1 or LPT2 ports on my PC. My new printer is strictly USB. How do I
print to it from my database application?
Walter Mueller, Regina, Saskatchewan
I'm becoming more and more convinced that you simply should not buy a
printer that doesn't include a parallel port. USB printers have too
many limitations (see "How Do I Share a Printer on My Small Network?"
for another example). Fortunately, there's a workaround for this
problem in Windows XP and 2000 that involves printer pooling, which is
meant to allow one logical printer to print to two actual devices.
First, you'll need to open the Printers applet in Control Panel: In
Windows XP, select Start, Control Panel, Printers and Other Hardware
(if you are using XP's Categories view), Printers and Faxes. If you
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
at the top of the port list, and click OK (see FIGURE 1).
Windows 98 and Me have what appears to be a built-in remedy--an option
named Capture Printer Port on the Details tab of each printer's
Properties dialog box. Unfortunately, this function works only for
printers on a network, not for those connected directly to your
computer.
====
I will try that with my XP laptop and USB printer soon. I sort of
expect it to work.
My win98 machine is another matter. It has two parallel ports
connected plus one USB printer. (three altogether, no network) I get
==== (in DOS window)
Microsoft(R) Windows 98
(C)Copyright Microsoft Corp 1981-1999.
C:\WINDOWS>net use prn: \\tower\HP1012
Error 2106: This operation cannot be performed to your own computer;
it can be performed only on a server. For more information, contact
your network administrator.
C:\WINDOWS>
====
This might mean that it needs a "Microsoft Loopback Adapter" software
which tricks the computer into using its networking features even if
it is not actually on a network. However it is part of win2k and XP
but not 98.
http://www.columbia.edu/~em36/wpdos/winprint.html
I don't know of a single USB only printer that has the capability to be
printed to from DOS. The primary difference is that DOS sends ASCII
strings
Post by H-Man
to the printer and the printer responds appropriately. So when DOS tells
it
Post by H-Man
to print the letter "A" the printer performs all of the lookups internally
to find out how to go about printing the letter commanded of it. In
windows
Post by H-Man
with USB and "Windows only" or "Windows GDI" printers, when your
application tells the printer to print the letter "A" the character or
rather the entire page is first rasterized, that is converted into an
image. Then the printer is instructed as to where to put the dots and what
colors and so on. The difference then is that for a DOS compatible printer
it will take and ACII string and represent it correctly, directly. For a
"Windows GDI" printer, it requires the interaction of a driver to make it
work. Simple redirection won't work to accomplish this, you'll need to use
a Windows spooling program for this. In effect, print from DOS to a file,
and let Windows print the file to the printer. Look at
http://www.guolo.com/printfil/english.htm?en-us
This will provide the option for you to print to a Windows GDI Printer
from
Post by H-Man
DOS .
--
HK
Could you clarify what you mean by a "DOS" or "Window-Only" printer?
By DOS I mean to infer the program trying to print is a DOS program but
running in a DOS box within Windows. PCL Capable printers will print output
from a DOS program. By "Windows-Only" I mean that the printer is a Windows
GDI device and is not PCL capable, which means it will not understand ASCII
text as did the dot matrix printers of days past. The GDI printers require
the print data to be passed as a collection of where to place dots.
Post by H-Man
Perhaps I am living in a fool's paradise, (no comments, gentlemen, please.
<g>)but I have yet to run into a situation in which a USB printer could not
be configured to receive output from a "DOS Prompt" or Console application
by a simple configuration, either thru the Printer Applet, Net commands, or
'mode' settings.
I'm certainly not the definitive expert on which printers are or are not
PCL capable. I've never seen a USB printer that is, but then I've never
really had to find one either. My experience in all of this comes from
shopping for a laser printer that was PCL capable. The one I found was both
Parallel and USB. When I was looking all of the laser printers I looked at
that were USB only were not PCL capable.
Post by H-Man
Have I just been lucky? Is there some logo or spec to look for when buying a
USB printer? Is this only true for Win2k and up? (Never had an occasion to
attach a USB printer to a Win95/98 system.)
-ralph
AFAIK if you need to print from a DOS program in a DOS box in Windows, you
need to either have a PCL capable printer that is mapped to a LPT port, or
you need a program like PRINTFIL or DOSPRN to fill the gap.
--
HK
Brad Kunkel
2005-09-16 17:08:22 UTC
Permalink
Post by Stan Hilliard
First, you'll need to open the Printers applet in Control Panel: In
Windows XP, select Start, Control Panel, Printers and Other Hardware
(if you are using XP's Categories view), Printers and Faxes. If you
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
at the top of the port list, and click OK (see FIGURE 1).
I think this only works if the USB printer supports PCL in which case the
NET USE command works just as well. Many USB printers can't accept straight
text, so even if LPTx is pooled or captured using NET USE, nothing comes
out. I'd love to be wrong on this; maybe someone knows a better way.

As for Win98, I think there is no solution but to use one of the numerous
Print File programs which require the program to print to a file. This same
functionality can be had using Notepad with command line parameters (don't
remember them off hand) but not automated.

I wish there was a way to capture an LPTx print stream directly into a
Windows printer program. This way the program would not have to print to a
file and the user would not have the delay of waiting for the Print File
program to process it.

Regards,
Brad Kunkel
Integrated Business, Inc.
H-Man
2005-09-16 19:59:26 UTC
Permalink
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
First, you'll need to open the Printers applet in Control Panel: In
Windows XP, select Start, Control Panel, Printers and Other Hardware
(if you are using XP's Categories view), Printers and Faxes. If you
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
at the top of the port list, and click OK (see FIGURE 1).
I think this only works if the USB printer supports PCL in which case the
NET USE command works just as well. Many USB printers can't accept
straight
Post by Brad Kunkel
text, so even if LPTx is pooled or captured using NET USE, nothing comes
out. I'd love to be wrong on this; maybe someone knows a better way.
As for Win98, I think there is no solution but to use one of the numerous
Print File programs which require the program to print to a file. This
same
Post by Brad Kunkel
functionality can be had using Notepad with command line parameters (don't
remember them off hand) but not automated.
I wish there was a way to capture an LPTx print stream directly into a
Windows printer program. This way the program would not have to print to
a
Post by Brad Kunkel
file and the user would not have the delay of waiting for the Print File
program to process it.
Regards,
Brad Kunkel
Integrated Business, Inc.
Pardon the huge binary but if they can modify the DOS program and modify the
attached, maybe they can solve the problem.
I use it to print my old DOS prn files to my network printer.
Galen
Looking at the attchement I think that this only works if your printer,
network or otherwise is a DOS capable printer.

Good find though.
--
HK
Galen Somerville
2005-09-16 20:29:12 UTC
Permalink
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
First, you'll need to open the Printers applet in Control Panel: In
Windows XP, select Start, Control Panel, Printers and Other Hardware
(if you are using XP's Categories view), Printers and Faxes. If you
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
at the top of the port list, and click OK (see FIGURE 1).
I think this only works if the USB printer supports PCL in which case the
NET USE command works just as well. Many USB printers can't accept
straight
Post by Brad Kunkel
text, so even if LPTx is pooled or captured using NET USE, nothing comes
out. I'd love to be wrong on this; maybe someone knows a better way.
As for Win98, I think there is no solution but to use one of the numerous
Print File programs which require the program to print to a file. This
same
Post by Brad Kunkel
functionality can be had using Notepad with command line parameters (don't
remember them off hand) but not automated.
I wish there was a way to capture an LPTx print stream directly into a
Windows printer program. This way the program would not have to print to
a
Post by Brad Kunkel
file and the user would not have the delay of waiting for the Print File
program to process it.
Regards,
Brad Kunkel
Integrated Business, Inc.
Pardon the huge binary but if they can modify the DOS program and modify the
attached, maybe they can solve the problem.
I use it to print my old DOS prn files to my network printer.
Galen
Looking at the attchement I think that this only works if your printer,
network or otherwise is a DOS capable printer.
Good find though.
--
HK
Wrong. If I had a DOS capable printer I wouldn't need the program. The
program reads a DOS PRN file and spits it into the Windows print spooler
(for the chosen printer).

Galen
H-Man
2005-09-16 22:01:58 UTC
Permalink
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
First, you'll need to open the Printers applet in Control Panel: In
Windows XP, select Start, Control Panel, Printers and Other Hardware
(if you are using XP's Categories view), Printers and Faxes. If you
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
at the top of the port list, and click OK (see FIGURE 1).
I think this only works if the USB printer supports PCL in which case
the
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
NET USE command works just as well. Many USB printers can't accept
straight
Post by Brad Kunkel
text, so even if LPTx is pooled or captured using NET USE, nothing
comes
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
out. I'd love to be wrong on this; maybe someone knows a better way.
As for Win98, I think there is no solution but to use one of the
numerous
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Print File programs which require the program to print to a file. This
same
Post by Brad Kunkel
functionality can be had using Notepad with command line parameters
(don't
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
remember them off hand) but not automated.
I wish there was a way to capture an LPTx print stream directly into a
Windows printer program. This way the program would not have to print
to
Post by H-Man
Post by Brad Kunkel
a
Post by Brad Kunkel
file and the user would not have the delay of waiting for the Print
File
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
program to process it.
Regards,
Brad Kunkel
Integrated Business, Inc.
Pardon the huge binary but if they can modify the DOS program and modify
the
Post by H-Man
Post by Brad Kunkel
attached, maybe they can solve the problem.
I use it to print my old DOS prn files to my network printer.
Galen
Looking at the attchement I think that this only works if your printer,
network or otherwise is a DOS capable printer.
Good find though.
--
HK
Wrong. If I had a DOS capable printer I wouldn't need the program. The
program reads a DOS PRN file and spits it into the Windows print spooler
(for the chosen printer).
Galen
Gotcha. So if one could automate the program to look for the chosen .PRN
file, it's operation could be almost transparent. AFAIK, this is exactly
the sort of thing PrintFil does. I'll have to play with this one when I
have more time.

Again, good find, thanks.
--
HK
Galen Somerville
2005-09-17 00:24:44 UTC
Permalink
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
First, you'll need to open the Printers applet in Control Panel: In
Windows XP, select Start, Control Panel, Printers and Other Hardware
(if you are using XP's Categories view), Printers and Faxes. If you
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
at the top of the port list, and click OK (see FIGURE 1).
I think this only works if the USB printer supports PCL in which case
the
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
NET USE command works just as well. Many USB printers can't accept
straight
Post by Brad Kunkel
text, so even if LPTx is pooled or captured using NET USE, nothing
comes
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
out. I'd love to be wrong on this; maybe someone knows a better way.
As for Win98, I think there is no solution but to use one of the
numerous
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Print File programs which require the program to print to a file.
This
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
same
Post by Brad Kunkel
functionality can be had using Notepad with command line parameters
(don't
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
remember them off hand) but not automated.
I wish there was a way to capture an LPTx print stream directly into a
Windows printer program. This way the program would not have to print
to
Post by H-Man
Post by Brad Kunkel
a
Post by Brad Kunkel
file and the user would not have the delay of waiting for the Print
File
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
program to process it.
Regards,
Brad Kunkel
Integrated Business, Inc.
Pardon the huge binary but if they can modify the DOS program and modify
the
Post by H-Man
Post by Brad Kunkel
attached, maybe they can solve the problem.
I use it to print my old DOS prn files to my network printer.
Galen
Looking at the attchement I think that this only works if your printer,
network or otherwise is a DOS capable printer.
Good find though.
--
HK
Wrong. If I had a DOS capable printer I wouldn't need the program. The
program reads a DOS PRN file and spits it into the Windows print spooler
(for the chosen printer).
Galen
Gotcha. So if one could automate the program to look for the chosen .PRN
file, it's operation could be almost transparent. AFAIK, this is exactly
the sort of thing PrintFil does. I'll have to play with this one when I
have more time.
Again, good find, thanks.
--
HK
Or you could change the DOS program to create the prn file then run a Batch
file. The batch file would run a modified version of PrintPrn program.

Galen
H-Man
2005-09-22 18:57:57 UTC
Permalink
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
First, you'll need to open the Printers applet in Control Panel: In
Windows XP, select Start, Control Panel, Printers and Other Hardware
(if you are using XP's Categories view), Printers and Faxes. If you
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
at the top of the port list, and click OK (see FIGURE 1).
I think this only works if the USB printer supports PCL in which case
the
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
NET USE command works just as well. Many USB printers can't accept
straight
Post by Brad Kunkel
text, so even if LPTx is pooled or captured using NET USE, nothing
comes
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
out. I'd love to be wrong on this; maybe someone knows a better way.
As for Win98, I think there is no solution but to use one of the
numerous
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Print File programs which require the program to print to a file.
This
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
same
Post by Brad Kunkel
functionality can be had using Notepad with command line parameters
(don't
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
remember them off hand) but not automated.
I wish there was a way to capture an LPTx print stream directly into
a
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Windows printer program. This way the program would not have to
print
Post by H-Man
Post by Brad Kunkel
to
Post by H-Man
Post by Brad Kunkel
a
Post by Brad Kunkel
file and the user would not have the delay of waiting for the Print
File
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
program to process it.
Regards,
Brad Kunkel
Integrated Business, Inc.
Pardon the huge binary but if they can modify the DOS program and
modify
Post by H-Man
Post by Brad Kunkel
the
Post by H-Man
Post by Brad Kunkel
attached, maybe they can solve the problem.
I use it to print my old DOS prn files to my network printer.
Galen
Looking at the attchement I think that this only works if your printer,
network or otherwise is a DOS capable printer.
Good find though.
--
HK
Wrong. If I had a DOS capable printer I wouldn't need the program. The
program reads a DOS PRN file and spits it into the Windows print spooler
(for the chosen printer).
Galen
Gotcha. So if one could automate the program to look for the chosen .PRN
file, it's operation could be almost transparent. AFAIK, this is exactly
the sort of thing PrintFil does. I'll have to play with this one when I
have more time.
Again, good find, thanks.
--
HK
Or you could change the DOS program to create the prn file then run a Batch
file. The batch file would run a modified version of PrintPrn program.
Galen
Galen,
I've done some playing with the program and cannot get it to send anything
other than the exact contents of the file to the printer. For instance, my
test file contains the following;
*****************************************
This is a test of the PRINTPRN program!
(FF)
*****************************************

The form feed at the end is actually a hex(0c)

The output of the PRINTPRN program remains the same regardless of the
printer chosen, which should be expected given the use of the WritePrinter
API. But as this API bypasses the Printers Canvas, how then does the text
get raterized by the printer drive. AFAIKS, the printer driver never really
makes an enterance here. I treid several different printers, adn if the
printer is a Windows GDI only printer like a LEXMARK Z52, this will not
facilitate the conversion of DOS ASCII text to anything else. I don't know
how you get this animal to work on a non-pcl printer, but I'm really
curious now.
--
HK
Galen Somerville
2005-09-22 19:47:32 UTC
Permalink
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
First, you'll need to open the Printers applet in Control Panel: In
Windows XP, select Start, Control Panel, Printers and Other Hardware
(if you are using XP's Categories view), Printers and Faxes. If you
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
at the top of the port list, and click OK (see FIGURE 1).
I think this only works if the USB printer supports PCL in which case
the
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
NET USE command works just as well. Many USB printers can't accept
straight
Post by Brad Kunkel
text, so even if LPTx is pooled or captured using NET USE, nothing
comes
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
out. I'd love to be wrong on this; maybe someone knows a better way.
As for Win98, I think there is no solution but to use one of the
numerous
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Print File programs which require the program to print to a file.
This
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
same
Post by Brad Kunkel
functionality can be had using Notepad with command line parameters
(don't
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
remember them off hand) but not automated.
I wish there was a way to capture an LPTx print stream directly into
a
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Windows printer program. This way the program would not have to
print
Post by H-Man
Post by Brad Kunkel
to
Post by H-Man
Post by Brad Kunkel
a
Post by Brad Kunkel
file and the user would not have the delay of waiting for the Print
File
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
program to process it.
Regards,
Brad Kunkel
Integrated Business, Inc.
Pardon the huge binary but if they can modify the DOS program and
modify
Post by H-Man
Post by Brad Kunkel
the
Post by H-Man
Post by Brad Kunkel
attached, maybe they can solve the problem.
I use it to print my old DOS prn files to my network printer.
Galen
Looking at the attchement I think that this only works if your printer,
network or otherwise is a DOS capable printer.
Good find though.
--
HK
Wrong. If I had a DOS capable printer I wouldn't need the program. The
program reads a DOS PRN file and spits it into the Windows print spooler
(for the chosen printer).
Galen
Gotcha. So if one could automate the program to look for the chosen .PRN
file, it's operation could be almost transparent. AFAIK, this is exactly
the sort of thing PrintFil does. I'll have to play with this one when I
have more time.
Again, good find, thanks.
--
HK
Or you could change the DOS program to create the prn file then run a Batch
file. The batch file would run a modified version of PrintPrn program.
Galen
Galen,
I've done some playing with the program and cannot get it to send anything
other than the exact contents of the file to the printer. For instance, my
test file contains the following;
*****************************************
This is a test of the PRINTPRN program!
(FF)
*****************************************
The form feed at the end is actually a hex(0c)
The output of the PRINTPRN program remains the same regardless of the
printer chosen, which should be expected given the use of the WritePrinter
API. But as this API bypasses the Printers Canvas, how then does the text
get raterized by the printer drive. AFAIKS, the printer driver never really
makes an enterance here. I treid several different printers, adn if the
printer is a Windows GDI only printer like a LEXMARK Z52, this will not
facilitate the conversion of DOS ASCII text to anything else. I don't know
how you get this animal to work on a non-pcl printer, but I'm really
curious now.
--
HK
As I see it, your Z52 must use PCL. This link discusses printing to DOS
http://support.lexmark.com/cgi-perl/knowledgebase.cgi?ccs=229:1:0:292:0:0&framed=&docid=126&relevance=1

I'm not an XP expert but I think you can run DOS commends from Start - Run

You should test a prn file using the DOS command COPY xxxx.prn lpt1 /b
as shown on the link.

Apparently the Z52 driver does not present a direct PCL connection as the
link says to install a driver for some 500 series printer ???

Galen
H-Man
2005-09-22 20:13:13 UTC
Permalink
Post by Stan Hilliard
In
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
Windows XP, select Start, Control Panel, Printers and Other
Hardware
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
(if you are using XP's Categories view), Printers and Faxes. If
you
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
printer pooling near the bottom of the dialog box; then select
at the top of the port list, and click OK (see FIGURE 1).
I think this only works if the USB printer supports PCL in which
case
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
the
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
NET USE command works just as well. Many USB printers can't accept
straight
Post by Brad Kunkel
text, so even if LPTx is pooled or captured using NET USE, nothing
comes
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
out. I'd love to be wrong on this; maybe someone knows a better
way.
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
As for Win98, I think there is no solution but to use one of the
numerous
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Print File programs which require the program to print to a file.
This
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
same
Post by Brad Kunkel
functionality can be had using Notepad with command line parameters
(don't
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
remember them off hand) but not automated.
I wish there was a way to capture an LPTx print stream directly
into
Post by H-Man
Post by Brad Kunkel
a
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Windows printer program. This way the program would not have to
print
Post by H-Man
Post by Brad Kunkel
to
Post by H-Man
Post by Brad Kunkel
a
Post by Brad Kunkel
file and the user would not have the delay of waiting for the Print
File
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
program to process it.
Regards,
Brad Kunkel
Integrated Business, Inc.
Pardon the huge binary but if they can modify the DOS program and
modify
Post by H-Man
Post by Brad Kunkel
the
Post by H-Man
Post by Brad Kunkel
attached, maybe they can solve the problem.
I use it to print my old DOS prn files to my network printer.
Galen
Looking at the attchement I think that this only works if your
printer,
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
network or otherwise is a DOS capable printer.
Good find though.
--
HK
Wrong. If I had a DOS capable printer I wouldn't need the program. The
program reads a DOS PRN file and spits it into the Windows print
spooler
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
(for the chosen printer).
Galen
Gotcha. So if one could automate the program to look for the chosen
.PRN
Post by H-Man
Post by Brad Kunkel
Post by H-Man
file, it's operation could be almost transparent. AFAIK, this is
exactly
Post by H-Man
Post by Brad Kunkel
Post by H-Man
the sort of thing PrintFil does. I'll have to play with this one when I
have more time.
Again, good find, thanks.
--
HK
Or you could change the DOS program to create the prn file then run a
Batch
Post by H-Man
Post by Brad Kunkel
file. The batch file would run a modified version of PrintPrn program.
Galen
Galen,
I've done some playing with the program and cannot get it to send anything
other than the exact contents of the file to the printer. For instance, my
test file contains the following;
*****************************************
This is a test of the PRINTPRN program!
(FF)
*****************************************
The form feed at the end is actually a hex(0c)
The output of the PRINTPRN program remains the same regardless of the
printer chosen, which should be expected given the use of the WritePrinter
API. But as this API bypasses the Printers Canvas, how then does the text
get raterized by the printer drive. AFAIKS, the printer driver never
really
Post by H-Man
makes an enterance here. I treid several different printers, adn if the
printer is a Windows GDI only printer like a LEXMARK Z52, this will not
facilitate the conversion of DOS ASCII text to anything else. I don't know
how you get this animal to work on a non-pcl printer, but I'm really
curious now.
--
HK
As I see it, your Z52 must use PCL. This link discusses printing to DOS
http://support.lexmark.com/cgi-perl/knowledgebase.cgi?ccs=229:1:0:292:0:0&framed=&docid=126&relevance=1
I'm not an XP expert but I think you can run DOS commends from Start - Run
You should test a prn file using the DOS command COPY xxxx.prn lpt1 /b
as shown on the link.
Apparently the Z52 driver does not present a direct PCL connection as the
link says to install a driver for some 500 series printer ???
Galen
But that's my point. Without PCL cabability, PRINTPRN doesn't work from a
DOS created file. If the printer has PCL capability, then you could print
to it for the DOS program, either directly or via redirection. Either way,
PRINTPRN will not allow any Windows GDI printer to print output from a DOS
program. As I understood it, this was the claim you were making, if I
misunderstood you then I'm sorry, my bad.
--
HK
Galen Somerville
2005-09-22 21:43:19 UTC
Permalink
Post by H-Man
Post by Stan Hilliard
In
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
Windows XP, select Start, Control Panel, Printers and Other
Hardware
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
(if you are using XP's Categories view), Printers and Faxes. If
you
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
use Windows 2000, click Start, Settings, Printers. Now right-click
your printer's icon, and select Properties, Ports. Check Enable
printer pooling near the bottom of the dialog box; then select
at the top of the port list, and click OK (see FIGURE 1).
I think this only works if the USB printer supports PCL in which
case
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
the
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
NET USE command works just as well. Many USB printers can't accept
straight
Post by Brad Kunkel
text, so even if LPTx is pooled or captured using NET USE, nothing
comes
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
out. I'd love to be wrong on this; maybe someone knows a better
way.
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
As for Win98, I think there is no solution but to use one of the
numerous
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Print File programs which require the program to print to a file.
This
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
same
Post by Brad Kunkel
functionality can be had using Notepad with command line parameters
(don't
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
remember them off hand) but not automated.
I wish there was a way to capture an LPTx print stream directly
into
Post by H-Man
Post by Brad Kunkel
a
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Windows printer program. This way the program would not have to
print
Post by H-Man
Post by Brad Kunkel
to
Post by H-Man
Post by Brad Kunkel
a
Post by Brad Kunkel
file and the user would not have the delay of waiting for the Print
File
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
program to process it.
Regards,
Brad Kunkel
Integrated Business, Inc.
Pardon the huge binary but if they can modify the DOS program and
modify
Post by H-Man
Post by Brad Kunkel
the
Post by H-Man
Post by Brad Kunkel
attached, maybe they can solve the problem.
I use it to print my old DOS prn files to my network printer.
Galen
Looking at the attchement I think that this only works if your
printer,
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
network or otherwise is a DOS capable printer.
Good find though.
--
HK
Wrong. If I had a DOS capable printer I wouldn't need the program. The
program reads a DOS PRN file and spits it into the Windows print
spooler
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
(for the chosen printer).
Galen
Gotcha. So if one could automate the program to look for the chosen
.PRN
Post by H-Man
Post by Brad Kunkel
Post by H-Man
file, it's operation could be almost transparent. AFAIK, this is
exactly
Post by H-Man
Post by Brad Kunkel
Post by H-Man
the sort of thing PrintFil does. I'll have to play with this one when I
have more time.
Again, good find, thanks.
--
HK
Or you could change the DOS program to create the prn file then run a
Batch
Post by H-Man
Post by Brad Kunkel
file. The batch file would run a modified version of PrintPrn program.
Galen
Galen,
I've done some playing with the program and cannot get it to send anything
other than the exact contents of the file to the printer. For instance, my
test file contains the following;
*****************************************
This is a test of the PRINTPRN program!
(FF)
*****************************************
The form feed at the end is actually a hex(0c)
The output of the PRINTPRN program remains the same regardless of the
printer chosen, which should be expected given the use of the WritePrinter
API. But as this API bypasses the Printers Canvas, how then does the text
get raterized by the printer drive. AFAIKS, the printer driver never
really
Post by H-Man
makes an enterance here. I treid several different printers, adn if the
printer is a Windows GDI only printer like a LEXMARK Z52, this will not
facilitate the conversion of DOS ASCII text to anything else. I don't know
how you get this animal to work on a non-pcl printer, but I'm really
curious now.
--
HK
As I see it, your Z52 must use PCL. This link discusses printing to DOS
http://support.lexmark.com/cgi-perl/knowledgebase.cgi?ccs=229:1:0:292:0:0&framed=&docid=126&relevance=1
Post by H-Man
Post by Stan Hilliard
I'm not an XP expert but I think you can run DOS commends from Start - Run
You should test a prn file using the DOS command COPY xxxx.prn lpt1
/b
Post by H-Man
Post by Stan Hilliard
as shown on the link.
Apparently the Z52 driver does not present a direct PCL connection as the
link says to install a driver for some 500 series printer ???
Galen
But that's my point. Without PCL cabability, PRINTPRN doesn't work from a
DOS created file. If the printer has PCL capability, then you could print
to it for the DOS program, either directly or via redirection. Either way,
PRINTPRN will not allow any Windows GDI printer to print output from a DOS
program. As I understood it, this was the claim you were making, if I
misunderstood you then I'm sorry, my bad.
--
HK
The link I supplied is technical information for the Z52 printer. The first
paragraph says
quote
When you print from a DOS application, your printer uses PCL3 emulation. You
must install a printer driver for PCL3 emulation in each DOS application.
Lexmark recommend the HP 500c DeskJet.
unquote

So your printer does use pcl but you must install a driver that can access
it. They recommend the HP 500c DeskJet

I happen to be using a HP DeskJet 5650

Also the very end of the technical info shows
qoute
Environment
1000 color jetprinter 1100 color jetprinter
1020 be 1020 color jetprinter
2055 color jetprinte 2050 color jetprinter
2030 color jetprinter 2070 color jetprinter
3200 Color Jetprinter 5000 color jetprinter
5700 color jetprinter 5770 photo jetprinter
7000 color jetprinter 7200 color jetprinter
z11 color jetprinter z31 color jetprinter
z51 color jetprinter z12 color jetprinter
z22 color jetprinter z32 color jetprinter
z42 color jetprinter z52 color jetprinter
z53 color jetprinter z43 color jetprinter
kodak ppm 100 by lexmark kodak ppm 200 by lexmark
Microsoft Windows 3.1x Microsoft Windows 95
Microsoft Windows 98 MS-DOS
unquote

And again the z52 is listed.

It doesn't show WinXP as your printer is older but that shouldn't matter.

Galen
H-Man
2005-09-23 20:06:53 UTC
Permalink
Post by Stan Hilliard
Post by H-Man
Post by Stan Hilliard
In
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
Windows XP, select Start, Control Panel, Printers and Other
Hardware
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
(if you are using XP's Categories view), Printers and Faxes. If
you
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
use Windows 2000, click Start, Settings, Printers. Now
right-click
Post by H-Man
Post by Stan Hilliard
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Post by Stan Hilliard
your printer's icon, and select Properties, Ports. Check Enable
printer pooling near the bottom of the dialog box; then select
at the top of the port list, and click OK (see FIGURE 1).
I think this only works if the USB printer supports PCL in which
case
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
the
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
NET USE command works just as well. Many USB printers can't
accept
Post by H-Man
Post by Stan Hilliard
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
straight
Post by Brad Kunkel
text, so even if LPTx is pooled or captured using NET USE,
nothing
Post by H-Man
Post by Stan Hilliard
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
comes
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
out. I'd love to be wrong on this; maybe someone knows a better
way.
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
As for Win98, I think there is no solution but to use one of the
numerous
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Print File programs which require the program to print to a file.
This
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
same
Post by Brad Kunkel
functionality can be had using Notepad with command line
parameters
Post by H-Man
Post by Stan Hilliard
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
(don't
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
remember them off hand) but not automated.
I wish there was a way to capture an LPTx print stream directly
into
Post by H-Man
Post by Brad Kunkel
a
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
Windows printer program. This way the program would not have to
print
Post by H-Man
Post by Brad Kunkel
to
Post by H-Man
Post by Brad Kunkel
a
Post by Brad Kunkel
file and the user would not have the delay of waiting for the
Print
Post by H-Man
Post by Stan Hilliard
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
File
Post by H-Man
Post by Brad Kunkel
Post by Brad Kunkel
program to process it.
Regards,
Brad Kunkel
Integrated Business, Inc.
Pardon the huge binary but if they can modify the DOS program and
modify
Post by H-Man
Post by Brad Kunkel
the
Post by H-Man
Post by Brad Kunkel
attached, maybe they can solve the problem.
I use it to print my old DOS prn files to my network printer.
Galen
Looking at the attchement I think that this only works if your
printer,
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
Post by H-Man
network or otherwise is a DOS capable printer.
Good find though.
--
HK
Wrong. If I had a DOS capable printer I wouldn't need the program.
The
Post by H-Man
Post by Stan Hilliard
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
program reads a DOS PRN file and spits it into the Windows print
spooler
Post by H-Man
Post by Brad Kunkel
Post by H-Man
Post by Brad Kunkel
(for the chosen printer).
Galen
Gotcha. So if one could automate the program to look for the chosen
.PRN
Post by H-Man
Post by Brad Kunkel
Post by H-Man
file, it's operation could be almost transparent. AFAIK, this is
exactly
Post by H-Man
Post by Brad Kunkel
Post by H-Man
the sort of thing PrintFil does. I'll have to play with this one when
I
Post by H-Man
Post by Stan Hilliard
Post by H-Man
Post by Brad Kunkel
Post by H-Man
have more time.
Again, good find, thanks.
--
HK
Or you could change the DOS program to create the prn file then run a
Batch
Post by H-Man
Post by Brad Kunkel
file. The batch file would run a modified version of PrintPrn program.
Galen
Galen,
I've done some playing with the program and cannot get it to send
anything
Post by H-Man
Post by Stan Hilliard
Post by H-Man
other than the exact contents of the file to the printer. For instance,
my
Post by H-Man
Post by Stan Hilliard
Post by H-Man
test file contains the following;
*****************************************
This is a test of the PRINTPRN program!
(FF)
*****************************************
The form feed at the end is actually a hex(0c)
The output of the PRINTPRN program remains the same regardless of the
printer chosen, which should be expected given the use of the
WritePrinter
Post by H-Man
Post by Stan Hilliard
Post by H-Man
API. But as this API bypasses the Printers Canvas, how then does the
text
Post by H-Man
Post by Stan Hilliard
Post by H-Man
get raterized by the printer drive. AFAIKS, the printer driver never
really
Post by H-Man
makes an enterance here. I treid several different printers, adn if the
printer is a Windows GDI only printer like a LEXMARK Z52, this will not
facilitate the conversion of DOS ASCII text to anything else. I don't
know
Post by H-Man
Post by Stan Hilliard
Post by H-Man
how you get this animal to work on a non-pcl printer, but I'm really
curious now.
--
HK
As I see it, your Z52 must use PCL. This link discusses printing to DOS
http://support.lexmark.com/cgi-perl/knowledgebase.cgi?ccs=229:1:0:292:0:0&framed=&docid=126&relevance=1
Post by H-Man
Post by Stan Hilliard
I'm not an XP expert but I think you can run DOS commends from Start -
Run
Post by H-Man
Post by Stan Hilliard
You should test a prn file using the DOS command COPY xxxx.prn lpt1
/b
Post by H-Man
Post by Stan Hilliard
as shown on the link.
Apparently the Z52 driver does not present a direct PCL connection as
the
Post by H-Man
Post by Stan Hilliard
link says to install a driver for some 500 series printer ???
Galen
But that's my point. Without PCL cabability, PRINTPRN doesn't work from a
DOS created file. If the printer has PCL capability, then you could print
to it for the DOS program, either directly or via redirection. Either way,
PRINTPRN will not allow any Windows GDI printer to print output from a DOS
program. As I understood it, this was the claim you were making, if I
misunderstood you then I'm sorry, my bad.
--
HK
The link I supplied is technical information for the Z52 printer. The first
paragraph says
quote
When you print from a DOS application, your printer uses PCL3 emulation. You
must install a printer driver for PCL3 emulation in each DOS application.
Lexmark recommend the HP 500c DeskJet.
unquote
So your printer does use pcl but you must install a driver that can access
it. They recommend the HP 500c DeskJet
I happen to be using a HP DeskJet 5650
Also the very end of the technical info shows
qoute
Environment
1000 color jetprinter 1100 color jetprinter
1020 be 1020 color jetprinter
2055 color jetprinte 2050 color jetprinter
2030 color jetprinter 2070 color jetprinter
3200 Color Jetprinter 5000 color jetprinter
5700 color jetprinter 5770 photo jetprinter
7000 color jetprinter 7200 color jetprinter
z11 color jetprinter z31 color jetprinter
z51 color jetprinter z12 color jetprinter
z22 color jetprinter z32 color jetprinter
z42 color jetprinter z52 color jetprinter
z53 color jetprinter z43 color jetprinter
kodak ppm 100 by lexmark kodak ppm 200 by lexmark
Microsoft Windows 3.1x Microsoft Windows 95
Microsoft Windows 98 MS-DOS
unquote
And again the z52 is listed.
It doesn't show WinXP as your printer is older but that shouldn't matter.
Galen
Again, that's the point.
The HP5650 does in fact have limited support for DOS printing. The only
thing DOS cannot do is address the printer directly, because it is USB
only. The printer does however understand the print output from a DOS
program. You may not know this, but there are may printers out there that
do not understand this output, and with those printers the PRINTPRN program
is of little help. There are ways to map the USB port to a LTP port, I'm
not really sure of the details right now, but, check this out for some
ideas.
http://www.geekswithblogs.net/dtotzke/articles/26204.aspx
This way you won't need an additional layer of software to rely on.
--
HK
Ken Halter
2005-09-23 20:20:32 UTC
Permalink
Post by H-Man
Post by Galen Somerville
And again the z52 is listed.
It doesn't show WinXP as your printer is older but that shouldn't matter.
Galen
Again, that's the point.
The HP5650 does in fact have limited support for DOS printing. The only
thing DOS cannot do is address the printer directly, because it is USB
only. The printer does however understand the print output from a DOS
program. You may not know this, but there are may printers out there that
do not understand this output, and with those printers the PRINTPRN program
is of little help. There are ways to map the USB port to a LTP port, I'm
not really sure of the details right now, but, check this out for some
ideas.
http://www.geekswithblogs.net/dtotzke/articles/26204.aspx
This way you won't need an additional layer of software to rely on.
--
HK
I guess you guys have never heard of trimming posts? Jeezzzz
--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
Please keep all discussions in the groups..
H-Man
2005-09-23 21:41:01 UTC
Permalink
Post by Ken Halter
I guess you guys have never heard of trimming posts? Jeezzzz
Normally I do, I kinda got carried away, my appologies to the group.
--
HK
Galen Somerville
2005-09-24 01:16:42 UTC
Permalink
Post by H-Man
Post by Ken Halter
I guess you guys have never heard of trimming posts? Jeezzzz
Normally I do, I kinda got carried away, my appologies to the group.
--
HK
Not to beat a dead horse but the Lexmark documentation says it does use pcl3
if you install the Hp 500 etc driver.

Have you tried that?

Galen
H-Man
2005-10-03 16:40:42 UTC
Permalink
Post by Galen Somerville
Not to beat a dead horse but the Lexmark documentation says it does use pcl3
if you install the Hp 500 etc driver.
Have you tried that?
Galen
The horse is dead. It does not support it in hardware, that was the point.
Pick a different printer, one that does not support PCL at all, it won't
work, that's the point! It will not work for a non DOS compatible printer.
If the printer supports PCL then it is DOS compatible. If it supports PCL
through a driver, then the driver provides "limited DOS support". Either
way PRINTPRN is not required to make the thing work. There are easier ways.
If there is no PCL support for the printer, PRINTPRN won't do anyone any
good, again, this was my point.
--
HK
MikeD
2005-09-24 01:08:39 UTC
Permalink
Post by Ken Halter
I guess you guys have never heard of trimming posts? Jeezzzz
No kidding. Now if we can just get Ralph to start trimming posts. <g>
--
Mike
Microsoft MVP Visual Basic
Ralph
2005-09-24 01:38:47 UTC
Permalink
Post by MikeD
Post by Ken Halter
I guess you guys have never heard of trimming posts? Jeezzzz
No kidding. Now if we can just get Ralph to start trimming posts. <g>
--
Mike
Microsoft MVP Visual Basic
OK, OK, I hear you!

-ralph
Loading...