Ok, good suggestion... I second the proposal.
However, do you read those EULA's ... ?
If you installed it, you were obligated to agree that you did. And so, you
recognize that things like that may not be available. Sorry to say that, but
if you have problems, sometimes there isn't always an answer. They are still
in the process of coming out with a release. Some systems have problems that
cannot be diagnosed on every single system since configs are different on
some systems. Overall, there shouldn't have been big problems that effects
everyone's like the fake MSDN virus or the unability to install. Was that
fake virus during scan put there intentionally? What was the deal with that?
This program doesn't have much user interaction as others. It's mostly a 1
button-push event to start/stop full-scans. And the other event is a constant
behind the scenes monitoring. A third, the event for daily updates...doesn't
count really. If you know about flow charts, why don't you make up one as a
proposal to set as an example...something to spur them on...
Programming on the other hand is not ALL about money. It does take time.
Months? Half a year? Who knows how long this program has been in the works of
programming and review. Look at windows though... just so many programs out
there, and it is still not completed. And in all actuality, it may never be
complete. As new programs, or viruses are created, new updates need to be
made to facilitate to the needs of the change. A simple name change requires
an update. A change in a function call could use different resources of the
windows environment, requires an update. The whole engine of beta 2 needed to
be replaced to solve the automatic update problem. Until then, we needed to
run a command ourself to remove the old update.
I'll give 'em another month. By then, they should have an update and a short
manual. But really, what do you need to see? Tell them what you want
exactly... do you want to know the meaning of each update? Sometimes with
virus scanners, they don't tell you everything in too grate of detail. If
they do, it's just the name of the virus and what names it goes by and
possibly the calls or locations they infect. You can see that on most
websites that are virus scanners such as McAfee... their updates most likely
are just to update what the programs that can be recognized. Some on my list
still can't be recognized, especially the newer Microsoft programs that are
just coming out, a corporate internal mismatch, definitely. All MS should be
represented. Then again, with the firewalls in your computer and user defined
restrictions, creating a function that can do this for all conditions can be
difficult. Take a discrete math course. A simple case statemeint if-else
program update is not something to use for updates, or else you'll have a
list of 10 million programs of hash code checking individual program. There
is part to these things to allow updates to fix the problem or update what is
necessary, but they also want to do it in a systematic fashion and not use up
all your resources, memory and harddrive space, for things that do not
pertain to your system. Everyone's computer is unique. Making one file that
fits every computer is more difficult. This is why the updates come in
stages. And sometimes a tiny error can cause chaos. The power of programming
is unbelievable until you take classes on it and learn what it's all about.
What do you exactly want to see in these flowcharts? How the program does
it's search. Some of it you can see by what they display during a full
search. I think I see it go file and register together, if I'm thinking of
the correct program. It scans a program, confirms it in local machine
register, and checks it's own database for matches for possible bugs/viruses.
It's fast, but not very fast... it seems to go into zip files too I believe,
some compressed files... I also used Windows One care, and I think it does
that, so I hope not to confuse the 2. This is not ms word...only observation
during my execution of the programs. Could it be different, of course. Do I
care much more now, probably not... unless I had code in front of me...
And by the way, we are not customers of this product. It was a beta release,
not a sale. Again, read the License, I'm sure it clearly states we get only
what is given to us. And it also states that there might not be help
available at all times if they don't have the answer. But as they collect the
data they need to make improvements as many have already successfully done,
it WILL be available. Rome wasn't built in a day...don't we all know that
phrase. How can a complex program fulfill everyone's desire witn no flaws.
Many things reside to be discovered...some basic plans are surely not
definite. A simple drawing you wish could change in the next engine if the
search is taking longer than expected or is not doing something that can be
done in another way... Again, as I say, if you haven't already, take some
classes in Information Systems. It goes so deep, you'll understand why it
wasn't released.
Question/Tip of the day:
Did you ever program a debugger of infinite code? A math problem for you to
solve. Take the sum of days, assume today is day 0, and add 1 to each day it
would take to make a program that could find any type of bug on a computer.
Assume if it took 1 month to make code for a basic engine for the viruses
defined on day 0, how long would it take to fulfill a successful program that
is up to date? Keep in mind, as you program, you are originally working on
one program. Over the month, viruses develop spiratically at a rate of n^2
every other day (made up function). When a virus changes form, a new function
in code for the program needs to be made... meaning a later release of the
program.
Now I have no idea how many viruses are out there by a long shot. But this
is being done every day. Take this into consideration... That's my best
guess. Then there's business to attend to in other forms beyond
programming...let that go...
-Jmonkey
