Print from DOS app under XP

[Richard Bonner]

Richard,

No, they are Windows utilities for DOS programs running on Windows machines

*** OK, thanks for the answer.

(by the way there are no other ways to print to Windows printers or use
Windows ODBC32 drivers in plain DOS).

*** Interesting. Would it not be possible to construct such an
interface?

Anyway, even DosPrn and Dos2Usb, which are listed on your site, are Windows
utilities.

Davide

*** I contacted both websites and you are correct. They have been or
will be removed this weekend.

Richard Bonner
http://www.chebucto.ca/~ak621/DOS/

 

[Davide Guolo]

Richard,

*** Interesting. Would it not be possible to construct such an
interface?

do you mean rewriting the Windows Printing System and the ODBC32 layer in
DOS ? (and the spooler, and the TCP/IP stack, and ... Windows ?)

It's not only a matter to drive an interface (USB) which was not existing at
the DOS time. More and more printers nowadays are GDI (also known as
Windows-Only). This means they simply cannot understand an ascii data flow
as input. They needs something created by the Windows printer driver.

In addition, many Windows "printer" drivers are virtual (WinFax, Adobe
Distiller, ...)
You have no chances to use such software on a plain DOS machine, but a DOS
application running on a Windows machine can use those drivers too, through
Printfil.

Considering that most of the DOS applications out there works perfectly even
on Windows, I don't see why they should be used on plain DOS machines
anymore (expecially if the users wants to use the "Windows" stuff also, like
GDI printers and connections to remote databases)

Regards,
Davide
aSwIt s.r.l.
--------------------------------------------------------------
Printfil - Windows Printing System for Applications
http://www.printfil.com
Odbc4All - Connection to ODBC Data Sources for any Application
http://www.aswit.com/odbc4all
@Kill - Batch Close Windows Applications - Freeware
http://www.aswit.com/akill
--------------------------------------------------------------

 

[Terence]

I originally used to program output in either Epson Esc coding. or
graphic 8-pin coding, or esle used the HP PCL 5 and GL/2 languages,
which seemd to cover almost all printers that were "compatible" with
something else.

But now I get around these problems by outputting either pure ascii and
if needed use a conversion routine to provide an .RTF file, or program
..RTF code directly.

Then I pass the RTF file to Word-for Windows or Winpad, both of which
can then print to any defined printer connected to the computer,
whatever the printer model is.

Since then I've had no printing problems.

 

[Terence]

I originally used to program output in either Epson Esc coding. or
graphic 8-pin coding, or else used the HP PCL 5 and GL/2 languages,
which seemd to cover almost all printers that were "compatible" with
something else.

But now I get around these problems by outputting either pure ascii and

if needed use a conversion routine to provide an RTF file, or program
..RTF code directly.

Then I pass the Ascii or RTF file to Word-for Windows or Winpad, both
of which
can then print to any defined printer connected to the computer,
whatever the printer model is.

Since then I've had no printing problems.

 

[Richard Bonner]

Richard,

do you mean rewriting the Windows Printing System and the ODBC32 layer in
DOS ? (and the spooler, and the TCP/IP stack, and ... Windows ?)

*** No, I mean writing an interface for a DOS-only system that would
translate a DOS program's printer output to a Windows printer.

It's not only a matter to drive an interface (USB) which was not existing at
the DOS time.

*** There are DOS USB capabilities out now. I have not tried mine on a
USB printer, though.

More and more printers nowadays are GDI (also known as
Windows-Only). This means they simply cannot understand an ascii data flow
as input. They needs something created by the Windows printer driver.

*** Then how does Linux do it? Or cannot Linux print to a Windows
printer?

In addition, many Windows "printer" drivers are virtual (WinFax, Adobe
Distiller, ...)
You have no chances to use such software on a plain DOS machine, but a DOS
application running on a Windows machine can use those drivers too, through
Printfil.

*** I can understand that.

Considering that most of the DOS applications out there works perfectly even
on Windows, I don't see why they should be used on plain DOS machines
anymore

