Sandy Hook Scanner Feeds

OP

Great summary, I just read on page one.

In the dropbox, which files are relevant? Looks like there is an entire days worth of audio?

Well...short answer is everything in the Newtown folder starting with:

201212140813-441506-7623

That number is:

20121214 (date) 0813 (time) and other numbers you can ignore.

Very important: 0813 is CENTRAL time. That's the time all RadioReference files use as a reference. That means that files marked 0813 are really referring to 0913 or 9:13 a.m. local Newtown time.

The incident response allegedly began at 9:36 a.m., at least in the Newtown audio; so this is the first file.

Imo, though, all times are possibly relevant, including the days leading up to the event and def the days after...that's why I've always included them all.

I was thinking of uploading some of them to SoundCloud for easier review; now in light of Dropbox failure, may do that for sure.

Amazing isn't it?

Never shows the proof of their pronouncement. Just states it as fact even though nobody has any kind of evidence to back that up.

Just updated the article with that, better for understanding the audio.. thanks for all your hard work!

On the contrary, the people claiming that law enforcement waited before entering or that EMS was barred from entering are the ones making the false claims which they cannot back up with any evidence(because they are lies).

The courant wrote the following November, 22: Police Response In Sandy Hook Shooting Scrutinized

[link to www.courant.com]

Among the aspects of the response under scrutiny was a decision by the first responding Newtown officer to park nearly a quarter mile away on the street to the school and wait for other officers to arrive, sources familiar with the investigation said. Those officers moved to the school on foot along the tree line.

State police offices are approx. 7 min. away from Sandy Hook school, NPD offices are less than 2 min. away. Why did they wait for state police? Perhaps they were following orders from headquarters, as stated by the Newstimes

[link to www.newstimes.com]

The most disconcerting sound between the school and Newtown police may be the apparent order from headquarters for police responders to “wait” before entering the school, Hearst Connecticut Newspapers has learned.

“Wait until you go into the building,” one person says from police headquarters toward the end of the five-minute shooting spree. “I’m not going to send them in yet.”


----------------------------


the fact that the Triage area was never used for the alleged “mass casualty” event- which flies in the face of every single triage protocol ever devised- four “zones” are used for triage, immediate, delayed, minor and deceased. NEVER are police the ones deciding who is dead, and bodies are ALWAYS taken to the hospital, to be worked on.. but this didn’t happen during Sandy Hook

the fact that the Triage area was never used for the alleged “mass casualty” event- which flies in the face of every single triage protocol ever devised- four “zones” are used for triage, immediate, delayed, minor and deceased. NEVER are police the ones deciding who is dead, and bodies are ALWAYS taken to the hospital, to be worked on.. but this didn’t happen during Sandy Hook

Not only that all the bodies were left in the school for what 18 hours? They removed them " overnight "
I thought protocol was to immediately sanitize the scene and remove the bodies for health reasons.

I thought protocol was to immediately sanitize the scene and remove the bodies for health reasons.

Those are lies.

You know that they are lies.

You will suffer every lie youve told.

Those are lies.

You know that they are lies.

You will suffer every lie youve told.

Oh yeahhhhhh. I'm trolling my own thread. Report back to Sheila and tell her you guys are F-u-c-k-e-d! This can't be erased.

Team 5.A/
SITE
Location of official Agency folder
None NPRC
Team Contact
Sheila N******

CHECKLIST

Do any of the respondents display the urge to supply information that could be helpful to your mission?

Do the respondents appear hostile to your attempts to steer the discussion?

Have you made a personal chart taking care to note who appear to be the “leaders” versus who appear to be the “followers”?

Have you attempted to gauge the “temperature” of the forum’s users?

In other words, the prevailing social psychology of the forum’s members?

Have you been more successful with one or the other XStart methods that were demonstrated in N-7015A.DOC?

Have more technical members (Computer Programmers, Administrators, or Moderators) of the forum deduced or accused you of hiding behind a proxy?

