I just want my printer to work again. Then I will be happy.
Try resetting your printers. Preferences> Printer & Fax> right click on the left side in the white square, reset printing system. Then add it again.
I just want my printer to work again. Then I will be happy.
That's interesting, I have not had this problem and I too am using a Time Capsule to backup my MBP. Did you do a clean install or an upgrade? Also, are you backing up wired or wireless?
This comment makes no sense. Do you not realize how much effort Apple has put into Mac OS X 10.6 and what it means for the future of the OS and desktop applications?
It is possible for a company to work on multiple projects in multiple market segments.
S-
I just want my printer to work again. Then I will be happy.
Try resetting your printers. Preferences> Printer & Fax> right click on the left side in the white square, reset printing system. Then add it again.
Please read this page carefully ...
http://arstechnica.com/apple/reviews/2009/08/mac-os-x-10-6.ars/5
..or my statement on this from a while back..
https://forums.macrumors.com/posts/8163208/
(you don't really need to run the kernel 64-bit on that system, not gaining you a heck of a lot in the grand scheme of things and leaving you open to 3rd party, etc. incompatibilities in the short term)
(I personally wrote in requesting that the older Expose style be brought back, at least as an option - if you feel the same way, jump on the bandwagon and write in about it. Hopefully we'll see it soon!)
Which you can check by simply entering the following line:+1. Or you can always edit /Library/Preferences/SystemConfiguration/com.apple.Boot.plist to make it look like this:
Code:<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyLis <plist version="1.0"> <dict> <key>Kernel</key> <string>mach_kernel</string> <key>Kernel Flags</key> <string>arch=x86_64</string> </dict> </plist>
If your system is able, it will then boot into 64-bit mode every time with no need to hold the keys down.
ioreg -l -p IODeviceTree | grep firmware-abi
Looks like it might be time to load up the version I bought. Just waiting for 10.6.1 to upgrade.
It seems odd that Apple are looking for feedback from only a small select 'invitation only' group..... why don't they try to gain as much information from their customers as possible. They could save time and money by just trawling through all the threads on the MacRumors forum !!
Damn, that was fast.
At the current rate, Apple could immediately cease OS development for a decade and still be ahead of Microsoft in the operating systems "race."
Now that we're all about printers . . .
My Laserjet P2015 works fine. Drivers included in SL already.
However, still seems to default to 600x600 dpi despite the ProRes 1200 (1200x1200 dpi) option being available and me selecting it. Seems like HP didn't go the whole nine with their drivers, either in SL or Leopard. Oh well, output still looks quite good, the best 600x600 I've seen from a Laser in its price range ($300-$400.)
Either that, or 1200x1200 looks exactly like 600x600, which I don't think is normal.
Unsure whether the HP toolbox software (tweaking output, ink density, etc.) works. Haven't tried that yet.
I've had the following problems on my Mac Pro (2006):
- My Mac Pro won't go into sleep mode. I can force it to sleep by using the 'Sleep' command in the
menu, but it won't do it by it's self. I have tried this on both a 10.6 upgrade and clean install and both have the same problem.
- On occasion I have no
menu bar after booting up.
- Some of my drives go to sleep even thought I have disabled the option in energy saver.
- A few crashes with iTunes and Safari.
- Occasionally get permission errors when syncing my iPhone.
The above issues have been experienced after performing a clean install. I originally did an upgrade but the machine was unbearably slow after the installation.
I haven't had a single problem with Snow Leopard on either 3 of my Macs but any update from Apple will be good.
You're all winding yourselves up for a big letdown if you think .1 is going to fix all your problems.
Which you can check by simply entering the following line:Which should return: "firmware-abi" = <"EFI64">Code:ioreg -l -p IODeviceTree | grep firmware-abi