Saturday, September 25, 2010

Money for Nothing

When you give your two teenage sons $140 in cash to pick up their back-to-school items, including a scientific calculator, you expect to get some money back.  Then again, maybe not... "ok, take my debit card with you, if for any reason that's not enough money put the balance on the debit card."  The boys proceeded off to Staples armed with cash and card.

About a half hour later, Mikey sends me a text - "good thing you gave us the card"... "why? what's the tally?"... "the calculator alone cost $120"... ouch, da pain, I say to myself.  In my mind I make a mental note to search eBay with the calculator model # for a better price. We'll return the original to Staples. The boys come home a while later and proceed to hand me $84.12 in change.  "What's this?"  "Your change" "Nice, you didn't get the calculator?"  "yea, we got it"  "Lemme see the receipt"  The total read $195.88.  The receipt also shows two debit transactions of $140 cash for $280 total.  Hmm... let's see, 280-195=85... ah, I see what happened.  "Didn't you understand something was wrong when they didn't charge the card anything?"  Jack: "Well, I didn't really think about it when she gave us the change.. Mikey: nice, huh?  Betcha never thought you'd get money back!"  Sigh... "Well, we'll probably need togo back to return the calculator anyway, I'll give them their money back then, and have them charge the card properly."  "Why would you do that?  They'll never know."  Sigh (again)...

He was right, they would never know.  It was a valid (albeit incorrect) transaction.  I would know, however.  Chance for a lesson.  "Yea, but I would know.  That's stealing.  We don't do things that way in this family."  Point taken.  Nods of understanding from the boys. Ok, so time to head back to Staples... the Manager was grateful, albeit a bit bemused.  It was comical when the Manager struggled completing the transaction, the POS software had no mechanism for handling the return of lost money.  Eventually I received two more receipts, one to back out the original transaction and another with the debit card charge.

Seems to me a flag should have gone up during the original transaction when the $140 cash was logged twice... how many companies are losing money with these entry mistakes?  Or worse yet, how easy it for an employee to run a scam like this with a friend?

Tuesday, September 21, 2010

Blue Screen of Death

The Blue Screen of Death (BSoD) visited my laptop last night.  If you're unfamiliar with this surprise visitor, it's a disturbing crash of the Microsoft Windows operating system;  in my case, Windows XP.  Officially known as a "Stop Error", it's sometimes related to recent driver updates.  With the age of my laptop (2002), I'm thinking it's more likely related to a hardware or RAM failure.  The error will cause the operating system to put the memory data to a disk file, or "dump" file.  These files are usually placed in the C:\WINDOWS root directory.  Look for the file(s) with the .dmp extension.  I'll take a closer look at the dump file if my quick fix doesn't do the trick...

When I investigated the error code on the screen, it referenced the win32k.sys file.  Not good.  Per the Microsoft Technet reference library, the win32k.sys is part of the kernel.  It could be the file itself is corrupted.  So here's what I did, I renamed the file win32k.old (located in C:\windows\system32)... in essence I deleted the system file.  Many times when a system file is deleted in Windows, the operating system will automatically create the missing file.  In this case, XP recreated the file for me and I haven't experienced any further problems.

We'll see what happens, if it happens again I'll be taking a close look at the dump file.  In the meantime, I will make sure I have a full backup of my laptop's hard drive ready!