Would you gain more trust and/or credibility if you were to use one of the Agency’s allotted “HOME” pools? (most often needed when handling EVTS that are more sensitive to the pop. of a specific locale but also location centered web sites such as FB or Patch)

Has your PREDEV “persona” been successful or do you gauge that the users find you to be too obtrusive? Accusations of being “ever present” are.







Explained:


rdpclip.exe is the process that handles copy/paste & file copy transactions for terminal services during a REMOTE DESKTOP session. A few of you have questioned how the two text groups can be combined. rdpclip caches both clear-text and file copy data on each end during the transaction (the remote desktop server & client). After it completes the transaction, I think rdpclip calls a method (iostatZd15.1) to clear it's cache for the next job. This, however, didn't happen, so the rdpclip cache was still populated with 1) the error message and 2) the text content of the file that it was downloading for the client from Sharepoint cloud (C:\SharePoint012USNCSSAD_Wrkc9inet-N-7339.txt).

Next, the handler was probably using the remote server as it's bot host to interact with the website it was posting to. If the handler (either manually or automatically) pasted the thread reply and hit "post" the rdpclip process on the server was populated with not only the text reply for the thread, but also the existing data artifacts that were not successfully purged earlier. That explains how the error message, the .txt file (with the checklist) and the text reply got sent to the website as the reply from "Korea guy" (bot).

Summary:

1. We know the handler uses Remote Desktop to connect to the bot machine

2. We know the handler uses Remote Desktop to connect to Sharepoint cloud

3. We know that something broke rdpclip.exe during a transaction (evidenced by the windows exception stack values, header, and the warning dialogue)

4. We know that the rdpclip cache was not properly purged, and the error message was amalgamated with the contents of the last file copy job (the .txt file), and subsequently the text payload including quoted text and reply text.


EDIT: iostatZd15.1 is not a method, but a return from IOSTAT, in this case, when rdpclip ran out of room on the clipboard.

The actual error which occurred appears to be a known one involving Remote Desktop Protocol v5.1, since fixed in RDP v6, that involves something known as the "clipboard viewer chain".


It is an error that dates back to (at least) Windows 2000.

The actual bug surfaces because of the way the clipboard viewer chain (hereafter abbreviated to CBVC) is managed internally by Windows.

The CBVC is basically a Linked list.

This list of clipboard viewers is global, and each application shares it. Windows, however, only maintains a reference pointer to the first member of the list, and it is expected that each application, if interested in being made aware of changes in the state of clipboard, first register with the system. Registering adds that application's viewer to the global chain. Each CBVC member must maintain a reference pointer to the next member in the chain (why I emphasized this will be clear momentarily, if it is not already...).

Windows sends notification of clipboard changes by sending the WM_DRAWCLIPBOARD message to the 1st member in the CBVC, whose pointer, remember is maintained by Windows. This member has to deal with the event and pass it along to the next member in the list whose pointer it maintains, and so on and so forth.

So the simplest explanation of the bug, would also be the most obvious:
having each separate application sharing the responsibility of managing the pointers to an OS-level operation (the clipboard), is a really stupid and byzantine implementation.

The following paragraph, found here are a typical use-case for the manifestation of the type of failure we seem to be dealing with:

From Microsoft———>
I use Remote Desktop all the time to work inside of my development systems hosted by Microsoft Virtual Server. I use the host system to browse the web for documentation and searches as I work and when I need to copy some text from the web browser I find many times the link between the host clipboard and the remote clipboard is broken. In the past I have read that somehow the remote clipboard utility, rdpclip.exe, gets locked and no longer allows the clipboard to be relayed between the host and the client environment. My only way to deal with it was to use the internet clipboard, cl1p.net. I would create my own space and use it to send content between environments. But that is a cumbersome step if you are doing it frequently.


