Re: A86: Edit lock
[Prev][Next][Index][Thread]
Re: A86: Edit lock
ummmmm ok exactly how many ppl do you know that would pay for a basic
program?
-----Original Message-----
From: Jeff Tyrrill <Jeff_Tyrrill@msn.com>
To: 'assembly-86@lists.ticalc.org' <assembly-86@lists.ticalc.org>
Date: Sunday, February 08, 1998 2:05 AM
Subject: RE: A86: Edit lock
>
>I edit-lock my Basic programs mainly so some stupid lamer at some school
>doesn't change my name on my program to his own, and then sell it. Most
>people with Graph-Links or the means to un-edit-lock a program wouldn't do
>that. You might not think that anyone would, but I've seen it happen many
>times at my school, both people changing the author's name on a program,
>and people selling programs (that they didn't write).
>________________
>
>Jeff Tyrrill
>http://tyrrill-ticalc.home.ml.org/
>http://ti-philes.home.ml.org/
>
>
>-----Original Message-----
>From: Klukan [SMTP:renegade@bmt.net]
>Sent: Saturday, February 07, 1998 11:33 PM
>To: assembly-86@lists.ticalc.org
>Subject: Re: A86: Edit lock
>
>
>TGaArdvark@aol.com wrote:
>
>> > an edit locked program (as far as i know) has a null (00h) as it's
>> last
>> > character. can someone verify this?
>>
>> No, not basic anyway (I think it's a different type of variable for
>> asmcomped asm). For basic, it's a $FF anywhere in an un-
>> executed portion of the program that has no gotos that go
>> across it (Lbl searches crash on $FF's too).
>
>As far as I know, ASM programs cannot be edit-locked. For BASIC, it is
>a $FF character that causes the program to become edit-locked. I think
>that it must come at the end of the program, but I am not sure about
>that. ASM programs do not really need to be edit-locked, since once
>they are compiled, there is no way to edit them. That is unless you
>decompile it, which would generate code that is uncommented and is full
>of pointers and such. Anyway, there are programs that can un-edit-lock
>programs, so the feature is pretty much useless anyway.
>
>-Jeremy
>
>
>