Hi!

>> IIRC, PRINTER.SYS only supported a few different kinds of printers anyway,
>> and was relatively useless even back in the day (at least for me).
> 
> Well, I can't remember if it even exists! And, let's be honest,
> printers are a pain even at the best of times. So me holding out blind
> hope that FreeDOS will ever work ("for me"), in this particular
> hardware area, is not going to happen.
> 
> Eric (Auer) probably knows more (or maybe Jim Tabor).

In MS DOS, it probably was something which knew the mapping
of characters to bytes for a number of widely used printers
for a number of possible DIP switch settings. I think today
it is more appropriate to just render text as graphics. Of
course this is a bit slower than printing plain text due to
the extra bandwidth used. It can work on e.g. HP/PCL, ESC/P
and PostScript printers (as GRAPHICS). Some printers, for
example ESC/P, also support limited font upload (faster).

There was some thread about how to make approximate fonts
for printers from VGA sized fonts a while ago.

>>>> alias reboot=fdapm warmboot
>>>> alias halt=fdapm poweroff
>>
>> On the same machine (Sony laptop), FDAPM doesn't work at all because
>> the BIOS doesn't have APM (only ACPI)...

ACPI is also supported but modern ACPI tables can be too
complicated for FDAPM. Then you will have to press ctrl-
alt-delete or the power button instead of using FDAPM...

> My old (dead) laptop didn't work with CTmouse.

That does not help much with testing ;-)

Eric


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to