🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.folklore.computers
Article #621412

Re: Old word processors

#621412
From: J. Clarke
Date: Sat, 24 Mar 2018 12:09
40 lines
3251 bytes
On Sat, 24 Mar 2018 04:59:50 -0500, Charles Richmond
<nume...@aquaporin4.com> wrote:

>On 3/22/2018 10:37 PM, J. Clarke wrote:
>> On Thu, 22 Mar 2018 22:32:07 -0500, Dave Garland
>> <dave.g...@wizinfo.com> wrote:
>> 
>>> On 3/21/2018 7:00 PM, Peter Flass wrote:
>>>> Andreas Kohlbach <a...@spamfence.net> wrote:
>>>
>>>>> With MP/M (1979) you had multitasking. Thus you could send a file to the
>>>>> printer while continuing other work, while on MS-DOS the PC would be
>>>>> blocked until the print job was completed. That's while some companies
>>>>> offered hardware printer buffers (for MS-DOS and other non-multitasking
>>>>> systems) to avoid this.
>>>>
>>>> I thought print spooling was one of the few multitasking features in DOS.
>>>>
>>>
>>> I don't think so. ISTR being happy when I found a (freeware/shareware)
>>> TSR that would print spool.
>> 
>> In any case it would have only worked with "well behaved" programs and
>> nothing to speak of was "well behaved", which is why the
>> non-IBM-compable MS-DOS boxes were so generally useless (I still have
>> two Victor 9000s and an Apricot).
>> 
>
>On your LAN, you might set up your MS-DOS incompatible... to be a 
>dedicated print server.

If (a) you can find network interface cards for both machines that
support the same network protocol and (b) your applications are well
behaved enough that you can redirect output to the LAN from them. This
latter wasn't guaranteed--some software accessed the I/O ports
directly.

>Everyone on the LAN could send the printout to 
>the server, and the software there would schedule the printing to the 
>attached printer or printers..
Technical Details
Message-ID: <rsfcbdhntqja39l8d7kg28p030r7ibs4e7@4ax.com>
Path: mbox-mo1.pugleaf.net!d3-v6ni1125itf.0!nntp.google.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!post02.iad!fx42.iad.POSTED!not-for-mail
References: <87605rpw4h.fsf@usenet.ankman.de> <20180320083453.d19d1d8bd925f19ba3ad0f5e@eircom.net> <87in9qse1j.fsf@usenet.ankman.de> <20180320205351.43b813333366179c8fdd65a3@eircom.net> <1063637826.543276913.620814.peter_flass-yahoo.com@news.eternal-september.org> <87370t2kdk.fsf@usenet.ankman.de> <434099342.543369576.912298.peter_flass-yahoo.com@news.eternal-september.org> <p91sfn$rfk$1@dont-email.me> <egt8bdpd93crlitlkkgn1sh7qe0gndt6e0@4ax.com> <p957ij$79c$1@dont-email.me>

Show Full Headers
Complete Article Headers
X-Received: by 10.107.88.8 with SMTP id m8mr14494503iob.15.1521893385640;        Sat, 24 Mar 2018 05:09:45 -0700 (PDT)
X-BeenThere: alt.folklore.computers@googlegroups.com
Received: by 10.107.114.16 with SMTP id n16ls2385927ioc.24.gmail; Sat, 24 Mar 2018 05:09:44 -0700 (PDT)
X-Received: by 10.107.9.80 with SMTP id j77mr14406397ioi.138.1521893384492;        Sat, 24 Mar 2018 05:09:44 -0700 (PDT)
Path: mbox-mo1.pugleaf.net!d3-v6ni1125itf.0!nntp.google.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!post02.iad!fx42.iad.POSTED!not-for-mail
From: J. Clarke <jclarke...@gmail.com>
Newsgroups: alt.folklore.computers
Subject: Re: Old word processors
Message-ID: <rsfcbdhntqja39l8d7kg28p030r7ibs4e7@4ax.com>
References: <87605rpw4h.fsf@usenet.ankman.de> <20180320083453.d19d1d8bd925f19ba3ad0f5e@eircom.net> <87in9qse1j.fsf@usenet.ankman.de> <20180320205351.43b813333366179c8fdd65a3@eircom.net> <1063637826.543276913.620814.peter_flass-yahoo.com@news.eternal-september.org> <87370t2kdk.fsf@usenet.ankman.de> <434099342.543369576.912298.peter_flass-yahoo.com@news.eternal-september.org> <p91sfn$rfk$1@dont-email.me> <egt8bdpd93crlitlkkgn1sh7qe0gndt6e0@4ax.com> <p957ij$79c$1@dont-email.me>
User-Agent: ForteAgent/8.00.32.1272
MIME-Version: 1.0
Lines: 40
X-Complaints-To: ab...@newsdemon.com
NNTP-Posting-Date: Sat, 24 Mar 2018 12:09:44 UTC
Organization: http://www.NewsDemon.com
Bytes: 2647
Date: Sat, 24 Mar 2018 08:09:43 -0400
X-Received-Bytes: 2709
X-Received-Body-CRC: 3183264769
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit