Re: A82: CrASH bug not Galaxian bug


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

Re: A82: CrASH bug not Galaxian bug




GeradS711 wrote:
> 
> In a message dated 98-01-26 16:40:28 EST, you write:
> 
> > Barubary was right. There is no difference in my routine's performance
> >  between version 1.2 and 1.3 of CrASH. When the contrast changer is used
> >  in the game it is like one of those battery saver progs. It can make the
> >  screen darker than the TI-82 can with its nine settings. There is no
> >  problem if you set the contrast to the level of a normal TI-82
> >  setting. The problem occurs when you select a setting that has a higher
> >  contrast than the normal TI-82 settings. When you shut down the calc
> >  from CrASH, and turn the calc back on the screen is incredibly light.
> >  Well in order to remedy this I thought I had to raise the contrast so I
> >  tried 2nd+Up. Didn't work. I didn't realize that because a setting higher
> >  than the 82's normal ones was selected than I had to push 2nd+Down.
> >  Pushing 2nd+Down remedies the problem. For some reason that kind of
> >  problem doesn't happen using ASH. There is some problem with CrASH that
> >  won't allow contrast settings higher than that of an 82(Only when the
> >  calc is being shut down from CrASH). I noticed the problem when I
> >  originally started using CrASH when some of the battery saving progs
> >  didn't work on it, but I didn't think anything of it because I didn't
> >  really care whether or not the battery saving progs worked.
> >  The contrast problem is with CrASH not Galaxian, but it shouldn't
> >  stop you from using the game with CrASH because CrASH is a more stable
> >  shell than ASH and the problem is easily remedied if you push 2nd+Down
> >  when you restart your calc. And I'll continue to use and others will use
> >  my contrast routine until a better one is created(or ported). I have
> >  already implimented it into Galaxian, the next version of Orzunoid will
> >  have it, and some games by Ahmed El-Helw are going to have it(Duckhunt
> >  1.1 already has it). So c'mon CrASH people fix this problem. If you don't
> >  believe that it exists try running Battery Saver II using CrASH and
> >  selecting a contrast higher than 9. Then turn the calc off while still in
> >  the CrASH by pressing 2nd+ON. When you turn the calc back on the calc
> >  looks as if it has crashed. The screen is blank and the buttons don't
> >  seem to do anything. Push 2nd+UP to turn the contrast up and nothing
> >  happens. Push and hold 2nd+DOWN and the contrast goes back to normal.
> >  Finally, just to make this clear, no this problem was not caused by using
> >  Crash to Crash.
> >           Evil Sam
> >
> Umm, can't you just stick a domain check in there so it doesn't go higher than
> the 82 allows, it doesn't seem like it would take more than 2 lines of code (3
> if you count the label)

I no longer think the problem is going over the max contrast limit 
because it happens even when you don't. When I release the source with 
v2.0, you can look at the source and see if you can determine the 
problem.


References: