It's not the flatness per se that's the problem IMO. That particular set is just really hard on the eyes.
Daiwa
Neill's a very smart dude. Be interesting to see what he can do once W10 is final. Patience.
Frogboy is feeling pretty damn good about his retirement nest egg about now. Demand for IP for W10 will be through the roof. And I don't mean Intellectual Property, folks. He's gotta have somebody on the inside over at MS. This is just too easy.
Unaware of such a restriction. Mods will need to clarify.
Don't find the Wallet feature in the BitDefender Small Business Security product we use, Doc. May just be in the personal version. Unless it's in the accompanying SafePay app which I haven't used.
While it appears to be a good PW generator, it looks like it doesn't handle remembering & autofilling them for you as does, for instance, LastPass. Personally, I find that feature of LastPass well worth the cost.
[e digicons]:yes:[/e]
Palemoon also skins well, FWIW. I've had only a couple of issues with PM - Flash frequently crashes (suspect that's Flash but interaction with an aspect of PM is reasonable to consider) and .pdf's fail to render at times & generate an error message saying there was a problem with Adobe (Reader or Acrobat). It claims to be a modified Firefox, "optimized" for Windows with all non-Windows features & code stripped out. At least in layman's terms.
Disabling SSL scanning in BitDefender & Avast (perhaps in other AV's as well) 'fixes' Chrome's FREAK vulnerability (at least here), but Chrome should fix it natively. Not sure how important SSL scanning is to one's AV, but until the AV's are updated to not use the old ciphers, wouldn't enable it. I prefer PM to Chrome in any event.
As usual, "Thanks, Doc!"
Thanks for the links, moshi. They raise an eyebrow a millimeter or 2 concerning Aviator, but more importantly are a good source of info for securing Chrome itself.
Hadn't looked at it that way, DaveRI. Some sound logic in that.
Aviator passes the Freak Check here on Win7 64bit, FWIW. And it claims to be more secure in general than Chrome (on which it is based).
I would strongly recommend the annual subscription for two reasons - price and indefinite use of the apps (always remember to download and archive). Not sure I can fathom paying $10/yr more to get less (apps vaporize when you don't renew). Seems a strange marketing plan to my simple mind. And I still contend the "infinite" tag is at minimum inconsistent with the product 'features'.
^^ [e digicons]:rofl:[/e] [e digicons]*_*[/e]
Well, well. The fix MS recommends breaks Windows Update. One of the comments in the ghacks article mentioned it and sure enough, it's broken on my rigs - when I check for updates I get an unknown error. It is MS, after all. [e digicons];P[/e] EDIT: Reset to Not Configured, rebooted & Windows Update is working again. What a cluster. EDIT2: Turns out the reason Chrome didn't initially pass was BitDe
Yeah, Aviator 37 passes here, too, despite Chrome 41 failing. Weirdness.
Can't expect you to vet everything, Doc. Well... we could. But that wouldn't be fair. The disclaimer you always provide should always be heeded . [e digicons]:thumbsup:[/e]
Thanks for the additional link, Doc. It is a white list so a shame the ZDNet author muddied the water. I followed the instructions from ghacks (& MS's security bulletin, using the cipher list there) and rebooted. Interestingly, Chrome 41 is still vulnerable after applying the policy according to the freak check tool. Hopefully, the OS cipher list filter protects it.
I looked at modifying the Group Policy as described in the ZDNet article. He provides a list of outdated vulnerable ciphers that he says should be added to the SSL Cipher Suite Order list and further says that adding them will prevent these ciphers from being used. As it happens, my SSL Cipher Suite Order is currently Not Configured, which from the description in the Group Policy Editor means the OS default list is being used , which presumably <
Chrome 41.0.2272.76 m fails the test here. Palemoon passes.
Don't worry - Mr. Wheeler will fix it. [e digicons]^_^[/e]
If Windowblinds is running, you'll want to change to the default Windows GUI (skin) within the Windowblinds Configuration dialog first. Then unload Windowblinds, then uninstall it using Control Panel. Si Windowblinds est en marche, vous aurez envie de passer à l'intérieur de <sp
There must be minor variations in W7 versions, Tom - I'm on 7Pro. FWIW.
Never confident enough to simply argue the evidence, the Warmists continue to wage the coward's war: The Warmish Inquisition