Ccleaner - Virtual Machine

I agree with you completely, Gary. The user should get rid of the junk and
any associated registry keys along with it.

"Gary S. Terhune" wrote in message

: While I strongly advise you to cease using CrapCleaner (for the same
: reasons I strongly advise against using any such tool), they have a
: forum--http://forum.ccleaner.com/
:
: Since they don't offer one iota of support, that's the best you can do,
: assuming you still want to keep this crapware--and crapware it is if it
: can't even handle errors properly.
:
: --
: Gary S. Terhune
: MS MVP Shell/User
:
: "Solkeys" wrote in message
:
: > I am running the Ccleaner program but it closes the following is the
: error
: > message.
: > Visual Basic Virtual Machine detected an error condition which was not
: > handled by the application.
: >
: > Module Name: MSVBVM60.DLL
: > Description: Visual Basic Virtual Machine
: > Version: 6.00.9782
: > Product: Visual Basic
: > Manufacturer: Microsoft Corporation
: >
: > Application Name: Ccleaner.exe
: > Version: 1.17.0090
: > Product: CCleaner
: > Manufacturer: CCleaner.com
: >
: > --------------------
: >
: >
: >
: >
:
 >> Stay informed about: Ccleaner - Virtual Machine 

OK I will listen to you guys but my question is what does this error mean?
Solomon
"Dan" wrote in message

 > I agree with you completely, Gary. The user should get rid of the junk
and
 > any associated registry keys along with it.
 >


 > : While I strongly advise you to cease using CrapCleaner (for the same
 > : reasons I strongly advise against using any such tool), they have a
 > : forum--http://forum.ccleaner.com/
 > :
 > : Since they don't offer one iota of support, that's the best you can do,
 > : assuming you still want to keep this crapware--and crapware it is if it
 > : can't even handle errors properly.
 > :
 > : --
 > : Gary S. Terhune
 > : MS MVP Shell/User
 > :


 > : > I am running the Ccleaner program but it closes the following is the
 > : error
 > : > message.
 > : > Visual Basic Virtual Machine detected an error condition which was not
 > : > handled by the application.
 > : >
 > : > Module Name: MSVBVM60.DLL
 > : > Description: Visual Basic Virtual Machine
 > : > Version: 6.00.9782
 > : > Product: Visual Basic
 > : > Manufacturer: Microsoft Corporation
 > : >
 > : > Application Name: Ccleaner.exe
 > : > Version: 1.17.0090
 > : > Product: CCleaner
 > : > Manufacturer: CCleaner.com
 > : >
 > : > --------------------
 > : >
 > : >
 > : >
 > : >
 > :
 >
 >
 >> Stay informed about: Ccleaner - Virtual Machine 

It means just what it says--an error was encountered which was not
handled by the application. Any application is going to throw an error
when it encounters a command or data that "does not compute". Happens
all the time. The trick in coding is to anticipate whenever such an
error could possibly occur and include code to handle it.

For example, I could write a script that would automatically delete all
files in TEMP at startup, telling it to "DELETE C:\Windows\TEMP\*.*"

That would work on 99% of the machines out there, because that really is
where the TEMP environment is located. But what if I have changed my
TEMP environment to D:\TEMP, and because I'm seriously anal, I've also
included a DELTREE C:\Windows\TEMP command at the proper moment in
startup to get rid of the empty TEMP folder that gets automatically
created in the Windows folder, regardless of where the TEMP environment
is. When the program attempts to complete the "DELETE
C:\Windows\TEMP\*.*" command, it can't--there *isn't* any
C:\Windows\TEMP. Error time. And if there isn't any code to handle the
error, you get the report you got (in that particular case, anyway.)

To handle my hypothetical error, I might include code at the beginning
of the script like this:
ON ERROR RESUME NEXT

That tells the program to continue, even if there's an error. To handle
the hypothetical problem above, I would put in code after that Delete
command that says:

IF ERR THEN
ERR CLEAR
(find out where the blasted TEMP files are stored.)
(repeat delete command)
END IF

(No, that isn't very good or accurate coding, above. It's a simplified
example. To do that task I'd first determine where the TEMP files are
supposed to be located and then make sure the path actually existed,
before I even gave the Delete command.)

--
Gary S. Terhune
MS MVP Shell/User

"Solkeys" wrote in message

 > OK I will listen to you guys but my question is what does this error
mean?
 > Solomon


  > > I agree with you completely, Gary. The user should get rid of the
junk
 > and
  > > any associated registry keys along with it.
  > >


  > > : While I strongly advise you to cease using CrapCleaner (for the
same
  > > : reasons I strongly advise against using any such tool), they have
a
  > > : forum--http://forum.ccleaner.com/
  > > :
  > > : Since they don't offer one iota of support, that's the best you
can do,
  > > : assuming you still want to keep this crapware--and crapware it is
if it
  > > : can't even handle errors properly.
  > > :
  > > : --
  > > : Gary S. Terhune
  > > : MS MVP Shell/User
  > > :


  > > : > I am running the Ccleaner program but it closes the following is
the
  > > : error
  > > : > message.
  > > : > Visual Basic Virtual Machine detected an error condition which
was not
  > > : > handled by the application.
  > > : >
  > > : > Module Name: MSVBVM60.DLL
  > > : > Description: Visual Basic Virtual Machine
  > > : > Version: 6.00.9782
  > > : > Product: Visual Basic
  > > : > Manufacturer: Microsoft Corporation
  > > : >
  > > : > Application Name: Ccleaner.exe
  > > : > Version: 1.17.0090
  > > : > Product: CCleaner
  > > : > Manufacturer: CCleaner.com
  > > : >
  > > : > --------------------
  > > : >
  > > : >
  > > : >
  > > : >
  > > :
  > >
  > >
 >
 >
 >> Stay informed about: Ccleaner - Virtual Machine 

"The trick in coding is to anticipate whenever such an error could possibly
occur and include code to handle it." Great, Gary and I couldn't have said
this any better myself. Thanks for including a simplified coding example for
everyone to view. It was interesting to me and gives me even more ideas.
<eg>

"Gary S. Terhune" wrote in message

