Hairclog

Do a little research on this dude. He's running another scam. Some people will believe anything

MTV Networks sells off Xfire gamer chat business to Titan Gaming August 2, 2010 | Dean Takahashi Add a Comment MTV Networks has sold off its Xfire gamer chat business, according to an announcement on the Xfire site. That’s an interesting twist, considering Viacom, the parent of MTV, bought Xfire in 2006 for $102 million. Titan Gaming announced this evening that it purchased Xfire for an undisclosed price. The purchase price has to be low, since Titan has raised only $1.3 million to date. The company plans to use Xfire to innovate in the gaming space. Titan itself runs a tournament games business. But Xfire’s current services will be uninterrupted, said John Maffei, chief executive of Titan Gaming, in a statement. The message posted on the Xfire web site says, “Xfire has been purchased by another company. Most of the team that has brought you Xfire for the last 6 years is leaving, including me. We’ve enjoyed our time and I personally am sad that I was only able to do 127 releases. Good bye and game on! –Chris.” It’s not clear who the buyer is yet. The Xfire site says it has more than 16.7 million registered users who use its chat service, which allows gamers to see what their friends are playing and to join them in an online multiplayer match simply by clicking on their names. Xfire was founded as Ultimate Arena in 2002 by Dennis “Thresh” Fong, a former professional game player who turned entrepreneur. He was joined by serial entrepreneur Mike Cassidy and David Lawee, now a Google executive. Xfire started as a tournament game site where players could bet real money against each other. But the business that took off was an instant messenger chat service for gamers. That enabled Xfire to grow quickly, but now it seems that Viacom has tired of the business. Fong, meanwhile, went on to create Raptr, the social network for gamers that is now one of Xfire’s competitors.

I was wondering what was going on...haven't played on the servers for a while cuz of my hand left hand going numb. So, I've been taking a break. Pretty cool program tho. Like it.

T-Mouse I think it's the ACE server he's talking about, Bear. And yes, it is possible to sprint faster with a weapon other than the Desert Eagle. The USP .45 also provides the speed boost. EDIT: Just to be clear, it doesn't seem to me there is any unfair play in question here, unless you're talking about something different entirely. Certain sidearms provide increased movement speed when you have them out, and everyone has access to them. Well, that's the issue...the players I've seen playing at a higher speed rate have been holding a primary weapon while doing it.

It's always been my understanding that in order to boost the sprint speed on the COD 4 DM server you have to pick the golden pistol to do it. Over the past several weeks I've noticed quite a few players zooming around the maps with their butts on fire like they had a jet engine coming out of their A holes. However, when specing them while doing this I've noticed that they are not using the golden pistol. Is that possible? Is it an overclocking adjustment that allows this? I kinda think this is a rather unfair advantage being used, whatever it is, and should be stopped.

I really like AVG free. I can't count the number of times it has saved my computer from alot of virus attacks by quickly removing them before they have a chance to get started. It's a very good program.

Was on the COD 4 Ace Mod server with a certain player and he was saying that he was getting a 1500 fps rate with this graphics card. Is that even possible on the server?

Well, it's all done, FINALLY!

JohnnyDos Hairclog this won't help ypu but last Saturday as I was about to install W7 my Seagate died.It allowed me to format but after I wanted to install windows 7 windows couldn't find it. So I tried to reinstall windows XP on it again Same thing couldn't find it .I went nuts for 2 days OK

Okay...so far so good.

We found some great tutorials on setting up some free cloning programs and a real cool (and free) Virutal XP machine, which will work with the goals we have for this stupid Seagate.

After nearly a month of alot of sweating, throwing stuff across the room, screaming, head pounding and cussing out the Seagate programmer who screwed up thousands and thousands of Barracuda hard drives with a bad firmware code, I FINALLY GOT MY HARD DRIVE BACK!!!!!!

Still at it peeps.

The second CA-42 cable arrived and nothing went good or according to expected results. Still couldn't get the thing to be recognized by the computer, even though drivers and Nokia PC suite software were supplied with this one. One of the major problems with this workaround is that the Nokia cables apparently are not manufactued consistenly from one source to another on the net. The wiring configs always seem to be different. There are a couple of other ways to try, parts for the next try are on the way...more later

