[Info-vax] Licenses on VAX/VMS 4.0/4.1 source code listing scans

Dave Froble davef at tsoft-inc.com
Fri Dec 10 20:10:35 EST 2021


On 12/10/2021 7:07 PM, Arne Vajhøj wrote:
> On 12/10/2021 4:50 PM, Dave Froble wrote:
>> On 12/10/2021 2:23 PM, Simon Clubley wrote:
>>> On 2021-12-10, Dave Froble <davef at tsoft-inc.com> wrote:
>>>> Instead, I'll ask these questions.
>>>>
>>>> What is the problem, if there is nobody to question such usage?
>>>>
>>>
>>> Ownership of assets doesn't cease just because a company fails.
>>>
>>> You are setting yourself and your customers up for a future owner
>>> of the VSI assets to come after you, especially if you reduce the
>>> resale value of those assets by coming up with a way to bypass the
>>> need for existing VMS customers to purchase more of those assets.
>>
>> If there is an entity that allows my customers to continue, then there isn't
>> an issue, is there?
>>
>> If there is not an entity, who, other than you and Bill, is going to really
>> give a damn?
>
> There can be cases where there is an entity  willing
> to sue copyright violaters without being  willing to
> sell a license.

It occurs to me this can be reversed.  Customers have an implied, if not more 
specific, contract with the vendor.  Should another entity acquire the software, 
and not fulfill this contract, perhaps they could be sued to force them to honor 
the contract.  Acquire the product, you also acquire the responsibilities.

This could be fun.  Lawyers could have a field day.

:-)

>>>> What is your opinion of a vendor potentially destroying a customer's business?
>>>
>>> You know what VSI have done by putting time limits on production
>>> licences and you could port away today if the risk is unacceptable
>>> to you.
>>
>> Porting is not an option.
>
> Porting is per definition an option for all software
> at all time.

Not when cost is involved.

> Everybody makes the decision to port or not port
> all the time - some think about it - some make a
> decision by not thinking about it.
>
> You can look at expected cost, risk and benefits of not
> porting and you look at expected cost, risk and benefits
> of porting and you make a decision.
>
> A port may be a rewrite from scratch if the code is
> totally non-portable. But there are plenty of
> technologies out there to pick and chose from.
>
> Arne


-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486



More information about the Info-vax mailing list