Image of Modern Operating Systems (3rd Edition)
Image of Beginning Google Maps API 3
Image of Linux Kernel Development (3rd Edition)
Image of Android Wireless Application Development

UEFI-based Windows 10 Platform - Failure to Boot Due to Missing or Corrupt BCD

I was prompted to write this post as a result of Windows 10 Professional recently attempting to do a silent update while I was waiting in an airport which I unknowingly interrupted when I powered down my UEFI-based laptop prior to boarding the plane. When I later powered on the laptop, it failed to boot and simply displayed the following message: A Boot Configuration Data (BCD) store (there can be more than one) contains boot configuration parameters which control how the operating system is started in Windows 10. First introduced in Windows Vista, these parameters were previously stored in the

Vista VMware Network Connections

When I am traveling, I often use VMware workstation on my Windows Vista Ultimate laptop to host both Redhat and Ubuntu VMs. One thing that irritates me about this arrangement is that whenever I reconfigure networking in VMware, Windows Vista shows these networking interfaces are part of a unidentified network with limited access. For example, when you right click on the networking icon, the following networks are displayed. Network is my regular wireless or hard-wired LAN connection to my router and from there to the Internet. The unidentified network, marked limited connectivity, are two VMware virtual network adapters. Here is

PowerShell CTP3

There was an early Christmas present from the Windows PowerShell (AKA PoSH) Team.  The Community Technology Preview 3 (CTP3) of Windows PowerShell v2.0 was released on December 23rd just in time for Christmas.  The announcement is here.  As expected CTP3 builds on the new technology provided in CTP2 which was released in May 2008.  You can download CTP3 from the Microsoft Download Center. Hemant Mahawar, Program Manager for PowerShell, summarized the CTP3 release as follows: This release brings, among other things, performance improvements … things will be faster/more efficient than before. PowerShell remoting now allows implicit remoting where command execution appears to be local

More on PowerShell

Microsoft’s PowerShell is radically different than shells on UNIX or GNU Linux systems in that Powershell can deal in objects rather than just plain text. A concrete example may help you more quickly understand the difference.  Suppose you want to get and save information about all the files in a certain subdirectory.   We want to get not only the names of the files but as much metadata as possible relating to each file such as date of creation, date of modification, etc.  This information also needs to be stored in a single XML document.  To keep the size of this post manageable,

PowerShell Grows Up

I am excited about the emminent release of Microsoft Windows Powershell Version 2 CTP3 (Community Technology Preview Version 3) which is due “real soon now.”   The first CTP for Powershell 2.0 was in November 2007 and there has been a lot of progress on the product since then.  See the permanant link at the side of my blog to access the Powershell developers blog. Why am I, a UNIX/Linux developer, excited by Powershell V2?  After all it does not run on any UNIX or GNU Linux platform and microsoft has no plans to port itMto these platforms.  The main reason is that Powershell