Re: A86: Death by Linux

To: assembly-86@lists.ticalc.org
Subject: Re: A86: Death by Linux
From: David Phillips <electrum@tfs.net>
Date: Sun, 27 Sep 1998 21:45:11 -0500
Delivered-To: assembly-86-outgoing@towerguard.unix.edu.sollentuna.se
Reply-To: assembly-86@lists.ticalc.org

Ok, to make this on-topic, I would say that it would be better to work with
what you have rather than disassemble your program.  However, if you some
of those routines that took you an hour and a half to write (like a 32-byte
RLE decoder), then you might benefit from disassembling the program and
copying those over.  However, for most other stuff, it would probably be
better to rewrite them.  Code is always better the second time around (if
you actually try).

What program are you using to look at the partition table?  I would assume
that a hex editor like that would allow you to look at it.  I have always
like the Norton Utilities Disk Edit (called something different in 4.5,
which I used on my 8088 with monochrome monitor and 21mb hard drive).  It
will let look at the physical disk and such.  I have used it for such
thnigs as getting rid of OS/2 partions (harder than it sounds, unless I'm
just dumb).

At 10:41 PM 9/27/98 -0400, you wrote:
>
>To summarize a long, sad tale, I tried to reinstall Linux today, but instead
>ended up destroying the partition table on my secondary hard drive. This
>drive was, of course, the drive that contained the latest version of my
>TI-86 programs. I have only a two-week old backup of the asm file that is
>missing half of the new code, and the actual program which i uploaded to my
>calc last night. I grabbed the program from the calc, but was wondering if
>its really a horrible task to try to disassemble something?? Is it
>impossible? Should I work up from the 2 week old file or disassemble the new
>one and keep going??
>
>Also, it MAY be possible to recover data from the drive simply because I
>never formatted it. It's basically got a blank partition table that i've
>been mucking around with trying to get an entry that worked (I've tried
>everything from FAT32 LBA to FAT 12 (which is for floppies and obviously
>would never work)) but no luck. I figured if i directly look at the data on
>the drive, it could be possible to search for the file... but does anyone
>know how this could be accomplished? I have no idea what programs do this...
>
>Anwyays, thanks  for your time
>
>-- Steve "Linux ate my hard drive" Horne
>
>

--
David Phillips
mailto:electrum@tfs.net
ICQ: 13811951
AOL/AIM: Electrum32