: It means just what it says--an error was encountered which was not
: handled by the application. Any application is going to throw an error
: when it encounters a command or data that "does not compute". Happens
: all the time. The trick in coding is to anticipate whenever such an
: error could possibly occur and include code to handle it.
:
: For example, I could write a script that would automatically delete all
: files in TEMP at startup, telling it to "DELETE C:\Windows\TEMP\*.*"
:
: That would work on 99% of the machines out there, because that really is
: where the TEMP environment is located. But what if I have changed my
: TEMP environment to D:\TEMP, and because I'm seriously anal, I've also
: included a DELTREE C:\Windows\TEMP command at the proper moment in
: startup to get rid of the empty TEMP folder that gets automatically
: created in the Windows folder, regardless of where the TEMP environment
: is. When the program attempts to complete the "DELETE
: C:\Windows\TEMP\*.*" command, it can't--there *isn't* any
: C:\Windows\TEMP. Error time. And if there isn't any code to handle the
: error, you get the report you got (in that particular case, anyway.)
:
: To handle my hypothetical error, I might include code at the beginning
: of the script like this:
: ON ERROR RESUME NEXT
:
: That tells the program to continue, even if there's an error. To handle
: the hypothetical problem above, I would put in code after that Delete
: command that says:
:
: IF ERR THEN
: ERR CLEAR
: (find out where the blasted TEMP files are stored.)
: (repeat delete command)
: END IF
:
: (No, that isn't very good or accurate coding, above. It's a simplified
: example. To do that task I'd first determine where the TEMP files are
: supposed to be located and then make sure the path actually existed,
: before I even gave the Delete command.)
:
: --
: Gary S. Terhune
: MS MVP Shell/User
:
: "Solkeys" wrote in message
:
: > OK I will listen to you guys but my question is what does this error
: mean?
: > Solomon
: > "Dan" wrote in message
: >
: > > I agree with you completely, Gary. The user should get rid of the
: junk
: > and
: > > any associated registry keys along with it.
: > >
: > > "Gary S. Terhune" wrote in message
: > >
: > > : While I strongly advise you to cease using CrapCleaner (for the
: same
: > > : reasons I strongly advise against using any such tool), they have
: a
: > > : forum--http://forum.ccleaner.com/
: > > :
: > > : Since they don't offer one iota of support, that's the best you
: can do,
: > > : assuming you still want to keep this crapware--and crapware it is
: if it
: > > : can't even handle errors properly.
: > > :
: > > : --
: > > : Gary S. Terhune
: > > : MS MVP Shell/User
: > > :
: > > : "Solkeys" wrote in message
: > > :
: > > : > I am running the Ccleaner program but it closes the following is
: the
: > > : error
: > > : > message.
: > > : > Visual Basic Virtual Machine detected an error condition which
: was not
: > > : > handled by the application.
: > > : >
: > > : > Module Name: MSVBVM60.DLL
: > > : > Description: Visual Basic Virtual Machine
: > > : > Version: 6.00.9782
: > > : > Product: Visual Basic
: > > : > Manufacturer: Microsoft Corporation
: > > : >
: > > : > Application Name: Ccleaner.exe
: > > : > Version: 1.17.0090
: > > : > Product: CCleaner
: > > : > Manufacturer: CCleaner.com
: > > : >
: > > : > --------------------
: > > : >
: > > : >
: > > : >
: > > : >
: > > :
: > >
: > >
: >
: >
:
 >> Stay informed about: Ccleaner - Virtual Machine 

Thank you very much for your great explanation. Maybe you can recommend an
other good and simple registry cleaner? The Ccleaner was recommended by the
Popular Mechanic magazine.
Solomon

"Gary S. Terhune" wrote in message

 > It means just what it says--an error was encountered which was not
 > handled by the application. Any application is going to throw an error
 > when it encounters a command or data that "does not compute". Happens
 > all the time. The trick in coding is to anticipate whenever such an
 > error could possibly occur and include code to handle it.
 >
 > For example, I could write a script that would automatically delete all
 > files in TEMP at startup, telling it to "DELETE C:\Windows\TEMP\*.*"
 >
 > That would work on 99% of the machines out there, because that really is
 > where the TEMP environment is located. But what if I have changed my
 > TEMP environment to D:\TEMP, and because I'm seriously anal, I've also
 > included a DELTREE C:\Windows\TEMP command at the proper moment in
 > startup to get rid of the empty TEMP folder that gets automatically
 > created in the Windows folder, regardless of where the TEMP environment
 > is. When the program attempts to complete the "DELETE
 > C:\Windows\TEMP\*.*" command, it can't--there *isn't* any
 > C:\Windows\TEMP. Error time. And if there isn't any code to handle the
 > error, you get the report you got (in that particular case, anyway.)
 >
 > To handle my hypothetical error, I might include code at the beginning
 > of the script like this:
 > ON ERROR RESUME NEXT
 >
 > That tells the program to continue, even if there's an error. To handle
 > the hypothetical problem above, I would put in code after that Delete
 > command that says:
 >
 > IF ERR THEN
 > ERR CLEAR
 > (find out where the blasted TEMP files are stored.)
 > (repeat delete command)
 > END IF
 >
 > (No, that isn't very good or accurate coding, above. It's a simplified
 > example. To do that task I'd first determine where the TEMP files are
 > supposed to be located and then make sure the path actually existed,
 > before I even gave the Delete command.)
 >
 > --
 > Gary S. Terhune
 > MS MVP Shell/User
 >


  > > OK I will listen to you guys but my question is what does this error
 > mean?
  > > Solomon


   > > > I agree with you completely, Gary. The user should get rid of the
 > junk
  > > and
   > > > any associated registry keys along with it.
   > > >


   > > > : While I strongly advise you to cease using CrapCleaner (for the
 > same
   > > > : reasons I strongly advise against using any such tool), they have
 > a
   > > > : forum--http://forum.ccleaner.com/
   > > > :
   > > > : Since they don't offer one iota of support, that's the best you
 > can do,
   > > > : assuming you still want to keep this crapware--and crapware it is
 > if it
   > > > : can't even handle errors properly.
   > > > :
   > > > : --
   > > > : Gary S. Terhune
   > > > : MS MVP Shell/User
   > > > :


   > > > : > I am running the Ccleaner program but it closes the following is
 > the
   > > > : error
   > > > : > message.
   > > > : > Visual Basic Virtual Machine detected an error condition which
 > was not
   > > > : > handled by the application.
   > > > : >
   > > > : > Module Name: MSVBVM60.DLL
   > > > : > Description: Visual Basic Virtual Machine
   > > > : > Version: 6.00.9782
   > > > : > Product: Visual Basic
   > > > : > Manufacturer: Microsoft Corporation
   > > > : >
   > > > : > Application Name: Ccleaner.exe
   > > > : > Version: 1.17.0090
   > > > : > Product: CCleaner
   > > > : > Manufacturer: CCleaner.com
   > > > : >
   > > > : > --------------------
   > > > : >
   > > > : >
   > > > : >
   > > > : >
   > > > :
   > > >
   > > >
  > >
  > >
 >
 >> Stay informed about: Ccleaner - Virtual Machine 

What AB said. There is no such thing as a "simple, automatic" Registry
cleaner that is any good. The only tool that is reasonable capable of
cleaning the Registry decently is the person in front of it--providing
that person knows what s/he is doing. Yes, said person might employ any
of a number of tools to help ferret out anomalies, but letting any such
tool decide what to do is folly. If *you* don't know enough to
accurately second-guess the app, then you shouldn't be running it.
You're better off with a cluttered Registry than with a screwed up
Registry.

No, I don't have any recommendations these days. However, while
acknowledging that the wetware component is paramount in such endeavors,
I have used, and continue to use, *old* Norton WinDoctor (2000),
EasyCleaner, and RegCleaner (by Jouni Vuoro.) Plus, on occasion, a
couple of others that I won't even mention for fear you'd try them, <s>.

--
Gary S. Terhune
MS MVP Shell/User
<a rel="nofollow" style='text-decoration: none;' href="http://www.grystmill.com/articles/cleanboot.htm" target="_blank">http://www.grystmill.com/articles/cleanboot.htm</a>
<a rel="nofollow" style='text-decoration: none;' href="http://www.grystmill.com/articles/security.htm" target="_blank">http://www.grystmill.com/articles/security.htm</a>

"Solkeys" wrote in message

 > Thank you very much for your great explanation. Maybe you can
recommend an
 > other good and simple registry cleaner? The Ccleaner was recommended
by the
 > Popular Mechanic magazine.
 > Solomon
 >


  > > It means just what it says--an error was encountered which was not
  > > handled by the application. Any application is going to throw an
error
  > > when it encounters a command or data that "does not compute".
Happens
  > > all the time. The trick in coding is to anticipate whenever such an
  > > error could possibly occur and include code to handle it.
  > >
  > > For example, I could write a script that would automatically delete
all
  > > files in TEMP at startup, telling it to "DELETE C:\Windows\TEMP\*.*"
  > >
  > > That would work on 99% of the machines out there, because that
really is
  > > where the TEMP environment is located. But what if I have changed my
  > > TEMP environment to D:\TEMP, and because I'm seriously anal, I've
also
  > > included a DELTREE C:\Windows\TEMP command at the proper moment in
  > > startup to get rid of the empty TEMP folder that gets automatically
  > > created in the Windows folder, regardless of where the TEMP
