Re: reading BIOS dump
- From: Randy Howard <randyhoward@xxxxxxxxxxxxxxxxx>
- Date: Sat, 30 Dec 2006 03:57:15 GMT
On Fri, 29 Dec 2006 19:59:34 -0600, CBFalconer wrote
(in article <4595C806.55D90293@xxxxxxxxx>):
Randy Howard wrote:
On Fri, 29 Dec 2006 17:02:07 -0600, Bill Cunningham wrote
The answer to the OP's question is it starts at f0000 (f000:0000
for the old DOS crowd). You can open /dev/mem, seek to that
address and read it as if it were a file. It's the entire
"segment", or 64K in length.
Instead of going to the trouble to write a small C program what
about using the dd command. Copy if=/dev/mem to of= and use bs=64k
and seek=0xffff0 ? Would that work ? I'll try it if it sounds safe
I don't want to screw up my system.
Reading from /dev/mem can't hurt your system. Writing to it is
another matter entirely.
What if i/o is memory mapped? Reading a location may reset a
'ready' flag and/or empty a hardware buffer.
The original form of this question was in reference to Linux boxes. I
know of none that have such a problem to be worried about. Do you?
--
Randy Howard (2reply remove FOOBAR)
"The power of accurate observation is called cynicism by those
who have not got it." - George Bernard Shaw
.
- Follow-Ups:
- Re: reading BIOS dump
- From: CBFalconer
- Re: reading BIOS dump
- References:
- reading BIOS dump
- From: Bill Cunningham
- Re: reading BIOS dump
- From: Phlip
- Re: reading BIOS dump
- From: Randy Howard
- Re: reading BIOS dump
- From: Bill Cunningham
- Re: reading BIOS dump
- From: Randy Howard
- Re: reading BIOS dump
- From: CBFalconer
- reading BIOS dump
- Prev by Date: javatouch is your java companion with a different flavor
- Next by Date: Re: Shuffling a linked list
- Previous by thread: Re: reading BIOS dump
- Next by thread: Re: reading BIOS dump
- Index(es):
Relevant Pages
|
|