NetNews Usenet Archive 1992 #26/NN_1992_26.iso/spool/comp/sys/misc/939

Internet Message Format | 1992-11-05 | 1.7 KB

Path: sparky!uunet!stanford.edu!bcm!lib!oac.hsc.uth.tmc.edu!jmaynard
From: [e-mail] (Jay Maynard)
Newsgroups: comp.sys.misc
Subject: Re: Necessity/presence of TSRs?
Message-ID: <[e-mail]>
Date: 5 Nov 1992 16:16:03 GMT
References: <[e-mail]> <[e-mail]>
Sender: [e-mail]
Organization: UT Health Science Center Houston
Lines: 20
Nntp-Posting-Host: oac.hsc.uth.tmc.edu

In article <[e-mail]> [e-mail] (peter da silva) writes:
>In article <[e-mail]> [e-mail] (John Boyd;LAHDI;) writes:
>> Are TSRs still around in OS/2?  If not, how does
>> one accomplish some of the 'background' things that TSRs have been doing
>> all this time, i.e., print spoolers, screen savers, etc?
>I don't now about OS/2, but on UNIX workstations and Amigas you just run
>ordinary programs in the background to do this sort of thing.

You do much the same thing in OS/2. Note, however, that a lot of that kind of
function is supplied as an integral part of the operating system, especially
print spooling and screen blanking. The TCP/IP package runs its daemons by
starting them from STARTUP.CMD, OS/2's equivalent to AUTOEXEC.BAT. You can
also place program objects in the Startup folder, and the Workplace Shell will
start them automatically on initialization (that's how I start KA9Q for PM on
that box). OS/2 provides commands for starting a program in a background
session.
--
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
[e-mail]      | adequately be explained by stupidity.
     We survived Jimmy Carter; we'll (probably) survive Bill Clinton.