Windows 7 Installation - First Try

I decided to install Windows 7.  I had previously written up my preferred Windows XP installation process.  This post updates that previous writeup for Windows 7.  It seemed likely that I would find additional helpful Win7 tweaks after using it for a while, so I considered this my first try.  The version I was installing was Win7 Ultimate.  My efforts as described here were fairly comprehensive -- I worked through lots of issues -- but also pretty disorganized.  The second try, I hoped, would be better.

I decided to get and use a 32-bit version of Win7.  I had tried a 64-bit version of Ubuntu and found that there were quite a few problems.  Even at the time of this writing, I was hearing some indications that reminded me that 64-bit Win7 and other 64-bit operating systems were still not established.  This was from the perspective of someone who usesd the computer for work, and a wide variety of general-purpose work functions at that, and not much for play.  I would have had a different opinion if I had different needs.  Presumably 64-bit had more speed.

I also decided to do a clean installation, completely overwriting the previous Windows XP installation.  Although I didn't look into it, it sounded like there might be some kind of "hard link" alternative.  I didn't explore it, so I was not sure if it was actually much easier than the fresh install option.  For upgrades from Vista, apparently there was an Upgrade Advisor that might have been helpful.

In my case, with my Gigabyte motherboard, the essential first step, before even completing the Win7 installation, was to install two motherboard drivers that were supposed to be installed from floppy disk.  I did not realize this.  A belated search led to one source who claimed that reinstallation was not necessary, but I had only just done the installation, and it had been pretty easy, so I decided it was easier to just reinstall than to follow his directions.

I started by downloading the current drivers from the motherboard manufacturer's website.  Gigabyte's website contained a link to DriverAgent, which did a free scan for missing drivers but then wanted to charge me a fee to download and install them. I decided to just get them from the Gigabyte site. I unzipped them, but to see and actually install their setup files, I had to make adjustments in Windows Explorer (Tools > Folder Options > View > unhide everything). I made other changes to the View tab while I was there. It had not changed much since Windows XP, so I used pretty much the same settings as before. (For details, go to the previous writeup and search for "Windows Explorer.")  The drivers unzipped automatically into separate folders.

It then occurred to me that possibly a complete reinstallation was not necessary.  I left my new but imperfect Windows 7 installation in place for the moment and rebooted from the Windows 7 DVD.  I clicked Next to get past the first Install Windows screen and chose the "Repair your computer" option. In the System Recovery Options dialog, I clicked on the Load Drivers button, inserted the CD containing the drivers, double-clicked on the file that was a "setup information" file type in the folder for the first driver, and clicked Add Drivers. I repeated those steps for the other driver. Evidently these steps loaded the drivers into memory.  Then I clicked Next and proceeded to the System Recovery Options dialog.  I clicked Startup Repair, but it could not detect a problem.  So I gave up on this approach and did the complete reinstallation.

Gigabyte's webpage said that the two drivers that had to be installed during Windows 7 installation would have to be installed from a floppy drive.  I did not have a floppy drive.  I burned the folders containing those drivers onto a CD.  Then I inserted the Windows 7 DVD and rebooted.  When the BIOS was loading, I got an option to press any key to boot from the DVD.  I did that.  This put me at the Install Windows screen.  I clicked Next > Install Now.  I took the custom installation option.  When I saw the question, "Where do you want to install Windows?" I clicked "Load Driver."  But after a minute, it came back with a message:

No device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK.

One of these troublesome drivers was for a RAID array.  I had not actually set one up yet.  I unchecked the option that said, "Hide drivers that are not compatible with hardware on this computer," and then clicked Rescan. I still got the same message.  I wasn't sure what that meant regarding the quality of my download and the relevance of the drivers that Gigabyte's webpage had listed for my motherboard.  It appeared that I would be able to set up software RAID in Windows 7 regardless of my hardware, and that a hardware RAID array would have to be in place before I installed Windows.  As I was thinking this over, I came across a good article on RAID in Windows 7 that made me think that a Win7 software RAID array was actually better for my purposes anyway.  So at this point I bailed out of the attempt at reinstallation and just rebooted the Windows 7 installation that I had already set up.  I describe my actual RAID setup process in a separate post.