Once is quite enough...thank you

Finally, got the Nokia CA-42 cable needed to start the process to get my Seagate drive fixed, but the thing was a knock-off product and didn't work the way it was supposed to. So, we had to order another one on Thursday. This one contains the software to install it properly and all of that. So, it should get here next week and we'll try it again.

I'm totally with ya on this Rugger! I don't care who it is or what rank he/she has on the servers. If anybody comes into the servers to constantly start drama and unneeded conflict with other players, it is time for that person to go...and I do mean QUICK!! It is a shame that other members of our German part of the family don't quite understand the justification for the action taken (probably due to faults in translation), but it is clear that this was not a spur of the moment decision and very careful consideration was made before this action was taken. I'm sorry that a few of our German friends and members are leaving, or considering that option, as a result of this. I think this is just because alot of these members/visitors don't understand the rules we have in place here and don't know the complete story behind the final decision.

Be sure to check back for updates as we try to fix this stupid Seagate drive.

Some of you may have and know about the bricking issue with the Seagate 7200.11 (along with other their models) related to their SD15 firmware upgrade. Here is a description of the problem that I found on a MSFN.org forum: "This condition was introduced by a firmware issue that sets the drive event log to an invalid location causing the drive to become inaccessible. The firmware issue is that the end boundary of the event log circular buffer (320) was set incorrectly. During Event Log initialization, the boundary condition that defines the end of the Event Log is off by one. During power up, if the Event Log counter is at entry 320, or a multiple of (320 + x*256), and if a particular data pattern (dependent on the type of tester used during the drive manufacturing test process) had been present in the reserved-area system tracks when the drive's reserved-area file system was created during manufacturing, firmware will increment the Event Log pointer past the end of the event log data structure. This error is detected and results in an "Assert Failure", which causes the drive to hang as a failsafe measure. When the drive enters failsafe further update s to the counter become impossible and the condition will remain through subsequent power cycles. The problem only arises if a power cycle initialization occurs when the Event Log is at 320 or some multiple of 256 thereafter. Once a drive is in this state, there is no path to resolve/recover existing failed drives without Seagate technical intervention. For a drive to be susceptible to this issue, it must have both the firmware that contains the issue and have been tested through the specific manufacturing process." Well, after so many users of the drive contacted Seagate about the problem, they posted a patch on their website which was supposed to have corrected the problem. The only thing was that nearly everyone who tried to install the patch found out that it made the issue even worse. So, they removed the patch from the website and worked out another one and posted that. But the problem with the patch is that it doesn't work on the HD already affected by the bricking issue, since it can't be applied to a drive the computer won't even detect. So, there are two options....send it back Seagate for a reset of the firmware's event log or use a repair rig and code set worked out by a poster to MSFN.org site [http://www.msfn.org/board/solution-seagate-7200-11-hdds-t128807.html], (or another variation of the same thing posted on Overclock.com[http://4f768b3a.qvvo.com]. In earlier statements by Seagate they told owners of the 7200.11 drive that they would fix the event log issue and, if any data loss was involved in the issue, they would also provide FREE data recovery services to make it right. Well, when my dad questioned them about this announced policy, he was told something entirely different. They told my dad that they didn't guarantee the data, so if after fixing the event log, any data lost on the drive would mean extra charges...anywhere between $500 and $3000, depending on the difficulty involved in retrieving the data. So, we are gonna try to do the Overclock.com fix. My dad already ordered the Nokia data cable and connectors that are needed to do the recovery. We're just waiting for them to get here. If you didn't guess already, the drive was on MY COMPUTER, and it went down last Saturday morning when I turned it on. That's why I haven't been playing on any of the XI servers all this week. I don't have anything installed on this new HD and don't want to go all through that until we see what happens with the attempt to fix the Seagate. According to what they say on both of the sites listed above, once the code to correct the event log has been entered and the new firmware upgrade is installed from Seagate, the drive should return to normal, since no data loss was involved in the original failure. Well, we'll see. I'll keep you posted on whether it works or not.