Sometimes I wish that Microsoft were something tangible that I could grab hold of and slap 32 different ways from sideways as I watched it writhe in anguish begging for mercy. Why? Because it does that to me almost daily. And I am sure I am not alone.
Tonight my wife showed me that she had installed Opera 9.5 on her computer. I was very impressed with her technical savvy that she showed in doing this. So much so that I told her that Firefox has just come out with a new version and, since Firefox the previous has all but killed my wife’s computer, updating may be the order of the day so that she could use Firefox instead of Opera.
So I had her load up Firefox and attempt to update from within the application. And you know what? Two words: Epic. Fail.
Frick.
Firefox froze and took the entire system with it. Not wanting to watch Firefox think about dying on the spot, I decided to power down the computer and start afresh. Yes ladies and gentlemen, I killed the windows.
Apparently the registry was being written to/read from when Firefox decided to crap all over itself. And as such, shutting the computer down in the middle of that process freeze basically wiped out the registry. Thanks Microsoft for the awesome idea of the registry. I so love that.
So I got a blue screen of death (BSOD) on the boot. I tried logging in to the last known good configuration. Nothing. Safe mode? No dice. Safe mode with networking? Nada. Safe mode in any capacity? Pukage.
I was crapola.
So I hit up the Microsoft Support site and did a search for a corrupt registry hive file and found article #307545 - How to recover from a corrupted registry that prevents Windows XP from starting. Remarkably, this article saved my hide.
Now I will be the first to admit that Microsoft is the bane of all even semi-smart people’s existence. I hate them with a passion that is unrivaled in normal circumstances. But tonight… well, tonight I actually applaud them.
There knowledge base article actually worked almost to the letter the way they said it would. I had to guess a couple of times, but the guesses were logical and easy to make based on what I was seeing. In about an hour and half’s time I was able to get my wife’s computer back on its feet and ready to be (ab)used once again.
So tonight, for the briefest of moments, I thank you Microsoft for putting out a halfway decent article on getting a Windows XP machine back up and running after your stupid registry hive files go belly up at a time when they shouldn’t have. You actually earned your $32,000,000,000,000,000,000,000 USD tonight, in my book.
You would have thought that I would have learned from my recent migration from Windows to Linux that there are steps to follow when moving computers. Apparently I have a lot yet to learn about this subject.
Head to my steps on migrating computers.
As I sit here and think about the stress of moving from one PC to another at work, I am again plagued with all of the things that I need to take care of the ensure that when I start using my new machine that it will be able to perform for me the way my old machine did. Only better. Because, after all, it is a new machine.
I am wondering if I will actually ever get all of the stuff out of the old computer that I need to have. I know I can take care of the obvious. Those are easy. Things like browsers, editors, the AMP bits of the (L|W|M)AMP stack. The things that trouble me the most are things like IP addresses that are stored in communication utilities like Putty and WinSCP. Or things like passwords that I have saved in FileZilla or FireFTP. Those are things that I never look at beyond once and never think to write down because I have them where I need them.
So I am now looking through the things that are going to need to be set up in order for me to do my job. And as I look at these things I find myself thinking that it might be a good idea to offer this up for others as well. So here is my list of things that I needed to do in order to allow myself to work on my new machine.
Migration list when moving to a new computer
- Apache web server:
- Make sure when setting up a new Apache web server locally that you look closely at the modules that are currently included on your old setup.
- Also make sure to copy your httpd.conf and any associated conf files that are included by the Apache configuration file, including all virtual hosts that you have setup.
- Of special interest here is the hosts files that you may have edited to set up local virtual hosts. For good measure make a copy of your hosts file for migration to the new machine.
- MySQL database server:
- Make sure this is installed before installing PHP. After it is installed make sure to edit the my.cnf file so that it closely resembles or even matches the current machine’s database server config.
- Install any MySQL client tools that you are using like MySQL Administrator, MySQL Query Browser, MySQL Workbench, Navicat and/or SQLYog.
- Make sure you have a backup of any databases that you intend to use locally, including the
information_schema and mysql databases.
- Take note of any stored connection details for each client tool, including host names, user names, passwords, SSH tunnels, HTTP tunnels.
- PHP:
- Install PHP after your web server (duh!) and after your database server(s). I mention this because you will want the database server client libraries installed before installing PHP so PHP can hook into them as needed with as little headache as possible.
- Make sure to also setup any and all PHP extensions that are currently setup on your “old” machine, taking note of packages that might now be in the PHP core that will not need to be included.
- Take note of the fact that many packages (including MySQL/MySQLi and cURL) have to be handled in a bit of different way because of the use of client libraries. Specifically, on Windows, there are several DLL files that need to be copied into a system path folder to allow PHP to see the client library hooks.
- Test each extension to make sure they are working as expected. Also use this time to test any local virtual hosts that are set up in the hosts file.
- Transfer and Source Control:
- Get your source code control apps set up. This includes Subversion, CVS and other source code control clients.
- Checkout to your local environment any repositories that you will be working with.
- Get all file transfer applications installed and configured, including FTP and SCP clients. These would be things like FileZilla, FireFTP, WinSCP (for Windows), etc.
- Get any other communication tools setup, like SSH clients and Telnet clients.
- Enter any stored connection details into these apps if you want to store them. It is important to copy these from the old machine in much the same way as you would copy the database server connection details.
- Editors and IDEs:
- This will range for each individual developer. The most important thing to remember here is to install the editors and IDEs that are most important to you.
- If your editors or IDEs support projects, setup any necessary projects.
- Graphics applications:
- Install any graphics manipulation programs that you use. These would include Photoshop (or the CS package), Gimp, etc.
- Install any video editing software.
- Miscellaneous:
- Install any other applications that you would expect to use.
- Install/paste/migrate/import any files that you will need onto your new machine. These could be web files, image files, personal files… whatever.
- Install any anti-virus applications that you will need.
- Configure your machine to your liking. Yes, I did wait to the end for this. I did this because quite honestly how your machine feels to you is completely irrelevant to getting your environment into a usable state. I know this is debatable, but these are my instructions.
I hope these steps help you in some way. I am constantly remembering things in the two recent migrations I have done, so I may edit this list at some point in the future.
I do think it is a rather comprehensive list of things to consider when migrating computers. If I am missing something, please be sure to let me know.