A
Anonymous Bob
Robin Walker said:
Thank you. You were one step ahead of me. <g>
Is it a bullet-proof sandbox? Can I allow a virtual pc to be
infected with no fear?
Bob Vanderveen
Thank you. You were one step ahead of me. <g>
Is it a bullet-proof sandbox? Can I allow a virtual pc to be
infected with no fear?
Bob Vanderveen
A
Anonymous Bob
plun said:
Yep...the price is going up. said:You mentioned Linux before and it is really easy to run Linux
with WMWare.
good
And also Longhorn copies found in the wild..
I'm not going there. BTW, it's known as Vista now.
http://www.businessweek.com/ap/financialnews/D8BGJ6OG0.htm?campaign_id=apn_tech_down&chan=tc
I'm in no hurry to upgrade to a new windows os...maybe when XPP
enters extended support and Windows Vista SP4 with IE 7 SP2 is
available. <g>
Bob Vanderveen
P
plun
After serious thinking Anonymous Bob wrote :
Yup
http://www.microsoft.com/windowsvista/default.mspx
First Beta Aug 3 ..........
We no chance to betatest it is only to look
in the wild........
Yup
http://www.microsoft.com/windowsvista/default.mspx
First Beta Aug 3 ..........
We no chance to betatest it is only to look
in the wild........
A
Anonymous Bob
http://www.microsoft.com/windowsvista/default.mspx
First Beta Aug 3 ..........
We no chance to betatest it is only to look
in the wild........
Be sure to wipe your feet before going back into the house.<g>
Bob Vanderveen
P
plun
Anonymous Bob formulated on fredag :
Well, I have no scruples with testing Betas.
And my shoes is on .............
Why don´t you test Virtualpc from MS instead of WMware ?
http://www.microsoft.com/windows/virtualpc/default.mspx
Also a 45 days trial !
Well, I have no scruples with testing Betas.
And my shoes is on .............
Why don´t you test Virtualpc from MS instead of WMware ?
http://www.microsoft.com/windows/virtualpc/default.mspx
Also a 45 days trial !
R
Robin Walker [MVP]
Anonymous Bob said:
Well, it depends what you mean. A Virtual PC is just like a real PC. If a
Virtual PC is infected with a worm, that worm will attempt to propagate over
the network. Any real PC on the same network will be at risk.
But if you mean whether malware can spread from the Virtual PC's filing
system to the host's, then the answer is no.
A
Alan
I'm an electrical engineer, just so you know.
When I downloaded the "current" updated version of MSAS,
it was supposed to be 615, it WAS NOT. I actaully
downloaded 614, even though the page said it was released
on 7/18/2005, the date that 615 was released. I had to
download the installer again on the 19th to get the
correct installer. This has happened to MANY people,
until the installer on the server was updated to the
correct 615 build installer, because the page was updated
with the new data but the installer was not.
As for the web-based e-mail part of AOL that I was
talking about, it WAS NOT AOL. Instead, I was talking
about webmail.aol.com, an Internet e-mail site that AOL
designed for people to check their e-mail without having
to launch AOL. Since I use broadband, I used to check my
e-mail that way, instead of launching AOL just to
check/write e-mails.
If you search your system for gcThreatAuditScanData and
gcThreatAuditThreatData (the two files that make up the
definitions), you will find that they are infact stored
in your web browser's temp files. Remember, in order to
download anything from the Internet, you must use a web
browser to connect to the IP address that you need to
download those files. MSAS, then MUST use launch an
internal browser to download these files. This is
because you CAN NOT directly connect to the site that the
files are stored at, unless you surf to that page. The
web browser that it uses is IE. Shocking isn't it that a
MS product uses another MS product to update? The same
holds true for Apple, as they use Safari to update their
software.
Alan
When I downloaded the "current" updated version of MSAS,
it was supposed to be 615, it WAS NOT. I actaully
downloaded 614, even though the page said it was released
on 7/18/2005, the date that 615 was released. I had to
download the installer again on the 19th to get the
correct installer. This has happened to MANY people,
until the installer on the server was updated to the
correct 615 build installer, because the page was updated
with the new data but the installer was not.
As for the web-based e-mail part of AOL that I was
talking about, it WAS NOT AOL. Instead, I was talking
about webmail.aol.com, an Internet e-mail site that AOL
designed for people to check their e-mail without having
to launch AOL. Since I use broadband, I used to check my
e-mail that way, instead of launching AOL just to
check/write e-mails.
If you search your system for gcThreatAuditScanData and
gcThreatAuditThreatData (the two files that make up the
definitions), you will find that they are infact stored
in your web browser's temp files. Remember, in order to
download anything from the Internet, you must use a web
browser to connect to the IP address that you need to
download those files. MSAS, then MUST use launch an
internal browser to download these files. This is
because you CAN NOT directly connect to the site that the
files are stored at, unless you surf to that page. The
web browser that it uses is IE. Shocking isn't it that a
MS product uses another MS product to update? The same
holds true for Apple, as they use Safari to update their
software.
Alan
K
Kerry
-----Original Message-----
I didn't use a link to download 615. The AutoUpdater
grabbed it on 7/20/2005, and I know how to click the
little "Help - About" menu option to see the installed
version info.
Yes, and if you will search this thread, you will find
that this issue had nothing to do with a local web cache.
Remember, I'm a computer engineer and I've been doing
this for over 25 years. You do NOT need to use a web
browser to connect to anything on the Internet. FTP uses
diferent ports and doesn't need a browser. Even HTTP
doesn't require a browser (I can write a program that
issues HTTP GETs and PUTs on port 80 without touching a
browser at all).
But in the case of MSAS, it does use embedded IE
technology (it doesn't have to, but that was the choice
they made).
There are many ways to connect to servers on the Internet
without browsers (depending on the open ports on the
target server). Programs that perform auto updates over
the Internet can either utilize existing TCP/UDP
communication libraries (such as the dll's that IE
provides) or they can create their own TCP (or even UDP)
communication layers to do so (and pick their own obscure
ports to use, if desired).
I didn't use a link to download 615. The AutoUpdater
grabbed it on 7/20/2005, and I know how to click the
little "Help - About" menu option to see the installed
version info.
Yes, and if you will search this thread, you will find
that this issue had nothing to do with a local web cache.
Remember, I'm a computer engineer and I've been doing
this for over 25 years. You do NOT need to use a web
browser to connect to anything on the Internet. FTP uses
diferent ports and doesn't need a browser. Even HTTP
doesn't require a browser (I can write a program that
issues HTTP GETs and PUTs on port 80 without touching a
browser at all).
But in the case of MSAS, it does use embedded IE
technology (it doesn't have to, but that was the choice
they made).
There are many ways to connect to servers on the Internet
without browsers (depending on the open ports on the
target server). Programs that perform auto updates over
the Internet can either utilize existing TCP/UDP
communication libraries (such as the dll's that IE
provides) or they can create their own TCP (or even UDP)
communication layers to do so (and pick their own obscure
ports to use, if desired).
A
Alan
I think they might still be using the code for the update
feature that Giant Company coded when the software was
known as Giant AntiSpyware. The reason for this is that
the program went to beta 21 days after being acquired
from Giant Company, and they really only changed the
referneces from Giant and Giant Company to Microsoft and
Microsoft Windows, as in Help > About Microsoft Windows
AntiSpyware...
The other noticable change was to the defaults for the
Browser Hijack Settings Restore feature.
I had downloaded the trial version of Giant AntiSpyware
just a few days before Microsoft bought out Giant
Company. I didn't use the updater at that time, as the
definitions were the latest version when I downloaded it,
so I'm not certain if any real changes were made there.
Since the source code was written in VB, it's possible
that it will be converted to another more robust
programming language, such as C/C++ or even C# at a later
date. If they do make the conversion, I hope they
convert it to .NET, as it can utilize .NET's modular
programming style, and its just-in-time compilation when
calling parts of the code that are not usually needed,
leading to a smaller final executable file. This will
also allow the application to be run as a service, which
could lead to the updater being replaced by Windows
Update, a HUGE improvement.
Alan
feature that Giant Company coded when the software was
known as Giant AntiSpyware. The reason for this is that
the program went to beta 21 days after being acquired
from Giant Company, and they really only changed the
referneces from Giant and Giant Company to Microsoft and
Microsoft Windows, as in Help > About Microsoft Windows
AntiSpyware...
The other noticable change was to the defaults for the
Browser Hijack Settings Restore feature.
I had downloaded the trial version of Giant AntiSpyware
just a few days before Microsoft bought out Giant
Company. I didn't use the updater at that time, as the
definitions were the latest version when I downloaded it,
so I'm not certain if any real changes were made there.
Since the source code was written in VB, it's possible
that it will be converted to another more robust
programming language, such as C/C++ or even C# at a later
date. If they do make the conversion, I hope they
convert it to .NET, as it can utilize .NET's modular
programming style, and its just-in-time compilation when
calling parts of the code that are not usually needed,
leading to a smaller final executable file. This will
also allow the application to be run as a service, which
could lead to the updater being replaced by Windows
Update, a HUGE improvement.
Alan
K
Kerry
Since the source code was written in VB, it's possible
It will have to be converted soon. Hopefully before
commercial release. Support for VB6 sunsets in 2007 (or
is it 2006?). But a conversion of that nature would
really result in a different app (even if the look and
feel were identical) so then you have to start the Beta
cycle all over again (which means they probably won't
convert it before it is released as "final" - too bad).
Beyond the expiration of support issue, VB6 is not suited
for creating multi-threaded apps, nor apps that run as a
service (both of which would be preferred features for
something like spyware scanning, just like antivirus
scanning). Changing to .NET (whether C# or VB) or
changing to C++ would solve that, as well as provide an
easier means for getting around the problem of having to
run MSAS while logged in as an Administrator (if it were
a Service instead of a VB6 app, it could run with System
credentials regardless of the current user type).
It will have to be converted soon. Hopefully before
commercial release. Support for VB6 sunsets in 2007 (or
is it 2006?). But a conversion of that nature would
really result in a different app (even if the look and
feel were identical) so then you have to start the Beta
cycle all over again (which means they probably won't
convert it before it is released as "final" - too bad).
Beyond the expiration of support issue, VB6 is not suited
for creating multi-threaded apps, nor apps that run as a
service (both of which would be preferred features for
something like spyware scanning, just like antivirus
scanning). Changing to .NET (whether C# or VB) or
changing to C++ would solve that, as well as provide an
easier means for getting around the problem of having to
run MSAS while logged in as an Administrator (if it were
a Service instead of a VB6 app, it could run with System
credentials regardless of the current user type).
A
Alan
I think that the expiration of VB support is sometime in
2007.
The reason that MS pushed the expiration of MSAS back to
the end of the year might be to give them the time to
convert the source code from VB to .NET or C++, and to
address the entire mulitple-user account and limited-user
account scanning issue.
Let's hope that's what they are doing right now.
The reason the application doesn't currently support
multiple-user account and limited-user account scanning
is to give them time to code and test, and code some more
so that the system files and file permissions are kept
intact. The last thing we need is for them to push a
major revission out the door before it's been properly
tested, leading to MANY, MANY unhappy users, who have to
reinstall Windows, and possible lose everything in the
process.
Alan
2007.
The reason that MS pushed the expiration of MSAS back to
the end of the year might be to give them the time to
convert the source code from VB to .NET or C++, and to
address the entire mulitple-user account and limited-user
account scanning issue.
Let's hope that's what they are doing right now.
The reason the application doesn't currently support
multiple-user account and limited-user account scanning
is to give them time to code and test, and code some more
so that the system files and file permissions are kept
intact. The last thing we need is for them to push a
major revission out the door before it's been properly
tested, leading to MANY, MANY unhappy users, who have to
reinstall Windows, and possible lose everything in the
process.
Alan