environment
  > > is. When the program attempts to complete the "DELETE
  > > C:\Windows\TEMP\*.*" command, it can't--there *isn't* any
  > > C:\Windows\TEMP. Error time. And if there isn't any code to handle
the
  > > error, you get the report you got (in that particular case, anyway.)
  > >
  > > To handle my hypothetical error, I might include code at the
beginning
  > > of the script like this:
  > > ON ERROR RESUME NEXT
  > >
  > > That tells the program to continue, even if there's an error. To
handle
  > > the hypothetical problem above, I would put in code after that
Delete
  > > command that says:
  > >
  > > IF ERR THEN
  > > ERR CLEAR
  > > (find out where the blasted TEMP files are stored.)
  > > (repeat delete command)
  > > END IF
  > >
  > > (No, that isn't very good or accurate coding, above. It's a
simplified
  > > example. To do that task I'd first determine where the TEMP files
are
  > > supposed to be located and then make sure the path actually existed,
  > > before I even gave the Delete command.)
  > >
  > > --
  > > Gary S. Terhune
  > > MS MVP Shell/User
  > >


   > > > OK I will listen to you guys but my question is what does this
error
  > > mean?
   > > > Solomon


   > > > > I agree with you completely, Gary. The user should get rid of
the
  > > junk
   > > > and
   > > > > any associated registry keys along with it.
   > > > >


   > > > > : While I strongly advise you to cease using CrapCleaner (for
the
  > > same
   > > > > : reasons I strongly advise against using any such tool), they
have
  > > a
   > > > > : forum--http://forum.ccleaner.com/
   > > > > :
   > > > > : Since they don't offer one iota of support, that's the best
you
  > > can do,
   > > > > : assuming you still want to keep this crapware--and crapware it
is
  > > if it
   > > > > : can't even handle errors properly.
   > > > > :
   > > > > : --
   > > > > : Gary S. Terhune
   > > > > : MS MVP Shell/User
   > > > > :


   > > > > : > I am running the Ccleaner program but it closes the
following is
  > > the
   > > > > : error
   > > > > : > message.
   > > > > : > Visual Basic Virtual Machine detected an error condition
which
  > > was not
   > > > > : > handled by the application.
   > > > > : >
   > > > > : > Module Name: MSVBVM60.DLL
   > > > > : > Description: Visual Basic Virtual Machine
   > > > > : > Version: 6.00.9782
   > > > > : > Product: Visual Basic
   > > > > : > Manufacturer: Microsoft Corporation
   > > > > : >
   > > > > : > Application Name: Ccleaner.exe
   > > > > : > Version: 1.17.0090
   > > > > : > Product: CCleaner
   > > > > : > Manufacturer: CCleaner.com
   > > > > : >
   > > > > : > --------------------
   > > > > : >
   > > > > : >
   > > > > : >
   > > > > : >
   > > > > :
   > > > >
   > > > >
   > > >
   > > >
  > >
 >
 >
 >> Stay informed about: Ccleaner - Virtual Machine 

