TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: The Dark Ages etc - reply From:Doc <dlettvin -at- attbi -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 28 Jun 2002 15:21:03 -0400
Sorry to get to you so late about this, but there is a solution to
If your IT people do an internet search for "software metering" they
will find a wide selection of products available.
These products track the use of software licenses and let IT do some
1. Track the use of licenses to determine future needs.
2. Manage licenses by quantity. This lets IT set the number of
purchased licenses in the software. It also allows several people to
use the same license at different times. Each time someone opens the
program they "check-out" a license. This is done a first come first
3. Prioritize users. This lets IT rank users of a license by priority
to let people with critical jobs access the software consistently.
4. Allow license overruns. This lets IT permit users to check out the
license even if none is available. Many It departments use this in
conjunction with #1 to determine software purchasing.
5. Determine if there is software that is not being used.
Maybe that will help the situation.
David W Lettvin
South Hamilton, MA
"You cannot grow a beard in a moment of passion." - G.K. Chesterton
On Wed, 19 Jun 2002 20:59:25 +0100, "Mark Emson"
<mt -dot- emson -at- ntlworld -dot- com> wrote:
>Thanks again for the comments.
>Registry foul ups were one of the topics of discusion and I agree, I doubt
>that the install, de-install plan will run for long. The considered opinion
>(guessing game) was that if the sofware is fully removed the registry will
>be fairly clean. If the softwre is then re-installed it will overwrite any
>remenants that it may have left. If worst come to the worst, all of our
>machines are of a standard base spec that is ghosted onto one of our servers
>and hence the whole system can be re-installed in very little time. All of
>our working files are remote on the servers and so, nothing will be lost by
>My personal feeling is that IT want to make a point to us and the software
>manufacturers, even if it entails work for them. Anyway, as soon as they
>'perfect' the system for quick fool proof :~) installs I can see that
>they'll hand it over for us to do ourselves. Eventually I think they'll
>buckle and we'll end up buying more licences but for now this seems to be
>As for slapping the boss with a load of e-mails and still being in
>employement, I was admit, carefull not to leave her with any of them and, at
>the end of the day it's only a job.
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
Save $600: Create great-looking Help files and software demos with
RoboHelp Deluxe. Get RoboHelp and RoboDemo - our new demo software - for one
low price. OR Save $100 on RoboHelp Office in June with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.