20 September 2016

BitLocker Orange Screen with White Vertical Lines

That's not right

I powered up my work machine after three weeks and was greeted with an orange screen with white vertical lines in place of the expected screen asking for a password.  Flip - that's not right, perhaps the machine crashed during an update.  Oh well, I will just reboot and everything will be fine - after all it is a Microsoft box.

But the reboot didn't rectify matters and neither did a cold boot with the power removed for thirty seconds.  Time to Google the matter on my phone.  Wow, in contrast with fixing computers twenty years ago the combination of the readily available information on the Internet and the access to another computer has transformed the effort needed to resolve an issue on another machine into a simple affair.  The 'solution' I was glad to learn was that the machine was still waiting for my encryption password under that garish orange veneer and by entering it and pressing Enter the machine would continue to boot as normal.  I was relieved to read this and indeed my machine booted to Windows shortly after.

The next day, today, this didn't approach didn't appear to work and I arrived at the BitLocker Recovery Key screen.  The link shown on-screen: http://windows.microsoft.com/recoverykeyfaq, was of little help so I reboot the machine and entered my password again, but more slowly this time.  The machine booted into Windows, but could very quickly become a hassle and a security risk if I need to remotely guide someone else to use my PC.

More Googling and several sites later I found this working solution which described that the boot font had been corrupted - I wonder what else has been corrupted? - and that reverting from the pretty Windows 8 BitLocker font to the simple text based Windows 7 version would produce a more useable interface.

The command to executed in a CMD window with Admin privileges is:
bcdedit /set {default} bootmenupolicy legacy
and to revert back to the, potentially corrupted, pretty screen (change "legacy" to "standard").

The solution was provided by Sholtz and this is the forum thread on TechNet.  Thank you Sholtz.

12 November 2012

Touching Two Continents

Hi all,

November started with my PhD viva - the defense of my previous few years of research.  The cross examination undertaken by experts in the field concealed threat detection was successful and pending correction of some typos, I gain the title of Doctor.

11 September 2012

Handed In


Long time, no post.  I've now finished and submitted my thesis.  It's difficult to describe the relief and the euphoria of that weight lifting from my shoulders!  I'm looking to the many tasks I've put on hold pending my submission, that I expect I'll be even busier than before, but at least I won't be writing.  Yes, I have to defend my work in cross examination, but I know my stuff and an that in comparison to writing up should be a doddle and hope to only get minor corrections.

I'll try and not repeat my extended break from posting - I could have posted what I've been researching, but it's sufficiently off topic from my adventures into 3D printing (or not) with the SumPod, as to be irrelevant.

I see Mr Sum, has been busy with some notable changes in the design.
Take care all.
SumPod Guinea Pig

16 February 2012


I received a surprise parcel on Saturday from Mr Sum, just one day after he sent it. The postal service obviously doesn't loose all of his parcels it seems, they must be losing their touch.  The parcel contained most of the missing parts for my SumPod and an incomplete hotend v2.  It would be so much easier to tell with a picklist what parts are missing - at least at Ikea you know what you're supposed to have and tell what's missing (and the customer service is a lot better too).

Over the weekend I built the supplied parts into my SumPod and loaded the SumPod Sprinter firmware.  After double checking connections, I excitedly powered up the SumPod to test the three axis of motion and experienced a sinking feeling, not the light-headed, vomit inducing miss-typed dd or clicking hard drive variety, thank goodness, just a 'frustrated this should work, here we go again' feeling in anticipation of the inevitable fault finding.  The stepper motors were 'spazzing' (a well known technical term) and would turn when a finger was prodded onto pins of the Pololu driver - a fault finding technique I recommend (after discharging any static) to indicate floating pins with a little capacitive coupling.  I was concerned the Pololu drivers had been damaged having missed the tell tale 'magic smoke' while reassembling the electronics and connecting it to the SumPod.  Had rousing them from an extended slumber damaged them?  Who knows, they had been in a box on a shelf since mid October...