Re: A82: Re: password program
[Prev][Next][Index][Thread]
Re: A82: Re: password program
There is a simpler solution but as I wrote it involves modifying Crash. What
you need to do is append your program to the end of CrASH, and modify the
var which is used to call CrASH so it calls you program. Your program then
checks the password and starts CrASH if it is correct. When the password is
first entered it is stored in a part of the mem which is unused and not
transmitted when a backup is send (the stach, display controller ram or
possibly a temp variable). Each time the program wants to check the password
it first checks to see whether the right password is stored in that
location, if so it just starts CrASH. Otherwise it prompts the user ofr a
password.
The above would be possible, but it does involve a bit of programming.
Another problem is that modifying CrASH is not that easy, there are a few
different places which are used to start CrASH, and you want to make sure
that the modifications work with all of them.
Dines
----- Original Message -----
From: Jimmy Conner <timagic@yahoo.com>
To: <assembly-82@lists.ticalc.org>
Sent: Saturday, March 27, 1999 8:28 AM
Subject: Re: A82: Re: password program
>
> I have thought about this alot lately.
> You would have to make sure that only your 'hacked'
> version is the only one out there. If it isn't the
> only one that they can use then it isn't doing much
> good to have one with a password.
>
> Also I really don't know too much about how Crash
> works I'm just started learning 82 asm, but I know 83
> asm fairly well so bear with me then just give me a
> slap upside the head later.
>
> First of all have a nice little installer program to
> run through Crash. You run the installer and it hides
> Crash (simple enough but I don't know if it would crash
> if you do this). Then it creates a new program that
> will run Crash (if it can be done with crash hidden).
>
> Now before it runs crash it checks a byte at the end
> of one of your programs to see if it is set or not. If
> so you run crash, if not you run a simple password
> program.
>
> Now here is the tricky part, then you run a interrupt
> program to see if they press [2nd] [Link]
> And if they do then you reset the byte to make you have
> to enter the password program again.
> This interrupt program would have to be set up to run
> anytime you exit crash but you would still have the
> problem of the interrupt program not being on when they
> decide to send it.
>
> Its just a thought though. I'm sure you all can
> elaborate on it to get it to work.
>
>
> Jimmy Conner
> ===
> »»»»»»»»»»»»»»»«««««««««««««««
> » TIMagic@beer.com «
> » http://www.timagic.cjb.net «
> »»»»»»»»»»»»»»»«««««««««««««««
> -PACA - Programmers Against Calculator Abuse
> Stop calculator mistreatment, use Calc'Em!
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
References: