Odd Manual "Sleep" Behavior

At the end of every day I restart my iMac and then manually put it to sleep (via drop-down Apple icon). Computer is programmed to wake at a fixed time each morning (works perfectly).
Commencing about 3 weeks ago (still using 10.6.2), the iMac would immediately "wake up" after "sleeping" for only about 4 seconds. A second attempt at "sleeping" is successful! This phenomenon would occur about 50% of the time.
After installing 10.6.3 (apparently fault-free), this annoyance (that's all it is) has continued.
Any ideas?

Well... I tried your suggestion, but "sleep" worked perfectly!
When it starts back up on its own volition is quite unpredictable. In the past 3 weeks, I'd say it has occurred about 50% of the evenings.
Anyway... here is last evening's log. Can you decipher the problem?
4/1/10 7:35:02 PM 1PasswordAgent[245] Shutting down 1PasswordAgent 3.0.9 #30535 built Feb 22 2010 12:27:04
4/1/10 7:35:02 PM shutdown[637] reboot by normankhester:
4/1/10 7:35:02 PM shutdown[637] SHUTDOWN_TIME: 1270168502 591638
4/1/10 7:35:02 PM kernel Kext loading now disabled.
4/1/10 7:35:02 PM kernel Kext unloading now disabled.
4/1/10 7:35:02 PM kernel Kext autounloading now disabled.
4/1/10 7:35:02 PM kernel Kernel requests now disabled.
4/1/10 7:35:02 PM SystemStarter[20] BRESINKx86Monitoring (640) did not complete successfully
4/1/10 7:35:03 PM kernel Kext unloading is disabled (com.bresink.driver.BRESINKx86Monitoring).
4/1/10 7:35:05 PM SystemStarter[20] The following StartupItems failed to stop properly:
4/1/10 7:35:05 PM SystemStarter[20] /Library/StartupItems/BRESINKx86Monitoring
4/1/10 7:35:05 PM SystemStarter[20] - execution of Startup script failed
4/1/10 7:35:05 PM mDNSResponder[27] mDNSResponder mDNSResponder-214.3 (Feb 11 2010 04:49:16) stopping
4/1/10 7:35:05 PM DirectoryService[38] BUG in libdispatch: 10D573 - 1960 - 0x10004004
4/1/10 7:35:05 PM com.apple.SecurityServer[23] Session 0x13030f7 dead
4/1/10 7:35:05 PM com.apple.SecurityServer[23] Killing auth hosts
4/1/10 7:35:05 PM com.apple.SecurityServer[23] Session 0x13030f7 destroyed
4/1/10 7:35:05 PM kernel VBAKPIKernelControlGetOptionsFiltering: No waiting process found
4/1/10 7:35:06 PM kernel Kext unloading is disabled (com.intego.iokit.BehavioralKext).
4/1/10 7:35:51 PM kernel npvhash=4095
4/1/10 7:35:51 PM kernel PAE enabled
4/1/10 7:35:51 PM kernel 64 bit mode enabled
4/1/10 7:35:51 PM kernel Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386
4/1/10 7:35:51 PM kernel vmpagebootstrap: 968364 free pages and 80212 wired pages
4/1/10 7:35:51 PM kernel standard timeslicing quantum is 10000 us
4/1/10 7:35:51 PM kernel migtable_maxdispl = 73
4/1/10 7:35:51 PM kernel AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
4/1/10 7:35:51 PM kernel AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
4/1/10 7:35:51 PM kernel calling mpopolicyinit for TMSafetyNet
4/1/10 7:35:51 PM kernel Security policy loaded: Safety net for Time Machine (TMSafetyNet)
4/1/10 7:35:51 PM kernel calling mpopolicyinit for Quarantine
4/1/10 7:35:51 PM kernel Security policy loaded: Quarantine policy (Quarantine)
4/1/10 7:35:51 PM kernel calling mpopolicyinit for Sandbox
4/1/10 7:35:51 PM kernel Security policy loaded: Seatbelt sandbox policy (Sandbox)
4/1/10 7:35:51 PM kernel Copyright (c) 1982, 1986, 1989, 1991, 1993
4/1/10 7:35:51 PM kernel The Regents of the University of California. All rights reserved.
4/1/10 7:35:51 PM kernel MAC Framework successfully initialized
4/1/10 7:35:51 PM kernel using 16384 buffer headers and 4096 cluster IO buffer headers
4/1/10 7:35:51 PM bootlog[42] BOOT_TIME: 1270168541 0
4/1/10 7:35:51 PM kernel IOAPIC: Version 0x20 Vectors 64:87
4/1/10 7:35:51 PM kernel ACPI: System State [S0 S3 S4 S5] (S3)
4/1/10 7:35:51 PM kernel mbinit: done (64 MB memory set for mbuf pool)
4/1/10 7:35:51 PM kernel rooting via boot-uuid from /chosen: 07464C6F-6C92-32E1-ACEE-8F3DDA7AD0AF
4/1/10 7:35:51 PM kernel Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
4/1/10 7:35:51 PM kernel com.apple.AppleFSCompressionTypeZlib load succeeded
4/1/10 7:35:51 PM kernel AppleIntelCPUPowerManagementClient: ready
4/1/10 7:35:51 PM kernel BTCOEXIST on
4/1/10 7:35:51 PM kernel wl0: Broadcom BCM4328 802.11 Wireless Controller
4/1/10 7:35:51 PM kernel 5.10.91.27
4/1/10 7:35:51 PM kernel FireWire (OHCI) Lucent ID 5901 built-in now active, GUID 001d4ffffe6ad190; max speed s800.
4/1/10 7:35:51 PM kernel Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PR T0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageD river/ST3500630AS Q Media/IOGUIDPartitionScheme/Customer@2
4/1/10 7:35:51 PM kernel BSD root: disk0s2, major 14, minor 2
4/1/10 7:35:51 PM kernel Warning - com.olympus.CamFWSerialBusProtocolTransport declares no kernel dependencies; using com.apple.kernel.6.0.
4/1/10 7:35:51 PM kernel [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
4/1/10 7:35:51 PM kernel [Bluetooth::CSRHIDTransition] transition complete.
4/1/10 7:35:51 PM kernel CSRUSBBluetoothHCIController::setupHardware super returned 0
4/1/10 7:35:51 PM kernel AppleIntelCPUPowerManagement: initialization complete
4/1/10 7:35:51 PM kernel AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
4/1/10 7:35:51 PM kernel AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RXMAXLE 1024, TXMAXLE 768, STMAXLE 3328
4/1/10 7:35:41 PM com.apple.launchd[1] * launchd[1] has started up. *
4/1/10 7:35:49 PM com.apple.launchd[1] (com.wdc.drivemanagerservice[46]) posix_spawn("/Library/Application Support/WesternDigital/WDDriveManager/WDDriveManagerService", ...): No such file or directory
4/1/10 7:35:49 PM com.apple.launchd[1] (com.wdc.drivemanagerservice[46]) Exited with exit code: 1
4/1/10 7:35:54 PM com.apple.SecurityServer[24] Session 0x5fbff962 created
4/1/10 7:35:54 PM blued[43] Apple Bluetooth daemon started
4/1/10 7:35:54 PM mDNSResponder[28] mDNSResponder mDNSResponder-214.3 (Feb 11 2010 04:49:16) starting
4/1/10 7:35:55 PM kernel yukon: Ethernet address 00:1b:63:a6:7a:37
4/1/10 7:35:55 PM kernel AirPort_Brcm43xx: Ethernet address 00:1c:b3:75:a9:0b
4/1/10 7:35:55 PM kernel IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
4/1/10 7:35:55 PM kernel systemShutdown false
4/1/10 7:35:55 PM kernel Waiting for DSMOS...
4/1/10 7:35:55 PM kernel AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
4/1/10 7:35:55 PM com.apple.usbmuxd[19] usbmuxd-190 built for iTunesNineOne on Mar 8 2010 at 20:25:36, running 32 bit
4/1/10 7:35:55 PM /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[29] Login Window Application Started
4/1/10 7:35:55 PM com.apple.SecurityServer[24] Entering service
4/1/10 7:35:55 PM com.apple.autofsd[44] automount: Mount for UUID=C450DD50-21F5-3F5D-B17B-AC28D768E7E8 has no path for the directory to mount
4/1/10 7:35:55 PM com.apple.autofsd[44] automount: Mount for UUID=7679B4FC-7318-3FBC-94F9-C244CA36C8FC has no path for the directory to mount
4/1/10 7:35:55 PM com.apple.autofsd[44] automount: Mount for UUID=21387D12-BF67-335F-A0ED-EED31F84F771 has no path for the directory to mount
4/1/10 7:35:55 PM com.apple.autofsd[44] automount: Mount for UUID=4527C986-6866-3B1B-AEE2-27101EBB2269 has no path for the directory to mount
4/1/10 7:35:56 PM kernel Previous Shutdown Cause: 5
4/1/10 7:35:56 PM kernel DSMOS has arrived
4/1/10 7:35:56 PM kernel ** Device in slot: SLOT--1 **
4/1/10 7:35:56 PM blued[43] writeExtendedInquiryResponse returned 99
4/1/10 7:35:56 PM configd[40] bootpsessiontransmit: bpf_write(en1) failed: Network is down (50)
4/1/10 7:35:56 PM configd[40] DHCP en1: INIT-REBOOT transmit failed
4/1/10 7:35:56 PM configd[40] setting hostname to "Macintosh-2.local"
4/1/10 7:35:56 PM configd[40] network configuration changed.
4/1/10 7:35:56 PM blued[43] writeExtendedInquiryResponse returned 198
4/1/10 7:35:56 PM configd[40] network configuration changed.
4/1/10 7:35:56 PM configd[40] network configuration changed.
4/1/10 7:35:57 PM kernel Auth result for: 00:18:01:db:56:38 MAC AUTH succeeded
4/1/10 7:35:57 PM kernel AirPort: Link Up on en1
4/1/10 7:35:58 PM kernel AirPort: RSN handshake complete on en1
4/1/10 7:35:58 PM configd[40] network configuration changed.
4/1/10 7:36:00 PM TechToolProDaemon[47] 3891612: (CGSLookupServerRootPort) Untrusted apps are not allowed to connect to or launch Window Server before login.
4/1/10 7:36:00 PM TechToolProDaemon[47] kCGErrorRangeCheck: On-demand launch of the Window Server is allowed for root user only.
4/1/10 7:36:00 PM TechToolProDaemon[47] kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
4/1/10 7:36:00 PM com.micromat.TechToolProDaemon[47] Thu Apr 1 19:36:00 Macintosh-2.local TechToolProDaemon[47] <Warning>: 3891612: (CGSLookupServerRootPort) Untrusted apps are not allowed to connect to or launch Window Server before login.
4/1/10 7:36:00 PM com.micromat.TechToolProDaemon[47] Thu Apr 1 19:36:00 Macintosh-2.local TechToolProDaemon[47] <Error>: kCGErrorRangeCheck: On-demand launch of the Window Server is allowed for root user only.
4/1/10 7:36:00 PM com.micromat.TechToolProDaemon[47] Thu Apr 1 19:36:00 Macintosh-2.local TechToolProDaemon[47] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
4/1/10 7:36:00 PM /Library/PreferencePanes/TechTool Protection.prefPane/Contents/PlugIns/TechToolProDaemon.app/Contents/MacOS/TechT oolProDaemon[47] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
4/1/10 7:36:00 PM com.micromat.TechToolProDaemon[47] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
4/1/10 7:36:02 PM kernel [08bb4000][BNBMouseDevice::init][51] init is complete
4/1/10 7:36:02 PM kernel [08bb4000][BNBMouseDevice::handleStart][51] Done
4/1/10 7:36:02 PM kernel [090dc600][AppleMultitouchHIDEventDriver::start] entered
4/1/10 7:36:02 PM kernel [090d0f00][AppleMultitouchDevice::start] entered
4/1/10 7:36:02 PM com.apple.SystemStarter[20] Starting HP IO Monitor
4/1/10 7:36:02 PM com.apple.SystemStarter[20] Starting HP Trap Monitor
4/1/10 7:36:02 PM com.apple.SystemStarter[20] /Library/StartupItems/HP Trap Monitor/HP Trap Monitor: line 15: /Library/Printers/hp/hpio/HPIO Trap Monitor.app/Contents/MacOS/HPIO Trap Monitor: No such file or directory
4/1/10 7:36:03 PM com.intego.VirusBarrierX6.realtime.daemon[126] ba_init Mon Mar 22 19:04:59 2010
4/1/10 7:36:03 PM com.apple.autofsd[44] automount: Mount for UUID=C450DD50-21F5-3F5D-B17B-AC28D768E7E8 has no path for the directory to mount
4/1/10 7:36:03 PM com.apple.autofsd[44] automount: Mount for UUID=7679B4FC-7318-3FBC-94F9-C244CA36C8FC has no path for the directory to mount
4/1/10 7:36:03 PM com.apple.autofsd[44] automount: Mount for UUID=21387D12-BF67-335F-A0ED-EED31F84F771 has no path for the directory to mount
4/1/10 7:36:03 PM com.apple.autofsd[44] automount: Mount for UUID=4527C986-6866-3B1B-AEE2-27101EBB2269 has no path for the directory to mount
4/1/10 7:36:04 PM virusbarriers[49] VirusBarrier X6 OK
4/1/10 7:36:05 PM kernel ERROR: VendorAccelerator::setdisplay_mode_andvram() call to fFramebuffers[1].framebuffer->getPixelInformation() result: 0xE00002F0
4/1/10 7:36:05 PM kernel ERROR: VendorAccelerator::setdisplay_mode_andvram() call to fFramebuffers[1].framebuffer->getPixelInformation() result: 0xE00002F0
4/1/10 7:36:05 PM kernel ERROR: VendorAccelerator::setdisplay_mode_andvram() call to fFramebuffers[1].framebuffer->getPixelInformation() result: 0xE00002F0
4/1/10 7:36:05 PM com.apple.SecurityServer[24] Session 0x1042617 created
4/1/10 7:36:05 PM com.apple.SecurityServer[24] Session 0x1042617 attributes 0x30
4/1/10 7:36:06 PM loginwindow[29] Login Window Started Security Agent
4/1/10 7:36:08 PM WindowServer[80] kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
4/1/10 7:36:08 PM com.apple.WindowServer[80] Thu Apr 1 19:36:08 Macintosh-2.local WindowServer[80] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
4/1/10 7:36:09 PM SecurityAgent[161] Showing Login Window
4/1/10 7:36:09 PM mds[27] (Error) DiskStore: Unable to create/find index location
4/1/10 7:36:10 PM com.apple.autofsd[44] automount: Mount for UUID=C450DD50-21F5-3F5D-B17B-AC28D768E7E8 has no path for the directory to mount
4/1/10 7:36:10 PM com.apple.autofsd[44] automount: Mount for UUID=7679B4FC-7318-3FBC-94F9-C244CA36C8FC has no path for the directory to mount
4/1/10 7:36:10 PM com.apple.autofsd[44] automount: Mount for UUID=21387D12-BF67-335F-A0ED-EED31F84F771 has no path for the directory to mount
4/1/10 7:36:10 PM com.apple.autofsd[44] automount: Mount for UUID=4527C986-6866-3B1B-AEE2-27101EBB2269 has no path for the directory to mount
4/1/10 7:36:10 PM mds[27] (Error) DiskStore: Unable to create/find index location
4/1/10 7:36:10 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 23
4/1/10 7:36:10 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 22
4/1/10 7:36:10 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 19
4/1/10 7:36:10 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 18
4/1/10 7:36:10 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 17
4/1/10 7:36:10 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 15
4/1/10 7:36:11 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 16
4/1/10 7:36:11 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 21
4/1/10 7:36:11 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 41
4/1/10 7:36:11 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 40
4/1/10 7:36:11 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 37
4/1/10 7:36:11 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 36
4/1/10 7:36:11 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 35
4/1/10 7:36:11 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 33
4/1/10 7:36:11 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 34
4/1/10 7:36:11 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 39
4/1/10 7:36:12 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 32
4/1/10 7:36:12 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 31
4/1/10 7:36:12 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 28
4/1/10 7:36:12 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 27
4/1/10 7:36:12 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 26
4/1/10 7:36:12 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 24
4/1/10 7:36:12 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 25
4/1/10 7:36:12 PM com.apple.notifyd[13] EV_DELETE failed for file watcher 30
4/1/10 7:36:13 PM ntpd[16] time reset +0.146759 s
4/1/10 7:36:13 PM warmd[18] [fetcheropenfile:936] open("/var/db/dyld/dyldshared_cache_x8664") => -1 (errno: 2)
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=C450DD50-21F5-3F5D-B17B-AC28D768E7E8 has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=7679B4FC-7318-3FBC-94F9-C244CA36C8FC has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=21387D12-BF67-335F-A0ED-EED31F84F771 has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=4527C986-6866-3B1B-AEE2-27101EBB2269 has no path for the directory to mount
4/1/10 7:36:13 PM warmd[18] [fetcheropenfile:936] open("/var/db/dyld/dyldshared_cachei386") => -1 (errno: 2)
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=C450DD50-21F5-3F5D-B17B-AC28D768E7E8 has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=7679B4FC-7318-3FBC-94F9-C244CA36C8FC has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=21387D12-BF67-335F-A0ED-EED31F84F771 has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=4527C986-6866-3B1B-AEE2-27101EBB2269 has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=C450DD50-21F5-3F5D-B17B-AC28D768E7E8 has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=7679B4FC-7318-3FBC-94F9-C244CA36C8FC has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=21387D12-BF67-335F-A0ED-EED31F84F771 has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=4527C986-6866-3B1B-AEE2-27101EBB2269 has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=C450DD50-21F5-3F5D-B17B-AC28D768E7E8 has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=7679B4FC-7318-3FBC-94F9-C244CA36C8FC has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=21387D12-BF67-335F-A0ED-EED31F84F771 has no path for the directory to mount
4/1/10 7:36:13 PM com.apple.autofsd[44] automount: Mount for UUID=4527C986-6866-3B1B-AEE2-27101EBB2269 has no path for the directory to mount
4/1/10 7:36:18 PM SecurityAgent[161] User info context values set for normankhester
4/1/10 7:36:18 PM SecurityAgent[161] Login Window Showing Progress
4/1/10 7:36:18 PM SecurityAgent[161] Login Window done
4/1/10 7:36:18 PM loginwindow[29] Login Window - Returned from Security Agent
4/1/10 7:36:18 PM loginwindow[29] USER_PROCESS: 29 console
4/1/10 7:36:18 PM com.apple.launchd.peruser.501[200] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
4/1/10 7:36:21 PM 1PasswordAgent[244] Starting 1PasswordAgent 3.0.9 #30535 built Feb 22 2010 12:27:04
4/1/10 7:36:21 PM 1PasswordAgent[244] reloadAllObjects
4/1/10 7:36:21 PM 1PasswordAgent[244] Database (agilekeychain:/Users/normankhester/Library/Application Support/1Password/1Password.agilekeychain) load time [Cache]: 0.027 (121 objects)
4/1/10 7:36:21 PM 1PasswordAgent[244] Beginning backup to '/Users/normankhester/Library/Application Support/1Password/Backups/1Password 2010-04-01 193621 (121 items).agilekeychain_backup'
4/1/10 7:36:22 PM com.apple.launchd.peruser.501[200] (com.apple.Kerberos.renew.plist[238]) Exited with exit code: 1
4/1/10 7:36:46 PM kernel AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
4/1/10 7:36:46 PM configd[40] network configuration changed.
4/1/10 7:36:47 PM kernel System Sleep
4/1/10 7:36:47 PM kernel Wake reason = UHC4
4/1/10 7:36:47 PM kernel System Wake
4/1/10 7:36:47 PM kernel Previous Sleep Cause: 0
4/1/10 7:36:47 PM kernel EIR is not supported.
4/1/10 7:36:47 PM kernel en1: 802.11d country code set to 'TW'.
4/1/10 7:36:47 PM kernel en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 56 60 64 149 153 157 161 165
4/1/10 7:36:47 PM kernel Auth result for: 00:18:01:db:56:38 MAC AUTH succeeded
4/1/10 7:36:47 PM kernel AirPort: Link Up on en1
4/1/10 7:36:48 PM kernel AirPort: RSN handshake complete on en1
4/1/10 7:36:48 PM configd[40] network configuration changed.
4/1/10 7:36:48 PM mDNSResponder[28] RegisterInterface: Frequent transitions for interface en1 (192.168.0.3)
4/1/10 7:36:48 PM [0x0-0x17017].backupd-helper[263] Not starting Time Machine backup after wake - less than 60 minutes since last backup completed.
4/1/10 7:36:48 PM kernel ERROR: VendorAccelerator::setdisplay_mode_andvram() call to fFramebuffers[1].framebuffer->getPixelInformation() result: 0xE00002F0
4/1/10 7:36:51 PM mDNSResponder[28] RegisterInterface: Frequent transitions for interface en1 (FE80:0000:0000:0000:021C:B3FF:FE75:A90B)
4/1/10 7:36:54 PM com.apple.autofsd[44] automount: Mount for UUID=C450DD50-21F5-3F5D-B17B-AC28D768E7E8 has no path for the directory to mount
4/1/10 7:36:54 PM com.apple.autofsd[44] automount: Mount for UUID=7679B4FC-7318-3FBC-94F9-C244CA36C8FC has no path for the directory to mount
4/1/10 7:36:54 PM com.apple.autofsd[44] automount: Mount for UUID=21387D12-BF67-335F-A0ED-EED31F84F771 has no path for the directory to mount
4/1/10 7:36:54 PM com.apple.autofsd[44] automount: Mount for UUID=4527C986-6866-3B1B-AEE2-27101EBB2269 has no path for the directory to mount
4/1/10 7:37:12 PM mDNSResponder[28] DeregisterInterface: Frequent transitions for interface en1 (FE80:0000:0000:0000:021C:B3FF:FE75:A90B)
4/1/10 7:37:13 PM kernel AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
4/1/10 7:37:14 PM configd[40] network configuration changed.
4/1/10 7:37:14 PM kernel System Sleep
4/2/10 4:40:00 AM kernel Wake reason = RTC

Similar Messages

  • Odd Calc Order Behavior

    Hello all,
    I've put together a hybrid analysis cube and I'm experiencing some odd calc order behavior. It appears the years are calculating backwards.
    I load my 2007 end balances and calc forward three years. 2008 is correct, but 2009 and 2010 are incorrect. They are incorrect inasmuch as the calcs that require 2008/2009 end balances are incorrect. So I run the script again and now 2009 is right, but 2010 is incorrect. Then I run it once more and 2010 is correct.
    It appears the end balances for 2008 and 2009 aren't available for 2009 and 2010, respectively. Thus, I think 2010 is calcing first, but with no 2009 end bals, so it's off. Then 2009 goes, again no end bals, so it's off. Then 2008 calcs, and since 2007 end bals are in there, it's calcing correctly. Thus, I have to calc again two times for 2009 and 2010 to be correct.
    Here's my script:
    Fix (@IRSiblings("2008"),"ScenarioMbr")
    CALC ALL EXCEPT DIM("Years","Scenario");
    Endfix
    ScenarioMbr is a level 0 descendant of the Scenario dimension.
    Thanks for any help anyone has.

    I would suggest checking on your outline order. It sounds like your ending balance hasn't been calculated by the time the beginning balance needs it (as evidenced by your three passes). The order of members in your FIX statement has no bearing on the calculation order. By this, I mean make sure that your Years dimension is ordered as follows...
    Years
    + 2007
    + 2008
    + 2009
    + 2010
    Also, make sure that your periods (where your months are is, assuming it is a different dimension) is located above your Years dimension.
    Lastly, how are you facilitating getting your Ending balances into your Beginning balances? Sometimes the sequencing for this type of work is improtant as well. For example, if your Ending Balance is a two-pass, it will not be ready until a second pass is done.
    IF this doesn't help, maybe provide one of the BegBal members that isn't working, your outline order, the order of the Years dimension, and the dense/sparse settings (assuming BSO).
    Good Luck!!

  • Odd Junk Mail Behavior

    I've been experiencing odd Junk Mail behavior on my Mac; I've got the Mail app set so it puts the emails it thinks is Junk in the Junk folder. I do this because I've noticed that certain legitimate emails keep ending up in the Junk folder automatically.
    I've also noticed that some of the emails in the Junk folder have not actually been flagged as Junk Mail, they were not colored brown by the Junk Mail rule and there is no button available to tell Mail it's not Junk. How do I stop Mail from flagging something as Junk when it doesn't seem to tag it as Junk but it still ends up in the Junk folder?
    I see emails tagged as Junk in the Junk folder that are legit, so I click the "Not Junk" button and move them back to the proper mail folder. But the next time I get mail from the same source, it gets flagged and tagged as Junk again. I thought the Mail app learns from the training we give it. How do I resolve this situation?
    I've already set the Junk filtering to not filter emails from recipients who are in my Address Book.

    Either you’ve messed with the Preferences > Junk Mail > Advanced settings, or those settings have become corrupt, or you have one or more rules that have a bearing on this.
    Assuming it isn’t the latter, try this:
    1. Go to Preferences > Junk Mail, disable junk mail filtering, then enable it again. This resets the rule that governs what the junk filter does.
    2. Choose either Training or Automatic mode (it doesn’t matter) and leave the other options checked. Click Advanced to see how the junk filter rule is defined now if you want, but don’t touch anything there.
    3. Reset the junk filter database (Preferences > Junk Mail > Reset).

  • Auto-sleep, okay. Manual sleep, and it wakes back up. ???

    My iMac keeps waking itself up after I set it to sleep. It only stays asleep if the auto-sleep time runs out in the power saver under system preferences. Why won't manual sleep (through the apple menu) work?
    Message was edited by: Enio Rigolin2

    Hi Enio
    First eject and disconnect any External HD's, iPod's, iPhone's, iPad's, other USB devices, turn off your printer and see if it will sleep.
    Next reset the SMC > http://support.apple.com/kb/HT3964
    +1. Shut down the computer.+
    +2. Unplug the computer's power cord.+
    +3. Press and hold the power button for 5 seconds.+
    +4. Release the power button.+
    +5. Attach the computers power cable.+
    +6. Press the power button to turn on the computer+
    Then if that does not help, see > http://support.apple.com/kb/HT1776
    Dennis

  • Manual Sleep Problem

    Occasionally, when I try to put my G5 to sleep manually, it won't go to sleep. I always make sure that all powered peripherals are unplugged. And then the problem goes away after restarting. But the the manual sleep problem returns within a week or so. I prefer to keep my Energy Saver on "Never Sleep" because I run Pro Tools on my machine and it doesn't support sleep mode.
    Has anyone else had this problem?
    Thanks

    David Penick1-
    From your description it is most likely one of the externally attached devices.
    The USB and FW hubs built in to the Apple monitors have a habit of causing this problem. I would disconnect those hubs first and see what happens.
    It may be one of the drives as well.
    I would suggest disconnecting all external peripherals except keyboard and mouse and see if the problem goes away. If it does, keep adding devices one at a time until you discover which one is causing the problem.
    Luck-
    -DaddyPaycheck

  • Preventing Manual Sleep in Tiger

    I maintain a couple of Intel iMacs running 10.4.11 that run some launchd tasks at a certain time every night. If the tasks run successfully, the machines shut themselves down later in the night. If the tasks encounter a problem, the scheduled shutdown is aborted.
    Despite gentle "encouragement", the standard users that run the machines occasionally put the machines to sleep manually. I can set the machines to wake up at a certain time...but, because of a bug in launchd on 10.4.11 the time spent asleep is ADDED to the scheduled time of the task. For example, if I schedule a task to run at 1am -- and the machine has been asleep for 4 hours --- the task won't run until 5am at the earliest. Considering that these machines might be asleep for days at a time, manual sleep can cause some real problems. This bug also mangles the scheduled shutdown.
    Is there a way I can prevent users from manually putting their machines to sleep? Is there a safe way to disable the Sleep menu?
    Thanks.

    Limnos wrote:
    Maybe something here, but I would make sure you had a good backup first...
    http://hints.macworld.com/article.php?story=20050422121335362
    This hint suggests editing the menu interface files in /System. In my own testing, it seems to work ok...still, I am nervous about pushing this out to a half-dozen aged machines.
    also related things here. Maybe Applescript could be used as a reminder?
    http://hints.macworld.com/article.php?story=20091104040449752
    Some kind've automated reminder...? It's a possibility...but they've already shown a willingness to disregard reminders...!

  • Manually "sleeping" my MAC results in a state where I cannot wake it

    I'm running 10.5.6, and if I manually sleep my iMAC, I cannot wake it. Only solution is to push and hold the power button for around 10 secs (or unplug the unit) and then power back on.
    Solutions?
    - Greg

    I don't normally "sleep" my Mac. Today a family member visiting manually put it to "sleep".
    When I tried to wake the Mac .... the USB hub came to life (lights) .... the scanner warmed up and reset, but the screen was dark and the keyboard/mouse dead.
    I had to shut it down with the power button and restart. I have never had this happen before, but it is quite rare for me to "sleep" my Mac.

  • Odd sleep behavior

    Here's a new one on me.
    I fianlly took the plunge to add eSATA to my MacBookPro (original version) with an express card eSATA. This is connected to a 400gig external drive. No more hacing to load from the cheap Canon camera onto the internal drive and then transfer top an externall firewire drive!
    Here's the odd thing: while batch capturing, the display (23" Cinema Display hooked up to the laptop) goes to sleep after 15-20 miniutes. Pressing any key (like [shift]) to wake up the display messes up the capture.
    I ended up "capturing now" in 10 minute chunks just to get the session moving. Bu this isn't good, obviously.
    The preferences are set to "never sleep" for both the display an the hard drive(s). Yet the monitor is clearly going ot sleep. Don't know about the laptop internal drive, as I can't hear or see it. Something's amiss.
    Setup: MacBook Pro, 2 gig, eSATA via express card, latest updates of FCP Studio (1, not 2), Canon consumer camera used as tape deck (I know, not good, but all that's available a the moment).
    Thoughts?
    Thanks in advance.
    Jeff M.

    So the Cinema Display is the only active monitor...the laptop lid is closed. Only one monitor shows up in the preferences pane. All sleep settings are already set to "never." Drive sleep is set to never. Screen saver is set to never.
    These settings were already in place - I didn't have to make any changes. I'll try to load some footage when I get a few moments to breathe.
    Jeff M.

  • Nexus 5000 - Odd Ethernet interface behavior (link down inactive)

    Hi Guys,
    This would sound really trivial but it is very odd behavior.
    - We have a server connected to a 2, Nexus 5000s (for resiliancy)
    - When there is no config on the ethernet interfaces whatsoever, the ethernet interface is UP / UP, there is minimal amount of traffic on the link etc. E.g.
    Ethernet1/16 is up
      Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
      Description: shipley-p1.its RK14/A13
      MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is access
      full-duplex, 10 Gb/s, media type is 1/10g
      Beacon is turned off
      Input flow-control is off, output flow-control is off
      Rate mode is dedicated
      Switchport monitor is off
      Last link flapped 00:00:07
      Last clearing of "show interface" counters 05:42:32
      30 seconds input rate 0 bits/sec, 0 packets/sec
      30 seconds output rate 96 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 0 bps, 0 pps; output rate 8 bps, 0 pps
      RX
        0 unicast packets  0 multicast packets  0 broadcast packets
        0 input packets  0 bytes
        0 jumbo packets  0 storm suppression packets
        0 runts  0 giants  0 CRC  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        0 unicast packets  163 multicast packets  0 broadcast packets
        163 output packets  15883 bytes
        0 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble
        0 Tx pause
      1 interface resets
    - As soon as I configure the link to be an access port, the link goes down, flagging "inactivity" E.g.
    sh int e1/16
    Ethernet1/16 is down (inactive)
      Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
      Description: shipley-p1.its RK14/A13
      MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is access
      auto-duplex, 10 Gb/s, media type is 1/10g
      Beacon is turned off
      Input flow-control is off, output flow-control is off
      Rate mode is dedicated
      Switchport monitor is off
      Last link flapped 05:38:03
      Last clearing of "show interface" counters 05:41:33
      30 seconds input rate 0 bits/sec, 0 packets/sec
      30 seconds output rate 0 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
      RX
        0 unicast packets  0 multicast packets  0 broadcast packets
        0 input packets  0 bytes
        0 jumbo packets  0 storm suppression packets
        0 runts  0 giants  0 CRC  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        0 unicast packets  146 multicast packets  0 broadcast packets
        146 output packets  13083 bytes
        0 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble
        0 Tx pause
      0 interface resets
    - This behavior is seen on both 5Ks
    - I've tried using a different set of ports, changed SFPs, and fibre cabling to no avail
    - I can't seem to understand this behavior?!  In that, why would configuring the port cause the link to go down?
    - If anyone has experience this before, or could shed some light on this behavior, it would be appreciated.
    sh ver
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
    The copyrights to certain works contained herein are owned by
    other third parties and are used and distributed under license.
    Some parts of this software are covered under the GNU Public
    License. A copy of the license is available at
    http://www.gnu.org/licenses/gpl.html.
    Software
      BIOS:      version 1.2.0
      loader:    version N/A
      kickstart: version 4.2(1)N1(1)
      system:    version 4.2(1)N1(1)
      power-seq: version v1.2
      BIOS compile time:       06/19/08
      kickstart image file is: bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin
      kickstart compile time:  4/29/2010 19:00:00 [04/30/2010 02:38:04]
      system image file is:    bootflash:/n5000-uk9.4.2.1.N1.1.bin
      system compile time:     4/29/2010 19:00:00 [04/30/2010 03:51:47]
    thanks
    Sheldon

    I had identical issue
    Two interfaces on two different FEXes were INACTIVE. I have two Nexus 5596 in vPC and A/A FEXes.
    I also use config-sync feature.
    Very same configuration was applied to other ports on other FEXes and they were working with no problems.
    interface Ethernet119/1/1
      inherit port-profile PP-Exchange2003
    I checked VLAN status associated with this profile and it was active (of course it was, other ports were ok).
    I solved it by removing port profile from this port and re-applied it... voila, port changed state to up!
    Very very strange.

  • IMac no longer connects to Wi-Fi on startup or after manual sleep

    Hello folks,
    I need some suggestions. Here is a description of the problem (as brief as possible):
    My late '09 21.5" iMac spur-of-the-moment didn't connect to my wireless network on a random day (2 or so weeks ago). I thought nothing of it, until I noticed it happening after I put it to sleep that same evening. I turned it off hoping it wouldn't happen again.
    It did.
    I have since been in contact with an Apple support person (it's still under warranty) and haven't talked to him in a while. I'm going to call him within the next few days (back in school now) to see if he has any solutions. Here is some more info without stories:
    Tried:
    Deleting preference files (all related to Airport and System Configuration
    Removing the Airport service altogether and adding it back on
    Turned router off and back on
    Changed routers completely (from an old Netgear to a new Netgear from Comcast)
    Turned modem off and took backup battery out
    Removed all references to wi-fi networks in Keychain Access
    Turned Firewall off in Sys Prefs and in Antivirus software (which will be deleted soon)
    Removed any unused login items/programs
    Other tidbits:
    Only happens at start-up and when I put it to sleep (not if it goes to sleep itself)
    Message pops up about no preferred networks being available as soon as my desktop loads up (my network is always on the top with 5 bars)
    Nothing changed on my Mac or Internet or environmentally
    During these changes I've restarted my Mac some 20 or 30 times.
    Running 10.6.4 and have all updates.
    Trust me, many things were covered in our 3 hour phone conversation. And as I said earlier, I will be calling him soon.
    I have never had a problem with my Mac before and am curious as to why this has happened so spur-of-the-moment.
    If you need any other specs, please ask.

    My previous 27" iMac is also '09 model just like your 21.5" iMac. I had the same connection issue as what you have described. But once the wireless connection had been made manually, the connection was rather reliable with reasonable bandwidth and without dropped connection. The problem was not resolved until Apple released updates for Mac OS 10.6.4 and transmission power of wireless router was increased to maximum. I suppose the problem was partly because of changes to aluminum unibody casing and smaller antenna. The only difference between your setup and mine is different wireless router (Netgear vs Airport Extreme).
    If you are confident on good signal strength, perhaps execute Software Update from Apple icon on main menu bar to make sure that all updates have been applied properly. Last resort is to reinstall Mac OS 10.6.4 from scratch with all updates applied. There is also one easy way to monitor signal strength after connection has been made manually, pressing on option key while right clicking on Airport icon on main menu bar. The field RSSI indicates signal strength in negative dB value (smaller negative value means higher signal strength).
    If you do not want to mess with the Netgear wireless router, one way is to bypass iMac built-in antenna all together by using Airport Express. Based on my regular monitoring of signals on iMac and Airport Express, Airport Express has much higher and consistent signal strength than unibody iMac. Plug in Airport Express on power socket outlet near your iMac, connect a Ethernet cable from iMac to Airport Express and use Airport Express as wireless bridge between main Netgear wireless router and iMac. Better still if you can afford to discard the Netgear router, just replace Netgear with Airport Express all together and use newer 802.11n protocol instead of older 802.11b/g protocol for better speed and range (assuming the Netgear router does not support 802.11n protocol). The Airport Express can also be doubled as base station for sharing printer and speaker in wireless network.
    Apple has to assume responsibility to ensure all its Airport wireless products work properly with all models of Mac whereas it is different story for other brands of wireless products. I once was using Belkin wireless router but had to switch to Airport Extreme/Express because of issues occurred whenever Apple released updates for Mac products. If there is problem between iMac and Airport Express rather than Netgear, there is no reason Apple technical support can ignore the problem (particularly if you have purchased AppleCare for your iMac which cover all Apple accessories as well).

  • Odd Time Capsule behavior

    My time capsule was working fine since I set it up in late June. I then returned from a month in Europe (sorry for whining after a month in Europe). I don't know when the strange behavior began precisely. I do know that I saw the desktop icon many times and even saw backups made of August and I think even September.
    Now, however, I cannot get my time capsule to work. It shows the last backup as July 7, which is not accurate--I know of August and possibly September backups. And it simply tries to connect "preparing" on the blue activity bar.
    The only thing I can think of is a password issue. I don't recall ever setting a password for time capsule but perhaps I'm loosing it. Should I just reset the time capsule (hard reset) and see if it asks me to set up a new password? I occasionally get a message asking for a password and every password I put in that I think could possibly be mine gets kicked back. (BTW, since the first or second time time capsule worked, I have used it only wirelessly. If I hard reset I would probably connect it with hard wire connection.
    Context: I'm new to Mac. I was a 20-plus year wintel user until June, 2008.

    First, let's find out why it's stuck "Preparing...". So consider the causes I noted in the previous post.
    The only thing I can think of is a password issue. I don't recall ever setting a password for time >capsule but perhaps I'm loosing it. Should I just reset the time capsule (hard reset) and see if it asks me to set up a new password?
    Again, if the TCs light shows green, then you shouldn't need to reset it.
    I occasionally get a message asking for a password and every password I put in that I think could possibly be mine gets kicked back.
    It will be important to know what is going on, or what you are doing when it asks for the password. Is it asking for a password only when Time Machine attempts a backup? Consider this:
    Launch Airport Utility --> Manual Setup --> Time Capsule tab.
    For "Time Capsule password" are there black dots where you would type a password? If so do you remember what you put there? If you don't then enter a new password.
    Next, is there a check mark beside "Remember this password in my Keychain"? If not, you will always be asked for a password any time the Time capsule is accessed. Put a check mark there.
    Also, click on "Disks" in the tool bar above.
    Click "File Sharing" tab.
    What is selected beside "Secure Shared Disks"? If it says "With Accounts" or "With a Disk Password" then the system will ask you for a password every time it mounts the TC hard disk. If you switch it to "With Time Capsule Password" then use the password you designated a moment ago in the Time Capsule" tab. It should only ask you once and then never again - because you had checked "Remember in keychain".
    If you have made any changes then click "Update".
    BTW, since the first or second time time capsule worked, I have used it only wirelessly. If I hard reset I would probably connect it with hard wire connection.
    Doing a hard reset, will not erase the hard drive, so you data will still be there. You won't need to connect it directly to your Mac unless you want to start over and do another full backup.
    Let us know if any of this helps
    Glenn

  • Odd Port 139 Behavior

    Hi everyone,
    I've been running in to some trouble with my university's IT department. They say that my Mac Mini (1.66GHz CoreDuo) has times when it's trying to connect to something via port 139 (netbios-ssn). They claim that it averages over 1 attempt per second. However, in all of my snooping, using Activity Monitor, Network Utility, and Little Snitch, I've never noticed anything odd. I do admit that I might not be observing it at the correct times, but I would like to get to the bottom of this. Currently my IT department has my computer "quarantined" and won't authorize it to access the network again until I can sort this out.
    Have any of you heard of something like this before (the 139 connection attempts)?
    Any help is GREATLY appreciated.
    Thanks,
    Dave DeLong

    At least for me, anytime I use a file dialog I get a message from little snitch telling me that it's trying to connect to port 139 - so any time I try to open or save a document, etc. Little Snitch tells me that the program I'm using is trying to connect via port 139.
    Same for when I try to choose a network printer.
    The snitch tells me about connect attempts over port 139 quite often, but not once per second.
    Finder is doubtless doing its own queries to "discover" what's out there on the network.
    I have a hard time believing it's even an issue, as every Mac, Linux, and Unix box that tries to connect to the windows shares on the network are going to have similar behavior. The Engineering department alone would be *+up in arms+* over such a policy. **** hath no fury like a few dozen EE students whose computers are banned.
    First because it's asinine - a connection attempt over port 139 is fairly innocent; you have to discover what's on the CIFS/SMB (ie. Windows shares) network somehow. Pretty much every non-Microsoft device (including Macs) that can access Windows shares uses "samba", which can be set to periodically ping the network to discover shares on the network. The whole point is so things "plug and play" without the IT manager having to do anything.
    SMB/CIFS is a very chatty protocol to begin with...

  • Odd battery/charge behavior

    Something odd happened today with my MBP (2011)...  I'm working away with it while it's plugged into power and all of a sudden it starts charging... but I never unplugged it or lost power or anything (and it's on a mondo UPS anyway).
    It's been showing 98% instead of 100%, but showing "fully charged" with a green light and from reading the articles from Apple this is totally normal.  I did manage to get it to show 100% after a SMC reset, but after a subsequent reboot it went back to 98%.  Anyway, it actually looks like it's going to charge to 100% now (99% and still showing orange light).
    Has anyone seen this behavior?  Normal?  Something to consider going to Apple store about?
    Thanks.

    I understand the system will charge when it needs to, but in all my days with MacBook's and the like I've never seen one up and start charging AFTER being plugged in for several days and without any provocation (i.e. unplugging it for a few minutes).
    My battery info all looks really good and the condition says "normal" so as long as "normal" is the same as "good" then it's probably fine.  Still odd, but fine.

  • Odd Smart Mailbox Behavior

    I receive a lot of mail with attachments so I created a Smart Mailbox with the following conditions -- ALL must be met:
    1. Contains Attachments
    2. Date Received is not in the last 2 weeks
    My goal is to keep my mail intact for 2 weeks, and then delete the attachments so I can save disk space.
    The Smart Mailbox works but not as I expected. I would assume that every day there would be at least one message that meets the conditions since I receive at least one attachment per day. What actually occurs is that the Smart Mailbox only shows mail every two weeks but some of the messages are older than two weeks -- as old as four weeks. The behavior seems odd to me.
    Any suggestions?
      Mac OS X (10.4.3)  

    If it's "not in the last 2 weeks" then it'll show messages older than the last 2 weeks. Do you want to show messages that are 2 weeks old? If yes, then change "not in the last 2 weeks" to "is exactly 2 weeks".

  • Odd file move behavior

    On my startup disk, I have a movie file (.mov) and a folder I want to collect movies in. Straightforward enough.
    So I click/drag the .mov file onto the folder. It shows me the green + icon, and when I let go, it COPIES the file into the folder, not by simply MOVING the file from the disktop to the folder. Wha?
    When I grab that same file in the folder and move it to the disktop, it works as expected, insisting that it must be DUPLICATED, replacing the disktop, original file.
    OK. So instead of doing that, I decide to trash the original file, then move the version out of the folder and back to the disktop.
    In order to do that, I use the contextual menu that drops down with Control+mouse click. It now asks me for my administrator password to do the trash move. (???)
    Once the original has been tossed, the file will now move from folder to disktop and back to folder with complete impunity. But if I try this with another .mov file, the process starts all over again.
    No extra key combo during the original move gets rid of the + icon.
    Permissions were repaired. No change.
    Log off was cycled, no change.
    Obviously somehow this disk has picked up wierdness when Leopard replaced well-tempered Tiger on it, but where is the checkbox that dumps this odd behavior?
    No Right-click on the mighty mouse will bring down the contextual menu at all.

    Yea! The Mac is back on track!
    It took extra innings and a visit to 1 800 APL CARE to get to the bottom of it, but this therapy should be on everyone's A-list: The Install disk's version of Disk Utility is significantly different from any version you can install on your hard drives. Or so it would appear.
    Where the Disk Utility can be there for you on two different hard drives connected to the same computer, running it from different drives is not at all the same - in visible results - as running it directly from the OS X Install Disk.
    You can have several disks with OS X on them and run Disk Utility on your main startup disk from those, but they won't find all the messy permissions that are gumming up your system.
    It took yet another previous back up Restore cycle, an extra clean install, followed immediately by an Install Disk run of Disk Utility's First Aid/Repair Disk Permissions to clear the cobwebs. Frequent re-weedings (after any program installs or upgrades from anybody, including Apple's own) finds more things to fix. Not always, but frequently.
    The Install Disk's Disk Utility--it's not just for breakfast any more.

Maybe you are looking for