Mail Archives: djgpp/1999/05/15/11:51:43.2
Guillermo Rodriguez Garcia wrote:
> > You aren't writting to the hard-drive, you are writing to RAM. Now this
> >situation is VERY UNLIKELY, but it is still possible:
> [...]
> Are you sure that you can write to CMOS memory by writing to RAM? I
> think this is not possible.
It isn't a direct approach. We know that you can write code that writes to CMOS.
If you were to overwrite the return address of your function, and it were to jump into
memory that had instructions to overwrite CMOS (which could also have been put there
by jumping your array bound). That is how by just writting into RAM can cause (a few
clock-cycles later) your CMOS to be overwritten. I'm not arguing this is likely or
easy to produce, but it is possible.
> > It's not only the configuration you may loose, but the configuration PROGRAM
> >which BIOS loads. That could be very bad. Most boards these days allow upgrades
> >to the CMOS program to fix bugs, so this is a viable option.
> But this program is in flash ROM, not RAM, AFAIK.
>
> Anyway, I still ask: what hardware is being damaged here? It is all a
> mater of software / data / configuration. Nothing is broken. No need
> to buy new parts or replace any IC or component.
It has to be on reprogrammable chip if it wants to be updated by the vendor. If
the vendor can update it, that means that you data could be machine code to overwrite
the "flash ROM" or whatever.
You are right about that not causing any direct hardware damage, but as I
mentioned before, my CMOS controls my voltage to my processor, so if it screwed up, I
would smell smoke very soon.
--
(\/) Endlisnis (\/)
s257m AT unb DOT ca
Endlisnis AT HotMail DOT com
ICQ: 32959047
- Raw text -