Sapphiron
Expert Member
- Joined
- Jan 29, 2004
- Messages
- 3,808
So my local ABSA ATM locked up with my card stuck in it.
after the cancel button did not return my card, I pressed the assist button, nothing happened for 30 seconds, I then proceeded to hold it down. After about 5 seconds, it started shutting down, including bringing up the notification of the offending non-responding process getting killed off.
(hello windows 7)
Out popped my card and it proceeded to reboot. I don't know if the assist button works as a power button, or if it triggered some SNMP health check from a remote monitoring system to send a remote reboot command.
Watching the process, It was incredibly slow. The hardware in the ATM must be so slow. It took over 8 minutes to boot to the log-in screen. I have R1999 thin clients that boot windows 10 faster. I guess providing clients with fast ATM's, so you don't waste their time, is not high on the budget priority list.
The rest of the application launch process probably took a further 12minutes before the ATM was usable again. Working completely normally from that point.
ABSA, you know that expensive windows 7 enterprise licence can probably buy an eMMC SSD and more RAM that will make your ATM less frustrating to use. You know Linux works great for single-purpose appliances right?
after the cancel button did not return my card, I pressed the assist button, nothing happened for 30 seconds, I then proceeded to hold it down. After about 5 seconds, it started shutting down, including bringing up the notification of the offending non-responding process getting killed off.
(hello windows 7)
Out popped my card and it proceeded to reboot. I don't know if the assist button works as a power button, or if it triggered some SNMP health check from a remote monitoring system to send a remote reboot command.
Watching the process, It was incredibly slow. The hardware in the ATM must be so slow. It took over 8 minutes to boot to the log-in screen. I have R1999 thin clients that boot windows 10 faster. I guess providing clients with fast ATM's, so you don't waste their time, is not high on the budget priority list.
The rest of the application launch process probably took a further 12minutes before the ATM was usable again. Working completely normally from that point.
ABSA, you know that expensive windows 7 enterprise licence can probably buy an eMMC SSD and more RAM that will make your ATM less frustrating to use. You know Linux works great for single-purpose appliances right?