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:ending support for 16-bit/Win 3.1 From:Kristin Nietz <knietz -at- SHOWCASECORP -dot- COM> Date:Thu, 8 Jan 1998 11:34:57 -0600
This message is cross-posted to WINHLP-L and TECHWR-L.
After much discussion, my organization is planning to end development
and support of 16-bit applications. Following our next release, all
additional releases will be 32-bit only and thus require Windows
95/above or Windows NT. As we have a significant customer base still
using 16-bit/Windows 3.1, we plan to announce this change when we
rollout our next release, which will run on both 16-bit and 32-bit
platforms. In essence, we plan to warn our clients one release (and
several months) ahead of time before cutting off the 16-bit support.
My question: have any of you experienced this before, and how did you
handle it? We want to show that we're sensitive to the needs of our
clients, and we are concerned about how we stage this announcement. If
you have any press releases, notices, or client letters that you'd be
willing to share, I'd really appreciate it. Likewise, if you have any
thoughts to share about the reaction of your clients, I'd be interested
in hearing about that too.
If you'd like more background, feel free to e-mail me personally at
knietz -at- showcasecorp -dot- com -dot- Thanks in advance!