The other troublesome driver was for AHCI.  After installing the other drivers and rebooting, I got an option to set the BIOS to boot in AHCI mode.  Or something like that -- it had a short fuse and demanded a decision before I could really read what it was saying.  I went with the Yes option, I think, and that made Windows unable to run.  I had to reboot, hit Del to go into the BIOS, and look around to replace the AHCI option with the Native IDE option.  I then observed that, of course, the BIOS update had wiped out my settings, so I changed some other items while I was there.  Then I rebooted.

The next step was to install antivirus and firewall software.  I had always previously gone with free versions, most recently AVG.  For the moment, I decided to continue with AVG, but also looked into stronger alternatives, and on that basis, I thought I would eventually switch to F-Secure.

Next, updates.  I wanted to download them once and save them, so that I wouldn't have to re-download hundreds of megabytes' worth of updates and service packs every time I re-installed Windows 7.  But I had spent a lot of time taking the manual approach with Windows XP, it was hard to be sure of the right order to install them in, and it was a lot easier to just let the Windows Update site do it automatically.  I had already encountered an opportunity to set the downloads the way I wanted, which was to download but not install.  I preferred that because otherwise Windows XP, at least, would keep insisting on rebooting the system, until at some point that reminder would pop up right while I was in the middle of typing something and, presto! I would hit the wrong key and the system would reboot, taking all my work with it.  Unlike XP, Win7 wasn't showing me an icon in the system tray to indicate that it had downloaded updates and was waiting for a chance to install them.  It also didn't offer to do so when I clicked the Turn Off option to shut down the system.  But I could tell that it had downloaded updates because, when I did go to the Windows Update page, it didn't need to download anything; it just proceeded right into the installation of about 140MB worth of updates (counting those that weren't ready to install until after a reboot).

While updates were installing, I looked into user accounts.  For efficiency reasons, I had been running WinXP as administrator.  Microsoft said the user account would protect my computer by preventing users (me) from making changes that affect everyone who used the computer (me).  In other words, I decided to continue to do my work while logged in as administrator.  So before I installed programs that might configure themselves for individual user accounts, I did a search for how to delete my user account.  The advice I followed led me to the Control Panel, so at this point I decided to go ahead with the full Control Panel tour, which I had postponed until later when installed WinXP.

Ideally, I would have taken care of the accounts at this point.  But I didn't.  So some of the changes described below were made to my own personal account ("Ray"), and therefore had to be redone after I started up the Administrator account and deleted the Ray and Guest accounts.  Another thing that complicated that step of changing accounts was that I did not approach it through Control Panel.  I made the change in a different way, before looking at Control Panel > User Accounts.  So I was not sure what that User Accounts area would have looked like originally.

What actually happened was that I went ahead with the Control Panel tour (below), and toward the end of that process I discovered Ultimate Windows Tweaker (UWT), and used it to make some of the changes that I would have made through Control Panel.  UWT had some options that Control Panel did not have, but it also lacked some options that Control Panel.  It probably did not make much difference which came first, but in my own future installations I felt I would probably go through Control Panel first, and then run UWT, or possibly God Mode (below).

At any rate, I had to go into Control Panel > User Accounts (having switched, at the top right corner of Control Panel, from Category view to small icons), select the Ray account, and then click the "Delete the account" option.  There did not appear to be a way of deleting the Guest account, so I just left it turned off.  Then, to continue preparing for the Control Panel tour, I opened Internet Explorer and opened a separate tab for each webpage that I often checked in Internet Explorer (e.g., Hotmail).  Then, in Intenet Explorer, I went to Tools > Intenet Options > Home Page > Use current.

What I wanted, for this purpose, was to konw how to use the PowerShell ISE to create a set of modules for PowerShell that would do things (e.g., adding features) that otherwise I would have to do manually, by going into this menu and choosing that option, etc.  Why should so many of us spend so much time doing that sort of thing, when it was (in my understanding) entirely possible to use PowerShell commands, already installed in Win7, to share a set of commands that would do it all automatically, in one step?  But apparently I was misunderstanding something about this.  My search suggested that, while there were plenty of websites sharing Win7 tweaks, there were almost none sharing Win7 tweaks contained in PowerShell modules.

