1. File Examiner 1.1
------=_NextPart_000_0016_01BF91C0.23A49440
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Time moves at a different rate when you are programming, Ive noticed! =
LOL
Ive updated File Examiner so that it can now read in files above 32k in =
size, and also so you can key in the address of the byte to change, and =
lastly added progress bars. You can download it from =
www.spectresoftware.co.uk but the link is the same as the old one, and =
filename of the zip too.
------=_NextPart_000_0016_01BF91C0.23A49440
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2722.2800" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Time moves at a different rate when you are =
programming, Ive=20
noticed! LOL</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>Ive updated File Examiner so that it can now read in =
files=20
above 32k in size, and also so you can key in the address of the byte to =
change,=20
and lastly added progress bars. You can download it from <A=20
href=3D"http://www.spectresoftware.co.uk">www.spectresoftware.co.uk</A> =
but the=20
link is the same as the old one, and filename of the zip=20
------=_NextPart_000_0016_01BF91C0.23A49440--
2. Re: File Examiner 1.1
Well, this is the third time that I have tried to answer your post of your new
Examiner code, and my machine has hung up twice. Don't know the cause
yet, but just for safety, I am not quoting you. Some stray character
somewhere causing trouble...speaking of hex.
The new version looks great and all works that didn't work before. Got past
the false file end and was able to look at files greater than 32k, though it
ain't speedy going from seg to seg. Now we get to the nitty gritty of updating
files in the raw. The reason I wanted a wider view was so that I could
see ASCII strings in the binary. Also, many times when I have update
instructions, they go like this. "Go to a particular hex offset in the file and
then go to the hex address you find at that offset." I can accomplish that
with your program, but I will need a pencil and some time. We need the
location and the content in hex as well as decimal and ASCII, both for
information and for entry. There is plenty of room for more boxes on your
current setup.
I used to have to wade through 10-20 hex and EBCDIC(read ASCII for our
purposes) dumps every morning on the way into my office and many of
them were more than a half box of 11x14 paper. They used a format
somewhat like the following...adjusted for narrower format.
Address ....2 hex dwords.... ...ASCII...
00F8BCD0 30313233 34353637 0123 4567
00F8BCD8 00410042 43004445 .A.B C.DE
where the dots represented non-printing hex combinations. Needless to say,
the decimal address in a situation like this is basically irrelevant. Now, as
my cursor moves across one of these sets, a highlight should move across
the other set. The cursor should be able to tab between the sets. As the
cursor moves, the decimal can appear in one of your windows. It would even
work if multiple bytes could be updated at once by entering decimal triplets
delimited by a space... 048 049 , but I would really want to be able to make
ASCII and especially hex changes also. You might even put in a binary
window for those who need to change bits in a map. Anyway, just my
suggestions. It looks a lot better and is functional.
Everett L.(Rett) Williams
rett at gvtc.com
3. Re: File Examiner 1.1
----- Original Message -----
From: "Everett Williams" <rett at GVTC.COM>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Sunday, March 19, 2000 11:39 AM
Subject: Re: File Examiner 1.1
> Well, this is the third time that I have tried to answer your post of your
new
> Examiner code, and my machine has hung up twice. Don't know the cause
> yet, but just for safety, I am not quoting you. Some stray character
> somewhere causing trouble...speaking of hex.
>
> The new version looks great and all works that didn't work before. Got
past
> the false file end and was able to look at files greater than 32k, though
it
> ain't speedy going from seg to seg. Now we get to the nitty gritty of
updating
> files in the raw. The reason I wanted a wider view was so that I could
> see ASCII strings in the binary. Also, many times when I have update
> instructions, they go like this. "Go to a particular hex offset in the
file and
> then go to the hex address you find at that offset." I can accomplish that
> with your program, but I will need a pencil and some time. We need the
> location and the content in hex as well as decimal and ASCII, both for
> information and for entry. There is plenty of room for more boxes on your
> current setup.
>
> I used to have to wade through 10-20 hex and EBCDIC(read ASCII for our
> purposes) dumps every morning on the way into my office and many of
> them were more than a half box of 11x14 paper. They used a format
> somewhat like the following...adjusted for narrower format.
>
> Address ....2 hex dwords.... ...ASCII...
>
> 00F8BCD0 30313233 34353637 0123 4567
> 00F8BCD8 00410042 43004445 .A.B C.DE
>
> where the dots represented non-printing hex combinations. Needless to say,
> the decimal address in a situation like this is basically irrelevant. Now,
as
> my cursor moves across one of these sets, a highlight should move across
> the other set. The cursor should be able to tab between the sets. As the
> cursor moves, the decimal can appear in one of your windows. It would even
> work if multiple bytes could be updated at once by entering decimal
triplets
> delimited by a space... 048 049 , but I would really want to be able to
make
> ASCII and especially hex changes also. You might even put in a binary
> window for those who need to change bits in a map. Anyway, just my
> suggestions. It looks a lot better and is functional.
Reminds me of Xtree, which still use, i was using it this morning to rename
advert.dll. I keep these old dos apps around just so i can break the panes
in windoze, lol.
Kat
4. Re: File Examiner 1.1
-----Original Message-----
From: Everett Williams <rett at GVTC.COM>
To: EUPHORIA at LISTSERV.MUOHIO.EDU <EUPHORIA at LISTSERV.MUOHIO.EDU>;
kingpete at KINGPETE.F9.CO.UK <kingpete at KINGPETE.F9.CO.UK>
Cc: Everett Williams <rett at GVTC.COM>
Date: Sunday, March 19, 2000 6:45 PM
Subject: Re: File Examiner 1.1
>Well, this is the third time that I have tried to answer your post of your
new
>Examiner code, and my machine has hung up twice. Don't know the cause
>yet, but just for safety, I am not quoting you. Some stray character
>somewhere causing trouble...speaking of hex.
Im not sure why either! Problem with the list serve?
>
>The new version looks great and all works that didn't work before. Got past
>the false file end and was able to look at files greater than 32k, though
it
>ain't speedy going from seg to seg.
Thanks for your comments. File Examiner was intended as just that... but I
guess it would be nice to have better file edit functions and a wider
window. To implement this I am thinking of redesigning the interface
completely, give me a couple of days.
>Now we get to the nitty gritty of updating
>files in the raw. The reason I wanted a wider view was so that I could
>see ASCII strings in the binary. Also, many times when I have update
>instructions, they go like this. "Go to a particular hex offset in the file
and
>then go to the hex address you find at that offset." I can accomplish that
>with your program, but I will need a pencil and some time. We need the
>location and the content in hex as well as decimal and ASCII, both for
>information and for entry. There is plenty of room for more boxes on your
>current setup.
Well Im grateful for your suggestions and will be improving the File
Examiner shortly.
Pete King.
5. Re: File Examiner 1.1
Private thru the list.
Agent Spectre wrote:
>Im not sure why either! Problem with the list serve?
Did not mean to accuse. Probably at my end entirely, but I was getting
very frustrated after typing the reply three times...even at my typing speed.
snip
>
>Thanks for your comments. File Examiner was intended as just that... but I
>guess it would be nice to have better file edit functions and a wider
>window. To implement this I am thinking of redesigning the interface
>completely, give me a couple of days.
>
>>Now we get to the nitty gritty of updating
>>files in the raw. The reason I wanted a wider view was so that I could
>>see ASCII strings in the binary. Also, many times when I have update
>>instructions, they go like this. "Go to a particular hex offset in the file
>and
>>then go to the hex address you find at that offset." I can accomplish that
>>with your program, but I will need a pencil and some time. We need the
>>location and the content in hex as well as decimal and ASCII, both for
>>information and for entry. There is plenty of room for more boxes on your
>>current setup.
Maybe I was a bit too frank in my discussion. Unfortunately, while hex
examination is a rarity in modern programming, it used to be one of the
standard debugging methods. We got quite good at it, and the tools were
well suited for the purpose even though we didn't have the interactive
capabilities now available. Normally, my hex dumps came 1000 to 3000
pages at a whack. I could even guide an inexperienced operator through a
dump over the phone...allowing the person to report to me what I needed
to know without a 40 mile trip into downtown Houston. Necessity being the
mother of invention, the style of such dumps quickly settled down into the
format that I mentioned. Since it was the equivalent of Euphoria's Ex.err,
it also included register dumps and calling traces. A stack dump would
be the equivalent on the Intel and most other processors and PC OS's.
My perspective on what you have written was from the viewpoint of one
who has had and used such tools as much as anyone that I can imagine.
The only tool that was close to what I have been proposing to you was a
little afterthought editor attached to a DOS menu and command product.
A thing called AutoMaxx had a direct hex editor that was very fast and
very powerful. The basic product that you threw out made me hungry for
a tool that I have often missed.
Everett L.(Rett) Williams
rett at gvtc.com
6. Re: File Examiner 1.1
My most public apologies to Pete King. I meant that last post to be private,
but hit the wrong button.
Everett L.(Rett) Williams
rett at gvtc.com
7. Re: File Examiner 1.1
>My most public apologies to Pete King. I meant that last post to be
private,
>but hit the wrong button.
>
>Everett L.(Rett) Williams
>rett at gvtc.com
>
No apologies needed Everett, I welcome your comments and opinions : )
I can remember entering Hex in from the Program Pitstop section of Your
Sinclair, back when I was about 11, using an editor that didnt even let you
delete your mistakes! LOL
Pete King.
