9/12/08

Parallels (17 months later)

Parallels LogoI'm one of the Mac supporters at work. Recently, I was assigned the task of reloading a MacBook Pro (2.16 Ghz, 2 GB RAM) with OS X Leopard and Boot-Camping with Vista SP1 and using Parallels to have access to the Boot Camp partition.

Things were going well (aside from a few slow downs due to shipping issues). Until I started working with Windows Vista in Parallels.

After I got all my software installed, including items such as Adobe Photoshop and Microsoft Office, I started my testing of the software in Parallels. This didn't turn out so well. I fired up a few Adobe applications, such as Photoshop and ImageReady. Along with IE (7 of course, per Vista's requirements) and Microsoft Office. The only problem that I found was that the system was unable to run Photoshop. Granted, we were running the Parallels Virtual Machine hardware, so I can't really blame either Parallels or Adobe for the problems I was having. --Where I can blame Parallels is for the system being unable to free up memory and being unable to shut down afterward.


Once I was done testing, I was getting ready to gather up a few things and return the laptop to the Director that assigned me the task of getting the computer configured.

All I had to do was shut Parallels down, and test the system one more time in Windows Vista under Boot Camp. This is where my problems began...

Parallels just wouldn't shut down. The system got far enough in the shutdown process that I was unable to bring up task manager. After waiting for over half an hour to shut the system down, I finally gave up and clicked on the Parallels "Stop" button, which informed me that it was possible that I would lose data if I agreed to the improper shutdown. Since I had waited for so long, I did agree, and the unit powered off. I tried to turn it back on, and guess what happened....

The system was unable to boot. It would "blue screen" at boot. It was really quite frustrating. So I booted into Boot Camp, and loaded the system in safe mode (regular mode also wasn't working for Boot Camp). I found the .SYS file that wasn't working correctly, one of the Parallel Tools system files, I moved the file, and restarted the computer. I didn't notice any other major problems, so I called it "Stable" and moved on to restart the computer into Mac OS X Leopard for Parallels testing.

Upon starting Parallels, I didn't seem to have too many problems. I had to reactivate, but that was a problem that Parallels clearly documented as a known issue with Parallels software. Strange that it would come up now, after the previous problems I had with the system, but not quite unexpected. And, after activating Vista, the system did boot normally. I tested the software, and found everything to be operational. So I called it "Stable" and shut the Parallels virtual machine down. I then rebooted the computer, to load up Boot Camp to be sure that the system was still stable on that side.

I was quite surprised to find out that Windows, on the Boot Camp side, needed to be activated. I thought it was strange, but once again, this issue was documented by Parallels. So I reactivated Windows. Things were working just fine. I was able to access all of the programs and all of the drivers seemed to have installed correctly. I called it "Stable" and decided to reboot into Leopard to test Parallels (post Boot Camp side activation) to see how it held up).

Boot Camp started normally, but it needed activation. Once it was activated, it worked swimmingly. I found no major problems, aside from the fact that Photoshop wouldn't start up. No big deal, since most of the graphic design would be done from within the Boot Camp partition.

For certainty, I decided to reboot the PC into Boot Camp to see how the install of Vista came though. Unfortunately, it didn't turn out so well --once again, it needed activation. I went around with Boot Camp and Parallels for nearly three hours, trying to figure out what was causing the system to deactivate itself. The only thing that I could conclude was that the .SYS file that I moved was the source of the problem. Unfortunately, since the system was being so stable without that file, I decided to actually delete the file, and reinstalling the Parallels System Tools did not seem to help my problems at all.

My options, that were once limited, now seemed to be down to one: reinstall Windows and see what happens.

I did just that. The system was behind schedule by two days now, but it was coming along well enough. I was able to get the operating system and the software configured and tested within a few hours. I found no obvious problems. So I called the Director, and informed him that the PC was ready for pick up. I went though a tutorial on how to use some of the features of Parallels and reiterated the limitations (and apparent sensitivity of the software). I didn't want him to be out of the state and have the system crash on him.
* * *

Blue Screen of DeathThe following Monday, I received an email stating that the system wasn't able to boot into Boot Camp or Parallels - it was blue screening at boot. Mac OS was working fine though.

I made it into work early that day and immediately took to working on the MacBook Pro. I met up with the Director, he explained that he was finally able to get the Mac to boot into Windows after following instructions he was able to dig up with extensive digging though the internet, but found that the Parallels Tools, which he no longer trusted (since it was the cause of the blue screening issues) was unable to be uninstalled unless it was running from within Parallels - which he uninstalled from Mac OS (I would have done the same).

