Re: A86: Edit lock

[Prev][Next][Index][Thread]

Re: A86: Edit lock


Umm.. I think you're all wrong but no offence.  It doesn't change the 
program type.. All basic programs start with a two byte size and then 
a null byte ($00). After that comes the actual text. If you want it 
to be locked, just add a second null byte after the first.. Let's say 
you use this test program:

:DISP "HI"

The data would go like this for unlocked:
$0A00                ;the size
$00                     ;null byte
$444953502022484922                     ;the text 'DISP "Hi"'

Now for the locked version, it would be like this:
$0B00                ;size is one bigger for the extra null byte 
$0000                 ;null bytes needed for being locked 
$444953502022484922                     ;the text 'DISP "Hi"'

> On the computer, there is a protection option for programs.  What I believe
> this does is it changes the program type from $12 to maybe $32 (I haven't
> checked on the 86) and then it disappears from the edit menu.  You can also
> edit protect a program with $FF but then it is somewhat permanent.
> 
> -----Original Message-----
> From: Klukan <renegade@bmt.net>
> To: assembly-86@lists.ticalc.org <assembly-86@lists.ticalc.org>
> Date: Sunday, February 08, 1998 12:37 AM
> 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
> |
> |
> 
>
Follow-Ups: References: