UtterlyBoring.com is produced by Jake Ortman (e-mail, resume), a 30-year-old dad, percussionist, freelance Web designer, consultant and jack-of-all-trades computer geek, living in Bend, Oregon. He created this so that his expensive journalism and technology degree isn't getting totally wasted. In addition to editing this site in his free time, he is the IT Director and Ad Designer at both Sunray and Discover Sunriver. He has LinkedIn, MySpace, Facebook profiles if you're trying to stalk him.
Opinions and comments on this site are the opinions of the author, not the author's employer, family, friends or pets.
This site is powered by Movable Type and is hosted by orty.com. Internet connection provided by Bend BroadBand. Since December 1st, 2002, there have been 5256 entries. Visitors to this blog have posted 16470 comments.
If you're reading this, you have too much time on your hands.
Barney said on 08/27/03 @ 06:56 PM: Okay, I'll admit - I'm the one with this "little" problem today!
I also posted a note at Lockergnome Forums, had this disturbing reply post from 'Wolf':
There is a utility that MS put out called Boot Vis, that causes the symptoms you are describing. I ran into serious problems with this utility, as it would run at startup (it monitors how files are being loaded during startup (and actually, as long as it's running) and allows you to make adjustments to how these files start - supposedly allowing you to optimize the way files and programs start up for a faster start time), and continue to run. It uses a temp file, that it constantly adds too, so by the end of the day, I had a HUGE temp file hogging almost ALL of my drive space. When you shut down and reboot, it recreates the temp file and starts fresh.
The problem I ran into with this program, is that once it was started, it COULDN'T BE STOPPED! It just continues to run. I tried everything - uninstalling, deleteing all file parts, turning off system restore, and then deleteing all parts of the file.. I even tried to talk to MS about it (they don't care - they don't provide support for the utility - even though they put it out). The program would not go away, and it started no matter what I did. In the end, I wound up having to reformat the HD and then re-install Windows to get rid of it...
If you installed BootVis from MS, you can try uninstalling it, and turning it off in the services, and even deleting the files (after turning off system restore). I doubt you'll be able to get rid of it short of a reformat.
If you are not willing to reformat, be prepared to reboot at least once a day to let the utility erase and recreate the temp file.
I hope this helps!
--------------------
Take Care and God Bless!
Wolf
---
NOOOO! AAAAh!
Neil T. said on 08/28/03 @ 03:05 AM: I know someone else had this problem, although I don't think it was BootVis that caused the problem - she wouldn't have been the sort of person to run that kind of program.
I've personally never had any problems with BootVis.
Barney Lerten said on 08/29/03 @ 10:24 PM: Well, it was a McAfee problem (see my posting on Lockergnome's Windows Forums if you're interested) and I just, after 5 HOURS in queue on their online help desk, had the woman step me through the steps to scrape the old VirusScan out of the system, then went online and downloaded the new one. Reboot didn't bring the problem - we'll see if it's a permanent fix. I said repeatedly they should push a fix to ALL users, she said "We'll look forward to that"(? Are they making more advanced bots these days?)
Sheesh!;-)
Tom said on 10/22/03 @ 12:49 PM: I have the probnlem at the moment too, with BootVis, but bootvis can be stopped... although you have to do it each time your computer reboots... start up bootvis, and tell it to stop tracing. I havent figured out a way to make it not start up next time you boot, but there must be one...
misiek said on 10/14/04 @ 08:31 AM: I found the way to stop bootvis , hdd format , nothing else works
(Caused by running bootvis program with tracing enabled "I found and eliminated the issue through the registry key - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\GlobalLogger has its start value defaulting to "1" this had been set by bootvis)" Change the 1 to a 0 and no more problem.