On 4/25/2021 10:43 PM, TK Chia wrote:
Hello Ralf,
Still an excellent tool I consider TROFF, now GROFF, for Unix/Linux
-which also exists for Windows, appeared in 1990 (Version 0.3.1) by
James Clark) coming from “a text-formatting program called RUNOFF,
which was written by Jerome H. Saltzer fo
Hello Ralf,
Still an excellent tool I consider TROFF, now GROFF, for Unix/Linux
-which also exists for Windows, appeared in 1990 (Version 0.3.1) by
James Clark) coming from “a text-formatting program called RUNOFF,
which was written by Jerome H. Saltzer for MIT's CTSS operating system
in the mi
On 4/23/2021 1:44 PM, Thomas Desi wrote:
Hi Ralf,
good to focus on the “whys”.
You said:
| “Nor would I do any graphics work in DOS, or any word
| processing these days.”
I did get into DOS because of “word processing”.
More precisely it is a text-processing tool(!) EVA.EXE which was develop
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
hopefu
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:
https://downloadcenter.intel.com/download/29138/Intel-Ethernet-Adapte
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 a
...for some reason, this has not been delivered on Friday...
(continuing a privately started debate in the mailing list)
We need to start from the fact (which you have found out, and I have
cofirmed) that your printer is probaby GDI based. (To me this sad
fact is still surprising, or "despite all
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 i
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 attem
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/
___
Freedos-us
Thanks, Mateusz:
If you have a printer that is network enabled and it speaks
Postscript, PCL, Epson ESC P2, or plain text then you can "print to a
file" under DOS and then use Netcat to send the file to your printer.
{Protocols
IPv4
ARP, RARP, BOOTP, DHCP, APIPA(Auto IP), WINS/NetBIOS name
re
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 clien
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
Hi Ralf,
good to focus on the “whys”.
You said:
| “Nor would I do any graphics work in DOS, or any word
| processing these days.”
I did get into DOS because of “word processing”.
More precisely it is a text-processing tool(!) EVA.EXE which was developed by
Primož Jakopin in the 1970ies and
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,
I
Hi Ralf,
good to focus on the “whys”.
You said:
| “Nor would I do any graphics work in DOS, or any word
| processing these days.”
I did get into DOS because of “word processing”.
More precisely it is a text-processing tool(!) EVA.EXE which was developed by
Primož Jakopin in the 1970ies and
17 matches
Mail list logo