Unfortunately, the only option I could figure out, was to reinstall and reconfigure the Parallels software and uninstall the tools from within Parallels, and hope for the best.

The first attempt didn't work so well. The cursor turned into it's new version of the hour glass and was just "clocking" as we waited for the control panel to load up. After waiting for a decent bit of time, Windows returned that Explorer.exe had failed. We had to power down Parallels from the Parallels Stop button. Luckily, upon rebooting it, we were able to get the system into Parallels and we were able to remove the software without problem.

* * *

Well, the happiness and joy of a job well done didn't last long. It was only a few hours later that the Director contacted me to let me know that the drivers for the audio in Windows died out, he was in a desperate state to get the system up and running as soon as possible or he would miss a plane shortly there after. I did a quick check of the system, but I was unable to find a cause for the hardware problems. The system kept reporting that there was no audio devices installed. It was also reporting that all the drivers of the system were installed, just that there was no audio devices installed in the MacBook Pro.

The director eventually had to switch to using a regular Windows based laptop to take with him out of state, but he wanted to take the MacBook Pro with him to tinker with it to see if he could get it back up and running.

A few days later, he contacted me to let me know that he wants to try reloading Windows Vista to see if that will rectify the issues. This time, Parallels will be a "no-go for launch."

9/8/08

42 Years of Star Trek

United Federation of Planets (logo)42 Years of Going Boldly Where No One Has Gone Before.

I do have to disclaim that Star Trek is one of the biggest reasons that I got into Technology. This show has inspired so many people in so many ways. It has not only driven a new generation of scientists and space enthusiasts, but also helped mold a population of people more willing to accept one another and to venture outside of their comfort zone, to do something different - to boldly go where they haven't been before.

It's unfortunate that this anniversary comes upon the heals of The Star Trek Experience closing (last Monday, 1 September 2008).

Happy Anniversary Star Trek.

9/5/08

If it aint broke, don't fix it...

Such simple words for such an important statement.

Managing the Firefox executable in Linux (my install of SuSE 9.3, I should say) is fairly simple. One just opens up File Manager as root, and then navigates to /opt/MozillaFirefox/lib/ and copies lib for a backup (I leave the backup in the same directory, but name it with the Firefox software version at the end, such as lib2.0.0.16). This works fairly well. Step one done: a backup of the current version of Firefox has been made.

Next, take the new Firefox tar.gz file, decompress it. I keep mine in /home/user/daniel/My Downloads/*latest version of Firefox*/, so I went to /home/user/daniel/My Downloads/firefox-3.0.1/ (still in super-user mode in my file explorer) and opened up the one folder in there, "firefox" - so very simple and benign. Things were looking good.

Inside "firefox" is the core application of firefox and firefox-bin and all it's core "Firefox centric" files, like chrome and whatnot. Do a "select all" and then copy all the files.

Continuing on, (once again, still in super-user mode in my file explorer), and paste the contents of the folder firefox into /opt/MozillaFirefox/lib/ and permit an over-write of the files in there. It'll over write of the files that need to be updated, while maintaining anything special that one already has in there.

Update of MozillaFirefox is now done.

Note: This is more complicated than the Windows version of this update, and far more difficult than the very simple Mac version of updating software. However, backing up ones installation of Firefox is much simpler in Linux than in Windows. It is about the same to backup ones programs in Mac OS though

Now, just click on your usual Firefox icon and the browser starts.
~or, at least that is the theory.

* * *

One may get: nothing at all.

I thought, "Perhaps I didn't click it..." - so I clicked it again. No dice.

~sigh, it must be some strange error. I fired up Konsole and navigated to /opt/MozillaFirefox/lib/ and executed firefox, which returned:
daniel@Suzi-lnx:/opt/MozillaFirefox/lib> ./firefox
./firefox-bin: error while loading shared libraries: libpangocairo-1.0.so.0: cannot open shared object file: No such file or directory


All I could think was " f r e l l . " (see references in the American Sci-Fi show Farscape) I was looking down the long slope to dependency hell, which has been known to on many occasions to cause serious over-hauls of the system's software, and on some rare major cases, reinstallation of the OS itself. I wasn't about to go down that route unless I was really aware of what I was doing, that meant research time.

Since I didn't have an operational Firefox, I chose to use Opera to google up some results, I chose to use firefox 3 suse 9 error while loading shared libraries: libpangocairo-1.0.so.0: cannot open shared object file as my search "tearm" (if one can call such a long string like that a "term") and found some results. The first result was pretty spot on, ./firefox-bin: error while loading shared libraries: libpangocairo-1.0.so.0: cannot open shared object file: No such file or directory at the Firefox Support Forum. Page 2 [.link] is even more useful. This second page informed me that there was a work around for this issue on good 'ol mozillaZine (my most trusted site for Mozilla application troubleshooting). The article I was told to look up is Firefox 3 on CentOS 4?

