They sent the wrong tires twice, finally received the correct tires the 3rd time. They covered the return shipping of the wrong tires including UPS pickup at our house both times. Minimized the hassle of the return at least.

One thing to note, I got a foreign currency charge on my credit card with this purchase. Was only like a $1.50, but still unusual.

The 1st time I made an appointment for a tech to come to my house, the tech installed an amplifier on the cable line. That worked for two days then the random outages started again.

Next, I called again and made another appointment and was told the next available was three days away. Fine. The next day I called to reschedule the appointment due to a scheduling conflict and was told by the call center that I never had an appointment in the first place!

The third time I made an appointment for a tech to come to my house, they didn’t show up. No call or anything. That was last week.

I’m getting ready to call again. We’ll see what happens this time.

If Comcast sees this blog, please help me before I’m forced to switch to Knology. Maybe somebody can contact me who can actually do something and not just say, “Call Comcast and make an appointment”. I already tried that. Send me a message here.

UPDATE:
So we called and made an appointment for after 5pm on Wednesday. 10 minutes later we call again to double check the appointment time with the automated system and it says our appointment is Tuesday between 8 – 5pm. WTF. So either Comcast’s appointment system is a piece of junk or the call center staff is intentionally screwing up appointments. With 3 of our 4 appointments were scheduled incorrectly, I wager that Comcast staff is screwing up the appointments intentionally (or they just don’t care).

UPDATE AGAIN: Comcast tech came out Tuesday and ran a new cable from the pole to the house. Been working fine since. Comcast tech was super nice and seemed very competent.

The first time this happened, our monthly utility bill was entered every month up to the year 4800. This causes the QDF file to grow huge. Mine went from 12 MB to 120 MB. The second time this happened one of our scheduled deposits entered 300 years into the future before I realized what was happening and killed Quicken. The QDF file had grown to 30 MB this time.

The fix is to:
1. Backup your quicken data files!!!!!!!!!!!!
2. Set your system clock back to 12/31/2008.
3. Open quicken.
4. Delete the problem scheduled transaction.
5. Set your system clock back to current date.
6. Open quicken and run a verify on the data file.
7. Delete all the erroneously entered scheduled transaction – in the register, filter by date into the future ~300 years at a time (more than that and Quicken will crash), highlight them all and delete. Do that changing the date filter until all the bad transactions are gone.
8. Recreate the scheduled transaction you previously deleted.
9. Run verify again.

Your QDF file will still be huge so I did a File -> File Operations -> Copy. The new copy won’t have all the empty space from those hundreds/thousands of years of transactions you just deleted. Use the new copy as your active Quicken file.

Intuit has a support article on this issue with similar instructions but I can’t find it now.

We’ve changed all our scheduled transactions to be reminders, not automatically entered. This is a highly annoying bug. Intuit sucks.

I found the Intuit support article: Quicken freezes when attempting to open a data file created prior to 1/1/09

Companies can employ the talent to develop and maintain open-source products. But that talent can leave at ANYTIME. That’s the problem with open-source in the corporate environment.

Worked fine with Firefox or with IE if you used the IP address of the webserver. Just not with IE using the NetBIOS or FQDN of the webserver. Ended up being SPN and Kerberos issues.

Read this.

This is also useful.

A “Multivendor Post” to help our mutual iSCSI customers using VMware

Conficker Worm: Help Protect Windows from Conficker.A and Conficker.B

“…a simple and easy way to organize, connect and switch between remote desktops.”

Comcast seems to be prowling the web for unhappy customers, if you notice the comment on the previous post. Not a bad thing.

First, the Ubuntu server download is available here.

Second, the fix so the install will recognize the cd-rom is here. The important part is this:

“The cd issue could be solved in my imac G3 slot-loading typing in the command prompt (switch to another virtual screen with Ctrl-Alt-F2):

modprobe ide-scsi

then when asked for a cd device answer /dev/scd0″

That worked on my 667 mhz G4 titanium DVI Powerbook also.

via metafilter

Found via Carpe Datum

Other good articles in the blog linked…