[RANT]False Beeprog. AGAIN.

[Dave G4UGM]

> -----Original Message-----
> From: cctalk [mailto:cctalk-bounces at classiccmp.org] On Behalf Of Paul
> Koning
> Sent: 23 June 2015 17:10
> To: General Discussion: On-Topic and Off-Topic Posts
> Subject: Re: [RANT]False Beeprog. AGAIN.
> 
> 
> > On Jun 23, 2015, at 12:03 PM, Johnny Billquist <bqt at Update.UU.SE> wrote:
> >
> > On 2015-06-23 17:59, Alexandre Souza wrote:
> >>
> >>> I doubt there any legal problems with their course of action. They
> >>> are not obliged to ensure that their software works correctly on a
> >>> pirate copy of their hardware.
> >>> If they add some additional checks, and they trap out on a clone, I
> >>> doubt that could be considered illegal. They do not try to destroy
> >>> your device. Their software just refuse to run. And I can't see it
> >>> other than they are in their right to do that. Talk with the
> >>> manufacturer of the clone for a software update from them instead.
> >>
> >>    If you use a software newer than 2.62, it bricks your clone device.
> >> Period.
> >
> > Yes. Ask the manufacturer of the device to fix it. Do you really expect that
> someone who have nothing to do with the device has any responsibility
> here? You (or whoever) install software that was not intended for the device
> on it anyway, and then you blame the maker of that software.

They have deliberately damaged it. If using software you don't own is THEFT as the various copyright organizations want us to believe then this is Criminal Damage and Vandalism.
This backfired badly on FTDI ....

> 
> It depends.  If the failure is an accidental side effect of a failed attempt to talk
> to the device, that’s excusable.  If the code goes out of its way to disable the
> device, it is not.  It’s a bit like bringing your Ford to a Chevy garage.  A result
> of “I can’t fix that” is fine.  Having the technicians pull out the spark plugs and
> say “ok, here is your car back” is not.
> 
> >
> > Do you also try to install OS-X on a DELL laptop, and claim that it's
> > Apples fault that your DELL machine don't work? (God knows what
> > interesting things might happen if you actually try this...)
> 

Pretty common these days...

http://www.macworld.com/article/1140818/hackbook.html

> Most likely it will detect the wrong hardware and simply say “not supported”
> and stop.  But it won’t wipe the device BIOS in retaliation.
> 
> 	paul

Dave
G4UGM