The registry is a dangerous thing to mess with.
There are absolutely NO good automatic registry cleaners, all it takes is
one mistake, one key incorrectly removed, one .dll determined to be no
longer required and you have a large grey box suitable for use as a boat
anchor, requiring fdisk format and reinstall, with the loss of any and all
information that isnt backed up.
Mechanic- Fixes cars
Popular Mechanic - Fixes Popular cars?
even IMacs dont look like cars,
the man in the computer shop doesnt try to tell you how to fix your car does
he, there is always another source of information
--
Adaware <a rel="nofollow" style='text-decoration: none;' href="http://www.lavasoft.de" target="_blank">http://www.lavasoft.de</a>
spybot <a rel="nofollow" style='text-decoration: none;' href="http://security.kolla.de" target="_blank">http://security.kolla.de</a>
AVG free antivirus <a rel="nofollow" style='text-decoration: none;' href="http://www.grisoft.com" target="_blank">http://www.grisoft.com</a>
Etrust/Vet/CA.online Antivirus scan
<a rel="nofollow" style='text-decoration: none;' href="http://www3.ca.com/securityadvisor/virusinfo/scan.aspx" target="_blank">http://www3.ca.com/securityadvisor/virusinfo/scan.aspx</a>
Panda online AntiVirus scan <a rel="nofollow" style='text-decoration: none;' href="http://www.pandasoftware.com/ActiveScan/" target="_blank">http://www.pandasoftware.com/ActiveScan/</a>
Catalog of removal tools (1)
<a rel="nofollow" style='text-decoration: none;' href="http://www.pandasoftware.com/download/utilities/" target="_blank">http://www.pandasoftware.com/download/utilities/</a>
Catalog of removal tools (2)
<a rel="nofollow" style='text-decoration: none;' href="http://www3.ca.com/securityadvisor/newsinfo/collateral.aspx?CID=40387" target="_blank">http://www3.ca.com/securityadvisor/newsinfo/collateral.aspx?CID=40387</a>
Blocking Unwanted Parasites with a Hosts file
<a rel="nofollow" style='text-decoration: none;' href="http://mvps.org/winhelp2002/hosts.htm" target="_blank">http://mvps.org/winhelp2002/hosts.htm</a>
links provided as a courtesy, read all instructions on the pages before use

Grateful thanks to the authors/webmasters
_


"Solkeys" wrote in message

 > Thank you very much for your great explanation. Maybe you can recommend an
 > other good and simple registry cleaner? The Ccleaner was recommended by
the
 > Popular Mechanic magazine.
 > Solomon
 >


  > > It means just what it says--an error was encountered which was not
  > > handled by the application. Any application is going to throw an error
  > > when it encounters a command or data that "does not compute". Happens
  > > all the time. The trick in coding is to anticipate whenever such an
  > > error could possibly occur and include code to handle it.
  > >
  > > For example, I could write a script that would automatically delete all
  > > files in TEMP at startup, telling it to "DELETE C:\Windows\TEMP\*.*"
  > >
  > > That would work on 99% of the machines out there, because that really is
  > > where the TEMP environment is located. But what if I have changed my
  > > TEMP environment to D:\TEMP, and because I'm seriously anal, I've also
  > > included a DELTREE C:\Windows\TEMP command at the proper moment in
  > > startup to get rid of the empty TEMP folder that gets automatically
  > > created in the Windows folder, regardless of where the TEMP environment
  > > is. When the program attempts to complete the "DELETE
  > > C:\Windows\TEMP\*.*" command, it can't--there *isn't* any
  > > C:\Windows\TEMP. Error time. And if there isn't any code to handle the
  > > error, you get the report you got (in that particular case, anyway.)
  > >
  > > To handle my hypothetical error, I might include code at the beginning
  > > of the script like this:
  > > ON ERROR RESUME NEXT
  > >
  > > That tells the program to continue, even if there's an error. To handle
  > > the hypothetical problem above, I would put in code after that Delete
  > > command that says:
  > >
  > > IF ERR THEN
  > > ERR CLEAR
  > > (find out where the blasted TEMP files are stored.)
  > > (repeat delete command)
  > > END IF
  > >
  > > (No, that isn't very good or accurate coding, above. It's a simplified
  > > example. To do that task I'd first determine where the TEMP files are
  > > supposed to be located and then make sure the path actually existed,
  > > before I even gave the Delete command.)
  > >
  > > --
  > > Gary S. Terhune
  > > MS MVP Shell/User
  > >


   > > > OK I will listen to you guys but my question is what does this error
  > > mean?
   > > > Solomon


   > > > > I agree with you completely, Gary. The user should get rid of the
  > > junk
   > > > and
   > > > > any associated registry keys along with it.
   > > > >


   > > > > : While I strongly advise you to cease using CrapCleaner (for the
  > > same
   > > > > : reasons I strongly advise against using any such tool), they have
  > > a
   > > > > : forum--http://forum.ccleaner.com/
   > > > > :
   > > > > : Since they don't offer one iota of support, that's the best you
  > > can do,
   > > > > : assuming you still want to keep this crapware--and crapware it is
  > > if it
   > > > > : can't even handle errors properly.
   > > > > :
   > > > > : --
   > > > > : Gary S. Terhune
   > > > > : MS MVP Shell/User
   > > > > :


   > > > > : > I am running the Ccleaner program but it closes the following is
  > > the
   > > > > : error
   > > > > : > message.
   > > > > : > Visual Basic Virtual Machine detected an error condition which
  > > was not
   > > > > : > handled by the application.
   > > > > : >
   > > > > : > Module Name: MSVBVM60.DLL
   > > > > : > Description: Visual Basic Virtual Machine
   > > > > : > Version: 6.00.9782
   > > > > : > Product: Visual Basic
   > > > > : > Manufacturer: Microsoft Corporation
   > > > > : >
   > > > > : > Application Name: Ccleaner.exe
   > > > > : > Version: 1.17.0090
   > > > > : > Product: CCleaner
   > > > > : > Manufacturer: CCleaner.com
   > > > > : >
   > > > > : > --------------------
   > > > > : >
   > > > > : >
   > > > > : >
   > > > > : >
   > > > > :
   > > > >
   > > > >
   > > >
   > > >
  > >
 >
 >
 >> Stay informed about: Ccleaner - Virtual Machine 

