custom bios bin

[Sus~]

what does one use to read and alter the original bios bin?

[qball]

not sure what you mean?

Hit [f8] upon boot when message says:

"Hit [f8]/esc/whatever to enter BIOS setup"???

[Sus~]

nope.. *s* I mean as.. read the bios on the program level..the absolute guts of it.

[qball]

ok, *s*...

but you asked:


what does one use to read and alter the original bios bin?


what do you use?

Most use the BIOS setup program!


read the bios on the program level..the absolute guts of it


kinda like the program that allows me to configure my BIOS settings, guts like. right? *da*?

iffin 'flashin me BIOS" updates "BIOS"

you tell me:

'how does 'flashing' BIOS proggies work'?

"how do firmware updates occur?"

Start with:

http://www.pcwebopaedia.com/TERM/P/PROM.html
then:
http://www.pcwebopaedia.com/TERM/E/EEPROM.html

[Sus~]

I know how to flash a bios,
I know how to use my bios setup ..
I know what each thing in the set up IS...

What I am LOOKING for is something that allows me to read the actual program language.. each and every thing that is PART of that bios BIN.

Or quit simply what language do they use so I can dnld the appropriate program and view it myself.

[Quandary]

Um.. a BIN file would be machine code (bin = binary = compiled executable). That's the short answer as to 'what language they use.'

The long answer:

They could use anything from C++ to assebly language to write out the BIOS prog because they have a compiler on thier end. It really doesn't matter to you what language was originally used because all you are going to get back from it is assebly code. And unless you know what all of the opcodes for that chip are (I'll bet an awful lot that it ain't using plain old x86 assebly commands) you are *still* screwed.


Don't screw with your bios. It isn't worth it.

-Q

[Sus~]

That was exactly the answer I was looking for.

*s*