Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Adrian Caspersz <email@here.invalid> |
|---|---|
| Newsgroups | comp.misc |
| Subject | Re: McDonald's Kiosk failure |
| Date | 2019-03-28 12:38 +0000 |
| Organization | Keep Usenet Text Newsgroups Alive!! |
| Message-ID | <gg3thhFnc0fU1@mid.individual.net> (permalink) |
| References | <gg321vFhie8U1@mid.individual.net> <gg3mr1FltlaU1@mid.individual.net> <gg3ra5Fms75U1@mid.individual.net> |
On 28/03/2019 12:00, Sylvia Else wrote: > On 28/03/2019 9:43 pm, Adrian Caspersz wrote: >>> >>> 4. Somehow, and upstream failure can break a touch screen driver. >>> >>> The mind boggles. >>> >> >> Faulty driver update deployed from remote? >> > > I don't think so. It appears I didn't adequately explain what was going > on. None of the McDonald's order system was working, not the kiosks, not > the counter cash registers, nor ordering over the Ap. > > The kiosk BSofD seemed just a symptom of the wider problem, albeit not > the kind one would expect. Maybe this. There apparently is a "EloView" management thing that looks after both Android and Windows clients, one of the features is a Connectivity Watchdog https://www.elotouch.com/eloview/support/whats-new-release-1.17-3 "You can now get more reliable connectivity to devices thanks to implementation of a connectivity watchdog. Devices can rarely go OFFLINE in the EloView portal due to prior network upsets or other issues. The watchdog will automatically reboot devices every 24 hours in case they lose connectivity. This is an optional feature you can select if you notice that your devices lose connectivity – i.e. show OFFLINE on EloView when they are in fact connected to the internet." The network went down, the driver noticed it and attempted to take windows down (unsuccessfully). -- Adrian C
Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
McDonald's Kiosk failure Sylvia Else <sylvia@email.invalid> - 2019-03-28 15:48 +1100
Re: McDonald's Kiosk failure mm0fmf <none@invalid.com> - 2019-03-28 07:37 +0000
Re: McDonald's Kiosk failure Roger Blake <rogblake@iname.invalid> - 2019-03-31 00:19 +0000
Re: McDonald's Kiosk failure Adrian Caspersz <email@here.invalid> - 2019-04-01 18:16 +0100
Re: McDonald's Kiosk failure Adrian Caspersz <email@here.invalid> - 2019-04-01 18:18 +0100
Re: McDonald's Kiosk failure Roger Blake <rogblake@iname.invalid> - 2019-04-01 18:02 +0000
Re: McDonald's Kiosk failure Adrian Caspersz <email@here.invalid> - 2019-04-03 13:37 +0100
Re: McDonald's Kiosk failure Roger Blake <rogblake@iname.invalid> - 2019-04-04 01:20 +0000
Re: McDonald's Kiosk failure Eli the Bearded <*@eli.users.panix.com> - 2019-04-04 20:57 +0000
Re: McDonald's Kiosk failure Andy Burns <usenet@andyburns.uk> - 2019-03-28 08:27 +0000
Re: McDonald's Kiosk failure Sylvia Else <sylvia@email.invalid> - 2019-03-28 22:55 +1100
Re: McDonald's Kiosk failure Richard Kettlewell <invalid@invalid.invalid> - 2019-03-28 08:39 +0000
Re: McDonald's Kiosk failure Sylvia Else <sylvia@email.invalid> - 2019-03-28 22:56 +1100
Re: McDonald's Kiosk failure Adrian Caspersz <email@here.invalid> - 2019-03-28 10:43 +0000
Re: McDonald's Kiosk failure Sylvia Else <sylvia@email.invalid> - 2019-03-28 23:00 +1100
Re: McDonald's Kiosk failure Adrian Caspersz <email@here.invalid> - 2019-03-28 12:38 +0000
Re: McDonald's Kiosk failure Sylvia Else <sylvia@email.invalid> - 2019-03-28 23:47 +1100
Re: McDonald's Kiosk failure kludge@panix.com (Scott Dorsey) - 2019-03-28 10:02 -0400
Re: McDonald's Kiosk failure Huge <Huge@nowhere.much.invalid> - 2019-03-28 14:17 +0000
Re: McDonald's Kiosk failure Ivan Shmakov <ivan@siamics.net> - 2019-03-28 14:30 +0000
Re: McDonald's Kiosk failure Andy Burns <usenet@andyburns.uk> - 2019-03-28 15:30 +0000
Re: McDonald's Kiosk failure Dan Espen <dan1espen@gmail.com> - 2019-03-28 09:45 -0400
Re: McDonald's Kiosk failure Rich <rich@example.invalid> - 2019-03-28 14:18 +0000
Re: McDonald's Kiosk failure Adrian Caspersz <email@here.invalid> - 2019-03-28 16:21 +0000
csiph-web