I agree with ya.

If the OP really wants to clean his registry, there is only ONE "right way"
to do it: reinstall (I mean *clean install*) windows and all programs all
over again.

AlmostBob wrote:
 > The registry is a dangerous thing to mess with.
 > There are absolutely NO good automatic registry cleaners, all it takes is
 > one mistake, one key incorrectly removed, one .dll determined to be no
 > longer required and you have a large grey box suitable for use as a boat
 > anchor, requiring fdisk format and reinstall, with the loss of any and all
 > information that isnt backed up.
 > Mechanic- Fixes cars
 > Popular Mechanic - Fixes Popular cars?
 > even IMacs dont look like cars,
 > the man in the computer shop doesnt try to tell you how to fix your car
does
 > he, there is always another source of information
 > --
<font color=purple> > Adaware <a rel="nofollow" style='text-decoration: none;' href="http://www.lavasoft.de</font" target="_blank">http://www.lavasoft.de</font</a>>
<font color=purple> > spybot <a rel="nofollow" style='text-decoration: none;' href="http://security.kolla.de</font" target="_blank">http://security.kolla.de</font</a>>
<font color=purple> > AVG free antivirus <a rel="nofollow" style='text-decoration: none;' href="http://www.grisoft.com</font" target="_blank">http://www.grisoft.com</font</a>>
 > Etrust/Vet/CA.online Antivirus scan
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://www3.ca.com/securityadvisor/virusinfo/scan.aspx</font" target="_blank">http://www3.ca.com/securityadvisor/virusinfo/scan.aspx</font</a>>
<font color=purple> > Panda online AntiVirus scan <a rel="nofollow" style='text-decoration: none;' href="http://www.pandasoftware.com/ActiveScan/</font" target="_blank">http://www.pandasoftware.com/ActiveScan/</font</a>>
 > Catalog of removal tools (1)
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://www.pandasoftware.com/download/utilities/</font" target="_blank">http://www.pandasoftware.com/download/utilities/</font</a>>
 > Catalog of removal tools (2)
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://www3.ca.com/securityadvisor/newsinfo/collateral.aspx?CID=40387</font" target="_blank">http://www3.ca.com/securityadvisor/newsinfo/collateral.aspx?CID=40387</font</a>>
 > Blocking Unwanted Parasites with a Hosts file
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://mvps.org/winhelp2002/hosts.htm</font" target="_blank">http://mvps.org/winhelp2002/hosts.htm</font</a>>
 > links provided as a courtesy, read all instructions on the pages before
use
 >
 > Grateful thanks to the authors/webmasters
 > _
 >
 >


  >> Thank you very much for your great explanation. Maybe you can recommend
an
  >> other good and simple registry cleaner? The Ccleaner was recommended by
the
  >> Popular Mechanic magazine.
  >> Solomon
  >>


   >>> It means just what it says--an error was encountered which was not
   >>> handled by the application. Any application is going to throw an error
   >>> when it encounters a command or data that "does not compute". Happens
   >>> all the time. The trick in coding is to anticipate whenever such an
   >>> error could possibly occur and include code to handle it.
   >>>
   >>> For example, I could write a script that would automatically delete all
   >>> files in TEMP at startup, telling it to "DELETE C:\Windows\TEMP\*.*"
   >>>
   >>> That would work on 99% of the machines out there, because that really is
   >>> where the TEMP environment is located. But what if I have changed my
   >>> TEMP environment to D:\TEMP, and because I'm seriously anal, I've also
   >>> included a DELTREE C:\Windows\TEMP command at the proper moment in
   >>> startup to get rid of the empty TEMP folder that gets automatically
   >>> created in the Windows folder, regardless of where the TEMP environment
   >>> is. When the program attempts to complete the "DELETE
   >>> C:\Windows\TEMP\*.*" command, it can't--there *isn't* any
   >>> C:\Windows\TEMP. Error time. And if there isn't any code to handle the
   >>> error, you get the report you got (in that particular case, anyway.)
   >>>
   >>> To handle my hypothetical error, I might include code at the beginning
   >>> of the script like this:
   >>> ON ERROR RESUME NEXT
   >>>
   >>> That tells the program to continue, even if there's an error. To handle
   >>> the hypothetical problem above, I would put in code after that Delete
   >>> command that says:
   >>>
   >>> IF ERR THEN
   >>> ERR CLEAR
   >>> (find out where the blasted TEMP files are stored.)
   >>> (repeat delete command)
   >>> END IF
   >>>
   >>> (No, that isn't very good or accurate coding, above. It's a simplified
   >>> example. To do that task I'd first determine where the TEMP files are
   >>> supposed to be located and then make sure the path actually existed,
   >>> before I even gave the Delete command.)
   >>>
   >>> --
   >>> Gary S. Terhune
   >>> MS MVP Shell/User
   >>>


   >>>> OK I will listen to you guys but my question is what does this error
mean?
   >>>> Solomon


   >>>>> I agree with you completely, Gary. The user should get rid of the
junk
   >>>>> and any associated registry keys along with it.
   >>>>>


   >>>>>> While I strongly advise you to cease using CrapCleaner (for the same
   >>>>>> reasons I strongly advise against using any such tool), they have a
   >>>>>> forum--http://forum.ccleaner.com/
   >>>>>>
   >>>>>> Since they don't offer one iota of support, that's the best you can
do,
   >>>>>> assuming you still want to keep this crapware--and crapware it is if
it
   >>>>>> can't even handle errors properly.
   >>>>>>
   >>>>>> --
   >>>>>> Gary S. Terhune
   >>>>>> MS MVP Shell/User
   >>>>>>


   >>>>>>> I am running the Ccleaner program but it closes the following is the
   >>>>>>> error message.
   >>>>>>> Visual Basic Virtual Machine detected an error condition which was
not
   >>>>>>> handled by the application.
   >>>>>>>
   >>>>>>> Module Name: MSVBVM60.DLL
   >>>>>>> Description: Visual Basic Virtual Machine
   >>>>>>> Version: 6.00.9782
   >>>>>>> Product: Visual Basic
   >>>>>>> Manufacturer: Microsoft Corporation
   >>>>>>>
   >>>>>>> Application Name: Ccleaner.exe
   >>>>>>> Version: 1.17.0090
   >>>>>>> Product: CCleaner
   >>>>>>> Manufacturer: CCleaner.com
   >>>>>>>
   >>>>>>> --------------------
 >> Stay informed about: Ccleaner - Virtual Machine