The results were pretty poor however. Install Firefox 3 though a package manager. Upgrade your pango libraries by hand. Use wine and run the Windows version of Firefox instead. Upgrade your OS - maybe it'll have Firefox 3 preinstalled.

The worst line: "It's probably not recommended, but here's one way."

Even though the post moderator has the best intentions, I find it hard to go to such extremes.

I think for now, I'm going to let FF 3 in Windows and Mac OS, and I'll work on upgrading it after work-arounds for this pango issue become well documented.

For those of you who are in need of the link to the old Firefox software releases, see Mozilla Firefox 2: Download Firefox 2.

9/4/08

Help - Help is not avaliable in this version of Windows!!!

Today at work, I was tinkering with a Vista computer (trying to pin down what can be done about it's excessive RAM utilization), and upon closing all of the open Windows on the computer, I found this notice behind everything.

I loved the wording of the message. "Windows Help Program is no longer included with Windows." - Strategically worded so they don't say "Help isn't included with Windows anymore... we gave up on "helping" with this version of Windows."

* * *

Why couldn't this be phased out anyway? I've even got help file viewers on Linux and Mac OS X computers, it seems a little odd that Microsoft would just stop including it with Windows. What I would have done is include the old help viewer, but start writing all the new help documentation in the new format. Maybe with the next version of Windows, include the old help viewer as an optional addition, but not have it installed by default.

At least Microsoft does include it as a download from their website [.link] - however, there is a total of 6 pages of documentation, over half of which is "known issues after installing WinHlp32.exe" - sigh.

Well, that's my two-cents anyway.

9/1/08

Firefox 3.0.1 (Mac OS X version) Preliminary

This afternoon, I finally decided to start some testing of Firefox 3, I've been putting it off for ages now, and with the frequent notices by Firefox about how version 3.0.1 is available (as well as the fact that the Firefox people have made it to version 3.0.1 already) I decided to give it a shot.

The way I work with new releases like this, I start by using the Mac OS X version of the software, where backing up old programs and demoing new versions is so much easier than in Windows (and lets not even talk about how hard that is to do in Linux), but I found something interesting while using the browser in Mac OS X 10.4.11: the menu bar repeats itself. On Mac, you should see something that looks like this:

[click the image below to see a full-sized version]

But, what I'm seeing with Firefox 3.0.1 is a bit different than usual Apple interface standards:

[click the image below to see a full-sized version]

The items seem to "slide" -- sometimes, the "Firefox" item is the furthest to the left, other times, "Help" or "Window" or "File" will be furthest to the left.

Presently, closing and reopening the browser has not helped the software out. I'll keep tinkering with the software, perhaps Firefox 3.0.1 isn't quite ready for Mac OS X 10.4.11 yet. I'll keep running it for now, and maybe I'll find something out there on the MozillaZine that will help out.

[update]
Since restarting the MacBook, Firefox has worked just fine. It seems restarting the software several times was not the root cause of the issue... Something must have been running resident in memory that needed to be cleared out before the menu bar would work correctly.

Still a strange error, one that I've never encountered before in the many years that I've been running Mac OS (from System Software 7 to OS X 10.5).

NewEgg's DVD store no more?

I was looking up prices on "China's First Emperor" that aired on the History Channel, it's around $35 USD + Shipping and Handing from History.com [.link]

I was hoping that I'd be able to find a better price, and not seeing the DVD listed at Amazon.com, I decided to proceed to the NewEgg DVD store - I didn't think that I'd be able to find it there, but if I did, I figured it would be at a better price.

But when I loaded up NewEgg.com, I could not find any references to the DVD store. I even did a NewEgg.com search for "Movies" and "DVD" -- nothing turned up but blank media, DVD burners, etc. So, in a last ditch effort, I did a google search for "NewEgg DVD store" which found the NewEgg DVD store [.link].

The page looked oddly blank, but it did not display an error or reference the store being closed - it is even titled as having "Blu-Ray DVD & HD DVD" movies, making me believe that it had to have recently been accessible. So I ran a search for "China's first emperor" - which returned no results. Searching for "Anime" also returned no results, and searching for "DVD" returned the same results that searching for "DVD" at the NewEgg main page did.

I can only conclude that the DVD store is gone. :( I always found good prices at the NewEgg DVD store, but I never got the change to order anything from there, I hardly ever order DVDs (I prefer to buy them at a local FYE). I guess it'll be back to FYE and Amazon's DVD store for me.