This YouTube video was sent to me via e-mail.
It is for Breast Cancer Awareness.
Pink Glove Dance
Dec 5th, 2009 by Johnny
Chase Credit Cards royally suck
Dec 3rd, 2009 by Johnny
![]()
I’ve been a Chase Bank customer for 25+ years. Today I received my credit card statement and it showed an amount due. I found that odd because I didn’t charge anything since I paid off the statement last month. Looking into it I found that …
late fee $15, posted 11/22.
full payment $49, posted 11/23.
finance charge of $1, posted 11/27.
statement closing date 11/27 with an amount due of $16 (all fees).
WTF! This is ridiculous! $16 in fees for a $49 charge for one-day late! That is almost loan-sharking at 979.59% per MONTH (which equals to 11755.10% per year). Gee wouldn’t it be nice to make those kinds of returns! If any citizen did this, they would be locked up!
I then proceeded to call Chase and see if they can reverse the charges. The first customer service rep said “Late is late. And you are late by one day, so there is nothing that I can do. Unless it is a Chase fault, we cannot do anything.” She then proceed to try and sell me a credit protection service. I hung up and called back. The 2nd customer service rep was even worse. He basically said, “there is nothing I can do and if you don’t like our policy, you can close the account.”
Holy crap! I guess they don’t like customers who pay off their credit card bills each month, despite the fact they make 2-3% off the merchants where I use their cards.
Another surprise. When I called back a 3rd time, the customer service rep told me that Chase sent out a notice with their statements a few months ago stating that there is a 5-day change in their grace period. She claims that Chase increased the grace period to 20-days. Upon more careful examination, I found that Chase reduced it to 20-days; but that is not all and this is what I found:
My statement closing dates were always the 27th or 28th of the month and my charges were due on the same day (historically for years).
Now, my statements still close on the same 27th or 28th. However, the due dates are now 5-6 days earlier! To make things worse, I’ve noticed that my statements are not arriving before the 1st of the month like they used to. Instead, they are now arriving around the 4th or 5th of the month. So this means they are holding (or printing late) the statements before they mail them out. This basically cuts the time we have to look over the statements before paying them, down to less than 10 days from 20 days (taking into account 2-5 days Chase holds the money before posting it to the credit card account). In my recent case, the funds cleared out of my bank on the 20th, yet Chase posted it on my statement on the 23rd.
This royally sucks! Chase is basically playing with our money for those few days all interest free and yet, they want to rape their long-time customers because they are not making enough from us simply paying on-time (fundamentally no risk to Chase for making 1-3% per charge from the merchants, after the upto 1% cash back they give the card holder). Chase now wants their good paying customers to pay them 200-300% per year like those higher risk customers who defaults or file bankruptcy.
Totally ridiculous. I guess this is the way JP Morgan Chase makes up the money their investment banking side is losing to rival Goldman Sacks. Something has to look decent on the balance sheets for their shareholders.
Well as of today, I am going to move all of my monthly recurring charges to non-Chase cards (and I have a few Chase cards). The Amazon.com, Buy.com and Toys-R-Us cards now going into the drawer and staying there (except for the one charge per year to keep the card active). I am not closing the accounts as that would end up hurting my credit score with a lower debt to credit ratio (as per Suze Orman).
I hope you don’t experience this yourself.
Avast – reverting back to another VPS file
Dec 3rd, 2009 by Johnny

Avast tonight released their updated VPS 091203-0 signature file which has been causing a lot of grief to everyone around the world with false-positives for the trojan/worm Win32:Delf-MZG[Trj].
The only fix for now is to disable updates and go back to a previous signature file that is not “bad”.
Luckily I have another machine which has not yet taken down this update, so I saved the 400.vps file from C:\Program Files\Alwil Software\Avast4\DATA into my USB key. I then copied this older version of the 400.vps file onto the computer with bad 091203-0 VPS signature file. I placed it into C:\ for easy access later (because we will be using the Command Prompt, so everything would be typed).
Now on the computer with the bad VPS signature file,
disable the Avast updates by setting it to “Manual”.

Reboot the computer (assuming Windows XP) into
and type the following:
cd “C:\Program Files\Alwil Software\Avast4\DATA”
ren 400.vps 400.vps.091203-0.bad
copy C:\400.vps
(this is why I recommended putting it in C:\ above, less typing)
Then reboot the computer back to Normal mode.
Your Avast VPS signatures should now be reverted to the older version.
Good luck!
Update: December 3, 2009 8:25AM EST
Avast released an updated signature file (VPS 091203-1) that is suppose to resolve the bug. Goto http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=377
.
LimeWire not connecting? the QUICK FIX
Nov 28th, 2009 by Johnny

