scrolling text in server two video

[johny 5]

Here's the WhoIs info on that IP:

OrgName: Reuters America Inc.
OrgID: REUTE-3
Address: 587 James S McDonnell Blvd
City: St Louis
StateProv: MO
PostalCode: 63402
Country: US

NetRange: 159.43.0.0 - 159.43.255.255
CIDR: 159.43.0.0/16
NetName: REUTERS-CELL-INFRASTRUCTURE
NetHandle: NET-159-43-0-0-1
Parent: NET-159-0-0-0-0
NetType: Direct Assignment
NameServer: NS.EJV.COM
NameServer: GKBKUP3.BRIDGE.COM
Comment:
RegDate: 1992-03-06
Updated: 2006-01-27

OrgTechHandle: JPE67-ARIN
OrgTechName: Peters, Joe
OrgTechPhone: +1-631-435-7102
OrgTechEmail: **********@reuters.com

OrgTechHandle: KMO21-ARIN
OrgTechName: Montgomery, Keith
OrgTechPhone: +1-631-233-6795
OrgTechEmail: ****************@reuters.com

# ARIN WHOIS database, last updated 2007-07-11 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database
***********

As you can see, it was registered to Reuters (a very large news organization) in 1992. It's a class B IP range, which means they own everything from 159.43.0.0 through 159.43.255.255.

Also of note is it's net name: REUTERS-CELL-INFRASTRUCTURE.

While I seriously doubt Reuters is going to be involved in the ARG, it might be possible to call that the IP address with an IP phone system, which I don't have.

There's my 2 cents.

[MulletedOne]

when the bungie logo appears?

They never determined it to be anything.

[Xastabus]

I think we're going in the wrong direction here. While I don't have the ability to capture the video and go through it frame by frame, I can clearly see there are more than 2 character forms in the scrolling "text" on the server 2 vid.

Server 2 code magnified.jpg (32.13 KiB) Viewed 6193 times

I used the magnifier in Windows to blow up the image, then took a screen shot in one of the relatively dark sections. I can clearly see at least 5 types of "small" characters and 2 or 3 types of "large" characters.

In the sample below, I've highlighted what I think are the characters. Forgive me, the enlarged image is very grainy and I'm not to sure about some of the characters.

Server 2 code highlighted.jpg (11.94 KiB) Viewed 6193 times

And here is the original (cropped down so as to not be too large).

Server 2 code source.jpg (245.53 KiB) Viewed 6194 times

Someone with better tools at their disposal should look at this more carefully.

[S3NATOR]

Here is the video for all to enjoy courtesy of Big D Bassist over at CI:

Link

Should be helpful in trying to decipher this frame by frame.

S3N

[spartan117]

do you think the forerunners spoke in binary code?
by seeing pics of it in "Cradle of Life" and in the halo3 zune behind the chief im led to believe they were some kind of a cyborg. or machines driven by organisms.

[t0rm3n7]

looks like there are nine different characters formed from two base chars.

actually the top char looks like its a derivative of the bottom, or vice versa...

[kornman00]

When translating it into binary, don't forget to treat it as both big and little endian byte ordering before drawing conclusions.

[scapermoya]

bah. there are no assurances that this will lead to anything, and yet we have basically nothing else to work on right now. if only this type of analysis wasn't so daunting....

[Xastabus]

There also appears to be a basic "L" form (for lack of a better description) that has no horizontal bar.

That would make 10 character forms that we can decipher fairly clearly right now. Could these refer directly to numbers?

I'm not sure if that is the limit of the number of character forms, the captured video doesn't appear to be as high quality as the original.

I'm not sure if anything can come of this. Every frame has a different character string and the images in many of the frames washes out the string making it very difficult to decipher. But at least it's something to investigate while we wait for more clues.

Edit: By the way, thanks for posting that link to the captured video, S3NATOR. Using that I determined that my enlarged image is 7 frames behind the normal size. I was hoping the magnifier wouldn't lag so much... I probably should have prepared my example differently.