All I can say is in answer to your question, "Can anyone install a printer driver" the day after I updated to 10.8.5 I downloaded and installed a Brother printer on a WiFi network connection with absolutely zero problems. My Macs saw the printer on the network and went through a "setting up the printer" process I don't recall seeing before and the printer, scanner, and fax all worked flawlessly. So yes, I can and have installed a printer.
That raises the question for me, what is different between our two systems. Just as a diagnostic, would you try something? If you do not have a "test" account with administrative priveleges create on in System Preferences > Groups and Users then logon to that pristine account and...
- Try to print to the printer. If that works then there is something in your user account that is somehow interfering with the CUPS print system. It would most likely be in System Preferences > Groups & Users > your account > Login items, where ~/ is shorthand for your user account look in ~/Library (Since the user's library is by default invisible you may have to get to that through Finders GO > Go to Folder... and type in ~/Library) then one of the following folders, LaunchAgents, LaunchDaemons, Startup Items. Don't delete the items in those folders but drag items out of them to the desktop, reboot, and test. If the problem still exists return the items to the folder it came from and repeat with the next item. If the problem goes away return the items to the folder one at a time until you find the culprit.
- If the first test reveals nothing, while logged into the Test account go to System Preferences > Print & Scan and delete all printers. Reboot and log into the Test account and Install the printers then test again from the Test account and from your regular account.
- If you are still getting garbage then there is something amiss in the System. Try unplugging all external devices including hubs but excepting the Keyboard and Mouse/Trackpad. Once again reboot and test from both accounts
- In the Library folder at the drive root look in the following folders, LaunchAgents, LaunchDaemons, Startup Itemsthe following folders, LaunchAgents, LaunchDaemons, Startup Items for potential culprits.
This is a long and tedious process, but it is the only way to positively eliminate some outside driver or softwre entity as the source of the problem.