Hello,
On Tue, 20 Apr 2021 at 17:19, Frantisek Rysanek
wrote:
> Built-in fonts are obviously an option, there's always some plain
> ASCII built in, and I believe in the old DOS era there used to be...
> programs that you ran before printing your jobs, that would
> pre-upload font sets or
Dear gentlemen,
today I've tested some ideas... one worked, one did not.
1) put a UNIX-domain named pipe in the Samba share, locally on the
server:
cd /mnt/samba
mknod print.q p
chmod 666 print.q
The above needs to run as user root.
The following can run as an
Thanks, Ralf:
As above in the mean time I have assigned printing to PRN (no longer
to LPT2).
OK, but that means your setup you have is different than the one you
mentioned many times before.
My setup changes according to trial and error experiment.
--
members.iinet.net.au/~kilgallin/
Thanks, Liam:
Bryan is not telling us the full story here.
I found log files confusing.
... (whatever that means) so I am giving up here.
Quitting may seem an easy option. But I have been going at this project
for months!
--
members.iinet.net.au/~kilgallin/
On 6/20/2021 9:02 AM, Bryan Kilgallin wrote:
Thanks, Ralf:
If you have mapped LPT2 to the network printer then you *must* print
to LPT2. Sending to PRN or LPT1 won't do anything because there's no
device there.
I will henceforth direct printing to PRN.
On the FreeDOS PC, in C:\MSNET>, I
Thanks, Ralf:
If you have mapped LPT2 to the network printer then you *must* print
to LPT2. Sending to PRN or LPT1 won't do anything because there's no
device there.
I will henceforth direct printing to PRN.
On the FreeDOS PC, in C:\MSNET>, I have edited LOGON.BAT. That now says
the
On Sun, 20 Jun 2021 at 17:52, Ralf Quint wrote:
>
> That doesn't make any sense. There must be something else in play for
> that to work. PRN: is an alias to LPT1:
>
> There should be no printout what so ever of you would send data to PRN:
> and have the network printer assigned to LPT2:
Agreed.
On 6/20/2021 7:06 AM, Bryan Kilgallin wrote:
If you have mapped LPT2 to the network printer then you *must* print
to LPT2. Sending to PRN or LPT1 won't do anything because there's no
device there.
I will henceforth direct printing to PRN.
The easy way to print to any port is just to copy or
Thanks for your interest, Liam:
From the FreeDOS PC, I can print a little over a hundred characters.
So does that meant that it _can_ print something?
Yes. I have just got that function operating again.
PRN: -- the default printer
Hm, I'd like all printing to go to the Samba-network
On Sun, 20 Jun 2021 at 13:44, Bryan Kilgallin wrote:
>
> From the FreeDOS PC, I can print a little over a hundred characters.
So does that meant that it _can_ print something?
> Because I want to print, and it's called "PRINT"!
OK, but it is not like that.
DOS inherits a lot of its design
Thanks, Liam:
On the FreeDOS PC:
* LMHOSTS lists the printer against its IP address; and
* LOGON.BAT lists the server and print queue, and
specifies "net use LPT2:, with the server, print queue,
and password.
That looks good! Great progress from when
On Sun, 20 Jun 2021 at 10:17, Bryan Kilgallin wrote:
>
> I wish to print from a FreeDOS PC. That connects via Samba to an Ubuntu
> server. That speaks via Ethernet to a Brother GDI printer. František has
> been advising me on this project.
>
> On the FreeDOS PC:
> * LMHOSTS lists the
Thanks, Frank:
...while looking for some existing "LPT port redirection software"
for DOS, I've first found this proggie:
I have tried using that. But I found its documentation limited! And I
have not been able to get printing done thereby.
It's a little TSR in .COM format that installs in
...while looking for some existing "LPT port redirection software"
for DOS, I've first found this proggie:
http://info.elf.stuba.sk/packages/pub/pc/utiltext/lpt2file.zip
It's a little TSR in .COM format that installs in memory, captures
any printing on LPT1 (done using the BIOS printing service
Thanks to Eric for taking a look at my Wireshark screenshot...
I was getting ready to make some PCAP files available, but ultimately
it is not needed, because I already know where the problem is :-)
After some further investigation, it started dawning on me, that this
does look like a bug in
Thanks, Michael:
I hate to even suggest this, but are you using the /B option on the file
copy to indicate that a binary copy is needed?
That didn't fix the printing problem. It's the same with /a. The first
5.1 lines of a text file got printed.
--
members.iinet.net.au/~kilgallin/
Just a short update:
I've retreated in my footsteps all the way back to my lab at work,
and its PXE-booted legacy NetBootDisk profile, and I have to say that
the LPT2 obtained via
net use lpt2: \\printserver\queue
misbehaves *exactly* the same as in my minimized VirtualBox
environment,
Hi Frank,
http://support.fccps.cz/download/adv/frr/dosnet/write_print_file_request.png
This says that, assuming that 192.168.3.54 is your DOS
computer, you got a TCP ACK from the Linux PC (139 to
39183), then SMB tree connect ANDX from the Linux PC,
then a MALFORMED PACKET from the DOS PC for
This is a re-post, my first two attempts had too many attachments.
I'm re-attaching just the TXT file being printed, and here are some
relevant screenshots:
http://support.fccps.cz/download/adv/frr/dosnet/ps.png
http://support.fccps.cz/download/adv/frr/dosnet/write_print_file_reque
st.png
I'm
I hate to even suggest this, but are you using the /B option on the file
copy to indicate that a binary copy is needed? Otherwise, the first Ctrl-Z
in the file will end the file copy prematurely.
On Wed, Jun 16, 2021 at 3:37 PM Frantisek Rysanek
wrote:
> Dear gentlemen,
>
> on and off, with
Dear gentlemen,
on and off, with Bryan we've been playing with Ubuntu, Samba, CUPS
and the MS Network Client running in FreeDOS. And we're facing a dead
end - same symptoms observed by me and by Bryan:
We can load the MS stack, to the point that we can "net use" network
disk volumes = map a
Thanks again, Frank:
Basically I'd say you're all set to try and load the DOS network
stack, and see if that works
I take it that means entering "start", in either MSNET OR PKTDRV.
:-) Again there are two alternative
flavours of the DOS TCP/IP stack, one tastes of Microsoft, the other
one
On 15 May 2021 at 13:56, Eric Auer wrote:
>
> Hi Bryan & Frank,
>
> > As you had suggested, on the FreeDOS PC, in C:\MSNET\ I entered "start".
> > Then I could ping from that PC to my printer, Ubuntu PC and Ubuntu laptop.
>
> Cool! Thanks for creating the network zip :-) What is
> in that start
On 15 May 2021 at 10:40, Ralf Quint wrote:
>
> On 5/15/2021 4:56 AM, Eric Auer wrote:
> >
> >> I had worried that the DOS machine on my network, would
> >> give easy access from the Internet for gremlins!
> > Because DOS normally does not run any servers, there is
> > not much which the gremlins
On 5/15/2021 4:56 AM, Eric Auer wrote:
I had worried that the DOS machine on my network, would
give easy access from the Internet for gremlins!
Because DOS normally does not run any servers, there is
not much which the gremlins could access. So it depends
on which servers you manually start
Eric:
As you had suggested, on the FreeDOS PC, in C:\MSNET\ I entered "start".
Then I could ping from that PC to my printer, Ubuntu PC and Ubuntu laptop.
Cool! Thanks for creating the network zip :-) What is
in that start bat file and which packages with which
licenses are required to make
Hi Bryan & Frank,
> As you had suggested, on the FreeDOS PC, in C:\MSNET\ I entered "start".
> Then I could ping from that PC to my printer, Ubuntu PC and Ubuntu laptop.
Cool! Thanks for creating the network zip :-) What is
in that start bat file and which packages with which
licenses are
Thanks again, Frank:
As I've already written, I myself have investigated the dark rabbit
hole of MS-DOS networking for you:
http://frantisek.rysanek.sweb.cz/FD_NET.zip
Unzip the three directories to your DOS hard drive, take a look at
the config.sys suggested, and see if you can get your DOS
Thanks, Eric:
Which changes have
you applied to load the network things?
Upon Frank's following package, I used Ubuntu's Archive Manager to
extract the contents. Then I used a USB stick to transfer the
directories to my FreeDOS PC. So in the latter's C: directory, are
MSNET, MTCPAPPS, and
Dear Bryan,
> My FreeDOS PC's FDCONFIG.SYS file now says this.
> Should I put `!' before the BREAK and STACKS statements?
That is not necessary. Actually I find it a bit odd that
the default config used ! so frequently. Tastes differ :-)
Eric
___
Oops. I've goofed up by running the last message throught the list.
Already. For more than one reason, and going off topic being the
least important. Apologies. Such an example of bad taste on my part.
I should know better. I'll keep the possible networking follow-ups in
private messages.
Bryan thanks for your progress reports :-)
Nice to see how you have cartographed your local network, and that
you're showing quite a bit of understanding.
Your existing autoexec looks pretty harmless to me.
I don't have any demands on what to put in there, that's why I didn't
provide an
Further, Eric:
I assume you have already added things from the FD_NET
autoexec to your existing autoexec?
Frank's package at this address--doesn't contain "autoexec"!
http://frantisek.rysanek.sweb.cz/FD_NET.zip
Whereas my FreeDOS PC's C: directory has an AUTOEXEC.BAT file. It
contains this.
Dear Eric:
feel free to notify the bootablecd.de maintainer that you
would prefer less contrast for the Blinky mascot background
to distract visitors less from reading the text on the page.
Yes, I've sent an e-mail request there.
Indeed ! marks
a line as "always use" while ? marks it as
Dear Bryan,
feel free to notify the bootablecd.de maintainer that you
would prefer less contrast for the Blinky mascot background
to distract visitors less from reading the text on the page.
> My FreeDOS PC's FDCONFIG.SYS file contents follow.
That seems to be one of the default versions.
Dear Frank:
As I've already written, I myself have investigated the dark rabbit
hole of MS-DOS networking for you:
http://frantisek.rysanek.sweb.cz/FD_NET.zip
Unzip the three directories to your DOS hard drive, take a look at
the config.sys suggested, and see if you can get your DOS box to take
On 2 May 2021 at 10:24, Bryan Kilgallin wrote:
> So, Frank:
>
> > Install Samba on your Linux PC. It may take a wee bit of learning to
> > configure, but it does not bite back. I can help with snippets of
> > config to make it accept ancient DOS clients.
> >
> > Install the Microsoft Network
Thanks, Robert:
If there's no problem of shelf space, get a used HP LaserJet 4 printer
on eBay.
I've made such an inquiry of the charity from which I got my refurbished
(Linux PC) and laptop.
--
members.iinet.net.au/~kilgallin/
___
Freedos-user
I wrote:
My main workhorse is a Dell OptiPlex GX270 running Ubuntu 20.04.2 LTS.
That is incorrect. My Linux PC is a Dell XPS 8300.
--
members.iinet.net.au/~kilgallin/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
Thanks, Frank:
Bryan says he's got a Linux computer.
My main workhorse is a Dell OptiPlex GX270 running Ubuntu 20.04.2 LTS. I
also have networked a Lenovo Thinkpad L430, also running Ubuntu.
A printer that natively understand PCL3 ... will commonly understand plain text.
I'll ask around
Hi Bryan,
>> Without any additional software,
>> a printer being used from DOS needs to be able to receive plain text,
>> with additional capabilities either through the industry standard ESC/P
>> (developed by Epson, who was for a long time the leader in printers
>> before laser printers
G'day Robert:
I vaguely remember using ps2pdf in plain DOS 15 years ago.
All is more complex now!
--
members.iinet.net.au/~kilgallin/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
Thanks, Ralf:
Without any additional software,
a printer being used from DOS needs to be able to receive plain text,
with additional capabilities either through the industry standard ESC/P
(developed by Epson, who was for a long time the leader in printers
before laser printers started to
Hi Eric,
> PS: We have GhostScript for PostScript processing and
> our "print screen hotkey" TSR exist for HP PCL, ESC/P
> and PostScript output. We have PDF viewers and it might
> be possible to use GhostScript to create PDF? Not sure.
> Some text editors also have built-in output converters.
I
Thanks, Adam:
It's worse than that. I've tried to get many different printers
working under Linux (which generally has pretty good hardware support)
and it turns out that a lot of manufacturers cut corners on their
devices and don't support standard print protocols like PostScript or
PCL, and
You are right, Eric:
That would of course be the EASIEST option as long as your PC
and your printer both still have Centronics connectivity
The PC does, but the printer doesn't. Hm, I found the following.
{USB to Parallel Bi-Directional Cable
USB to Parallel Bi-Directional Cable
USB to
G'day Bryan,
>> That would of course be the EASIEST option as long as your PC
>> and your printer both still have Centronics connectivity
>
> The PC does, but the printer doesn't. Hm, I found the following.
> {USB to Parallel Bi-Directional Cable
>
> USB to Parallel Bi-Directional Cable
Thanks, Frank:
Epson dot matrix printers (ESC*P language) were perfectly willing to
print individual characters, a line at a time I guess. They were
(are) line printers and the ESC*P "language" is little more than an
"extension" of raw ASCII + control characters (CR, LF, FF etc)
by "escape
G'day Eric:
Not sure which network chip your PC has?
networkNetLink BCM57788 Gigabit Ethernet PCIe
That would of course be the EASIEST option as long as your PC
and your printer both still have Centronics connectivity
The PC does, but the printer doesn't. Hm, I found the
So, Frank:
Install Samba on your Linux PC. It may take a wee bit of learning to
configure, but it does not bite back. I can help with snippets of
config to make it accept ancient DOS clients.
Install the Microsoft Network Client for MS-DOS. You can install this
from scratch, or you can try
On Tue, Apr 20, 2021 at 10:23 AM Eric Auer wrote:
> >> I have just connected my Brother HL-3150CDN laser printer to my Dell>>
> >> OptiPlex GX270.
> > I used the FreeDOS "print" command, unembellished.
>
> That is only needed for background printing. A more straightforward
> way is to send the
On Mon, 26 Apr 2021 at 19:49, Bryan Kilgallin wrote:
>
> Linux Archive Manager unpacked it!
Great!
So, your next step is probably to try to get the MS Network Client.
It's included on all the Windows NT Server CDs.
If I remember correctly, v3.0 includes sharing functionality -- it
makes DOS
On 4/26/2021 1:53 PM, Thomas Mueller wrote:
roven – Profile: https://about.me/liamproven
I think it might be possible to extraxt a self-extracting archive under DOS or
other OS with UNZIP.
But I see Linux Archive Manager did it for you.
7Zip does it most likely as well...
RAlf
--
This
> On Mon, 26 Apr 2021 at 01:21, Bryan Kilgallin wrote:
> > I copied the PRODOS.EXE file to my FreeDOS PC and entered "prodos".
> > Which resulted in this error:
> > "This program cannot be run in DOS mode.".
X-CMAE-Envelope:
You are right, Liam:
I copied the PRODOS.EXE file to my FreeDOS PC and entered "prodos".
Which resulted in this error:
"This program cannot be run in DOS mode.".
Could be a self-extracting archive. If you have Windows, try running
it under Windows, then copy across the unpacked files. If you
On Mon, 26 Apr 2021 at 01:21, Bryan Kilgallin wrote:
>
> I copied the PRODOS.EXE file to my FreeDOS PC and entered "prodos".
> Which resulted in this error:
> "This program cannot be run in DOS mode.".
Could be a self-extracting archive. If you have Windows, try running
it under Windows, then
Thanks, Eric:
And actually
it could work better to use the NETWORK for printing, because DOS
(wired LAN) network drivers are more evolved than DOS USB drivers
and you can use DOS versions of NETCAT or other tools to copy the
contents you want to print to the IP and port of your printer as
Eric Auer wrote:
Intel actually does provide DOS drivers for this chip
(but they say the stopped supporting DOS after 2019)
which contains at least NDIS support. I have not
checked whether it contains a packet driver as well:
On Sun, 25 Apr 2021 at 10:44, Bryan Kilgallin wrote:
>
> Transmission Control Protocol / Internet Protocol ( TCP/IP ) used
> for instance by UNIX, GNU/Linux, Windows Vista, OS X and the Internet,
We already know it must be TCP/IP. Everything else is obsolete.
> Unfortunately, I don't see
Sorry, Eric:
PCISCAN showed:
Bus 1
Dev C
Func 0
Slot 2C
Vend 0006
Dev. 100E
Class Name Network
Subclass Name Ethernet.
Correction: the vendor is "8086".
In case the vendor is something else, this might be an
Intel 82540EM Gigabit LAN controller.
You
Hi Bryan,
> PCISCAN showed:
> Bus 1
> Dev C
> Func 0
> Slot 2C
> Vend 0006
> Dev. 100E
> Class Name Network
> Subclass Name Ethernet.
In case the vendor is something else, this might be an
Intel 82540EM Gigabit LAN controller. If 0006:100e is
indeed correct, it
G'day Thomas:
Regarding printing I think there are two basic concepts:
Using fonts from the printer (I call this „generic“, but maybe this is
my private lingo)
or using graphics from the computer.
I hadn't got so much as a grunt out of the printer, from my FreeDOS PC!
I
wonder if you
Hm, Liam:
[1] Find out what network protocol(s) your printer speaks
Device URI: implicitclass://Brother_HL_3150CDN_series/
Make and Model: Brother HL-3150CDN series, driverless, cups-filters 1.27.4
--
members.iinet.net.au/~kilgallin/
___
Liam wrote:
{[1] Find out what network protocol(s) your printer speaks}
{Protocols
IPv4 ARP, RARP, BOOTP, DHCP, APIPA(Auto IP), WINS/NetBIOS name
resolution, DNS Resolver, mDNS, LLMNR responder, LPR/LPD, Custom
Raw Port/Port9100, IPP/IPPS, FTP Server, TELNET Server,
HTTP/HTTPS server, TFTP
Thanks, Frank, for the long reply:
But, yours is a different problem: your printer does not even have
LPT "input".
It has USB and Ethernet. At the moment, I have just the latter wired to
my router.
Technically, a USB printer shows up on the USB bus as a "USB LPT
device", or "USBLP".
How
Liam wrote:
{[2] Look for DOS support for 1 of those protocols}
FreeDOS protocols:
{The following protocols are supported by these three drivers:
Transmission Control Protocol / Internet Protocol ( TCP/IP ) used
for instance by UNIX, GNU/Linux, Windows Vista, OS X and the Internet,
On Fri, 23 Apr 2021 at 00:37, Bryan Kilgallin wrote:
>
> OK, I have plugged-in an Ethernet cable from the DOS PC to my router.
> Now what?
[1] Find out what network protocol(s) your printer speaks
[2] Look for DOS support for 1 of those protocols
[3] Install a DOS network stack that includes
I've only a few things to add to this discussion about printing in USB -- most
everything has already been said. But, I will summarize. USB support in the
BIOS (for computers that even still have a BIOS) is usually limited to some
subset of mouse, keyboard, and/or mass storage (disk drives).
On 21 Apr 2021 at 19:46, Bryan Kilgallin wrote:
> Eek, Frank:
>
> > oh that's right. Suppose that you have good support in the BIOS for
> > your USB keyboard, USB mouse and USB mass storage.
>
> Yes, I have a KVM switch driving both a keyboard and mouse from the
> DOS PC!
>
> > Then you
Eek, Frank:
oh that's right. Suppose that you have good support in the BIOS for
your USB keyboard, USB mouse and USB mass storage.
Yes, I have a KVM switch driving both a keyboard and mouse from the DOS PC!
Then you install
the USB LPT driver by Bret Johnson, which takes over the whole
So, Frank:
...just to follow up on what others have said, Bryan's printer is too
old to support PDF, but it is a pretty decent color laser apparently,
likely supports PCL5 in "HP emulation" mode, and something called
"BR-script (PostScript layer 3 emulation)" which I hope gets rendered
in the
On 20 Apr 2021 at 10:41, Ralf Quint wrote:
> dreaded (from the viewpoint of operability in DOS) USB connected
> printers. Finding USB drivers, given that the printer is software
> compatible with DOS as mentioned above, will likely be an exercise in
> futility. If someone has a surefire way of
On 20 Apr 2021 at 10:49, Ralf Quint wrote:
> If you are talking laser printers, then that might exclude printers
> that are Postscript only, as they require some software on the
> computer side to translate plain text into a Postscript data stream
> that the printer understands. Not such a big
On 4/20/2021 8:24 AM, Adam Nielsen via Freedos-user wrote:
I believe you have to install DOS USB drivers first.
It's worse than that. I've tried to get many different printers
working under Linux (which generally has pretty good hardware support)
and it turns out that a lot of manufacturers
On 4/20/2021 7:59 AM, Thomas Desi wrote:
If using a USB keyboard (and USB mouse), there is the problem that
when starting the USB driver (USBUHCI from Bret Johnsons USButils
collection), the Keyboard stops working. So you can’t start the
keyboard driver next, which seems should done to get
On 21 Apr 2021 at 0:00, Bryan Kilgallin wrote:
> I had transferred data from my DOS PC to my Linux PC via a USB-2
> stick. But I thought that I might do something as simple as printing
> text, directly from the DOS machine.
>
So there's another solution, one I already hinted at:
Install Samba
Hi, Bryan,
because I am fiddling with similar questions.
(Can’t compete anywhere near to the proficient replies of Eric and Frantisek
though!)
If using a USB keyboard (and USB mouse), there is the problem that when
starting the USB driver (USBUHCI from Bret Johnsons USButils collection), the
Hi Thomas,
> If using a USB keyboard (and USB mouse), there is the problem that
> when starting the USB driver (USBUHCI from Bret Johnsons USButils
> collection), the Keyboard stops working. So you can’t start the
> keyboard driver next, which seems should done to get somewhere.
The trick would
...just to follow up on what others have said, Bryan's printer is too
old to support PDF, but it is a pretty decent color laser apparently,
likely supports PCL5 in "HP emulation" mode, and something called
"BR-script (PostScript layer 3 emulation)" which I hope gets rendered
in the printer
> I believe you have to install DOS USB drivers first.
It's worse than that. I've tried to get many different printers
working under Linux (which generally has pretty good hardware support)
and it turns out that a lot of manufacturers cut corners on their
devices and don't support standard print
On 20 Apr 2021 at 16:59, Thomas Desi wrote:
> Regarding printing I think there are two basic concepts:
> Using fonts from the printer (I call this "generic", but maybe this
> is my private lingo) or using graphics from the computer.
> As I am only interested in printing out pure text (A-Z, 1-0
On 20 Apr 2021 at 16:21, Eric Auer wrote:
>
> Hi Bryan,
>
> I believe you have to install DOS USB drivers first. And actually it
> could work better to use the NETWORK for printing, because DOS (wired
> LAN) network drivers are more evolved than DOS USB drivers and you can
> use DOS versions of
Dear Mr. Kilgallin,
your request is less obvious than may have initially seemd to you.
DOS knows an OS-level "device" called LPT1. And, most software for
DOS that needs to print, can use this software-level LPT1 device
(using a DOS service to print).
DOS and BIOS work together to forward data
Hi Bryan,
I believe you have to install DOS USB drivers first. And actually
it could work better to use the NETWORK for printing, because DOS
(wired LAN) network drivers are more evolved than DOS USB drivers
and you can use DOS versions of NETCAT or other tools to copy the
contents you want to
I had transferred data from my DOS PC to my Linux PC via a USB-2 stick.
But I thought that I might do something as simple as printing text,
directly from the DOS machine.
I wrote:
I have just connected my Brother HL-3150CDN laser printer to my Dell
OptiPlex GX270.
My printer usually
Is it possible to get DOS to use a print server such as this?
If you have a packet driver, YES, theoretically, since one
can connect to HTTP servers ;-)
Windows for Workgroup, Windows 95/98/NT/Me/2000, NetWare
ww.viralbox.og So we could be having fun with DOS for decades to come
NOT amused
Supports Windows for Workgroup, Windows 95/98/NT/Me/2000, NetWare,
HP-UX, Sun Os, UnixWare,
From the page itself it looks like it supports Win311 and later. Worst
case you might have to use it through VirtualBox which runs most any
operating system even the latest junk from M$ in less memory
On Mon, Mar 1, 2010 at 8:17 PM, Ray Davison ray...@charter.net wrote:
Is it possible to get DOS to use a print server such as this?
http://tinyurl.com/ykf3raz
TY
Ray
Well, you could connect to an arbitrary network server (Netware,
Windows, Linux) and get at a server queue connected to such
Hi Chris,
I'll give printq a try and see what happens
Hmmm I only found a 6/2000 version on the page,
which is described as being from Dr Dobbs and
being a user interface for PRINT.
It tries to highly portable (various DOS compilers)
and seems to be 1991 by Robert Mashlan, Public
Domain. Most
Thanks Alain! I've downloaded it and will give it a try!
Alain M. wrote:
I was used to printq because it was far better then print, you should
give it a try. I found it at ibiblio (in Freedos, he he...)
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/print/
Alain
Chris Ruhl
I got the MS Print to load in FreeDOS by using CALLVER but couldn't
do a test print from a nasty paper jam that I'll clear tomorrow. I'll
let you know.
My only concern is the license issue ... I'm using this in a commercial
environment. Nobody would probably know that we're using a
I will certainly give the NEWDOS a whirl when I can. I've downloaded
it, just need to get time to play!
I will, no doubt, enjoy comparing the ms print with freedos print!! You
guys are great at fixing things up right and I seem to have the perfect
difficult hardware and applications for
I was used to printq because it was far better then print, you should
give it a try. I found it at ibiblio (in Freedos, he he...)
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/print/
Alain
Chris Ruhl escreveu:
I will certainly give the NEWDOS a whirl when I can. I've downloaded
Chris Ruhl schreef:
Any way I can pass this on to the PRINT side of the
project?? Anybody have any suggestions?? Again, can't
re-code the application.
No idea, never expected anyone to actually use PRINT application
anymore, maybe you're unique :)
Does MS print program work on FreeDOS?
I will test and let you know!
Bernd Blaauw wrote:
Chris Ruhl schreef:
Any way I can pass this on to the PRINT side of the
project?? Anybody have any suggestions?? Again, can't
re-code the application.
No idea, never expected anyone to actually use PRINT application
anymore,
95 matches
Mail list logo
