Taming Robocopy

A prolific commenter mentioned yesterday how much he dislikes Robocopy. Perhaps worse than I dislike Windows 7. And the nightmare scenario he describes sounds plausible. I’ve trashed directories with errant copy and xcopy commands, and I know I’m not the only one. And those are comparatively very simple.

I suppose one could put training wheels on a tool like Robocopy, but to me, that defeats much of its purpose. When I play the Robocopy card, it’s generally because I have a copy task that potentially will take several hours–if not days–and it’s going to run into errors, and I want it to just do the best it can, without asking me any questions, so I can walk away and let it chew on the problem for however long it takes.

I won’t say Robocopy is one of those things that can make or break a career, but it’s certainly allowed me to swoop in and save the day on several occasions, and that’s always good. So here’s how.
Read more

Using Robocopy to root out PST files

So the word came out that the office is migrating to Windows 7 at some yet-to-be-determined time, but soon. It’s in testing now. (Too bad they didn’t recruit me as part of the testing team, because breaking Windows 7 is one of my superpowers.)

We’ve been told to back up our data. Lots of people are paranoid that they’ll lose their Outlook PST files, and with it, their ability to do top-drawer work. Frequently we have to search our archives to find forgotten details about old projects. It helps to make the new projects go more smoothly.

I came up with a surprisingly easy solution. It doesn’t even require admin rights–which is good. I won’t elaborate.
Read more

How I fixed an infuriating printer problem

Windows 7 and my HP Laserjet 4100 weren’t getting along. And I was pretty livid about it. I paid $125 for my Windows 7 upgrade, and for that money, I got to mess around for 4 days trying to get better-than-1997 functionality out of what’s supposed to be the latest and greatest. I was about ready to trade it even up for a copy of Windows ME and Microsoft Bob. Because at least then I’d be able to print.

I finally fixed the problem, but finding the solution wasn’t easy. So I’ll present the symptoms and the ultimate solution here.

Read more

How I fixed a maddening Code 43 in Windows 7 (no firearms involved)

Gatermann talked me into trying one last time to re-install Windows 7, and if it didn’t work, he’d help me go Office Space on it.

Those of you who’ve been following me for the past week will know I started installing and trying to use Windows 7 on Saturday, and it didn’t go well. Among other things, my video driver constantly died with a Code 43, and I could print anywhere from 0-1 documents in between reboots. Basically, the computer became less useful to me than a Commodore 64. And given all the hype about how this was the best Windows ever, I wasn’t happy.

Read more

I sure hope Windows 7 SP1 gets here fast

So I’ve been running Windows 7 for about a day on an Intel motherboard. And I don’t know for certain if it’s the shoddy Intel hardware, or Windows 7, but I don’t think I’ve been this un-impressed since the first time I laid eyes on Windows ME.

Yeah, it’s that bad. I’m sure the Microsoft fanboys will jump in and chew me up, but let’s see if they can explain this away.

Read more

Attempting to tame C:\Windows\Installer

Nobody seems to know why the C:\Windows\Installer directory sometimes spirals out of control.

All I can add is that I’ve seen this kind of behavior. At a previous job, I administered a couple hundred servers. I had web servers, database servers, domain controllers, utility servers, installation servers, and the old web servers which basically served as a playground for the people who had more clout than me.

Everything but the playground servers theoretically started out identical to each other except for the IP address. They were built following the same instructions.

But invariably, one or two servers in each team would suffer from perpetual low disk space. To keep things running, I had a few Red Green-like solutions.
Read more

Ways to speed up an aging laptop

Yesterday Lifehacker did a feature on laptop tweaks and upgrades, that basically came down to reinstalling the OS, adding memory, and upgrading to an SSD. All of those are good things to do of course, but there’s more you can do. I posted a response there; I’ll elaborate a bit here, where I have more room to do so.

There are tons of links here to previous content I’ve written; optimizing aging machines is a recurring theme for me. I’ve been writing on that topic for 11 years now.

Read more

Defrag scareware

This isn’t exactly news, as word has been going around for a couple of weeks, but if you haven’t heard about it elsewhere, there are some fake defragmenters going around.

I heard mention of it today, and it reminded me that I saw one last week when I was working on my mother in law’s computer. This was especially obnoxious, considering that at the time, I was running Firefox and I was visiting a mainstream site.

So there are a couple of things you need to keep in mind.
Read more

A free SSD alignment tool

We’ve talked recently about the importance of aligning your partitions on your SSD or your RAID array. What if I told you you could align an SSD or RAID array for free? Here’s where to find a free SSD alignment tool–it’s just not normally billed as such.

Alignment helps performance, sometimes tremendously, and it also dramatically improves your SSD’s life expectancy. Newer versions of Windows automatically align their partitions, but only if you do a clean installation to an empty drive. Older versions of Windows created their partitions starting at sector 63, for tradition’s sake. Maybe moving off sector 63 made dual-booting with Windows 9x harder.

Two readers, Jim and Xrocode, suggested utilities to do the job. One costs $30 and seems fairly automatic. One is free and requires a small amount of work. Grab the freebie here. It’s a 274 MB download, so it doesn’t even take all that long.

Read more

Optimizing Windows’ startup sequence

In days of yore, it was possible to go by one simple rule. When several minutes passed between the time your desktop appeared and the time you could actually do something, you could just run MSConfig and disable anything you don’t recognize. Back when a typical PC started up maybe a half-dozen things and a sick PC started up 12-18, that was manageable.

Not so much today. Not when there are 22,528 known things (as of 30 Nov 2010) that insert themselves into system startup.

I didn’t make that 22,528 number up. How did I know?

Read more