If you voted for Obama because he's black, then you're racist!
Somebody had to say it!
Tuesday, July 28, 2009
Monday, June 29, 2009
mBank? Fifth/Third? No contest!
I've been a regular patron of Fifth/Third for 15 years, at least. Back then, they were Old Kent, and they helped my mom get a mortgage for her house (back when her income wasn't the greatest). Old Kent was so helpful, our whole family became loyal customers. When I started my business, there was no question about who would get my business checking account.
However, when Old Kent got bought out by Fifth/Third, everything changed. Their customer service became an absolute joke. They offered me a wonderful "special rate" of 19% for a small business loan. They started charging (without warning) fees on every debit card usage. They mistakenly added finance charges to my 5/3 MasterCard (when I hadn't bought anything). They added overdraft protection to my checking account, when I had explicitly stated I didn't want it on there. They warned me that they would charge me fees if I ever spoke to a teller instead of using the ATM. They would send statements to the wrong address after I made absolutely sure they had the right address, and then refuse to reverse the late charges.
I started using mBank. Just a little at first. I couldn't help but notice how nice their tellers were. They remembered me - and I only go into the bank once every other month or so! I've never had a problem with them charging me ridiculous fees caused by computer errors, and then hassling me when removing them. It's been like a breath of fresh air. I am always, always impressed with the friendliness and helpfulness of their employees. Their web site doesn't look as pretty as 5/3, but it actually works better.
Last week, I took my leave of Fifth Third, permanently. I will never, ever do business with them again. I stood by them over the years; I still remember a whole slew of people leaving when they pulled the debit card fee stunt, but I stuck it out. My last experience with them, however, was the last straw. According to my estimates, I've lost about $65 from fraudulent charges by Fifth Third over the years. This last episode only accounts for $11.35 of that, but I've had it.
Fifth Third: you're fired.
mBank, welcome to the family. You just got my business.
Saturday, August 02, 2008
Unresolved BSOD
This morning, one of my development machines died unexpectedly from a BSOD. I haven't been able to find any information from Google, so I'm posting my experience here for others to find.
The culprit seems to be ipnat.sys, which is interesting because even though I have a complex network setup, Windows doesn't handle the NATing. I'm running XP SP3 on this laptop, with ipnat.sys 5.1.2600.5512, modified Monday, April 14, 2008, 12:27:16 AM. The OCA failed because I had the minidump open in WinDbg at the time (oops).
Detailed network setup at the time of crash (10 adapters total):
- 1394 (FireWire) port - disabled
- Builtin wireless - disabled
- Dialup connection via physical modem - enabled but phone line not plugged in
- USB wireless - active, with Internet access
- NIC - active, local access only
- PCMCIA cell tower wireless ("dialup") - enabled but not inserted
- VMWare VMNet1 for virtual machines - enabled but not active (no virtual machines were running)
- VMWare VMNet8 for virtual machines - same
- VPN virtual adapter for OpenVPN connections - disabled; no longer used
- VPN virtual adapter #2 for OpenVPN - same
VMWare and OpenVPN both handle their own NAT, and adapter #4 is *not* shared over the network on #5, so I don't know why Windows was doing something with NAT.
Anyway, here's the WinDbg analysis:
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\Stephen Cleary\Local Settings\Temp\WERe5f9.dir00\Mini080208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\Work\RAC\RAMDisk\Project\debug;symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Sat Aug 2 07:35:32.341 2008 (GMT-4)
System Uptime: 0 days 20:28:21.531
Loading Kernel Symbols
...............................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {3a003e, 2, 1, ed878886}
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ipnat.sys ( ipnat!NatDereferenceAddressPoolEntry+ce )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 003a003e, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: ed878886, address which referenced memory
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
WRITE_ADDRESS: 003a003e
CURRENT_IRQL: 2
FAULTING_IP:
ipnat!NatDereferenceAddressPoolEntry+ce
ed878886 894804 mov dword ptr [eax+4],ecx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: f78b6dac -- (.trap 0xfffffffff78b6dac)
ErrCode = 00000002
eax=003a003a ebx=8a4eef58 ecx=e75b94c8 edx=00000000 esi=8a4260e8 edi=8a4260e8
eip=ed878886 esp=f78b6e20 ebp=f78b6e30 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
ipnat!NatDereferenceAddressPoolEntry+0xce:
ed878886 894804 mov dword ptr [eax+4],ecx ds:0023:003a003e=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from ed878886 to 80540683
STACK_TEXT:
f78b6dac ed878886 badb0d00 00000000 ed52b35c nt!KiTrap0E+0x233
f78b6e30 ed87d965 8a4eef58 8a4260e8 8a4eefb8 ipnat!NatDereferenceAddressPoolEntry+0xce
f78b6e44 ed87f601 8a4eef58 fdfd0128 ed87f266 ipnat!NatDeleteTicket+0x2f
f78b6e88 804ffd88 ed887da0 00000000 df47447e ipnat!NatTimerRoutine+0x39b
f78b6fa4 804ffe9f 99893074 000000ab ffdff000 nt!KiTimerListExpire+0x122
f78b6fd0 80541b8d 80552da0 00000000 0047f961 nt!KiTimerExpiration+0xaf
f78b6ff4 8054185a ba43e9c8 00000000 00000000 nt!KiRetireDpcList+0x46
f78b6ff8 ba43e9c8 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
WARNING: Frame IP not in any known module. Following frames may be wrong.
f78b6ffc 00000000 00000000 00000000 00000000 0xba43e9c8
STACK_COMMAND: kb
FOLLOWUP_IP:
ipnat!NatDereferenceAddressPoolEntry+ce
ed878886 894804 mov dword ptr [eax+4],ecx
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ipnat!NatDereferenceAddressPoolEntry+ce
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ipnat
IMAGE_NAME: ipnat.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025786
FAILURE_BUCKET_ID: 0xD1_W_ipnat!NatDereferenceAddressPoolEntry+ce
BUCKET_ID: 0xD1_W_ipnat!NatDereferenceAddressPoolEntry+ce
Followup: MachineOwner
---------
Friday, July 04, 2008
Some excellent math jokes!
Why did the chicken cross the Möbius strip? To get to the same side!
Life is complex: it has both real and imaginary components.
There are 10 kinds of people in the world: those who understand binary and those who don't.
92.734587% of all statistics claim a precision of results that is not justified by the method employed.
Let epsilon be less than 0.
He thinks he's really smooth, but he's only C^1.
One day, Jesus said to his disciples: "The Kingdom of Heaven is like 3x squared plus 8x minus 9." Peter remarked: "Ah, another one of His parabolas."
A polar bear is just a rectangular bear after a coordinate transform.
Integral z-squared dz
from 1 to the cube root of 3
times the cosine
of three pi over 9
equals log of the cube root of 'e'.
Parallel lines never meet, unless you bend one or both of them.
My love for you is a monotonic increasing function of time!
Life is complex: it has both real and imaginary components.
There are 10 kinds of people in the world: those who understand binary and those who don't.
92.734587% of all statistics claim a precision of results that is not justified by the method employed.
Let epsilon be less than 0.
He thinks he's really smooth, but he's only C^1.
One day, Jesus said to his disciples: "The Kingdom of Heaven is like 3x squared plus 8x minus 9." Peter remarked: "Ah, another one of His parabolas."
A polar bear is just a rectangular bear after a coordinate transform.
Integral z-squared dz
from 1 to the cube root of 3
times the cosine
of three pi over 9
equals log of the cube root of 'e'.
Parallel lines never meet, unless you bend one or both of them.
My love for you is a monotonic increasing function of time!
Monday, April 14, 2008
Telemarketing
Well, I have an admission to make. I had to work for a little more than a month at a telemarketing position. While that was not the most enjoyable job in the world, I did get to learn all about the legal ins and outs of telemarketing.
One of the most common questions people have about telemarketing is how to stop it. It is not really as difficult as it seems.
There are four Do Not Call (DNC) lists that telemarketers abide by:
- The Direct Marketing Association (costs $3.00, and also implicitly places you on a Do Not Mail list as well)
- State DNC list (probably free)
- National DNC list (free)
- Each company usually has their own private DNC list as well; when you ask a telemarketer to be placed on the DNC list, you go on their private DNC list. Of course, that won't prevent you from getting calls from other companies.
- They're only good for five years. For example, if you get on the National DNC list, you'll have to get back on it every five years.
- The following telemarketers are not affected by the DNC lists:
- Non-profit companies
- Politicians
- Surveys
- Companies with whom you have an Established Business Relationship (EBR)
- Get on the National DNC list.
- Respond to Privacy Act Notices.
- Never say "not interested." This is the most common response, but they'll just call you back in a few weeks with a different offer.
- Explicitly ask to be placed on the "Do Not Call" list. They are then required to read this paragraph confirming your name and address, apologizing, letting you know it may take up to 30 days to take effect, phone number of the company they're representing, etc. Let them finish.
- Be nice! There have been situations where people were... ah, accidentally... placed on the Spanish callback list... and it's just coincidental that these people were absolute jerks...
Friday, August 10, 2007
Continuing my tradition of yearly blogging...
Ah, my mind is filled with beautiful music! "Her voice enters my heart... and makes me a better man." "Sweet hope and cold fear are battling in my heart."
I just got home from attending Bay View's presentation of La Cenerentola. What an incredible production! I'm not normally a huge fan of opera, but after reading about this one and seeing a preview in the park downtown, I decided to go.
All I can say is: wow.
What was truly incredible about this production is that they added so many little things to keep it interesting. The most noticeable is that when the valet dressed up as the king, he actually dressed up as The King. Yes, Elvis was large and in charge. This setup helped add a lot of spice throughout the opera. Whenever Dandini would sing a long solo piece, he would always keep it interesting by trying out a few of Elvis' moves. In an ordinary opera performance, he would just sing out his rather repetitive song; in this performance, he was constantly moving and - while I'm sure this detracted from his ability to sing to the utmost - it enhanced the audience's enjoyment considerably.
This pattern was repeated all througout the opera, especially during the repetitive, repetitive, repetitive songs. There was one additional fellow who kept showing up (dressed as a Blues Brother, I believe). He was credited as "supernumerary", which is just a fancy word for an extra, and I doubt if he's actually in the opera proper. Clorinda's solo near the end of the opera involved her and the unnamed extra sitting at a table, with a constant joke of not quite smoking and him drinking out of her glass.
Another memorable little item was when Alidoro was proclaiming Cenerentola's arrival at the ball; the other four characters in the room all ask him questions (over and over again). This was handled in a very creative fashion: as they were repeating their questions to him, they would step closer and closer until (just at the moment they all start singing together), they are all literally just inches from his face singing right at him, and his voice is breaking through the wall around him "No one knows..."
The stand-out character (and the one who made me want to see the opera) was Don Magnifico, whose acting was absolutely incredible in every way! Enough cannot be said about this one! He totaly stole the show.
Another running joke was the instant camera. When the sisters are introduced to the "prince" (actually Dandini dressed up as the king, er, The King), during that piece each of the sisters took a turn getting their picture taken with Dandini. Then, Don Magnifico had to have his moment in the spotlight and got his picture taken with him too. All of this action is done while they are all singing their parts without missing a beat. The camera returned at the end of the opera; at the close of the final song, Mr. Extra returned and took a picture of them all striking a pose.
The singing, of course, was excellent. Cenerentola had an awesome voice, with the sisters close behind. Some of the ensemble got a little off during the sextet in the second act, but c'mon, it's not like I could sing it any better! Almost flawless music throughout.
As much as I thoroughly enjoyed the opera tonight, though, what I took away was the intermission.
I stepped outside the Crooked Tree Arts Center for some fresh air and stood at the corner of Division and Mitchell. There, I saw a single star a little above the new stately library building. Polaris, beautifully situated. And I started thinking.
Some people exclude others, leaving them alone. Just like that star is alone. I am like that star.
But the star is not alone. There are other stars there waiting; I just cannot see them now. Millions of others will follow the first star into the night, where their light will shine more brightly because of the darkness.
It is only needful, for a time, that the star appear alone.
For one must lead.
Saturday, August 19, 2006
A good quote about being a man of good character where women are concerned
Found a good quote today. This is Professor Henry Higgins on why he is not a man of good character as far as women are concerned:
"I find that the moment I let any woman make friends with me, she becomes jealous, exacting, suspicious, and a ****** nuisance. And I find that the moment that I make friends with a woman, I become selfish and tyrannical. So here I am, a confirmed old bachelor, and likely to remain so."
Subscribe to:
Posts (Atom)
Posts