Registry edits were an alternative for some such tweaks.  My key sources for guidance, in these tweaks, included the massive collection of SevenForums tutorials and the How-To Geek list of registry hacks.  This was the point at which, in future installations, I would run Win7RegEdit.reg, a text file that I built up during the process of learning how to configure Win7.  Running it at this point, which I did not do, would have affected some of the other instructions shown below.  Before running it, I would need to adjust editing permissions for one branch of the registry.  Steps for that:  go into regedit, navigate to HKEY_CLASSES_ROOT\CLSID, right-click on CLSID, go tinto Permissions, highlight Administrators, click Allow Full Control, go into Advanced, check "Replace all child object permissions with inheritable permissions from this object."

Next, in Control Panel, at the top right corner, I switched from Category view to small icons.  Then, going down the list, I hit a number of other items.  These are shown here in alphabetical order as they appeared in Control Panel, but this order also happened to be important for a few of these items:

• Action Center:  I had already set my Windows Update settings.
• Administrative Tools:  in Computer Management > Storage > Disk Management, right-click on the CD-ROM drive (at the bottom) and change its drive letter to Y.  Then change other drive letters (after rebooting, if necessary) as needed.
• AutoPlay:  turned off for all devices.  Defaults set to "Take no action" for all items except movies and videos.
• Backup and Restore:  I had not had good luck with Windows System Restore.  I preferred Acronis True Image.  So I just verified that this option was turned off.
• Folder Options:  finished setting items I had not already set (above).
• Internet Options:  I went into Tools > General tab > Browsing history > Settings > Move folder to another drive. I also went to Tools > General tab > Tabs > Settings > adjust as desired. I went to Security tab > Custom Level > Scripting section (near the bottom) > Allow programmatic clipboard access > Enable.  Then I navigated to YouTube.com and played a video, so as to trigger the process of installing Adobe Flash Player.
• Notification Area Icons:  Always show all icons and notifications on the taskbar.
• Personalization:  Windows Classic theme.  Window Color > Adjust at least Active Title Bar, Inactive Title Bar, Menu, and Desktop.
• Power Options:  Show additional plans > High performance > Change plan settings > Change advanced power settings > Change settings that are currently unavailable > High performance > change individual items as desired > Apply.
• Programs and Features:  Turn Windows features on or off > Make sure Indexing Service is off.
• System:  Windows Activation > Activate.  System Protection > Hardware tab > Device Manager > verify are no yellow-circle exclamation marks.  Hardware tab > Device Installation Settings > Yes, do this automatically.  Advanced tab > Performance > Settings > Advanced > Change > Uncheck automatically manage paging file size for all drivers; instead, set a paging file of 4000-8000 MB (or more) on each hard drive.  System Protection tab > Configure > adjust Disk Space Usage as needed.
• Taskbar and Start Menu:  Start Menu tab > Customize.  Adjust various items to taste.  Turn on Run command.  Save and close.
• User Accounts:  see above.  When the dust settled, I had only the Administrator account here.
• Windows Defender:  turn on.
• Windows Update:  after installing desired updates, highlight all unwanted updates (e.g., foreign language packs, right-click, and select "Hide updates."  

For purposes of doing these tweaks, UWT (above) was not the only consolidated alternative to Control Panel.  Another was God Mode.  Apparently this was just originally going to be an All Tasks folder in Win7, but Microsoft didn't include it in the final version, and bloggers gave it the God Mode name.  It seems there were actually a number of different subcollections of tweaks which, at brief glance, didn't look like they added much to UWT for my purposes.  What I decided to do with this was to create a Start Menu entry for an All Tasks folder.  The full folder name was long, so I parked it further down in the Programs listing within the Start Menu (below), and just put a shortcut to it at the top level of the Start Menu.  To automate part of that last step, I wrote a command for a DOS batch file. That batch file (Win7NewInstall.bat) eventually came to have other lines as well.

In the past, I had overlooked some Control Panel items that would have been useful.  So in that God Mode (what I called the All Control Panel Options) folder, I hit Ctrl-A (i.e., I selected everything) and then right-clicked and said "Create shortcut."  This put 276 shortcuts on my desktop.  I moved them to a folder, where I could see their full names.  I deleted those that I didn't think I would need.  I moved a bunch of them to a folder for items that I would run only when installing a new system.  I put the rest in other categories, and moved them to relevant places in my Start Menu.  This was an alternative to the approach of removing or hiding unwanted items in Control Panel.  With these steps, I hoped to be able to do without Control Panel, but it was still there unchanged for purposes of following steps advised by others.

I had worked out a customized Start Menu, with several advantages.  Another post describes the process of making that work in Win7.

Something else that I should have done early in the process was to map my network drives.  The problem was, I was simultaneously doing some hardware changes.  I had a Synology Network Attached Storage (NAS) unit, but for performance reasons I wanted to change to some other arrangement.  I needed to get that other arrangement in place first -- actually, before proceeding with this installation -- or at least I needed to know which drives would be where, because of course when I mapped them I would assign them drive letters, and aspects of this installation would be looking for those letters.  So I took a detour, during this installation, to figure out that part of my hardware arrangement. 

The next task was to customize Windows Explorer.  It looked like I was stuck with the new menu bar that Microsoft added at the top, unless I wanted to risk seriously screwing up the system.  I wondered if there was a good alternative to WinExp.  When I started looking around, I saw statements that resonated with my experience regarding WinExp's slowness.  It developed that there were a bunch of alternatives.  I prepared a separate post leading to my conclusions in that area.  Basically, I decided to start with Total Commander and see if I liked it.  Of course, I could still use Windows Explorer regardless.  This somewhat took the fire out of my interest in more Windows Explorer tweaks.

Other Tweaks

Early in the process, I installed Google Chrome.  I had to.  It was impossible to get anything done in Internet Explorer, especially in terms of looking at lots of different webpages providing advice on how to solve problems.  Within Chrome Extensions, I installed Webpage Decorator.  The reason for this extension was to make it easier to see which links in Google searches I had already visited.  Their colors were almost identical in Chrome originally.  After installing it, I clicked its newly installed icon (at the right end of the Chrome search bar) and made the colors of links and visited links more clearly distinct.

I got an uninvited item on the taskbar saying, "Welcome to Windows Media Player."  I went through a custom installation, making it the default player for the time being.  Then I unpinned the icon from the taskbar.

Also, from almost the beginning, Windows Defender would give me an error message at startup:  "Service has stopped.  A problem caused this program's service to stop.  To start the service, click the Start now button or restart your computer."  I searched for a solution and noticed lots of posts on how to uninstall or disable Windows Defender.  I looked into that.  While Windows Defender appeared to be antispyware that ordinarily performed a valid function, it was also no different than other antispyware.  Apparently this problem could be caused by conflicts with other antivirus software (e.g., McAfee).  I originally thought Windows Defender kept being turned off after I turned it on because I had disabled UAC; apparently Windows Defender was related to that.  Ordinarily, to turn it off, I would go to Control Panel > Windows Defender > Turn it on > Tools > Options > Administrator > uncheck > Save.  This would still produce the error, "This program is turned off."  In another approach, I tried running services.msc and selecting Disabled as the Startup type under Windows Defender (right-click > Properties).  But that, too, left me with a reminder to turn on Windows Defender on startup.  Anyway, this approach of trying to shut Windows Defender up was not working.  If you can't beat 'em, join 'em.  I went back to services.msc and set it to Automatic; I went into Control Panel and uninstalled AVG antivirus; and I downloaded and installed Microsoft Security Essentials.  I planned to upgrade to better antivirus software later, but hoped that this would reduce conflicts for the short term.

Epilogue

By this point, it was time to start over again.  The reason was that this installation had somehow acquired a networking problem that I just could not fix. The reinstallation is described in another post.

Ubuntu 10.10: Tweaked Installation

I had previously installed Ubuntu 10.04, and had arrived at a fast way of adjusting the basic installation to my needs. This post updates and simplifies the separate post in which I described that process.  Here, I was using Ubuntu 10.10, not 10.04.

This post begins with a basic Ubuntu setup already installed.  That basic installation process was very straightforward; but for those unfamiliar with Ubuntu, there were many webpages on how to install Ubuntu 10.10.  The question addressed in this post was, what additional steps did I need to take, in order to make Ubuntu look and act the way I wanted?  Of course, people will have various preferences.  This post does not go into that kind of individual detail.  It is more a matter of how to go about choosing and preserving one's desired setup.

In this case, I had installed Ubuntu 10.10 in a two-drive RAID0 setup.  I have written a separate post on that as well.  It looked and acted the same as a normal single-drive Ubuntu installation.  But the following discussion contains a few references to the setup described in that other post, for those who have come to this description from there.

The Home Partition

If I had been installing Ubuntu without using RAID, I probably would have decided, in the initial installation, to install everything in a single root ("/") partition.  But the RAID process had required the creation of a separate /boot partition, so I now had those two partitions instead of one.  Either way, though, my installation did not yet include a separate /home partition.  I did want a separate /home partition to be part of the mix, because /home was where all kinds of program settings were preserved.

I had retained a copy of my previous /home partition.  It was on a third hard drive.  That is, it was not part of the RAID array, and I did not plan to copy it into the RAID array.  RAID 0 is risky, in the sense that failure of any drive in the array means the end of the entire array and everything on it.  So I was just going to leave the /home partition on that separate drive, and back it up from there.  The question was, how should I get the new installation to recognize that separate /home partition?  I had struggled with this step previously, but now I wanted to write it up in simpler form.

On that third drive, I had a folder called Saved Settings.  In that folder, I had kept a copy of my old fstab (that is, the file called "fstab," from the /etc folder, viewable by typing "sudo gedit /etc/fstab").  I added lines from that copy into my current fstab, making sure that its lines referred to UUIDs (available via "sudo blkid") rather than to drive letters (e.g., sda, sdb), so that the commands in the fstab would still function if I rearranged partitions in my computer.  I also made sure it had a line referring to the correct UUID for the /home partition.  I saved and closed fstab.

To give /home a place to be mounted, I typed "sudo mkdir /media/home."  To prevent the newly installed (and nearly empty) /home partition from interfering with the selection and use of my preferred, preexisting /home partition, I typed "sudo mv /home /old_home."  I had meanwhile allowed Update Manager to install updates, and that process was done, so at this point I rebooted.  I got an error message, "Could not update ICEauthority file /home/ray/.ICEauthority."  I clicked through that, and after a moment my old, preferred desktop layout was there and seemed to be functioning normally.  (I worked through the ICEauthority problem as described in a separate post.  Basically, the solution was to make sure the user (i.e., ray, not root) had ownership of the home folder.)  The last step was to delete the temporary old_home folder I had created by typing "sudo rm -r /old_home."

Repositories

Having the home folder in place meant that about 90% of the work of installing and configuring programs was already done and saved.  This was one huge advantage over Windows XP installations, where the only programs that did not have to be reinstalled in the event of a new operating system installation were portable applications.  This section describes the relatively few steps that I did have to take to install applications and configure my Ubuntu system, as compared to the writeup in a separate post on Windows XP reinstallation.

I could not rely on my previously saved sources.list file to set up my repositories, since I was now dealing with a new version of Ubuntu.  Instead, I went into System > Administration and discovered that, unlike Ubuntu 10.04 (as discussed in a separate post), Ubuntu 10.10 no longer had a Software Sources option.  A search revealed that this change was made to make Ubuntu more user-friendly.  I could either edit the menu to add back the Software Sources option or use System > Administration > Synaptic Package Manager as an alternative.  Choosing the latter, I went into Synaptic's Settings > Repositories > Other Software and selected the non-source options.  In the Authentication tab, I saw a list of Trusted Software Providers, and the names on it were Ubuntu (archive, CD image, and extras), GetDeb, and Google.  I had no problem with any of these except maybe Ubuntu extras.  I wasn't sure if these had come from my previous installation or were pre-supplied with Ubuntu 10.10.  I could have hit "Restore Defaults" to find out, but then I would have had to figure out how to restore them.  I closed out of that and, back in Synaptic, clicked Reload.

In Terminal, I typed "sudo gedit /etc/apt/sources.list."  I saw that it contained a handful of repositories.  I wondered if there were others I should include, so I went to the Ubuntu Sources List Generator and got a list that was more concise and that also included a few third-party repos of interest (i.e., GetDeb, Google, Medibuntu, Wine, and X Updates).  I ran the commands in the "Getting the GPG Keys" list from the bottom of the page, one at a time.  In previous installations, I had saved such commands in a text file and had executed it, but that had made it easier to overlook error messages.  In this case, the Medibuntu command gave me "Unable to locate package medibuntu-keyring."  A search indicated that virtually nobody had gotten precisely that message.  Not a good sign.  A community documentation page gave me a different command to add Medibuntu:

sudo wget --output-document=/etc/apt/sources.list.d/medibuntu.list http://www.medibuntu.org/sources.list.d/$(lsb_release -cs).list && sudo apt-get --quiet update && sudo apt-get --yes --quiet --allow-unauthenticated install medibuntu-keyring && sudo apt-get --quiet update

... all on one line!  It also said that Medibuntu's repository is deactivated whenever you upgrade to a newer Ubuntu release, so this reinstallation would have to happen each time.  I copied and pasted that command and ran it.  It gave me an error message:

Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

to which the answer was yes, of course, Synaptic is still running.  I shut down Synaptic and tried again.  This time, it ran.  I took another look at the Authentication tab in Synaptic (see above), and now Medibuntu was on the list of trusted software providers.  So the answer to my question was, this was my customized list.

I went back to the process of running commands generated by the Ubuntu Sources List Generator.  They ran without further difficulty.  I typed "sudo gedit /etc/apt/sources.list" again, and replaced its contents with the lines generated by that Generator.  I took another look at Synaptic's Authentication tab, and this produced an error indicating that I had duplicate entries for Medibuntu and, I think, something else.  But when I tried to figure out what that was about, the error went away, and I didn't seem to be able to get it back.  Anyway, the Authentication tab did show that I now had the five third-party repos that had interested me (above), so all that remained was to go into System > Administration > Update Manager > Check and download the additional updates that it detected.

Installing Programs & Other Adjustments

In Terminal, I navigated to my Saved Settings folder (basically, cd "/folder name/" -- using quotes because "folder name" has a space in it) and verified that I had a copy of the installed-software file that I had created, in my previous installation, by typing "dpkg --get-selections > installed-software."  Now that I wanted to restore the programs listed in installed-software, I entered these commands:

sudo dpkg --set-selections < installed-software
sudo apt-get install dselect
sudo dselect

That opened up dselect.  The dpkg command had provided the list of what I wanted to install, so all I had to do now, in dselect, was to arrow down and hit Enter at the Install option.  This gave me an option of installing a large quantity of stuff, and I said OK, do it.  That took an hour.  At the end, I declined to let it erase previously downloaded .deb files, when it asked.  The last time I used this installed-software approach, I got a bunch of errors after reboot, and had to work back through the process manually.  There were some errors this time, too (see below), but they did not appear to be related to the dselect process.

As before, I navigated to the folders containing other program downloads (with .deb, .gz, .bin, and .bundle extensions).  I typed "sudo sh [filename]" to install my .bin and .bundle downloads (e.g., GoogleEarthLinux.bin).  Double-clicking on the filename in Nautilus no longer installed my .deb downloads; instead, I had to right-click and choose "Open with GDebi Package Installer."  In the case of my Synology software, I typed "sudo sh install.sh."  I wasn't sure where to install it, so I told it to install in /home, just in case that would spare me from having to install it again.  But I should have said /home/ray.  When I was done with all installations, I went into Update Manager, and ran and reran it until I was all caught up.

GRUB2 menu edits were the same as before:  to get rid of the Memtest+ options, I typed "sudo chmod -x /etc/grub.d/20_memtest86+." To let Ubuntu remember which operating system it had used last, I typed "sudo gedit /etc/default/grub," changed the first line to be "GRUB_DEFAULT=saved," and added a second line that said "GRUB_SAVEDEFAULT=true."  To limit the number of Ubuntu kernels shown, I typed "sudo gedit /etc/grub.d/10_linux," added "GRUB_DISABLE_LINUX_RECOVERY=true" at the top, and changed two lines at the bottom to be three that read as follows:

list=`echo $list | tr ' ' '\n' | grep -vx $linux | tr '\n' ' '`
list=`version_find_latest $list`
done

I saved and closed that and typed "sudo update-grub."

I also needed to make some adjustments for VMware.  First, I typed "sudo vmware" and made some root adjustments there.  As before, I typed "sudo gedit [path][filename].vmx," for the .vmx file pertaining to this VM; and at the end of that file I added a line that said this:

bios.bootDelay = "10000"

and that bought me ten seconds instead of one or two, when that vmware logo came up.  In a variation from Ubuntu 10.04, the restricted drivers for my monitor were now at System > Administration > Additional Drivers.

Bugs and Other Problems

There were some problems.  First, BOINC would not suspend itself when the system was in use, so I just suspended it, period.  Also, as discussed in a separate post, there were some Firefox errors.  The solution there was to completely uninstall and reinstall Firefox, though possibly it would have been sufficient just to uninstall firefox-gnome-support and delete my profile.

Another problem was that Ubuntu was not clearly recognizing all local and network partitions.  The problem of mapping the drive in my Synology NAS required another separate post.  In that case, it came down to a problem with the line used to mount the drive in fstab.  It had seemed like there were other drive recognition problems, but evidently they sorted themselves out, or perhaps I was just mistaken.  At this point, the drives seemed to be recognized in good form.

There was also the problem that GParted wouldn't run.  It wasn't just in my installation; it wasn't running when I booted from the live CD either.  I guessed that this was some kind of brand-new bug in Ubuntu 10.10 that would be fixed shortly.  When I started GParted from System > Administration, it would start up, but then it would disappear after just a few seconds.  When I typed "sudo gparted" or "gksu gparted," it did the same thing, but it gave me an error message:

glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: basicI_string::_S_create
aborting...

A search indicated that this was indeed a bug in Ubuntu.  It looked like a new release would be fixing the problem imminently.  Another problem:  Google Earth would not install.  I got this error message:

parser error : Document is empty
parser error: Start tag expected, '<' not found
Couldn't load 'setup.data/setup.xml'

The command I used was "sudo sh GoogleEarthLinux.bin."  The first response to it was "Verifying archive integrity... All good."  Just in case, I downloaded a replacement of GoogleEarthLinux.bin, but got the same result.  It looked like others had also had this problem.  It seemed to be another instance of Ubuntu 10.10 not yet having all the kinks worked out.  I started with a lengthy thread on the issue.  One post in that thread recommended a command-line alternative, which in full form went like this:

sudo apt-get install googleearth-package
sudo make-googleearth-package --force
sudo dpkg -i googleearth_5.2.1.1588+0.5.7-1_i386.deb

I tried that.  The make-googleearth-package command generated a lot of errors that included the sentence, "Can't extract name and version from library name."  I got that long package name shown in the last line (googleearth_5.2.1 etc.) from one of the last lines produced by the make-googleearth-package command:  it said this was the name of the package it was building.  (It also seemed to say that simply "googleearth" was the name of the package, but that didn't work.)  The third command (sudo dpkg etc.) seemed to run successfully.  There was also now a Google Earth icon in Applications > Internet > Google Earth.  I clicked on that, and it worked.

Another problem involved VMCI Sockets.  I have addressed that one in a separate post.  I ran out of time to continue this project at the time.  When I returned to it two months later, I had decided to stop trying to maintain a primarily Ubuntu machine, but instead to return to Windows 7 for the foreseeable future.