This is how to resolve the following error I encountered while upgrading Fedora 16 (EOL) to Fedora 17 using yum: Loading Fedora (3.8.12-100.fc17.i686) Kernel panic – not syncing: VFS: Unable to mount root fs on unknown block(0,0) Pid: 1, comm: swapper/0 Not tained 3.8.12-100.fc17.i686 #1 The error and resolution are nearly identical to the Kernel…
This is how I solved a problem of Microsoft Outlook 2010 “Trying to Connect” for several days.
Encrypting the Microsoft Windows temporary folder causes Microsoft Outlook 2010 to not open Word file attachments because of these “cryptic” errors: Word could not create the work file. Check the temp environment variable The file (filename) cannot be opened because there are problems with the contents. Unspecified error Location: Part: /word/document.xml, Line:2, Column:0 Run this…
Some R code designed for ggplot2 0.8.9 is not compatible with ggplot2 0.9.0, and today the ggplot2 web site has outdated documentation which gives this broken example: Dennis Murphy points to the ggplot2 0.9.0 transition guide from where I derived a solution: The transition guide has more details about transformations such as log, log10, sqrt,…
If you do parallel processing in R on Windows, then you probably have heard of the doSMP package. However, it was recently removed from the CRAN repository with the terse message: Package ‘doSMP’ was removed from the CRAN repository. Revolution Analytics develops the doSMP package and promptly sent me this explanation: The doSMP package relies…
There are multiple causes for the error Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block(0,0), but this is how I caused and later fixed my hosed system. Also I will explain the related issues. UPDATE (May 2013): Kernel panic – not syncing: VFS: Unable to mount root fs on unknown…
This error occurred while installing WinPcap, which comes bundled with Wireshark (a network protocol analyzer): Error WinPcap 4.1.2 Setup An error occurred while installing the NPF driver (0x00000430). Please contact the WinPcap Team including the file C:\Program Files\WinPcap\install.log. The installation will now continue anyway The older WinPcap 4.0.1 produces a similar error: An error occurred…
