Some users reports resetting SMC and PRAM solve the problem of patching fail (see julian-poidevin/MBPMid2010_GPUFix#65).

This should be suggested if patching fails with error " Could not open Info.plist file".

Add a pop-up to suggest reset of SMC and PRAM in this case.

Use report ProgressPlugin instead of printing to console.

see: https://webpack.js.org/api/plugins/#reporting-progress

![mgs2_sse screenshot 2019 01 10 - 10 59 12 21](https://user-images.githubusercontent.com/45542721

You can currently reconcile them by using the printAeronStreamIdentifiers() option, but this isn't very useful for people ingesting stuff into a monitoring system like prometheus.

One option might be to expose the API programmatically like:

AtomicCounter msgSeqNo = FixCounterView.sentMsgSeqNo(sessionId).  - FixCounterView.bytesInBuffer(sessionId);

Another would be to see if we

It seems like usbcore quirks for AMD chipsets which involve PixArt mice can cause trouble that the mouse does not work properly after resume from suspend any more. There is a RESET_RESUME quirk set for the default PixArt mouse USB IDs 093a:2510. I guess booting with usbcore.quirks=093a:2510:b fixes this issue. It toggles the RESET_RESUME quirk flag.

For doing proper documentation, *