The moment that happens, you are infected. I deal with that...it's
for prevention as best as can be.
Not necessarily. Loss of an internet connection doesn't automatically
mean infected. Technically, unless you're dealing with a virus you
aren't infected anyway. Trojans (fake antimalware scanners that beg for
a credit card) are not infectious on their own. They don't replicate.
As far as best as can be, that's simply a personal opinion. Based on the
knowledge you don't! display here, it's a bad opinion that probably
shouldn't be followed.
kinda answered in the other thread.
I must have missed it. So why not either retype or do a copy/paste?
24 seconds from the time I hit enter at login till my wireless comes
online...that is the last TSR to load . I'm not counting the time to
login.
TSR? Windows 7 doesn't have tsrs. You probably mean windows/or wireless
manu app indicator loads. As the drivers are already loaded and online
prior to your login prompt, just so you know. You accuse me of not
sharing information and hoarding it all to myself, so I thought I'd
share a little with you now.
You shouldn't call it a 24 second boot time then, as it's misleading.
Either that or you don't know what boottime means. The information
you've provided doesn't allow me to get even the foggiest idea of what
your boottime maybe. Only that you don't know how to measure it. hehe.
Safe hex is discussed in my comprehensive security plan posted on my
website ...has been for years. My post here have been excerpts of a
complete security plan...for the purpose of discussing that phase. I
don't think I've mentioned wifi security, identity theft, anti-
keylogging, banking, software & system updates, routine malware
scans, rescue CD's, password and form management, proxies, or some of
the other of many security concerns which should be addressed in a
comprehensive discussion about security. That takes more time than I
wish to spend when I post about a specific topic I wish to discuss.
Understood. I've frequented your site as I'm sure you know. The majority
of the information offered isn't actually written by you tho. Surely you
don't take full credit for the material on that site?
use my clean image until a MS Update or I decide to make a permanent
change, then I reload that image, make the change and reimage. Then I
use that image until the next change. Such works very well for me.
Understood. It places you in a good way in the event hardware failure
occurs or something seriously borks the software. It's not a good way to
deal with malware tho. As in some cases, it's overkill.
LOL...none the more so of all the other things I do.
Ok. I just don't really understand the point of filling a landfill
someplace sooner than one needs to. I run my hardware well into the
ground before it's scrap. And even then, I'm known to keep it for extra
caps, diodes, etc.
Well, I use the term infected as a general description to malware
that inserted into my machine. It's what most people do or say. We
could make up another term to use if that would please you, but I
would likely not use it.
I see no need to make up terms. It would make more sense to use the ones
which are already well defined and exist. What most people do or say
doesn't mean it's done correctly nor accurate.
As you feel in some way superior to my lowly blue collar self, You of
all educated people! (bow bow) should understand the importance in the
differential as explained.
I'm collecting general information for my own purposes...not
scientific data for a foundation. What I do is generally a good
indication of how it compares to another AV or program...and as I
said, good enough for my purposes...much better than just trusting
what someone else says they do or did, as I've found many of even the
experts tests and conclusions faulty.
I understand your collecting information and making BearWear
recommendations based on the results of the information. So, it's not
just for your private use; People may make bad/good decisions based on
it. It's irresponsible to make information public and recommendations
based on it if the information itself is bad.
So, I will ask again, what testing methodology do you practice?
As it reads, you likely are doing what I jokingly referred to. I can
help, if that's the case. You just need to be on the level here.
