When one member of my mirrored pair of system drives failed earlier this year, I replaced that pair of Seagate 7200.10 320 GB drives with a pair of Samsung SpinPoint HD501LJ SATA II 3.5″ drives with 16MB Cache. I also installed the still-working member of that pair in my system, so as to retain access to all kinds of files and information from that machine.
Continue reading Begone! Dratted (Old) System Files: Begone!
In writing about my trials and tribulations with Windows Vista on my production PC over the summer, I summarized my situation in a blog entitled “Time for a new motherboard?” on September 20. By the beginning of October things with the system had quieted down enough, thanks to switching to a single-vendor security solution (PC Tools Spyware Doctor with Antivirus, plus the PC Tools Firewall, and their ThreatFire behavioral malware blocker) and making some other software and configurations changes, that I thought I had the hiccups behing me. I was down to random problems once a week, and went three whole weeks without a single BSOD.
Continue reading A Change of Memory Makes a Difference?
Last night when I was quitting for the day, after 11 PM, I noticed that the autoupdate function in Windows Update had posted two more items to my primary production PC. Both look interesting, but so far I”ve had some trouble trying to ferret out more details about one of these two patches.
Continue reading More out-of-cycle MS Updates post
I”ve been using Spyware Doctor to handle spyware on my machine for over two years now, with great success in handling spyware. In the past three months, I have switched to PC Tools Spyware Doctor with AntiVirus thanks to issues documented in my story “Best-of-Breed Apps Aren”t Always Best for Vista” –namely, incompatibilities between AVG AntiVirus 8.0 and Spyware Doctor 6.0 that kept causing blue screens on my primary production machine.
Continue reading Snapshot: PC Tools Spyware Doctor with AntiVirus
Normally, Microsoft reserves its security patches, fixes, updates, and other software tweaks and maneuvers for the second Tuesday in each month, aka “Patch Tuesday.” Yesterday afternoon I was somewhat surprised to see various sources trumpeting the release of an out-of-schedule security patch through Windows Update on the fourth Thursday in October.
Continue reading Out-of-cycle Security Patch Posts to Fix Huge, Gaping RPC Hole
Given the focus of this Web site, I hope it makes sense that I also follow industry news about Windows Vista as well as its technical ins and outs. Recently, I”ve noticed a growing swell of journalistic opinion/reporting that Vista has failed, that Vista is no good, and that the business world is aleady passing Vista by. Jason Hiner”s 10/6 story for ZDNet is a pretty good example of this genre: it”s entitled “The top five reasons why Windows Vista failed” and it reports the Vista OS as having already failed in the marketplace 22 months after its introduction in January 2006.
Continue reading Is It Really “Game Over” for Vista Already?
One of the many things I do for a living is to develop and revise courseware for a local Austin company that provides “Learning Centers” for all kinds of Fortune 500 companies. This includes some companies whose high tech products and business activities overlap with my interests and expertise. Right now, I’m hot on the track of revising a course on spam and spyware that somebody else developed back in 2004. Among other things this means revising statistics, information, and tools supplied during Windows XP’s heyday, and updating them to reflect an increasingly Windows Vista world in 2008.
Continue reading Sysinternals TCPView Reveals Port Activities
In yesterday’s blog, I reported on the appearance of reports for numerous (9 one day, 10 the next) “corrupt and unusable” VolumeShadowCopyXX entries in the System Log in Event Viewer. All of these originated from source Ntfs, the Vista file system manager.
Continue reading Shadow Copy Puzzle Partly Deciphered
In the past couple of months, I ‘ve been grappling with graphics stability issues. Mostly, this has meant driver restarts where you get a message that reads something like “Display driver stopped responding and has recovered.” Occasionally, this has involved a BSOD that mentions the Nvidia driver files nvlddmkm.dll or nvlddmkm.sys. When it happens, it seldom occurs more than twice a week. I keep checking the Nvidia driver download page, grabbing new drivers as they become available (including occasional betas), and hoping for the best.
Continue reading New Graphics Drivers, New Shadow Copy Puzzles to Ponder
Any time something surfaces in Event Monitor that I’ve never seen before, it always piques my interest. My usual practice is to scan the Event Monitor’s Windows Application and System logs every Monday morning to see what might need my attention. This morning, among the items that caught my eye was this message “Application (pid 4684) cannot be restarted – Application SID does not match Conductor SID” from an unfamiliar source–namely the Restart Manager.
Continue reading Restart Manager Surfaces In Event Monitor