Recommended Posts

I saw that "miracle survivor" it was called, might watch it proper later

It was good. Explained the physics behind how he survived and how he ended up on top of the collapsed building. And he also explained how they were watching the second plane crashing into the other building on the news and didnt hear/feel anything. How crazy is that.

I was in high school at the time. I was in the auditorium where they were telling us not to do drugs. When I got back to class, the TV was on where I saw the smoke coming from the buildings, but they hadn't collapsed yet. I don't remember much else, other than by lunch time, I was fully aware of everything that happened.

I was 15 years, skiving from school and watching the daytime airing of Neighbours in bed when it was interrupted by BBC News on the BBC.

I have never seen anything cause an emergency BBC News broadcast since that day 11 years ago.

I was in shop class. In my school we had a 5 minute bell that rang to let us know the period was ending. It rang at exaclty 9:11 AM. So, I first heard about the attacks after the equipment shut off at the 5 minute bell via the radio. 9:11 AM on 9/11. :ermm:

High School French Class. They said it over the intercom, and then proceeded to roll a tv into the classroom. Needless to say, we didn't get much work done that day. I think I saw both buildings collaspe during that class but heard about the pentagon and pa crashes later on offically.

I was at work when someone mentioned that a small plane had hit. Then the news came through that another plane had hit and they weren't small planes. After work, watched it all on TV.

I was sitting at my desk, answering phones for a production company manager. The owner of the company came in over the intercom and called a shop meeting, to halt all production (I'm talking about a thousand-people manufacturing company). Then they wheeled in a TV in the middle of the shop, as we all watched as the second plane hit...I couldn't believe what I was seeing! Then they announced that we had the option to either work all day, or go home to be with our loved ones. That shop cleared out faster than a tornado can destroy a house. Everybody went home, except for myself, the production manager, and the owner. (I had to stay and correct time cards for the ones that did not clock out before leaving) I'll never forget that day as long as I live.

I was on my way to work listening to the radio as the first plane hit. I made it in time to the office lunch room to see the second plane hit. We had a perfect view of the Sears tower and we just knew it was going to get hit as well. Luckily; that didn't happen but it was a very sad day in the office. Not a day I'll ever forget.

i was arriving from the college, had been talkin in IRC with some friends who's relatives worked in the WTC (didn't know back then); when i arrived home my father said that some accident happened, a plane crashed into a bulding... as it was unrraveling i was puzzled and in awe as the attack was unfolding, and just couldn't think of anything but "a terrorist atrack could happen in my country as easly as this one, as long somente prepares for it well enough and has the will to" - it was a scary thouth.

was in Grade 7. Another teacher came into the room and told my teacher. He then in turn told us, I don't think any of us knew what the World Trade Centers were, all we understood was that a plane hit a building.

Went home for lunch and my Dad had CNN on which was showing the replays of the planes hitting. I wasn't really phased by it, I mean I found it more interesting the next couple days where there was no planes in the sky.

I came home from school and I went to the lounge to see what was on the TV, and it was the WTC on fire, it hadn't fallen at the time I noticed. I was younger so I didn't stay and watch, I just said something like 'Oh god..', and carried on doing what I was doing.

21 at the time, was away at college in Hawaii. Due to the -3 hour time change, my dad called me close to 300am Hawaii time. He had to call 4 times before I woke up. Never heard fear in his voice before that day (he was a Vietnam vet, beat thyroid cancer, before losing to melanoma in 2008). Really shook me up because I had no chance of getting home.

My roommate and I turned on the TV and for the next 10 hours that's what we did. Oahu was shut down, military personnel had priority on the streets to get to the bases, school was cancelled. And I'll never forget driving home from downtown Honolulu a couple days later and seeing an airliner coming into the airport. Was a very strange feeling.

This topic is now closed to further replies.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!