🚀 go-pugleaf

Again, I suggest to talk to McAfee or Dr Solomon about exact details - I
remember some time ago (last year) I came across a virus spec sheet, on the
Net, which listed some (more than one) cmos viruses. I disagree with the
statement that the cmos would be corrupted if a virus or any other mini pgm
would install in unused space! - Writing to *unused* space never corrupts!
I am not going into hardware details as this would be foolish considering
the numerous different mobo designs on the market!

Stefan
--
*COSA IT Solutions /MS-OEM/MS-SBNL2
http://www.ozemail.com.au/~billis/cohp/cohp.htm
*Billi's Designer Studio
http://www.users.bigpond.com/kreidi/Studio/billishp.htm
___________________
Nostradamus once said:
"Quia non est nostrum noscere tempora nec momenta"
[It is not for us to know the times or the instants]

Richard RUDEK wrote in message <3576bee2.55962514@news.zeta.org.au>...
>"GroundHog" <kreidi@bigpond.com> wrote:
>
>>CMOS viruses are real - no doubt for me! I suggest to contact McAfee or
the
>>like for more detailed answers - there are quite some large virus
families
>>with cmos subtypes! Depending on the cmos chip there is more or
>>less 'waste' space, not used by the bios, which can be used by viruses if
>>the space is sufficient!
>
>[snip]
>
>I was going to leave this one alone, but your getting way off track now. A
>virus using "unused" CMOS RAM to store itself is crazy. Sure, some systems
>do contain 2KB or more. But the keyword here is *SOME*.
>
>Now apart from anything else, if a virus did install itself into CMOS RAM,
>a standard system could in no way execute code out of CMOS, therefore it
is
>no longer a virus. About the only thing it could do, is corrupt this RAM,
>which is typically used for BIOS configuration settings. That's probably
>enough though. RAM timming Chipset features etc, etc would be effected.
>  __   __   _______________________________
> //)) //)) | Richard RUDEK. MicroDek.      | Insert sh, ah,
>//\\ //\\  | Chatswood, Sydney. Australia. |  witty comment here. :)
>           `-------------------------------'