Re: A83: Unsquish
[Prev][Next][Index][Thread]
Re: A83: Unsquish
In a message dated 3/2/99 4:33:08 PM Mountain Standard Time, DaBumer2u@aol.com
writes:
> > Right, thats what I meant, I was in a hurry (its almost the same thing
tho,
> > no need to get all defensive) ... oh was that what it was about...well,
I
> > see very little point in making a program to do this because I have a
> > feeling that there are very few people who want to unsquish programs and
> > don't have a graphlink. (speaking of which, dasm.zip on ticalc has a
> > bin2hex program in it). He could (assuming he was at least partially
> adept
> > at asm), write a quick prog that looked up the progs location and
> outputted
> > it to another program in "unsquished" form using (I forget who's)
makehex
> > routines...
> >
> > -Dan
>
> I dont think that would be to easy to accomplish.
>
> -Dustin
>
<sigh> No graphlink? Damn...the "unsquish" task would be _so_ easy if you did.
(I mean, Microsloth's Visual Basic could do it!)
Well, you could make a program that used LDIR in some _very_ creative
ways...for example, create a byte equivlaency chart (e.g. byte C9 = ASCII
characters "C" and "9"...anybody care to help me optimize this?), and then
loop through the program to be unsquished, reading in the bytes, and then
writing to a seperate program that contained the unsquished ASCII characters.
Obviously I won't be the one making this--unless somebody is willing to help
:-)
This program would require maybe about 1.5K-2.5K of memory (if you're lucky),
not to mention the space you would need to hold the unsquished program (let's
say you're unsquishing Diamonds 1.9...you would need, I would estimate, 4500+
bytes of free RAM to hold the unsquished version.)
But I repeat Dan's sentiments...
Why would somebody want to unsquish a program?
--David
Follow-Ups: