FarmerPete said:
Someone suggested I get a PowerBook, and I said that I already have a laptop that is more than adequate, I don't really need another one.
Really? So you're saying that the laptop you have is adequate for learning to support Macs?
Someone who says that they want to support Macs isn't going to gain any experience with a system sitting in the corner in their home.
If you are really looking to learn, a PowerBook or iBook would be ideal for you. It would be a system that you could take with you to learn on in your spare time... and better yet, a system that you could connect to the network at work to see how to actually solve the issues that the people you'll be supporting are going to run into.
Personally, the $500 to $1200+ that you are planning on spending on a Mac is more money than I have spent on any of my systems. If I was in your place I would buy a used iBook for under $400 and an old PowerMac G4 for under $200. The iBook would be great for testing things at work and getting used to the environment and the PowerMac is an easy system to break down, put back together and experiment with.
I just thought instead of throwing myself into a world that I don't understand and being 100% alone, I would invest another $25 on a book that could help me. When I learned C++ I didn't try to do it on my own. I went out and bought a book. But since I already knew other programing languages, I found a C++ book that showed more of the context than the logic. I didn't need a C++ book that was aimed at people who didn't know how to program at all. Getting the more specialized book saved me a lot of time and reading. I had hoped that there was a similar scenario with books on Macs. Since I wasn't able to find one myself, I figured I would ask a group of people that might know of one. Apparently such a book does not exist.
There are plenty of books out there... I have hardware service manuals, developer notes and user guides on systems going back into the 80's. I have operating system references for just about every version of the Mac OS ever made. I even have the original (flawed) troubleshooting guide that Apple gave out to it's internal support personal for Mac OS X when it was first released.
And what did all that cost? $0.00
... well, except for the cost of printing and binding some of the materials at Kinko's.
There is nothing stopping you from getting any of this stuff... except for your need for a "magic pill" solution. You'll spend more money and learn less following the path you've set for yourself.
In the PC world, the answers are always right there. PC support people are a dime a dozen.
I come from a research background in mathematics. In the area I was working in there weren't any text books, there weren't any classes, it was new mathematics that I was learning and using to create new mathematics at the same time. In that environment, there are no safety nets. You can't ask for help and the answers are never in the back of the book.
When it comes to computers, I like mine like I like my mathematics... as far from the norm as possible. I use Macs because they are frontier computing, I use Rhapsody, OPENSTEP, IRIX and Solaris because they are even more fringe than Macs (sometimes the Mac community is a little crowded for me).
It looks like you are looking for easy answers. The problem is, even if you get them... you won't actually get them. I could point you in the direction of a wealth of knowledge on Macs... but you wouldn't be willing to put in the effort to actually learn the stuff, so why should I waste the time to show you?
The reason I come to boards like this one is not to ask questions (I don't think I've ever asked a Mac question in a post)... I'm here to practice helping support people and to see what types of support issues are popping up with Macs in general.
You want to learn how to support Macs? You could start by looking at posts that are made here and trying to figure out what the solution to people's problems might be. Odds are that the requests for help you see here are going to be very similar to what you would see in the field.
You can't find that type of thing in a book.