VeeshanVault

So yeah, I've got this Linksys wireless network at home with my DSL. I'm currently using an external USB receiver on my computer. It's nice, I guess...no wires (duh!) is pretty convenient...but I get a recurring packet loss every minute or so.

What do I mean by this?

let's take counter-strike for example. I'll be going along...playing...everything fine - then *boom* 3 seconds of lagging out. Then i come back in (sometimes dead, which is extremely fucking frustrating) and I have about 45 seconds (it's not set, but it always is between 20-50 seconds) before it happens again.

Normally : 0% packetloss
but randomly: 100% for 2-4 seconds

Anyone have any fucking clue what might be causing this? I'm thinking radio/phone interference - but I have moved the wireless router repeatedly (My comp is about 15 feet from it, and one floor - About 40 feet if you were to trace from the router to computer w/o going through floor) to no avail.

I'll donate the 280 VV's i got saved in the bank to whoever can help me solve this ^^

scream at linksys and threaten to quit using their product. fill diapers full of shit and squeal until they cater to you.

Ok first of all, I assume when you say USB receiver, you mean USB external NIC.

If this is the case it's most likely that you need to update the drivers for that. It won't kill anything to make sure you have the latest firmware for your Linksys either. Beyond that, see if a wired connection has the same issues. That will tell you for sure if the problem is your router/internet connection or your USB NIC.

Typically I try to stay away from USB NICs, but that's just me.

IT MUST BE TEH ATI 9700!!!11!!1

I've got the latest drivers =/

Try the wired connection if you can (i.e. a standard (Fast) Ethernet NIC). You need to narrow down the scope of your problem to determine whether it's the NIC, your Linksys router/firewall, or your actual connection to the Internet.

It's something between the router and my computer - Other computer (the one directly hooked via Ethernet as opposed to wireless) is working perfectly...This one is just nonstop fuckups though =/

Ok so it's basically a wireless problem. I'd call in to Linksys support, and see what they say, but I think it's more likely a problem with the NIC than the router. Just my opinion.

Good luck.

Edit: Want to add, there's not really anything more I can do to troubleshoot it. I'm pretty familiar with the Linksys routers, and there's nothing really you can tweak from a wireless signal perspective.

Solution:

go back to cat5 cable!

Thanks for the VV's!

here's an example of my problem =/

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\DREWNO>ping -t http://www.hotbot.com

Pinging hotbot.lycos.com.akadns.net [209.202.195.206] with 32 bytes of data:

Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=3542ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=55ms TTL=240
Reply from 209.202.195.206: bytes=32 time=63ms TTL=240
Reply from 209.202.195.206: bytes=32 time=59ms TTL=240
Reply from 209.202.195.206: bytes=32 time=59ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=58ms TTL=240
Reply from 209.202.195.206: bytes=32 time=55ms TTL=240
Reply from 209.202.195.206: bytes=32 time=56ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=47ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=47ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=2933ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=52ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=53ms TTL=240
Reply from 209.202.195.206: bytes=32 time=47ms TTL=240
Reply from 209.202.195.206: bytes=32 time=57ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=52ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=56ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=53ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=53ms TTL=240
Reply from 209.202.195.206: bytes=32 time=63ms TTL=240
Reply from 209.202.195.206: bytes=32 time=64ms TTL=240
Reply from 209.202.195.206: bytes=32 time=65ms TTL=240
Reply from 209.202.195.206: bytes=32 time=52ms TTL=240
Reply from 209.202.195.206: bytes=32 time=56ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=47ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=51ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=2932ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=48ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=50ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240
Reply from 209.202.195.206: bytes=32 time=49ms TTL=240

Ping statistics for 209.202.195.206:
Packets: Sent = 162, Received = 162, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 3542ms, Average = 107ms
Control-C
^C

You can see it's decently fast - but every 20-30 seconds it just fucks up for no reason .... I HATE YOU LINKSYS!

Kguku wrote:Solution:

go back to cat5 cable!

Thanks for the VV's!

LMAO

CAT6 IS BETTAR! =P

Sure it isn't just the server you are trying to play on? We used to get problems like that with EQ - 100% packetloss for a few moments, only could get rid of it by sending a tell. Very strange.

Try connecting to different servers, and with different applications/games.

Also might be sure you have the most recent and/or correct drivers for the wireless ethernet card. That shit is really picky. 2.4ghz wireless phones are also bad around a wireless network.

Gotta be my ghey router

I do a ping to my router for about 5 minutes and I get an identical list as to the one i posted earlier...so i'm ....uh...taking 3 full seconds to send a packet 20 feet - Technology!

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\DREWNO>ping -t 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=3ms TTL=150
Reply from 192.168.1.1: bytes=32 time=3ms TTL=150
Reply from 192.168.1.1: bytes=32 time=3ms TTL=150
Reply from 192.168.1.1: bytes=32 time=3ms TTL=150
Reply from 192.168.1.1: bytes=32 time=2ms TTL=150
Reply from 192.168.1.1: bytes=32 time=3182ms TTL=150
Reply from 192.168.1.1: bytes=32 time=3ms TTL=150
Reply from 192.168.1.1: bytes=32 time=4ms TTL=150
Reply from 192.168.1.1: bytes=32 time=3ms TTL=150
Reply from 192.168.1.1: bytes=32 time=3ms TTL=150
Reply from 192.168.1.1: bytes=32 time=3ms TTL=150

Ping statistics for 192.168.1.1:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3182ms, Average = 292ms
Control-C



lol - That's my router 10 feet below me atm....Yeah - it's gotta be my NIC =/

Do a Tracert to that Ip and see if any of the hops are timing out.

Everything beyond my own router downstairs shows the same problem - gotta be a problem with connection from my external NIC and the router.
(computer downstairs doesn't have this problem)

The problem is, a ping is not conclusive to tell you whether it's your router or your NIC. Again, make sure your router's firmware is up to date, and I'd highly recommend calling Linksys support. True, they're kind of tools, but they might have seen something like this in the past.

Ok I know this is off the wall but going from a RL experience, you dont live near an airport do you?

I know, I know its out there. Just trying to help.

I had a very similar problem with my linksys wireless router.. I fixed it by getting an amplifier. Maybe that will help

I use wireless and I get insane packet loss whenever someone in the room I'm using my computer in farts.. =/

Linksys recommended buttplugs for my guests..

me thinks Coatie means a repeater. Its just a stand alone piece that repeats the signal. I see a few probs like this every week with Linksysy especially.
There is also a prob with 54g wireless and certain Gateway Laptops. A few friends of mine have tried to use Linkys 54g Cards on a brand new Gateway Laptop, it wont work, there is a driver issue with the Vid card and the 54g card. They will both say they are fine , the nic will grab an IP and have connect for about 12 secs , then POOF. The exact same thing happens if you try to input the stack manually as well , aprox 12 secs of connect then POOF. Just thought i would add to the discussion

woops, Phugg, you're right me bad!

I'm tired and disoriented! Never post on VV when you're like that!

at least I got more VV's

My father had similar problems. Turned out to be the router firmware itself. I have called linksys multiple times and they aren't that helpful but they try.

Deward

USB network cards are a bit flaky in general from all I've seen. The interface wasn't really designed for that type of useage, and the devices themselves are usually kind of cheesy.

If you can borrow a PCMCIA or PCI wireless card from someone try that, it would help narrow the problem down.

If you live in an apartment, condo, etc it could be one of your neighbors starting a microwave oven. Lots of stuff runs on 2.4Ghz.

It could be the port, the NIC, drivers, cordless phones, electrical devices nearby, all kinds of stuff. A ceiling fan in a house we used to live in made 90% of cordless phones worthless on an intermittent basis when it was turned on.

A piece of spyware might also be affecting your connection. Try running AdAware just in case.

you running encryption across your wireless LAN?

disable the security features and see if that helps performance.

they are pretty easy to circumvent anyway, so no big deal to disable them (in my opinion).

Spyware wouldn't take down the connection between his NIC and his Router. Spyware needs that connection to live.

It's most likely the NIC, and least likely a flakey router.

Is the router is doing DHCP to assign addresses? Have you tried increasing the legnth of time you lease the addy? It could be forcing your PC to renew its addy too often.

Nah mast
DHCP on my comp renews once per day =/

Well, did an interesting test today. Hooked up this computer (The one with problems) Downstairs earlier today, right next to the router. Same problem. Now i'm leaning towards the fact that it's an External USB wireless receiver being the problem. Gonna try with an internal one tomorrow, gratz NetGear on $30.

woot ! netgear powns

Well, I've been lurking long enough. Time to start posting.

Drewno,

I’m not sure if you’ve solved this problem yet, but I’ll post a “fix” in case someone else comes across it. (Skip to the bottom for solution information…the rest is information on the problem.)

Ok, I’m going to assume you’re using Windows XP due to the fact that this problem only/mainly occurs with it. Under any other operating system, the WUSB11 wireless nic card will function properly (the problem is the card and windows xp, not the router itself).

Essentially, Windows XP has a service it runs called, “Windows Zero Wireless Configuration”. Essentially, if supported by the nic card manufacturer (Linksys in this case), Windows XP will automatically locate the access point for you. Now, this would be a good thing if it were a one time deal. However, every couple of minutes or so, windows XP will attempt to check for any new access points or changes in current ones. This is bad; this is what causes you to lose connection, albeit briefly, while doing any online tasks. Not such a big deal while surfing porn…huge problem when playing a FPS.

Now, fortunately for you and me, linksys is “aware” of the problem and hopefully working on a fix. But unfortunately, whether this means today or next year, the world will never know. So, our only two solutions are to setup the router/card manually for direct wireless connection (good luck if you try this btw…linksys is horrible when it comes to firmware updates and customer support. Hell, disabling SSID alone will cause the nic to fail to connect) or disable the ZWC (zero wireless configuration) since Windows XP doesn’t have a simple “don’t check for new AP’s once one is found.

Now, I did a search on the web in regards to this problem and found a myriad of other users with the same problem. However, very few, if any, people offered a solution. Everything from batch files to dual boot operating systems was covered. But, nothing simple and effective would work. The only thing the solutions shared was this: disable ZWC. So, after trying a few different combinations, I came up with a recipe that seemed to work for me with the fewest of hassles or headaches.

Solution:

Once windows has booted to the desktop, you will need to set Windows Zero Wireless Configuration to manual. Start or Stopping the service alone while in automatic mode will not work due to the fact it requires a reboot, thus nullifying the whole process. To do this, you will need to:

- Right click on the “my computer” icon via the desktop or menu bar.

- Select manage

- Double click on services and applications, then again on services when it appears.

- Towards the bottom, you will see a service called “Zero Wireless Configuration”

- Right click on this and select “manual”. You may be required to reboot at this point.

- From this point on, the WZC will only start or stop when you tell it too.

So, what you’ll need to do from this point on is access the WZC service via the steps above every time you want to go online. Except, instead of selecting manual or automatic, you will just select start or stop depending on what you’re doing. You would select start immediately after boot-up to get network connectivity. Once windows XP found your access point/network (you can tell by the icon it leaves in the system tray…it’ll say something along the lines of network found, signal strength: excellent) you would then select stop to disable the service. From this point, you will retain your internet connection and no longer search for new AP’s. So, no more connection loss every two minutes, sporadic streaming audio, or porn interruptions. You will now see Jenna Jameson’s assets in all their jiggly glory.

I recommend leaving the service on manual even if you don’t plan to play any online games or use online services. It’s much less hassle to click start and stop once in a while than to set it to manual, reboot, then hit start or stop again anyway.

Anyway, Sorry to be so long winded, but I hope this helps. If you still have the problem after this (or aren’t even using windows XP…tee hee) let me know. We’ll see what we can do.

-Cthuldan

Cthuldan, brother You are missed!

I've used quite a few of those linksys routers. Not sure which one you have but I know the one I have will NOT WORK if someone is using a 2.4ghz cordless phone in the area... seeing as they operate on the same signal - the wireless drops out.

My solution for this was buy a 900mhz phone.

Not sure if you're in an area where maybe a neighbor might be using one or something.

What's up Cthuldan? Run out of panties to sniff, or is Kelgar wearing boxers now?

Drolgin Steingrinder wrote:Cthuldan, brother You are missed!

Hehe...I miss all you folks too, little tanklet.

Unfortunately, life decided to bend me over a barrel and systematically deprive me of my manhood. Shortly thereafter he took a huge dump on my chest whilst his dog dry humped my leg. I won’t bore you with the all the gory details.

Things are starting to look up a bit, though, and hopefully I can hang around more often than not. I might try to give Planetside a whirl, but I’ll have to lay off online MMORPG’s for a bit due to the time constraints involved.

However, Fear not! I’ll make sure to stop by occasionally and pester you folks like no one else can. I have a lot of new faces to insult and anger. Until then!

Aranuil wrote:What's up Cthuldan? Run out of panties to sniff, or is Kelgar wearing boxers now?

(missed your reply while I was typing)

Haha...Fok Joo Osshole!

Not too bad at the moment. Unfortunately, Kelgar decided to run off to the orient and get himself a “real” woman. I guess my bitch tits just weren’t good enough for him. Oh well, back to ol’ Rosie for me it seems.

It’s good to hear from you as well though, brudder (as pops used to say). We really need to get together sometime for a good old fashion shindig. It sucks I had to miss the Vegas fan faire…a lot of the finest people attended from what I gather. Sounds like you all had a blast. Soon though; Soon Cthuldan will attend the greatest of all gatherings where as he shall destroy you all, one by one, in the greatest of great events: Buffet-a-thon!

Until we meet on the battle field!

Oh yeah…pie really is better than cake. Prove me wrong children…prove me wrong.

Cthuldan
-The Fattest of fatties.

OMG! Cthuldan you gimp! How the hell have you been? Shoot me a PM.