🚀 go-pugleaf

For those new to this thread can someone please assist me.
Rod Speed cant see why my defenition of firmware is accurate.

I State:
> Firmware is a generalisation for software that runs from the same place it
> is stored.
>
> The actual memory that stores the software can be any number of things the
> most populat being....
>
> Flash Memory bank (Whole lot has to be read and rewritten to change 1 bit)
>  or
> EEPROM (Electrically Erasable Programmable Read Only Memory - single bit
> changable)
>
> He sights that a PC-BIOS isn't called firmware commonly so it's not
firmware.


He says that:
> IT IS NOT POSSIBLE TO HAVE A
> NICE TIDY PRECISE DEFINITION OF THE TERM FIRMWARE

I have told him on many occasions that a PC-BIOS is firmware but....


"Rod Speed" <rod_speed@yahoo.com> wrote in message
news:prgz5.4613$O7.75155@ozemail.com.au...

> >> Quite a bit of the time its actually run from ram, not the place its
stored.
>
> > So it just magically copies itself from the rom to ram at boot time?
>
> Completely and utterly irrelevant how it gets into
> ram you pathetic excuse for a bullshit artist. It clearly
> doesnt run from where it is stored after its in ram.

We were talking about Firmware in general, You introduced the PC-BIOS
analogy so I set you straight saying that it's an OPTION. A BIOS is still
FIRMWARE because it still runs from the place it's stored before it gets
copied to ram IF you have selected that option....


> > That is a choice on PC's not embedded Microcontrollers or PHONES BTW...
>
> Got SFA to do with where a PC bios fits your pathetically inadequate
> 'definition' of firmware you pathetic excuse for a bullshit artist.
>
> Keep digging.

You dug yourself the hole...
Read it again.. you might glean more understanding the second time round...

>
> >>> but your busy nitpicking here rather than providing
> >>> a clear concise argument for your case.
>
> >> Pathetic really. I originally said very concisely,

No you stated another example of My argument...


> > You state this fact and can't provide alternate evidence to your
support.
>
> More of your childish lying, I've provided just that.
>
> You did too with the 'internal combustion engine'

I'm Human, Meaning you are?

>
> I say again for the pathetically intellectually crippled, there aint
> no nice tidy perfect definition,  like with quite a bit of technology.

WHAT TECHNOLOGY??

> You cant be THAT thick. IT IS NOT POSSIBLE TO HAVE A
> NICE TIDY PRECISE DEFINITION OF THE TERM FIRMWARE.
>
> Stamping that tiny foot and demanding one cant change
> that little boy.  No matter how much of a trantrum you chuck.
>
> >>> If it is such an ambiguous term
>
> >> No one ever said it is. Just that 'there aint no nice tidy
> >> perfect definition, like with quite a bit of technology'
>
> > If its not anbiguous then what does "not precise" mean?
>
> No point in trying to explain the difference to someone
> as stupid as you boy.  It should be obvious.
>
> >> Cant you even manage to read and comprehend the
> >> simplest sentence ? Hardly any words or more than one
> >> syllable, even you should be able to manage that one.
>
> >>> and obviously SO many people dont know what it is
>
> >> Just as true of many technical terms you stupid posturing child.
>
> > You can't name any,
>
> More of your childish lying. The ones I named are there for all to see.
>
> > but there are SO MANY!!!
>
> There are indeed. Like that or lump it.

You cant produce one yet you continue to make wide open blanket statements
like that last one.

>
> >>> then you will have no trouble showing that a FIRMWARE
> >>> dosen't run from the same place that the code is stored...
>
> >> Just did, twice. Keep digging.
>
> > Where?
>
> Pathetic.

Oh your NIC-bootrom and the BIOS??
Soz they are both firmware applications....

Your beat, give up?