*** I do because today's DOS setups are far from plain, I am not
interested in having to deal with WIndows when I use DOS. I tried that
and could not believe the hassles and complications I ran into, so I
upgraded to DOS in 1999. (-:


(expecially if the users wants to use the "Windows" stuff also, like

GDI printers and connections to remote databases)

Davide

*** That does not help those that don't want the expense and hassle of
Windows, such as myself. I have had quite enough of Windows, thanks. (-:

Richard Bonner
http://www.chebucto.ca/~ak621/DOS/

 

[Davide Guolo]

Richard,

*** No, I mean writing an interface for a DOS-only system that would
translate a DOS program's printer output to a Windows printer.

that's my point. Since more and more printers are GDI, you need to deal with
the Windows driver in order to create a GDI "image" to forward to the
printer, unless you want to rewrite a "DOS" graphical driver for each
printer out there (even in Windows you have differents drivers for different
printers). This is not far from "rewriting the Windows Printing System".
And what about network printers ? DOS does not natively have TCP/IP support.

*** There are DOS USB capabilities out now. I have not tried mine on a
USB printer, though.

I've seen DOS drivers for USB disks, written by the specific disk
manufacturer.

*** Then how does Linux do it? Or cannot Linux print to a Windows
printer?

Linux does it similarly to Windows (in reality it's the reverse, as Linux is
derived from Unix). It has his own set of drivers (and you cannot use
Windows ones on Linux), spooler, TCP/IP etc.
In addition, you cannot compare Linux to DOS. DOS has limited RAM, graphic
abilities, File System ...

*** I do because today's DOS setups are far from plain, I am not
interested in having to deal with WIndows when I use DOS. I tried that
and could not believe the hassles and complications I ran into, so I
upgraded to DOS in 1999. (-:

I understand your point, and I agree with you up to a certain point.

(expecially if the users wants to use the "Windows" stuff also, like
*** That does not help those that don't want the expense and hassle of
Windows, such as myself. I have had quite enough of Windows, thanks. (-:

I personally like Linux and use it most of the time. Obviously anyone can
decide not to use Windows at all. If someone don't want to use Windows, then
probably he don't need to use a Windows-Only printer or to connect his DOS
application to a Windows ODBC32 database thought.

Sometimes even a DOS fan can decide to use his app. on Windows with Printfil
and a cheap Win-Printer rather than having to buy an expensive Dos
compatible printer. Sometimes even expensive networked all-in-one printers
are not DOS compatible.

Regards,
Davide
aSwIt s.r.l.
--------------------------------------------------------------
Printfil - Windows Printing System for Applications
http://www.printfil.com
Odbc4All - Connection to ODBC Data Sources for any Application
http://www.aswit.com/odbc4all
@Kill - Batch Close Windows Applications - Freeware
http://www.aswit.com/akill
--------------------------------------------------------------

 

[Richard Bonner]

Richard,

that's my point. Since more and more printers are GDI, you need to deal with
the Windows driver in order to create a GDI "image" to forward to the
printer, unless you want to rewrite a "DOS" graphical driver for each
printer out there (even in Windows you have differents drivers for different
printers). This is not far from "rewriting the Windows Printing System".
And what about network printers ? DOS does not natively have TCP/IP support.

*** I think we are on different pages here. I am speaking of using
Widows printers on DOS-only machines - no Windows in sight.

I've seen DOS drivers for USB disks, written by the specific disk
manufacturer.

*** I am only using USB for flash drives and camera downloads.

In addition, you cannot compare Linux to DOS. DOS has limited RAM, graphic
abilities, File System ...

*** Not so much anymore. DOS has media players, can access the graphic
Internet, and can handle gigabyte drives.

I personally like Linux and use it most of the time. Obviously anyone can
decide not to use Windows at all. If someone doesn't want to use
Windows, then probably one doesn't need to use a Windows-Only printer

Davide

*** Being able to would increase the number of available printers for
DOS, though.

Richard Bonner
http://www.chebucto.ca/~ak621/DOS/

 

[support]

Anyway, evenDosPrnand Dos2Usb, which are listed on your site, are Windows

will be removed this weekend.

I want to draw the community attentions on the Mr.Guolo posts. You can
see an example of unfair competition here.

Mr.Guolo promote and sale your own printing utility four times
expensive then DosPrn and Dos2Usb. But he make more efforts to
fighting with competitors then for reducing the price of your own
product.

 

[Davide Guolo]

Dear Mr. "(e-mail address removed)"

I want to draw the community attentions on the Mr.Guolo posts. You can
see an example of unfair competition here.

This is not unfair competition.

By rereading my previous posts you'll see I've asked Mr. Bonner to add our
utilities to his DOS web page in addition to the others which were already
listed. I never asked him to remove your own, nor I've never said nothing
bad or false about it.

Mr. Bonner kindly replied me that he wouldn't have added Printfil and the
other utilities of ours because they requires Windows on the machine. If he
removed your own, it's for the same reason.

You'll agree with me that Mr. Bonner has right to decide what he wants to
list on his website and what he doesn't want.

Mr.Guolo promote and sale your own printing utility four times
expensive then DosPrn and Dos2Usb. But he make more efforts to
fighting with competitors then for reducing the price of your own
product.

Printfil has much more features than the the other products, and if it's
cheaper or not depends by how many licenses the Client needs.

I'm not fighting with anyone, and you're not allowed to decide if we should
reduce the price of our software or not.

Once the Clients knows all the choices, they can decide themselves which is
the right product for them. The market is not influenced neither by me nor
by you. The Clients makes it.

Regards,
Davide Guolo
aSwIt s.r.l.
--------------------------------------------------------------
Printfil - Windows Printing System for Applications
http://www.printfil.com
Odbc4All - Connection to ODBC Data Sources for any Application
http://www.aswit.com/odbc4all
@Kill - Batch Close Windows Applications - Freeware
http://www.aswit.com/akill
--------------------------------------------------------------