Tag Archive for BSOD

Why CTRL + ALT + DELETE

Why CTRL + ALT + DELETEEvery PC user has given their computer the three-finger salute as it locked up – frequently at the most inopportune time. But why CTRL + ALT + DELETE? Turns out the three-finger salute was a 10-minute hack to make programmers life easier. The CTRL + ALT + DELETE was born at IBM (IBM) in the early 1980s.

IBM PCProject Acorn was the code name for the rush project to build IBM’s new personal computer – because Apple (AAPL) and RadioShack were already selling small stand-alone computers. David Bradley was part of the team working from the IBM offices in Boca Raton, FL on the IBM PC.

Mental Floss reports that the programmers’ working on the IBM PC had to manually restart the entire system whenever the computer encountered a coding glitch. This was a waste of time. Mr. Bradley told Mental Floss,  “Some days, you’d be rebooting every five minutes as you searched for the problem … The tedious tests made the coders want to pull their hair out.

IBM logoMr. Bradley worked on everything from writing input/output programs to troubleshooting wire-wrap boards on Project Acorn. In order to placate the programmers, Mr. Bradley created a hack. His hack was a keyboard shortcut that triggered a system reset without memory tests.

To Mr. Bradley CTRL + ALT + DELETE, was just another item to tick off his to-do list. He says. “It was five minutes, 10 minutes of activity, and then I moved on to the next of the 100 things that needed to get done.

The engineer chose the keys by location—with the DEL key across the keyboard from the other two, it seemed unlikely that all three would be accidentally pressed at the same time. Mr. Bradley never intended to make the shortcut available to customers, nor did he expect it to become a cultural icon. It was meant for his fellow coders, for whom every second counted.

Thank IBM for CTRL + ALT + DELETE

The IBM team managed to finish Acorn on schedule. In the fall of 1981, the IBM PC hit the market. It was a dull gray box beneath a green screen monitor. Marketers predicted that the company would sell less than 50,000 units a year. IBM execs thought that estimate was too optimistic. They were all wrong. Computing would never be the same.

Statista Percent of US households with a computer 1984 - 2016

As PC sales took off – few users were aware of Mr. Bradley’s shortcut hidden in their machines. That changed in the early 1990s when Microsoft’s (MSFT) Windows 3 took off. Now Microsoft’s Windows PCs were crashing and the infamous “blue screen of death” plagued Windows users. A quick fix to the BSOD spread by word of mouth (this was before the WWW) – CTRL + ALT + DELETE. Suddenly, Mr. Bradley’s quick hack was a big deal.

At an event celebrating the 20th anniversary of the IBM PC industry big-wigs gathered for a panel discussion. Mental Floss says that the first question to the panel bypassed Microsoft chairman Bill Gates and was for David Bradley. Mr. Bradley, who has always been surprised by how popular his CTRL + ALT + DELETE hack made him, was quick to deflect the glory. The programmer joked;

I have to share the credit, I may have invented it, but I think Bill made it famous.

rb-

Bill Gates has publicly admitted that CTRL + ALT + DELETE was a mistake – but the company he founded continues to use Mr. Bradley’s hack. In Windows 10  the keyboard combination starts Windows Security, which lets you lock the computer, switch to a different user, log off, start Task Manager, or shut down/reboot the computer.

Stay safe out there!

Related article

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

Son of Facebook Phone

Son of Facebook PhoneThe tech world never learns from its mistakes. Rumors are that data-leaker Facebook is combining two bad ideas, software from Windows NT with FB hardware. The Verge reports that Facebook is developing its own operating system. Facebook’s effort is being led by Mark Lucovsky, who co-authored the Windows NT operating system.

Could the FB OS be the greatest thing since?The reports say the FB OS could be used on Facebook’s hardware products. Oculus, Portal, and forthcoming augmented reality glasses, code-named “Orion,” currently run on a modified version of Google’s Android. FB wants to reduce or remove entirely the control GOOG has over its hardware.

Ficus Kirkpatrick, who heads Facebook’s AR and VR group hedges his bets, he told The Verge “it’s possible” that future FB hardware won’t rely on Google’s software. Facebook’s head of hardware, Andrew Bosworth is more definitive, “… we’re gonna do it ourselves.

Facebook phone crashed and burned almost immediately.The Verge points out that Facebook’s last attempt at producing its own OS did not go so well. The Facebook phone, or, more precisely, the Facebook phone mobile operating system, crashed and burned almost immediately. Unveiled in 2013, Mark Zuckerberg promised the $99 device would “turn your Android phone into a great social device.

It didn’t exactly work out that way. Instead, shortly after the Facebook phone went on sale, the price dropped to 99 cents. The operating system was called out as mediocre, and early adopters complained that it was counter-intuitive and hard to — of all things — place a phone call. By 2014, the New York Times reported that Facebook had disbanded the mobile OS engineering team.

The FB mobile OS attempt resulted in a forked version of Android that ran on an HTC produced phone back in 2013. Flooding a phone with Facebook’s social feed was wildly unpopular even back before Facebook’s brand was tarnished with numerous privacy scandals. Facebook will have an uphill battle on its hands if it wants people to give its software another shot.

For those with short memories FB has leaked nearly 1 billion personal data records that we know about since 2018:

The idea of another FB OS gets even scarier when you add the legacy of Windows NT on top of FB’s lack of respect for its user privacy. The for uninitiated, Windows NT was released in 1993. It was Microsoft’s first foray into a network operating system (NOS). WinNT had a number of issues that made the Blue Screen of Death (BSOD) a household phrase.

Blue Screen of DeathA blue screen occurs when Windows encounters a “STOP Error.” This critical failure causes Windows to crash and stop working. The only thing Windows can do at that point is to restart the PC. This can lead to data loss, as programs don’t have a chance to save their open data. FB has put Mark Lucovsky, who co-authored the Windows NT operating system in charge of writing the FB OS. Some of the more notable problems with WinNT included,

  • Allowing the default user to run at admin/root privilege without a password.
  • Noted cryptographer Bruce Schneier, noted that part of Windows NT 4.0 is so broken it can’t be fixed with patches. Schneier said, “Last time they released a fix, it broke so many other parts of Windows NT.”
  • WinNT did not support USB.
  • NTVDM (also known as Windows on Windows, or WOW) that blocked access to the hardware so that legacy applications would run as though on a DOS computer, except without access to protected areas of memory. This resulted in a substantial number of applications simply did not work.

rb-

People back then perhaps thought better of letting Facebook on their phones. Toward the end of the decade, it seems we’ve come full circle

The rumor mill also says Facebook is working on a brain control interface for its devices, which could allow users to control them with their thoughts. But of course, that also means that FB could have access to the user’s brain – and sell their thoughts and then your brain will throw a BSOD, and will you have to reboot your brain to recover.- I’m just saying……

Related article

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

Windows Terrible, Horrible, No Good Month

Windows Terrible, Horrible, No Good MonthRedmond’s Terrible, Horrible, No Good, Very Bad month continues. The WannaCry ransomware hit mostly Windows 7 machines, and now researchers from the Russian information security company Aladdin RD recently discovered a new bug that will slow down and crash Microsoft (MSFT) Windows Vista, Windows 7, and Windows 8 PCs, but does not seem to impact Windows 10 so far.

Microsoft logoIn a throwback to the Windows 95 and 98 era, Ars Technica reports that certain specially crafted filenames could make the operating system lock up or occasionally crash with a blue screen of death. Ars reports that the bug allows a malicious website to try to load an image file with the “$MFT” name in the directory path. Windows uses “$MFT” for special metadata files that are used by the NTFS file system. The effected systems do not handle this directory name correctly.

The file exists in the root directory of each NTFS volume, but the NTFS driver handles it in special ways. Ars explains that it’s hidden from view and inaccessible to most software. Attempts to open the file are normally blocked, but if the filename is used as if it were a directory name—for example, trying to open the file c:\$MFT\123—then the NTFS driver takes out a lock on the file and never releases it. Every subsequent operation sits around waiting for the lock to be released. Forever. This blocks all other attempts to get access to the file system, and so every program will start to hang, rendering the machine unusable until it is rebooted.

DDoSArs says that web pages that use the bad filename in an image source will provoke the bug and make the machine stop responding. Depending on what the machine is doing concurrently, it will sometimes blue screen. Either way, you’re going to need to reboot it to recover. Some browsers will block attempts to access these local resources, but Internet Explorer will try to open the bad file.

Ars couldn’t immediately cause the same thing to occur remotely (by sending IIS a request for a bad filename), but it wouldn’t immediately surprise us if certain configurations or trickery were enough to cause the same problem.

Windows Blue Screen of DeathThe Verge has successfully tested the bug on a Windows 7 PC with the default Internet Explorer browser. Using a filename with “c:\$MFT\123” in a website image, their test caused a machine to slow down to the point they had to reboot to get the PC working again.

A Microsoft spokesperson told Engadget that the company is looking into the matter and will give an update as soon as it can.
“Our engineers are currently reviewing the information. Microsoft has a customer commitment to investigate reported security issues and provide updates as soon as possible.”

The Redmond boys also had to release an emergency out-of-band update for the Malware Protection Engine aka Windows Defender. Two Google security researchers discovered the “crazy bad” flaw. They claimed it was “the worst Windows remote code exec in recent memory.” The TechNet article says the vulnerability they patched would allow remote code execution if the Microsoft Malware Protection Engine scans a specially crafted file (CVE-2017-0290). To MSFT’s credit, they did fix the bug and release the patch with a week of being notified.

rb-

Early reports are that this bug is an attack vector. However, this is a denial of service attack that will need a reboot. This new flaw could be bundled with other more dangerous malware to force the user to reboot allowing the attacking malware to get loaded.

Related articles

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.