Article View: alt.comp.hardware
Article #829Re: Nokia Firmware upgrade
From: Rod Speed
Date: Sun, 24 Sep 2000 00:00
Date: Sun, 24 Sep 2000 00:00
208 lines
8323 bytes
8323 bytes
Some pathetic excuse for a bullshit artist hiding behind Lefty2446 <lefty2446@**nospam**hotmail.com> wrote in message news:39cd9b03$0$26544$7f31c96c@news01.syd.optusnet.com.au... > For those new to this thread can someone please assist me. They aint done so yet boy. Have you the remotest concept of how many are reading this particular thread and pissing themselves laughing at your predicament ? Obviously not. > Rod Speed cant see why my defenition of firmware is accurate. For the rather obvious reason that there are plenty of examples of what fits you 'defenition' of firmware which aint firmware. > I State: >> Firmware is a generalisation for software >> that runs from the same place it is stored. And there are plenty of obvious examples of 'software that runs from the same place it is stored' which aint called firmware like NIC boot roms. And there are plenty of examples of what you claim is firmware, which aint 'software that runs from the same place it is stored' most obviously PC motherboard bios. >> 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) And that crap completely mangles the erasure story too. >> He sights that a PC-BIOS isn't called >> firmware commonly so it's not firmware. Thats what matters with that particular technical term, how its commonly used. No one actually made you Pope so you get to rule ex cathedra that your pathetic excuse for a 'defenition' is anything more than your pig ignorant bullshit. Cant imagine why for the life of me. > He says that: >> IT IS NOT POSSIBLE TO HAVE A NICE TIDY >> PRECISE DEFINITION OF THE TERM FIRMWARE He's right. No one can do that, no matter how many tantrums you chuck little boy. > I have told him on many occasions that a PC-BIOS is firmware but.... Wota pity it doesnt even fit YOUR 'defenition' you silly little child. > Rod Speed <rod_speed@yahoo.com> wrote >>>> 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 were desperately attempting to bullshit your way out of your predicament and fooling absolutely no one at all. Ever. > You introduced the PC-BIOS analogy Taint an 'analogy' its an EXAMPLE of what you claim is firmware which clearly doesnt always 'runs from the same place it is stored' > so I set you straight Yet another of your pathetic little fantays. > saying that it's an OPTION. Wota pity your 'defenition' says firmware is ''software that runs from the same place it is stored' and when its shadowed, it clearly doesnt 'run from the same place it is stored' Keep digging. > 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.... Taint the only way it gets shadowed you pathetic excuse for a bullshit artist. And fuck all of it 'runs from the same place it is stored' even if it does do the remapping itself. The vast bulk of the bios DOESNT 'run from the same place it is stored' Keep digging. >>> 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... Pathetic really, even you should be able to manage better than that. > Read it again.. you might glean more understanding the second time round... Pathetic really, even you should be able to manage better than that. >>>>> 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... Childish lying, completely trivial for anyone to check on that. And your peurile deleting of what I said there. Fools absolutely no one at all. As always. >>> 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? Pathetic really, even you should be able to manage better than that. >> I say again for the pathetically intellectually crippled, there aint >> no nice tidy perfect definition, like with quite a bit of technology. > WHAT TECHNOLOGY?? Pathetic really, even you should be able to manage better than that. >> 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 More of your childish lying. The ones I named are there for all to see. > yet you continue to make wide open blanket statements like that last one. More of your childish lying. The ones I named are there for all to see. >>>>> 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?? The fuckwit must be a rocket scientist or sumfin. > Soz they are both firmware applications.... Wrong. As always. A motherboard bios doesnt even fit YOUR pathetic excuse for a 'defenition' > Your beat, give up? Pathetic. Try harder little boy.
Technical Details
Message-ID:
<5wjz5.4980$O7.77923@ozemail.com.au>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<39c9cbdb$0$26552$7f31c96c@news01.syd.optusnet.com.au> <39ca234c$0$26548$7f31c96c@news01.syd.optusnet.com.au> <pDpy5.1725$Z06.14402@news-server.bigpond.net.au> <39cc0c19$0$12088$7f31c96c@news01.syd.optusnet.com.au> <4nXy5.2958$O7.59637@ozemail.com.au> <39cc4dd5$0$26528$7f31c96c@news01.syd.optusnet.com.au> <Zd_y5.3177$O7.61975@ozemail.com.au> <39cc9711$0$26538$7f31c96c@news01.syd.optusnet.com.au> <pq7z5.4032$O7.68357@ozemail.com.au> <39cd2434$0$26533$7f31c96c@news01.syd.optusnet.com.au> <y1bz5.4074$O7.70227@ozemail.com.au> <39cd4d78$0$12088$7f31c96c@news01.syd.optusnet.com.au> <8mdz5.4272$O7.72359@ozemail.com.au> <39cd7993$0$26516$7f31c96c@news01.syd.optusnet.com.au> <prgz5.4613$O7.75155@ozemail.com.au> <39cd9b03$0$26544$7f31c96c@news01.syd.optusnet.com.au>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fb718,4387fef30f6d23cd X-Google-Attributes: gidfb718,public X-Google-Thread: f5f89,4825fafce09ddc95 X-Google-Attributes: gidf5f89,public From: "Rod Speed" <rod_speed@yahoo.com> Subject: Re: Nokia Firmware upgrade Date: 2000/09/24 Message-ID: <5wjz5.4980$O7.77923@ozemail.com.au> X-Deja-AN: 673449824 Distribution: world References: <39c9cbdb$0$26552$7f31c96c@news01.syd.optusnet.com.au> <39ca234c$0$26548$7f31c96c@news01.syd.optusnet.com.au> <pDpy5.1725$Z06.14402@news-server.bigpond.net.au> <39cc0c19$0$12088$7f31c96c@news01.syd.optusnet.com.au> <4nXy5.2958$O7.59637@ozemail.com.au> <39cc4dd5$0$26528$7f31c96c@news01.syd.optusnet.com.au> <Zd_y5.3177$O7.61975@ozemail.com.au> <39cc9711$0$26538$7f31c96c@news01.syd.optusnet.com.au> <pq7z5.4032$O7.68357@ozemail.com.au> <39cd2434$0$26533$7f31c96c@news01.syd.optusnet.com.au> <y1bz5.4074$O7.70227@ozemail.com.au> <39cd4d78$0$12088$7f31c96c@news01.syd.optusnet.com.au> <8mdz5.4272$O7.72359@ozemail.com.au> <39cd7993$0$26516$7f31c96c@news01.syd.optusnet.com.au> <prgz5.4613$O7.75155@ozemail.com.au> <39cd9b03$0$26544$7f31c96c@news01.syd.optusnet.com.au> X-Priority: 3 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Trace: ozemail.com.au 969786497 210.84.49.193 (Sun, 24 Sep 2000 20:08:17 EST) Organization: OzEmail Ltd, Australia X-MSMail-Priority: Normal NNTP-Posting-Date: Sun, 24 Sep 2000 20:08:17 EST Newsgroups: alt.comp.hardware,aus.comms.mobile