The only way I really knew to fix the clipboard transfer was to close my session and restart it. That meant closing the tools I was using like Visual Studio, Management Studio and the other ancillary processes I have running as I work and then restarting all of it just to restore the clipboard. But today I found a good link on the Terminal Services Blog explaining that what is really happening. The clipboard viewer chain is somehow becoming unresponsive on the local or remote system and events on the clipboards are not being relayed between systems. It is not necessarily a lock being put in place but some sort of failed data transmission. It then goes on to explain the 2 steps you can take to restore the clipboard without restarting your session.

Use Task Manager to kill the rdpclip.exe process
Run rdpclip.exe to restart it









All over the thread: Medical Response is total BS

and the Christmas trees on the 14th, on stacks behind the firehouse, that will get donated anonymously on the 15th.. 26 of them, also in the video.

#3556, since you are so knowledgeable about the event, maybe you can answer these questions:

Who declared the 27 victims at the school dead? When did that process start and when did it end?

I dont know that.


What I DO know for a fact is that LadyK and Zephyr keep telling known lies! Lie after lie after lie for almost a year now.

Why the fuck is that!?

Son, this is a forum for theorizing.

Running theories is not "lying." It is theorizing. The whole point is that you DON'T know everything you need to know when you're theorizing.

And I'd like to know who the hell is sticking up for NPD on a regular basis besides me. You're not exactly bending over backward to help anyone on the response side of Sandy Hook.

Well if you don't know the answer to my questions, then how do you know proper protocol was followed by emergency responders to sandy hook?

Yes, and guess who cleaned up the blood? Swansong, please help me find it, a company who has no experience with it, as well the Lady who called state police and asked who cleaned up the blood at 1:26:20:



and the Christmas trees on the 14th, on stacks behind the firehouse, that will get donated anonymously on the 15th.. 26 of them, also in the video.

Please also note that the Sandy Hook Medical Response was discussed in detail on GLP in March 2013, when a forum shill, paid by the government was exposed in the following Sandy Hook thread, trying to debunk the medical response with various user ID’s ON PAGE 7:

[link to www.godlikeproductions.com]

our article:

[link to www.insanemedia.net]

for the shill fail..

yup.. Medical Response is total BS

lies from the post I was responding to:

1)"NEVER are police the ones deciding who is dead,"
2) "and bodies are ALWAYS taken to the hospital, to be worked on."

Both of those are lies that LadyK and zephyr keep repeating. They know they are lies, yet they keep repeating them. AGAIN, why the fuck is that?

They have been here since the shooting telling thousands of intentional lies. Thats not accident. Its not just two wacko people either. Nor is it just a thousand mistakes. Its intentional lies and its being done for a purpose. AGAIN, why the fuck is that!?

First of all Im not your son you ignorant phaggot.

Second, telling lies that the individual knows are lies is not 'theorizing' you phaggot, its lying and nothing more.

Zephyr and ladyK have been pushing LIES(not theories but lies) ever since the shooting.

... which are the Sandy Hook Fire dept annual Christman tree sale which they have every year you liar



Why do you continue to tell all of these lies, which you know are lies?


You know, and I know you know, that all these things you are doing are lies. You know, and I know you know, that the SHFD has a Christmas tree sale every year.


Someone here, anyone, please tell my why LadyK, Zephyr, and several others keep telling lie after lie?

What is their purpose in telling all these lies?

anyone, please?

about police not triaging the deceased:

[link to www.sponsorhospital.org]


Pre-hospital personnel shall follow the direction of law enforcement with respect to crime scene management.
XIII. It is important to realize that law enforcement personnel have the authority to presume death. If death has been presumed by a law enforcement officer, medical confirmation procedures do not need to be performed by pre-hospital providers[ie. EMS] unless requested.




Zephyr and LadyK very plainly know that fact.

ie, they are liars.

There aren't many statements I can make with 100% certainty, but one of those is that I have never, ever said anything I knew not to be true, and never would. It is completely antithetical to research and theory to knowingly state a non-fact.

To knowing state a non-fact is like purposely making a 001 degree navigation error in space--it throws you completely off course and you never get home.

I wouldn't do it, and I don't do it.