Re: MacSpeech Dictate Amazon reviews - comments?

This is a deal killer for me as well. I was just getting ready to
upgrade from iListen to Dictate.

But I need to install on two machines: my Mac Pro in the office, and my
MacBook Pro when I'm on the road. Clearly as a single user, I will only
USE one machine at a time, but I need it on two machines.

The pain involved in moving licenses and reinstalling software isn't
worth the hassle. Buying two licenses and then future upgrades
(discounts of which are often limited to one/customer) isn't worthwhile
for me.

So I guess I'll move to Dragon when the time comes. Bummer.

On the good news front, it sounds like they've figured out how to
install a license for every account on a machine. I wish all developers
would do that. I have a number of packages (shareware and commercial)
that require entering license keys for each account on the system, even
though the license terms read like a machine-wide license.

In article
<e70d20ac-60f5-4591-82f7-1a6790e57f89@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
billmcc <william.mcclatchey@xxxxxxxxx> wrote:

2. The real deal killer for me is the license structure. I don't
believe that anyone has addressed this issue in the thread. Unlike
many other software packages, and indeed unlike Dragon in Windows, the
license is to the hardware and not to the user. ie you can only
install it on one machine at a time. And this is enforced, not
allowing more than one hardware activation. In Dragon, multiple
machines are allowed to install the software, but only one user per
license. This is a really big deal in the medical world where most
providers have several locations, and multiple machines. This will
render the software unusable in the medical professional environment.
A real shame since this is one of the highest penetrations of Mac
hardware in the market, and a market that should have been a slam dunk
for Dictate. I don't understand the logic of single hardware install
license, but I guess it is not the first time that a company has shot
itself in the foot over this issue. A much more reasonable license
structure for a product of this type, since an individual purchases,
uses, and licenses the software, is to restrict the use to one
individual on any machine.


----== Posted via Pronews.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.pronews.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= - Total Privacy via Encryption =---
.

Relevant Pages

  • Re: OEM activation - where do I stand?
    ... All the other hardware remained the (hardrive, gfx card, memory etc. even the case with the license sticker on). ... Yesterday I had a total harddrive failure so replaced the harddrive and did a clean install. ... This time when I tried to activate Windows it wouldn't as it claimed that the product key and be activated too many times. ...
    (microsoft.public.windowsxp.general)
  • Re: OEM activation - where do I stand?
    ... All the other hardware remained the (hardrive, gfx card, memory etc. even the case with the license sticker on). ... Yesterday I had a total harddrive failure so replaced the harddrive and did a clean install. ... This time when I tried to activate Windows it wouldn't as it claimed that the product key and be activated too many times. ...
    (microsoft.public.windowsxp.general)
  • Re: Swapping XP licences between 2 PCs
    ... like to swap the versions of windows between the 2 machines so I can ... The OEM license is tied to the qualifying hardware with which the license was purchased. ...
    (microsoft.public.windowsxp.basics)
  • Re: VMS is younger than Windows
    ... PC hardware and boot the new hardware ... all the machines in the lab. ... There are also license issues. ... blow the motherboard on an machine with an OEM license, put in a replacement motherboard of a new type, ...
    (comp.os.vms)
  • Re: VMS is younger than Windows
    ... PC hardware and boot the new hardware ... all the machines in the lab. ... There are also license issues. ... blow the motherboard on an machine with an OEM license, put in a replacement motherboard of a new type, ...
    (comp.os.vms)