Skip navigation

Tag Archives: frustrating

“Well, if we’re all done, I’ll just make myself scarce.”  I don’t know where I picked up the expression, but it’s really cute and gets a chuckle now and then.  In a more serious light, though, “making one’s self scarce” is exactly what I’m doing with phone calls, starting today.  Now, me being a small business owner may incite much questioning about this new policy.  Doesn’t a good business owner answer the phone and talk to customers?  What could possibly be the reason behind this?

There is an article that covers this topic well which deserves an honorable mention: Should You Turn Off Your Telephone? Now I’ll answer the question about why and how I am getting away from the telephone.

I have access to three professional telephone numbers: two at the shop which are daisy-chained together by call forwarding, and my own cell phone.  Both sets of phones have voicemail at the end.  Well, had voicemail.  About 15 minutes ago, I cut my T-mobile voicemail service off completely.  Every time I made a voicemail greeting, it would politely recite the shop phone number, insist on calling that number, texting, or calling back in 10 minutes, and explaining what to press to unblock a call, followed by a request, then a demand, to not leave voicemail because I won’t get it.  That request was not respected at all, and my phone would constantly blip up voicemail notification reminders despite my explicit demands to simply wait on a call back! Where did people lose their ability to understand basic English, and to respect my explicitly spelled out request and warning that I don’t check voicemail?

I felt disrespected beyond belief every time someone left a message.  It’s like they said “okay, I’ll leave one anyway because I don’t give a damn about what YOU want, Mister Smarty-Pants Business Owner!”  It’s like someone else spitting in my face.  There’s no excuse for it.  Nowhere in the realm of human decency is ignoring an explicit request even remotely close to existing, yet people do it daily.  I’ve come to realize that many people simply do not consider the human factor of people in business.  The reasons are obvious, but the most significant one is that each ten-minute conversation to them is one ten-minute conversation, while to me it’s just one ten-minute interval in a huge flood of calls that eventually ruins almost half of my potential work time per day.  I need that time to grow my business, write some software, redesign the website, print business cards, and things like that, but instead it is completely drained away having conversations that my technicians could easily handle if callers would stop demanding to talk exclusively to me for anything and everything under the sun.

I want to be available to help everyone, but I am being forced to come to terms with the fact that I am one person with only 16 hours a day to do everything that must be done.  I understand now why corporate types rarely talk to customers: it’s simply not possible to do that and still get their own jobs within the company finished too.

I have decided that I must take charge of my time.  I must manage my time and treat it as the most precious resource in this company, as well as in my life.  It is limited and non-renewable, and I need to make all of it count for as much as possible.  If that means making a customer upset because they can’t speak directly to me, then so be it.  If a customer would refuse to do business with my business simply because they can’t talk directly to me whenever they feel like it, then I wonder whether they are the kind of customer we are in business to serve.  I hired and mentored a team of professionals so that I could extend my capabilities to more people, and it is extremely important that customers take advantage of their knowledge and willingness to help.

Not to mention the fact that some work might actually get finished around here now…

Advertisements

UPDATE: I found a solution.

I changed my Sylvania G (original, non-Meso) netbook to Windows XP/Linux dual-boot to test some software I’m working on, and discovered that while Windows XP certainly does boot and run in general on the G, some kind of system timer or timing loop is severely out of whack!  I wanted to use my little G as a portable gaming machine from the Windows XP install, and to my horror, ZSNES couldn’t decide what speed it wanted to run!  Now, I’ve never had a single issue with ZSNES on any computer I’ve ever tried it on, even preferring the Windows port of it over the Linux native one, and not once has a problem existed with ZSNES that I couldn’t find an easy fix for, until now.

I’ve been researching the matter and gathering evidence, and I may have a potential answer to the problem.  Linux requires activation of the VIA C7 Enhanced PowerSaver module e_powersaver to clock the VIA C7 CPU properly between 400 and 1200 MHz; apparently the default speed of the CPU is only 600 MHz instead of 1200 MHz, because Linux installs without e_powersaver and Windows XP report a ~600 MHz processor where a 1.2 GHz one exists.  Here’s the extremely weird part, though: if I check the System control panel shortly after bootup and read the clock speed, sometimes it registers a clock speed of 198 MHz (about 200 MHz) which isn’t even one of the ACPI P-states for the VIA C7-M 1.2 processor.

I’ve unlocked the Windows HAL options (I’ll post how to do that at another time) and switched between ACPI Multiprocessor PC (the default for the image I used) and ACPI Uniprocessor PC and MPS Uniprocessor PC, all of which use the local APIC for IRQ routing but the MPS variant of which doesn’t theoretically touch ACPI.  Nothing seems to have helped.  I have two working theories as to what’s going on here, and how it might be fixed:

  1. A calibration loop in Windows a la BogoMIPS in Linux is being screwed up by the VIA C7, or
  2. The VIA C7’s PowerSaver feature is ignored or incorrectly used by Windows (via generic ACPI P-states) and it’s throwing off some kind of timer that ZSNES relies on for proper emulation of the 65816 CPU and SPC audio processor.

So far, I haven’t found a solution to this problem, and Sylvania’s site is extremely unhelpful, with only Windows drivers and a new version of gOS, but no BIOS updates or further information.  I’m looking into the technical stuff on the VIA c7 now, and it looks like the solution (assuming Windows isn’t doing something sinister) lies in clever manipulation of the C7 model-specific registers (MSRs) that control the processor’s power state.  If ZSNES is mis-calibrating some kind of tight internal timing loop because of some kind of CPU clocking issue, then tweaking the MSRs may be the solution to the problem.  Unfortunately, I’m no Windows developer, so I’m not certain how I should approach the problem.  I don’t think it’s isolated to ZSNES either, but I don’t recall what I saw that justifies that belief.  In any case, I’m working on it.  It’s just one of many pesky projects I’m hitting my head against at the moment.  We’re still working on that remote access software package; in fact, someone found our site and called us, and I had to sort of turn her away.  It’s all a bit behind schedule, and there’s not really much I can do to make things proceed any more quickly.  Stay tuned…

Greetings! This article has been moved to the Tritech Computer Solutions page called Fix for STOP 0x0000007E Blue Screen on AMD Platforms. Please update your links and bookmarks to reflect this change.

(If you get a STOP 0x0000007E error after upgrading to an AMD platform from an Intel platform, i.e. replacing an Intel-chipset motherboard with something like a VIA or AMD or nForce or ATI chipset for an Athlon64, here’s a little hint that’ll help you avoid a complete reinstall from scratch: It’s the “intelppm.sys” driver.)

%d bloggers like this: