Quake3World

What is a Stealthboot Virus? I found an old, OLD computer with Windows95 OS and it runs pretty good, but when it boots up, it says "Stealthboot Virus detected" just before it goes to Windows. It still boots up. I plan on using this as a repair platform for other comps...after I upgrade it to xp...but that doesn't seem like a good idea if there's a virus on it. I'm looking to get rid of the virus, but I don't know about this sorta thing. You guys know that I'm not that smart, so if you could tell me in noob words, that would be helpful. Thanks.

This is what you have. Don't have time to read through it, just thought I would post it now and check back later tonight...

You could have one of the other variants, and I don't know how different they are from each other... but read some of that and see if you can give some more insight on what's going on.

That link was perfect. Thank you. All's I hafta do, is locate a "McAfee emergency disk".

Also, it mentioned that the only way to get this virus, is to use an infected floppy. I think I understood that correctly. Do you think it would infect a secondary harddrive - connected to the infected primary drive - if I am loading an OS onto the secondary drive from the cd drive?

you should be able to use whatever virus software you want. it's not like mcafee is the only way to get rid of it. i'd get something free (avg, avast, etc), update it, then boot into safe mode and see if you can nuke it that way.

or, if you're going to reformat, then fuck it, who cares - but if you're gonna "upgrade" in a strict sense, then yeah, you need to nuke that bitch.

well, here is a better link on what a virus of this type can actually do...

Also, if the machine is running 95, have you considered the cost of upgrading to Xp over just buying a lower end machine with Xp already on it?

Juggs, or whoever... if the primary drive has this code running off the MBR and you attach a slave to that one, would there be any damages to the slave... it couldn't merge over and infect the other could it?

better yet, put linux on that old pos and not worry about that kind of stuff anymore.

I bet you someone replaced the bootscreen with the one that appears. the file name should be logo.sys in windows directory. i used to love changing the bootscreens. what fun

Blurredman wrote:I bet you someone replaced the bootscreen with the one that appears. the file name should be logo.sys in windows directory. i used to love changing the bootscreens. what fun

That's interesting. Cause when I set the virus killers on it, it showed the thing cured. But, on the next boot up, I got the same message on the boot screen.

you never know.

Peenyuh wrote:

Blurredman wrote:I bet you someone replaced the bootscreen with the one that appears. the file name should be logo.sys in windows directory. i used to love changing the bootscreens. what fun

That's interesting. Cause when I set the virus killers on it, it showed the thing cured. But, on the next boot up, I got the same message on the boot screen.

but did you do it in safe mode? you may need to kill that process before you nuke it also.

+JuggerNaut+ wrote:but did you do it in safe mode? you may need to kill that process before you nuke it also.

I'll try that. Shoulda thought of that myself...thank you.

yw man