🚀 go-pugleaf

In article <22771@venera.isi.edu>, jas@ISI.EDU (Jeff Sullivan) wrote:
> 
> In article <mike_steiner-291092114456@192.35.50.131> mike_steiner@qm.claris.com (Mike Steiner) writes:
> 
> > I ordered my upgrade to Helix Express on Sept. 30th.  Yesterday I received
> >it (exactly 4 weeks after I mailed my check); it had been shipped on Oct
> >22; three weeks after I mailed the check.  Yesterday, I also received my
> >bank statement yesterday.  The check cleared the bank on October 5th.  That
> >means that Helix Technologies did not ship until 17 days after they cashed
> >the check (more than that, allowing for the float).  I do not like this
> >policy at all; it gives the impression that they were/are short of cash and
> >had to receive upgrade fees before they could pay for at least some of the
> >expenses involved in providing the upgrades.
> 
> Or, they cashed the check, and shippied HE as soon as it was ready.
> Maybe they even thought HE was going to be ready 2 weeks earlier than
> it was.

Most places don't cash the check until they ship the product.
 
> >Another thing that I don't like is that when you run the  buckler
> >application to join the two halves of the application, you have to enter a
> >four-digit serial number and a 20-character (approximation; I did not count
> >the exact number of characters) "enabling code."  The code is provided on a
> >mailing label that is too big to tape to the floppy disk.  If I had known
> >that the product had this protection on it, I may not have ordered the
> >upgrade.  I don't like copy protection of any sort whatsoever.
> 
> You have some really extreme definitions of copy protection--how hard
> is it to write the SN on your floppy?

The size of the label was incidental.  Why is a 20+ character alphanumeric
needed in order to install a product?  My definition of copy protection is
anything that prevents you from running the software from a direct copy of
a master disk or that requires more than a simple installation without
entering any data from elsewhere.

+---------------------------------------------------------------------+
|Now that I have a reader that can do .sigs, I can't think of a witty |
|one to put here, so I won't.  All normal disclaimers apply.          |
+---------------------------------------------------------------------+