Absa and Standard Bank to say goodbye to Windows 10

Microsoft generally cuts end user support but not really industry user support. Last year I finally shut down my one corporate Windows XP machine. Every 6 months an Microsoft engineer would patch it to make sure all worked well still.


The machine was a Windows XP machine that we virtualised, yet in 20 years we only rebooted it after patching and that's it. It was the most stable internal server we ever used with zero outtages, zero issues and worked like a steam engine just chugging along.
 
Corelli said:
Microsoft generally cuts end user support but not really industry user support. Last year I finally shut down my one corporate Windows XP machine. Every 6 months an Microsoft engineer would patch it to make sure all worked well still.


The machine was a Windows XP machine that we virtualised, yet in 20 years we only rebooted it after patching and that's it. It was the most stable internal server we ever used with zero outtages, zero issues and worked like a steam engine just chugging along.
Click to expand...
I still use an XP machine to this day to carry out specialized tasks.
Doesn't crash... never says die.
 
FNB moved away from Windows to a great part, along with PNP, as I have seen the hardware failure screens, which for FNB is a Red Hat based system, running a virtual XP machine to run the IE6.0 activeX that they use to interface with mainframes. Remember almost every ATM runs XP Embedded, which is still supported my MS, and they are firewalled off from any access orther than the internal secure network, because the US government also still run XP internally, and they pay a rather large annual bill to keep the security patches current, and backported to the image as well. PNP is running RHEL as well, have seen the boot panic screen on the local shop smart shopper interactive terminal, it probably has a HDD with corrupted areas, as the kernel is trying to boot, but is finding a configuration error, and needs a key pressed on the non existent keypad to continue.
 
Justanotherguybythesea said:
FNB moved away from Windows to a great part, along with PNP, as I have seen the hardware failure screens, which for FNB is a Red Hat based system, running a virtual XP machine to run the IE6.0 activeX that they use to interface with mainframes. Remember almost every ATM runs XP Embedded, which is still supported my MS, and they are firewalled off from any access orther than the internal secure network, because the US government also still run XP internally, and they pay a rather large annual bill to keep the security patches current, and backported to the image as well. PNP is running RHEL as well, have seen the boot panic screen on the local shop smart shopper interactive terminal, it probably has a HDD with corrupted areas, as the kernel is trying to boot, but is finding a configuration error, and needs a key pressed on the non existent keypad to continue.
Click to expand...
The ATMs I worked on ran Windows CE, and used eMMC as main storage. The IDE for development was Visual Studio 2003.
The "internal secure network" is provided by a South African company. I cannot mention details as I am under NDA.

What PnP uses is Linux, and those machines, I've had a tiny bit of involvement in, are not nearly as secure as what the ATMs were.

The current crop of NCR machines run on Windows but not XP embedded.. It was a heavily customized version of Windows 7 IIRC, with their BS baked in
 
i remember seeing one of SB diebold machines that had crashed, and the OS background was XP, though, because the trackball does not have clickable keys on it, I was unable to run anything, as the keyboard they used did not have any control or windows keys available to the outside.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X