Windows takes a breather in London's Spitalfields
No, not that sort of Rust
12BoC The Register's Bork column is coming to an end, and to mark the occasion we present the 12 Bork's of Christmas. Today: an unwanted appearance by the Windows command line.
No PowerShell for this administrator, oh no. Whoever is behind this screen (spotted by Register reader Sam Owens) has fired up
cmd.exe, probably via a script or batch file, and piped the output somewhere passers-by can admire it.
timeout and why three seconds?
timeout is usually used to pause the command processor for a few seconds (although a user could strike a key to skip it, if only a keyboard was attached). As for the why – maybe a wait for a connection or a network host to respond?
Or as Owens observed: "Maybe the board is getting [ready] for the grand wfh on Monday!" – this one being snapped earlier this month as the UK Prime Minister issued guidance that working from home would probably be a good idea to counter the Omicron variant.
While we can't comment on the ins and outs of yet another COVID-induced timeout for the country, it appears the deliberately rusted Spitalfields signage is getting itself ready for a period of inaction.
The sign doubles as a Wi-Fi access point as well as advertising. Well it would do if it wasn't for the hulking box of Windows
cmd.exe obscuring the view.
Still, it is somehow appropriate that a rusty metal box be used to house Microsoft's finest. Far be it from us to wonder how far that corrosion has spread through the operating system, and what patches have had to be hurriedly welded in place to stop the whole thing falling apart.
Instead, let's take an administrator's scripting whoopsie as a metaphor for the last couple of years. Waiting 3 seconds? If only... ®
A little ditty we are calling: The 12 Borks of Christmas '21
♬ On the fourth day of Borkmas, the bork gods sent to me:
a playful scripting stuffup;