~BD~ <BoaterDave@hot.mail.co.uk> wrote in
news:7ridndLhg8MJXkfWnZ2dnUVZ8rqdnZ2d@bt.com:

> David H. Lipman wrote:
>> From: "David H. Lipman"<DLipman~nospam~@Verizon.Net>
>>
>> | From: "~BD~"<BoaterDave@hot.mail.co.uk>
>>
>> | FUD post !
>>
>> | There is NO malware that infects are resides within the; BIOS,
>> | Motherboard or Video-card
>> | EEPROM.
>>
>>
>> That should have been...
>> "...that infects or resides within..."
>>
>>
>>

> So now we are in a situation where someone (drdos) has posted
> information on a well known technical forum saying one thing .......
> and Mr David H Lipman (whoever he may *really* be!) making a post on
> Usenet groups claiming that the original poster is wrong.


If the article claims an infection in the bios or eeprom vs corruption;
then the article is indeed, wrong. BD.

> Take a step outside the box, David.


Google bios and eeproms David. You might find it somewhat enlightening.

> How could anyone simply 'visiting' these groups have any notion of who
> is actually telling the truth?


By doing their own research into the matter?

> I am /inclined/ to believe what *you* say - but there is no supporting
> evidence to that effect - is there?


See above. Google really is your friend.

> Is it reasonable for readers to accept that, as you have made no
> disparaging comment to the contrary, that "Most wiping, erasing,
> formatting, and partitioning tools will not overwrite logical bad
> sectors on the Disk, leaving the Rootkits and their accompanying
> payload of malware behind and still active."?


behind, possibly; active.. no.

> If so, what action would one recommend one takes before reinstalling
> an operating system on a previously used disk - Darik's Boot and Nuke?
> http://download.cnet.com/Darik-s-Boo...-DVD/3000-2094
> _4-10151762.html


If it does sector overwrites (and I believe it can be configured to do
so) yes.

> Or, maybe FDISK will do? http://support.microsoft.com/kb/255867


FDISK is a partitioning tool. it doesn't address sectors marked as bad.

> Or does one simply assume that one's disk is Rootkit free and simply
> use a Windows set-up disk and the in-built formatting facility?


If the system disc is clean and initializes the bootsector with clean
code, bye bye rootkit. Assuming it was an MBR based one.


--
"Hrrngh! Someday I'm going to hurl this...er...roll this...hrrngh.. nudge
this boulder right down a cliff." - Goblin Warrior