Re: A86: memory viewer/editor


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

Re: A86: memory viewer/editor



In a message dated 97-10-28 01:52:04 EST, you write:

> 
>  Steve86Asm@aol.com wrote:
>  > 
>  > In a message dated 97-10-27 15:56:56 EST, you write:
>  > 
>  > >
>  > >  Steve86Asm@aol.com wrote:
>  > >  >
>  > >  > In a message dated 97-10-27 03:35:49 EST, you write:
>  > >  >
>  > >  > >
>  > >  > >  im making another memory editor that is like memedit86 except 
> souped
>  > up.
>  > >
>  > >  > >  i would like to know if anyone else has done this and if they
>  > >  > >  encountered these problems:
>  > >  > >
>  > >  > >  if the program quits with ret the routine at the current address

> that
>  > 
>  > > is
>  > >  > >  being looked at is called from the program on exit (this is way 
> weird
>  > >  > >  and i looked through all my code, found no cause of it). so i
have 
> to
>  > >  > >  use the new getkey so you can break out of it by pressing 2nd-ON
>  > >  > >
>  > >  > >  it freezes up when viewing some addresses around page 3, what is
>  > > located
>  > >  > >  there and do you have any ideas why this would happen there?
>  > >  > >
>  > >  > >  btw i found some interesting effects that happen to the screen 
> when
>  > you
>  > >  > >  edit some of the addresses towards the end, it turns on pixels
at 
> the
>  > >  > >  bottom of the screen depending on the value you change them to
>  > >  > >
>  > >  >
>  > >  > The last section of the memory is the video mem, so when you edit
it, 
> it
>  > >  > turns on/off pixels.
>  > >  >
>  > >  > ~Steve
>  > >
>  > >  and crashes the calc :)
>  > >
>  > 
>  > Crashes the calc when you change the last couple bytes?  wierd...  you 
> never
>  > mentioned that.
>  > 
>  > ~Steve
>  
>  yeah well i think theyre only sposed to handle on and off on the pixels
>  so when u put in other values they sometimes crash it or else turn on 5
>  or six pixels at a time
>  

No, each bit represents a pixel, so no matter what is in each byte, it is
always a valid value.

~Steve