While enjoying Thanksgiving with family and friends this weekend, I was asked how to fix LimeWire? It would run but it kept saying it was “not connected”.
Well, a quick Internet search all turned up with suggestions on uninstalling and reinstalling LimeWire. This is great if you have the installer to the version that was installed on the machine readily available. In my friend’s case, that was not the case. Besides, he didn’t want to redo all of his settings (tweaks) which has been working great for years.
While tinkering around on his laptop, I started to think it would be a quick fix if I could make LimeWire re-download the list of current peers. Hopefully do this without losing all of the other LimeWire settings.
So here is the QUICK FIX, all WITHOUT losing the other LimeWire settings:
Exit out of LimeWire completely and make sure it is NOT running.
In Windows (I am sure there is a comparable equivalent on the Mac and Linux),
open the folder
(on some older profiles, it maybe in
Delete the file gnutella.net.
Restart LimeWire and it should download a new peers list.
The file gnutella.net is automatically recreated when you exit LimeWire.
NOTE: this worked for my friend’s LimeWire Pro v4.12.3; so it may or may not work with other versions. If it works or does not work for you please leave me a comment with your LimeWire version, so the info can help others.
I hope this little bit of information helps you.
‘dangerous’ celebs in cyberspace
Aug 25th, 2009 by Johnny
Doing simple searches for your favorite celebrities online can give you results which links to malware. Trying to get some dirt on your favorite celebrity may result in you getting some dirt installed on your computer.
Jessica Biel most ‘dangerous’ celeb in cyberspace. Followed by Beyoncé, Jennifer Aniston, Tom Brady, and Jessica Simpson to round out the top 5.
Source: http://news.cnet.com/8301-1009_3-10317029-83.html?part=rss&subj=news&tag=2547-1_3-0-20
Suggestion: use a safer browser like Mozilla Firefox 3.5.
A very odd thing just happened to me this morning. While browsing on NewEgg in Firefox 3.5.2, I noticed that my browser slowed down.
Using TCPview, I noticed that I had a lot of TCP connections opened to cpe-24-29-138-176.nyc.res.rr.com. That struck me as very odd. I thought I had spyware loaded on my computer or something, and that bug was phoning-home.
Upon further investigation, I find that whenever I reloaded a NewEgg page, especially if it was a page with lots of images, several of these TCP sessions would open up again. So I decided to look at the source code of the NewEgg page.
Doing a NSLOOKUP on the hostname c1.neweggimages.com gave me a very interesting result.
Non-authoritative answer:
Name: a200.g.akamai.net
Addresses: 24.29.138.176, 24.29.138.186
Aliases: c1.neweggimages.com, images10.newegg.com.edgesuite.net
The IP addresses 24.29.138.176 and 24.19.138.186, both are residential RoadRunner cable modem dynamic IPs according to NYC RoadRunner; reverse resolving to cpe-24-29-138-176.nyc.res.rr.com and cpe-24-29-138-186.nyc.res.rr.com, respectively.
It struck me very odd that Akamai would use such home-grade dynamic broadband connections to provide their expensive edge-of-network services.
A few minutes later, I did another NSLOOKUP and the IPs changed, as it should with the Akamai service to spread the traffic around their servers.
Non-authoritative answer:
Name: a200.g.akamai.net
Addresses: 209.107.209.91, 209.107.209.122
Aliases: c1.neweggimages.com, images10.newegg.com.edgesuite.net
Non-authoritative answer:
Name: a200.g.akamai.net
Addresses: 77.67.91.72, 77.67.91.122
Aliases: c1.neweggimages.com, images10.newegg.com.edgesuite.net
And as I am writing this blog entry, c1.neweggimages.com now resolves to:
Non-authoritative answer:
Name: a200.g.akamai.net
Addresses: 24.29.138.172, 24.29.138.162
Aliases: c1.neweggimages.com, images10.newegg.com.edgesuite.net
Once again traffic routed back onto RoadRunner residential service in NYC (reverse resolving to cpe-24-29-138-172.nyc.res.rr.com and cpe-24-29-138-162.nyc.res.rr.com). Looks like Akamai is using a lot of residential IPs within the NYC RoadRunner network.
As a result, some of these residential IPs do not work all the time, causing the NewEgg (and now BUY.COM) pages not to load and just hang.
![]()
Would you pay Akamai to basically host your images at someone’s home using a cable modem?
I know I would not pay premium dollars to get stuff hosted at a home. I like the redundancy of a data center.
Twitter under Denial-of-Service Attack
Aug 6th, 2009 by Johnny

Since approximately 9am Eastern Time, Twitter has been down. Just now on CNBC, they announced that Twitter came out and confirmed they are under a DoS (Denial-of-Service ) attack.
Source: http://www.cnbc.com/id/32297641/
Happy Birthday America
Jul 4th, 2009 by Johnny
removing Microsoft .NET Framework Assistant Extension (spyware-like installation) from Firefox
Jul 3rd, 2009 by Johnny
How to remove Microsoft .NET Framework Assistant Extension from Firefox 3.0 and Firefox 3.5

I just upgraded to Firefox 3.5 and realized that Microsoft snuck in (spyware-like installation, without user acknowledgment) an extension to Firefox 3.0 that is not compatible with Firefox 3.5, that extension is the Microsoft .NET Framework Assistant 1.0.
Microsoft has released a newer version of that extension, version 1.1, which is compatible with Firefox 3.5. However, Firefox 3.5 cannot automatically update to it, you have to do it manually and can be found here:
https://addons.mozilla.org/en-US/firefox/addon/9449
Well … being that I want to use Firefox and stay away from Microsoft’s browser and plug-ins, I wanted to find a way to remove the Microsoft .NET Framework Assistant 1.0 extension, since you cannot just click “Uninstall” like all the other extensions I have in Firefox. Besides, why would I want to keep an extension installed that I did not install myself? Would you knowingly keep a piece of spyware running on your computer? Heck no!
So digging around, I found clues on how to remove it. Here is a script that I wrote to remove the extension from the computer and remove it from Firefox. However, I still had to manually remove the additional information Microsoft added to the Firefox UserAgent header.
@echo off
echo Removing dotNET Assistant Extension files …
rd /s “%windir%\Microsoft.NET\Framework\v3.5\Windows Presentation Foundation\DotNetAssistantExtension”
echo.
echo Removing dotNET extension from registry …
REG.EXE DELETE “HKLM\SOFTWARE\Mozilla\Firefox\Extensions” /v “{20a82645-c095-46ed-80e3-08825760534b}” /f
echo.
echo.
echo MUST manually remove the UserAgent setting from each Firefox profile …
echo.
echo you can manually delete this line from each prefs.js:
echo user_pref(“general.useragent.extra.microsoftdotnet”, “(.NET CLR 3.5.30729)”);
echo.
echo or do it from “about:config” within Firefox
echo.
However, this code did NOT work for all of my workstations. I found that in those cases I needed to manually remove an entry from the registry, so I created this .REG file:
REGEDIT4[HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Firefox\extensions]
“{20a82645-c095-46ed-80e3-08825760534b}”=-
Finally, to remove the added text from the UserAgent header in Firefox.
One way to do this is to simply open the prefs.js for your Firefox profile and remove the line which reads:
user_pref(“general.useragent.extra.microsoftdotnet”, “(.NET CLR 3.5.30729)”);
Or you can … in Firefox, type “about:config” into the URL box and you should see this:

Now in the filter box, type “useragent” and you should see something like this:

Right-click on the “general.useragent.extra.microsoftdotnet” line brings up a menu, select “Reset”.
Now close out of Firefox completely and restart it. You are now done.
Reference: http://support.microsoft.com/kb/963707
Censorship 2.0: China Blocks Google Search, Apps, GMail, and More
Jun 24th, 2009 by Johnny

Reference Source: TechCrunch – Censorship 2.0: China Blocks Google Search, Apps, Gmail, And More
Google for some reason started to blocking access to everything Google today. It is really preventing my clients with China offices from doing their work. Especially since they use Google Apps for their e-mail. When will China join the rest of the world and realize that the network is now global for many companies.

China must have done something with their Great Firewall to even block proxy traffic. My client has a proxy server in the US which they use in Firefox. Even that was blocked today. It results in a message saying that the “network was interrupted”.
Anyone know of a way to prevent that (blocking of the proxy, that is)?
| « Older Posts | Newer Posts » |
