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 |
#31
|
|||
|
|||
!!!BOOTVIS EATS UP MY DRIVE!!!
"Comp Guy" wrote in message
... Well I tried using recovery console. It deleted the file and directory, but they came right back. Any other ideas? -- Please be polite. ------ "Comp Guy" wrote in message ... Did you check services? Have you tried to id it in processesand end it there? I'd try and stop it there then run msconfig and see if it's in startup. BTW Although I do think the crossposting is excessive you did get jumped on awful quick in here. Good luck |
Ads |
#32
|
|||
|
|||
!!!BOOTVIS EATS UP MY DRIVE!!!
Well I tried using recovery console. It deleted the file and directory, but
they came right back. Any other ideas? -- Please be polite. ------ "Comp Guy" wrote in message ... I told bootvis to trace. After my computer restarted, nothing happened. I decided to get rid of bootvis, so I tried to uninstalled it. The uninstall messed up, and wouldn't work again, so I went through, deleting as many bootvis files and registry entries as possible. Now, a file called trace.log in the c:\windows\system32\logfiles\wmi is there and I can't delete it. It grows at about 1 mb a second. When I try to delete it, it tells me that it is in use. So I boot to safe mode, but I still get the same error when I try to delete it. -- Please be polite. ------ |
#33
|
|||
|
|||
!!!BOOTVIS EATS UP MY DRIVE!!!
Thank you for your polite reply, but that was one of the first things I
checked for. Any other ideas? -- Please be polite. ------ "tk" wrote in message ... "Comp Guy" wrote in message ... Well I tried using recovery console. It deleted the file and directory, but they came right back. Any other ideas? -- Please be polite. ------ "Comp Guy" wrote in message ... Did you check services? Have you tried to id it in processesand end it there? I'd try and stop it there then run msconfig and see if it's in startup. BTW Although I do think the crossposting is excessive you did get jumped on awful quick in here. Good luck |
#34
|
|||
|
|||
!!!BOOTVIS EATS UP MY DRIVE!!!
On Mon, 29 Sep 2003 23:55:26 -0400, "Comp Guy" wrote:
couldn't you just go into "restore" and restore you system to the point where you didn't have this program installed on your system? Monte and one last question, if I removed it from my computer, then why is it still tracing? |
#35
|
|||
|
|||
!!!BOOTVIS EATS UP MY DRIVE!!!
When you run low on space, Windows deletes all restore points.
-- Please be polite. ------ "Montgomery Hounchell" wrote in message ... On Mon, 29 Sep 2003 23:55:26 -0400, "Comp Guy" wrote: couldn't you just go into "restore" and restore you system to the point where you didn't have this program installed on your system? Monte and one last question, if I removed it from my computer, then why is it still tracing? |
#36
|
|||
|
|||
!!!BOOTVIS EATS UP MY DRIVE!!!
I'm not sure if this will really help or not, but after reading all the
posts it seems as if you haven't found a working solution yet,... Two possibilities worth trying involve applying the freeware programs "RegCleaner v4.3" by Jouni Vuorio, and the "Xteq Systems" utility. If there's a registry entry without a program it links to, there's a good chance that the RegCleaner program will discover the fact and delete the entry (when in full auto cleaning mode). Of course, it might not have that capability, if the item the entry links to is running. But, if it's running, then the file can't be gone, can it? Which would mean RegCleaner wouldn't find a faulty key,... So, I guess that won't work. The Xteq Systems utility is a power-tweaking thing. It's essentially a collection of applets that are accessed via a GUI list of descriptions. There's a section called "Startup/Shutdown". Within that section, there will be a couple of subsections for type of OS. Picking the OS that applies to you, you should find a further subdivision called "Autorun"; there's a part one for the system in general, and a part two for the current user. Check the contents shown in the window to the right when you click on the Autorun programs item. You might find your Bootvis listed there. If it is, then disable it via the buttom below the window. Exit & reboot. That might (?) prevent it from being activated & put into use - and, give you the chance to do something different than what's been tried before. A few other thoughts,... a) Have you tried (recently) using the "Find" utility, for any file of any type, having the text "bootivs" in the name? b) Perhaps if you track down a way of contacting them, and approach them just right, the people who made the "bootvis" application would give you a list of all registry keys & values, & files installed during the installation process? c) Task Manager can give you a list of all running process, and you can end ANY running process from there. So, if it's in use, make it not in use - and, then you've got different options to pick from. Scruffy ===================== "Comp Guy" wrote in message ... I told bootvis to trace. After my computer restarted, nothing happened. I decided to get rid of bootvis, so I tried to uninstalled it. The uninstall messed up, and wouldn't work again, so I went through, deleting as many bootvis files and registry entries as possible. Now, a file called trace.log in the c:\windows\system32\logfiles\wmi is there and I can't delete it. It grows at about 1 mb a second. When I try to delete it, it tells me that it is in use. So I boot to safe mode, but I still get the same error when I try to delete it. -- Please be polite. ------ |
#37
|
|||
|
|||
!!!BOOTVIS EATS UP MY DRIVE!!!
Side note ... lessons learned ...
Bootvis cut my boot time by four seconds. Whooee! That's not even worth the time that I spent downloading the bootvis package. And considering the hassles that Comp Guy is experiencing, the conclusion can only be ... just don't do it. (Maybe that's why Microsoft removed it from their web site?) "Comp Guy" wrote in message ... Well I tried using recovery console. It deleted the file and directory, but they came right back. |
#38
|
|||
|
|||
!!!BOOTVIS EATS UP MY DRIVE!!!
I'm not sure if this will really help or not, but after reading all the
posts it seems as if you haven't found a working solution yet,... Two possibilities worth trying involve applying the freeware programs "RegCleaner v4.3" by Jouni Vuorio, and the "Xteq Systems" utility. If there's a registry entry without a program it links to, there's a good chance that the RegCleaner program will discover the fact and delete the entry (when in full auto cleaning mode). Of course, it might not have that capability, if the item the entry links to is running. But, if it's running, then the file can't be gone, can it? Which would mean RegCleaner wouldn't find a faulty key,... So, I guess that won't work. The Xteq Systems utility is a power-tweaking thing. It's essentially a collection of applets that are accessed via a GUI list of descriptions. There's a section called "Startup/Shutdown". Within that section, there will be a couple of subsections for type of OS. Picking the OS that applies to you, you should find a further subdivision called "Autorun"; there's a part one for the system in general, and a part two for the current user. Check the contents shown in the window to the right when you click on the Autorun programs item. You might find your Bootvis listed there. If it is, then disable it via the buttom below the window. Exit & reboot. That might (?) prevent it from being activated & put into use - and, give you the chance to do something different than what's been tried before. A few other thoughts,... a) Have you tried (recently) using the "Find" utility, for any file of any type, having the text "bootivs" in the name? b) Perhaps if you track down a way of contacting them, and approach them just right, the people who made the "bootvis" application would give you a list of all registry keys & values, & files installed during the installation process? c) Task Manager can give you a list of all running process, and you can end ANY running process from there. So, if it's in use, make it not in use - and, then you've got different options to pick from. Scruffy ===================== "Comp Guy" wrote in message ... I told bootvis to trace. After my computer restarted, nothing happened. I decided to get rid of bootvis, so I tried to uninstalled it. The uninstall messed up, and wouldn't work again, so I went through, deleting as many bootvis files and registry entries as possible. Now, a file called trace.log in the c:\windows\system32\logfiles\wmi is there and I can't delete it. It grows at about 1 mb a second. When I try to delete it, it tells me that it is in use. So I boot to safe mode, but I still get the same error when I try to delete it. -- Please be polite. ------ |
#39
|
|||
|
|||
!!!BOOTVIS EATS UP MY DRIVE!!!
Side note ... lessons learned ...
Bootvis cut my boot time by four seconds. Whooee! That's not even worth the time that I spent downloading the bootvis package. And considering the hassles that Comp Guy is experiencing, the conclusion can only be ... just don't do it. (Maybe that's why Microsoft removed it from their web site?) "Comp Guy" wrote in message ... Well I tried using recovery console. It deleted the file and directory, but they came right back. |
Thread Tools | |
Display Modes | |
|
|