I’ve done a bunch of VirtualBox installs, upgrades and VM migrations recently. I’ve found that the automated Guest Additions installation hasn’t always kicked off. Typically the installation can be started by selecting Device -> Install Guest Additions from the menu when the VM is running. But this wasn’t working for me, so I needed to manually install the additions. This was done with both Windows and OS X hosts with Windows guest OS’s.
This procedure gets down to the basics. In most cases I did not have to locate the Guest Additions ISO as it was already available in the library and just needed to be mounted. You can skip to “Installing Guest Additions” and see if the ISO is already available.
Locate the Guest Additions ISO
Mac OS X is a little more involved. First locate VirtualBox in the Application folder, right-click it and select show package contents.
Then browse to Contents/MacOS/VBoxGuestAdditions.iso. Copy it to a location that accessible when browsing for files.
On Windows PC hosts the VBoxGuestAdditions.iso file is located in c:program filesoraclevirtualbox. It can be accessed directly and does not need to be moved.
Installing Guest Additions
Start the VM that needs the guest additions.
Click the CD icon in the bottom task bar.
If it’s listed, select VBoxGuestAdditions.iso. If it’s not listed select “Choose…” and browse to the ISO file identified in “Locate Guest Additions ISO” above.
If autorun kicks in then run VBoxWindowsAdditions.exe. If autorun is disabled then browse to it in file explorer and run it. You’ll need to reboot when the installation is done.
For the record, this was with VirtualBox 4.2.4.
I use Bento a bit and I’ve been using a symbolic link to point to the database in a Dropbox folder. This has worked pretty well, except occasionally the symbolic link would break. I recently eliminated the symbolic link and it seems to be working well.
To set this up you’ll still need Dropbox but then you can skip the symbolic link.
- Decide where you want the database in Dropbox. I want mine in /Dropbox/data.
- Move the existing Bento database(s) to the new location. By default the default database is created in [UserHome]/Library/Application Support/Bento and is called bento.bentodb.
- Start Bento while holding down the option key so that the following dialog appears:
- Click the choose button and browse to the database you just moved and select it. It should now be listed as the selected database as shown below:
Note that in the above screenshots I checked the “Show This Dialog” option so this dialog always shows and I don’t have to hold the Option key down. This is useful if you have multiple Bento databases. I do but don’t want them all in Dropbox. Bento will continue to open the last database selected unless told to do otherwise.
- Click OK and the database will open.
Words of warning. Bento isn’t designed to be opened by multiple PCs at the same time so while the database will sync, be sure to only have it open on one computer at a time. Be sure to keep backups in case the syncing causes bad things to happen. I’ve been syncing this way with Bento 4, although Bento 3 does have the same database selection dialog.
One of the nice features of Windows Home Server is that the existing drives can be moved around without breaking anything. I benefited from this recently and did mention it in my last Trail Log but figured it was worth highlighting as a tip.
If you need to rearrange disk in a Windows Home Server or move them to new connections you can do so without any special work (other than shutting down WHS for the move). When I moved the warm hard drives from the internal bays to the external bays all I had to do was shut down the server and physically move the drives. Likewise when I re-seated all the cables I didn’t have to worry about putting them in the same SATA port.
One thing to keep in mind is that if your using a home build like I am, and use the Disk Management for Windows Home Server Add-in you will still need to keep track of the drive bay assignments when you move drives or cables.
As part of my website redesign I needed to change around my categories. With over 600 posts this could be quit daunting, although I was keeping the categories with a lot of the posts. I did a quick Google search for WordPress bulk move category to look for tips and all I found in the top results were references to plugins. Nothing against plugins (I use many) but this isn’t something I wanted to test enough to trust on this site. I’d hate to miss a bug that corrupts my site.
Then I did what I should have done first. I listed the posts in a category and looked at the bulk edit options. And my solution was there. I had three things going for me:
- I’ve been excluding category pages from search engine indexes for a very long time. No need to worry about someone clicking a search result to find a “page not found” error.
- I was completely eliminating the categories.
- With only a very few exceptions, I was moving every post into an old category into an existing category then I was adding a tag with the old category name.
The process was simple (for the record I’m on WordPress 2.9.x).
- Go to categories in the WordPress administration panel and click on the number next to the category to list all the posts in the category.
- Select all the categories listed then select “Edit” under bulk options and click “Apply”. This will open a bulk edit box at the top of the screen.
- I selected the category I wanted everything in and I typed in the new tag (to match to old category name)
- I clicked “Update Posts”. This added the category to the existing selection(s) and added the tag to the existing tags. Nothing was removed.
- If there were a lot of posts I completed steps 1 through 4 multiple times to get through them all, one page of 25 at a time.
- I went back to categories and deleted the old category (Ok, first I listed the posts again and made sure everything was right.) Since the posts were already in another category the old category was simply removed.
Sometimes it takes awhile for things to sink in through my skull. WordPress added post revisions back in version 2.6. So after months of seeing those post revisions listed, and those messages about there being a newer version than what I had posted I decided to do something about them.
Since it’s introduction I haven’t used the post revision feature so the decision to turn it off was a no-brainer. This is done by adding the following line to the wp-config.php file:
This doesn’t delete the existing post revisions but since that requires touching the MySQL database I decided to wait until I had a backup and the time to restore if things went bad.
I finally had the time this weekend I removed the old revision. The information came from Andrei Neceulau and his instructions for removing the revisions in WordPress 2.6. While others have posted queries that remove the post revisions themselves, Andrei has a query that also removes the meta data for those posts.
I guess it wouldn’t hurt to leave the old post revisions in the database, but I don’t like the idea of this useless data clogging my database. As for the revision feature itself, I guess it could be useful in some cases but certainly not for me.