6 Reasons I Chose A2Hosting
FTC Disclaimer: I'm a satisfied, four-year customer of A2Hosting and a proud member of their Affiliate Program. I'll make a buck or two if you purchase hosting via my site, so if you have a moral objection to helping me pay my monthly Netflix subscription, then by all means don't click my links. Either way, check out A2Hosting.
Anti-Disclaimer: My blog has had a long and proud tradition of sounding off about products that suck. Just this once I decided to get behind a product that I'm truly proud of and tell you all why I recommend A2Hosting's Shared Hosting package above the competitors.
Introduction
If one goes searching this vast Internet of ours for recommendations about cheap web hosting, one will be sure to drown in oceans of fake ratings and user reviews, not to mention affiliate links from folks who have never actually sampled a company's services or those of any of their competitors.
I've dealt with several cheap, shared web hosts from the largely unknown Global Internet Solutions (name intentionally left unlinked for your protection) to Danika Patrick's host-of-choice GoDaddy. But when I have the choice, I host with A2Hosting.com. This personal choice and my recommendation to my readers comes not from the promise of affiliate payments, but from four years of positive experiences with this company. Below are 6 reasons why I stand behind A2Hosting.
6. A2Hosting Watches & Listens
Up until just a few months ago I was running a now-defunct personal project called Sudoku Madness. This marginally-popular website was hosted on A2Hosting and hosted hundreds of thousands of unique Sudoku puzzles in a PostgreSQL database. My site became a small hit (especially with my sister's seventh-grade math class), which turned out to be a problem for other users who shared my server: my scripts were opening a new database connections on each request and not returning them for use by other users. A2Hosting didn't knock me offline as they had every right to do, but they immediately notified me that my PHP was running amock and proposed a fix.
A2Hosting solved a problem of my own creation and suggested a solution that kept me and their other customers online and happy. Plus they kept me earning literally tens of cents per week in affiliate income from that project! (Look for my money-making infomercial coming soon to QVC!)
5. A2Hosting Supports PostgreSQL
Many shared web hosts support only the typical LAMP development stack; but in addition to the traditional Mysql offering, A2Hosting also supports PostgreSQL. Attempting to debate the pros and cons of the two platforms is both out of this article's scope and risks inciting a religious war, but suffice it to say that Oracle's purchase of Sun Microsystems leaves MySQL's future uncertain so a choice in open database platforms can't be a bad thing.
I chose to use PostgreSQL on several of my projects, most notably on my Sudoku Madness site. That particular database housed hundreds of thousands of records and used home-brewed PGSQL procedures to speed up searches and puzzle creation. The site ran for several years largely unchanged, and speed and storage never became a factor.
My one complaint: A2Hosting's automatic backups include your MySQL databases, but at least as of a year ago, not your PostgreSQL databases. To the best of my knowledge, you'll need to set up your own backup schedule if you choose PostgreSQL (a good idea regardless).
4. A2Hosting's Server Rewind Feature
Whether you only host your own projects or resell hosting to clients, the day can and will come when you'll need a backup. There is nothing more embarrassing and damaging to your credibility than losing a client's site or database and not having a recent backup. Nobody is perfect. That's why pencils have erasers and decent web hosts provide backups.
I've tested A2Hosting's backup system on numerous occasions. The first was when my account was migrated to a new server and one of my databases was missed during the restoration (again, darn that lack of PostgreSQL backups!). With the help of A2Hosting's support department I was able to recover one of my manually created SQL dump files from the Server Rewind app and quickly get my site up and running again.
More recently a site which I inherited from another developer was hacked. The code for this site only worked when a certain directory under the web root had full write access by the Apache process and the client refused to pay for a rewrite. Suffice it to say, they eventually got theirs. I was able to recover both their site and their back-end database using Server Rewind, available through my management panel.
3. A2Hosting Supports Subversion
The day comes when a developer outgrows manually updating their websites via FTP. Fortunately A2Hosting supports Subversion over SSL, which provides you with secure version control of your code. They also offer CVS and Git hosting if Subversion isn't your thing.
I personally use A2Hosting's Subversion hosting for all of my projects that aren't based on another project (Wordpress, etc), even development projects that aren't hosted on A2Hosting. After committing my code to Subversion I SSH into my server and run a script that pulls the latest changes from the repository. Using version control to manage your sites saves you time and bandwidth by only uploading changed files, and it gives you the power to quickly undo a bad update.
2. A2Hosting Has Never Eaten My Domains
Granted, I've never given them the option. I've previously lost domains to other shared web hosts who offered me cheap domain registration but refused to release my domains after I became disgusted with their service and wanted to move.
On the other side of the coin, I've transferred a number of domains to A2Hosting and they've always offered assistance in this frustrating process when they can.
1. A2Hosting's Support is Unmatched
I can't begin to explain how helpful A2Hosting has been to me over the past few years. They've always responded quickly to my support requests no matter how inane, and they've saved my ass from embarrassment and lost clients on a number of occasions.
When I developed my first site using PostgreSQL, I uploaded my scripts to A2Hosting only to find that they had not enabled the pdo_pgsql extension which my code was completely dependant upon. Their support people had the issue resolved within hours, which I consider more than acceptable for a shared host, when other hosts have rejected my requests across the board for common PHP extensions in the past.
More recently I had an issue with mail from my domains being rejected. This is the sort of issue which truly tests a company's metal because there are so many possible points of failure. Many companies will play the blame game for days or even weeks with email issues, insisting that the problem is "on the other end." A2Hosting has never been afraid to dive in, and resolved this issue by the end of the day.
Summary
Though A2Hosting remains competitive in price, speed and options, their edge comes from their fanatical support. Though I award them zero points for originality by naming their support wing the Guru Crew, those are the folks who have made me a committed and loyal customer of A2Hosting. Choosing a web host is a lot like choosing car insurance: you can pay your premiums for years and have no concept of a company's quality. You find out when it's too late, and that's when A2Hosting truly shines.
Rexton and Siemens Connexx Module Freezes NOAH System 3
Over the weekend I worked on upgrading several laptops from Windows Vista to Windows 7 and updating NOAH System 3 from version 3.6.1 to 3.7.0. Across the board we experience issues with the Connexx module hanging up and crashing NOAH System 3. The problem, I found, was with the database used by the Connex module.
If you experience this problem, try the following.
- Close NOAH and any modules you might have open.
- On your Status Bar (the block in the bottom right-hand corner with the icons), locate the SQLAnywhere icon, which should look like an orange and white lightning bolt. Right-click the SQLAnywhere icon and select "Shutdown" to close the database.
- Open NOAH, and try any of the CONNEX modules. The modules should start the database automatically and then open successfully.
- If this works, delete the SQLAnywhere launcher from the Startup folder on your Programs menu.
This solution worked on my clients laptops and may not work for you. I'm not affiliated with HIMSA, NOAH, Siemens or Rexton. Though I will try to help if you post a question in the comments, I don't have much knowledge specific to this software.
Agent2.AGCV Trojan (kbdsock.dll)
I'm in the process of patching up a particularly nasty virus called Agent2.AGCV. Part of the virus resides in a file called C:\windows\system32\kbdsock.dll. What I noticed is that when the deleted the file or allowed AVG to clean it, it would reappear after the next reboot.
Prevent the actual virus file from loading by booting up to a Windows installation CD and entering the Recovery Console. Copy another DLL file over kbdsock.dll and reboot. The file you just copied will be loaded instead of the virus.
Zend_Http_Client_Adapter_Socket Problems
While running my unit tests for an application I'm developing, I noticed that certain web service components were intermittently failing. The failure was caused by irregularly formed XML responses from Amazon's Web Services. The failures occured as Exceptions from within the Zend_Service_Amazon component, but upon further inspection I was able to discover that the HTTP Adapter being used from within Zend_Service_Amazon, which is by default Zend_Http_Client_Adapter_Socket, was not returning the entire stream from Amazon. After I switched adapters to Zend_Http_Client_Adapter_Curl, my unit tests began running without fail.
I was not able to find any information about the problem from the Zend Framework Issue Tracker, so I have no way of knowing at the moment if there is a bug within the Socket adapter, or something with my computer or my Internet connection.
What To Do When Firefox Forgets It’s Own Age
Yesterday I dealt with some issues that were plaguing my cousin's computer, among which was the odd fact that both MySpace and Yahoo Mail would not allow him to use their sites because his version of Mozilla Firefox was too far out-of-date. The problem was, he was using the most recent version of the program, Firefox 3.5.5, which I confirmed by checking the "About" window under the Help menu in his browser.
Firefox and all other web browsers tell the web pages you visit what browser and version number you are using by sending something called a User Agent string. My suspicion was that Firefox was reporting the wrong User Agent string, and this suspicion turned out to be correct.
First attempt to resolve the issue by turning off or uninstalling your Firefox plug-ins, one-by-one. Chances are, one of your plug-ins corrupting the User Agent string.
If removing plug-ins doesn't fix the problem you can try to manually check and modify the User Agent settings by typing the address "about:config" into the Firefox address bar and checking the settings under "general.useragent" for an incorrect browser version.
Stop Using Limewire!
I have no physical proof to show you and no statistics to back up my claim, but I highly recommend that anyone intending to use their computer for a legitimate purpose uninstall and never again use Limewire. I fix several computers a week that have become infected with the FakeSecScan (a malware application that masquerades as an antivirus app), and about 75% of the infected machines are running Limewire.
Limewire is a breeding ground virus activity. Uninstall it immediately, and if you insist on engaging in risky behavior online, learn to use BitTorrent.
KiXtart Fails to Delete Network Drives
I recently ran into an issue with a logon script written in KiXtart failing to disconnect network drives. I can only guess from the dozens of forum posts I found online that this is a common problem that scripters run into. Luckily there is a simple solution.
The Problem
When you issue a Use "<drive>" /Delete comment from KiXtart or a NET USE <drive> /DELETE batch file command, the drive letter in question isn't actually deleted from My Computer. Instead, the drive will be listed as a Disconnected Network Drive and when opened it will automatically reconnect. This happens when the drive was initially connected using by mapping the drive manually and selecting "Reconnect at logon" or by executing one of the following commands:
Use [drive] /Persistent
NET USE [drive] /PERSISTENT:YES
The Solution
Deleting persistent drives may require that you use the /Persistent switch when you execute the delete command. You can delete a single network drive using one of the following commands:
Use [drive] /Delete /Persistent
NET USE [drive] /DELETE /PERSISTENT:YES
Or alternatively, you can delete all network drives at the beginning of your script using one of the following:
Use * /Delete /Persistent
NET USE * /DELETE /PERSISTENT:YES
Dell ControlPoint vs. Sleep and Standby Modes
Today I was tasked with preparing two new Dell Latitude E6500 laptops for deployment with two administrative employees. Between software installs both laptops went into Sleep Mode. One laptop would not return from sleep mode at all, or at least the display didn't. The other laptop returned from Sleep Mode, but the wireless network connection never came back.
The problemeturned out to be the Dell ControlPoint software which came installed on the laptops. Though ControlPoint has one or two neat features, I decided to uninstall it from the machines anyway. After all of the ControlPoint applications were removed both laptops returned from Sleep and Standby modes without any issues.
Hopefully this helps somebody! If anyone finds a specific setting within ControlPoint that can be changed to solve the problem please feel free to post it!
7 System Building Tips
I've built hundreds of PC's in my day. That includes dozens of one-off systems that I've configured and assembled for my own use as well as for friends, family, and customers. It also includes batches of new systems that I build during the summer at my full-time job. Below are just a couple of tips that I've picked up along the way that make the system-building process as painless as possible.
1. Plan Ahead
Many retailers provide reviews, which are invaluable when choosing hardware.
Building a desktop computer isn't rocket science, but it's not work you could assign to a team of chimps, either (with all due respect to the intelligent and majestic chimpanzee, of course). Planning ahead ahead before you go full-force into system building will pay off later by saving you time, money, and frustration.
Research your components. Read blogs, forums and industry sites like Tom's Hardware to find out more about your hardware and whether or not your components will "play nice together." Google is your friend at this stage of the game. Verify that each component has drivers available for the OS you intend to install before you make a purchase. Make sure your power supply provides enough power to support the rest of your hardware. Make sure your motherboard provides the correct ports for any other hardware and adapters you intend to install.
I also recommend reading user reviews for each component on sites like New Egg, Amazon, or MWave. Users tend to write a review when they have a really good or a really bad experience with a product, so they can be a wealth of information and have saved me from countless bad purchasing decisions. Bottom line: Plan, plan, plan!
2. Plan Some More
Once your components arrive gather everything you need and plan the order in which you will install them. Have a trash can handy to immediately discard packaging so it isn't taking up space in your work area. This is the order in which I generally proceed (though your preferences may vary).
- Open and clear the case. Manufacturers will generally pack any extras inside the case, including wires and a bag of hardware. Sit all these items to the side, and position all cables (power supply cables, front panel header wiring, etc). so they are hanging over the outside of the case. You should have a clear view of the chassis where the motherboard will be installed.
- Prepare your case to accept the motherboard by installing the brass risers in the appropriate configuration. Replace the metal panel in the back of the case with the one that matches the built-in components on your motherboard.
- Install the motherboard.
- Connect front panel header wires. This includes the power button, reset button, LED lights, and front USB and audio ports. It is easier to deal with these small wires now than trying to fat-finger them around a bunch of other components later.
- Install memory.
- Install CPU and CPU fan.
- Install drives.
- Install PCI/PCI-X/AGP adapters (video, audio, etc.)
- Connect all power cables.
- Cable Management (see below).
- Plug-in and test. If you need to make adjustments, your case is still open and components are easily-accessible.
- Close the case.
3. Pick a Quality Case
This is how your case should look prior to installing the motherboard.
A good case doesn't necessarily contain 10 fans and light up like the aurora borealis when you hit the power button. Ventilation is incredibly important, but from a system builder's perspective so is ease of assembly. Make sure your case provides plenty of working room. It's not hard to damage a motherboard and other components when you have to angle them awkwardly to get them into the case.
The following outlines the "no-frills" criteria that I have for cases. These are just choices that I have found to be ideal and they may not fit your situation.
- Front USB and audio ports. (If you don't get it now, its not so simple to add later)
- Front ports should be located high on the case. When placed on the floor, devices plugged into USB ports low on the case will get kicked and possibly destroyed.
- No hinged doors unless you have a very good reason for having them. Plastic doors will break quickly.
- No ventilation shafts. Feel free to disagree but I remain unconvinced that plastic ventilation shafts above the CPU do anything other than take up space and slow you down.
- Simple drive access. There are many ways that manufacturers can accomplish this (rails , lock-in drive trays), but if I have to unscrew and remove an additional piece of metal to get to my drives and swap them, I'll look for another case. You should be able to swap drives without disconnecting other wires or hardware.
Note: You can solve a lot of overheating and ventilation problems in your case by cleaning out your fans, adding new fans, or simply moving your tower to a location where it can breath.
4. Use a Magnetic, Manual Phillips Screwdriver
The Magnetic Phillips Head Screwdriver: One tool to rule them all...
In most scenarios a Phillips head screwdriver is the only tool you will need to build a system. I say magnetic because you will drop screws and they will find their way to the most inconvenient crevice in your new case that they can! Don't worry about the magnetism affecting your hardware. It's simply not strong enough to harm your hardware, and I don't know any other system builders who don't use one.
I say use a good, old-fashioned manual screwdriver instead of an electronic screwdriver or drill because most electronic devices are simply too bulky to use effortlessly inside a computer case. Besides: if you're not careful you risk stripping out or severely over-tightening your screws, both of which will make adjustments a pain in the future.
Note: You may also need a flat-head screwdriver for installing and adjusting certain types of CPU fans.
5. Take Anti-Static Measurements
Whether you ground yourself with an anti-static bracelet or an intricate alligator-clip and wire system, make sure you are properly grounded to avoid shocking your new components with static electricity. Damage caused by static is difficult to diagnose but very simply to avoid.
6. Don't Force Anything
Yoda Cat says, "force components you will not!"
If screw doesn't seem to fit or if a component doesn't seem to snap into location easily, do not force it. Step back from the situation and analyze it for a moment. There are usually at least two different sized screws used when assembling a computer, and you may be using the wrong one. If your memory doesn't seem to snap in, it may be backward or you may be trying to install DDR 1 memory into a DDR 2 slot. If an IDE cable doesn't want to push into a port with ease, try flipping it in the other direction.
Though occasionally you may encounter a screw hole bored slightly too narrow you should always think twice about forcing it through. You could strip out the hole or the screw, making removal of the hardware difficult later.
Forcing components and connection wires can easily damage pins and leads and ruin expensive hardware. Think about the situation before you manhandle components or use other tools to force a solid connection.
7. Practice Good Wire Management
Practicing wire management prevents mistakes and make maintenance tasks simpler.
In my opinion there are no hard and fast rules as to how you should effectively manage the cabling inside a computer case. When building systems I inevitably find that I have several twisty-ties left over from the component's packaging, and I save them for tying up and organizing wires. Most cases will provide holes along the edges where a tie can easily be inserted to wrap up and tighten wires. Make sure that all wires and cables can reach from their origin to their destination, but keep the slack far away from CPU and case fans. It's best to handle this before you put the case back together, otherwise you will waste your time later reopening the case to make adjustments.
Note: Though the plastic fan blades in a PC probably won't damage wires if they strike them, stray wires can cause fans to stop working and thus overheat and possible damage your CPU.
Summary
With a little bit of planning and some common sense it is easy to configure and build a stable desktop computer. Plan ahead of time so you know you are buying reliable components that work well together and support the operating system that you intend to run. Keep organized from start to finish: lay out all of the components and tools you will need, keep your work area clean by throwing out packaging and other garbage as it accumulates, and manage the wires and connections inside your tower by tying them off as you build. Use the right tools for the job, avoid static discharge, and don't force connections. Using this simple advice you can fully assemble a stable desktop PC within 25 minutes of receiving the components.
Questions or comments about this article? Or better yet, do you have your own system building tips to share? Leave a comment below! We'd love to hear from you.
Going 64-Bit, Revisited
In my last post I expressed my frustration with HP's lack of 32-bit OS support on a laptop purchased by one of my clients. I received some constructive criticism on that post that I think deserves special attention.
ArunHorne Expands my Vocabulary: "Luddism!"
A user name ArunHorne on Dzone made the following comment:
If you are arguing that manufacturers should not have switched to 64-bit operating systems this is Luddism to the extreme. If you really need to use a 32-bit OS you could always try something like VMWare to run legacy software.
My post wasn't intended as a rant against 64-bit technology. Obviously my style of writing needs some adjustment because I didn't get the point across that I was trying to make. I did try to make it clear that I was talking specifically about the lack of 64-bit support for software and devices used in niche markets such as that of my customer, a hearing specialist.
I'm all for moving ahead with 64-bit architecture, and I don't think I made a case against it in my article. I simply live in a reality where I (and my customers) cannot embrace the 64-bit revolution. My complaint was that HP has locked us in to using a 64-bit operating system on a laptop that should have no problem supporting a 32-bit OS.
JP Says: We Got Exactly What We Paid For
A reader named JP made the following comment:
So, the technology should not evolve because there are some legacy applications out there? If the laptop had windows vista 64 bit as advertised (and they DO advertise it), it is a well known fact that you won’t have 16 bit support. Its not like there aren’t any laptops with xp or vista 32 bit. So, if someone made an ignorant choice, now is the manufacturer’s fault?
Btw most of these issues can easily be solved using vmware, virtualbox or something like it. If the laptop’s cpu has VT support, a vm will be a lot faster than a 4 or 5 year-old computer.
Should Legacy Applications Hold Back Technology?
Certainly not. However on behalf of my clients and as the person who supports them I have to ask: how is this our choice? Again my complaint was never with changing technology, it was with the fact that HP was locking us in to a 64-bit operating system when many industries have yet to adopt it.
The Customer Knowingly Bought 64-Bit
JP makes a good point: the OS that an OEM system runs is advertised in it's description and so we can't plead false advertising regarding the purchase.
Had the client asked me to select a laptop for them this system would have been red-flagged and there never would have been an issue. Unfortunately I can't stop anyone from making a bad purchase if they don't ask for my advice ahead of time; I can only help remedy the situation after the fact.
Again, HP said they would not support the laptop if we installed a 32-bit OS (which the hardware supports). Why should installing an operating system 100% compatible with the hardware I'm installing it on to void my warranty? Fans of Linux and other open source operating systems should be very scared of this line of thinking.
Another point to be made is that 64-bit versus 32-bit means nothing to the average consumer unless they have memories of the video game console wars where we all just assumed that "more bits is better." Even if my client had read "Vista Home Basic 64-Bit Edition" they wouldn't have had a clue what it meant.
Virtualization as a Solution
JP as well as other users posed virtualization as a solution to this issue. It was noted that I could easily use VMWare, VirtualBox or VirtualPC to run a 32-bit OS on top of the 64-bit operating system. Taking only the technology involved into consideration this is certainly one possible solution, however there are other factors involved.
The first kink in this plan is that my clients are not technically inclined individuals and don't have full or even part-time IT support. I come around about once a month to help with IT issues, so adding the (what we might consider minimal) complexity of virtualization software and a second operating system on top of a technology they already find a little confusing isn't a viable option for either one of us.
The second issue is that, from my understanding of Microsoft's EULA, they'd have to pay for a second Windows license to run the OS under the virtual machine. I'm against this simply on the principle that I don't think someone should have to pay for a second operating system just to make their computer work the way that it needs to.
Third and possibly most important issue is that I'm not sure how well any virtualization technology will support their hardware. I have a fair amount of experience with VirtualBox and VirtualPC but not VMWare. Though both programs seem to support serial and some USB communications, I required flawless USB support as well as Bluetooth, which I'm not sure that either one supports. I know someone will feel free to correct me if that's not the case.
Gene: You Made a Bad Purchase, Deal With It!
Gene writes,
Sounds like he just bought a laptop that wasn’t suited to the task. Would you have blamed HP if the user’s software was all Linux-based? The first step in buying hardware is making sure it will support the software you need it for.
I completely agree with Gene. It was a poorly thought-out purchase and we shouldn't hold it against HP that my customer bought a laptop incapable of doing what we wanted it to do. In the future I'll encourage (or insist) my clients include me in all computer purchasing decisions so we avoid this type of complication.
KL Says: Your Story Sucks!
A reader named KL says,
Sorry, but this is a terrible story for the title. I thought it was going to be an analysis of the state of 64 bit systems, etc, etc. But it’s a story about someone purchasing (most likely accidentally) a 64-bit computer, and you (the author) are saying it’s the manufacturers fault? This article has little relevance to 64-bit architecture.
It’s like saying a man went in to buy a Diet Coke, but instead walked out with a regular Coke. Is Coke jumping the gun and adding sugar unnecessarily?
The Problem is, it's My Story KL!
All I have to say is this: who writes this blog? Me, and not you? Because if this were my blog I'd tell you that I wrote exactly what I advertised in the title and description. Remember the description? The one that said "If you intend to run niche software or devices, think twice before switching to a 64-bit operating system?" Remember how I then wrote about switching to a 64-bit OS to run niche industry software and devices? Remember how I then wrote about how that failed? Yeah, I don't remember that either. Just kidding KL. I kid because I care.
All ball-bustery aside, there isn't much I can do about the fact that KL wanted to read about something else, other than point him in a different direction.
Diet Coke Analogy
Ignoring the distinct possibility that KL is a Coke employee hired to keyword stuff their brand into other people's websites, the analogy still doesn't make sense to me. I'm not buying a can of Coke. I'm buying an expensive piece of hardware that is, technically speaking, is completely capable of running the software and devices that I need it to run. Yet the manufacturer is telling me that I cannot. Elaborating on KL's analogy, it's more like Mack Truck telling Coke that the warranty on their 18-wheelers are void because they hauled Diet Coke, when they clearly marked the truck with regular Coke branding.
I admit this analogy makes even less sense. But I entertained myself for at least three minutes while thinking of it, so I consider it a great success.
Bubak: Did You Even Try to Make This Work?
Finally, a reader named Bubak writes:
Did you actually __tryed__ installing those apps? 32 bit emulation is very good and it may work fine.
Also upgrade to Windows 7 may be cheep solution.
I tried knowing that I was going to fail. It is absolutely correct to say that the 64-bit editions of both Windows XP and Vista have impeccable 32-bit software support. I've been running 64-bit operating systems exclusively both at home and at the office for about two years now without a single software issue. Drivers, however, are a different story entirely.
Without exception you cannot install a 32-bit driver on a 64-bit version of Windows, and so you are at the mercy of your hardware manufacturers (or a clever, reverse-engineering third party) to release a 64-bit driver. Windows 7 has some features that will solve backwards compatibility issues with software designed for older versions of Windows, but I don't think it has any solutions that bridge the gap between architectures.
Other Affected Industries
Though the client I was discussing works in the hearing aide sales and testing industry, his is not the only industry that will have problems upgrading to a 64-bit operating system. I also work a full-time job as an IT Specialist at a vocational school, and I've run into similar issues there with hardware and software in the following industries: dentistry (drivers for computerized and network-enabled imaging and X-Ray machines), machining (drivers for routers, rapid prototyping devices, and laser engravers), electrical engineering (PLC interface drivers), and all facets of the automotive industry (drivers for vehicle diagnostic links).
Summary
Obviously my complaint that OEM's and hardware manufacturers are moving at a much faster pace than industry was missed by most of my readers and taken as an attack on progression toward the future of 64-bit computing. I'd love for that to happen, but I have to live in a reality where that might not occur for another three to four years.
In hindsight it was probably a mistake to post this piece on Dzone, where the audience is highly technical and naturally wanted to solve the problem by throwing more technology at it.
Thanks to all of my readers who left positive feedback and suggestions on how to overcome my 64-bit dillema.
To those who left comments treating me and my client like idiots, I admit I don't know everything, and compared to some of you I might know much at all. But I do know that if I approached my clients with the same "Big Man Behind the Keyboard Syndrome" with which some folks communicate, I wouldn't have clients very long at all!
Trusted Affiliates
Categories
- Beginner
- Complaint Dept.
- Courses
- Crash Course: Home PC Maintenance
- Developement
- Expert
- Hardware
- Intermediate
- Internet
- LAN Administration
- Networking
- NOAH
- OS Deployment
- PHP
- PostgreSQL
- Product Reviews
- reviews
- Scripting
- Security
- Site News
- Software
- Software Updates
- Support
- The Basics
- Videos
- Web Browsing
- Web Design
