• Content Count

  • Joined

  • Last visited

Community Reputation

23 Neutral

About goates

  • Rank

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. goates

    R.I.P. 15 dead as 707 crashes into dwelling

    The sanctions on Iran have long affected their aircraft, including preventing them from acquiring spare parts for Western built aircraft. One of the first things Iran did when the sanctions were lifted a few years ago was acquire new, and far more modern, aircraft. Now that the US has pulled out of the deal and re-imposed sanctions, they are being forced to go back to stripping aircraft for parts. https://www.forbes.com/sites/dominicdudley/2018/09/07/iran-old-aircraft-flying-sanctions-new-planes/#4cd109616156 May or may not have had any effect on this crash as it does sound like they landed at the wrong airport.
  2. goates

    How does Boeing or other manufacturers use Python?

    CAD and FEA packages like CATIA (a common aircraft design package from Dassault) use scripting languages like Python. Here's one example: http://ifcuriousthenlearn.com/blog/2015/06/10/catia-and-simulia-scripting-and-automation-with-python/
  3. goates

    Congratulations SpaceX !!

    And Mr. Musk just threw down the gauntlet. https://arstechnica.com/science/2018/02/elon-musk-i-will-eat-my-hat-if-a-competitors-rocket-flies-before-2023/ Will ULA take up the challenge and buy him some mustard??
  4. goates

    Congratulations SpaceX !!

    It's confirmed, the centre core didn't make it. https://arstechnica.com/science/2018/02/this-may-be-the-moment-spacex-opened-the-cosmos-to-the-masses/ Very impressive achievement overall for SpaceX! As Mr. Musk said in the news conference, hopefully this leads to others trying to catch up and start a new space race.
  5. Microsoft's patches have been having trouble on older AMD processors. https://www.theverge.com/2018/1/9/16867068/microsoft-meltdown-spectre-security-updates-amd-pcs-issues
  6. From what I've read elsewhere it sounds like there are more official and less aggressive ways of doing this, while others get more aggressive and creative.
  7. Here's more info from Intel about the Meltdown/Spectre problem. https://www.intel.com/content/www/us/en/architecture-and-technology/facts-about-side-channel-analysis-and-intel-products.html
  8. Again, that issue is a different one than the current Meltdown/Spectre issue. Yes, Intel and others knew about the Meltdown/Spectre problem last year, but that link you posted and the tool posted earlier in the thread are for a different problem affecting Intel's Management Engine. They are not the same thing.
  9. Exactly, check the revision dates at the bottom of the article. It is not for this latest security problem. Nothing about these latest Meltdown/Spectre issues are related to the Intel Management Engine issue that was discovered last fall. Here's the correct Intel Security Center link. https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr
  10. Are you sure that isn't for the previous Intel ME issue from last year? https://arstechnica.com/information-technology/2017/11/intel-warns-of-widespread-vulnerability-in-pc-server-device-firmware/
  11. Some of the flaws were discovered and reported to the CPU manufacturers last June. https://googleprojectzero.blogspot.ca/2018/01/reading-privileged-memory-with-side.html
  12. Hackers are getting more and more creative all the time. Remember the CCleaner infection from last year? https://arstechnica.com/information-technology/2017/09/ccleaner-malware-outbreak-is-much-worse-than-it-first-appeared/
  13. It should be noted that there are two issues, one that affects Intel only and second one that affects AMD, ARM and other processors too. https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-every-modern-processor-has-unfixable-security-flaws/?comments=1&start=40
  14. That tool is for a different issue, not this latest CPU problem.
  15. That tool is looking at the Intel ME issue from last year and is completely irrelevant to the latest CPU issue. At this point it is really confusing the issue and it would be great if the link could be removed.