Thanks for the link to the article on the DC Bus iPhone app (Cavan any relation?). I use the Fairfax Connector so it doesn't help for me, but I'm sure it is advantageous for some. I used the commuterpages with my WM phone (free), but it doesn't seem to be supported for the iPhone (Yet?).

As a scientist and a user of both platforms (I am not an IT person. I'm an untrained geek.), I don't give much credence to anecdotal information. I can usually match anecdote for anecdote with users on either platform.

I have a HP Scanjet 8250 (USB) sitting next to my MBP 15" that I can't use while booted in Leopard. I spent considerably more time than half an hour testing HP drivers, bonjour, generic printers, etc. only to discover it wasn't going to work at all. All the software loads fine, but the scanner won't work. The same is true for a desktop HP photoprinter (USB). I have to Boot Camp into XP to use either of these devices, which is an incredible cramp on the work flow. Ironically, I can print to a HP 5500 poster printer from Leopard, over Apple Talk or TCP/IP on a Novell and MS driven network; and print locally (USB) to an HP Laserjet 4050. Go figure.

I can list many other anecdotes, too, from both platforms. One of this weeks highlights on the Apple side was a newer iMac inexplicably loosing it's association with its Time Machine backup (over seven months worth). The Apple Care person gave me a telephony shoulder shrug and said start a new backup. On the Windows side it's an 'Add New Hardware' Wizard that won't stop trying to add a serial printer even after it's been 'told' what the printer is, that the drivers are loaded, and to stop 'asking.'

I thought I would come to the cguys listerserv and get away from the debate a bit (It does say on Kojo's site for guidelines for the listserv, "•The PC vs. Apple feud is tiresome and should be avoided"), but I guess this isn't the case.

So rage on, I guess. This scientist will hold his judgment until somebody comes up with some objective, substantiated, repeatable data.

--------------------------------------------------
From: "b_s-wilk" <[email protected]>
Sent: Thursday, August 06, 2009 1:14 PM
To: <[email protected]>
Subject: Re: [CGUYS] Ford! Chevy! Lather, rinse, repeat [Finally an FCC that earns its keep]

> It's your job to provide IT/network support.

Yeah?  So what?

Tom's point was that he would have to hire additional staff to handle PCs. Your experience notwithstanding, my experience proves him decidedly wrong.


Our businesses involve work other than IT. Your business is IT. Ours isn't. What's your point?

If we need a tech support, it significantly cuts into our bottom line, so it's best to have a network and computers that require the least amount support, and the fewest steps to complete tasks.

Example:
Today we were working with some sound apps that involve changing sound output device from internal to broadcast. On the Mac, I can switch on the fly from one output to another. On the Dell, it requires a reboot with the same device, wasting time and effort. I could list more examples, but the point is that it took about a half an hour to figure out the differences, and reset the Dell [no manual provided, had to search and download drivers from mfg.]. End result is the device is permanently attached to a Mac.

We don't 'schlep' to a Mac 'genius'. We rarely need the tech support in the first place, and a simple phone call, email, SMS, IM almost always get the answer quickly. We go to the Apple store to play with new toys, borrow their WiFi, buy new toys.


*************************************************************************
**  List info, subscription management, list rules, archives, privacy  **
**  policy, calmness, a member map, and more at http://www.cguys.org/  **
*************************************************************************



*************************************************************************
**  List info, subscription management, list rules, archives, privacy  **
**  policy, calmness, a member map, and more at http://www.cguys.org/  **
*************************************************************************

Reply via email to