If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Ccleaner - Virtual Machine
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 -------------------- |
#2
|
|||
|
|||
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 -------------------- |
#3
|
|||
|
|||
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 : : -------------------- : : : : : |
#4
|
|||
|
|||
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 : : -------------------- : : : : : |
#5
|
|||
|
|||
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 : : -------------------- : : : : : |
#6
|
|||
|
|||
"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 : : : : -------------------- : : : : : : : : : : : : : : : |
#7
|
|||
|
|||
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 "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 : : -------------------- : : : : : |
#8
|
|||
|
|||
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 http://www.lavasoft.de spybot http://security.kolla.de AVG free antivirus http://www.grisoft.com Etrust/Vet/CA.online Antivirus scan http://www3.ca.com/securityadvisor/virusinfo/scan.aspx Panda online AntiVirus scan http://www.pandasoftware.com/ActiveScan/ Catalog of removal tools (1) http://www.pandasoftware.com/download/utilities/ Catalog of removal tools (2) http://www3.ca.com/securityadvisor/n...aspx?CID=40387 Blocking Unwanted Parasites with a Hosts file http://mvps.org/winhelp2002/hosts.htm 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 "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 : : -------------------- : : : : : |
#9
|
|||
|
|||
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 -- Adaware http://www.lavasoft.de spybot http://security.kolla.de AVG free antivirus http://www.grisoft.com Etrust/Vet/CA.online Antivirus scan http://www3.ca.com/securityadvisor/virusinfo/scan.aspx Panda online AntiVirus scan http://www.pandasoftware.com/ActiveScan/ Catalog of removal tools (1) http://www.pandasoftware.com/download/utilities/ Catalog of removal tools (2) http://www3.ca.com/securityadvisor/n...aspx?CID=40387 Blocking Unwanted Parasites with a Hosts file http://mvps.org/winhelp2002/hosts.htm 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 "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 -------------------- |
#10
|
|||
|
|||
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 http://www.grystmill.com/articles/cleanboot.htm http://www.grystmill.com/articles/security.htm "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 "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 : : -------------------- : : : : : |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
System monitor window appears at start up | jawbreaker40(removethis)@cox.net | General | 6 | December 10th 04 01:42 PM |
Win98SE CPUROCKET.DLL Not found! | Wayne | Improving Performance | 16 | December 6th 04 07:54 AM |
Startup | John | General | 9 | October 9th 04 05:55 AM |
Little popup interrupts everything | Sue | General | 6 | October 8th 04 04:14 AM |
problem with my virtual machine | shawnk | General | 0 | June 19th 04 11:35 PM |